This topic contains sections marked as revised for this release

WebSphere Message Brokers
File: af03950_
Writer: John Morris-Smith

Task topic

This build: July 31, 2007 21:29:21

Removing a deployed object from an execution group

Before you start:

To remove a deployed message flow, first stop the message flow.

You can remove deployed objects from an execution group in three ways:

Using the Message Broker Toolkit

Follow these steps to remove an object from an execution group using the workbench.

  1. Switch to the Broker Administration perspective.
  2. From the Domains view, right-click the object that you want to remove.
  3. Click Remove from the pop-up menu, and OK to confirm.

An automatic deployment is performed for the updated broker and a BIP08921 information message is produced, which confirms that the request was received by the Configuration Manager.

Using the mqsideploy command

Follow these steps to remove an object from an execution group 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:
    On z/OS:
    /f MQ01CMGR,dp t=yes b=broker e=execgroup
                          d=file1.cmf:file2.cmf:file3.dictionary:file4.xml

    where MQ01CMGR is the name of the Configuration Manager component.

    On distributed platforms:
    mqsideploy -i ipAddress -p port -q qmgr –b broker –e execgp
                          –d file1.cmf:file2.cmf:file3.dictionary:file4.xml

    where -i IP address, -p port, and -q qmgr specify the connection details of the Configuration Manager workstation.

    The -d parameter (d= on z/OS) is a colon-separated list of files that are to be removed from the named execution group. When you invoke the command, the deployed objects (file1.cmf, file2.cmf, file3.dictionary, file4.xml) are removed from the specified execution group and broker.

    Optionally, specify the m= (z/OS) or -m (distributed) option to clear the contents of the execution group. This option tells the execution group to completely clear any existing data before the new bar file is deployed.

The command reports when responses are received from the Configuration Manager and any brokers that are affected by the deployment. If the command completes successfully, it returns 0.

Using the Configuration Manager Proxy API

To remove deployed objects from an execution group, get a handle to the relevant ExecutionGroupProxy object, and then invoke the deleteDeployedObjectsByName() method. For example:
import com.ibm.broker.config.proxy.*;

public class DeleteDeployedObjects {
  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");
      ExecutionGroupProxy e =
            b.getExecutionGroupByName("default");
      e.deleteDeployedObjectsByName(
            new String[] { "file1.cmf",
                           "file2.cmf",
                           "file3.dictionary",
                           "file4.xml" }, 0);
    }
    catch (ConfigManagerProxyException e) {
      e.printStackTrace();
    }
  }
} 
Next:

If you have deleted one or more message flows, you can now delete the resource files that are associated with and used by those message flows; for example, JAR files.

Related reference
mqsideploy command
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:29:21

af03950_ This topic's URL is: