Cisco Cisco Workload Automation 6.3 User Guide

Page of 78
67
Working with SAP Jobs
Troubleshooting the SAP Adapter
Limit SAP jobs to individual job steps
 – It is recommended that SAP jobs be limited to a single job step. Convert 
SAP jobs with multiple job steps into job groups of single-step SAP jobs in CWA. Breaking down multiple-step jobs 
into jobs of individual steps provides greater control over each job step. By using single job steps, you can set 
dependencies for each job step. Dependencies on a multiple-step SAP jobs apply to the entire job, not the job step. 
Delete past SAP jobs 
– Jobs that have already run in CWA are normally cleared from the SAP database when that 
job instance is deleted in CWA. However, it is recommended that the administrator should create an SAP job that 
runs the 
RSBTCDEL
 
ABAP
 program with a variant that specifies the set of jobs that you want to delete and schedule 
this job to run at regular intervals to clean up any jobs that missed being deleted. For more information on SAP job 
deletion, consult your SAP documentation or your SAP Administrator. 
You must delete job history (PSPRCSRQST records) in SAP as part of your regular database maintenance. You can 
run the SQR Report process, PRCSPURG, to purge old request records that accumulate in the SAP database. You 
can use CWA to run the PRCSPURG utility on a regular basis. 
Note: 
The default job history retention interval for jobs in CWA is set on the Defaults tab of the System Configuration 
dialog. You can set job history retention for an individual job in the Options tab of the Job Definition dialog. CWA will 
automatically delete job history from its own logs when the job history retention limit is met. The default is 30 days.

Deleting a job from the Jobs pane removes the job only from CWA. You still must delete the job history from SAP.
Troubleshooting the SAP Adapter
There are several things you can investigate to troubleshoot the SAP Adapter:
Studying the Logs
There are logs that can be studied for diagnostic clues when issues arise when running SAP jobs. These logs are:
Log
Location
Master
C:\Program Files\TIDAL\Scheduler\Master\log
AdapterHost
C:\Program Files\TIDAL\Scheduler\Master\log
Client Manger
C:\Program Files\TIDAL\ClientManager\plugins\tes-6.0\log
and
C:\Program Files\TIDAL\ClientManager\log
SAPService
C:\Program 
Files\TIDAL\Scheduler\Master\services\{51C57049-3215-44b7-ABE1-C012FF
786010}\log