Business Data Project Versioning

BOMs use the version number of their parent Business Data project. Correct version management of Business Data projects is essential when upgrading BOMs or process applications that reference them.

Version numbers are set on the Properties > Lifecycle dialog of the Business Data project.

The default format for a Business Data project's version number is:

major.minor.micro.[qualifier]

where:

  • major defines the major version number of the project.
  • minor.micro.[qualifier] defines the minor version number of the project.
  • qualifier is an optional parameter that, if used, will be replaced by the timestamp value in the Properties > Lifecycle > Build Information > Build Version field. Build Version is a timestamp that is updated whenever the project is updated.
    Note: If you import the project into a different major version of Business Studio (for example, from a 3.x version to a 4.x version) the project is updated automatically and the Build Version timestamp is changed, even if you make no changes to the project.
    Note: Process projects also use a qualifier in their version number, but this is handled differently. On a process project version number, qualifier is replaced by a timestamp when the DAA is created. Importing a process project into a different major version of Business Studio does not change the qualifier timestamp.
The current version number is used when the Business Data project is deployed, and is visible:
  • in TIBCO Administrator, as the business data application's Application Template Version.
  • (if the project contains a case data model) in the Openspace Data Admin gadget, as the case model's version number.

If a process project references a class in a local or global BOM in a Business Data project, the version number of the Business Data project is used in the reference when the DAA for the process project is generated. This creates an exact-match application dependency from the process application to that version of the BDS application.

Consequently, when you upgrade a Business Data project (either by modifying a local or global BOM, or by importing the project into a new major version of Business Studio), you should also upgrade any existing process application that references that Business Data project - even if that process application makes no use of any updated parts of a BOM. Keeping BDS applications and dependent process applications in step in this way facilitates subsequent deployments or undeployments of either application.

See Also

"Case Data Model Versioning" in the TIBCO ActiveMatrix® BPM Case Data User's Guide.