5.3. Resources That Require Additional Configuration for Discovery
There are some resource types which require specific configuration for the resource or for the JBoss ON agent in order for them to be discovered.
5.3.1. Configuring the Agent to Discover EAP Instances
As covered in Chapter 4, Interactions with System Users for Agents and Resources, the system user as which the agent runs has a direct effect on how the agent can manage certain resource types. For EAP instances, the agent's system user must have the appropriate permissions to be able to manage EAP resources:
- For JBoss EAP 5 and earlier, the agent must have read permissions to the
run.jarfile, plus execute and search permissions for every directory in the path to therun.jarfile. - For JBoss EAP 6 and 7, the agent must have read permissions to the application server's configuration files.
- When a JBoss EAP instance is installed from an RPM, the agent user must belong to the same system group which runs the EAP instance. This is jboss, by default.
5.3.2. Configuring Tomcat/EWS Servers for Discovery (Windows)
Tomcat servers are discovered automatically on Linux and Unix systems, but they require additional configuration before they can be discovered on Windows systems.
- Run regedit.
- Navigate to Java preferences key for the Tomcat server,
HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun2.0\TomcatVer#\Parameters\Java. - Edit the Options attribute, and add these parameters:
-Dcom.sun.management.jmxremote.port=9876 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false
- Restart the Tomcat service.
After a few minutes, the Tomcat instance should show up in the Discovery Queue.
