Implementation > EBICS > EBICS Server > Monitoring with Sentinel > Overview

Monitoring EBICS Server processes

Monitoring EBICS with Sentinel

You can use Sentinel to collect information about two types of EBICS Server activity:

Processing of incoming and outgoing exchanges
Client subscriber initiation processes (key exchange and approval)

To provide information to Sentinel, the EBICS Server generates event notification messages that it sends to Sentinel. Sentinel stores the information contained in these messages in the Sentinel database. You can then use Sentinel features to recover, organize and display the stored data.

Sentinel also provides you with tools that help you create pre-programmed automatic responses to specified network conditions. Using these tools, you can configure Sentinel to act immediately to handle exceptional and/or abnormal integration processing events and statuses.

The information that the EBICS Server collects and sends to Sentinel is defined by Tracked Objects. A Tracked Object is a data container in Sentinel that defines the parameters of a specific application event. For monitoring the activities of the EBICS Server you use two Tracked Objects:

XFBTransfer – to generate messages concerning the processing of exchanged messages
EBICSINI – to generate and send Client subscriber initiation processes (key exchange and approval)

Overflow file for Sentinel tracking

You can define an overflow file for Sentinel tracking. The overflow file stores Sentinel events when the Sentinel Server is not available because of network issues or because the Sentinel Server is stopped. When the Sentinel connection is available again, the next event to come will trigger the sending of previously-stored events.

If Sentinel tracking is enabled, either the message "Using Overflow file" or "No Overflow file defined" is written to the log at the INFO level.

You can configure the name and size of the overflow file in the EBICS Server configuration file configuration.properties.