Versions Compared

Old Version 10

changes.mady.by.user Annegret Bernhardt

Saved on

compared with

New Version 11

changes.mady.by.user Kirstin Seidel-Gebert

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: xuml_standard_log_levels, xuml_transaction_log_levels

...

Table Filter
inverse,,,
ddSeparator‚‚
sparkNameSparkline
columnChapter,Name,Excerpt
isNewtrue
limitHeight
sortChapter ⇧,Name ⇧
separatorPoint (.)
labels‚‚‚
ddSeparatorstrue
default,,,
isFirstTimeEntertrue
ddOperator,,
cell-width,,,
datepatterndd M yy
globalFiltertrue
id1639556948101_752411974
worklog365|5|8|y w d h m|y w d h m
isORAND
order0,1,2,3


NameExcerptDocumentationsUsage (Link)
click_to_see_gif


Multiexcerpt
MultiExcerptNameclick_to_see_gif


Tip

Click the image to see an animated version.



  • API Management Guide
  • Academy (Designer Tutorial)
click_to_see_gif_above


Multiexcerpt
MultiExcerptNameclick_to_see_gif_above


Tip

Click the image above to see an animated version.





info_grey_sample_data


Multiexcerpt
MultiExcerptNameinfo_grey_sample_data


Info

Sample data is displayed in gray .



  • Designer Guide
xuml_standard_log_levels


Multiexcerpt
MultiExcerptNamexuml_transaction_log_levels
shouldDisplayInlineCommentsInIncludesfalse

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.

Log LevelDescription
NoneNo 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.

WarningLog warnings.

Warnings indicate unexpected but non-critical situations that do not interrupt normal operation.

InfoLog 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.

Note
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.



Tip

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]



  • Designer
  • Administration
xuml_transaction_log_levels


Multiexcerpt
MultiExcerptNamexuml_transaction_log_levels
shouldDisplayInlineCommentsInIncludesfalse

You can set the following transaction 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.

Log LevelDescription
NoneNo logging executed.
Custom

Log everything that is written by the logger adapte-

For more details, see Logger.

ServiceLog the start and the end of calls to a service operation (service interface).For example, calls to SOAP, SAPRFC, or HTTP operations.
IOExternalLog 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.
IOInternalLog also calls of adapters to internal (local) resources.E.g. Filesystem Adapter.

Logging also includes start and end time of service calls and can be used to analyze process performance.


  • Designer
  • Administration

xuml_transaction_log_levels


Multiexcerpt
MultiExcerptNamexuml_transaction_log_levels
shouldDisplayInlineCommentsInIncludesfalse