WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Connecting to a remote broker
To administer a remote broker by using the WebSphere® Message Broker Toolkit or WebSphere Message Broker Explorer, you must connect to the broker.
Before you start:
Before you can connect to a remote broker, the broker
and its queue manager must be running. You must also complete the
following steps:
- Ensure that a command server is running on the queue manager.
- Ensure a server-connection channel has been defined on the broker queue manager. When you create a broker, a default SVRCONN channel, called SYSTEM.BKR.CONFIG, is created. This channel supports connections from one or more remote clients to the broker.
- Create a TCP/IP listener on the broker queue manager.
- Ensure that the listener is running.
- Create a group and a user ID on the computer where the broker is running by using the local system facilities; for example, the groupadd command on Linux on x86. Add the user ID to the group.
- Run the setmqaut command on the broker queue
manager to grant authority to the group:
setmqaut -m queueManager -t qmgr -g group +connect
You can create a connection to a remote broker, or you can create a connection to a remote broker by using settings from a .broker file. Right-click the Brokers folder, and click Connect to a Remote Broker Using *.broker File. Select the .broker file, and click Open. The connection to the remote broker is created in your workspace.
To create a connection to a remote broker:
You can now view properties and configure your broker using the WebSphere Message Broker Toolkit or WebSphere Message Broker Explorer.