Environment parameters

Set to true to have address verification failures shown as errors instead of warnings. This parameter has no effect if EnableAddressVerification is set to false.

Default: false

See also

• EnableAddressVerification

Whether PolicyCenter can be started in development mode while there are domain graph errors.

Set this parameter to true if you wish to do development work before fixing domain graph errors.

This parameter is ignored when running in production mode. PolicyCenter cannot be started in production mode while there are domain graph errors. This is true even if archiving has been disabled.

Default: false

Set this value to the name of the plugin that you intend to use to manage encryption. This plugin implements the IEncryption plugin interface. Typically, a Guidewire installation has only a single implementation of an encryption plugin interface. However, you can decide to implement a different encryption algorithm using a different implementation of the encryption interface as part of an upgrade process. In this case, you must retain your old encryption plugin implementation in order to support the upgrade and any archived items that use the previous implementation.

To support multiple implementations of the encryption plugin, PolicyCenter provides the CurrentEncryptionPlugin configuration parameter. Set this configuration parameter to the value of the EncryptionIdentifier property of the encryption plugin currently in use.

• If you do not provide a value for this configuration parameter or if the value is an empty string, data is unencrypted.
• If you provide a value for this configuration parameter that does not match the value of the EncryptionIdentifier property of an encryption plugin implementation, the server cannot start.
• If you create multiple implementations of the encryption plugin interface, you must name each plugin implementation individually and uniquely. The application retrieves the name of the plugin from the EncryptionIdentifier property.

Default: None

See also

• For information on the how to configure your database to support encryption, see Encryption integration.
• For information on the steps to take if you upgrade your installation and change your encryption algorithm, see Changing your encryption algorithm.
• For information on using the Plugins Registry editor, see Using the Plugins Registry editor.

Whether to use the now-deprecated event logic that had previously been available.

Default: false

Set this value to true to enable address verification warnings. Address verification checks that all the fields match each other based on the zone data.

This parameter works in concert with the AddressVerificationFailureAsError parameter to show either a warning or an error, as follows:

• If EnableAddressVerification is true and AddressVerificationFailureAsError is false, PolicyCenter shows a warning message if verification against zone data fails.
• If EnableAddressVerification is true and AddressVerificationFailureAsError is true, PolicyCenter shows an error message if verification against zone data fails.
• If EnableAddressVerification is false, PolicyCenter does not verify the address based on zone data.

Default: false

See also

• AddressVerificationFailureAsError

Make internal debug tools available to developers.

Default: false

Set for server: Yes

This prefix must not exceed 9 characters in length. Use only letters and numbers. Do not use space characters, colon characters, or any other characters that other applications might process or escape specially.

Required: Yes

Default: pcext

The number of key identifiers (as a block) that the server obtains from the database with each request. This integer value must be 0 or greater.

As you create a new PolicyCenter object such as a Policy, PolicyCenter assigns it a key, or unique public identifier. To ensure that keys are unique, the server requests an available key from the PolicyCenter database. If every server in a cluster queried the database each time it needed a single key, performance would degrade.

Instead, use this configuration parameter to obtain a block of keys with a single request. For example, a server can reserve a block of 100 keys, and then assign each key without needing to query the database again. The server continues to assign the keys from a block until it uses all keys in that block.

In the base configuration, Guidewire sets the default value of this parameter to 100. For small test environments, this value is likely large enough to prevent frequent database queries for more keys. It is also small enough to not waste too many keys that the server reserves but never uses.

However, for large production systems, the value of this parameter needs to be much larger. For example, for a production InsuranceSuite database with 20,000 concurrent users, try setting this value to 2000.

As the server shuts down, it discards keys that are allocated but are unused. As keys are 64-bit integers, wasting a few keys is not an issue.

Default: 100

How often the PolicyCenter server logs memory usage information, in minutes. This is often useful for identifying memory problems.

To disable the memory monitor, do one of the following:

• Set this parameter to 0.
• Remove this parameter from config.xml.

Default: 0

The prefix to use for public IDs generated by the application. Generated public IDs are of the form prefix:id. This id is the actual entity ID. Guidewire strongly recommends that you set this parameter to different values in production and test environments to allow for the clean import and export of data between applications.

This PublicIDPrefix must not exceed 9 characters in length. Use only letters and numbers. Do not use space characters, colon characters, or any other characters that other applications might process or escape specially. Do not specify a two-character value. Guidewire reserves for itself all public IDs that start with a two-character ID and then a colon.

Required: Yes

Default: None

Indicates whether resource are mutable (modifiable) on this server. If you connect Studio to a remote server (on which this parameter set to true), then Studio pushes resource changes to the remote server as you save local changes. Guidewire strongly recommends that you set this value to false on a production server to prevent changes to the configuration resources directory.

See also RetainDebugInfo.

Studio Read-only Mode

If you set the value of ResourcesMutable to false in config.xml on a particular application server and then restart the associated Studio, that Studio becomes effectively read-only. In this context, read-only means:

• It is not possible to modify a Studio-managed resource. This applies, for example, to files that you open in the Gosu or Rules editor.
• If it is possible to modify a Studio-managed resource, it is not possible to save any modification you make to that resource. This applies, for example, to files that you open in the PCF editor.

To indicate the read-only status:

• Studio displays a padlock icon on the status bar that is visible only if Studio is in read-only mode. If you click the icon, Studio displays a modal message box indicating the reason why it is in read-only mode.
• Studio disables the Save button any time that Studio is in read-only mode.
• Studio changes the Save button tooltip in read-only mode to display the reason that save is not active in this mode. This is the same message that Studio shows if you click the padlock icon on the status bar.

Setting the value of configuration parameter ClusteringEnabled to true provides the same Studio read-only behavior.

Default: true

See also

• ClusteringEnabled

Whether the production server retains debugging information. This parameter facilitates debugging from Studio without a type system refresh.

• If set to true, PolicyCenter does not clear debug information after compilation.
• If set to false, the server does not retain sufficient debugging information to enable debugging. As a production server does not recompile types, it is not possible to regenerate any debugging information.

Default: false

See also

• ResourcesMutable

Controls whether PolicyCenter uses the pre-PolicyCenter 4.0 behavior for configuring data types, through the use of the fieldvalidators.xml file.

• Set this value to false to preserve the existing behavior. This is useful for existing installations that are upgrading but want to preserve the existing functionality.
• Set this value to true to implement the new behavior. This is use for new PolicyCenter installations that want to implement the new behavior.

StrictDataTypes = true

If you set the StrictDataTypes value to true, then PolicyCenter:

• Does not permit decimal values to exceed the scale required by the data type. The setter throws a gw.datatype.DataTypeException if the scale is greater than that allowed by the data type. You are responsible for rounding the value, if necessary.
• Validates field validator formats in both the PolicyCenter user interface and in the field setter.
• Validates numeric range constraints in both the PolicyCenter user interface and in the field setter.

StrictDataTypes = false

If you set the StrictDataTypes value to false, then PolicyCenter:

• Auto-rounds decimal values to the appropriate scale, using the RoundHalfUp method. For example, setting the value 5.045 on a field with a scale of 2 sets the value to 5.05.
• Validates field validator formats in the interface but not at the setter level. For example, PolicyCenter does not permit a field with a validator format of [0-9]{3}-[0-9]{2}-[0-9]{4} to have the value 123-45-A123 in the interface. It is possible, however, to set a field to that value in Gosu code, for example. This enables you to bypass the validation set in the interface.
• Validates numeric range constraints in the interface, but not at the setter level. For example, Guidewire does not allow a field with a maximum value of 100 to have the value 200 in the interface. However, you can set the field to this value in Gosu rules, for example. This enables you to bypass the validation set in the interface.

Default: true

The threshold year value for determining whether to resolve a two-digit year to the earlier or later century.

Default: 50

Determines whether the Gosu compiler generates errors if it detects unreachable code or missing return statements.

Default: true

PolicyCenter does not evaluate permissions for the unrestricted user. As a consequence of PolicyCenter bypassing permission checking, the unrestricted user has access to the entire PolicyCenter application. Thus, an unrestricted user behaves as if it has all permissions.

In the base configuration, PolicyCenter defines user su user as the unrestricted user. To set the unrestricted user to a different user, set the value of the UnrestrictedUserName parameter to that user’s login name.

Default: su

Deprecated. This parameter has no effect in PolicyCenter.

Default: false

A value of true indicates that the Gosu compiler generates warnings if it determines that an implicit coercion is occurring in a program.

Default: true

Specifies the location of the Web resources directory under the root of the Tomcat configuration directory.

Default: resources