Deploying a broker configuration

The broker configuration deployment overview explains when you might want to deploy a broker configuration.

Using the Message Brokers Toolkit

If you modify any multicast or interbroker settings with the workbench, a broker configuration deployment is automatically initiated when the changes are applied.

Using the mqsideploy command

Follow these steps to deploy a broker configuration using the mqsideploy command:

  1. Open a command window that is configured for your environment.
  2. Using these as examples, enter the appropriate command, typed on a single line, specifying the broker to which you want to deploy:
    On z/OS:
    /f MQ01CMGR,dp b=broker
    On other platforms:
    mqsideploy -i ipAddress -p port -q qmgr -b broker
    The -i (IP address), -p (port), and -q (queue manager) parameters represent the connection details of the queue manager workstation, and on the z/OS console, MQ01CMGR is the name of the Configuration Manager component.

    By specifying the broker to which you want to deploy (b= or -b), without indicating a bar file (-a), the broker configuration is deployed rather than a message flow application.

Next:

Continue by checking the results of the deployment.

Using the Configuration Manager Proxy API

Use the deploy method of the BrokerProxy class.

For example:
import com.ibm.broker.config.proxy.*;

public class DeployBrokerConfig {
  public static void main(String[] args) {
    ConfigManagerConnectionParameters cmcp =
            new MQConfigManagerConnectionParameters
                ("localhost", 1414, "QM1");
    try {
      ConfigManagerProxy cmp = ConfigManagerProxy.getInstance(cmcp);
      TopologyProxy t = cmp.getTopology();
      BrokerProxy b = t.getBrokerByName("BROKER1");
      if (b != null) {
        b.deploy();
      }
    }
    catch (ConfigManagerProxyException e) {
      e.printStackTrace();
    }
  }
}

Next:

Continue by checking the results of the deployment.