Before you start:
Canceling a deployment should be used only as a last resort, and you should be sure that a broker, or several brokers in a domain, will never be able to process a previous deployment request. For this reason, make sure that you understand the implications of this action, described in the Cancel deployment overview topic.
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:
Continue by checking the results. A BIP0892I information message is displayed to show that the request was received by the Configuration Manager.
Follow these steps to cancel a deployment using the mqsideploy command:
Next:
Continue by checking the results. A BIP0892I information message is displayed to show that the request was received by the Configuration Manager.
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:
Continue by checking the results. A BIP0892I information message is displayed to show that the request was received by the Configuration Manager.