How to configure Web Agent traces to see connection and clustering information

Document ID : KB000116285
Last Modified Date : 28/09/2018
Show Technical Document Details
Introduction:
I am having connection issues in my Web Agents when reaching Policy Servers, but in Web Agent traces I do not see enough detail to determine why an Agent chooses one Policy Server or another in the cluster, or which connectivity problems is having. What can I do?
Environment:
Web Agent R12.52 SP1
Instructions:
In order to get this information, you can enable the Agent_Con_Manager component in the Web Agent traces. To do this, follow the steps below:

1) Edit your 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 changing Time data field by PreciseTime, and adding the Agent_Con_Manager component, like:
components:  AgentFramework, HTTPAgent, WebAgent, Agent_Con_Manager
data: Date, PreciseTime, Pid, Tid, SrcFile, Function, TransactionID, IPAddr, IPPort, AgentName, Resource, User, Message
4) (Optional) You can increase the details of the data fields adding more of them, like:
data: Date, PreciseTime, Pid, Tid, TransactionID, Function, Message, SrcFile, User, Domain, Realm, AgentName, DomainOID, IPAddr, IPPort, RequestIPAddr, CertSerial, SubjectDN, IssuerDN, SessionSpec, SessionID, UserDN, Resource, Action, RealmOID, ResponseTime
5) Save your changes, and restart the Web Agent.

You will see this additional information in the traces generated to help you troubleshoot the issue.