Although you might be installing
only one broker initially, you might want to 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 might consider creating the
Configuration
Manager on
z/OS to manage the broker domain:
- In a new installation of WebSphere Event
Broker,
or
- If you are migrating from an earlier version of the product, where
the Configuration
Manager was previously on Windows.
If you want to run a
Configuration
Manager on
z/OS, you can either:
If you are using publish/subscribe with
security, you also require a User Name Server,
which can be on z/OS or another
platform.
The following rules apply:
- Queue managers must 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®. See Database contents for
details of the DB2 database
user tables that are created.
- 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 WebSphere MQ queues that are created and
used by WebSphere Event
Broker on z/OS in mqsicreatebroker command.
When
planning to work in a
z/OS environment,
you must complete the following tasks:
- Create started task procedures for the broker, User Name Server, and Configuration
Managers that you plan to use. These
procedures must be defined, in the started task table, with an appropriate
user ID.
- Decide on your recovery strategy. As part of your systems architecture,
you must have a strategy for restarting systems if they end abnormally.
Common solutions are to use automation products like NetView or the
Automatic Restart Manager (ARM) facility. You can configure WebSphere Event
Broker to use ARM.
- Plan for corequisite products, including UNIX® System Services, Resource Recovery
Services, DB2, WebSphere MQ, and Java.
- Ensure that the runtime library system (RTLS) for the broker is
turned off in the default options of the language environment for
the system. This setting is required because the broker code is compiled
using XPLINK, and XPLINK applications
cannot be started while RTLS is active.
- Collect broker statistics on z/OS.
See the following topics for more information:
For an overview of how to create WebSphere Event
Broker components, see Creating WebSphere Event Broker components on z/OS.