The Upgrade and Versions screen

The Server Tools Upgrade and Versions screen displays information about any upgrade process that is run on this server.

Note: Some functionality on the Upgrade and Versions screens is visible only if configuration parameter ClusteringEnabled is set to true in config.xml.

Guidewire divides this screen into the following areas:

A row of buttons that control upgrade functionality, not all of which are visible at all times.
A summary table that contains upgrade information for this particular application server.

The upgrade and versions screen summary table

The upgrade summary table contains the following information.

Version	Version information for each application installation. PolicyCenter provides the version information in the following format: Guidewire build.customer build (n,n,n,n,n) These numbers have the following meaning: Guidewire build – Guidewire application version, 10.1.2, for example. Customer build– Custom label, defined in file customer-version.properties. If not defined, this field is empty. (n,n,n,n,n) – Numbers that have the following meaning: Platform major version Platform minor version Application major version Application minor version Data model version
Status	Status of each upgrade, for example, new schema or upgraded.
Type	Type of each upgrade, for example, install or full.
Start Time	Date and time of the beginning of the upgrade.
End Time	Date and time of the completion of the upgrade.
Duration	Length of time that the upgrade process took. Time is shown as both the total number of seconds involved and the time for just the database upgrade portion of the upgrade.
Deferred Upgrade Tasks Status	Execution status of the Deferred Upgrade Tasks batch process.
View Details	Click the View icon to open a pop-up from which you can view the same reports contained in the UpgradeInfo.zip file.
Download Details	Click the Download arrow to download an UpgradeInfo.zip file that contains a set of HTML reports describing various aspects of the upgrade process.
Remove Detail Data	Click the trash can icon to remove this row of data.

The upgrade and versions screen buttons

The top of the Upgrade and Versions screen contains a number of buttons that initiate specific upgrade actions. Not all buttons are visible at all times. Individual buttons become visible depending on various aspects of the cluster and its members.

The Upgrade and Versions screen contains the following buttons that initiate upgrade-related actions.

Refresh	Click to update the information on this screen.
Start Rolling Upgrade	Click to open a Start Rolling Upgrade screen from which you can initiate a rolling upgrade for this cluster. Before you can start the upgrade, you must actively affirm that you have taken certain pre-upgrade steps by selecting the check box next to each pre-upgrade step.
Rolling Upgrade Complete	Click to notify PolicyCenter that the in-progress rolling upgrade is now complete. The rolling upgrade is complete after you have restarted all cluster members with the new target configuration. Without this notification, PolicyCenter prevents cluster members with the old configuration from starting up again.
Initiate Backout	Click to attempt to stop an in-progress rolling upgrade and initiate a backout of the new target configuration. The attempt to stop and backout the rolling upgrade may or may not succeed, depending at what point in the rolling upgrade that the request to stop occurs. If a backout of the rolling upgrade is possible, PolicyCenter opens a series of confirmation screens to assist you in correcting issues related to backing out the new configuration.
Start Full Upgrade	Click to open a Start Full Upgrade screen. Clicking Yes on this screen sets a flag in the database that you intend to start a full database upgrade. You must set this database flag before deploying your new configuration to members of the cluster. If you do not set this flag, PolicyCenter refuses to start and refuses to alter the database. After you complete the full upgrade, PolicyCenter deletes this flag from the database. You must set the flag again before starting a new full upgrade. Note: You can also initiate a full PolicyCenter upgrade using the administrative system_toools command option `-startfullupgrade`.
Cancel Full Upgrade	Click to attempt to cancel an in-progress full upgrade. If PolicyCenter determines that it is safe to cancel the upgrade, it does so.