Patterns broker interactions for Intra- and Inter-enterprise
The Patterns for e-business are a group of proven, reusable assets that can be used to increase the speed of developing and deploying Web applications. This IBM Redbooks publication concentrates on distributed application integration using the Process-focused Application Integration::Broker applicat...
| 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: | IBM redbooks.
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009628098806719 |
Tabla de Contenidos:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Part 1 Patterns for e-business
- Chapter 1. Introduction to Patterns for e-business
- 1.1 The Patterns for e-business layered asset model
- 1.2 How to use the Patterns for e-business
- 1.2.1 Select a Business, Integration, or Composite pattern, or a Custom design
- 1.2.2 Selecting Application patterns
- 1.2.3 Review Runtime patterns
- 1.2.4 Review Product mappings
- 1.2.5 Review guidelines and related links
- 1.3 Summary
- Chapter 2. Fundamental concepts in Process Integration
- 2.1 The need for a unifying technique
- 2.1.1 Similarities between intra- and inter-enterprise integration
- 2.1.2 Summary
- 2.2 Process Integration concepts and notations
- 2.2.1 Collaboration and Interaction
- 2.2.2 Connectors and Adapters
- 2.2.3 Classification of interaction between sub-systems
- 2.3 QoS capabilities framework
- 2.3.1 Operability
- 2.3.2 Availability
- 2.3.3 Federation
- 2.3.4 Performance
- 2.3.5 Security
- 2.3.6 Standards compliance
- 2.3.7 Transactionality
- 2.4 Application patterns for Application Integration
- 2.5 Application patterns for Extended Enterprise
- 2.6 Summary
- Chapter 3. Application Integration pattern
- 3.1 Using the pattern
- 3.2 Defining the Application Integration patterns
- 3.2.1 Business and IT drivers
- 3.2.2 Context
- 3.2.3 Solution
- 3.2.4 Putting the pattern to use
- 3.2.5 Application Integration considerations
- 3.2.6 What's next
- 3.3 Application patterns
- 3.4 Process-focused application patterns
- 3.4.1 Direct Connection application pattern
- 3.4.2 Direct Connection: Message Connection variation
- 3.4.3 Direct Connection: Call Connection variation
- 3.4.4 Broker application pattern
- 3.4.5 Broker: Router variation.
- 3.4.6 Serial Process application pattern
- 3.4.7 Serial Process: Workflow variation
- 3.4.8 Parallel Process application pattern
- 3.4.9 Parallel Process: Workflow variation
- 3.5 Data-focused application patterns
- 3.6 Previous Application Integration patterns
- Chapter 4. Extended Enterprise pattern
- 4.1 Using the pattern
- 4.2 General guidelines
- 4.2.1 Business and IT drivers
- 4.2.2 Context
- 4.2.3 Solution
- 4.2.4 Putting the pattern to use
- 4.2.5 What's next
- 4.3 Application patterns
- 4.3.1 Exposed Direct Connection application pattern
- 4.3.2 Exposed Broker application pattern
- 4.3.3 Exposed Serial Process application pattern
- Chapter 5. Runtime patterns and product mappings
- 5.1 Node types
- 5.2 Application Integration patterns
- 5.2.1 Runtime pattern and product mapping for the Broker
- 5.2.2 Runtime patterns and product mappings for Router
- 5.3 Extended Enterprise
- 5.3.1 Runtime patterns and product mapping for Exposed Broker
- 5.3.2 Runtime pattern and product mappings for the Router variation
- 5.4 Products used in these mappings
- 5.4.1 IBM WebSphere Application Server
- 5.4.2 IBM WebSphere MQ
- 5.4.3 WebSphere Business Integration Message Broker
- Part 2 Scenarios and guidelines
- Chapter 6. Business scenarios used in this book
- 6.1 Customer overview
- 6.1.1 Business profile
- 6.1.2 Business goals
- 6.1.3 Existing environment
- 6.1.4 Non-functional requirements
- 6.2 Intra-enterprise scenarios
- 6.2.1 Stage I: Internal delivery date on demand
- 6.2.2 Stage II: Internal Get earliest delivery date on demand
- 6.3 Inter-enterprise scenarios
- 6.3.1 Stage III: External get delivery date on demand
- 6.3.2 Stage IV: External get earliest delivery date on demand
- Chapter 7. Technology options
- 7.1 Selecting an integration technology
- 7.2 XML
- 7.2.1 Defining XML documents.
- 7.2.2 XSLT
- 7.2.3 XML security
- 7.2.4 Advantages of XML
- 7.2.5 Disadvantages of XML
- 7.3 Web services
- 7.3.1 Static and dynamic Web services
- 7.3.2 Web Services Invocation Framework
- 7.3.3 Web services and the service-oriented architecture
- 7.3.4 Web services security
- 7.3.5 Advantages of Web services
- 7.3.6 Disadvantages of Web services
- 7.3.7 Comparing Web services with CORBA and RMI
- 7.4 J2EE Connector Architecture
- 7.4.1 CICS resource adapter
- 7.4.2 IMS resource adapter
- 7.4.3 Advantages of J2EE Connectors
- 7.4.4 Disadvantages of J2EE Connectors
- 7.5 Java Message Service (JMS)
- 7.5.1 What messaging is
- 7.5.2 JMS and IBM WebSphere MQ
- 7.5.3 Advantages of JMS
- 7.5.4 Disadvantages of JMS
- 7.6 Message Oriented Middleware
- 7.7 Flow languages
- 7.7.1 Flow Definition Language
- 7.7.2 Flow Definition Markup Language
- 7.7.3 Business Process Execution Language for Web Services
- 7.8 Other integration technologies
- 7.8.1 RMI/IIOP
- 7.8.2 CORBA
- 7.9 Where to find more information
- Part 3 Scenarios
- Chapter 8. Router solutions using Web Services Gateway
- 8.1 Business scenario
- 8.2 IBM Web Services Gateway
- 8.3 Applying patterns
- 8.3.1 Application patterns
- 8.3.2 Runtime Patterns and Product mappings
- 8.4 Design guidelines
- 8.5 System design overview
- 8.5.1 Stage 1: Basic integration
- 8.5.2 Stage 2: Enhanced integration
- 8.5.3 Stage 3: Extended enterprise
- 8.6 Development guidelines
- 8.6.1 Implementation process
- 8.6.2 Web service enable the target application
- 8.6.3 Register the services in the UDDI Registry
- 8.6.4 Create the filter
- 8.6.5 Define the services and filter to Web Services Gateway
- 8.6.6 Export the Web service definition
- 8.6.7 Web service-enable the source application
- 8.6.8 Best practices
- 8.7 Quality of service capabilities.
- 8.7.1 Performance and availability
- 8.7.2 Security
- 8.7.3 Standards compliance
- 8.7.4 Autonomic
- 8.8 References
- Chapter 9. Broker solutions using WebSphere Business Integration Message Broker
- 9.1 Business scenario
- 9.2 IBM WebSphere Business Integration Message Broker
- 9.2.1 Architectural overview
- 9.3 Applying patterns
- 9.3.1 Application patterns
- 9.3.2 Product mappings
- 9.4 Design guidelines
- 9.4.1 Selecting a transport
- 9.4.2 Using real-time applications
- 9.4.3 Using Web services support
- 9.4.4 Using aggregation
- 9.5 System design overview
- 9.5.1 Stage 1: Internal "Get earliest delivery date" solution
- 9.5.2 Stage 2: Internal sales forecast publish/subscribe
- 9.5.3 Stage 3: External "Get earliest delivery date" solution
- 9.6 Developing message flows with Web services
- 9.6.1 Development environment
- 9.6.2 Development steps
- 9.6.3 Step 1: Access the Web service directly
- 9.6.4 Step 2: Access the Web service using through message flow
- 9.6.5 Step 3: Add the broker function
- 9.7 Developing real-time message flows
- 9.7.1 Prepare the subscriber applications
- 9.7.2 Prepare the publisher application
- 9.7.3 Build and deploy the message flow
- 9.8 Quality of service capabilities
- 9.8.1 Availability
- 9.8.2 Performance
- 9.8.3 Security
- 9.8.4 Transactionality
- 9.9 For more information
- Part 4 Appendixes
- Appendix A. Additional material
- Locating the Web material
- Using the Web material
- How to use the Web material
- Related publications
- IBM Redbooks
- Other publications
- Online resources
- How to get IBM Redbooks
- Help from IBM
- Index
- Back cover.
