Before you begin
On
z/OS, you must install
WebSphere MQ locally, because only local
connections to queue managers are supported.
Procedure
To configure WebSphere MQ on z/OS:
- Create your queue manager. When you create
your integration node, you must specify the queue manager to associate
with it. For more information, see the -q parameter
information in mqsicreatebroker command - z/OS.
- Your queue manager must have a dead-letter queue. If the
queue manager does not have a valid dead-letter queue, you must
define one. Check the STGCLASS value is valid
by completing the following steps:
- Check that this queue exists by using the WebSphere MQ command: +cpf DIS QMGR
DEADQ
- Check that the queue exists by using the command: +cpf
DIS QL(name) STGCLASS
- Then, use: +cpf DIS STGCLASS(...)
- Creating and deleting components on z/OS uses the WebSphere MQ command server.
- Ensure that the command server component is running.
The component is normally started automatically.
- The command server requires a reply-to queue based on
SYSTEM.COMMAND.REPLY.MODEL; by default, this model queue is defined
as permanent dynamic. However, if you leave the queue defined in this
way, each time you run a create or delete component command these
reply-to queues remain defined to the queue manager. To avoid these
queues persisting, you can set the SYSTEM.COMMAND.REPLY.MODEL queue
as temporary dynamic.
- If you have enabled WebSphere MQ Security,
you must define a set of security profiles for the integration
node to work. For a list of the security profiles that are required
and instructions on how to define them, see WebSphere MQ authorizations.
Results
The
WebSphere MQ environment
is now ready. All
IBM® Integration Bus for
z/OS system queues are defined
during customization.