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

Modifying the WebSphere MQ service for a broker

How you modify the WebSphere® MQ service for a broker.

To alter the status of a WebSphere Message Broker so that it runs as a WebSphere MQ service use the mqsichangebroker command.

Carry out the following procedure:

  1. Stop the broker and its associated queue manager. If it is a multi-instance broker, you must stop all broker instances, and the multi-instance queue manager, if you want the changes to take affect immediately after the queue manager restarts.
  2. Use the mqsichangebroker command with the –d defined option to activate the WebSphere MQ service as follows:
     mqsichangebroker MyBroker –d defined  
    where
    MyBroker
    Is the name of the broker that you want to modify.

    If the WebSphere MQ service did not previously exist, it is defined, and the service CONTROL attribute is set to QMGR.

    You should no longer start the broker with the mqsistart command. The broker starts and stops automatically when the queue manager starts and stops.

    You can stop the broker manually with the mqsistop command, but the broker will not restart until the queue manager is stopped and started again. For a multi-instance broker this can occur during failover of the active queue manager.

  3. Use the mqsichangebroker command with the –d undefined option to remove the WebSphere MQ service as follows:
     mqsichangebroker MyBroker –d undefined  
    where
    MyBroker
    Is the name of the broker that you want to modify.
    When a WebSphere MQ service is being removed, and the queue manager is stopped, the mqsichangebroker command needs to start the queue manager to perform the deletion of the service. The command then stops the queue manager. The following example shows a possible output:
    >mqsichangebroker BK3 -d undefined
    WebSphere MQ queue manager 'QM3' starting.
    5 log records accessed on queue manager 'QM3' during the log replay phase.
    Log replay for queue manager 'QM3' complete.
    Transaction manager state recovered for queue manager 'QM3'.
    WebSphere MQ queue manager 'QM3' started.
    Waiting for queue manager 'QM3' to end.
    Waiting for queue manager 'QM3' to end.
    WebSphere MQ queue manager 'QM3' ended.
    BIP8071I: Successful command completion.

    You can start the broker manually using the mqsistart command, which invokes the WebSphere MQ service to restart the broker.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:05


Task topicTask topic | Version 8.0.0.7 | be13760_