1335757 Enabling And Disabling Tracin

SAP Knowledge Base Article

1335757 - Enabling and disabling tracing in XI 3.1 for specific services without requiring a restart
Version 7 Validity: 24.08.2011 - active

Language English

Symptom l l l Need to trace the CMS but do not want to restart it
Need to trace server but do not want to restart services
How to enable tracing without stopping services

Reproducing the Issue
New tracing options to enable/disable tracing without restarting services was added in XI 3.1

Cause
There are several reasons it may be desired to trace BO services without restarting them

Resolution
New Functionality
The traces in XI3.1 for all native servers (not java) are unified. It means that the output format and activation mechanism are the same for all the
BIP native servers. The format used if the TraceLog that has a richer structure of the trace files which allows an easier browsing of those files
The second new functionality is the default activation of exception logging. Basically, when an exception occurs, the traces will write a log file every time even if the traces have not been activated.

Best Practices for traces activation
The official document xi3-1_bip_admin_en.pdf contains a bug on page 214. You cannot activate traces by only modifying the default BO_trace.ini

Windows
In order to activate traces on Windows, you have to create a file with a name following the array below and copy it in [BusinessObjects install folder]
\BusinessObjects Enterprise 12.0\win32_x86
Process to monitor
File Name
AAAnalytics
AAAnalytics_trace.ini
AADMining
AADMining_trace.ini
AADMining : XI 3.1 Name PredictiveAnalysisServer
AADashboard
AADashboard_trace.ini
AAMetrics
AAMetrics_trace.ini
AAProfiler
AAProfiler_trace.ini
AAQueryMgr
AAQueryMgr_trace.ini
AARepoMgt
AARepoMgt_trace.ini
AARules
AARules_trace.ini
AASPC
AASPC_trace.ini
CMS
CMS_trace.ini
ConnectionServer
ConnectionServer_trace.ini
EventServer
EventServer_trace.ini
JobServerChild
JobServerChild_trace.ini
JobServer
JobServer_trace.ini
WIReportServer
WIReportServer_trace.ini busobj busobj_trace.ini crcache crcache_trace.ini crproc crproc_trace.ini crystalras crystalras_trace.ini designer designer_trace.ini fccache fccache_trace.ini fcproc fcproc_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;
// Any other folder you might want, default [bobj]/BusinessObjects Enterprise 12.0/logging
//log_dir="C:/Temp";
WARNING: Enabling tracing for Web Intelligence Report Server 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.
Tracing the Central Configuration Manager for SIA creation
On Windows, when the SIA fails to be created under the CCM, a file can be created for the CCM to be traces under the [BusinessObjects install folder]\BusinessObjects Enterprise 12.0\win32_x86 folder: SvcMgr_trace.ini
This trace is particularly useful when it comes to SIA failing to be created. Unlike other traces related to services, this process requires a restart for the trace to be taken into account.

WebIntelligence Rich Client
For the WebIntelligence Rich Client traces, you need to copy the WebIRichClient_trace.ini in "[BusinessObjects install folder]\"
The WebIntelligence Rich Client traces will be generated by default in the folder: "C:\Documents and Settings\<username>\My Documents\My
Business Objects Documents\LocData"

All tracing on Windows were started correctly using the above file names and were activated without requiring a restart
This included changing the log directory.

Unix
In order to activate traces on Unix, you have to create with a name following the array below and copy it in [BusinessObjects install folder]\bobje or the current working directory of the command that started your servers.
Process to monitor File Name
AAAnalytics
AAAnalytics_trace.ini
AADMining
AADMining_trace.ini
AADashboard
AADashboard_trace.ini
AAMetrics
AAMetrics_trace.ini
AAProfiler
AAProfiler_trace.ini
AAQueryMgr
AAQueryMgr_trace.ini
AARepoMgt
AARepoMgt_trace.ini
AARules
AARules_trace.ini
AASPC
AASPC_trace.ini
CMS
boe_cmsd_trace.ini
ConnectionServer ConnectionServer_trace.ini
EventServer
boe_eventsd_trace.ini
JobServerChild
boe_jobcd_trace.ini
JobServer
boe_jobsd_trace.ini
WIReportServer.bin_trace.ini
WIReportServer
WIReportServer_trace.ini (File name in Linux) crcache boe_crcached.bin_trace.ini crproc boe_crprocd.bin_trace.ini crystalras boe_crystalrasd.bin_trace.ini fccache boe_fccached_trace.ini fcproc boe_fcprocd_trace.ini fileserver boe_filesd_trace.ini The file should contain the following text lines. active = true; importance = xs; alert = true; severity = ' '; keep = true; size = 100 * 1000;
//log_dir="/var/logs"; Any other folder you might want, default: bobje/logging
Process to monitor
File Name
AAAnalytics
XI 3.1 Name : DashboardAnalyticsServer AAAnalytics_trace.ini
AADMining
AADMining_trace.ini

RESULT
OK
OK but not pick up logs folder

XI 3.1 Name : PredictiveAnalysisServer
AADashboard
XI 3.1 Name : DashboardServer
AAMetrics
XI 3.1 Name : PMMetricsServer
AAProfiler
XI 3.1 Name : SetsProfileServer
AAQueryMgr
XI 3.1 Name : SetsQueryServer
AARepoMgt
XI 3.1 Name : PMRepositoryServer
AARules
XI 3.1 Name : PMRulesServer
AASPC
XI 3.1 Name : ProcessAnalysisServer
CMS
ConnectionServer
EventServer
JobServerChild
JobServer
WIReportServer crcache crproc crystalras fccache fcproc fileserver

Correct Name :AADMining.bin_trace.ini OK
AADashboard_trace.ini

OK

AAMetrics_trace.ini

OK

AAProfiler_trace.ini

OK

AAQueryMgr_trace.ini

OK

AARepoMgt_trace.ini

OK

AARules_trace.ini

OK

AASPC_trace.ini

OK

boe_cmsd_trace.ini
ConnectionServer_trace.ini
boe_eventsd_trace.ini boe_jobcd_trace.ini boe_jobsd_trace.ini
WIReportServer.bin_trace.ini
boe_crcached.bin_trace.ini boe_crprocd.bin_trace.ini boe_crystalrasd.bin_trace.ini boe_crystalrasd_trace.ini boe_crystalras_trace.ini boe_fccached_trace.ini boe_fcprocd_trace.ini boe_filesd_trace.ini OK
OK
OK
OK
OK
OK
OK
OK
NO
NO
NO
OK
OK
OK

RESULTS: On UNIX some of the file names for the trace files must be different from those shown above as the process names are different on
UNIX. The PM servers have different names in the XI 3.1 CMC than they are XI R2 name (both UNIX and Windows).
All tests included settings an alternate log directory.

Stopping tracing
To deactivate tracing (Windows and Unix) you will need to set the active variable (in .ini file)to false. Deleting the .ini file will not stop the tracing.
Once the ini file with the active variable set to false is read again (within a minute) you can remove the file.

Bugs
ADAPT01136604: When log in or log out, from Deski or Designer, traces log files are generated with Exception.
FR ADAPT01136611: When log in Deski or Designer, traces with Exception are generated in the "win32_x86"folder

See Also
Employees see internal memos for internal links

Keywords dynamic on the fly on demand automatic XIR3 XI31 XI3.1 zie

Header Data
Released On
Release Status
Component

24.08.2011 14:29:53
Released to Customer
BI-BIP-ADM User & server configuration, InfoView refresh, user rights

Other Components BI-BIP-DEP SBOP Web Application Deployment, Wdeploy
Priority
Category

Normal
How To

Product
Product

Product Version

SAP BusinessObjects Business Intelligence platform SAP BusinessObjects Enterprise XI 3.1