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
Starting and stopping a broker as a WebSphere MQ service
Configuring a broker to start and stop as a WebSphere® MQ service.
Before you start:
Ensure that you make the mqm user ID a member of the mqbrkrs group. On Windows, you must reboot your workstation for the change to take effect.
To configure a broker to run as a WebSphere MQ service, use one of the following options:
When you have configured a broker to start and stop as
a WebSphere MQ service:
- The broker starts and stops automatically when its associated queue manager starts and stops. For a multi-instance broker, this action can occur during failover of the active queue manager.
- A multi-instance broker cannot be started in standby mode when its WebSphere MQ service is defined as active.
- You can stop the broker manually by using the mqsistop command, but the broker
does not restart until the queue manager is stopped and started again.
Alternatively, you can start the broker manually with the mqsistart command, which invokes the WebSphere MQ service to start the broker.
- On UNIX systems the broker environment is inherited from WebSphere MQ. Set any required environment variables (such as ODBCINI) by using a script in the work_path/common/profiles directory. See Command environment: Linux and UNIX systems for more information.