Cisco Cisco Workload Automation 6.3 User Guide

Working with SAP Jobs

Troubleshooting the SAP Adapter

Tracing for the SAP Service

Increasing the logging to diagnose issues with the SAP service is done in different ways depending upon whether you 
are using the connection parameter or the saprfc.ini

 file.

Double-click on the SAP connection definition and select the 

 tab on the 

 tab.

In the 

 field, enter 

TRACE=1 to enable the tracing function.

When done logging the information, turn off the function by changing the 

1 to a 0 (TRACE=0).

With the saprfc.ini

 file you can increase tracing for the SAP service by turning on a variable in the file.

While tracing via file would still produce some level of logging, it will not be complete. Therefore, it is highly 

recommended you use Connection Parameter instead of file when setting up the trace.

Locate the saprfc.ini file on the SAP adapter machine. Refer to the section, “Configuring Default System Settings for 
SAP” for more details on locating this file.

Inside the saprfc.ini file is a variable called RFC_TRACE. This variable controls the trace function for SAP.

Turn on the tracing function by changing the variable from RFC_TRACE=0 to RFC_TRACE=1.

Both options record diagnostic data to a single trace file called rfcxxxx.trc. By default they are written to the SAP GUID 
directory under services.

For example (Windows):

C:\Program Files\TIDAL\Scheduler\Master\services\{51C57049-3215-44b7-ABE1-C012FF786010}

It is highly recommended that you perform a search on the machines where the master and SAP adapter resides for the 
rfcxxxx.trc files location.

The rfcxxxx.trc files contain diagnostic information, a detailed description of the problem and the job(s) in question. 
These items should be provided to Technical Services and/or to SAP Support for troubleshooting purposes.

If the connection to the SAP does not work, verify that the JCO files have Read and Execute permissions for the system 
account. The SAP service cannot communicate with the SAP system if the system does not have the proper access. 

Cannot Connect to the SAP Instance

If you are unable to connect to the SAP instance from the master or a client:



Search on that master or client machine for a file called dev_rfc.trc. This file is a text file and can be read using the 
Notepad program. This file contains the error message and other information explaining why a network connection 
failed.  For example, if you get an error message about security, the SAP administrator may have failed to grant 
access to a necessary SAP object to the user account. Run a SU53 security trace to search for missing objects. 



When using external scheduling tools with 

log entries are written to a data table called 

. A large number of log records may cause the table to fill up. Once the table becomes too large, 

CWA cannot connect to the SAP instance and the agent connection light will stay red no matter what action is 
attempted until the table is cleared out. On a regular basis (we recommend weekly), the SAP administrator should 
schedule a job that clears out the 

 table. 

A weekly scheduling of the job, consisting of an ABAP report containing the following function module call is 
recommended: