You can cancel all outstanding deployments in the domain, or just those sent to a particular broker. But cancel a deployment only as a last resort and be sure that the brokers affected, will never be able to process a previous deployment request.
Before you start:
Make sure that you understand the implications of this action. See Cancel deployment.
Check the details at the start of this topic, and then follow these steps to cancel the deployment to a particular broker or all outstanding deployments in a domain, using the workbench:
Deployments to the broker or domain are canceled.
Next:
Checking the results of deployment. A BIP0892I information message is displayed to show that the request was received by the Configuration Manager.
Check the details at the start of this topic, and then follow these steps to cancel a deployment using the mqsideploy command:
Next:
Checking the results of deployment. A BIP0892I information message is displayed to show that the request was received by the Configuration Manager.
First, check the details at the start of this topic
public class CancelAllDeploys { public static void main(String[] args) { ConfigManagerConnectionParameters cmcp = new MQConfigManagerConnectionParameters ("localhost", 1414, "QM1"); try { ConfigManagerProxy cmp = ConfigManagerProxy.getInstance(cmcp); cmp.cancelDeployment(); } catch (ConfigManagerProxyException e) { e.printStackTrace(); } } }
import com.ibm.broker.config.proxy.*; public class CancelDeploy { 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("B1"); b.cancelDeployment(); } catch (ConfigManagerProxyException e) { e.printStackTrace(); } } }
Next:
Checking the results of deployment. A BIP0892I information message is displayed to show that the request was received by the Configuration Manager.