Although you might be installing only one broker initially, you should consider how the product will be used in your organization in a few years' time. Planning ahead makes developing your WebSphere Event Broker configuration easier.
You should consider creating the Configuration Manager on z/OS to manage the broker domain. If you are migrating from an earlier version of WebSphere Event Broker you should consider migrating the Configuration Manager that was previously on Windows.
If you are using publish/subscribe with security, you also need a User Name Server. The User Name Server can be on z/OS or on another platform. The queue managers need to be interconnected so that information from the User Name Server can be distributed to the brokers on other queue managers.
A broker requires access to a queue manager and to DB2. A Configuration Manager and User Name Server require access to a queue manager only. A broker cannot share its queue manager with another broker, but a broker can share a queue manager with a Configuration Manager and User Name Server.
You cannot use WebSphere MQ shared queues to hold data related to WebSphere Event Broker as SYSTEM.BROKER queues, but you can use shared queues for your message flow queues.
You can find details of the DB2 database user tables and the WebSphere MQ queues created and used by WebSphere Event Broker on z/OS in the topic mqsicreatebroker command.
For an overview of how to create WebSphere Event Broker components,
see Creating WebSphere Event Broker components on z/OS
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ae22100_ |