Skip to main content

Verify blue/green deployment compatibility

Before starting a blue/green deployment, you must verify that the changes between the application configurations are compatible with a blue/green deployment. For information about compatible changes, see Blue/green deployment compatible changes.

Guidewire provides tools that compare the source and target applications and report whether the changes are compatible with a blue/green deployment. You can use one of the following:

Note:

If your changes aren't compatible, don't run a blue/green deployment.

Build management job​

  1. In Guidewire Home, select the star system (physical star system) containing the application to deploy.

  2. Go to Planets.

  3. Select Build management to go to the TeamCity console.

  4. Expand the application to view its tasks.

  5. Select the Verify Blue/Green Compatible task, then select Run.

  6. In the Run Custom Build dialog, set the task parameters.

    1. On the Parameters tab, set the following:

      ParameterDescription
      password

      username      		The username and password for the application unrestricted user (such as su), used to log into the blue server.
      verify_config_blue_serverThe URL of the blue server. You can find this in Guidewire Home. Navigate to the planet containing the server configuration, then under Applications and add-ons select InsuranceSuite. View the URL at the bottom of the application tile.

    2. On the Changes tab, select the branch containing your changes (this is the green branch).

  7. Select Run Build. Wait for the build to complete.

  8. Select the completed build, then select Build log.

  9. Expand the log line Step 3/3: Run verify config against blue server and review its output.

    • If the changes are compatible, the following line appears at the end of the step:
      Local server configuration is compatible with the current configuration. A rolling or blue/green upgrade is allowed.
    • If the changes aren't compatible, then you'll see more details about the incompatible changes. In this case, a blue/green deployment isn't allowed.

Command prompt tool​

Guidewire provides a command prompt build tool to use in determining if the source and target application configurations are sufficiently compatible to support the blue/green deployment process. To use this tool, run the following command from a command prompt on any cluster member.

system_tools -verifyconfig filepath

This tool compares the local server configuration with the configuration of the remote cluster. The filepath parameter defines the path to the local WAR/EAR file that contains the PolicyCenter application, pc.war, for example.

The tool provides an on-screen report that contains information about the feasibility of the deployment changes for the server members in the cluster:

  • Source and target configurations are incompatible

    If the source and target configurations are incompatible, Guidewire requires a full deployment. You can't use blue/green deployment to deploy the target configuration. If a blue/green deployment of the cluster isn't possible, the command lists the incompatible or missing files.

  • Source and target configurations are identical

    If the source and target configurations are identical, no deployment is necessary.

  • Source and target configurations are compatible

    If the source and target configurations are compatible, you can use blue/green deployment to deploy these changes.

Example use of verifyconfig​

The system_tools verfyconfig command provides the means to determine if the source and target application configurations are identical or sufficiently different as to require a database upgrade. This command uses the following syntax:

system_tools -verifyconfig filepath -user user -password password -server server

The command options have the following meanings.

-filepath

(Required) Fully qualified path to the local WAR/EAR file that contains the PolicyCenter application.

-password

(Required) Password to use to connect to the server that contains the local WAR/EAR file.

-server

URL of the server that contains the local WAR/EAR file.

-user

User that matches the supplied password.

A complete command example looks like the following:

system_tools -verifyconfig P:\PC\dist\wars\TomcatDbcp\pc.war
  -server http://localhost:8081/pc -user su -password gw
On this page