DS CWA 16374-44:2014

Extensions for Financial Services (XFS) interface specification – Release 3.20 – Part 44: XFS MIB Application Management MIB 3.20

Scope

This document provides the specific MIB definition (Management Information Base) variables for the Application Management sub-tree version one, as foreseen by the XFS MIB Architecture and SNMP Extensions Programmer’s Reference document.

The xfsAppMIB version one sub-tree is identified by:

xfsMIBRoot
• xfsManagedApp (1000)
• xfsAppMIBV1 (1)

The xfsAppMIBV1 sub-tree contains the following variables:

• xfsConsumerApplication is the state of the consumer application functionality.
• xfsSupervisorApplication is the state of the supervisor functionality.
• xfsConsumerAppCommStatus is the status of the communication between the consumer application and the host.
• xfsExtension is a list of vendor dependent additional application state information.
The xfsConsumerApplication and xfsSupervisorApplication variables allow the applications view of the overall state of the terminal to be determined and reported. These variables identify system issues, e.g. the consumer application may be offline while all devices are available - the terminal is then not able to offer transaction services (even if the individual states of all the terminal’s devices are online and functioning properly).
The xfsConsumerAppCommStatus reports the communication status of the customer application with the host, whether it is online, offline or the communication status is unknown.

This document describes the OID structure for reporting the application state. This MIB reflects the status of the consumer application, the status of the supervisor application and the status of the consumer application communications. The status of XFS devices is separately defined and reported by the XFS device class MIBs.

It is important to be clear that this document provides a standard interface for management clients to obtain state information. It does not define an interface for how this information is obtained locally. How this information is populated by local self-service SNMP agents is the responsibility of the agent implementation. In addition, the application management agent implementation must be compatible with the device agent so that the agents can coexist on the same platform. This approach:

• Allows the SNMP agent supplier to define how best that this information be populated.
• Avoids the CEN XFS device standard from encroaching in non-device functionality.

The XFS MIB Architecture and SNMP Extensions Programmer’s Reference document provides an overview of the MIB structure. The following picture shows the structure of the xfsAppMIBV1 sub-tree.