If you change a BAR file, and want to propagate those changes to one or more integration nodes, you can redeploy the updated BAR file.
You can redeploy the updated BAR file to one or more integration servers by using one of the deployment methods described in Deploying a BAR file. You do not have to stop the message flows that you deployed previously. All resources in the integration server or groups that are in the redeployed BAR file are replaced and new resources are applied.
If your updates to the BAR file include the deletion of resources, a redeployment does not result in their deletion from the integration node. For example, assume that your BAR file contains applications A1, A2, and A3. Update the file by removing A2 and adding application A4. If you redeploy the BAR file, all four applications are available in the integration server when the redeployment has completed. A1 and A3 are replaced by the contents of the redeployed BAR file.
If your message flows are not transactional, stop the message flows before you redeploy to be sure that all the applications complete cleanly and are in a known and consistent state. You can stop individual message flows, integration servers, or integration nodes.
If your message flows are transactional, the processing logic that handles commitment or rollback ensures that resource integrity and consistency are maintained.
Check the results of the redeployment by following the instructions in Checking the results of deployment.