Basic Settings for Application Logging
In order to be able to use i.s.h.med application logging, you must execute the application logging basic settings thereby activating application logging.
If application logging is not activated, no logging will take place on this client.
You make the basic settings in the implementation guide
under .
Here you can activate application logging with a switch. To do this you select the menu option and set the App.Log. Active
indicator.
Note
As long as you have not activated application logging using this switch, no logging will take place on this client. Regardless of this switch you can configure Logging Profiles and Logging Configurations. You can therefore prepare and configure logging, but guarantee that no logging entry is written during configuration.
In the application logging basic settings you can also define that application logging should be executed asynchronously. This means that application logging does not take place during the user execution in the dialog, but the system temporarily saves the events. You can process these events later at a time convenient to you using a background process.
You activate asynchronous processing as follows:
In transaction N1EVDEF
choose to call a dialog box in which you can activate the Asynchronous Processing
option. You therefore define that you allow asynchronous processing of events.
In the implementation guide
select . The Change Logging Definitions
screen appears (transaction N1ALDEF
). Use the menu option to select the AppLog Asynchron.
option, to determine that application logging should take place asynchronously.
You can change these options during system operation.
Note
You should note that these basic settings are deliberately not connected to the transport system. If you transport a functioning setting from a test system to a productive system, you must separately adapt these basic settings on the target system. This has the advantage that you can select different basic settings in the test and productive systems.