tracing in boexi3
DESCRIPTION
sssTRANSCRIPT
Tracing In BOEXI3.1Windows
BIP, ETACDate: 30 April 2009
© SAP AG 2009. All rights reserved. / Page 2
1. Every BOE Server Or Process has its own trace log files.Trace Log is composed of Process (Server) Name ,Process Id and Full Date.For Ex : ics_2344_2008_09_10_21_24_666_trace.log
To help Administrators identify and resolve problems with BOE Servers, allerrors and critical events (asserts) are by default traced and written to a log file.
What IS Trace?
© SAP AG 2009. All rights reserved. / Page 3
1. Traces for all servers are unified.
It means that the output format and activation mechanism are the same for all the BIP native servers.
2. 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.
New Functionality
© SAP AG 2009. All rights reserved. / Page 4
Configure Trace For BOE Servers
BO_trace.ini File Bo_trace.ini file is read every minute and is disabled by default.
To Enable
- Go to Servers In CMC
- Select Server, Stop Server- Choose Properties- Enter CMD Line Parameter “-configFile InstallDir\BusinessObjects Enterprise\12.0\
Logging\logConfig\Bo_trace.ini”- Save & Close- Restart Server- Open File in Notepad And Modify It.
© SAP AG 2009. All rights reserved. / Page 5
Trace File Parameters
Parameter Possible Value
Active True/False
Importance <<,<=,==,>=,>>, xs, s, m, l, xl
Alert True/False
Severity ‘ ‘,W,E,A
Size >=1000
Keep True/False
Log_Dir String
Always_Close On, Off
© SAP AG 2009. All rights reserved. / Page 6
Trace File Example
//active = false;
//importance = m;
//alert = true;
//severity = 'E';
//keep = false;
//size = 100 * 1000;
By Default All Parameters Are Commented.
© SAP AG 2009. All rights reserved. / Page 7
Additional Information
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
CMS CMS_trace.ini
ConnectionServer ConnectionServer_trace.ini
EventServer EventServer_trace.ini
JobServerChild JobServerChild_trace.ini
JobServer JobServer_trace.ini
WIReportServer WIReportServer_trace.ini
crcache crcache_trace.ini
crproc crproc_trace.ini
© SAP AG 2009. All rights reserved. / Page 8
Additional Information
WARNING: Removing the .ini file did not stop the tracing - once it was enabled the .ini file needs to have active = false added until the file is read in again (within a minute) before removing it.
EXPECTED BEHAVIOUR: As we usually start the trace by copying the .ini file in place I would also expect the tracing to stop if the file is not present, i.e. it has been removed.
© SAP AG 2009. All rights reserved. / Page 9
Thank you!