There are different types of deployment. Find out what they are and when you should use them.
Follow the links to later topics in this section that describe each type of deployment and the situation in which each type should, and should not, be used.
This type deployment uses a broker archive (BAR) file.
This table lists examples of appropriate ways of deploying in a number of common scenarios:
Scenario | Suggested deployment |
---|---|
Adding a broker to the domain (when not using publish/subscribe) | None required. |
Modifying the publish/subscribe topic hierarchy | Delta deployment of the topics hierarchy. (The changed elements only in the topic hierarchy are deployed to all brokers in the domain.) |
Connecting publish/subscribe brokers using connections or a collective | Delta topology deployment. |
Modifying the publish/subscribe topic hierarchy, after adding a new broker to the domain | Complete topics deployment. (The entire topic hierarchy is deployed to all brokers in the domain. The new broker also receives the complete topic hierarchy.) |
Tidying up a broker's resources after removing it from the topology | If the broker is part of a publish/subscribe network, or if you are using the workbench, initiate a delta publish/subscribe topology deployment. Otherwise, no deployment is required. |
Creating an execution group | Message flow application deployment using an incremental BAR file deployment. |
Deleting an execution group | None required. |
If a broker is not responding to a deploy request | Ensure that the broker is running. If the broker is not running, cancel the broker deployment. You should cancel a broker deployment only if you are sure that the broker will never respond to the deploy request. |