JeOMS Configuration

All the parameters of JeOMS have default values and no parameter value required to deploy and run JeOMS in basic mode. You may change the following parameters to tune the performance of the Jeopardy Management System.

Jeopardy Management Tuning Parameters

The Jeopardy Management Tuning Parameters are as follows:

Risk Threshold

Set this parameter to specify percentile increase over typical duration beyond which a task can be considered to be running in a hazard region. For example, if typical duration of a process component is 60 minutes and if risk threshold is 50, any plan item that is executing for more than 90 minutes is considered to be running in a hazard region. Default value is 25 percentile point.

Out of Scope Threshold

Set this parameter to specify Percentile increase over maximum duration beyond which an execution can be considered running out of scope for jeopardy detection. And no further jeopardy monitoring be performed on the plan. For example, if maximum duration of a process component is 60 minutes and if out of scope threshold is 100, any plan item that is executing for more than 120 minutes is considered as out of scope and JeOMS stops monitoring the plan.

Time Window Value/Time Window Unit

The Configuration parameter Time window value and Time Window Unit are combined together to determine the Time window or Chronon to which plan items of execution plans belong in JeOMS. It is a user-defined interval of time during which any execution of any plan item would result in grouping the plan item together. Configure this value based on execution characteristics of process components in fulfillment eco system. This value is used by jeoMS to cluster plan items in execution to optimize jeopardy detection cycle.
Time Window Value/Time Window Unit


For example, if fulfillment tasks executed by the process components typically take few days to complete, it is probably meaningless to use seconds or milliseconds to track the progress of a plan item. In this case, the you can provide a value in terms of hour units. On the other hand, if JeOMS monitors very fast executing plans, JeOMS will require a Chronon of milliseconds or seconds to accurately predict the jeopardy condition. The default value is 10 Minutes.

Messaging Configuration

JeOMS piggyback on message configuration parameters of OMS and no additional configuration required.

Datasource Configuration

JeOMS piggyback on data source configuration parameters of OMS and no additional configuration required.

Colocated Jeopardy Mode

Colocated Jeopardy mode will only support "Cache" as the second level data store. The existing data store options like File and ActiveSpace will not be supported.

Two tables are responsible for the cache data store. The tables are:

  1. TIME_WINDOW
  2. DAMPENING_CRITERIA

Change in JeOMS

If the node status has not been set to STARTED, none of the JeOMS requests will be processed. Currently, all JeOMS requests are processed by the state machine. JeOMS will wait for the node to achieve the STARTED state to begin jeopardy monitoring.