Importing rules after a data model change

During an export of business rules, PolicyCenter records the data model of the exporting environment and creates a checksum for that data model. PolicyCenter then adds this checksum to the business rules export file. On import of the exported file, PolicyCenter compares the checksum of the export environment with the checksum of the import environment. PolicyCenter uses the checksum comparison to ensure that the data model of the exporting and importing environments match:

  • If the two checksums match, PolicyCenter imports the exported rules.

  • If the two checksums do not match, the import process fails.

The process of continually matching data models between export and import environments can cause problems with rule import during the PolicyCenter development phase, in particular. During PolicyCenter development, the data model often changes frequently Thus, you can export the business rules, modify the data model, and then fail at the attempt to import the business rules as the data model checksums of the export and import environments are different.

To minimize the need to regenerate the rule export file after a data model change, Guidewire provides a system property that disables checksum verification on business rule import.

System property VerifyRuleImportDataModelCheckSum

System property VerifyRuleImportDataModelCheckSum can be one of the following Boolean values.
true PolicyCenter enforces verification of the data model during rule import. The default is true.
false PolicyCenter does not enforce verification of the data model during rule import.
System property VerifyRuleImportDataModelCheckSum is only valid on a PolicyCenter server under the following circumstances:
  • The server mode is either DEV or TEST. The server mode cannot be PROD (production).
  • The value of configuration parameter BizRulesDeploymentEnabled is false.

Setting system property VerifyRuleImportDataModelCheckSum

You can set system property VerifyRuleImportDataModelCheckSum in the following ways:
  • In Guidewire Studio, in the server JVM options.
  • From a PolicyCenter command prompt, as you start the application server.