To plan for your integration to WebSphere InterChange Server, follow the steps outlined in Planning for back-end integration. Table 25 summarizes the integration steps to integrate WebSphere Partner Gateway with InterChange Server (ICS).
Integration step | For more information |
---|---|
1. Confirm that you have a supported version of WebSphere InterChange Server installed and available to WebSphere Partner Gateway. |
Introduction to InterChange Server integration: InterChange Server versions that WebSphere Partner Gateway supports |
2. Determine the business protocol of the WebSphere Partner Gateway document. |
Planning for back-end integration: Which business protocol are you using? |
3. Determine the packaging type for the document: None or Backend Integration. |
Planning for back-end integration: Which packaging will you use? |
4. Determine the transport protocol to use between WebSphere Partner Gateway and WebSphere InterChange Server. |
Introduction to InterChange Server integration: Message transports that InterChange Server supports |
5. Configure WebSphere Partner Gateway. |
Introduction to InterChange Server integration: Configuring WebSphere Partner Gateway for InterChange Server |
6. Configure WebSphere InterChange Server components for use over the chosen transport protocol. |
Introduction to InterChange Server integration: Configuring InterChange Server |
Version 6.0 of WebSphere Partner Gateway supports integration with the following versions of InterChange Server:
InterChange Server is available on several platforms, including Windows 2000 and several UNIX-based platforms. For more information, consult your installation guide for InterChange Server in the WebSphere InterChange Server documentation set.
When WebSphere Partner Gateway sends your message to InterChange Server over a particular message transport protocol, it sends that message to the appropriate adapter, which understands the particular transport protocol and routes the message to InterChange Server. Similarly when InterChange Server sends a message to WebSphere Partner Gateway, it sends the message to the appropriate adapter for routing to WebSphere Partner Gateway over the appropriate transport protocol.
The adapter works with a data handler, which handles the actual conversion from serialized data to business object, or from business object to serialized data. The data handler appropriate for the payload type is used to perform these conversions.
The following two message-transport protocols are supported by InterChange Server:
Use the transport protocol that best suits the needs of your business. Consider the following:
Which adapters are required to send and receive documents between WebSphere Partner Gateway and InterChange Server over HTTP depends on the following:
Table 26 summarizes where to find information on how to configure adapters for use with InterChange Server.
Condition | For more information |
---|---|
If you are transferring non-SOAP documents with InterChange Server | Using HTTP transport protocol with ICS |
If you are sending SOAP documents | Sending SOAP documents over HTTP/S |
The components required to send and receive documents between WebSphere Partner Gateway and InterChange Server over JMS are summarized in Table 52. Basically, support for JMS involves the use of the WebSphere Business Integration Adapter for JMS. The Adapter for JMS invokes collaborations within InterChange Server asynchronously.
As you decide which message transport to use with InterChange Server, consider the following benefits of each transport:
Guaranteed event delivery ensures that events are never lost or sent twice.
WebSphere Partner Gateway provides samples to assist you in the integration process with InterChange Server. These samples reside in the following subdirectory of the WebSphere Partner Gateway product directory:
Integration/WBI/WICS/samples
Table 27 lists the subdirectories of the samples directory for the different transport protocols that InterChange Server supports.