Direct load properties
The Gateway Server processes payment transmission information by creating artifacts and adding them directly into the database. By directly loading the artifacts, serialization and deserialization of the artifacts is not required.
During ingestion, most of the information added to the database is done locally by the Gateway Server. The Gateway Server also interacts with the Transaction Server by placing messages on a WebSphere® MQ queue. Transaction Server retrieves these messages and uses them to manage the events that occur during the ingestion process. Several Gateway properties control the behavior of the direct load process.
| Property | Default value | Description |
|---|---|---|
| directInsertCommitRate | 5 | The Gateway Server processes the specified number of insertions between database commits during the direct load item insertion process. This value must be in the range 1 - 60,000. |
| directBatchSize | 500 | The Gateway Server batches database insertion activity by allowing the specified number of insertions for a batch during the direct load process. Batch insertion does not require as much communication on the network, making it more efficient. A batch size of zero disables database insertion batching. This value must be in the range 5 - 5,000. |
| directLoadTimeout | 50000 | The amount of time, in milliseconds, that the direct load process waits on a socket connection before it closes the socket. |
| eventAggregationRate | 100 | To minimize the number of messages that are placed on the Transaction Server queues, the
loaded and captured PresentmentStateChange events are aggregated during ingestion. This property specifies the
maximum number of events to put into a single WebSphere MQ message. When large transmissions are processed, the mqMaxUncommittedMsgs property is also used when the number of events to aggregate into a single event is determined. If the value that is specified in this event aggregation property results in a number of messages that exceeds mqMaxUncommittedMsgs, a calculated event aggregation rate is used instead. Using both properties to determine the event aggregation rate prevents having too many messages in a unit of work. |