3 options
B2B solutions using WebSphere partner gateway V6.0 / Lee Gavin et al.
- Format:
- Book
- Author/Creator:
- Gavin, Lee.
- Series:
- IBM redbooks.
- Redbooks
- Language:
- English
- Subjects (All):
- Electronic commerce.
- WebSphere.
- Physical Description:
- 1 online resource (830 p.)
- Place of Publication:
- White Plains, N.Y. : IBM, c2005.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Part 1 Overview of the technology and products
- Chapter 1. Business-to-business concepts
- 1.1 Impact of the Internet on the world of business applications
- 1.2 E-commerce
- 1.2.1 Business-to-consumer
- 1.2.2 Business-to-business
- 1.2.3 Evolution of the B2B data structures
- 1.2.4 Evolution of B2B data communications
- 1.3 Enterprise application integration and B2B
- 1.4 B2B integration
- 1.4.1 Types of B2B integration
- 1.4.2 Summary
- Chapter 2. Business-to-business technologies and standards
- 2.1 Requirements for a B2B solution
- 2.2 Some terminology
- 2.2.1 Messaging and queuing
- 2.2.2 Electronic data interchange
- 2.2.3 Transport protocols
- 2.2.4 Security
- 2.2.5 Java
- 2.2.6 Extensible Markup Language
- 2.2.7 Web services
- Chapter 3. Introduction to WebSphere Partner Gateway
- 3.1 Editions of WebSphere Partner Gateway
- 3.2 Architecture of WebSphere Partner Gateway
- 3.2.1 Runtime components
- 3.2.2 Configuration components
- 3.2.3 Profile management
- 3.3 B2B features and standards
- 3.3.1 Transport options
- 3.3.2 Messaging protocol options
- 3.3.3 Business document formats
- 3.3.4 Security options in WebSphere Partner Gateway
- 3.4 Extensible architecture
- 3.4.1 Encryption, validation and transformation
- 3.4.2 Custom transports, packages and protocols
- 3.5 Enterprise Integration
- Part 2 Building a B2B exchange
- Chapter 4. Implementation scenarios
- 4.1 Implementing WebSphere Partner Gateway Enterprise for Windows
- 4.2 Implementing WebSphere Partner Gateway Advanced for AIX
- 4.3 Implementing a basic exchange
- 4.4 Securing the exchange between Company E and Company A
- 4.5 Implementing WebSphere Partner Gateway Express for Windows.
- 4.6 Using FTP with WebSphere Partner Gateway
- 4.7 Using FTP Scripting to enable Value Added Network (VAN) connectivity
- 4.8 Managing the B2B infrastructure
- 4.9 EDI translation
- Chapter 5. WebSphere Partner Gateway Enterprise on Windows
- 5.1 Implementation overview
- 5.2 Verify software levels on the hub and data servers
- 5.2.1 Verifying WebSphere MQ 6.0
- 5.2.2 Verifying DB2
- 5.3 Installing the software for the data machine
- 5.3.1 Adding user IDs and a group
- 5.3.2 Configuring WebSphere MQ 6.0
- 5.3.3 Installing the database schema
- 5.3.4 Local validation
- 5.4 Install WebSphere Partner Gateway
- 5.4.1 Adding a user and group
- 5.4.2 Installing the product code
- 5.4.3 Local validation
- 5.5 Initial configuration of the WebSphere Partner Gateway server
- Chapter 6. WebSphere Partner Gateway Advanced for AIX
- 6.1 Implementation Overview
- 6.2 Verifying software levels on the AIX machine
- 6.2.1 Verifying DB2
- 6.2.2 Verifying WebSphere MQ
- 6.3 Software Installation
- 6.3.1 Adding the user accounts
- 6.3.2 Configuring WebSphere MQ
- 6.3.3 Installing the database schema
- 6.3.4 Installing the Product Code
- 6.3.5 Local Validation
- 6.3.6 Starting the help system
- 6.4 Initial configuration of the WebSphere Partner Gateway server
- Chapter 7. Creating a basic B2B exchange
- 7.1 Scenario overview
- 7.2 Role-based configuration
- 7.2.1 Outbound flow
- 7.2.2 Inbound Flow
- 7.3 Configuration tasks for hubadmin of Company E
- 7.3.1 Creating targets
- 7.3.2 Creating interactions
- 7.3.3 Creating a Community Manager
- 7.3.4 Creating a Community Participant
- 7.4 Configuration tasks for Company E administrator
- 7.4.1 Initial logon by the Community Manager
- 7.4.2 Creating a gateway
- 7.4.3 Providing B2B capabilities
- 7.5 Configuration tasks for partner Company A
- 7.6 Connecting Company E to Company A.
- 7.7 Configuration tasks for the Company A hubadmin
- 7.8 Validating communication
- 7.9 Revisiting role-based configuration
- Chapter 8. Securing the B2B exchange
- 8.1 What is needed to perform encryption an decryption
- 8.2 Enabling encryption
- 8.2.1 Company E generates a public/private key pair
- 8.2.2 Company E uploads private key to its own server
- 8.2.3 Company E uploads public certificate to partner's server
- 8.2.4 What happens next?
- 8.2.5 Company A generates a private/public key pair
- 8.2.6 Company A uploads a private key to its own server
- 8.2.7 Company A uploads their public key to their partner's server
- 8.2.8 Updating the participant connections
- 8.2.9 Validating that encryption is enabled
- 8.3 What is needed to digitally sign and verify the signature?
- 8.4 Enabling digital signatures
- 8.4.1 Changes to be performed on the server of Company A
- 8.4.2 Changes to perform on the server of Company E
- 8.4.3 Validating that digital signatures are enabled
- Chapter 9. WebSphere Partner Gateway Express on Windows
- 9.1 Overview of the Express edition
- 9.2 Software installation and configuration
- 9.3 Initial configuration of the Express server
- Chapter 10. Extending the B2B exchange
- 10.1 Scenario overview
- 10.2 Implementation steps
- 10.3 Configuration of Company X
- 10.3.1 Customizing My Profile
- 10.3.2 Customizing the profile of Participant Company E
- 10.4 Additional configuration of Company E
- 10.4.1 Creating a new Community Participant
- 10.4.2 Creating a new document flow definition
- 10.4.3 Creating a new XML format
- 10.4.4 Create an interaction
- 10.4.5 Updating Company X's profile on Company E's server
- 10.4.6 Updating Company E's profile on the Company E server
- 10.5 Validating Communication
- 10.5.1 Sending XML documents from Company E to Company X.
- 10.5.2 Sending XML documents from Company X to Company E
- Chapter 11. Managing the B2B exchange
- 11.1 Tools available to manage the exchange
- 11.2 System log files
- 11.3 Event Viewer
- 11.4 Document Viewer
- 11.5 AS1/AS2 Viewer
- 11.6 Gateway queue
- 11.7 Using the tools for problem determination
- 11.7.1 MDN HTTP URL not defined
- 11.7.2 Problems with encryption
- 11.7.3 Problems with digital signatures
- Part 3 FTP support
- Chapter 12. Integrating FTP servers
- 12.1 Overview of FTP and FTP Scripting scenarios
- 12.1.1 FTP method one: FTP servers
- 12.1.2 FTP method two: FTP Scripting
- 12.2 Configuration of Company A for FTP outbound
- 12.2.1 Outbound implementation steps
- 12.2.2 Creating the directory structure
- 12.2.3 Updating the hubadmin profile
- 12.2.4 Updating the profile for Company F
- 12.2.5 Updating the profile for Company A
- 12.2.6 Creating a participant connection
- 12.2.7 Validating outbound communication
- 12.3 Configuration of Company A for FTP Inbound
- 12.3.1 Integrating with the AIX FTP server
- 12.3.2 Updating the configuration of WebSphere Partner Gateway
- 12.3.3 Validating Inbound communication
- 12.4 Implementing FTPS
- 12.4.1 FTPS outbound
- 12.4.2 FTPS client authentication
- 12.4.3 FTPS inbound
- 12.5 Configuration of FTP Scripting outbound
- 12.5.1 Outbound FTP Scripting overview
- 12.5.2 Updating the B2B Capabilities of Company F
- 12.5.3 Creating the new interaction
- 12.5.4 Create an FTP Scripting Gateway for Company F
- 12.5.5 Update the participant connection
- 12.5.6 Validating the connection
- 12.6 Configuration of FTP Scripting inbound
- 12.6.1 FTP Scripting inbound overview
- 12.6.2 Creating the FTP Scripting Target
- 12.6.3 Updating the participant connection
- 12.6.4 Validating inbound communication with FTP Scripting target.
- 12.7 FTPS for FTP Scripting Gateways and Targets
- 12.7.1 FTPS for the FTP Scripting Gateway
- 12.7.2 FTPS for the FTP Scripting Target
- 12.8 Comparing FTP and FTP Scripting
- Chapter 13. Enabling VAN connectivity using FTP Scripting
- 13.1 Scenario overview
- 13.2 Configuration of Company E for outbound
- 13.2.1 Implementation steps
- 13.2.2 Updating the profile of hubadmin
- 13.2.3 Updating the profile of Company V
- 13.2.4 Updating the profile of Company E
- 13.2.5 Creating a participant connection
- 13.2.6 Validating communication
- 13.3 Configuration of Company E for inbound
- 13.3.1 Creating a FTP Scripting Target for Company E
- 13.3.2 Updating the WebSphere Partner Gateway configuration
- 13.3.3 Validating communication
- 13.4 Securing VAN connectivity
- 13.4.1 Uploading certificates to Company E's WebSphere Partner Gateway
- 13.4.2 Updating the FTP Scripting gateway to use secure mode
- 13.4.3 Validating outbound communication
- 13.4.4 Using secure mode for inbound communication
- 13.4.5 Validating inbound communication
- 13.5 Summary
- Part 4 Native mapping support for non-EDI standards
- Chapter 14. Native mapping support in WebSphere Partner Gateway
- 14.1 Install the Data Interchange Services client
- 14.2 The system view of Data Interchange Services
- 14.3 Development environment
- 14.3.1 Configure a development environment using DB2
- 14.4 Component view of the development environment
- 14.5 Connect the Data Interchange Services client to a development database
- 14.6 Functional areas
- 14.6.1 XML functional area
- 14.6.2 EDI functional area
- 14.6.3 Record Oriented Data (ROD) functional area
- 14.6.4 Mapping functional area
- 14.7 Runtime environment
- Chapter 15. Mapping
- 15.1 Scenario overview
- 15.2 Create a ROD document definition
- 15.2.1 Create a new ROD dictionary.
- 15.2.2 Create a new Record ID.
- Notes:
- "November 2005."
- Includes bibliographical references and index.
- OCLC:
- 614891929
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.