Removing a deployed object from an execution group

You can remove deployed objects from an execution group, for example, to rename them..

Before you start:

Stop all message flows in the execution group. See Starting and stopping message flows.

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

Using the Message Brokers 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.

Next:

If you have removed one or more message flows, you can now remove the resource files that are associated with those message flows; for example, JAR files.

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.

Next:

If you have removed one or more message flows, you can now remove the resource files that are associated with those message flows; for example, JAR files.

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 removed one or more message flows, you can now remove the resource files that are associated with those message flows; for example, JAR files.

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

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

af03950_