On the Process Server, you can deploy the snapshot of a
process application. The process application snapshot acronym is used
to uniquely identify the version.
For process application snapshot deployments, the version context
is a combination of the following items:
- Process application name acronym
- Process application snapshot acronym
Resources should be uniquely named and identified externally using
the version context. The following table shows an example of names
that are uniquely identified:
Table 1. Example of names and acronyms| Type of name |
Example |
|---|
| Process application name |
Process Application 1 |
| Process application name acronym |
PA1 |
| Process application snapshot |
1.0.0 |
| Process application snapshot acronym |
1.0.0 |
A resource, such as a module or library, has the version context
as part of its identify.
The following table shows an example of two modules and how the
associated EAR files include the version context:
Table 2. SCA
modules and version-aware EAR files| SCA module name |
Version-aware name |
Version-aware EAR/application name |
|---|
| M1 |
PA1-1.0.0-M1 |
PA1-1.0.0-M1.ear |
| M2 |
PA1-1.0.0-M2 |
PA1-1.0.0-M2.ear |
The following table shows an example of two process-application-scoped
libraries and how the associated JAR files include the version context:
Table 3. Process-application-scoped libraries and version-aware JAR
files| SCA process-application-scoped library name |
Version-aware name |
Version-aware JAR name |
|---|
| Lib1 |
PA1-1.0.0-Lib1 |
PA1-1.0.0-Lib1.jar |
| Lib2 |
PA1-1.0.0-Lib2 |
PA1-1.0.0-Lib2.jar |