The Intentional Logging screen
| Item | Description |
|---|---|
| Turn Intentional Logging On / Turn Intentional Logging Off | Set of buttons that enable (On) or disable (Off) the use of intentional logging in Guidewire PolicyCenter. If you disable intentional logging, PolicyCenter disables the use of any of the defined logging markers into the application log. |
| Settings Per Element table | Table that lists the defined logging markers and provides the means to enable or disable individual logging markers. |
By default, Guidewire enables the use of logging markers globally in the base configuration. Guidewire also enables the use of each individual logging marker as well.
Marker visibility in the Intentional Logging screen
Initially, in a new installation, PolicyCenter does not know all possible intentional logging markers that exist in the base configuration and in custom code. Consider that an intentional logging marker is an arbitrary string that you use to delineate a business or a system event. And, in fact, some markers are dynamic, meaning that the marker includes the name of a work queue, or a batch process, or that the marker name depends on the use of some data.
For example, imagine a custom batch process exists for importing some data into the database. Imagine that this batch process uses a custom marker for intentional logging as the batch process executes. In this example, suppose that the name of the marker is dynamic and that the marker name depends on the data the batch process imports into the database. In this situation, PolicyCenter does not have a way of knowing the name of the marker before the use of that marker in the system.
At the first use of an intentional logging marker anywhere in a Guidewire cluster, PolicyCenter stores the marker name in the database, which registers the marker name in PolicyCenter. Registering a marker makes the marker name visible in the Server Tools Intentional Logging screen, which shows only registered markers.
Whenever you start a PolicyCenter installation with a new database, there are no registered markers in the empty database. As the PolicyCenter server starts for the first time, the database upgrade process uses various intentional logging markers for logging the start up process. As the start up process unfolds, it registers each marker that it encounters in the database. Over time, as you use your PolicyCenter installation (meaning running batch processes, work queues, messaging, and exercising SOAP/REST APIs), the more PolicyCenter uses the defined logging markers and consequently the more markers that it registers in database.
At some point, PolicyCenter has used all of the possible markers, which register the markers in the database, and makes the full set of markers visible on the Intentional Logging screen.