Caching workflow data
You can use Object Query Cache (OQC) to intercept queries that are used for a workflow object's construction with cached queries, thus enhancing workflow event processing. This mechanism reduces the database use for each event that is processed by caching the workflow definition data.
The cache size and cache assessing time is configured in the following
common.properties options:
- max_workflow_in_cache=<n>
- Sets the limit for the cache size in the JVM.
- max_workflow_cache_timeout_in_seconds=<n>
- Sets the time interval in seconds for how often the JVM checks for workflow updates.
Note: If you are using a clustered environment, to synchronize the workflow data, set the value of
max_workflow_in_cache and
max_workflow_cache_timeout_in_seconds properties to
-1.
If set to -1, the cache is disabled. If set to 0, then the JVM always checks for workflow updates. Updates that are made on a given JVM are always immediately available on that JVM.