WebSphere Event Broker depends on the WebSphere MQ transport services to support internally-generated communications between components. Some of these resources are created for you, when you create WebSphere Event Broker components that depend on them. Others depend on the exact setup of your broker domain; you must create these resources yourself.
Communications between WebSphere Event Broker components are protocol-independent, with the exception of the connection between every instance of the workbench and the Configuration Manager. This must be a TCP/IP connection, as must connections to the WebSphere MQ Everyplace and SCADA nodes. Other connections can use any of the protocols supported by the WebSphere MQ messaging product for the operating system for your WebSphere Event Broker product.
Except for WebSphere MQ Everyplace and SCADA applications, applications that use broker services must also use WebSphere MQ to send and receive all messages. The resources required by your applications (queues and client connection and server connection channels) are application specific; you must create these resources yourself.
The information here concentrates on the specific requirements that WebSphere Event Broker imposes on a WebSphere MQ network. For a full description of designing and connecting a WebSphere MQ network, see WebSphere MQ Intercommunication, which covers the basics, such as setting up transmission queues and channels, in detail.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ae19610_ |