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, confirming that the request was received by the Configuration Manager.
A JAR file that is being used by a message flow cannot be deleted
before the message flow that is using it has first been deleted.
If more than one message flow is using the same JAR file, the all of these
message flows must first be removed before the JAR file can be deleted.
Follow these steps to remove an object from an execution group using the mqsideploy command:
The -d argument (or d= argument on z/OS) is a colon separated list of files to be removed from the named execution group. Invoking the command above causes the deployed objects (file1.cmf, file2.dictionary and file3.xml) to be removed from the specified execution group and broker.
The command displays feedback as responses are received from the Configuration Manager and any brokers 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.dictionary", "file3.xml" }, 0); } catch (ConfigManagerProxyException e) { e.printStackTrace(); } } }
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
af03950_ |