Websphere Java Agent Name Auto Naming error

Document ID : KB000004880
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

On a Java agent installed on Websphere, the autonaming functionality is not working.  It issues this agent log error:

[IntroscopeAgent.Agent] Unable to automatically determine the Agent Name because: The Application Server naming mechanism is not yet available.

Setting up a custom service did not solve the issue.

Environment:
Java agent 10.1WAS 7.0Suse
Cause:

Besides custom service, if Java2 Security is enabled on WAS, permissions needs to be added to server.policy. 

Resolution:

a.) create a custom service, as described in:

https://docops.ca.com/ca-apm/10-1/en/extending/ibm-websphere-application-server-distributed-environments/installing-apm-for-ibm-websphere-application-server-distributed/install-and-configure-apm-for-ibm-websphere-application-server-distributed/creating-custom-service-and-enable-the-pmi-modules/through-the-websphere-application-server-administration-console-manual-setup/configure-a-custom-service-in-websphere

 

b.) If Java2 Security is enabled, it is necessary to modify server.policy:

https://docops.ca.com/ca-apm/10-1/en/implementing-agents/java-agent/install-the-java-agent/configure-application-server-to-use-the-java-agent/websphere#WebSphere-ModifyJava2SecurityPolicy

 

Please note:

When the following lines are not effective:

// permissions for Introscope AutoProbe

grant codeBase "file:${was.install.root}/-" {

permission java.io.FilePermission "${was.install.root}${/

}wily${/}-", "read";

 

Please use the following:

// permissions for Introscope PMI support 

grant codeBase "file:${was.install.root}/-" { 

permission java.security.AllPermission; 

};