You can use the information that is logged to the transaction log for performance measurements or statistical evaluations (for instance, how often the transaction has been called, in which context, etc.). There is one log file per day or one per hour – depending on what has been configured in the transaction log rotation interval of the service preferences (see Preferences of an xUML Service). The amount of data that is logged depends on the selected transaction log level (see Transaction Log Levels).

BRIDGE > xUML Service Transaction Log > xml_service_transaction_log.png

How to search the logfiles is explained in detail on Logging of xUML Services.

Usually, you will not analyze the transaction log within the Bridge, but download the log file. Then you can have a look at it either in Excel ...

BRIDGE > xUML Service Transaction Log > xuml_service_transaction_log_excel.png

... or analyze it with the Analyzer.

BRIDGE > xUML Service Transaction Log > xuml_service_transaction_log_analyzer.png

Transaction ID

The Transaction ID is a unique number used to trace service calls through the call stack of multiple service calls.

SOAP clients calling a service running on the Bridge can provide a transaction ID in the SOAP header. This ID will be passed on through the call stack of the xUML service, so that the whole transaction can be traced. When analyzing the log file in case of error, this can be useful.
If an xUML service is called without providing a transaction ID, the E2E Runtime will generate such an ID and pass it on to other xUML services being called.

In the Analyzer, the transaction log will be sorted by transaction ID. You can expand the tree of a transaction ID to inspect the sequence diagram of this transaction in the panel on the right.

BRIDGE > xUML Service Transaction Log > xuml_service_transaction_log_transaction_id.png

While modeling services with MagicDraw and Builder, you have access to the received transaction ID and you can pass it on in your service model.