CA SiteMinder® SessionLinker Guide › Installing and Configuring the SessionLinker › How to Configure the CA SiteMinder® SessionLinker › Enable SessionLinker Logging on your Apache or Oracle iPlanet Servers

Enable SessionLinker Logging on your Apache or Oracle iPlanet Servers

Some types of web servers can keep log files related to the SessionLinker product itself (this setting is separate from the SessionLinker Daemon). If you use one of the following web servers, you can enable SessionLinker logging:

• Apache web servers (on the Windows and UNIX operating environments)
• Oracle iPlanet (formerly named Sun Java System) web servers (on the Solaris operating environment)

Follow these steps:

1. Do one of the following tasks:
   • For an Apache web server, open the http.conf file and remove the comment from the following line:

     #SessLinkInit "/muks/CA/sessionlinker-64/SessionLinker.log" 0
     

   • For a Sun Java System Web Server, open the magnus.conf file and remove the comment from the following line:

     # Init fn="npssessionlinkerInit" logfile="/dir0/ngtyerpc/sessionlinker/sessionlinker-64/NPSNSAPISessionLinker.log" loglevel=0
     

2. Replace the number at the end of the previous line with one of the following numbers:

   0

   Disables logging. Log files are not kept.

   1

   Records any errors in the SessionLinker initialization and communication only. These messages appear with ERR in the log file.

   Important! The highest logging level we recommend for production environments is 1. Higher levels quickly produce large log files.

   2

   Records informational errors, which sometimes indicate the cause of a problem. The specific cause is not always shown. These messages appear with INF in the log file.

   3

   Records debugging information. These messages appear with DBG in the log file.

   4

   Records extra information that is designed to locate problems in the library code. Use this setting only if directed to by CA Technologies personnel. These messages appear with XXX in the log file.

3. Restart your web server.

   SessionLinker logging is enabled on your web server.