WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Removing a deployed object from an execution group

You might want to remove deployed objects from an execution group if, for example, you want to rename them.

Before you start:

Stop all message flows in the execution group. For more details, see Stopping an execution group using the WebSphere Message Broker Toolkit or WebSphere Message Broker Explorer.

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

Using the WebSphere Message Broker Toolkit

To remove an object from an execution group by using the WebSphere Message Broker Toolkit, complete the following steps.

  1. In the Brokers view, right-click the object that you want to remove.
  2. Click Delete, then OK to confirm.

The request is sent to the broker, and a synchronous response is sent back.

Using the WebSphere Message Broker Explorer

To remove an object from an execution group by using the WebSphere Message Broker Explorer, complete the following steps.

  1. In the Navigator view, expand the broker and execution group with which you want to work.
  2. Right-click the object that you want to remove.
  3. Click Delete, then OK to confirm.

The request is sent to the broker, and a synchronous response is sent back.

Using the mqsideploy command

To remove an object from an execution group by using the mqsideploy command, complete the following steps.

  1. Open a command window that is configured for your environment.
  2. Enter the appropriate command for your operating system and configuration, using the following examples as a guide.
    On distributed systems:
    mqsideploy -i ipAddress -p port -q qmgr –e egroup
                –d file1.cmf:file2.cmf:file3.dictionary:file4.xml

    The -i (IP address), -p (port), and -q (queue manager) parameters represent the connection details for the queue manager associated with the broker. If you have created the broker on the computer on which you run this command, you can specify the broker name instead.

    mqsideploy -n brokerName -e egroup
    -d file1.cmf:file2.cmf:file3.dictionary:file4.xml
    On z/OS®:
    /f MQ01BRK1,dp e=egroup d=file1.cmf:file2.cmf:file3.dictionary:file4.xml

    where MQ01BRK1 is the name of the broker.

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

    Optionally, specify the -m parameter (m= on z/OS) to remove all currently-deployed message flows and message sets from the execution group as part of the deployment. If you do not set -m, the contents of the BAR file are deployed in addition to what is already deployed to the execution group. Any deployed objects with the same name as an item inside the BAR file are replaced by the version inside the BAR file. For a remove message flow or message set operation, the -m parameter is ignored.

The command reports when responses are received from the broker. If the command completes successfully, it returns zero (0).

Using the CMP API

To remove deployed objects from an execution group, get a handle to the relevant ExecutionGroupProxy object, then run the deleteDeployedObjectsByName method. Use the following code as an example.
import com.ibm.broker.config.proxy.*;

public class DeleteDeployedObjects {
  public static void main(String[] args) {
    BrokerConnectionParameters bcp =
            new MQBrokerConnectionParameters
                      ("localhost", 1414, "QM1");
    try {
      BrokerProxy b =
            BrokerProxy.getInstance(bcp);
      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.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:02


Task topicTask topic | Version 8.0.0.7 | af03950_