IBM BPM, V8.0.1, All platforms > Get started with IBM BPM > Key concepts

Versioning

The lifecycle of a process application begins with the creation of the process application and continues through a cycle of updating, deploying, co-deploying, undeploying, and archiving the process application. Versioning is a mechanism used to manage the lifecycle of the process application by uniquely identifying the individual versions of the process application.

The way that versioning works in IBM BPM depends on what you are deploying–a process application, deployed from the repository in IBM Process Center, or an enterprise application deployed directly from IBM Integration Designer.

The process applications and toolkits that you deploy to a runtime environment from the Process Center are, by default, versioned. For enterprise applications, you can choose to version modules and libraries in IBM Integration Designer.

In addition, you can create versions of a human task or state machine, so that multiple versions of the task or state machine can coexist in the runtime environment.

See

1. Versioning process applications
   
2. Versioning modules and libraries
   
3. Modules and libraries associated with process applications or toolkits
   
4. Naming conventions
   
5. Version-aware bindings
   
6. Version-aware dynamic invocation
   
7. Versioning of BPEL processes
   
8. Deploying process applications with Java modules and projects
   
9. Deploying process applications with business rules and selectors
   

Key concepts