Waiting for engine...
Skip to main content

Deploy process operation (Legacy deployment, Deprecated)

You can use the deployProcess operation to copy a process deployment from one environment to another.

caution

The Deploy Process operation is a deprecated API and should no longer be used. Boomi recommends that you take advantage of the API functionality provided by the Deployed Package object instead. This change is to support the introduction of Packaged Component Deployments, which leverage the way Legacy account users deploy components to environments. For more information about Boomi's API object deprecation status, refer to the API deprecation and versioning policy topic.

Boomi encourages administrators of Legacy deployment accounts to take advantage of the new Packaged Components Deployment by upgrading their accounts. Learn more about the new Deployment workflow and Enabling Packaged Component Deployment for Legacy accounts. In the meantime, do not use the replacement API without first converting your Legacy account.

The deployProcess operation is limited to copying process deployments. To copy other component deployments, use the deployComponent operation.

For processes that contain Process Route components, the process routes and the subprocesses that they call are not copied as part of this operation. Because they are not dependent components, you must copy process routes and their subprocesses independently.

Parameters​

You can use the following parameters to perform the deployProcess operation:

  • deploymentId - The ID of the process deployment to copy.

    You can find this ID in the Process Deployment History table on the Deploy page.

  • environmentId - The ID of the deployment environment to copy the process deployment to.

    This ID can be found in the Environment Properties section of the Runtime Management page.

  • digest - The digest corresponds to a hash of the configurations for the components that are included in the deployment.

    This digest must match the deployment's digest in order for the deployment to be copied. A match ensures that the deployment you are intending to copy is actually copied. The digest can be retrieved by using the API's GET call for Deployment objects.

  • listenerStatus - (Optional, for listener processes only) Used to copy a listener process deployment in a specific state, either RUNNING or PAUSED.

By default, listener processes that do not exist in the target environment deploy in a running state. If the listener process exists in the target environment, it deploys in the same state as the existing process unless you include this parameter.

RESTish Implementation​

Send an HTTP POST with an empty request body to:

https://api.boomi.com/api/rest/v1/accountId/deployProcess/deploymentId/environmentId/digest?listenerStatus=listenerStatus

where:

  • accountId is the user's account ID

  • deploymentId is the ID of the process deployment to copy

  • environmentId is the ID of the environment to copy the deployment to

  • digest is the digest of the deployment's component configurations

  • listenerStatus is an optional parameter used to deploy a listener process in a specific state, either RUNNING or PAUSED.

If the platform processed the deploy request successfully, the response is true.

For a JSON response, send the request with the following HTTP header:

Accept: application/json

If the platform processed the deploy request successfully, the response is true.

On this Page