Message Flow Application Deployment

Message Flow Application Deployment

At First, Package all your resources in the message flow to a broker archive (BAR) file for deployment. Use the techniques that I have discussed earlier in my previous post. A message flow application cannot be deployed directly into an execution group. At first all the relevant resources should be packaged into a BAR file, now you can deploy. When you add files to the broker archive (BAR) file, they are automatically compiled as a part of the entire process. JAR files that are required by JavaCompute nodes in message flows are added automatically from your Java project. The broker archive (BAR) file is a compressed type of file, which is sent to the broker for its content extraction and then distributed to the execution groups.

This mode of working can affect the number of execution groups and message flows that you can deploy, and the types of nodes that you can use.

A BAR file can be deployed in two ways:

Incremental BAR files deployment:

Here, Deployed files are added to the execution group. Files which exist in the execution group are replaced with the new version. If you run an incremental deployment of a BAR file, the broker extracts the contents of the BAR file and send 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.
• This can be used when, to incrementally deploy message flows, message sets, or other deployable objects to an execution group.
• This should not be used when, 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 files deployment:

Here, 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. 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.

• This can be used when, to deploy message flows, message sets, or other deployable objects to an execution group.
• This should not be used when, 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.