Naming conventions
A naming convention is used to differentiate the various versions of a process application as it moves through the lifecycle of updating, deploying, co-deploying, undeploying, and archiving.
This section provides you with the conventions that are used to uniquely identify versions of a process application.
A version context is a combination of acronyms that
uniquely describes a process application or toolkit. Each type of
acronym has a naming convention. The acronym is limited to a maximum
length of seven characters from the [A-Z0-9_] character set, except
for the snapshot acronym, which can also include a period.
A business process definition in a process application is typically
identified by the process application name acronym, the snapshot acronym,
and the name of the business process definition. Choose unique names
for your business process definitions whenever possible. When duplicate
names exist, you might encounter the following problems:
- You might be unable to expose the business process definitions as web services without some form of mediation.
- You might be unable to invoke a business process definition created in IBM Process Designer from a BPEL process created in IBM Integration Designer.
The version context varies, depending on how the process application is deployed.