Planning for integration with Message Broker

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

Table 60. 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 Partner Gateway.

Integrating with WebSphere Business Integration Message Broker: Message Broker versions that WebSphere Partner Gateway supports

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

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

5. Configure WebSphere Partner Gateway.

Integrating with WebSphere Business Integration Message Broker: Configuring WebSphere Partner Gateway for Message Broker

Message Broker versions that WebSphere Partner Gateway supports

WebSphere Partner Gateway supports 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

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.

HTTP

Message Broker uses the HTTP transport protocol for its Web Services transactions. You need no additional software to send and receive documents between WebSphere Partner Gateway and Message Broker over the HTTP protocol. However, to send the document out of Message Broker to some other destination, you need WebSphere MQ.

Note: WebSphere Partner Gateway supports both asynchronous and synchronous interactions with Message Broker over HTTP.

JMS

Message Broker uses the JMS transport protocol for most of its transactions. To send and receive documents between WebSphere Partner Gateway and Message Broker over the JMS transport protocol, you must use JMS queues. If these two components reside on different computers, you must create the JMS queues on each computer. 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: WebSphere Partner Gateway supports only asynchronous interactions with Message Broker over JMS.

Support for Message Broker integration

WebSphere Partner Gateway provides samples to assist you in the integration process with Message Broker. These samples reside in the following subdirectory of the WebSphere Partner Gateway product directory:

Integration/WBI/WBIMB/samples

Copyright IBM Corp. 2003, 2005