Starting and stopping an integration node as an IBM MQ service

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

Before you begin

Ensure that you make the mqm user ID a member of the mqbrkrs group. On Windows systems, you must restart your workstation for the change to take effect.

Procedure

To configure an integration node to run as an IBM MQ service, complete the following steps.

  1. Create an integration node to start as an IBM 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 an IBM MQ service.
    MyQMGR
    Is the name of the queue manager that is associated with the integration node.
  2. Optional: If you want to create an App Connect Enterprise vault to hold the credentials that are used by the integration node when secured resources are accessed, use the mqsivault command.
    For example, 
    mqsivault MyBroker --create --vault-key 12345678
    where
    MyBroker
    Is the name of the integration node that you want to start and stop as an IBM MQ service.
  3. Optional: If you created an IBM App Connect Enterprise vault by running the mqsivault command at step 2, you must configure your environment by running one of the following steps:
    1. Set the vault key as an environment variable. For example, on Windows: set MQSI_VAULT_KEY=12345678
    2. Add the vault key to an .mqsivaultrc file and copy the file into the home directory of the user who starts the IBM MQ queue manager.
      For more information about IBM App Connect Enterprise vaults and the .mqsivaultrc file, see mqsicreatebroker command and mqsivault command.
  4. Stop the queue manager.

Results

When you configure an integration node to start and stop as an IBM 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 IBM 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 and Linux® systems, the integration node environment is inherited from IBM MQ. Set any required environment variables (such as ODBCINI) by using a script in the work_path/common/profiles directory. For more information, see Setting up a command environment.