Modifying the runtime configuration of a model

Use the WebSphere® Application Server administrative console to configure event processing and on-time situations for a specified version of a monitor model.

1. In the WebSphere Application Server administrative console, click Applications > Monitor Models.
2. In the Version column, click the monitor model for which you are editing the configuration properties.
3. Click Change Runtime Configuration.
4. Click the Tuning tab, and view or modify the following properties as appropriate.
   Processing Strategy

   Property	Description
   Processing Strategy	Displays the processing strategy selected during the deployment of the model version.

   Event reordering

   Property	Description
   Event reordering enabled	Indicates whether event reordering was enabled during the deployment of the model version.
   Late arrival stand off delay (seconds)	Specifies the number of seconds to delay the processing of a batch of related events to allow late out-of-order events to arrive, be reordered, and added to the batch. Enter an integer from 10 to 1800. This property is used only when event reordering is enabled.

5. Click the Error Handling tab, and modify the following properties as appropriate.
   Stop event processing conditions

   Property	Description
   No instance found correlation error	Specifies whether to stop event processing when no instance found causes a correlation error. Select this check box to stop event processing if the expected monitoring context instance was not found.
   One instance found correlation error	Specifies whether to stop event processing when one instance found causes a correlation error. Select this check box to stop event processing if one unexpected monitoring context instance is found.
   Multiple instances found correlation error	Specifies whether to stop event processing when multiple instances found causes a correlation error. Select this check box to stop event processing if two or more unexpected monitoring context instances are found.
   No parent found error	Specifies whether to stop event processing when a no parent found error occurs. Select this check box to stop event processing if no parent monitoring context instances are found for a non-root monitoring context.
   Multiple parents found error	Specifies whether to stop event processing when a multiple parents found error occurs. Select this check box to stop event processing if more than one parent monitoring context instance is found for a non-root monitoring context.
   Value out of range error	Specifies whether to stop event processing when a value out of range error occurs. Select this check box to stop processing if a number is too large or too small or if a string is too long to be persisted.
   Runtime exceptions	Specifies whether to stop event processing when runtime exceptions occur. Select this check box to stop event processing when runtime exceptions occur. This selection overrides any other selections on this page.

6. Click the KPI tab, and perform one of the following tasks:
   • Modify the values for the KPI cache refresh interval (in minutes) property, as described in the following table:

     Property

     Description

     KPI cache refresh interval (in minutes)

     Specifies in minutes how often the KPI cache refreshes. The default value of 0 indicates that KPIs are not being cached. The default value for the data movement service interval is 5 minutes. The default value for the Cognos cube cache interval is 1 minute. For efficiency, this interval along with the Cognos cube cache interval should not be less than the interval specified for the data movement service (if enabled). KPI caching is recommended to improve system performance. For information related to changing the data movement service interval or the Cognos cube cache interval, see Related tasks.

   • Clear the KPI cache immediately without waiting for the interval by clicking Clear KPI Cache Now.
7. To accept and save the settings, click OK or Apply. To ignore the changes, click Cancel, or to retrieve the last saved values, click Reset.
8. Restart the monitor model application for these changes to take effect.