Ways to override configuration values

Guidewire provides the following mechanisms for overriding configuration values defined in file config.xml from a command prompt at server start up:
  • --systemProperty name=value
  • --configParam name=value
  • gw.config.paramName=value
You must supply the name (name) and value (value) of the property to change, for example:
  • gwb runServer --configParam OverrideJSONSchemaWarnings=on
  • gwb runServer --systemProperty OverrideJSONSchemaWarnings=on
  • gwb runServer -Dgw.config.OverrideJSONSchemaWarnings=on

If you use --systemProperty and --configParam to redefine the same configuration parameter at the same time, PolicyCenter uses the value set by --configParam.

These overrides work on the QuickStart (Jetty) application server only. Thus, you can only use these override in development or testing environments. It is not possible to use these overrides in a production environment. Also, if you attempt to override configuration parameters that Guidewire defines as permanent, or semi-permanent (one-way), the override will fail.

Important: If you are using external server configuration, do not use these configuration override mechanism.

Overriding parameters by environment

You can make the configuration override active in a single environment only. Set the environment from the command prompt as you start the application server using the following syntax:
  • env={dev|test|prod}
For example:
  • gwb runServer env=dev --systemProperty OverrideJSONSchemaWarnings=on