Connecting the User Name Server to a broker on z/OS

Before you start:

To complete this task, you must have completed the following task:

You need to make the broker known to the User Name Server. You can do this using either of the following methods.

If the User Name Server is not connected to the broker's queue manager, you need channels between the broker's queue manager and the User Name Server's queue manager. You need channels between the Configuration Manager queue manager and the broker's queue manager to receive message flows and Access Control Lists.

Check the z/OS console for the message BIP8204, which is issued when the User Name Server has successfully registered a client.

Change the Configuration Manager to use the queue manager name used by the User Name Server on z/OS, or another supported platform. You can use the mqsicreateconfigmgr or mqsichangeconfigmgr commands to set this value.

On the Topics panel in the workbench, you can view user information sent from the User Name Server.

Check that the User Name Server has registered the Configuration Manager. Also, check the z/OS console for message BIP8204, which is issued when the User Name Server has successfully registered a client. For more information on implementing topic-based security using the workbench, see Enabling topic-based security.

Example startup messages

When a broker starts for the first time, and a User Name Server queue manager has been specified, and no response has ever been received from the User Name Server, you will receive the following message:
+BIP9141W  UserNameServer 0 The component was started.
When the User Name Server starts and indicates that it has registered with the broker, you will receive the following message:
18:17:18.54 BIP9141W: The component was started. 
18:17:18.57 BIP2001I: The WebSphere Message Broker service has started, process  ID 196827.  
18:17:24.31 BIP8201I: User Name Server starting with refresh interval 60.
18:17:28.21 BIP8204I: User Name Server is registering a client with UUID   
                 12345678-1234-1234-1234-123456789abc, and cache version 0.