Partnership-based CA SiteMinder® Federation Standalone contains a secure proxy engine that forwards traffic to backend servers. The secure proxy engine includes the following components:
Acts as the HTTP listener, handling HTTP traffic for incoming requests, and can handle HTTPS traffic, once properly configured.
Provides a servlet container for the operation of the Administrative UI. The Apache web server communicates to the Tomcat server through a Tomcat connector named mod_jk.
You can supply CA Support with log files related to these components to troubleshoot problems in your CA SiteMinder® Federation Standalone environment.
Two Apache logs that aid CA SiteMinder® Federation Standalone troubleshooting are:
mod_jk.log is enabled by default with the product. After the first contact with the federation server, information begins logging to this file.
To modify this log file:
JkLogFile "path_to_mod_jk_log"
JkLogLevel debug
JkRequestLogFormat "%w %V %T %m %h %p %U %s"
Note: The path "logs/mod_jk.log" is the default location for the JkLogFile the entry. Use the default or set this path to your preferred location.
To disable the mod_jk.log, comment out or remove these lines from the file.
For debug purposes only, you can enable the httpclient.log. The httpclient.log file is located in federation_install_dir\secure-proxy\proxy-engine\logs.
To modify this log file:
httpclientlog="yes"
To modify the location of the httpclient.log file and the log level, edit the httpclientlogging.properties file. Locate this file is in the directory federation_install_dir\secure-proxy\Tomcat\properties.
|
Copyright © 2013 CA.
All rights reserved.
|
|