Values set for runtime instance, transport, and database connection configuration properties can be reviewed and edited. See Reviewing and Editing Configuration Properties.
|
Instance Property |
Description |
|
Control |
|
|
Auto Start |
When set to true, causes a runtime instance to auto-execute each time the agent server is launched. When set to false, the runtime instance must be started manually. |
|
Optional |
|
|
BizTracker Transport |
Identifies the transport to which the process probe puts tracking messages and from which BizTracker picks up the information. |
|
Cleanup Threads |
Specifies the number of threads the engines uses to remove obsolete information from the runtime database. (0=no cleanup or 1=perform cleanup) |
|
Custom JVM Startup Options
|
Specifies any custom Java Virtual Machine (JVM) options that you require. For example, to use JMS Queues on the J2EE reference implementation from Sun, add -Djava.class.path=<your class path>. -Xms<size> sets the initial Java heap size and -Xmx<size> sets the maximum Java heap size. If you supply more than one option, separate each option with a space. Use Custom JVM Startup Options to modify the Web service timeout on the Unwired Orchestrator service instance. The value of the property is the Web service timeout in milli-seconds. Example: |
|
Cluster Mode
|
Allows an service instance to be run in a ring providing failover or distributed processing functionality. User must first configure clustering properties in the Endpoint Manager. See Clustering. |
|
Resource Retry Count |
Value indicates the number of times that the engine will attempt to establish a connection to transport and database resources if a connection fails. Resource connection retry functionality is only valid if the connection fails at engine startup. The default is 0 (no retries). |
|
Resource Retry Interval |
Value indicates the time in seconds that engine will wait between attempts to establish a connection to transport and database resources if a connection fails. Resource connection retry functionality is only valid if the connection fails at engine startup. The default is 0. |
|
State Database Port |
Specifies the port number to use for external connections to the runtime engine state database. This parameter is used when configuring for clustering. All engines in the cluster must use the same port to access the same non-embedded state database. |
|
Required |
|
|
Analysis Threads |
Specifies the number of threads the engine uses to evaluate and execute business process activities. |
|
Cleanup Interval |
Specifies the time interval in minutes between invocations of the cleanup operation to remove expired business processes. The value must be greater than 16; the default is 60. If a value less than 16 is entered, the default of 60 is used by the engine. |
|
Cleanup Period - Retain Completed
|
Number of hours before freeing memory and disk space of business process information that successfully completed. |
|
Cleanup Period - Retain Error
|
Number of hours before freeing memory and disk space of business process information that completed in an error state. |
|
Date/Time Format
|
When a date/time is in an incoming message, the first attempt at parsing the string is with the default format "YYYY-MM-DD HH:MM:SS.mmm". If that fails, an attempt to parse with DateTimeInputFormat is performed. |
|
Date Format
|
Specifies the format for the second highest probability to parse date and time values in a document. When a date is in an incoming message, the second attempt at parsing the string is with the default format "YYYY-MM-DD". |
|
Engine Logging Level
|
Setting to provide logging of business process messages to the NNSYMessageLog.nml. Settings are: |
|
Engine Logging Threads |
Specification of the number of threads the engine uses for logging messages. (NNSYMessageLog.nml). (0=no logging or 1=perform logging) |
|
Error Transport
|
Endpoint name of the transport used for handling events in an error state. Select from the list of defined endpoints. Events with errors other than routing errors result in a message being put to the specified transport. |
|
No Hit Transport |
Endpoint name of the transport used for handling events that are not successfully routed to a business process. Select from the list of defined endpoints. Events with routing errors result in a message being put to the specified transport. |
|
Services Console Logging Level |
Setting to provide logging of service messages to the console and to the psengine.log file. Settings are: |
|
Services Debug Setting
|
Specification of whether to turn on debugging for the services plug-in and provide the information in the NNSYMessageLog.nml file. |
|
Services Log File |
File name to which service plug-in messages are written. (defaults to sybesp.log). |
|
Services Log File Level |
Setting to provide logging of service plug-in messages to the sybesp.log. DEBUG |
|
Time Format
|
Specifies an alternate format to use in parsing date and time values. The default format is "HH:MM:SS.mmm". |
|
XML Parse Mode
|
Specifies when to validate the XML data against a schema or DTD. Options are: |