Page History
| Div | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
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).
How to search the logfiles is explained in detail on Logging of xUML Services.
The transaction log contains the following information:
...
Elapsed time, for each call (service calls, external or internal calls) in milliseconds.
If the elapsed time is displayed as "0", the logged step has taken below 1 millisecond of time. The value of elapsed time does not contain:
before
SERVICE_ENTERreading the request data from the network
parsing the request body (e.g. SOAP)
after
SERVICE_EXITcreating the response (e.g. SOAP)
sending the response to the client
...
36
...
- If an adapter has been called, the domain fields contains a value denoting the adapter, for instance SAPRFC, SQL, FILE, SYSAD, POP3, URL, etc.
- If a service operation has been called, the value is INTERFACE.
- If a log entry has been triggered by the user via the logger adapter, the value was defined in the UML model.
...
INTERFACE
...
- SERVICE_ENTER or SERVICE_EXIT, if the logging concerns the service call.
- TRANSITION_ENTER or TRANSITION_EXIT, if the logging concerns persistent state handling.
- IO_ENTER or IO_EXIT, if the logging concerns service adapter calls.
- If the logger adapter triggered the log entry, the value is CUSTOM.
...
SERVICE_EXIT
...
- Parameters, for instance, if the file system adapter has been called, the first parameter corresponds to the executed action (e.g. ReadDirectory) and the second one to the specified file.
- If the logger adapter triggered the log entry, the first parameter corresponds to the description defined as input for the adapter in the UML model.
...
anonymous 2.0.232.75
| Multiexcerpt include | ||||
|---|---|---|---|---|
|
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 ...
... or analyze it with the Analyzer.
Transaction ID
| Multiexcerpt-include |
|---|
...
...
The Transaction ID is a unique number used to trace service calls through the call stack of multiple service calls.
...
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.
While modeling services with MagicDraw and Builder, you have access to the received transaction ID (getTransactionID) and you can pass it on in your service model.
| Panel | ||
|---|---|---|
| ||
|
| Panel | ||
|---|---|---|
| ||
Overview
Content Tools