How to generate Application Server Agent logs/traces (TAI)?

Products

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

Issue/Introduction

 

How to set the ASA Agent logs to DEBUG

There are 2 log files that could be generated for an application server agent:

SmWasAsaDefault.log (defined in the smagent.properties) that contains information on the initialization and on the DoManagement messages (connection to the PS) like

[07 Oct 2011 11:37:58,087] [Thread-15] [DEBUG] The Configuration Management thread is calling doManagement()
[07 Oct 2011 11:37:58,213] [Thread-15] [DEBUG] There are doManagement messages
[07 Oct 2011 11:38:28,219] [Thread-15] [DEBUG] The Configuration Management thread is calling doManagement()

Smwasasassertion.log (defined in the smassertion.conf file) that contains information on the request like

[14 Aug 2011 04:30:32,130] [WebContainer : 0] [INFO] High Level Agent processing request https://_host.example.com/wps/myportal/adcustomer.
[14 Aug 2011 04:30:32,130] [WebContainer : 0] [INFO] High Level Agent checking if SiteMinder credentials are present.
[14 Aug 2011 04:30:32,130] [WebContainer : 0] [DEBUG] SiteMinder HLA Credential Manager is obtaining an appropriate credential collector.
[14 Aug 2011 04:30:32,130] [WebContainer : 0] [INFO] High Level Agent returning the SMSESSION credential collector.
[14 Aug 2011 04:30:32,346] [WebContainer : 0] [DEBUG] SiteMinder HLA SMSESSION cookie credential collector successfully decrypted the SMSESSION cookie.

 

Resolution

 

To configure those log for debug, you need to "loglevel=5" in smagent.properties and smassertion.conf file.
You also need to insure that you are using different file names SmWasAsaDefault.log, Smwasasassertion.log.

Also make sure that allowlocalconfig is set to YES in the ACO associated with the ASA.