Configuring Event Monitoring


Configuration files	Thin Client .. \ parameter \ client \ ecEvents.properties .. \ parameter \ server\ecServerEvents.properties Full Client ..\parameter\client\ecEvents.properties ..\parameter\server\ecServerEvents.properties

General Information

The Clients support monitoring via the GK/Retail Enterprise Cockpit using predefined events.

All events of all systems are automatically transmitted via the Storemanager infrastructure to the Enterprise Cockpit, which is the GK/Retail standard monitoring tool.

Events can be enabled or disabled per application. In the Enterprise Cockpit, it is also possible to set the events that should be visualized and in which way.

Structure of the Event IDs

Table 1. X.FunctionID.NN
Component	Description
X	"S" = Standard event "S" = Event of a customer enhancement
FunctionID	The number consists of 11 characters: PPBBGGMMFFF P = Product ID B = Process, service ID G = Grouping ID, e.g. application, component, etc. M = Module ID (optional) F = Function ID, starting with 001 (if optional module ID is not used: 00001)
NN	Event number of the function, starts with 00

Structure of an Entry

An entry looks as follows:

 EnterpriseCockpitEventConfig.ecEvents.0.eventId=S_01010101201_00
EnterpriseCockpitEventConfig.ecEvents.0.enabled=true
EnterpriseCockpitEventConfig.ecEvents.0.messageLevel=INFO
EnterpriseCockpitEventConfig.ecEvents.0.messageContent=Worker {0} logged in.

Enabling/disabling events

All events are disabled in the standard product configuration. To enable, set .enabled=true, to disable, set .enabled=false.

Configuring the Monitoring for POS Thin Client

Configuration files

Two configuration files are available for the POS Thin Client:

ecEvent.properties

The file ecEvent.properties contains the events that are triggered via the Client.

ecServerEvents.properties

The file ecServerEvents.properties contains the events that are triggered via the Service.

Note:

A list of available events can be found in the document "POS Client - Operation Guide".

Configuring the Monitoring for POS Full Client