Setup Functions for Application Logging
You define which actions, executed by a user or the system in a specific application, should be logged.
To determine which actions of an application should be logged and how the resulting messages should be compiled in logs, you define Logging Configurations and Logging Profiles.
Integration
Event management is the basis for application logging, in particular the asynchronous processing of events, triggered by the actions of the user or the system in the logging applications.
See Event Management
Note
Asynchronous processing of events triggered by the user can minimize the impairment of the response time caused by application logging. Asynchronous processing means that, in the dialog process which the individual user is operating, the system only executes the checks and actions which are necessary to ensure later processing. Following these checks the system continues the relevant program logic of the application.
Features
In general, the setup functions for application logging in i.s.h.med involve the following settings:
A logging configuration always refers to a specific logging application and contains the definition for which events and with which filter criteria application logging is executed.
A logging profile comprises a quantity of logging configurations.
Scheduling of a background process which processes the messages.
Furthermore the business add-in (BAdI) N1_ALENTRY_FINALIZE
(enhancement spot N1_ALENTRY_FINALIZE
) with the FINALIZE_ALENTRY
method is available. When a new message is logged, the system calls this enhancement spot.
You can find detailed information about this Business Add-In (BAdI) in the Implementation Guide
under 
Industry-Specific Component Clinical System
Cross-Application Settings
Event Management
Application Logging
BAdI: Design Log Entries in Application Logging
.