How to enable/disable tracing in CA Business Intelligence (CABI) 3.x for specific CABI processes/services without requiring any restarts

Document ID : KB000056703
Last Modified Date : 14/02/2018
Show Technical Document Details

Description

How to enable/disable tracing in CA Business Intelligence (CABI)  3.x for specific CABI processes/services without requiring any restarts

Solution

In order to activate traces within CABI, create a file with a name following the array below and place it within the 'SC\CommmonReporting3\BusinessObjects Enterprise 12.0\win32_x86' directory on the CABI server

Process to Monitor File Name 
  
 CMS CMS_trace.ini
 ConnectionServer ConnectionServer_trace.ini
 EventServer EventServer_trace.ini
 JobServerChild JobServerChild_trace.ini
 JobServer JobServer_trace.ini
 WIReportServer WIReportServer_trace.ini
 CrystalRAS crystalras_trace.ini
 FileServer fileserver_trace.ini

 The file should contain the following lines:

------------------------------------------------------

 active = true;

//importance can be set to debug, xs, m depending on the level of tracing requested by support

importance = xs;

alert = true;

severity = ' ';

keep = true;

size = 100 * 1000

-------------------------------------------------------------------------------------

All trace files will be located within the 'SC\CommmonReporting3\BusinessObjects Enterprise 12.0\logging' directory on the CABI server

WARNING: Enabling tracing for Web Intelligence Report Server (WIReportServer) also creates a 'wicdztrace' folder under the logging folder. This folder contains xml files related to data retrieved and calculation generated for the reports ran during the time the trace is active. This is expected behaviour but should be monitored for disk space usage if traces run for a long period of time.

Stopping Tracing

To deactivate tracing, set the active variable in the corresponding INI to false (i.e. active = false;). Simply deleting the INI file will not stop the tracing.

 

NOTE: Tracing the Central Configuration Manager (CCM) for SIA creation

In a situation where the SIA fails to be created under the CCM, a file can be created for the CCM to be traced.

Create a file called 'SvcMgr_trace.ini' within the  'SC\CommmonReporting3\BusinessObjects Enterprise 12.0\win32_x86' directory on the CABI server.

Place the following lines within the file:

------------------------------------------------------

 active = true;

//importance can be set to debug, xs, m depending on the level of tracing requested by support

importance = xs;

alert = true;

severity = ' ';

keep = true;

size = 100 * 1000

-------------------------------------------------------------------------------------

This trace is particularly useful when the SIA fails to be created. Please be aware that unlike the other traces mentioned above, the SIA tracing DOES require a restart of the CABI services.