Message flow application deployment
====================================
Package all the resources in your message flow into a broker archive (BAR) file for deployment.
You cannot deploy a message flow application directly to an execution group. You must package all the relevant resources into a BAR file, which you then deploy. When you add files to the broker archive, they are automatically compiled as part of the process. JAR files that are required by JavaCompute nodes in message flows are added automatically from your Java™ project.
The broker archive file is a compressed file, which is sent to the broker, where its contents are extracted and distributed to execution groups.
The mode in which your broker is working, can affect the number of execution groups and message flows that you can deploy, and the types of node that you can use. See Restrictions that apply in each operation mode.
This diagram shows the flow of events when you deploy a message flow application:
This diagram shows the flow of events when you deploy a message flow application.
The diagram illustrates the following steps.
1. You create a broker archive.
2. You add files to he broker archive.
3. You deploy the BAR file by sending it to the broker, from where its contents are distributed to the execution groups.
You can deploy a BAR file in two ways:
* Incremental BAR file deployment. Deployed files are added to the execution group. Files which exist in the execution group are replaced with the new version.
* Complete BAR file deployment. Files that are already deployed to the execution group are removed before the entire contents of the BAR file are deployed. Therefore, nothing is left in the execution group from any previous deployment.
Incremental BAR file deployment
If you run an incremental deployment of a BAR file, the broker extracts the contents of the BAR file and sends the contents to the specified execution group. The following conditions are applied when a file is deployed to the BAR file:
* If a file in the BAR file has the same name as an object that is already deployed to the execution group, the version that is already deployed is replaced with the version in the BAR file.
* If a file in the BAR file is of zero length, and a file of that name has already been deployed to the execution group, the deployed file is removed from the execution group.
When to use
* To incrementally deploy message flows, message sets, or other deployable objects to an execution group.
When not to use
* To completely clear the contents of the execution group before the BAR file is deployed. Use a complete BAR file deployment if you want this action.
Complete BAR file deployment
If you run a complete deployment of a BAR file, the broker extracts the deployable content of the BAR file and sends the contents to the specified execution group, first removing any existing deployed contents of the execution group.
When to use
* To deploy message flows, message sets, or other deployable objects to an execution group.
When not to use
* To merge the existing contents of the execution group with the contents of the BAR file. Use an incremental BAR file deployment if you want this action.
====================================
Package all the resources in your message flow into a broker archive (BAR) file for deployment.
You cannot deploy a message flow application directly to an execution group. You must package all the relevant resources into a BAR file, which you then deploy. When you add files to the broker archive, they are automatically compiled as part of the process. JAR files that are required by JavaCompute nodes in message flows are added automatically from your Java™ project.
The broker archive file is a compressed file, which is sent to the broker, where its contents are extracted and distributed to execution groups.
The mode in which your broker is working, can affect the number of execution groups and message flows that you can deploy, and the types of node that you can use. See Restrictions that apply in each operation mode.
This diagram shows the flow of events when you deploy a message flow application:
This diagram shows the flow of events when you deploy a message flow application.
The diagram illustrates the following steps.
1. You create a broker archive.
2. You add files to he broker archive.
3. You deploy the BAR file by sending it to the broker, from where its contents are distributed to the execution groups.
You can deploy a BAR file in two ways:
* Incremental BAR file deployment. Deployed files are added to the execution group. Files which exist in the execution group are replaced with the new version.
* Complete BAR file deployment. Files that are already deployed to the execution group are removed before the entire contents of the BAR file are deployed. Therefore, nothing is left in the execution group from any previous deployment.
Incremental BAR file deployment
If you run an incremental deployment of a BAR file, the broker extracts the contents of the BAR file and sends the contents to the specified execution group. The following conditions are applied when a file is deployed to the BAR file:
* If a file in the BAR file has the same name as an object that is already deployed to the execution group, the version that is already deployed is replaced with the version in the BAR file.
* If a file in the BAR file is of zero length, and a file of that name has already been deployed to the execution group, the deployed file is removed from the execution group.
When to use
* To incrementally deploy message flows, message sets, or other deployable objects to an execution group.
When not to use
* To completely clear the contents of the execution group before the BAR file is deployed. Use a complete BAR file deployment if you want this action.
Complete BAR file deployment
If you run a complete deployment of a BAR file, the broker extracts the deployable content of the BAR file and sends the contents to the specified execution group, first removing any existing deployed contents of the execution group.
When to use
* To deploy message flows, message sets, or other deployable objects to an execution group.
When not to use
* To merge the existing contents of the execution group with the contents of the BAR file. Use an incremental BAR file deployment if you want this action.
Comments
Post a Comment