Understanding Guidewire software versioning

Guidewire application versioning is a way to label a particular snapshot of a Guidewire application. It is a string label that Guidewire applies to its software. You see this version number primarily in Server Tools, in the Cluster Members screen and the Upgrade and Versions screens.

Guidewire manages software versioning through internal classes that provide the following information:

  • Guidewire application name and version
  • Guidewire module name and version

PolicyCenter writes version information to the application log at PolicyCenter start.

Application version numbering

Both the Server Tools Cluster Members screen and the Upgrade and Versions screens show the PolicyCenter application version as the following sequence of numbers:
  • A.B (a,b,c,d,e)

These numbers have the following meaning:

Version #

Meaning

A

Guidewire application version plus the application release build version, for example, 9.0.0.905.

B

Custom version label

a

Platform major version

b

Platform minor version

c

Application major version

d

Application minor version

e

Data model version number
The following example illustrates these concepts.
  • 9.0.0.905.20161017 (6,22,11,45,175)

Notice that:

  • 9.0.0.905 is the application version number (9.0.0) plus the application release build version number (905).
  • 20161017 is a custom label that you define in file customer-version.properties. In this case, the label indicates the date of a PolicyCenter configuration upgrade. If not defined, this field is empty.
  • 175 is an upgrade version number that you define in file extensions.properties.
Warning: In a production environment, Guidewire requires that you increment the data model version number whenever you make changes to the data model, before you restart the application server. Otherwise, unpredictable results can occur. Use of the extensions.properties file in a development environment is optional.