Web Agent traces configuration for connection and clustering information

Products

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

Issue/Introduction

 

When having connection issues in Web Agents with Policy Servers communication, the Web Agent traces does not provide enough information to determine the reason why a Web Agent chooses one Policy Server or another in the Cluster, or which connectivity problems is having.

 

Environment

 

Web Agent: 12.52.x

 

Resolution

 

To get this information, enable the Agent_Con_Manager component in the Web Agent traces. To do this, follow the steps below:

1. Edit the WebAgentTrace.conf being used by the Web Agent (under <webagent_home>/config folder);
2. Go to the bottom of the file, and locate the following lines:
     
   components:  AgentFramework, HTTPAgent, WebAgent
data: Date, Time, Pid, Tid, SrcFile, Function, TransactionID, IPAddr, IPPort, AgentName, Resource, User, Message
   
   
3. Modify the lines with the following:
        
   components: AgentFramework, HTTPAgent, WebAgent, AgentFunc, Agent_Con_Manager
data: Date, Time, PreciseTime, Pid, Tid, TransactionID, Message, SrcFile, Function, RequestIPAddr, IPAddr, IPPort, AgentName, Domain, DomainOID, Realm, RealmOID, Resource, Action, User, SessionSpec, SessionID, CertSerial, SubjectDN, IssuerDN, UserDN, Threshold, Throughput, MinThroughput, MaxThroughput, HandleCount, BusyHandleCount, FreeHandleCount, State, ClusterID
   
   
4. Save the changes, and restart the Web Agent.

Additional information in the traces will be generated to help troubleshoot the issues.

Note that above additional components come from 2 other config templates located in the same directory of WebAgentTrace.conf:

  AgentConMgr.conf
  AgentFunctions.conf