WebSphere MQ resources for the User Name Server

The User Name Server depends on a number of WebSphere MQ resources: some must be available; others depend on the broker domain setup:
  1. The User Name Server must be associated with a queue manager to host its services. You must specify a queue manager name when you create the User Name Server. If this queue manager does not exist, it is created for you. On z/OS, you must create a queue manager in WebSphere MQ for your broker. See Creating a broker on z/OS for more details.

    The User Name Server can share a queue manager with a component (broker, or the Configuration Manager, or both) if they are on Windows platforms.

  2. The User Name Server must have a number of fixed-name queues on its queue manager. These allow it to exchange information with other components in the broker domain. These queues are defined for you when the User Name Server is created.
  3. The User Name Server must communicate with the Configuration Manager. If the two do not share a queue manager, you must define the transmission queues and channels to support two-way communications between the two queue managers.
  4. The User Name Server must communicate with every broker in the broker domain. Define transmission queues and channels to support two-way communications between the User Name Server and every broker except the one (if defined) that shares its queue manager.
  5. The User Name Server's queue manager must have a listener to receive messages from other components that do not share its queue manager. Create a listener for every protocol used for connections to the User Name Server. If you create a TCP/IP listener, you must also decide which port it must listen on.
Related concepts
Broker domains
Related tasks
Creating a broker on z/OS
Related reference
Designing the WebSphere MQ infrastructure
WebSphere MQ resources for brokers
WebSphere MQ resources for the Configuration Manager