Thursday, September 23, 2010

Enabling and disabling tracing in XI 3.1 for specific services without requiring a restart - 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

WIReportServer.bin_trace.ini

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 = 'E';
keep = true;
size = 100 * 1000;
//log_dir="/var/logs"; Any other folder you might want, default: bobje/logging

Process to monitor

File Name

RESULT

AAAnalytics
XI 3.1 Name : DashboardAnalyticsServer

AAAnalytics_trace.ini

OK

AADMining
XI 3.1 Name : PredictiveAnalysisServer

AADMining_trace.ini
Correct Name :AADMining.bin_trace.ini

OK but not pick up logs folder
OK

AADashboard
XI 3.1 Name : DashboardServer

AADashboard_trace.ini

OK

AAMetrics
XI 3.1 Name : PMMetricsServer

AAMetrics_trace.ini

OK

AAProfiler
XI 3.1 Name : SetsProfileServer

AAProfiler_trace.ini

OK

AAQueryMgr
XI 3.1 Name : SetsQueryServer

AAQueryMgr_trace.ini

OK

AARepoMgt
XI 3.1 Name : PMRepositoryServer

AARepoMgt_trace.ini

OK

AARules
XI 3.1 Name : PMRulesServer

AARules_trace.ini

OK

AASPC
XI 3.1 Name : ProcessAnalysisServer

AASPC_trace.ini

OK

CMS

boe_cmsd_trace.ini

OK

ConnectionServer

ConnectionServer_trace.ini

OK

EventServer

boe_eventsd_trace.ini

OK

JobServerChild

boe_jobcd_trace.ini

OK

JobServer

boe_jobsd_trace.ini

OK

WIReportServer

WIReportServer.bin_trace.ini

OK

crcache

boe_crcached.bin_trace.ini

OK

crproc

boe_crprocd.bin_trace.ini

OK

crystalras

boe_crystalrasd.bin_trace.ini
boe_crystalrasd_trace.ini
boe_crystalras_trace.ini

NO
NO
NO

fccache

boe_fccached_trace.ini

OK

fcproc

boe_fcprocd_trace.ini

OK

fileserver

boe_filesd_trace.ini

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.

No comments:

Post a Comment

Sonarqube Upgrade from 9.4.4 to 9.9.4 LTS

 Issue:  1) Java hasbeen upgraded from 11 to Open JDK 17. And Sonarqube is upgraded from 9.4 to 9.9.4. 2) After the upgrade sonarqube servic...