Starting and stopping an integration node as a WebSphere MQ service

Configuring an integration node to start and stop as a WebSphere® MQ service.

Before you begin

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.

About this task

To configure an integration node to run as a WebSphere MQ service, use one of the following options:

Procedure

  • Create an integration node to start as a WebSphere MQ service by using the mqsicreatebroker command with the -d parameter.
    Note: You must be a member of the mqm group to run the mqsicreatebroker command with the -d parameter.
    For example, 
    mqsicreatebroker MyBroker -q MyQMGR -d defined
    where
    MyBroker
    Is the name of the integration node that you want to start and stop as a WebSphere MQ service.
    MyQMGR
    Is the name of the queue manager associated with the integration node.
  • Modify an existing integration node to start as a WebSphere MQ service by using the mqsichangebroker command with the -d parameter.
    For example, 
    mqsichangebroker MyBroker -d defined
    where
    MyBroker
    Is the name of the integration node that you want to start and stop as a WebSphere MQ service.

Results

When you have configured an integration node to start and stop as a WebSphere MQ service:
  • The integration node starts and stops automatically when its associated queue manager starts and stops. For a multi-instance integration node, this action can occur during failover of the active queue manager.
  • A multi-instance integration node cannot be started in standby mode when its WebSphere MQ service is defined as active.
  • You can stop the integration node manually by using the mqsistop command, but the integration node does not restart until the queue manager is stopped and started again.
  • On UNIX systems the integration node 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 Setting up a command environment for more information.