Show TOC

Logging and TracingLocate this document in the navigation structure

Use

Logging and tracing is essential for analyzing problems. It is offered for all components required for SAP NetWeaver PI.

Components Based on AS ABAP

The Integration Engine uses logging and tracing to log and analyze the processing steps of messages.

While a message is being processed by the pipeline of the Integration Engine, the current status of the message is logged as a separate message version (log version).

Traces in XML format are attached to the message and the entire message is saved (persisted) in the database. No message data is persisted in the file system.

You can view message log versions and traces by using the message monitor of the Integration Engine.

More information: Logging and Tracing

Components Based on AS Java

The Java-based parts all use the standard logging of AS Java. This can be configured by using the log configuration function of the SAP NetWeaver Administrator under Start of the navigation path Problem Management  Next navigation step  Logs and Traces  Next navigation step  Log Configuration End of the navigation path (alias: /nwa/log-config ).

On the Integration Server host (Enterprise Services Repository and Integration Directory may be installed on another server), <Javadir> stands for the following in the table below (where n specifies the number of cluster nodes):

/usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/server<n>

Log and trace files (where n specifies the number of files):

Content

File

Path

Default server trace

defaultTrace<n>.trc

<Javadir>/log

Tracing is activated by default. To change the preset trace level, perform the following steps:

  1. Call Log Configuration .

  2. Show the Tracing Locations .

  3. Select a location.

  4. Change the Severity to the required value.

Available locations in the default server trace are:

Component

Location

Enterprise Services Repository

com.sap.aii.ib

com.sap.aii.ib com.sap.aii.ibrep

com.sap.aii.ib... (sources used by ESR & Directory because of shared Framework)

  • sbeans.* (Beans)

  • client.* (Client)

  • gui.* (UI Classes)

  • core.* (Classes for Server+Client)

  • server.* (Server)

  • web.* (Servlets)

  • com.sap.aii.utilxi.* (Utility classes of Framework - used by ESR & Directory)

com.sap.aii.ibrep

Enterprise Services Repository Object Types

com.sap.aii.ibrep.server.persist.alert com.sap.aii.ib.bom.bpm.* com.sap.aii.ibrep.gui.bpm.* com.sap.aii.ibrep.server.persist.bpm.*

Enterprise Services Repository User interface elements for conditions, expressions and properties

com.sap.aii.ib.bom.condition.xi71.*

com.sap.aii.ib.bom.gen.container.*

com.sap.aii.ib.bom.gen.property.*

com.sap.aii.ib.gui.condition.freetexteditor.*

com.sap.aii.ib.gui.container.*

com.sap.aii.ib.gui.extractor.*

com.sap.aii.ib.gui.propertyview.*

Integration Directory

com.sap.aii.ib

com.sap.aii.ibdir

com.sap.aii.ibdir.sbeans.* (Beans)

com.sap.aii.ibdir.client.* (Directory Client)

com.sap.aii.ibdir.gui.* (Directory UI Classes)

com.sap.aii.ibdir.core.* (Classes for Server+Client)

com.sap.aii.ibdir.server.* (Directory Server)

com.sap.aii.ibdir.web.* Servlets

Mapping Runtime

com.sap.aii.ib

com.sap.aii.ibrun

Runtime Workbench

com.sap.aii.mdt

com.sap.aii.rwb

Adapter Engine

com.sap.aii.af

com.sap.aii.adapter

Adapter Framework security

com.sap.aii.security

Messaging runtime

com.sap.engine.messaging

Proxy Framework

com.sap.aii.proxy

Proxy Runtime

com.sap.aii.proxy.xiruntime

General adapter locations

com.sap.aii.adapter* (rnif, rnif11, cidx, bc, mail, file, jdbc)

RFC, JMS, JDBC, File adapters

com.sap.aii.af.service*

RFC adapter

com.sap.aii.af.rfc

SOAP and Mail adapter

com.sap.aii.af.sdk

SOAP adapter

com.sap.aii.af.mp.soap

Additional locations for RNIF adapters and CIDX adapter

com.sap.aii.af.sdk.*(rnif,rnif11,cidx)

com.sap.aii.af.protocol.ispeak

XML validation

com.sap.aii.utilxi.xml

User-defined message search

com.sap.aii.af.service.search

Java Web services runtime

com.sap.engine.services.webservices.*

com.sap.engine.interfaces.webservices.*

Logging is activated by default. To change the preset log level, perform the following steps:

  1. Call the Log Configuration .

  2. Show the Logging Categories .

  3. Choose Start of the navigation path ROOT CATEGORY Next navigation step Applications  Next navigation step  Exchange Infrastructure  Next navigation step  Adapter End of the navigation path or Adapter Framework .

  4. Navigate to the required category and choose it.

  5. Change the Severity to the required value.

Old logs are compressed (zipped up) to save disk space. By default, logs are written to a maximum of five files with 10 MB capacity of each file. Thus, when this set of five files is full, the system rotates back to the first file and starts overwriting the old logs. Before overwriting the old logs, the log configuration function backs up the five files into a zip file. So, each zip file contains a set of five log files. The logs within these zip files are called archive logs.

You can view traces, log files, and archive logs by using the log viewer function of the SAP NetWeaver Administrator under Start of the navigation path Problem Management  Next navigation step  Logs and Traces  Next navigation step  Log Viewer End of the navigation path (alias: /nwa/logs ).

More information: Log Viewing .

Available logging categories under :

Start of the navigation path ROOT CATEGORY Next navigation step Applications  Next navigation step  ExchangeInfrastructure  End of the navigation path

Logging Categories

Description

→ Adapter

Sample adapter for adapter development

→ AdapterFramework → AdapterEngine → ModulesRoot → MODULE_PROCESSOR

Module processor

→ AdapterFramework → ResourceAdapter → AFWServlet

HTTP access to Adapter Framework messaging system

→ AdapterFramework → ResourceAdapter → Bc

SAP Business Connector adapter

→ AdapterFramework → ResourceAdapter → Rfc

RFC adapter

→ AdapterFramework → SAPLibraries → SAPXDK

Access to PI message object during runtime

→ AdapterFramework → Services → ADAPTER → ADMIN → Conversion

CSV conversion of file adapter

→ AdapterFramework → Services → ADAPTER → ADMIN → File

File adapter

→ AdapterFramework → Services → ADAPTER → ADMIN → JDBC

JDBC adapter

→ AdapterFramework → Services → ADAPTER → ADMIN → JMS

JMS adapter

→ AdapterFramework → Services → ADAPTER_APPLICATION

Conversion module application in module processor

→ AdapterFramework → Services → AuditLog

Audit log application

→ AdapterFramework → Services → CPACache

Adapter Framework Integration Directory cache

→ AdapterFramework → Services → Licence

Adapter Framework licensing service

→ AdapterFramework → Services → MP

Adapter Framework modules in Module Processor

→ AdapterFramework → Services → SLD

Adapter Framework access service to System Landscape Directory (SLD)

→ AdapterFramework → Services → TREX

Adapter Framework access service to TREX

→ AdapterFramework → Services → Util

Adapter Framework utilities

→ AdapterFramework → ThirdPartyRoot

Optional category for partner adapters

Adapter Engine (Java SE)

The Adapter Engine (Java SE) includes the File/FTP, JMS, JDBC, and SOAP adapters.

In the following table, <Javadir> stands for the directory where the Adapter Engine is installed.

Note

Multiple Adapter Engines (Java SE) can be installed in one process integration landscape.

Trace Files:

Content

File

Path

Technical logging information for all installed adapters

adapter_1.log

adapter_2.log

adapter_3.log

adapter_4.log

adapter_5.log

<Javadir>/tech_adapter/LOGFILES

You can view the log on the host that runs the Adapter Engine by choosing Traces from the main menu under the following HTTP address:

<Adapter Engine host>:<port>

You can set the trace level under the same HTTP address. Select the adapter in question under Available Adapters and then choose Configure .

The default logging settings produce a set of five trace files, each 2 MB in size. These files are used in rotation for logging, effectively limiting the file system space used for log files to 10 MB. The file names above represent the default logging settings.

Note

Trace level INFO is recommended for productive use.

The trace files can be viewed under the same HTTP address by choosing available trace files under Traces in the main menu.