Symptoms:
- SaaS agent start up successfully but is not visible in the Investigator, Webview or TeamCenter
- In the Agent log you can find below messages:
a) Agent log indicate that Agents are connected but in disallowed mode, for example:
1/10/20 12:00:46 PM EST [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected controllable Agent to the Introscope Enterprise Manager at em:5001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "muntest000477", Process = "TomcatProcess", Agent Name = "QAtestapp", Active = "false".
1/10/20 12:00:46 PM EST [INFO] [IntroscopeAgent.ConnectionThread] Connected to em:5001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory in disallowed mode.
b) Agent indicates that Agent is unable to connect due to client not compatible:
3/24/20 09:41:05 AM UTC [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at em:5001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (com.wily.isengard.postofficehub.auth.FailedToAuthenticateException:Invalid credentials for group name 'Agent'. Perhaps the client is not compatible with the server.).
APM Enterprise Manager 10.7
DXI APM SaaS agents or DX APM Onpremise 11.x, 19.x, 20.x
1. Stop the Agent
2. Open the \core\config\IntroscopeAgent.profile
a) Add hidden property:
introscope.agent.connection.compatibility.version=10.7
b) Comment agentManager.credential as below:
#agentManager.credential=<your agent token>
Or set it to an empty value:
agentManager.credential=
c) Configure the connection to your EM 10.7
agentManager.url.1=<em-10.7-host>:<em-port>
comment
#agentManager.url.2=https://apmgw.dxi-na1.saas.broadcom.com:443
4. Restart the application or monitor
For Java application in CloudFoundry, you can use 1 of the below options:
a) cf cups introscope -p '{"agent_manager_url”:”em-10.7-host:em-port", "introscope_agent_connection_compatibility_version":"10.7", "credential":"”}'
b) update the configuration using the Apps Manager as below: