Search results

This Redpaper provides key tuning recommendations for enterprise application integration (EAI) solutions based on WebSphere InterChange Server. This paper is not meant to be a comprehensive treatment of performance tuning, but instead a summary of experiences obtained through the use of the product. There are few easy answers to a performance problem, or what is perceived as a performance problem, in a complex system made up of multiple hardware and software components. For those who are either considering or are in the very early stages of implementing an WebSphere InterChange Server solution, this document should provide a useful performance information reference, serving as a supplemental starting point for setup, tuning, and configuration information. It provides a useful introduction to many of the issues affecting InterChange Server performance and can act as a guide for making rational first choices in terms of configuration and performance settings.

This IBM Redpaper is the first in a series of Redpapers dealing with the development and deployment of IBM WebSphere Business Integration Adapters. In this first Redpaper, "An Introduction to the Basics," we describe the basics of the WebSphere Business Integration Adapters, the components that make up the adapters, and how to get started with developing and deploying a customer adapter.

This Redpaper provides key tuning recommendations for enterprise application integration (EAI) solutions based on WebSphere InterChange Server. This paper is not meant to be a comprehensive treatment of performance tuning, but instead a summary of experiences obtained through the use of the product. There are few easy answers to a performance problem, or what is perceived as a performance problem, in a complex system made up of multiple hardware and software components. For those who are either considering or are in the very early stages of implementing an WebSphere InterChange Server solution, this document should provide a useful performance information reference, serving as a supplemental starting point for setup, tuning, and configuration information. It provides a useful introduction to many of the issues affecting InterChange Server performance and can act as a guide for making rational first choices in terms of configuration and performance settings.

This IBM Redpaper describes the implementation of AS/2 client products, iSoft's P2PAgent and Trading Partner Interchange, in an environment with multiple trading partners. First, we discuss the implementation of TPI between two trading partners and then that configuration is extended with another partner that is using iSoft's P2PAgent. The next step in the implementation of TPI is the interaction with back-office applications. We describe how to work with the EDI translation product WebSphere Data Interchange. This Redpaper explains both the inbound and outbound flow for a purchase order and a purchase order acknowledgement. Finally, we look at the use of the Interchange Server as the integration platform and how the ICS interacts with WebSphere Data Interchange and TPI. The last chapter of this Redpaper discusses the interoperability of AS/2 providers. The first part of that chapter discusses how trading partners using different AS/2 providers can interact with each other. A network of three partners is considered, where two partners are using TPI and another partner is using iSoft's P2PAgent. The second part of this last chapter discusses interoperability of AS/2 providers within a given enterprise. We first implement an integration solution for UCCnet that interacts with the TPI. In two steps, we demonstrate that this integration solution can also work with a different AS/2 provider. For more up-to-date information about WebSphere B2B, please refer to the following books: B2B solutions using WebSphere Partn

This IBM Redpaper describes the implementation of an AS/2 client product, iSoft's P2PAgent, in an environment with multiple trading partners. First, we discuss the implementation of the P2PAgent program between two trading partners; that configuration is then extended to multiple partners. The iSoft configuration is discussed for queue-based and file-based input and output. The next step in the implementation of iSoft's P2PAgent is the interaction with back-office applications. We describe how to work with the EDI translation product WebSphere Data Interchange. The Redpaper explains both the inbound and outbound flow for a purchase order and a purchase order acknowledgement. Finally, we look at the use of CrossWorlds as the integration platform and how CrossWorlds interacts with WebSphere Data Interchange and iSoft's P2PAgent. The last chapter of the Redpaper discusses the implementation of a fail-over solution for those situations where Internet connectivity between trading partners cannot be established. The fail-over solution uses IBM Expedite and the IBM VAN (Value-added Network). We describe in detail how to configure iSoft's P2PAgent and Expedite so that we have a fail-safe solution. For more up-to-date information about WebSphere B2B, please refer to the following books: B2B solutions using WebSphere Partner Gateway V6.0, http://www.redbooks.ibm.com/abstracts/sg247109.html?Open and Secure Production Deployment of WebSphere Business Integration Connect, http://www.redbooks.ibm.com/abstracts/sg246457.ht