See information about the latest product version
Customizing the z/OS environment
If you are planning to use a z/OS® environment, consider whether to create your brokers on z/OS. You must also complete a number of tasks to configure your environment.
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® Message Broker configuration easier.
- A broker requires access to a queue manager.
- A broker cannot share its queue manager with another broker.
- You cannot use WebSphere MQ shared queues to hold data related to WebSphere Message 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 Message Broker on z/OS in mqsicreatebroker command.
- Create started task procedures for each broker 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 Tivoli® NetView® for z/OS or the Automatic Restart Manager (ARM) facility. You can configure WebSphere Message Broker to use ARM.
- Plan for corequisite products, including UNIX System Services, Resource Recovery
Services (RRS), WebSphere MQ, and Java™.
You might also want to include DB2® in your configuration, if your message flows access databases.
- 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.
- z/OS customization overview
- Customizing UNIX System Services on z/OS
- WebSphere MQ planning for z/OS
- Resource Recovery Service planning on z/OS
- Defining the started tasks to z/OS Workload Manager (WLM)
- Automatic Restart Manager planning
- Mounting file systems
- Checking the permission of the installation directory
- Customizing the version of Java on z/OS
- Checking APF attributes of bipimain on z/OS
- Collecting broker statistics on z/OS
- Configuring an execution group address space as non-swappable on z/OS
For an overview of how to create WebSphere Message Broker brokers, see Creating a broker on WebSphere Message Broker for z/OS.