Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-XI-IS-IEN (Application Component) Integration Engine⤷
SXMSF (Package) XI: Integration Engine Runtime
Basic Data
| Data Element | SXMSLOG |
| Short Description | Integration Engine: Logging |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SXMSLOG | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Logging |
| Medium | 15 | Logging |
| Long | 20 | Logging |
| Heading | 20 | Logging |
Documentation
Definition
Logging for the Integration Engine can be activated in different locations.
The following logging variants are possible:
- Logging is activated for the entire Integration Engine (client)
In this case, logging is activated for all pipelines of an Integration Engine, in other words, all service calls of all pipelines in this Integration Engine are subject to logging.
Use the configuration parameter LOGGING in the category RUNTIME.
The configuration parameter LOGGING_PROPAGATION in the category RUNTIME enables you to activate logging globally. Processing of a message is then subject to logging from start to finish in all involved Integration Engines.
- Logging is activated for particular pipeline services
If you only want to log particular execution steps of a pipeline, select the relevant subparameter of the parameter LOGGING to set logging for particular pipeline services.
If you activate logging for the entire Integration Engine at a later date, then the settings at pipeline-service level are not included.
- Logging is set externally in the message
This settings means that this message is still subject to logging, even if logging is explicitly deactivated in the configuration settings. The logging information is then a part of the message header.
- <SAP:Logging>1</SAP:Logging> activates logging explicitly
- <SAP:Logging>0</SAP:Logging> deactivates logging explicitly
- Logging is set externally by the settings for error analysis
Logging is then only part of a conditioned action defined there. The message is still subject to logging even if it is explicitly deactivated in the configuration settings.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 620 |
