on 06-19-2008 6:08 PM
Diff bteween trace,log and audit log....?
Harsha
Log file:
A log file contains generally intelligible information for system
administrators. The information is sorted by categories and is used for
system monitoring. Problem sources or critical information about the status
of the system are logged in this file. If error messages occur, you can
determine the software component that has caused the error using the
location. If the log message does not provide enough details to eliminate
the problem, you can find more detailed information about the error in the
trace file.
The log file is located in the file system under
"/usr/sap/[SID]/[instance]/j2ee/cluster/server[N]/log/applications.[n].log"
for every N server node.
Access the file with the log viewer service of the J2EE visual
administrator or with the standalone log viewer.
Trace file:
A trace file contains detailed information for developers. This information
can be very cryptic and extensive. It is sorted by location, which means by
software packages in the Java environment, for example, "com.sap.aii.af".
The trace file is used to analyze runtime errors. By setting a specific
trace level for specific locations, you can analyze the behavior of
individual code segments on class and method level. The file should be
analyzed by SAP developers or experienced administrators.
The trace file is located in the file system under
"/usr/sap/[SID]/[instance]/j2ee/cluster/server[N]/log/defaultTrace.[x].trc"
for each N server node.
Access the file with the log viewer service of the J2EE visual
administrator or with the standalone log viewer.
Audit log
The audit log is a subcomponent of the XI 3.0 adapter framework messaging
system. It contains information about the status of an XML message in the
messaging framework. It logs the current status of the message at fixed
control points while the message is processed. If an error occurs during
the processing, you can narrow down the location of the problem by
analyzing the audit log.
The audit log contains generally intelligible information. It is accessed
with the "Details" pushbutton in the message display tool (MDT). The system
administrator should always analyze the audit log first.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"Trace", "log" and "audit log" are used for monitoring and troubleshooting the XML message flow in the SAP XI adapter framework. When you administer the system, you should access them in the following sequence:
1. Audit log
2. Log file
3. Trace file
Log file:
A log file contains generally intelligible information for system administrators. The information is sorted by categories and is used for system monitoring. Problem sources or critical information about the status of the system are logged in this file. If error messages occur, you can determine the software component that has caused the error using the location. If the log message does not provide enough details to eliminate the problem, you can find more detailed information about the error in the trace file.
The log file is located in the file system under
"/usr/sap/[SID]/[instance]/j2ee/cluster/server[N]/log/applications.[n].log" for every N server node.
Access the file with the log viewer service of the J2EE visual administrator or with the standalone log viewer.
Trace file:
A trace file contains detailed information for developers. This information can be very cryptic and extensive. It is sorted by location, which means by software packages in the Java environment, for example, "com.sap.aii.af". The trace file is used to analyze runtime errors. By setting a specific trace level for specific locations, you can analyze the behavior of individual code segments on class and method level. The file should be analyzed by SAP developers or experienced administrators.
The trace file is located in the file system under
"/usr/sap/[SID]/[instance]/j2ee/cluster/server[N]/log/defaultTrace.[x].trc" for each N server node.
Access the file with the log viewer service of the J2EE visual administrator or with the standalone log viewer.
Audit log
The audit log is a subcomponent of the XI 3.0 adapter framework messaging system. It contains information about the status of an XML message in the messaging framework. It logs the current status of the message at fixed control points while the message is processed. If an error occurs during the processing, you can narrow down the location of the problem by analyzing the audit log.
The audit log contains generally intelligible information. It is accessed with the "Details" pushbutton in the message display tool (MDT). The system administrator should always analyze the audit log first.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Audit Log :The adapter engine uses the messaging system to log the messages at every stage, This log is called the Audit Log.
The audit log can be viewed from the runtime work bench(RWB) to look into the details of the life cycle of the message. During our journey we will also have a look at the messages that are logged at different stages.
Audit logs are mainly used to trace our messages. In case of any failures, we can easily trace where message stands. we can give the entries for the logs in UDFs, custom modules etc..
Audit logs are generally gives us the sequence of the steps from where the message is picked up with file name and path and how the message is sent to the I.E pipeline..it also shows the status of the message like DLNG,DLVD like that...generally we look into the audit logs if there are any errors in message processing...
It gives the complete log of your message.
Go to RWB --> Component Monitoring --> Adapter Engine --> Communication channel Monitoring --> Select the Communicatin channel --> click on use filter --> then click on the Message Id.
Trace Log:
Log file:
A log file contains generally intelligible information for system administrators. The information is sorted by categories and is used for system monitoring. Problem sources or critical information about the status of the system are logged in this file. If error messages occur, you can determine the software component that has caused the error using the location. If the log message does not provide enough details to eliminate the problem, you can find more detailed information about the error in the trace file.
The log file is located in the file system under
"/usr/sap/SID/instance/j2ee/cluster/server[N]/log/applications.[n].log" for every N server node.
Access the file with the log viewer service of the J2EE visual administrator or with the standalone log viewer.
Trace file:
A trace file contains detailed information for developers. This information can be very cryptic and extensive. It is sorted by location, which means by software packages in the Java environment, for example, "com.sap.aii.af". The trace file is used to analyze runtime errors. By setting a specific trace level for specific locations, you can analyze the behavior of individual code segments on class and method level. The file should be analyzed by SAP developers or experienced administrators.
The trace file is located in the file system under
"/usr/sap/SID/instance/j2ee/cluster/server[N]/log/defaultTrace.[x].trc" for each N server node.
Access the file with the log viewer service of the J2EE visual administrator or with the standalone log viewer.
Thanks
Virkanth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.