search cancel

Enable httpclient logging in Access Gateway 12.7


Article ID: 15670


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On


With Access Gateway R12.7 using the documented way to enable httpclient logging does not work. 

The documented method is to change the server.conf entry: 

    httpclientlog ="yes"


But an extra setting is required in Ag R12.7


Release: ETRSWK99000-12.7-SiteMinder-Web Access Manager-SmWalker


For Access Gateway R12.7 it needs : 

In server.conf : 

   httpclientlog ="yes"

This should be the only setting required.

But httpclient logging uses a common logging module, that can use either SimpleLogging, or log4j or java.util.logging.  The common logging module does some checking at startup, and determines which logging mechanism to use.   Prior to R12.7 the default was java.util.logging, but some change in R12.7 has changed the default. 

You can set the default for common logging to java.util.logging via JVM startup property : 


For Access Gateway R12.7 this needs to be set in : 

For Windows: 



Edit the file and add the parameter : 

<Please see attached file for image>

src="/servlet/servlet.FileDownload?file=0150c000004AKovAAG" alt="2017-08-29 12_26_04-SPS R12.52 Sp1Cr02 - VMware Workstation.png" width="832" height="161">

For Unix : 


Edit the file and add the parameter :  

<Please see attached file for image>

src="/servlet/servlet.FileDownload?file=0150c000004AKowAAG" alt="2017-08-29 12_35_19-CentOS 6.5 64-bit-SPS - VMware Workstation.png" width="832" height="126">


It is also raised as an internal Sustaining Engineering ticket, and we expect it will be fixed in a latter CR version.




1558717452527000015670_sktwi1f5rjvs16ump.png get_app
1558717450471000015670_sktwi1f5rjvs16umo.png get_app