Verifying the product model
The product model is the part of PolicyCenter configuration that determines the types of policies that you can create. It also determines the coverages, coverage terms, conditions, exclusions, and other objects that are available in each policy. As you customize the product model, it is critical that you adhere to certain product model principles so that the product model remains internally consistent. Adhering to product model principles includes such rules as the following:
No Product may contain multiple PolicyLinePattern entities of the same type.
To help you make valid changes, Product Designer enables you to validate as much of the product model as possible as you work. All product model pages in Product Designer have a Validate link that validates the changes on the current page. Additionally, both the Commit All and Validate Only links on the Changes page perform validation on all of your changes before they are committed to PolicyCenter. However, these validations are only a subset of a complete product model verification.
To perform thorough product model verification and ensure that the product model is consistent and valid, PolicyCenter verifies the product model every time the server starts. Successful product model verification requires the product model to meet a specific list of criteria. PolicyCenter persists the product model through a set of XML configuration files, and checks the content of these XML files under the following circumstances:
- During server startup – PolicyCenter performs verification automatically when the application server starts. If it finds an error, it adds a message to the system console and fails to start.
- During a compile operation from Studio – PolicyCenter performs verification if you compile one or more product model files in Studio. PolicyCenter displays any errors in the Log window at the bottom of Studio.
See also