Perform a rolling upgrade in a production environment

Before you begin

Before performing a rolling upgrade in a production environment, ensure that you have completed all steps in Perform a rolling upgrade in a test environment.

Procedure

  1. In Guidewire Studio, open file database-config.xml and verify that the <database> element autoupgrade attribute is set to manual (or non-existent).
    If the attribute is missing, the default value for this attribute is manual. The value cannot be full.
  2. In Studio, open file extensions.properties (in configuration > config > Extensions) and increment the version number.
    Guidewire require that you increment the version number in a development or test environment, otherwise the upgrade fails.
  3. On any instance in the PolicyCenter production cluster, navigate to the Server Tools Upgrade and Versions screen.
    1. Click Start Rolling Upgrade.
    2. Verify the checklist of upgrade prerequisites.
    3. Click Start Rolling Upgrade.
      This action sets a flag in the PolicyCenter database that indicates a rolling upgrade is in progress.
  4. Navigate to the Server Tools Cluster Members screen on any server instance.
    1. For the instance that you want to shutdown, click Start Planned Shutdown in the Actions column.
    2. Set the appropriate shutdown parameters in the Schedule Planned Shutdown screen.
    3. Click Schedule Shutdown.
      This action schedules a shutdown of the specified instance. All users logged into this PolicyCenter instance see an on-screen message indicating that a planned shutdown is in progress. After the scheduled period of time elapses, there are no more user connections to this production instance.
    4. Manually shut down the application server that you scheduled for shutdown..
  5. Deploy the target PolicyCenter build to the production instance that you shut down.
  6. Bring the instance with the target build back up.
  7. Perform acceptance testing on the production instances that use the target build to determine if there are any major issues with running the source and target builds in the same cluster.
    If testing indicates that there are no major issues with running both build types simultaneously in the production cluster, continue to the next step. If there are issues, repeat the previous steps until you have upgraded all the production instances with the target build.
  8. Perform another round of acceptance testing.
    If testing indicates that there are no major issues with the target build running on all production instances, continue to the next step.
  9. Navigate to the Server Tools Upgrade and Versions screen of any instance in the PolicyCenter production cluster.
  10. Click Rolling Upgrade Complete.
    This action clears the upgrade flag indicating that a rolling upgrade is in progress. The rolling upgrade process is now complete.
  11. Run Product Model Pattern Activation batch processing to activate the newly added product model patterns.
    Running this batch process makes active all product model patterns that you added in the rolling upgrade. See Product Model Pattern Activation batch process for more information.
    Important: Restarting any node in the cluster after you complete the rolling upgrade (after you click Rolling Upgrade Complete) automatically triggers the activation of the added product model patterns. Guidewire does not recommend that you activate the product model patterns in this manner.
  12. Perform another round of acceptance testing to ensure that there are no issues with the upgrade changes.