Deploying a publish/subscribe topics hierarchy

Deploy your topics hierarchy using the workbench, the mqsideploy command, or the Configuration Manager Proxy.

Before you start:

Make sure that you have configured your broker domain.

The topic deployment overview explains when you might want to deploy a topic hierarchy and the difference between a complete and a delta deployment.

You can configure the workbench preferences so that a topics hierarchy is automatically deployed after you have made a change.

Using the Message Brokers Toolkit

Follow these steps to deploy a topics hierarchy using the workbench:

  1. Switch to the Broker Administration perspective.
  2. In the Domains view, expand the Domains from where you want to perform the deploy.
  3. Right-click Topics hierarchy.
  4. Click Deploy Topics Configuration.
  5. Click Delta to deploy only the changed items, or click Complete to deploy the entire configuration.

The topics hierarchy is deployed, and the Configuration Manager distributes the topics to brokers in the domain.

Using the mqsideploy command

Follow these steps to deploy a topics hierarchy using the mqsideploy command:

  1. Open a command window that is configured for your environment.
  2. Using the examples below, enter the appropriate command, typed on a single line:
    z/OS platform On z/OS®:
    /f MQ01CMGR,dp t=yes

    This command performs a delta deployment. Add the m=yes parameter to deploy the entire configuration.

    On other platforms:
    mqsideploy -i ipAddress -p port -q qmgr -t

    This command performs a delta deployment. Add the –m parameter to deploy the entire configuration.

    The -i (IP address), -p (port), and -q (queue manager) parameters represent the connection details of the queue manager workstation.

Using the Configuration Manager Proxy

Use the deploy method of the TopicRootProxy class. By default, the deploy method performs an incremental (delta) deployment. To deploy the complete hierarchy, use a variant of the method that includes the Boolean isDelta parameter set to false. Setting this parameter to true indicates an incremental deployment.

To perform a complete deployment, for example:
import com.ibm.broker.config.proxy.*;

public class DeployTopics {
  public static void main(String[] args) {
    ConfigManagerConnectionParameters cmcp =
            new MQConfigManagerConnectionParameters
                ("localhost", 1414, "QM1");
    try {
      ConfigManagerProxy cmp =
            ConfigManagerProxy.getInstance(cmcp);
      TopicRootProxy t = cmp.getTopicRoot();
      t.deploy(false);
    }
    catch (ConfigManagerProxyException e) {
      e.printStackTrace();
    }
  }
} 
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:21:52

af03930_