Product specifications
The Traces section of the cs.cfg file helps you activate traces for Connection Server jobs and drivers
and log them separately from SAP BusinessObjects applications.
You activate jobs traces by setting the Active attribute of Job and JobLevel to Yes. You activate
driver traces by setting the Active attribute of the Middleware to Yes. You can activate traces for a
specific driver by setting the Active attribute of the driver to Yes.
Example:
The following example shows the default values of Traces in the cs.cfg file:
<Traces Active="Yes">
<Logger Implementation="C" ClassID="csTRACELOG">
<Logger Implementation="Java" ClassID="com.sap.connectivity.cs.logging.TraceLogLogger"/>
<Trace Name="JobLevel" Active="Yes">
<Trace Name="Job" Active="Yes"/>
</Trace>
<Trace Name="MiddleWare" Active="Yes">
<Trace Name="Oracle" Active="Yes"/>
<Trace Name="Sybase" Active="Yes"/>
<Trace Name="Informix" Active="Yes"/>
...
<Trace Name="JDBC" Active="Yes"/>
<Trace Name="JavaBean" Active="Yes"/>
</Trace>
</Traces>
This configuration allows by default the tracing of Connection Server and drivers.
9.9.1 To activate traces in library mode
1.
Stop Connection Server.
2.
Create and set values to the following environment variables:
• BO_TRACE_LOGDIR, to set the folder name for logs, for example: C:\BOTraces
• BO_TRACE_CONFIGDIR, to set the folder name of configuration files for logs, for example:
C:\BOTraces\config
• BO_TRACE_CONFIGFILE, to set the name of the configuration file, for example BO_Trace.ini
Note:
These environment variables are commonly used to configure tracing of all BI platform activity.
3.
Create the BO_Trace.ini configuration file as follows:
active = true;
importance = '<<';
size = 100000;
keep = false;
Note:
The INI file name is case-sensitive.
4.
Add the logging.jar and tracelog.jar directory paths to the CLASSPATH environment variable.
For example: C:\BOTraces\lib\logging.jar and C:\BOTraces\lib\tracelog.jar.
5.
Restart Connection Server.
2012-03-15105
Configuring data access global parameters