Canceling a deployment that is in progress

Before you start:

Canceling a deployment should only be a last resort if you are 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.

It is possible to cancel all outstanding deployments in the domain, or just those to a particular broker.
  • When canceling deployment across the domain, you must have full access on the Configuration Manager.
  • When canceling deployment to a specific broker, you must have full access on that broker.
If you want to ensure that previous deployment messages are not processed when an affected broker is restarted, first remove any deployment messages:
  1. Stop the broker
  2. Check the broker's SYSTEM.BROKER.ADMIN.QUEUE and SYSTEM.BROKER.EXECUTIONGROUP.QUEUE, and manually remove any deployment messages.
  3. Proceed to cancel the deployment.

Using the Message Brokers Toolkit

Follow these steps to cancel the deployment to a particular broker or all outstanding deployments in a domain, using the workbench:

  1. Switch to the Broker Administration perspective.
  2. In the Domains view, right-click either a particular broker or a connected domain.
  3. Click Cancel Deployment.

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.)

Using the mqsideploy command

Follow these steps to cancel a deployment using the mqsideploy command:

  1. Open a command window that is configured for your environment.
  2. Using these as examples, enter the appropriate command, typed on a single line:
    On z/OS:
    /f MQ01CMGR,dp t=yes b=B1

    This cancels deployment to the broker called B1. Omit the b argument to cancel all outstanding deployments in the domain.

    On other platforms:
    mqsideploy -i ipAddress -p port -q qmgr –c –b B1

    This cancels deployment to the broker called B1. Omit the -b parameter to cancel all outstanding deployments in the domain.

    The -i (IP address), -p (port), and -q (queue manager) parameters represent the connection details of the queue manager workstation, and on the z/OS console, MQ01CMGR is the name of the Configuration Manager component.

Next:

Continue by checking the results. (A BIP0892I information message is displayed to show that the request was received by the Configuration Manager.)

Using the Configuration Manager Proxy API

To cancel all outstanding deployments in a domain, use the cancelDeployment method of the ConfigManagerProxy class. For example:
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();
    }
  }
} 
To cancel deployment to a specific broker in a domain, use the cancelDeployment method of the BrokerProxy class. For example, to cancel deployment to a broker called B1:
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.)