Parallel rating parameters
Guidewire provides the following configuration parameters in the config.xml file related to parallel rating.
.
EnableCPDTOParallelRating
Enable parallel rating using data transfer objects (DTOs) for commercial property. This parameter also enables access to Rating Management components in the sample data, such as rate table and rate routines, that use DTOs. These components are included in the small sample data set and are provided for demonstration purposes.
Default:
false
Required: No
Dynamic: Yes
ParallelizedRatingEnabled
Enable or disable parallel rating. If true, parallel rating is enabled
for each line of business which supports parallel rating. If false,
parallel rating is disabled.
Default:
true
Required: No
ParallelRatingTimeoutPerCoverable
The number of milliseconds per coverable to wait for parallel rating to complete. Because the timeout is per coverable, policies with a large number of coverables will have a longer timeout than smaller policies. This timeout applies to all lines of business that implement parallel rating.
For example, when quoting a policy with 10 coverables and using the default timeout of 20 seconds per coverable, the server times out on rating 200 seconds after it starts. When the timeout is reached, PolicyCenter displays an error to the user and attempts to stop the rating thread.
A value of -1
implies no timeout and the queue waits until rating completes or the session times out.
This is not recommended.
Default:
20000 milliseconds
Required: No
MaxRatingThreadPoolSize
Maximum number of threads spawned during parallel rating. The optimum number of threads depends upon how many tasks the typical policy generates and how long each task takes to complete. The optimum number of threads also depends upon the number of available processors, the typical number of users, and competition for processors from other PolicyCenter features which also implement parallel rating. As a starting point, set the initial value to the number of available processors in your environment. Be aware that other processes or PolicyCenter features which use parallel processing, such as product model availability, may be competing for processors. Perform benchmark testing to better determine the maximum number of threads.
Default:
4
Minimum:
1
Maximum: none
Required: No
