How To Turn Up Logging on the Siebel Web Server Extension in Siebel Versions 7.x and 8.x? [ID 477185

How To Turn Up Logging on the Siebel Web Server Extension in Siebel Versions 7.x and 8.x? [ID 477185.1]
		修改时间 10-FEB-2012     类型 HOWTO     状态 PUBLISHED

In this Document
  Goal
  Solution
     For Windows Environments
     For a UNIX Environment except Linux
     For Linux Environment using Oracle HTTP Server 10g
     For Linux Environment using Oracle HTTP Server 11g
     To Reverse the Default Logging Levels on the Web Server
     Related Documentation
  References

---

Applies to:

Siebel CRM - Version: 7.5.3 SIA [16157] to 8.1.1 [21112] - Release: V7 to V8
Information in this document applies to any platform.
Area(s):System Administration
Release(s):V7 (Enterprise), V7 (Professional), V7 (MidMarket), V8 (Enterprise), V8 (Professional)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V8 (Enterprise)
Keywords:Web server logging, SIEBEL_LOG_EVENTS, SIEBEL_SESSMGR_TRACE, SIEBEL_SISNAPI_TRACE

This document was previously published as Siebel FAQ 2117.

Goal

How To Turn Up Logging on the Siebel Web Server Extension in Siebel Versions 7.x and 8.x?.

Solution

While troubleshooting the Siebel Web Server Extension (SWSE) for Siebel version 7.5.3 or earlier, it is advisable to set the Log parameter in the SIEBEL_HOME\SWEApp\BIN\eapps.cfg file to details. This will write more detailed information into the SWSE log files located in the SIEBEL_HOME\SWEApp\LOG directory.

 

NOTE: Starting in Siebel version 7.7.x, the Log parameter in the eapps.cfg file is no longer used by the SWSE. You only need to set the environment variables documented below to trace the SWSE connections. Bug < a>12-JP45TC>> has been logged to address the documentation defect to request the Log parameter be removed from the eapps.cfg file. This parameter has been removed from the Siebel Bookshelf starting with Siebel version 7.7.

 

To troubleshoot further, the logging can be increased to include Siebel Internet Session API (SISNAPI) and Session Manager tracing. The following information details how to turn up logging for the SWSE on the Microsoft Windows and UNIX Operating Systems to include SISNAPI and Session Manager Information.

 

Be aware that by increasing the logging levels on the Web Server, this may cause performance degradation, the extent of which will depend on your specific implementation (mostly this is insignificant). Additionally, increasing the logging levels will require more available disk space in the SIEBEL_HOME\SWEApp\LOG directory as the log files will be bigger. It is always a good practice to test out these settings in your test environment first and then move these settings to production only if specifically requested by Siebel Technical Support. Once the behavior has been resolved, it is a good practice to unset the environment variables and reset the default logging for the SWSE in the production environment.

 

For Windows Environments

 

Perform the following steps to enable tracing for the SWSE:

 

1. Set the following System Environment Variables:

 

SIEBEL_LOG_EVENTS=4 (or higher)

SIEBEL_SESSMGR_TRACE=1

SIEBEL_SISNAPI_TRACE=1

 

To set up environment variables perform the following steps:

 

• • Start > Settings > Control Panel > System.

 

• • Click on the Advanced tab and then click on the Environment Variables button.

 

• • Under the System variables view, click the New button and add the variable names and values mentioned above. Click the Ok button when finished.

 

2. In the eapps.cfg file located on the web server machine under the directory SIEBEL_HOME\SWEApp\BIN folder, make the following changes under the [swe] section:

 

Log = details (only for 7.5.3 or earlier)

SessionMonitor = TRUE

 

3. Restart the IIS Admin Service and its dependent services for the changes to take effect. NOTE: The inetinfo.exe process has to be restarted for the new environment variables to take effect.

 

NOTE: If SWSE is installed on a Windows 2003 Server, it is necessary to reboot the machine otherwise logging will not be enabled.

 

For a UNIX Environment except Linux

 

Perform the following steps to enable tracing for the SWSE:

 

1. Set the following environment variables:

 

SIEBEL_LOG_EVENTS=4 (or higher)

SIEBEL_SESSMGR_TRACE=1

SIEBEL_SISNAPI_TRACE=1

 

To set up environment variables for the user who starts the web server, perform the following steps (for Bourne and Korn Shell):

 

$ <variable>=value; export <variable>

 

For example:

 

$ SIEBEL_LOG_EVENTS=4; export SIEBEL_LOG_EVENTS

 

2. In the eapps.cfg file found on the web server machine under SIEBEL_ROOT/sweapps/bin folder make the following changes:

 

Under the [swe] section:

 

Log = details (only for 7.5.3 or earlier)

SessionMonitor = TRUE

 

3. Restart the web server process for the changes to take effect.

 

For Linux Environment using Oracle HTTP Server 10g

For increasing the logging for SWSE when using Oracle HTTP Server 10g (OHS 10g) add the environment variables to a file named envvars under ohs/bin directory.

envvars-std - default environment variables for apachectl
#

This file is generated from envvars-std.in
#
LD_LIBRARY_PATH=
export LD_LIBRARY_PATH

SIEBEL_SESSMGR_TRACE=1
SIEBEL_SISNAPI_TRACE=1
SIEBEL_LOG_EVENTS=5

export SIEBEL_SESSMGR_TRACE
export SIEBEL_SISNAPI_TRACE
export SIEBEL_LOG_EVENTS

 

For Linux Environment using Oracle HTTP Server 11g

For increasing the logging for SWSE when using Oracle HTTP Server 11g (OHS 11g) add the environment variables to the script <ohs root>/ohs/bin/apachectl

Search for the entry where LD_LIBRARY_PATH is set and add the variables just under this section of the file:

SIEBEL_SESSMGR_TRACE=1
SIEBEL_SISNAPI_TRACE=1
SIEBEL_LOG_EVENTS=5

export SIEBEL_SESSMGR_TRACE
export SIEBEL_SISNAPI_TRACE
export SIEBEL_LOG_EVENTS

When you start the web server from <ohs root>/instances/instance1/bin using :

./opmnctl startall

The Apache web server script, apachectl, is called as part of this and the environment variables are sourced.

To Reverse the Default Logging Levels on the Web Server

 

1. Remove all three environment variable settings.
2. In the eapps.cfg file set Log = errors (only for 7.5.3 or earlier).
3. Restart the web server processes.

 

NOTE: For information about unsetting the environment variables, see the appropriate operating system documentation.

 

Related Documentation

 

Please refer to the following related FAQs and Siebel Bookshelf references found on SupportWeb for additional information on how to handle log files:

 

• Document 477112.1 details information about how to manage the size of the Siebel log files.

 

• Document 476703.1 details information about how to troubleshoot the error message "The Server You Are Accessing is Either Busy or Experiencing Difficulties......" in a Siebel 7 Web Client User Browser.

 

• Siebel Bookshelf version 8.1 > Siebel System Monitoring and Diagnostics Guide > Configuring SWSE Logging and Monitoring.

 

• Siebel Bookshelf version 8.0 > Siebel System Monitoring and Diagnostics Guide > Configuring SWSE Logging and Monitoring.

 

• Siebel Bookshelf version 7.8 > System Monitoring and Diagnostics Guide for Siebel Business Applications > Configuring SWSE Logging and Monitoring.

 

• Siebel Bookshelf version 7.7 > System Monitoring and Diagnostics Guide for Siebel eBusiness Applications > Configuring SWSE Logging and Monitoring.

 

• Siebel Bookshelf version 8.1 > Siebel System Administration Guide > Structure of the eapps.cfg File.

 

• Siebel Bookshelf version 8.0 > Siebel System Administration Guide > Structure of the eapps.cfg File.

 

• Siebel Bookshelf version 7.8 > Siebel System Administration Guide > Structure of the eapps.cfg File.

 

• Siebel Bookshelf version 7.7 > Siebel System Administration Guide > Structure of the eapps.cfg File.

 

• Siebel Bookshelf version 7.5.3 > Siebel Server Installation Guide for Microsoft Windows > Structure of the eapps.cfg File > Editing the Web Server Extension Configuration File.

 

• Siebel Bookshelf version 7.5.3 > Siebel Server Installation Guide for UNIX > Structure of the eapps.cfg File > Editing the Web Server Extension Configuration File.