Logging 
Use
Logging is used to log the processing steps of XML messages in the Integration Engine.
Integration
The logging mechanism is implemented during configuration of the Integration Engine. However, you can also set it externally (using the message header or in the settings for troubleshooting), as long as no setting was made during configuration.
Features
Logging logs the status of XML messages to be processed prior to the first processing step (inbound message) and after each pipeline service call. The entire message, including information regarding the processing status, is saved (persisted). Persisted XML messages can then be used for evaluation purposes as part of monitoring.
Activities
There are multiple levels of logging available in the Integration Engine. The following logging variants are possible; the sequence of the variants displayed corresponds to the overriding hierarchy of the logging mechanism:
· You can switch logging on or off for a particular pipeline, or you can choose Definition in Another Location.
This is setting for the pipeline itself. Logging can be activated or deactivated for the entire pipeline, which means that all service calls are either subject to logging or not.
· You can switch logging on or off for a particular pipeline element, or you can choose Definition in Another Location.
This makes sense if individual execution steps of a pipeline are to be logged only. Make a selection in the field Logging for PL Element.
If you activate or deactivate logging for the entire pipeline at a later point, the settings at pipeline element level have no effect.
If you choose Definition in Another Location, you can activate or deactivate logging using a switch in the message header.
· Logging is set externally using the message header or using the settings for error handling.
This is the lowest hierarchy level. This setting is only relevant if logging is not activated or deactivated explicitly at pipeline, or pipeline element level.
This means, for example, that no logging takes place if the logging is activated within the message, but is deactivated explicitly for the pipeline in the configuration.
If logging is set by the caller, the logging information is part of the XML message header.
¡ <SAP:Logging>1</SAP:Logging>
Activates logging explicitly.
¡ <SAP:Logging>0</SAP:Logging>
Deactivates logging explicitly.
If logging is set in the settings for troubleshooting, it is part of a conditioned action defined there.
The logging hierarchy is clarified using the following table:
|
Pipeline |
PL Element |
Message |
Logging |
|
yes |
any |
any |
yes (for the entire pipeline) |
|
no |
any |
any |
no (for the entire pipeline) |
|
-- |
yes |
any |
yes (for a selected pipeline element) |
|
-- |
no |
any |
no (for a selected pipeline element) |
|
-- |
-- |
yes |
yes (for the entire pipeline) |
|
-- |
-- |
no |
no (for the entire pipeline) |
|
-- |
-- |
-- |
no (for the entire pipeline) |
The first three columns represent the respective logging variants with the possible settings.
· Pipeline or PL Element means that the setting you made at configuration time was made for the entire pipeline or for the respective pipeline element.
· Message means that the setting in the message header was made by the sender or using the settings for troubleshooting.
The last column specifies if logging takes place and in what form.
The following are possible settings:
|
yes |
Logging activated explicitly |
|
no |
Logging deactivated explicitly |
|
any |
Any setting (yes or no, depending on the configuration) |
|
-- |
No explicit settings (definition in another location) |
