Show TOC

Procedure documentationConfiguring Connectivity Logging Locate this document in the navigation structure

 

Developers, technical administrators, and application administrators can use the log viewer to review runtime calls and analyze connectivity issues. By default, the system does not record this information. When necessary, you can activate the recording of information about the runtime calls by creating logging configurations. For each logging configuration, you should specify the length of the period for which the system collects this information, as well as what kind of information should be collected. The system collects and stores the required information only when there are active logging configurations, and once they expire it stops collecting information. You can also specify how long the system should keep the stored information.

For more information about viewing the collected information, see Viewing Connectivity Log.

Recommendation Recommendation

Setting a system to collect and store connectivity information may impact the performance of the system. It is suggested you consider the following when creating a logging configuration:

  • Create logging configurations only when necessary.

  • Carefully set the length of the period for which the system collects information.

    If you have found what you need in the connectivity log and the logging configuration has not expired yet, you can delete it.

  • In the logging configuration, specify the interfaces for which you want to collect information.

    This way the system stores only the information you need.

End of the recommendation.

Prerequisites

The user account that you use for configuring the logging activity meets one of the following conditions:

  • Assigned to the NWA_SUPERADMIN or other role that contains the LogConfigurator_ALL user management engine action.

    This type of account is typical for a technical administrator. It allows the user to create, edit, and display logging configurations.

  • Assigned to the NWA_READONLY or other role that contains the LogConfigurator_DISPLAY user management engine action.

    This type of account is typical for a business administrator. It allows the user only to display logging configurations and not to create or edit them.

For more information, see Authorizations and User Management of the Application Server Java.

Procedure

Displaying the Configurations List

  1. Log on to SAP NetWeaver Administrator.

  2. Choose   SOA   Logs and Traces   Connectivity Logging & Tracing  .

  3. Choose Log Configurator.

  4. If you want to specify how the configuration entries should be displayed in the list, choose Open Settings Dialog (Open Settings Dialog) and do one or more of the following:

    • To select which parameters should be displayed in the configurations list and how they should be ordered, choose Column Selection and modify the Displayed Columns list as needed.

    • To set how the entries in the configurations list should be sorted, choose Sort Sequence and modify the Sorted Columns list.

    • To specify the configurations list size and look, choose Display and edit the display parameters.

  5. To find configuration entries in the list:

    1. Choose Display Filter Row (Display Filter Row).

    2. Enter the search criteria in the corresponding field in the filter row.

      If you enter only part of the term for which you want to search, you should use the asterisk (*) wildcard character.

    3. Choose Filter (Filter).

Note Note

To make sure that the configurations list is valid, you should check the following

  • Below the list you can find information about when the currently displayed list was loaded.

  • The value in the Expiration Time column shows when the system should stop collecting logging information for the corresponding entry.

You should refresh the list whenever you need to make sure that the expired entries are not displayed any more.

End of the note.
Creating a Logging Configuration

  1. Choose New.

  2. Choose for which user the system should log the activity.

  3. In the Expiration Period field, enter the length of the period for which the system should log information.

    Consider the following:

    • The system does not persist the logging configurations during restart.

    • The system can keep the collected information until it reaches the allowed amount of time and space for storing connectivity information. For more information, see the Configuring Tracing Information Storage section below.

  4. Choose the direction of the calls and the type of binding for which the system should save logging information.

    If you do not specify a namespace and a connection interface, the system records information for all calls for the specified binding and direction.

  5. When you want the system to collect information only about calls held by applications in a particular namespace or via a particular connection interface, you can enter them in the Namespace and Interface Name fields, respectively.

    You should enter only values that are valid for the specified binding and direction. When you specify interfaces for a logging configuration the system stores only the information you need, and you can search the logs without needing to specify the interfaces in which you are interested.

  6. If you want the system to save the payload information you should check the Trace checkbox.

    Note Note

    The system also saves the payload information when one of the following conditions is met:

    • There are no active logging configurations, and the severity level of the com.sap.engine.services.webservices controller is set to DEBUG.

    • There are active logging configurations for which the business payload tracing is not activated.

    Note that in such situations the system obfuscates the business payload and displays it with “X” characters in the log viewer.

    End of the note.
Editing a Logging Configuration

  1. Select the logging configuration you want to modify.

  2. Choose Edit, and modify the expiration period or the business payload tracing options as necessary.

Deleting a Logging Configuration

Select the logging configuration you want to delete and choose Delete. Thus you set the system to stop collecting connectivity information as specified in the selected configuration.

Configuring Tracing Information Storage

  1. Log on to SAP NetWeaver Administrator.

  2. Choose   Configuration   Infrastructure   Java System Properties  .

    For more information about the Java System Properties tool, see Java System Properties.

  3. Choose Services.

  4. Locate the com.sap~tc~je~sca_integration service.

  5. In the Extended Details screen area, modify the following properties as necessary to specify how the system should keep the stored connectivity information:

    • The value of esblogtrace.row.number determines the maximum number of entries that the system keeps.

    • The value of esblogtrace.max.row.age.seconds (in seconds) determines which old entries should be removed from the system when the number of entries exceeds the maximum.

    The system monitors the number of entries. When this number becomes greater than the one specified in esblogtrace.row.number, the system deletes the entries older than the period specified in esblogtrace.max.row.age.seconds. Then, if the number of entries is still bigger than the allowed maximum, the system keeps the newest entries up to the allowed maximum and deletes the oldest entries.