Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Index

Why do I need this guide?

In some components like here Web Channel you may be asked to create a log file. In that case support does not want the default trace. Default trace is just too big and contains all information from all installed components. Web Channel support wants only the log from a certain package or even class, which is usually com.sap.isa. You can use this guide not only for Web Channel. You can use it for every package or class on the Engine.

The configuration on a SAP AS Java 7.00 is quite easy and everything is gone with the Visual Administrator.

Configuration of the LogManager

The configuration of the LogManager is a very important prerequisite. All configuration you do in this blog will not work if the LogManager is not properly configured.

The guide is using the Visual Administrator, because the most configuration you will need to do is done in this tool. It is not possible to do all the configuration in the SAP NetWeaver Administrator.

You need to change at least one property of the LogManager

  1. ForceSingleTraceFile to NO
    or
  2. Put the package you want to log in the SingleTraceFile_UnrestrictedLocations seperated by a semicolon (;)

The documentation about the properties of the LogManager is available at SAP Help Portal. You can choose what property you want to change.

Decision Help:

  • You are unsure what packages and classes you need to log and just want the logging to be working?
    Set the property ForceSingleTraceFile to NO
    !!! Warning !!!
    You should not set this property on a productive system. You should exactly know what you want to log/trace on such systems to avoid performance impacts or the higher memory consumption.
  • You only want to log certain packages or support asked you to log a certain package?Enter the package(s) separated by semicolon (;) in the SingleTraceFile_UnrestrictedLocations property. The property value could look like:

    ShortDumpHeader;ShortDumpBody;/System/Security/Audit;com.sap.engine.services.httpserver.server.Smd;com.sap.isa

Start the procedure:

  1. Log on to the operating system with the SAP System Administrator (usually the <sid>adm user)
  2. Start the Visual Administrator by double clicking the go script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/admin directory.
  3. Choose Server → Kernel → LogManager
  4. Change the property you decided to change from the section Decision Help
  5. Save the changes (you do not need to restart the cluster until you finished the whole configuration)

Create the formatter

  1. Log on to the operating system with the SAP System Administrator (usually the <sid>adm user)
  2. Start the Visual Administrator by double clicking the go script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/admin directory.
  3. Choose Server → Services → Log Configuration
  4. Choose the advanced mode
  5. Choose Runtime → Formatters → New
  6. Set the following:

    Name:

    isa_formatter

    Pattern:

    %d,%-3p %t %s %l %m

    Type:

    TraceFormatter

  7. Save and choose “Apply to all server nodes”.

Create the log file destination

  1. Log on to the operating system with the SAP System Administrator (usually the <sid>adm user)
  2. Start the Visual Administrator by double clicking the go script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/admin directory.
  3. Choose Server → Services → Log Configuration
  4. Choose the advanced mode
  5. Choose Runtime → Destinations → New
  6. Set the following in the resulting pop-up

    Name  

    application_sap.com/crm~isa

    Type  

    FileLog

    Pattern

    ./log/applications/isa_applications.log

    Limit

    10000000

    Count

    10


    ./ means the default folder of the J2EE engine node will be used. For example on Windows <Drive_J2EE_Engine_is_installed_to>:\usr\sap\<SID>\JC<Your_Instance_Number>\j2ee\cluster\server0\

  7. Select "Add" and choose the formatter that you have just created

Starting the logging

  1. Log on to the operating system with the SAP System Administrator (usually the <sid>adm user)
  2. Start the Visual Administrator by double clicking the go script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/admin directory.
  3. Choose Server → Services → Log Configuration
  4. Choose the advanced mode
  5. Choose Runtime → Locations
  6. In Log Controllers, go to Root Location → com → sap → isa
  7. Select Add, enter the destination, and set the severity level to “Debug”.
  8. Save and choose “Apply to all server nodes”.

Now ISA writes its own log file and you are finished from the J2EE side. Note that Steps Create the log file destination and Create the formatter do not require a re-start of the Cluster node.

!!! Attention !!!
If not you did not configure the LogManager properly as described in chapter Configuration of the LogManager then the file from the destination won't be created.