/ EUROPEAN COMMISSION
DIRECTORATE-GENERAL INFORMATICS
Directorate B - Digital Business Solutions (DBS)

e-TrustEx

Logging Summary

Date: / 22/10/2014
Version: / 1.0
Authors:
Revised by:
Approved by:
Public:
Reference Number:

Document History

Version / Date / Comment / Modified Pages
1.0 / 22/10/2014 / Document creation / All

Contents

1. Web modules used for web-services 4

2. CIPAdmin 4

3. Services and Integration layers 4

1. Web modules used for web-services

The web modules core-web and procurement-web are filtering the requests, and they log the following information:

·  the URL accessed,

·  the IP address from which the access is done, and

·  the request duration

Note: The GET requests are not logged.

2. CIPAdmin

The administration console logs any error or exception that might occur, plus successful operations like logins, creation, modification or deletion of entities. The information logged by the administration console includes:

·  username

·  user role

·  operation (login, creation etc.)

·  IP address from where user accesses the application

·  Page URL

·  Entity type and id (for operations on entities; like creation, deletion etc.)

3. Services and Integration layers

These layers are logging all errors and exceptions that might occur, but also some successful messages (like creating a message or a message binary successfully, or the duration of JMS message processing). If the processing chain is completed without error, a final success log is created.

For successful message creation, the logs can contain the following information

·  document type code

·  transaction id

·  message id

·  sender id

·  binary message size

·  binary message id

The final success log contains all available information

·  the business correlation id

·  the business domain id of the parties

·  the message id

·  the message document id

·  the transaction id

·  the document type code

·  the issuer party id

·  the receiver party id

·  the sender party id

·  a short description ("Message processed successfully" for example)

All exceptions and errors logged contain the error message, and can also contain additional information for an easier identification of the problem. This additional information may contain the following, when available to the system

·  the business correlation id

·  the business domain id of the parties

·  the message id

·  the message document id

·  the transaction id

·  the document type code

·  the message binary id

·  the ids of the issuer, sender and receiver parties

·  page URL

For message dispatching, the application also logs the endpoint URL and the destination queue.

Logging Summary Page 5 / 5