For Business Integration Connect and the back-end system to communicate,
you must choose a transport protocol that both these back-end-integration
components can support. Table 13 summarizes the information that this guide provides on
supported transport protocols.
Table 13. How to get information on supported transport protocols
Back-end-integration component | For more information |
---|---|
Business Integration Connect | Configuring Business Integration Connect |
Back-end system | Refer to the appropriate chapter of this guide, as listed in How do you access your back-end application?. |
For these two back-end-integration components to communicate, you must ensure that a transport-protocol mechanism exists; that is, the appropriate software and hardware entities must exist for these two components to communicate over the desired transport protocol. This section summarizes the steps in the creation of a transport-protocol mechanism for the following transport protocols:
To communicate over the HTTP or HTTPS transport protocol, Business Integration Connect and the back-end system require a URL address, one that each can access. Therefore, you must supply a URL address and provide it to each of these components. This address must have the following format:
bcgreceiver
To communicate over the JMS transport protocol, Business Integration Connect and the back-end system require a JMS queue for each direction of the communication. Therefore, you must take the following steps to supply the appropriate JMS queues:
The JMS queue manager can exist on any machine, including the following:
In addition, you can have a queue manager on both the machine where the back-end system resides and the machine where Business Integration Connect resides. In this case, use setup channels to tie the two queue managers together. Using this method, neither side needs to make client connections over the network.
Instructions for configuring a JMS transport-protocol mechanism using WebSphere MQ version 5.3 are provided in Appendix A, Configuring a JMS protocol with WebSphere MQ.