Using Web services for business integration
| Autor Corporativo: | |
|---|---|
| Otros Autores: | , , , , , , , , |
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Research Triangle Park, NC :
IBM, International Technical Support Organization
c2004.
|
| Edición: | 1st ed |
| Colección: | WebSphere software.
IBM redbooks. |
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009644317906719 |
Tabla de Contenidos:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Chapter 1. Web services technology and standards
- 1.1 Web services architecture
- 1.2 Transport layer
- 1.2.1 HTTP
- 1.2.2 JMS
- 1.2.3 SMTP
- 1.2.4 Emerging standards for transport
- 1.3 Service communication protocol layer
- 1.3.1 SOAP
- 1.4 Service description layer
- 1.4.1 XML
- 1.4.2 ebXML
- 1.4.3 WSDL
- 1.5 Service layer
- 1.5.1 Web services and J2EE
- 1.5.2 A new set of Java Specification Requests
- 1.5.3 The Apache Web Services Invoation Framework
- 1.6 Business process layer
- 1.6.1 Process Choreographer
- 1.6.2 WSFL and XLANG
- 1.6.3 Emerging standards for business process
- 1.7 Service registry layer
- 1.7.1 Static and dynamic Web services
- 1.7.2 UDDI
- 1.8 Policy layer
- 1.8.1 Security layer
- 1.8.2 Security at the transport layer
- 1.8.3 Security at the service communication protocol layer
- 1.8.4 Security at the service description layer
- 1.8.5 Emerging standards for security
- 1.8.6 Web services security references for further information
- 1.9 Transaction layer
- 1.9.1 WS-Coordination
- 1.9.2 WS-Transaction
- 1.9.3 Conversation support for Web services
- 1.10 Management layer
- Chapter 2. Sample application
- 2.1 Business motivation
- 2.2 Use cases
- 2.3 Applying the Patterns for e-business
- 2.4 Overall process/application description
- 2.4.1 Add a new contact
- 2.4.2 Use a service
- 2.4.3 Quota re-authorization
- 2.4.4 Remove contact
- 2.4.5 Summary
- 2.5 AccessTracker interfaces and tables
- 2.6 Building and deploying the DB2 database
- 2.6.1 Installing DB2 Enterprise Server Edition 8.1
- 2.6.2 Create database and application table
- 2.7 Implementing the application
- 2.8 Deploying the application.
- 2.8.1 Building a development environment
- 2.8.2 Importing the application in Studio
- 2.8.3 Configuring a Test Server in Studio
- 2.8.4 Testing the EJB
- 2.9 Development of the Web service
- 2.10 Summary
- Chapter 3. WebSphere InterChange Server as a Web services router
- 3.1 The WebSphere InterChange Server and its main components
- 3.1.1 The InterChange Server
- 3.1.2 Collaborations
- 3.1.3 Business objects
- 3.1.4 Adapters
- 3.2 Why Web services for a process broker
- 3.2.1 Introducing the Web services adapter
- 3.3 Building a runtime and development environment
- 3.3.1 Installing WebSphere InterChange Server
- 3.3.2 Starting and using the InterChange Server
- 3.3.3 Using WebSphere Studio
- 3.3.4 Installing WebSphere BI Adapters V2.3.1
- 3.3.5 Installing and configuring the Web-based System Monitor
- 3.4 Overview of implemented scenarios
- 3.5 Building the integration solution
- 3.5.1 Implementation steps
- 3.5.2 Preparing Studio
- 3.5.3 Develop business object ACC_CUSTOMERACCESS
- 3.5.4 Definition of maps
- 3.5.5 Configuring the JDBC connector
- 3.5.6 Configuring the Port connector
- 3.5.7 The collaboration template CustomerSync
- 3.5.8 The collaboration object ACC_CustomerSync
- 3.5.9 Deployment of the project
- 3.5.10 Testing the integration solution
- 3.6 Scenario 1: Invoking a collaboration as a Web service
- 3.6.1 Implementation steps
- 3.6.2 Create the top-level business object
- 3.6.3 Develop maps between ASBO and GBO
- 3.6.4 Updating the Port connector
- 3.6.5 Intermediate deployment and testing
- 3.6.6 Configure the Web services connector
- 3.6.7 Configure and create external resources for the connector
- 3.6.8 Deployment and testing
- 3.6.9 Generation of WSDL for the collaboration
- 3.6.10 Development of Web services clients
- 3.7 Scenario 2: Invoking a Web service from a collaboration.
- 3.7.1 Implementation steps
- 3.7.2 Using the Web services ODA
- 3.7.3 Create top-level business object
- 3.7.4 Transformation maps
- 3.7.5 Create a second instance of the Web Services adapter
- 3.7.6 Update the collaboration
- 3.7.7 Deploy and test
- 3.8 Summary
- Chapter 4. WebSphere BI Message Broker as a Web services router
- 4.1 Introducing the WebSphere BI Message Broker product
- 4.1.1 WebSphere Business Integration reference architecture
- 4.1.2 Components of WebSphere BI Message Broker
- 4.1.3 HTTP transport nodes
- 4.2 Why Web services for a message broker
- 4.3 Building a development and runtime environment
- 4.3.1 Installation of the Message Broker product
- 4.3.2 Creating the broker and configuration manager
- 4.3.3 Connecting the Toolkit to the broker domain
- 4.4 Overview of implemented scenarios
- 4.5 Scenario 1: Routing a Web service through a message flow
- 4.5.1 Implementation steps
- 4.5.2 Define the message flow
- 4.5.3 Create the broker test environment
- 4.5.4 Run the Web client
- 4.6 Scenario 2: Invoke a Web service in a message flow
- 4.6.1 Implementation steps
- 4.6.2 MQ message triggers a Web service invocation
- 4.6.3 Populating Web service invocation with MQ message elements
- 4.6.4 Populating an MQ message with the results of a Web service
- 4.7 Scenario 3: Publishing a message flow as a Web service
- 4.7.1 Implementation steps
- 4.7.2 Generate WSDL for a message definition
- 4.7.3 Update message flow
- 4.7.4 Create a bar file and deploy to broker
- 4.7.5 Build a Web service client and run it
- 4.8 Summary
- Chapter 5. WebSphere Enterprise as a Web services router
- 5.1 Introducing WebSphere Enterprise
- 5.2 Business process engine
- 5.3 Using WebSphere Enterprise for Business Integration
- 5.3.1 Request processing
- 5.3.2 Event notification.
- 5.3.3 Business integration based on Web services
- 5.4 Building a runtime and development environment
- 5.4.1 Installing and configuring WebSphere Application Server
- 5.5 Overview of implemented scenarios
- 5.6 Scenario 1: Router-initiated integration
- 5.6.1 Implementation steps
- 5.6.2 Connector configuration
- 5.6.3 Create and deploy a user project
- 5.6.4 Generate deploy code
- 5.6.5 Create a test server in Studio
- 5.6.6 Test end-to-end solution
- 5.7 Scenario 2: Application-initiated integration
- 5.7.1 Implementation steps
- 5.7.2 Database configuration
- 5.7.3 Create service project
- 5.7.4 Create the Enterprise JavaBean
- 5.7.5 Create the message-driven bean
- 5.7.6 Updating the test server configuration
- 5.7.7 Deployment to WebSphere Application Server and testing
- 5.8 The Adapter Monitor perspective
- 5.9 WebSphere Application Server deployment and runtime operations
- 5.10 Summary
- Chapter 6. Process Choreographer as a Web services router
- 6.1 Introducing Process Choreographer
- 6.2 Overview of implemented scenarios
- 6.3 Creating a development and runtime environment
- 6.3.1 Business process container setup
- 6.3.2 Business process container validation
- 6.4 Scenario 1: Invoking a collaboration
- 6.4.1 Overview and implementation steps
- 6.4.2 Importing and tailoring the WSDL
- 6.4.3 Creating the SOAP process
- 6.4.4 Creating the JMS process
- 6.4.5 Testing in the Unit Test Environment
- 6.4.6 Testing in WebSphere Application Server Enterprise
- 6.5 Scenario 2: Invoking a WebSphere Business Integration Adapter
- 6.6 Scenario 3: Invoking a message flow
- 6.7 Summary
- Appendix A. Hardware and software configuration
- Machine configuration
- Installation order
- Appendix B. Additional material
- Locating the Web material
- Using the Web material.
- System requirements for downloading the Web material
- How to use the Web material
- Abbreviations and acronyms
- Related publications
- IBM Redbooks
- Online resources
- How to get IBM Redbooks
- Help from IBM
- Index
- Back cover.
