Redeploying integration solutions to a production environment

If you change an integration solution, you can redeploy the updated solution to the same integration servers.

About this task

You can package an updated integration solution for redeployment by using one of the following methods:

You can repackage the updated integration solution in the BAR file editor, and generate a new BAR file; see Preparing packaged solutions for deployment.
You can refresh the existing BAR file; see Refreshing the contents of a BAR file.

You can redeploy the updated BAR file to one or more integration servers by using one of the deployment methods that are described in Deploying integration solutions to a production environment. You do not have to stop the message flows that you deployed previously. All the resources in the integration server that are also in the redeployed BAR file are replaced.

You do not have to redeploy JAR files unless you updated them. If one or more JAR files in your BAR file are present on the computer where the integration node is running, you can remove them from your BAR file before you deploy the BAR file again.

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 completes. A1 and A3 are replaced by the contents of the redeployed BAR file.

To clear previously deployed resources from the integration server before you redeploy (for example, if you are deleting resources), use one of the methods that are described in Deleting deployed resources.

To use the IBM Integration Toolkit, follow the instructions for a new deployment, making sure that you select Delete > All Flows and Resources before you deploy resources.
To use the mqsideploy command, follow the instructions for a new deployment, making sure that you add the -m parameter to perform a complete BAR file deployment.
To use the IBM Integration API, follow the instructions for a new deployment.

If your message flows are not transactional, stop the message flows before you redeploy resources to ensure 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.

What to do next

Check the results of the redeployment by following the instructions in Checking the results of deployment.