Generating Log files for the Siebel Gateway Name Server and the Siebel Web Server by Tim Bull
By Georgiana Codrescu on Mar 30, 2011
Outside the Siebel Enterprise we can enable logging on the Gateway Name Server and SWSE. To do this we need to take the following steps to set the correct environment variables.
- Right click the computer icon on your desktop and select properties.
- Click the Advanced tab and select environment variables.
- Under System Variables click New
- Enter the variable name of SIEBEL_LOG_EVENTS with a value of 5
There are 6 levels of logging available:
0 - Fatal
1 - Errors
2 - Warnings
3 - Informational
4 - Details
5 - Diagnostic
After restarting the Siebel Server and Gateway services navigate to the gtwysrvr/logNamesrvr.log file. With the log level of 5 this file will hold all the Gateway Name Server information and will therefore be quite large! directory and examine the
On the SWSE environment you can set the SIEBEL_SESSMGR_TRACE (again to 5). After restarting the web server logging into the Siebel Web Client will create a object manager session, which will be recorded in the file created in the SWEApp/log directory.
The task number of the Object Manager session will be in the file along with information on the session, logged against a session ID rather than a User ID.
The SIEBEL_LOG_EVENTS together with SIEBEL_LOG_DIR (the value of which will be the location of the log files) can also be used to produce logs for the Developer Web Client. (This is sometimes still referred to as the Dedicated Web Client).
You can find more information on Environment Variables for System Logging.
In addition there are also the Server Administration screens and command line interface where we can set Event logs at both the Siebel Server and Component level as well as producing Siebel Application Response Management (SARM) files to enable detailed performance tuning.
For more information on these subjects consult the Siebel System Monitoring and Diagnostics Guide (this link goes to version 8.0; for earlier Siebel versions go to the Oracle Technology Network and search for Siebel System Monitoring and Diagnostics Guide within Documentation).
Tim Bull joined Siebel Systems in 1999 and transferred to Oracle in 2006. He is a Principal Education Consultant at Oracle University and is the Senior UK instructor for Siebel software. Using his detailed product knowledge Tim delivers both In Class and Live Virtual Class courses across all the Siebel Curriculum.