7.4. Process versioning with Orchestra
Prev | Chapter 7. Advanced features | Next

## 7.4. Process versioning with Orchestra

Since Orchestra 4.6, versioning of process is supported.

This feature eases deployment of new versions of a process in an environment with long-running instances.

### 7.4.1. Process versions

To deploy a new version of a process, just deploy a new process with the same name and namespace as an already deployed process. The version is automatically incremented.

Only one version of a process can be active. If multiple versions are deployed:

- when a version becomes active, the previously active version becomes retired.

  In the SOA console you can set a process version as active by clicking on the button in the process view

- when the active version is undeployed, the highest retired version becomes active.

  In the SOA console you can set a process version as retired by clicking on the button in the process view

- when a new version is deployed, it becomes automatically active.

Prev | Up | Next
7.3.2. How to use camel context instead of HTTP for Web Service interactions ? | Home | 7.4.2. Restrictions on versioning