Transaction Manager Records

A number of records are provided with Transaction Manager that are specifically designed to gather transaction information from the transaction log files. This information includes:

  • Number of transactions, both financial and non-financial,

  • Number of approved/denied transactions,

  • Number of timeout transactions,

  • Percentage of approved/denied transactions,

  • Percentage of timeout transactions.

Plus, response times for:

  • Interchange/switch/host,

  • Authorizations or routings.

Transaction Manager can gather transaction count and approval rate information over the previous three intervals (interval sampling counts) by using records that contain a number of special fields. For example, the following fields are available in the Transaction Summary records:

Field Name

Description

ApprovalPercent

Short Name: APRV%

Percentage of approved transactions during the current sample period.

ApprovalPercentPrevious

Short Name: APRV%1

Percentage of approved transactions during the previous sample period.

ApprovalPercentPriorToPrevious

Short Name: APRV%2

Percentage of approved transactions during the sample period prior to the previous period.

Transactions

Short Name: TRANCNT

Number of transactions during current sample period.

TransactionsPrevious

Short Name: TRANCNT1

Number of transactions during the previous sample period.

TransactionsPriorToPrevious

Short Name: TRANCNT2

Number of transactions during the sample period prior to the previous period.

The three sample counts allow the Transaction Manager to detect changes in transaction rates that may indicate a loss of service for a specific interchange or terminal. With the availability of three sampling counts, statistical techniques can be applied in Transaction Manager to monitor the rate of change as opposed to change - an effective technique to differentiate low and high traffic periods during service failure.

For full details of the various ATM and POS Transaction Manager records and their associated fields please refer to the Prognosis Records.

Additional Records for Postilion Systems Only

The records currently provided with Transaction Manager for monitoring a Postilion environment include.

Used to monitoring request operations between HSM devices and the Postilion Realtime server. Fields include:

  • Average response times

  • Operations per second

  • Time Outs per second

Used to collect information relating to specific interchanges. Fields include:

  • Remote arrival and dispatch rates.

  • Source and Sink node arrival and dispatch rates.

  • Active remote connections.

  • Average driver call durations.

Used to collect internal state information relating to either the Transaction Manager or Postilion node applications. Fields include:

  • Event processing time.

  • Queue lengths and queue times.

  • Active database connections and deadlocks.

  • Transaction cache size.

Used to obtain negative acknowledgement data. Fields include:

  • Negative acknowledgment average times

  • Negative acknowledgment raw counter

Used to obtain call profile information. Field include:

  • Average call duration

  • Number of active calls

  • Number of calls per second

  • Total call duration

Used to gather information relating to sink node connections within the Transaction Manager process and the services provided to the upstream entities. Fields include:

  • The number of transactions per second.

  • Arrival and dispatch rates.

  • Response times, queue lengths and queue times.

  • Store and forward and transactions in flight.

  • Percentages of Transactions approved and declined.

Used to gather information relating to source node connections within the Transaction Manager process and the services provided to the downstream entities. Fields include:

  • The number of transactions per second.

  • Arrival and request rates.

  • Response times, queue lengths and queue times.

  • Percentage of transactions approved and declined.

Used to gather information about the overall system performance. Fields include:

  • Entity type

  • Event condition types

  • Node status

  • Number of active connections

  • Sink and Source node details

Used to gather information relating to the terminal driver object. Fields include:

  • Remote arrival and dispatch rates.

  • Source and Sink node arrival and dispatch rates.

  • Active remote connections.

  • Average driver call durations.

Used to gather transaction and performance metrics for the Postilion Terminal. Fields include:

  • Card acceptor name and location

  • POS data code

  • POS geographical data

  • Postilion terminal details

  • Time of last message

  • Time of last transaction

Provide feedback on this article