The Analyzer allows you to test all exposed operations of an xUML service on the fly via a SOAP interface and to work with any backends (for example, databases or web services). It traces the execution path of a deployed xUML service, and you can review this trace graphically in order to debug your service or verify its correct functionality.
The xUML Trace Analyzer is the interface to the tracing feature. With the Trace Analyzer you can test
-
each operation defined on a port type of an xUML service
-
class operations of classes that have been marked as to be testable
The tracing data can be collected synchronously or asynchronously and is stored per test run into a separate XML file.
Kubernetes Setup
In this setup, the trace files are stored to MinIO (S3):
-
The maximum storage space for tracing information is 10 GB. If this limit is exceeded, no traces can be stored anymore, and errors are reported in the Analyzer.
This ensures that sufficient free memory space is available for the correct operation of PAS at any time. -
By default, the trace files expire after 14 days. Files that are older than 14 days are automatically removed from MinIO (S3).
-
The trace file retention time can be configured on your PAS instance. Please contact our support if you want to change the default configuration.
Docker Setup
In this setup, the trace files are stored to the file system.
-
By default, the trace files expire after 7 days. Files that are older than 7 days are automatically removed from the file system.
-
The trace file retention time can be configured on your PAS instance. Please contact our support if you want to change the default configuration.
-
Synchronous tracing
Send calls to services and inspect immediate results, see Synchronous Tracing with the xUML Trace Analyzer. -
Asynchronous tracing
Trace service calls asynchronously with a focus on event-driven, queued, or process-centric scenarios, see Asynchronous Tracing with the xUML Trace Analyzer.