Planning for integration with Message Broker

To plan for your integration to WebSphere Business Integration Message Broker, follow the steps outlined in Planning the back-end integration. Table 79 summarizes the integration steps to integrate Business Integration Connect with Message Broker.

Table 79. Planning integration with WebSphere Business Integration Message Broker

Integration step For more information
1. Confirm that you have a supported version of WebSphere Business Integration Message Broker installed and available to WebSphere Business Integration Connect.

"Integrating with WebSphere Business Integration Message Broker": Message Broker versions that Business Integration Connect supports

2. Determine the business protocol of the WebSphere Business Integration Message Broker 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 message transport to use between WebSphere Business Integration Connect and WebSphere Business Integration Message Broker.

"Integrating with WebSphere Business Integration Message Broker": Message transports that Message Broker supports

5. Configure WebSphere Business Integration Connect.

"Integrating with WebSphere Business Integration Message Broker": Configuring Business Integration Connect for Message Broker

Message Broker versions that Business Integration Connect supports

Version 4.2.2 of Business Integration Connect can support integration with version 5.0 of Message Broker. Message Broker is available on several platforms, including Windows 2000 and several UNIX-based platforms. For more information, consult your installation guide for Message Broker in the WebSphere Business Integration Message Broker documentation set.

Message transports that Message Broker supports

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 WebSphere Business Integration Message Broker:

Support for these message transport protocols requires the installation and configuration of IBM WebSphere MQ.

Using HTTP with Message Broker

Message Broker uses the HTTP transport protocol for its Web Services transactions. To send and receive documents between Business Integration Connect and Message Broker over the HTTP protocol requires no additional software. However, to send the document out of Message Broker to some other destination does require WebSphere MQ.

Note:
Business Integration Connect supports both asynchronous and synchronous interactions with Message Broker over HTTP.

Using JMS with Message Broker

Message Broker uses the JMS transport protocol for most of its transactions. To send and receive documents between Business Integration Connect and Message Broker over the JMS transport protocol, you must use JMS queues. If these two components reside on different machines, you must create the JMS queues on each machine. Basically, support for JMS involves the use of a message flow within Message Broker and the underlying JMS queues. For more information on how to configure for JMS, see Using JMS transport protocol with Message Broker.

Note:
Business Integration Connect supports only asynchronous interactions with Message Broker over JMS.

Support for Message Broker integration

Business Integration Connect provides samples to assist you in the integration process with Message Broker. These samples reside in the following subdirectory of the Business Integration Connect product directory:

Integration/WBI/WBIMB/samples

Copyright IBM Corp. 2003, 2004