Configuration parameter behaviors

The configuration parameters in config.xml may implement the following behaviors:

Behavior	Summary	More information
Required	You must supply a value.	Required
Set for server	You can set a different value for different servers in a cluster.	Set for server
Dynamic	You can change the parameter value on a running server.	Dynamic
Permanent	Once you start the server, you cannot change the parameter value.	Permanent
Semi-permanent	Once you start the server, you can change the parameter value only in limited ways.	Semi-permanent
Nullable	The parameter value is allowed to be null.	Nullable

Required

Guidewire designates certain configuration parameters as required, which means that you must supply a value for that parameter.

Configuration parameters that are required have Required: Yes in their parameter descriptions.

Set for server

Guidewire designates certain configuration parameters as possible for the parameter value to vary on different servers in a cluster.

Configuration parameters that can be set per server have Set for server: Yes in their parameter descriptions.

Do not add a configuration parameter that is not designated as Set for server: Yes to a local configuration file. If you do so, PolicyCenter prints a warning message in the configuration log file when the application server starts. For example:

WARN Illegal parameter specified in a local config file (will be ignored): XXXXXXX

Note: For information on server environments in Guidewire PolicyCenter, see Understanding the PolicyCenter server environment.

Dynamic

Guidewire designates certain configuration parameters as dynamic. This indicates that Guidewire permits you to change this value on a running application server through management integration. The discussion of configuration parameters indicates this by adding Dynamic: Yes to the parameter description.

See Management integration.

Permanent

Guidewire specifies several configuration parameter values as permanent. After you set the value of a permanent parameter and start the production application server, you cannot change the parameter’s value. An example is the DefaultApplicationLocale configuration parameter. If you set the value of this parameter on a production server and then start the server, you are unable to change the value thereafter.

Guidewire stores these values in the database and checks the value at server start up. If an application server value does not match a database value, PolicyCenter throws an error.

Semi-permanent

Guidewire specifies a limited number of configuration parameter values as semi-permanent. After you set the value of a semi-permanent parameter and start the production application server, you can change the value of the parameter only once to a specified value.

Nullable

The parameter value is allowed to be null.