CA SiteMinder® SessionLinker Guide › Installing and Configuring the SessionLinker › Configure Apache Web Servers to Track Sessions With Multiple SAP Applications Hosted on the Same Server on UNIX

Configure Apache Web Servers to Track Sessions With Multiple SAP Applications Hosted on the Same Server on UNIX

If your environment includes several different SAP applications hosted on multiple instances of the same server and uses the same SiteMinder session for single sign-on between the applications, you must configure the SessionLinker on an Apache web server to provide a unique identifier for each instance of the server. Otherwise the SessionLinker will reject the original association between the SAP cookie and the SiteMinder session.

To configure a unique web server ID on Apache web servers:

1. Stop the SessionLinker Daemon service by typing the following command:

   kill PID_of_sessionlinkd_process
   

2. Update the httpd.conf file by editing the SessLinkInit line:

   #SessLinkInit "path/SessionLinker.log" 0
   

   Note: Steps a. through c. are not necessary if you have already configured SessionLinker logging.

   1. If necessary, remove the comment (#) symbol from the start of the line.
   2. If necessary, edit the log file path entry ("path/SessionLinker.log") to specify the full path to use for the log file.
   3. In necessary, edit the log level entry ("0" at the end of the line) to the desired logging level (where 0 disables logging and levels 1-4 enable increasingly higher levels of logging).
   4. Add a unique Web Server ID (1-30 alphanumeric characters) to the end of the line.

   For example:

   SessLinkInit "C:\Logfiles\SessionLinker.log" 1 Server1
   

3. Start the SessionLinker Daemon service by typing the sessionlinkd command (and optional command line parameters, as required).
4. Restart the web server for changes to take effect.

More information:

Starting the Daemon