Deploying Processes

If environments are enabled in your account, review the Working with Environments section to learn how to deploy process versions to an environment.

After you have tested a Process and it is ready to be used in production mode, the next phase in the integration life cycle is to deploy the Process to an Atom. There are two key steps to perform when deploying a new Process to an Atom:

1. Attach one or more Atoms to the Process
2. Deploy the latest version of the Process

You will typically attach only one Atom to a Process, although technically multiple Atoms can be attached to the same Process.

Attaching Atoms to a Process

If this is the initial deployment, first you must attach an Atom to the Process. You need to do this only once, unless you later decide to attach a different Atom or additional Atoms to the Process.

To Attach an Atom to a Process

1. On the Deploy menu select the Process from the Processes list.
2. Click the Attachments tab.
3. In the Unattached Atoms list, select the Atom(s) that you want to attach to the Process.
4. Click the Attach selected atoms button to move the Atom(s) to the Attached Atoms list.
   A connection audit will be performed during this step only if versions of the Process have been previously deployed. See Understanding Connection Licenses for more details.

To Detach an Atom from a Process

1. On the Deploy menu select the Process from the Processes list.
2. Click the Attachments tab.
3. In the Attached Atoms list, select the Atom(s) that you want to detach from the Process.
4. Click the Detach selected atoms button to move the Atom(s) to the Unattached Atoms list.
   This means that the Process is no longer deployed and it is disabled so that it cannot be executed manually or automated with a schedule.

Deploying Process Versions

After attaching an Atom to a Process you need to deploy a version of the Process. This allows the attached Atom(s) to download the latest Process version.

After the initial deployment, any revisions to a Process or its child components need to be deployed before they take effect. If any of the Process components have been revised since the latest version was deployed, the Process appears in bold in the Processes list.

To see the full list of deployed Processes per Atom and to configure Atom-level extensions, see the Manage menu's Atom Management page.

To Deploy a Process Version

1. On the Deploy menu select the Process from the Processes list.
2. Click the Deployments tab.
3. Do one of the following:
   If you want to deploy the most recent revision of the Process as a new version, click the Deploy Latest Revision of Process button.
   If you want to deploy an earlier version of the Process, click the gear icon next to the version you want and select Re-deploy this Version.
   The Deployment Confirmation dialog opens.
4. Type a note.
   It is helpful to add a note so that later you can determine which changes were applied to the Process version.
5. Click OK.
   If this is a new Process deployment and you have already attached an Atom, the number of unique connections in the Process will be audited against your license count. This is to ensure you do not exceed the number of purchased connections in your account. After a successful deployment, the new deployment version appears in the Process Deployment History list and the Atom downloads the latest Process configuration.

Deploying Processes That Include Process Calls

If your integration Process includes Process Call steps, you need to deploy only the "parent" Process, not the "child" Processes that the parent calls. During the deployment, all of the Process component dependencies including other Processes are gathered. The "child" Process configuration is bundled with the parent Process within the single deployment. Whenever you make a change to a child Process you need to re-deploy its parent Process. After you deploy the parent Process, the child Processes will still appear in the Processes list in bold indicating that they have been revised since the latest version of the parent Process was deployed.

However, if you need the ability to manually execute any of the child Processes from the Manage menu's Atom Management page, you will need to deploy them individually along with the parent Process. If you make any changes, you need to deploy both the parent and child Processes.