IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

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 IBM® Integration Bus configuration easier.

The following rules apply to the configuration:

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 IBM Integration Bus 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 IBM Integration Bus 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 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 IBM Integration Bus 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.
Collect broker statistics on z/OS.

See the following topics for more information:

For an overview of how to create IBM Integration Bus brokers, see Creating a broker on z/OS.

ae22100_.htm |

Last updated Friday, 21 July 2017

Customizing the z/OS environment

Subtopics