Business rules parameters

Time (in minutes) that PolicyCenter retains rule data in the RuleVersion cache before it considers cached items to be stale and thus eligible for reaping.

PolicyCenter initializes the RuleVersion cache once, at server start up. It then rebuilds the cache every time the following entities change:

• RuleHead
• RuleVersion
• Rule

Default: 60

Minimum: 1

Maximum: 120

Set for server: Yes

Determines whether it is necessary to explicitly deploy a business rule before PolicyCenter can evaluate the rule. If you set the value of this parameter to true, you must also provide a value for configuration parameter BizRulesDeploymentId.

Do not attempt to set this parameter to true in a non-production environment. If you do so, the server generates an error and does not start. In a non-production environment, with the value of this parameter set to false, PolicyCenter evaluates all enabled and valid rules at runtime, including rules in the draft state.

Default: false

Unique string identifier of the server to which you intend to deploy the business rules. There is no default value for this parameter. If the value of BizRulesDeploymentEnabled is true, then you must supply a value for this parameter. Otherwise, the server generates an error during server start and refuses to start. PolicyCenter ignores this configuration parameter if the value of BizRulesDeploymentEnabled is false.

It is possible to change the value of this parameter through a server restart. However, if you change the value of BizRulesDeploymentId, PolicyCenter does not update already deployed rule versions.

Guidewire recommends, in a production environment, that you have a single BizRulesDeploymentId value for the entire production cluster. This action guarantees that all nodes in the cluster use the same BizRulesDeploymentId parameter value. Using the same value on all cluster nodes ensures that rule deployment works consistently across all nodes in the cluster. You can choose any name for this value if you use only a single PolicyCenter production cluster. For example, if all nodes in a cluster point to a single database, you can use the database ID as the BizRulesDeploymentId value.

However, if you use multiple production clusters, each separate cluster must have its own unique value for this configuration parameter. PolicyCenter expressly does not permit you to import business rules from another cluster instance that has the same BizRulesDeploymentId value as the cluster instance into which you are importing the rules.

PolicyCenter associates the BizRulesDeploymentId value (name) with a rule during its deployment. Thus, if you deploy the rule in one production cluster, the name appears along with the rule version number in other production clusters to identify that the rule was deployed in a particular production cluster. For example, if the value of BizRulesDeploymentId is GW100-A, the rule version appears as 1.GW100-A in all other production clusters.

Default: None

See also

• Correct duplicate BizRuleDeploymentId values

Whether PolicyCenter imports the business rules located in folder config/import/bizrules on starting the application server with an empty database. Set the value of this parameter to true to import the files located in the bizrules folder.

Default: false

See also

• About the import directory
• Automatic import of business rules at server startup

Maximum number of hops for a leaf search to search through in suggesting matching results. This parameter refers to the autocomplete feature of the Rule Condition editor on the Business Rules detail screens.

In the following expression, A is the root, B is a single hop, and C is a leaf.

A.B.C

The following example illustrates a two hop expression, with the root being office and PhoneNumber the leaf.

office.ConferenceRooms[0].Table.PhoneNumber

Default: 3

The Rule Head cache stores the RuleHead IDs for all business rules used in the application. If not configured to do otherwise, PolicyCenter populates this cache using multiple database queries. The use of multiple queries can greatly impact the performance of the business rules. However, if you set this configuration parameter to true, PolicyCenter uses a single database query to bulk load the cache, thereby significantly improving the performance of the business rules.

Default: true

The Rule Entities cache stores the entities that comprise the entire rule graph for all rule versions that can possibly execute in the application. If not configured to do otherwise, PolicyCenter populates this cache using multiple database queries. The use of multiple queries can greatly impact the performance of the business rules. However, if you set this configuration parameter to true, PolicyCenter uses a single database query to bulk load the cache, thereby significantly improving the performance of the business rules.

Default: true