This topic contains sections marked as revised for this release
To remove a deployed message flow, first stop the message flow.
Follow these steps to remove an object from an execution group using the workbench.
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.
Follow these steps to remove an object from an execution group using the mqsideploy command:
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.
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();
}
}
}
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.