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.
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.
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.
- In the Brokers view, right-click the object that you want to remove.
- 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.
- In the Navigator view, expand the broker and execution group with which you want to work.
- Right-click the object that you want to remove.
- 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.
The command reports when responses are received from the broker. If the command completes successfully, it returns zero (0).
Using the CMP API
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();
}
}
}
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.