Show TOC Entering content frame

This graphic is explained in the accompanying text Log and Trace Output Locate the document in its SAP Library structure

Use

SAP provides a common framework for JAVA applications to incorporate logging and tracing options. This has two aspects, sending the log and trace output to the destination file and displaying the contents of the log file.

To use the log and trace option, choose  Settings ® Logging and Tracing

Creating the Log and Trace output: The Intelligence Connector directs the log and trace to the console of the J2EE engine or an output file. To do this, the application provides a JAVA server page where you can define the filters that control the information that flows to the output file. These filters are stored in a configuration file that can be maintained in the JAVA server page. The configuration file with default filters is available with the installation.

To view the current filter settings in the text area provided, use the Load option. You can change the message severity for logging and tracing output to NONE, DEBUG, PATH, INFO, WARNING, ERROR, FATAL or ALL for different packages. For all packages log and trace messages are implemented in application but it sends only those messages that have a severity higher than or equal to the one defined in the settings for the package. Setting the severity to NONE would stop the logging and tracing activity.

After creating the settings, you must specify the output file name in the Log File option.  A series of log files are created with a suffix <SequenceNumber>.log added to the file name that you have mentioned. For example, if you have entered the complete file name as C:\aaplos\Aap, then the log files created would be C:\aaplogs\Aap.0.log, C:\aaplogs\Aap.1.log, …, Cc:\aaplogs\Aap.9.log. The log files will be created on a rotation basis from 0 through 9. Once a log file reaches a maximum size, the next file will be created. After the last index file (that is, Aap.9.log) has reached the maximum size, the cycle will use the index 0 again.

Save and Apply the changed settings in the configuration file and start logging and tracing activity. If you have not specified the Log file, then the output is directed to the console of the J2EE engine.

Viewing the Log and Trace output: To view the log file, use the log viewer through the Computing Center Management System (CCMS) monitoring. You can start CCMS in the CRM System using the transaction CCMS Monitor Sets: Maintenance Functions (RZ20). Fur further information, see SAP Service Marketplace (http://service.sap.com/monitoring).

For this, you can use the two configuration files, the sapccmsr.ini which is the standard file for CCMS integration and an application specific configuration file, the aaplogs.ini file specific to the Intelligence Connector. The aaplogs.ini file must be populated with the same file name and directory with a wildcard as specified for the log file in the logging and tracing JAVA Server Page. The wildcard would be required to display all generated log files.

For example, if file name specified is C:\aaplogs\Aap, then the directory will be C:\aaplogs and file name will be Aap*.log, to display the file C:\aaplogs\Aap.0.log, c:\aaplogs\Aap.1.log and so on. The path of the AAPLOGS.ini file has to be registered in the sapccmsr.ini file as an entry shown below.

#LogFile <full path of logfile template>

LogFile <full path of AAPLOGS.ini file>

You can also specify filter information for the alerts and color codes in the aaplogs.ini file. This filter controls the information that is sent to the log viewer from the output log file. You must register the path of the aaplogs.ini file in the sapccmsr.ini file. The sapccmsr.ini file has a standard location and the CCMS log viewer fetches the location of the aaplogs.ini file from which it gets the output log file destination to read the logs.

Leaving content frame