Using the Technical Trace and Log
Use
The Adapter Framework trace and log interface has various mechanisms and general methods in its classes, which enable you to trace and log adapters.
Interface Overview
Characteristic |
Value |
Name |
Adapter Framework technical trace and log |
Purpose |
Writes entries to the SAP J2EE Engine logging tool and to the audit log, and creates time stamps for measuring performance |
Type |
Java library |
Technical name |
com.sap.aii.af.service.trace com.sap.aii.af.service.auditlog |
Certification |
Optional |
Syntax |
See Javadoc (.\index.html) package com.sap.aii.af.service.trace and audit log |
Integration
Use of the Adapter Framework trace and log interface is optional. If you do use this interface, you must fulfill the requirements for the following areas:
Features
The various different tools are contained in the following areas:
· SAP J2EE Engine Logging Tool
This mechanism provides functions for tracing and logging. Tracing gives details about where an error occurs and how often, while logging provides information about the functioning of a component on a detailed, technical level.
The term category is used if logging statements are written for a particular category of functions.
adapter.EISconnction
adapter.J2EEconnection
The term location is used when trace statements are created that enable processing code to be reconstructed.
The same terms are used in the method design of the technical trace and log interface.
· Adapter Framework Audits
The technical trace and log classes provide functions that enable audit entries to be written for a specific XI message. The entries document the message flow in the Adapter Framework. They are stored in the database that is used by the J2EE server.
· SAP J2EE Performance Trace Using JARM
When the inbound and outbound methods are executed, time stamps are filled that enable the performance of the Adapter Framework to be measured.
Connection to JCA Error Logging and Tracing Methods
The references refer to chapter 6.6 of the document J2EE Connector Architecture Specification, Final Version 1.0.
You can download this document at java.sun.com/j2ee/connector.
· If your adapter supports the Adapter Framework trace and log interface, it can ignore the received PrintWriter Character Output Stream.
· If the adapter supports JCA logging, only write JCA-related and no Adapter-Framework-related information to the log.
· If your adapter only supports the JCA logging method, it must write all its log statements to the Java PrintWriter object transferred by the J2EE JCA container. However, this mechanism is not sufficient for SAP certification.
· You can also choose to use neither the JCA logging method nor the Adapter Framework trace and log interface.
Use of the Adapter Framework trace and log interface is optional. However, if you do use it, all prerequisites described in the following sections must be fulfilled.