2 options
Integrating WebSphere Commerce with SAP R/3 using WebSphere InterChange Server / [Tamas Vilaghy ... et al.].
- Format:
- Book
- Series:
- IBM redbooks.
- IBM redbooks
- Language:
- English
- Subjects (All):
- Electronic commerce--Computer programs.
- Electronic commerce.
- WebSphere.
- SAP R/3.
- Physical Description:
- xii, 216 p. : ill.
- Edition:
- 1st ed.
- Place of Publication:
- Poughkeepsie, NY : IBM, International Technical Support Organization, c2003.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Chapter 1. Introduction to business integration
- 1.1 Why business integration?
- 1.2 Types of integration
- 1.2.1 Data-level integration
- 1.2.2 Application-interface-level integration
- 1.2.3 User interface-level integration
- 1.3 WebSphere Commerce integration options
- Chapter 2. Integration scenarios
- 2.1 WebSphere Commerce integration
- 2.2 JCA-based integration
- 2.2.1 Advantages and disadvantages of JCA
- 2.2.2 WebSphere Commerce and WebSphere Adapters
- 2.3 WebSphere MQ-based integration
- 2.3.1 Point-to-point MQ integration
- 2.3.2 WebSphere MQ Integrator-based integration
- 2.3.3 WebSphere InterChange Server-based integration
- 2.4 Web services-based integration
- 2.4.1 WebSphere Commerce as a service provider
- 2.4.2 WebSphere Commerce as a service requestor
- 2.5 Other integration solutions
- 2.5.1 HTTP-based integration
- 2.5.2 E-mail and file based integration
- 2.5.3 SAP Business Connector-based integration
- 2.6 WebSphere Commerce integration attributes
- 2.6.1 Synchronous and asynchronous communications
- 2.6.2 Direct and indirect connections
- 2.6.3 Point-to-point and multi-point connections
- 2.6.4 Summary of commerce integration attributes
- 2.7 Functions and benefits of the integration family products
- Chapter 3. Integration architectures
- 3.1 WebSphere Commerce architecture
- 3.1.1 Overview of the WebSphere Commerce Server
- 3.1.2 WebSphere Commerce Server components
- 3.1.3 Single-tier architecture
- 3.1.4 Two-tier architecture
- 3.1.5 Three-tier architecture
- 3.1.6 Extended enterprise architecture
- 3.1.7 Run-time architecture
- 3.1.8 Flow of an HTTP request
- 3.1.9 WebSphere Commerce messaging subsystem
- 3.2 SAP architecture.
- 3.2.1 Key architectural components of SAP
- 3.2.2 Remote Function Calls
- 3.2.3 Application Link Enabling
- 3.2.4 Intermediate Document
- 3.2.5 Business Application Program Interfaces
- 3.2.6 SAP server
- 3.3 WebSphere InterChange Server architecture
- 3.3.1 WebSphere InterChange Server components
- 3.3.2 Sample data flows
- 3.3.3 Collaborations, business objects, and connectivity
- 3.4 WebSphere MQ architecture
- 3.5 WebSphere MQ Integrator architecture
- 3.6 Overview of the integration process
- 3.6.1 Inbound message flow
- 3.6.2 Outbound message flow
- 3.7 Sample architectures
- Chapter 4. Message flow
- 4.1 WebSphere Commerce messaging system
- 4.1.1 Outbound messaging system
- 4.1.2 Inbound messaging system
- 4.1.3 Integration messages
- 4.2 Message flow in different WebSphere Commerce integration solutions
- 4.2.1 Connection with WebSphere Commerce using JCA
- 4.2.2 Connection with WebSphere Commerce using the WebSphere InterChange Server
- 4.2.3 Integration with WebSphere Commerce and SAP R/3 using WebSphere MQ and MQSeries Link for SAP R/3
- 4.2.4 Integration with WebSphere Commerce and SAP R/3 using WebSphere MQ Integrator and XML Bridge for SAP
- 4.2.5 SAP Business Connector integration with WebSphere Commerce
- 4.3 Message transformation possibilities for different integrations
- 4.3.1 Message transformations using JCA
- 4.3.2 Message transformations using WebSphere InterChange Server
- 4.3.3 Message transformations from MQSeries Link for R/3, WebSphere MQ Integrator, and XML Bridge for SAP
- 4.3.4 Message transformations from SAP Business Connector
- 4.3.5 Message transformations with Web services
- 4.4 Message types
- 4.4.1 XML
- 4.4.2 IDoc
- 4.4.3 SOAP message
- Chapter 5. Installation and configuration considerations
- 5.1 Reference application
- 5.2 Sample topology.
- 5.3 Installing and configuring WebSphere Commerce
- 5.3.1 Installing WebSphere Commerce
- 5.3.2 Configuring WebSphere Commerce messaging
- 5.3.3 Configuring the WebSphere Business Integration adapter in WebSphere Commerce
- 5.4 Installing and configuring WebSphere InterChange Server
- 5.4.1 Installing WebSphere InterChange Server
- 5.4.2 Configuring the WebSphere InterChange Server queue manager
- 5.4.3 Configuring WebSphere InterChange Server
- 5.4.4 Installing and configuring SAP
- Chapter 6. Developing a new message
- 6.1 Creating and customizing commands: An overview
- 6.2 Creating the new outbound message
- 6.2.1 Customizing the controller or task command
- 6.2.2 Creating the new view and view command
- 6.2.3 Setting up WebSphere Commerce messaging
- 6.2.4 Deploying new resources
- 6.3 Actions to perform in WebSphere InterChange Server
- 6.3.1 Configuring the WebSphere MQ adapter
- 6.3.2 Business objects
- 6.3.3 Mapping in WebSphere InterChange Server
- Chapter 7. Problem determination
- 7.1 WebSphere InterChange Server
- 7.2 WebSphere Commerce
- 7.3 WebSphere Commerce Server and SAP Integration
- 7.3.1 WebSphere Commerce and SAP R/3 integration test
- 7.3.2 Verification procedure in SAP
- Appendix A. Sample code
- Related publications
- IBM Redbooks
- Other resources
- Referenced Web sites
- How to get IBM Redbooks
- Help from IBM
- Index
- Back cover.
- Notes:
- "December 2003."
- "This edition applies to Version 5.4 of WebSphere Commerce, Version 4.0.1 of WebSphere InterChange Server, and Version 4.6C of SAP R/3"--T.p. verso.
- "SG24-6902-00."
- Includes bibliographical references (p. 207-210) and index.
- OCLC:
- 137342230
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.