Optimize 10.7 | webMethods Optimize Documentation | Configuring BAM | Managing webMethods Optimize Environments | Configuring Logical Servers | Defining Logical Server Subcomponents for the Analytic Engine | Defining Process Tracker Settings
 
Defining Process Tracker Settings
You can set a Process Tracker attribute to control the number of days to retain process data in the Process Tracker database. Process data is data about process execution, such as an Order Process started at 10:52:31, step 1 succeeded, step 2 failed, and so on.
*To define the Process Tracker setting
1. In My webMethods: Navigate > Applications > Administration > System-Wide > Environments > Define Environments.
2. On the Define Environments page, click the name of the environment you want to work with.
3. On the Edit Environment page, click the Configure Servers tab.
4. Under the appropriate Analytic Engine logical server node in the configuration tree, click Process Tracker Settings.
A new area appears beside the configuration tree, labeled Process Tracker Settings for Analytic Engine.
5. In the Process Tracker Settings for Analytic Engine area, define the Process Tracker settings.
The following table provides information about the Process Tracker settings.
Field
Description
Input Events
Specifies the type of events that Process Tracker consumes. Set to:
*MAPI (default) to define that Process Tracker consumes MAPI events. The Monitor API (MAPI) is used to deliver Optimize events and provide enhanced notifications for event delivery problems. For more information about the MAPI, see Administering webMethods Optimize.
*EDA to define that Process Tracker consumes EDA events. EDA events are part of Software AG's implementation of an Event Driven Architecture system. In an EDA environment applications can emit and consume EDA events that occur within the suite at run time. For more information about EDA events, see webMethods Event Processing Help.
Process Instance Cache Size
Specifies the size of the in-memory structure where Process Tracker keeps track of all running process instances.
The default value is 5000000 process instances.
Note:
If the specified size is reached, Process Tracker needs to load additional process instances data from the database, which might slow down its performance. Software AG recommends that you specify a higher value for a big number of long-running process instances.
Process Model Refresh Interval
Specifies the interval (in milliseconds) at which Process Tracker refreshes the process model definition from the database.
The default value is 300000 milliseconds.
Staging Queue Maximum Size
Specifies the maximum size of the staging queue.
The default value is 1000000 control operations.
Note:
If you expect large numbers of operations to be processed, Software AG recommends that you specify a higher value for this field.
Staging Queue Processing Batch Size
Specifies the number of objects to be passed for processing from the staging queue in a single transaction.
The default value is 1000000 objects.
Note:
If your database is large, Software AG recommends that you specify a value smaller than the value of the Staging Queue Maximum Size field.
Staging Queue Settling Period
Specifies the period (in milliseconds) in which Process Tracker allows for incoming control operations to be gathered in the staging queue before they are processed.
The default value is 10000 milliseconds.
6. Click Save to save changes or click Cancel to discard any changes you have made in this setting.
If you click Finish without first clicking Save, any changes made to this setting will be lost.
7. To configure another logical server subcomponent, click the name of that subcomponent in the configuration tree.
8. Click Finish to close this page and return to the Define Environments page.