Configure Engine Others Properties

The Engine Other properties define the engine's runtime database configuration, directory polling, event storage, and PAPI.

To configure Engine Others properties:

In the left pane of Process Administrator, click Engines.
In the right pane, on the Engines page, click the engine Name.
On the Engines | Edit Engines page, click the Others tab.
Configure the following properties and click Save.

Runtime Database Configuration	Sets the configuration ID for the database that will be used at runtime. The default for this ID is the name given the engine when creating it. However, it is possible to configure another ID (necessary when deploying the engine with an application server and you want to use the server's resources to handle database connections).
Directory Polling Interval	Determines how often, in minutes, the information in the directory service is read. This setting is important when working with a Directory Interface that does not support listeners, which necessitates the engine connecting to the Directory Interface service to check for updates in the data.
Store Events	Determines whether information about instances is retained for analysis and auditing. The following options are available: Always - Instance information is always retained. This option will lengthen transaction times. Never - Instance information is never retained. This option shortens transaction times. Depends on Process - Instance information is only retained if the processes were designed to log information.
Instance Retrieval Size	Determines the number of instances to be exchanged between the engine and its client (WorkSpace). While larger values impede engine performance, they may be necessary when processing large numbers of concurrent users.
Notify Thread Priority	Determines the thread priority when notifying clients (WorkSpace) of changes to the engine. The thread priority ranges from 1 - 10, with 1 being the highest priority and 10 being the lowest. This option is only available for ALBPM Enterprise Standalone; for J2EE, the thread priority is handled by the application servers's messaging queue (JMS).
Latency Between Notifications	Determines how often the engine notifies clients (WorkSpace) of updates, at which time the instance cache is updated. This option is only available for ALBPM Enterprise Standalone; for J2EE, the notification times are handled by the application servers's messaging queue (JMS).