Supported changes during a rolling update

Guidewire permits changes to the following files, file types, and PolicyCenter installation folders during a rolling upgrade of the individual members of a cluster.

File or file path	Safe actions
configuration > config > config.xml	It is safe to change the value of a configuration parameter that Guidewire designates as possible to vary on different servers in the same environment. Guidewire lists these parameters as Set for Environment: Yes in the parameter description.
configuration > config > database-config.xml	It is safe to change the value of attribute `useoraclestatspreferences` (from `false` to `true` or `true` to `false`) during a rolling upgrade. However, if you reset the value of this attribute from `true` to `false`, you must also perform manual steps to complete the process.
configuration > config > extensions > entity	It is possible to make certain, very narrow, changes to element attributes in entity definition files (.eti, .eix, *.etx) in a rolling upgrade.
configuration > config > import	It is safe for the import directory to differ across individual PolicyCenter instances, as long as the database is not empty on server startup. This is because the import directory contains files that PolicyCenter imports by default on server startup into an empty database.
configuration > config > Integration	It is generally safe to add, delete, or modify entries in the listed file types in the following directories and their sub-directories during a rolling upgrade: Integration > apis .swagger.yaml published-apis.yaml versions.json Integration > filters .gql Integration > mappings .mapping.json Integration > schemas .schema.json versions.json Integration > updaters *.updater.json Note: Guidewire generates the versons.json files if you run `gwb updateReleasedSchemaVersion` at a command prompt.
configuration > config > Localizations	It is safe to add, delete, or modify any of the display keys in the various display_`languageCode`.properties files. IMPORTANT It is not safe to make changes to either language.xml or localization_`localeCode`.xml as these files must remain consistent across all cluster members.
configuration > config > Page Configuration	It is safe to add or a delete a PCF or to modify an existing PCF.
configuration > config > Plugins	It is safe to modify a .gwp file in the root plugin directory, including pointing to a new implementation class. Guidewire does not permit the following with respect to plugins in a rolling upgrade: Modifications to non-distributed, startable plugins Modifications to files in the plugins/Gosu or plugins/shared directories Changes to plugin implementations can cause individual PolicyCenter instances to have different versions of an object. Thus, it is possible that PolicyCenter instances running the source configuration to consider objects create or updated on the target configuration to be invalid.
configuration > config > resources > productmodel	It is only safe to make changes to specific product model pattern types, as well as to very narrow changes to those types.
configuration > config > Rule Sets	It is safe to perform the following operations on PolicyCenter Gosu rules: Add a new rule Modify an existing rule, including enabling or disabling the rule Rename a rule, which is actually deleting a rule and adding the rule under a different name Changes to validation rules can cause individual PolicyCenter instances to have different versions of an object. Thus, it is possible that PolicyCenter instances running the source configuration. to consider the objects created or updated on the target configuration to be invalid.
configuration > config > servlet	It is generally safe to modify existing Gosu servlet implementations in a rolling upgrade. However, it is not permissible to modify config/servlet/servlets.xml in a rolling upgrade. IMPORTANT Guidewire recommends that you undertake thorough testing after making a change to a Gosu servlet implementation to verify that all product integrations continue to work as intended.
configuration > config > templates	It is safe to make modifications to note, email, and document templates in the following directories as the impact of a change to a template affects only that template. config/resources/doctemplates config/resources/emailtemplates config/resources/notetemplates
configuration > config > typelists	It is generally safe to add typecodes to an existing typelist or to add an entirely new typelist. Also, it is safe to edit the typelist description or change its category. Note: If you add a typelist, the typelist shows on servers running the target (new) configuration only. On servers running the source (old) configuration, the typelist shows as blank.
configuration > gsrc	It is generally safe to add new Gosu classes during a rolling upgrade. However, it is unsafe to modify or remove a Gosu class in a rolling upgrade.

Web services

It is generally safe to make changes to web services. However, a change to an existing web service has the potential to break integration with a third-party product.

IMPORTANT Guidewire recommends that you undertake thorough testing after making changes to web services configuration to verify that all product integrations continue to work as intended.