To plan for your integration to WebSphere InterChange Server, follow the
steps outlined in Planning the back-end integration. Table 26 summarizes the integration steps to
integrate WebSphere Business Integration Connect with InterChange Server
(ICS).
Table 26. Planning for integration with WebSphere InterChange Server
Integration step | For more information |
---|---|
1. Confirm that you have a supported version of WebSphere InterChange Server installed and available to WebSphere Business Integration Connect. |
"Introduction to InterChange Server Integration": InterChange Server versions that Business Integration Connect supports
|
2. Determine the business protocol of the WebSphere Business Integration Connect document. |
"Planning for back-end integration": What 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 Business Integration Connect and WebSphere InterChange Server. |
"Introduction to InterChange Server Integration": Message transports that InterChange Server supports
|
5. Configure WebSphere Business Integration Connect. |
"Introduction to InterChange Server Integration": Configuring Business Integration Connect 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 4.2.2 of Business Integration Connect can support 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 Business Integration Connect sends your message to InterChange Server over a particular message transport protocol, it sends that message to the appropriate InterChange Server-compatible component, which understands the particular transport protocol and routes the message to InterChange Server. Similarly when InterChange Server sends a message to Business Integration Connect, it sends the message to the appropriate ICS-compatible component for routing to Business Integration Connect over the appropriate transport protocol.
Table 27 summarizes the ICS-compatible components used in Business
Integration Connect integration.
Table 27. InterChange Server-compatible components
Business Integration Connect supports the message-transport protocols shown in Table 10. Of these supported protocols, 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 ICS-compatible components are required to send and receive documents between Business Integration Connect and InterChange Server over HTTP depends on the following:
Table 28 summarizes where to find information on how to configure
ICS-compatible components for use with InterChange Server.
Table 28. Configuring for HTTP transport with InterChange Server
Condition | For more information |
---|---|
If you are transferring non-SOAP documents with InterChange Server whose release version is before version 4.2.2 | Using HTTP transport protocol with pre-4.2.2 ICS |
If you are transferring non-SOAP documents with InterChange Server version 4.2.2 | Using HTTP transport protocol with v4.2.2 ICS |
If you are sending SOAP documents | Sending SOAP documents over HTTP/S |
As you decide which message transport to use with InterChange Server, consider the following benefit of using HTTP:
The ICS-compatible components required to send and receive documents between Business Integration Connect and InterChange Server over JMS are summarized in Table 71. 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 benefit of using JMS:
Guaranteed event delivery ensures that events are never lost or sent twice.
Business Integration Connect provides samples to assist you in the integration process with InterChange Server. These samples reside in the following subdirectory of the Business Integration Connect product directory:
Integration/WBI/WICS/samples
Table 29 lists the subdirectories of the samples directory for the different transport protocols that InterChange Server supports.
Table 29. Samples for InterChange Server integration