Transaction Server integration
The Gateway Server inbound process can be configured to call the Transaction Server to process transactions. The Gateway Server must use the Transaction Server classes that match the Transaction Server being used to work properly. To ensure the correct Transaction Server classes are being used, copy the txsvrcli.jar file from the folder install_directory\shared\v409\pfs\ITS\lib to the \lib folder of Gateway Server.
The following properties configure Transaction Server connectivity:
| Keyword | Values/Example | Description |
|---|---|---|
| ITSenable | true or false | Set to true to enable writing of the ANSI X9.37 records to
the Gateway repository. The default value is false. |
| ITSX937Exclude | 50, 52 | Identifies ANSI X9.37 records that should not be written to the FTM
database.
Specify the two-digit record types, separated by commas, that are to be omitted. This allows records that are
not needed to be omitted. Note: The 01, 10, 20, 25, and 31 record types may not be omitted.
|
| ITSReturnsUpdate | true or false (default) | Set to true to update the disposition flag in Transaction Server when processing a return transaction transmission. For each transaction (type 31 record) in the transmission, the transaction disposition flag will be updated with the return reason. The Forward Bundle Date field in the Type 31 record is used to locate the transaction in the Transaction Server therefore it must be populated with a valid date. |
| ITSFetchImageWithPaymentId | true or false | When fetching images from the Transaction Server, this parameter indicates if the
item record sequence number field in the outgoing X9 file contains sequence numbers or payment IDs. If this
parameter is set to true, Gateway uses the item record sequence number field as the payment
ID. When set to false, the item record sequence number field is used as the sequence number. The default value is false. |
| processTimingFilename | ./GWTiming.csv | File name used to create the timing CSV file. If this name is specified, a timing CSV file with various timing type information is created. Do not specify a file extension for this file name because an extension of CSV is automatically appended to it. For example, .\GWTiming produces a timing file in the current run directory named GWTiming0.csv. Once the file reaches the size specified, it becomes GWTiming1.csv and a new GWTiming0.csv is created. |
| timerResolution | 10 | The minimum timer resolution, in microseconds, used when a system timer is reset. Occasionally, the system high resolution timers are re-calibrated, which sometimes results in negative time intervals being measured. When a negative time interval is detected, the value specified in this parameter is used instead so that the timing statistics for the Transaction Server are not adversely affected. |
| timerResetCounts | 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. |
| ITSServer | ftm-transaction-server-service-name | The Red Hat®
OpenShift® networking service name of theTransaction Server from which the outbound gateway server retrieves remote image data. Note: If ITSServer or ITSPort is not
configured, the outbound gateway server fetches local images.
|
| ITSPort | 1099 | The Red Hat OpenShift networking service port-mapping of the Transaction Server networking service. |
| ITSToken | ClientRmiGateway | The token used for constructing the RMI address for the Transaction Server client interface. It is used when more than one Transaction Server is run on a single machine so that their RMI client interfaces can be isolated. |