System properties
The following parameters are general properties that are used by the Transaction Server to
control its processing:
| Property | Default value | Range | Description |
|---|---|---|---|
| componentStartTime | 5000 | 100-60000 | The time (milliseconds) that the Transaction Server waits for each of its internal components to start during system initialization. |
| agentRequestWaitTime | 5000 | 100-60000 | The time (milliseconds) that the Transaction Server waits to add a request to an agent queue. This property is only used for processing API requests that use the RMI interface. |
| siteId | 0 | 0-100 | Site under which all work is processed by default. |
| resourcePoolConnectionCount | 15 | 1-200 | Number of database connections to be pooled for Transaction Server to use. This number should be greater than the sum of maxApiAgents, numEventWorkers, maxExtractionWorkers, and numListeners, where numListeners is the total number of listeners that are defined for all queues in the ListenerProfile.xml. Occasionally, connections are needed in a few other places. If log messages indicate that the number of connections are insufficient, ensure that you are returning connections to the pool in any custom code. If the log messages continue, increase the resourcePoolConnectionCount. |
| enableDcims | false | true/false | Enable decentralized image subsystem image retrieval support. If enabled, the Transaction Server attempts to satisfy item or image retrieval requests that cannot be found in the FTM database. It does this function by accessing the decentralized image subsystem database system. This workstation must have the ahiit.dll loaded and in the path statement. |
| DcimsNativeTraceFlag | 0 | 0-15 | This flag controls the tracing of DCIMS messages in the Transaction Server. This
flag can be activated to write DCIMS message records out to a fixed file location. This file is created if
it is not present or appended if it exists. The following are the allowed values for this tracing flag:
|
| timerResolution | 10 | 1-1000 | The minimum timer resolution, in microseconds, used when a system timer is reset. Occasionally, the system high-resolution timers are recalibrated, which sometimes results in negative time intervals. When a negative time interval is detected, the value that is specified in this parameter is used instead so that the timing statistics for the Transaction Server are not adversely affected. |
| timerResetCounts | false | true/false | Specifies whether default timer resolution statistics are placed in the timing file. These statistics show the total value of the timer resolution corrections that were added to the timing values. |
| reportDir | /opt/ibm/ftm/transaction-server/reports | N/A | Specifies the directory where the Transaction Server writes its online reports. These reports are issued by the Transaction Server for various reasons. For example, a user-written DDL script can be configured to run for specific purge events. The report from the DDL script is in the report directory. The report directory is maintained or cleaned up periodically by using the ReportDirectoryMaintenance scheduled task. For more information, see Task Scheduler. |
| enableJaQI | false | true/false | Enable the Image Soft Titan e2 image retrieval support. If enabled, the Transaction Server attempts to satisfy item or image retrieval requests that cannot be found in the FTM database; it does this function by accessing the Image Soft JaQI interface. The Image Soft jaqiclient.jar file must be in the class path environment setting. |
| traceJaQICalls | false | true/false | If set to true, trace messages are logged for the calls to the Image Soft JaQI interface. This property is for debugging purposes only and is used if enableJaQI is set to true. |
| tcpNoDelay | true | true/false | Disables the Nagle algorithm for TCP. |