IBM BPM, V8.0.1, All platforms > Get started with IBM BPM > Key concepts > Versioning
Versioning process applications
Versioning provides the ability for the runtime environment to identify snapshots in the lifecycle of a process application, and to be able to concurrently run multiple snapshots on a process server.
To understand how process applications are versioned, it is important to remember that a process application is a container that holds various artifacts used in or by the process application (for example, process models or BPDs, toolkit references, services, tracks, or monitor models). Any versioning is done at this container level, not at the level of the individual artifacts. For process applications, that means that versioning happens when you take a snapshot.
You can compare snapshots to determine differences between the versions.
For example, if a developer fixed a problem with a service and took a snapshot of its containing process application or toolkit at that point, and then a different developer made several additional changes to the same service and took a new snapshot, the project manager can compare the two snapshots to determine which changes were made when and by whom. If the project manager decided that the additional changes to the service were not worthwhile, the project manager can revert to the snapshot of the original fix.
You can run different versions (snapshots) of a process application concurrently on a server; when install a new snapshot, either remove the original or leave it running.
Version context
Each snapshot has unique metadata to identify the version (referred to as version context).
You assign that identifier, but IBM recommends using a three-digit numeric version system in the format <major>.<minor>.<service>. See the topics about naming conventions for a more detailed description of this versioning scheme.
IBM BPM assigns a global namespace for each process application. The global namespace is specifically either the process application's tip or a particular process application snapshot. The version name used by the server cannot be longer than seven characters, so the assigned name is an acronym that uses characters from the snapshot name that you assigned. Snapshot acronyms areidentical to their snapshot names if the snapshot names conform to the recommended IBM VRM style and are not more that seven characters.
For example, a snapshot name of 1.0.0 will have an acronym of 1.0.0, and a snapshot name of 10.3.0 will have the acronym of 10.3.0. The snapshot acronym will be guaranteed to be unique within the context of the process application within the scope of the Process Center server. For that reason, you cannot edit the snapshot acronym.
Versioning considerations for process applications in multiple clusters
You can install the same version of a process application to multiple clusters within the same cell. To differentiate among these multiple installations of the same version of the process application, create a snapshot for each installation and include a cell-unique ID in the snapshot name (for example, v1.0_cell1_1 and v1.0_cell1_2). Each snapshot is a new version of the process application (from a pure lifecycle management perspective), but the content and function are the same.
When install a process application in a cluster, an automatic synchronization of the nodes is performed.
Versioning considerations for Process Designer toolkits
Remember that process application snapshots are typically taken when you are ready to test or install. Toolkit snapshots, however, are typically taken when you are ready for that toolkit to be used by process applications. Afterward, if you want to update the toolkit, you must take another snapshot of "tip" when you are ready, and then the owners of process applications and toolkits can decide whether they want to move up to the new snapshot.
Related concepts:
Process applications: Overview
Related information:
Manage snapshots