CA SiteMinder® SessionLinker Guide › Installing and Configuring the SessionLinker › How to Configure the CA SiteMinder® SessionLinker › Enable SessionLinker Logging on your IIS web server

Enable SessionLinker Logging on your IIS web server

You can enable SessionLinker logging on an IIS web server. These SessionLinker log files appear in your Web Agent trace files.

Follow these steps:

1. Enable agent trace logging by setting the following parameter:

   TraceFile

   Enables trace logging.

   Default: No

2. Specify an agent trace file by setting the following parameters:

   TraceFileName

   Specifies the full path to the trace log file.

   Default: No default

   Limits: Specify the file name in this parameter.
   Example: web_agent_home\log\trace.log

   TraceFileName32

   Specifies the full path to the trace file for the CA SiteMinder® Agent for IIS is running on a 64-bit Windows operating environment and protecting 32-bit applications. Set this parameter if you have a CA SiteMinder® Agent for IIS installed on a 64-bit Windows operating environment and protecting a 32-bit Windows application. The 32-bit applications run in Wow64 mode on the 64-bit Windows operating environment. If trace logging is enabled but this parameter is not set, the Web Agent for IIS appends _32 to the file name.

   Default: No default.

   Limits: For Windows 64-bit operating environments only. Specify the trace file name at the end of the path.

   Example: (Windows 64-bit operating environments using Wow64 mode) web_agent_home\log\WebAgentTrace32.log.

3. The default logging level is 2. To set a different logging level, open the following files on your IIS web server:
   • SessionLinker_Installation_Directory\bin\ISAPIlogging.reg (for 32-bit applications)
   • SessionLinker_Installation_Directory\bin\ISAPI64logging.reg (for 64-bit applications)
4. Change the log setting in each file to one of the following values:

   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.

   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.

5. Save your changes to the file and close the text editor.
6. Double-click the updated .reg file.
7. Restart your IIS web server.