Start of change

Connecting directly to a Configuration Manager on z/OS

Connection to the z/OS Configuration Manager directly, can be from:
  • The Message Brokers Toolkit.
  • A Configuration Manager Proxy (CMP) application.
  • One of the WebSphere Event Broker commands used for the Configuration Manager, for example mqsicreateexecutiongroup.
All of these connect through the WebSphere MQ server connection channel, SYSTEM.BKR.CONFIG. You can connect directly to this channel only if you have the optional WebSphere MQ Client Attach feature installed.

An alternative is to connect through an intermediate queue manager; see Connecting to a z/OS Configuration Manager through an intermediate queue manager.

Before you start

Before starting this task, you must have set up your system components as described in Creating WebSphere Event Broker components on z/OS.

Set up the connections between the Message Brokers Toolkit and the Configuration Manager by carrying out the following tasks:

  1. Verify that your queue manager and channel initiator are running and that the channel initiator is listening on the appropriate port.

    For more information see your WebSphere MQ documentation.

  2. Ensure that your Configuration Manager is running; see Starting and stopping a Configuration Manager on z/OS.
  3. Ensure that your user ID has been given the appropriate authorization on the z/OS Configuration Manager.
    In SDSF, grant FULL domain access to user Id test1. For all machines enter:
    '/F WMQxCFG CA U=test1,A=YES,P=YES,X=F' 
    To grant access to a specific machine for user test1, enter:
    '/F WMQxCFG CA U=test1,M=mymachine,P=YES,X=F' 
  4. Create a new domain connection; see Creating a domain connection.
Related concepts
Configuration Manager
Related tasks
Creating WebSphere Event Broker components on z/OS
Creating a Configuration Manager on z/OS
Starting and stopping a Configuration Manager on z/OS
Deploying a broker archive file
End of change