Руководство Пользователя для Cisco Cisco Tidal Enterprise Scheduler 6.2

There are logs that can be studied for diagnostic clues when issues arise when running SAP jobs. These 
logs are:

Each log collects information until it reaches one megabyte in size, when it is then saved and a new log 
file begun. The log file is named with the name of the log and a date and time stamp appended to the log 
name as in the following example: 

SAPService-20050819123934.log

The above log file example is an SAP service log file created on August 19, 2005 (20050819) at 
12:39:34.

See the next section, 

, to learn how to configure 

logging for the SAP Adapter and SAP connections.

If your jobs are not completing normally, you need to gather information through diagnostic logging (or 
tracing in SAP terms) while reproducing the problem. Once you have gathered the diagnostic 
information into logging files, send the file to Technical Services to help them troubleshoot the problem. 
There are two methods to configure diagnostic logging for the SAP adapter.

Higher levels of diagnostic logging require carefully monitoring. Diagnostic logging can consume large 
amounts of disk space and can have an adverse effect on system performance.

Diagnostic information is collected from the various TES components in different ways.  

You can increase diagnostic logging from the SAP adapter from the 

 dialog for 

the master connection.

In the 

 pane, open the connection for the master to display its 

 

dialog.

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-C012FF786010}\log