Rating Management parameters

Set this Boolean parameter to true if you want rate routines to be preloaded from the rate routines JAR file at system startup. This parameter also enables the Generate JAR File and Download JAR File buttons on the Rate Books screen.

If you enable this parameter, then you must also specify the location in the RateRoutinesJarFile parameter.

Default: false

See also

• Precompile rate routines JAR file

You can speed up rate table preloading by setting the parameter OverriddenTableArgsLabelSimple to true. (The RateBookPreloadEnabled parameter must also be true.)

When true, when viewing a rate routine on the Rate Routine screen, parameters in rate routine steps may appear as ellipses (...).

If true, enable Purge Rate Book Export Result batch processing.

Default: true

See also

• Purge Rate Book Export Result work queue

Enable the Purge Rating Worksheets batch process.

Default: false

See also

• Extract Rating Worksheets batch process

Default: 53

The time in seconds after which the rate book cache is rebuilt: all non-active rate books are refreshed and any rate books added after the last update are added to the cache.

Default: 307

Purge Rate Book Export Result batch processing removes from the PolicyCenter database RateBookExportResult Excel and XML files that have been around for more days than this parameter.

Default: 60

See also

• Purge Rate Book Export Result work queue

This parameter determines whether to load Rating Management components on system startup. If true, PolicyCenter loads all rate books and their associated rate routines and rate tables on system startup.

INFO Application.Rating.RateTableManagement Preloading all ratebooks

Default: true

See also

• Preload Rating Management components

When editing a long rate routine, you can edit the rate routine by section. A long rate routine has more steps than the value of the indexing threshold, the RateRoutineIndexingThreshold parameter.

Default: 150

See also

• Editing long rate routines

Specify the file system location of the rate routines JAR file. May be an absolute path or path relative to the web application root. For allowed locations, see Deploying non-OSGi Java classes and JAR files. Guidewire recommends that you deploy the JAR file in the following location:

modules/configuration/plugins/Gosu/lib/rateroutines.jar

For example, if you are running PolicyCenter under Apache Tomcat and the WAR file expands into <TOMCAT_HOME>/webapps/pc, where <TOMCAT_HOME> is the Tomcat root directory, then set RateRoutinesJarFile to webapps/pc/modules/configuration/plugins/Gosu/lib/rateroutines.jar.

If the directory does not exist, PolicyCenter will attempt to create it. If the file exists, it must be a valid JAR file. If the file does not exist, PolicyCenter will create it if EnableRateRoutinesJar is true. If the JAR does not exist at startup, PolicyCenter compiles all rate routines in the rate books returned by the RateBookPreloadPlugin to the JAR. To avoid this delay during startup, deploy the JAR file to the production system when you build PolicyCenter.

See also

• Precompile rate routines JAR file

Specify the location of the rate routines JAR file that is updated dynamically while PolicyCenter is running. If you specify this parameter, PolicyCenter modifies the file referred to by it whenever an update event happens. If you do not specify this parameter, PolicyCenter updates the file pointed to by RateRoutinesJarFile.

For allowed locations, see Deploying non-OSGi Java classes and JAR files. Guidewire recommends that you deploy the JAR file in the following location:

modules/configuration/plugins/Gosu/lib/rateroutines_update.jar

If the directory does not exist, PolicyCenter attempts to create it.

Modify the startup process

SET ROUTINES_JAR = %TOMCAT_HOME%\webapps\pc\modules\configuration\plugins\gosu\lib\rateroutines.jar
SET UPDATE_JAR=%TOMCAT_HOME%\webapps\pc\modules\configuration\plugins\gosu\lib\rateroutines_update.jar
IF EXIST %UPDATE_JAR% {
  del %ROUTINES_JAR%
  ren %UPDATE_JAR% %ROUTINES_JAR%
}
%TOMCAT_HOME%\bin\startup.bat

Provides guidance on the maximum number of concurrent operations on the rate table cache.

Default: 16

See also

• Improving performance of rate tables loaded in memory

Default: 53

The maximum number of rate tables that can be in the rate table cache. For no limit, set to -1. To disable rate table caching, set to 0.

The time in seconds after which the rate table cache is cleared.

Default: 307

The time in seconds after which the rate table definition cache is cleared.

Default: 601

See also

• Improving performance of rate tables loaded in memory

PolicyCenter determines whether to normalize a rate table if the table contains this many rows or more.

If the number of rows in the normalized table would exceed this limit, the table is automatically marked as non-normalizable. PolicyCenter stores the non-normalized version of the table.

Default: 10000

See also

• Rate table normalization configuration parameters

If the number of rows in the normalized table would exceed this threshold, the user is given the option to store a non-normalized version of the table.

Default: 1000

See also

• Rate table normalization configuration parameters

The Purge Rating Worksheets batch process uses this parameter as one factor in determining if a worksheet container can be purged. To be considered for purging, the worksheet container’s job must have been completed at least RatingWorksheetContainerAgeForPurging days.

Default: 90

See also

• Purge Rating Worksheet batch process

Upper bound on how often caches of RateBook and RateTableDefinition entities are refreshed, measured in seconds. This parameter addresses an issue with cluster installations.

The caches are refreshed when these entities are updated in the global cache. However, in a cluster installation, there is a possibility that messages for these updates can be lost. If the cache is not up-to-date, operations that depend upon these entities will fail. Keep in mind that rate books and rate table definitions are both versioned. So if, during quoting, a rate routine references a version that is not in the cache, the rate routine will fail.

To handle this, PolicyCenter forces a refresh of the caches based on this maximum duration. Cache refresh can happen in the middle of other operations. During refresh, the performance of operations that depend upon these entities, such as quoting, will be impacted.

The maximum value is 2147483. Do not set it any higher or the system will refresh the caches on each request.

Default: 600 seconds

Before importing rate tables, PolicyCenter scans the import file. The scan does not examine rate tables with more rows than specified in SmallRateTableRowLimit.

Default: 10000