Boomi – Deployment scenarios

Review some common scenarios for deploying processes or components to an environment.

Deploying a process and its dependent components

One of the most common deployment tasks is to deploy a process and all of its dependent components to an environment such as Test.

• Create a packaged component version of the process or component from the Build page or the Packaged Component page. The process and all of the dependent components that are required to support the process (such as maps or profiles and any subprocesses) are included in the packaged component. By creating a packaged component, you create a record of what that process looks like in development at a given point in time. Although you can create a packaged component at any time during its development, you typically want to create it when you have finished building the process, and are ready to test it or share it with other users.

Note :- If your process includes Process Route components, you need to create an individual packaged component of the Process Route, and then deploy it and all of its subprocesses independently from the parent process.

• Deploy the packaged component to the selected environment from the Deployments page. In addition to selecting an environment to deploy to, you can provide notes about the deployment, display detailed information about the versoin of the packaged component that you are deploying, or choose a different version to deploy, and more. A deployment consists of a single version of a packaged component that is deployed to a specified environment.

Deploying multiple processes or components

You might want to deploy multiple processes or components to an environment at the same time as part of a coordinated release. You can create multiple packaged components at one time and assign them all the same version ID to help you track their usage.

1. Create a packaged component version of the processes and components you want to deploy from the Packaged Component page.
2. You can create multiple packaged components by turning on one or more check boxes in the components list. An individual packaged component version is created for each component, but all packaged components are assigned the same version ID. A common version ID helps you track the group of related components.
3. Deploy the packaged components to the selected environment from the Deployments page.
4. By default, the most recent version of each packaged component will be deployed, but you can choose a different version of any packaged component. You can also provide notes about the overall deployment.

Deploying a different version of a previously deployed packaged component

You can deploy a different version of a packaged process or component that is actively deployed to an environment. For example, you might need to redeploy a previous version to roll back a deployment that has problems or deploy an updated version to roll out enhancements. Before you deploy a different version, you can compare two versions of the packaged component—the one that is actively deployed and the one that you are thinking about deploying in its place.

1. From the Deployments page, compare two versions of the deployed packaged component to identify the differences.
2. The comparison results highlight the differences between the two version of a packaged component. You can contact the user who last modified a component within either version or select a different version with which to compare.
3. After you identify the version of the packaged component that you want to deploy, do the following:
4. Create a new deployment (Deploy Packaged Components button on the Deployments page).
5. Select the version that you want to deploy (Select different package from the Select Packaged Components page of the Deploy wizard).
6. Review and complete the deployment.
7. The newly deployed packaged component version is displayed on the Deployments page and the previous packaged component version is removed from the list.