X3 session logs
| Administration Page | Application/Contract | Syracuse/Collaboration | Class | x3ClientLogs | Representation | x3ClientLog |
|---|
Introduction
For debugging purposes, this feature enables to define and activate X3 session logs. Logs are generated in the runtime/logs directory of the runtime managing the session.
Description
The X3 session log screen includes the following fields:
| Label | Description | Enabled | Enabled | Type | Level |
File
Label
Defines the code of the logs.
Description
A user-friendly name to identify the logs.
Enabled
Defines if the logs can be generated based on the target.
An enabled log can't be modified. To do so, you need to stop the current log, modify it, and enable it again.
MaxLogTime
Defines the time in minutes after which the log will be automatically stopped.
Target
Defines the kind of use cases to be tracked. The logs will be triggered if the use case meets the target.
Type
Defines the type of logs. It can be one of the following:
Batch administration
To track the session used for the batch administration. The batch server to track has to be specified.
Batch query
To track batch query execution. The batch server has to be specified.
The X3 user login, task code, and task number can be specified.
Web service
To track web service execution. The used endpoint has to be specified.
The web service, SOAP pool, and user can be specified.
Representation
To track a representation (sdata) execution. The used endpoint has to be specified.
The entity and user can be specified.
Function (classic page)
To track a classic function. The used endpoint has to be specified.
The classic function and user can be specified.
Levels selection
Level
Defines the log levels. You can add as many codes as needed.
The levels summary is the sum of the values related to the selected levels.