The <<Logger>> adapter also writes transactional logging information via a queue asynchronously into the transaction log file of the xUML service. The logged information is usable for performance measurements or statistical evaluations (how often has the transaction been called, in which context, etc.). On the E2E Bridge, the transaction log level needs to be set at least to Custom. For more information about the transaction log levels see Transaction Log Levels of an xUML Service.
The following picture shows the usage of the <<Logger>> adapter for this case.
Figure: Writing into the Transaction xUML Service Log
Figure: Logger Tag action
The Tag action of the logger adapter needs to be set to report. The following input can be provided:
Object Name | Type | Description | Field in Transaction Log |
---|---|---|---|
state | Boolean | true or false. This will result in setting the status field in the log entry to OK respectively ERROR. | State |
domain | String | self-defined name of the domain of the logged entry | Domain |
parameter | String | self-defined parameter | Parameter 2 |
description | String | description for the log entry | Parameter 1 |
timestamp | DateTime | Bridge 7.0.0-beta2 custom timestamp. This parameter is optional. If it is not given, the timestamp in the transaction log will be generated from the current timestamp. | Date, Time |
Example
set state = true; set description = "Example log entry for transaction log"; set domain = "Example Transaction"; set parameter = "counter = 3"; set timestamp = currentDateTime();
The output after running the example can be found in the xUML Service Transaction Log on the E2E Bridge.
Overview
Content Tools