Logging and Monitoring

Overview

The following sections describe logging information and monitoring Adapter for SAP connection statistics and performance.

Logging

About this task

Adapter for SAP produces detailed logging information using 19 different log facilities. The log level of Log facilities can be individually disabled or set to different log level,and the log level can be set from "Fatal" (logs only critical information) to "Trace" (logs verbose information) for the enabled log facilities. The log level determines the amount of logging information being produced by the adapter. Please note that a high log level will reduce the performance of the adapter's processing and should therefore only be set for diagnostic purposes.

Output

About this task

Adapter for SAP logging output can be received by different log consumers. Currently Adapter for SAP uses Integration Server logging mechanism to display the adapter log messages. You can configure and view the Integration Server logs to monitor and troubleshoot Adapter for SAP.

To receive and display the required logging information from the adapter, you need to set the log level of the SAP log facilities for Integration Server logging.

To set the log level of the SAP log facilities for Integration Server logging

Procedure

  1. From Integration Server Administrator screen, select Settings > Logging. The Logging Settings screen appears.
  2. In the Logger List, select Server Logger.
  3. In the Server Logger Configuration section click on Adapter for SAP to display the current log level setting of the adapter's log facilities.
  4. Click on Edit Server Logger to set the required log levels for Adapter for SAP facilities.
  5. Click Save Changes.

Results

For detailed information about logging in Integration Server, including instructions for configuring and viewing the different kinds of logs supported by the server, see IBM webMethods Integration Server Administrator’s Guide and IBM webMethods Audit Logging Guide for your release.

Viewing and Deleting RFC Trace Files and SAP Log Files

About this task

In the development and test phase it is sometimes helpful to view RFC traces if there are problems with the function modules you are trying to call. In order to avoid the need to access the file system of the machine on which Integration Server is running, you can view and delete RFC trace files and SAP log files from Integration Server Administrator.

All SAP log files, as well as the RFC trace files are stored in the packages/WmSAP/logs directory.

To view and delete RFC trace files and SAP log files

Procedure

  1. In Integration Server Administrator, browse to Adapters > IBM webMethods Adapter for SAP > Logging.
  2. The Logging screen appears. This screen lists the RFC trace files and SAP log files, and shows each file's size and creation date.
    • RFC trace files are split into several parts, each of them containing one trace entry along with the date and time it was created. To view the log entries for a specific Trace File, click the Trace File name.
    • Large SAP log files are split into several parts of about 500K. To view the log entries for a specific SAP log File, click the SAP Log File name.

      In this way it is avoided that the browser has to load too large documents, which would take a long time or even cause a time out. Using the Back button of your browser, you can return from the display of one part to the list of parts for that file. If you try to delete a file that is still open (for example, because the Server is still writing to it), you will receive a message, and the file will not be deleted.

  3. You can delete files that you no longer need:
    • To delete an individual trace file or SAP log file, click for the file to delete.
    • To quickly delete all trace files or all SAP log files, click Delete All.

Monitoring Statistics for Each Adapter for SAP Connection

About this task

The Monitoring screen allows the user to view the SAP repository connection pools, the SAP client connections, the SAP listener status, and the component response time monitor. From the Monitoring screen you may access a list of the size attributes of all currently active JCo Pools, as well as the attributes of all currently locked connections for a specific Adapter for SAP connection.

To view Adapter for SAP connection statistics

Procedure

  1. In the Adapters menu in the Integration Server Administrator's navigation area, click IBM webMethods Adapter for SAP.
  2. In IBM webMethods Adapter for SAP menu, click Monitoring. The Monitoring screen is displayed.
  3. To view the size attributes of all currently active JCo Pools for a specific Adapter for SAP connection:
    1. In the SAP Client Connections section of the Monitoring screen, click the number in the Poolscolumn that corresponds to the client connection for which you want to view the size attributes.
    2. The Connection Pools screen displays the following information:
      Attribute Description
      Name Name of the JCoPool.
      Current size Number of client connections that are currently open in the pool.
      Peak size Maximum number of client connections that were used simultaneously.
      Max size Maximum number of client connections that can be used simultaneously.
      Current used Number of client connections currently in use.
    3. To return to the Monitoring screen, click Return to Monitoring.
  4. A locked connection is an RFC connection that is locked to your Integration Server session so that it will always be used for subsequent calls. An RFC connection is locked by calling the public Adapter for SAP service pub.sap.client:lockSession.

    To view the attributes of all currently locked connections for a specific IBM webMethods Adapter for SAP connection:

    1. In the SAP Client Connections section of the Monitoring screen, click the number in the Locked Connectionscolumn that corresponds to the client connection for which you want to view the attributes.
    2. The Locked Connections screen displays the following information:.
      Attribute Description
      SAP user SAP user name associated with this connection (empty if unavailable).
      Client Client number associated with this connection (empty if unavailable).
      Language Language associated with this connection (empty if unavailable).
      Host SAP host from where the connection is executed (empty if unavailable).
      Conversation ID Internal JCo conversation ID for the connection (empty if unavailable).
      IS user IS user name associated with the connection (empty if unavailable).
    3. To return to the Monitoring screen, click Return to Monitoring.

Monitoring Adapter for SAP Performance

Performance Output Information in the SAP Log File

From log level "Debug" or higher you can view performance output information for Adapter for SAP in the SAP log file. The corresponding terms are described below.

  The term… Specifies…
1. Time for marshalling (ms) Time needed for transferring the data from IData (pipeline representation) to JCo Objects.
2. Time for unmarshalling (ms) Time needed for transferring the data from JCo Objects to IData (pipeline representation).
3. Time for preparing (ms) Time needed for preparing execution of a function module (outbound calls) or invocation of a service. This includes repository queries for the data structures and the function interface, opening connections to the involved systems, etc.
4. Time for rfc calls (ms) Time needed in the JCo layer for outbound calls.
5. Time for IBM webMethods Adapter for SAP service calls (ms) Time needed for the invocation of a service to handle an inbound request in Adapter for SAP after preparing/marshalling and before unmarshalling the data. (Listener performance data).
6. Total time for function calls (ms) Total time needed for handling inbound/outbound calls in Adapter for SAP layer.

Component Response Time Measurement

With this kind of monitoring, an application gets split into several components and the response time gets measured per component.You will find this information on Adapters > IBM webMethods Adapter for SAP > Monitoring:

At the bottom of this screen, you will find the following monitoring information:

The term… Specifies…
Requests total Number of requests executed so far.
Request rate Requests per second since monitoring was enabled.
Requests ok Number of successful requests.
Requests with errors Number of requests with errors.
Components total Number of components used in requests.
Components per request Average number of components per request.
Total time Execution time for all requests in milliseconds.
Average time Average execution time for a request in milliseconds.
Query Requests You can get the TOP 100 requests (the requests that needed the longest execution times.) To restrict those entries, you can specify the Info for and max. listed Requests inputs before pushing the Show Button.
Info for... Enter a wildcard-like pattern for the request names, for which you want the information. You can use only exact patterns and patterns with a single '*' at the end, such as 'client.*'. You cannot make entries with the format '*rfc*'.
max. listed Requests Limits the number of requests to the given number. After pushing the button, the Requests Overview is displayed.
Query Components You can get accumulated information about all components, that have been used in Request. To restrict those entries you can specify the Info for input before pushing the Show Button:
Info for... Enter a wildcard-like pattern for the Component names, for which you want the information. You can use only exact patterns and patterns with a single '*' at the end, such as 'client.*' You cannot make entries with the format '*rfc*'. After pushing the button, the Component Overview is displayed.