Logging and Tracing (SAP Library - Technical Operations for SAP NetWeaver)

Logging and Tracing

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

Components Based on Usage Type 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.

For more information, see Logging and Tracing

Components Based on Usage Type AS-Java

The J2EE parts, that is the Integration Builder (IB), the Adapter Engine (AE), and the Runtime Workbench (RWB), as well as the System Landscape Directory (SLD), all use the standard logging of the SAP NetWeaver J2EE Engine. This can be configured by using the Log Configurator service in the Visual Administrator.

On the Integration Server host (Integration Repository and Integration Directory may be installed on another server), <J2EEdir>stands for the following in the table below:

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

Log and Trace Files:

Content	File	Path
Technical trace information	tracefile.txt	<J2EEdir>/services/servlet_jsp/work/jspTemp/ MessagingSystem/root/admin/
Application log specific to usage type PI	xi.log	<J2EEdir>/log/applications/com.sap.xi
Default server trace	defaultTrace.trc	<J2EEdir>/log

Tracing is not activated by default. To activate tracing, perform the following steps:

...

1. Call the Log Configurator service.

2. Switch to advanced mode.

3. Select the Location tab page.

4. Select a location.

5. Change the Severity from None to the required value, for example, Debug.

Available Locations:

File: defaultTrace.trc

Path: <J2EE>/log

Component	Location
Integration Repository	XIREP
Integration Repository Integration Processes	com.sap.aii.ib.bom.bpm.* com.sap.aii.ibrep.gui.bpm.* com.sap.aii.ibrep.server.persist.bpm.*
Integration Repository User interface elements for conditions, expressions and properties	com.sap.aii.utilxi.swing.framework.propertysheet.* com.sap.aii.ib.gui.condition.* com.sap.aii.ib.bom.condition.*
Integration Directory	XIDIR
Mapping Runtime	XIRUN
Runtime Workbench	XIRWB /Applications/ExchangeInfrastructure/RuntimeWorkbench
Adapter Engine	com.sap.aii.af
Adapter Framework Security	com.sap.aii.security
Messaging Runtime	com.sap.aii.messaging
Proxy Framework	com.sap.aii.proxy.framework
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

Available Locations for PCK:

File: defaultTrace.trc

Path: <J2EE>/log

Component	Location
PCK	com.sap.xi.pck*
Adapter Framework	com.sap.aii.af*
Adapters	com.sap.aii.adapter* (bc, mail, file, jdbc) com.sap.aii.af.service* (rfc, jms, jdbc, file) com.sap.aii.af.mp.soap SOAP) com.sap.aii.af.rfc (RFC)
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
Monitoring	com.sap.aii.mdt*

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

...

1. Call the Log Configurator service.

2. Select the Categories tab page.

3. Choose Applications → Exchange Infrastructure.

4. 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 10MB capacity of each file. Thus, when this set of five files are full, it will rotate back to the first file and start overwriting the old logs. Before overwriting the old logs, the Log Configurator service 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 service in the Visual Administrator. For more information, see the SAP J2EE Engine Administration Manual under Log Viewer.