Versions Compared

Old Version 1

changes.mady.by.user Kirstin Seidel-Gebert

Saved on

compared with

New Version 2

changes.mady.by.user Kirstin Seidel-Gebert

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space WBRIDGE and version 7.2.0

...

The transaction log contains the following information:

FieldDescription 
Example
DateDate when request was received.Fields Date and Time are set automatically for system messages.
Custom log messages written with the Log Adapter or the report macro can contain a custom timestamp. This may result in log messages that are not sequential.		2018-06-06
TimeTime when request was received.08:02:45
Time ZoneTime zone offset+0200
Transaction IDUnique ID of transaction. It is used to trace service calls through the call stack (see Transaction ID managing_e2e_composite_services__1396).00000002d3b0bdc0000069ce00ff9700ea65376f
Request IDUnique ID of request. It will be reset when restarting the xUML service.101
Component NameName of component that has been requested (not the name of the xUML service).urn:Services.SupportCase.SupportAPI.supportcases.GET
Elapsed Time

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_ENTER

    • reading the request data from the network

    • parsing the request body (e.g. SOAP)

  • after SERVICE_EXIT

    • creating the response (e.g. SOAP)

    • sending the response to the client

36

StateState is either OK or ERROR.OK
Domain
  • 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

Log Type
  • 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

Parameter 1 and 2
  • 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

...

... or analyze it with the E2E Analyzer.

Transaction ID

Multiexcerpt
MultiExcerptNametransactionID

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 E2E 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 xUML Runtime will generate such an ID and pass it on to other xUML services being called.

In E2E 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 E2E Builder, you have access to the received transaction ID and you can pass it on in your service model.