TheStartupsection allows you to configure any startup properties for the engine.
| Property | Description |
|---|---|
| Start automatically during Process Administrator initialization | Determines if the engine is started automatically when Process Administrator is launched. |
| Additional arguments used in startup | Defines any startup arguments passed to the engine on startup. Available
engine arguments are:
|
| Additional java arguments used in startup | Defines any arguments passed to the Java Virtual Machine during engine startup. |
| Property | Description |
|---|---|
| Maximum Java Virtual Machine Heap Size | Specifies the maximum amount of memory, in megabytes, the engine
can
use. If the engine's memory usage reaches this limit, the engine stops itself and
restarts.
You should always try to set the minimum value for the Java Virtual Machine heap size. The default is 256 megabytes |
| Maximum Instance Size | Specifies the maximum amount of memory a process instance can use.
This property limits the size of all process instance variables used by a process
instance. When any instance exceeds this limit, the engine is not able to persist
instance data and the task fails and must be re-executed after increasing the size
of
this property.
The default is 16 kilobytes |
| Participant Cache | |
| Instance Cache Size | Defines the cache size used to store recently accessed process
instances. This cache is shared by all processes deployed on the engine.
The default is 5000 instances The default value of 5000 instances in the cache is usually considered above average for medium size installations. If the engine has processes with thousands of instances running and these processes have a high concurrency, it is advisable to increase the size of the cache so that the engine does not need to reload instance information when new instances are accessed. |
This section allows you to configure thread handling behavior of Oracle BPM Standalone. These properties should be configured to reflect the load on your deployed processes.
| Property | Description |
|---|---|
| Maximum number of execution threads used for interactive executions | Determines the size of the thread pool available for user requests.
These requests general originate from interactive activities within a process.
The recommended value for this property depends on the size of your process, number of concurrent users, and the number of interactive activities that must be processed. The default value is 50. |
| Maximum number of execution threads used for automatic tasks | Determines the size of the thread pool available for automatic tasks.
The default value is 5. |
| Priority of Automatic Execution Threads | |
| Automatic Items Queue Size | |
| Retry Times | |
| Retry Interval | |
| Persist instance data | |
| Maximum Number of Rogue Component Executions | |
| Maximum amount of acquired instances in a single execution context. | |
| Request Queue Size | |
| Request Queue Timeout |
| Property | Description |
|---|---|
| Property | Description |
|---|---|
| Property | Description |
|---|---|
| Maximum BP-Methods Timeout | |
| Interactive Component Timeout | |
| Maximum Process Web Service Session Timeout |
| Property | Description |
|---|---|
| Trace Components |