You can set the following log levels for each xUML service. The higher the log level, the more information is written to the log files. The log levels in the table below are cumulative and are ordered from the lowest to the highest log level. For each log level, also the information of the lower levels is logged.
Standard Log
Log Level
Description
None
No logging at all.
Fatal
Log fatal errors.
The service cannot continue its normal execution, e.g. due to repository errors, system limitations like no more available threads or memory. These errors need the intervention of an administrator to solve the problem.
Error
Log non-fatal errors.
These errors are not written if they are caught in the Designer service model, e.g. connection errors, wrong SQL statements, applying operations to invalid values, and so forth.
Warning
Log warnings.
Warnings indicate unexpected but non-critical situations that do not interrupt normal operation.
Info
Log general information.
This includes, for instance, which component is being started or stopped, loaded add-ons, licensing information, etc.
Debug
Log detailed trace information.
In addition to log level Info, detailed trace information is written into an error file specified in the error message. Furthermore, the full communication stream when using the URL or SOAP adapter is written to the xUML service standard log. For more details on debugging an xUML service, see xUML Service Dump.
Use this log level with care and only when investigating problems. As all tracing information has to be logged, it may result in significant loss of performance with increasing complexity of the deployed xUML service.
If an error occurred, a call stack is written into the error log exposing the path to the action state where the error occurred in the model. [2006-04-20 08:31:13 W. Europe Standard Time][Error] [Internal][FUASM][3][Division by zero - Callstack: calculate > Calculation > call_Division > Division > Divide]
Transaction Log
Log Level
Description
None
No logging executed.
Custom
Log everything that is written by the logger adapte-
Log the start and the end of calls to a service operation (service interface).
For example, calls to SOAP, SAPRFC, or HTTP operations.
IOExternal
Log calls of adapters that communicate with external systems.
External systems like SAP, SQL, SOAP, etc. For instance, the SQL queries that are sent to the database will be logged as well. Calls via the file system and system adapter are excluded.
IOInternal
Log also calls of adapters to internal (local) resources.