Before you start:
The following steps show you how to cancel an in-progress deployment.
The Configuration Manager allows only one deploy to be in progress to each broker at any one time. If for some reason a broker does not respond to a deployment request, the Configuration Manager does not allow subsequent deploy requests to reach the broker, because it correctly claims that a deployment is already in progress.
For any brokers from which you are still waiting for a reply, the deploy is cancelled, if they were previously connected. Use Cancel Deployment to unlock the Configuration Manager so that subsequent deploys to the broker can succeed. Otherwise, you cannot deploy to that broker. The action does not affect whether or not deploy messages are sent to the broker, nor does it remove any information that has already been deployed.
Cancel deployment is a domain-wide action: the locks for all outstanding deploys in the domain are removed.
Cancel deployment is the equivalent of the force deploy action in previous versions, except that cancel does not completely redeploy domain information.
For any brokers that have successfully deployed a configuration, the deployed information is kept on the broker.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
af03940_ |