BAR file deployment

You can use incremental BAR file deployment or complete BAR deployment to deploy your solution.

You can deploy a BAR file in two ways:
  • Incremental BAR file deployment. Deployed files are added to the integration server. Files that exist in the integration server are replaced by the new versions.
  • Complete BAR file deployment. Files that are already deployed to the integration server are removed before the entire contents of the BAR file are deployed. Therefore, nothing is left in the integration server from previous deployments.

Incremental BAR file deployment

If you run an incremental deployment of a BAR file, the integration node extracts the contents of the BAR file and sends the contents to the specified integration server. 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 integration server, the version that is already deployed is replaced by the version in the BAR file.
  • If a file in the BAR file is of zero length, and a file of that name is already deployed to the integration server, the deployed file is removed from the integration server.

Use incremental BAR file deployment to deploy applications, libraries, message flows, message model schema files, or other deployable objects incrementally to an integration server.

To completely clear the contents of the integration server before the BAR file is deployed, use complete BAR file deployment instead.

Complete BAR file deployment

If you run a complete deployment of a BAR file, the integration node extracts the deployable content of the BAR file and sends the contents to the specified integration server, first removing any existing deployed contents of the integration server.

Use a complete BAR file deployment to deploy applications, libraries, message flows, message sets, or other deployable objects to an integration server.

To merge the existing contents of the integration server with the contents of the BAR file, use incremental BAR file deployment instead.