Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.3/html/Users_Guide/special-discovery.html Section Number and Name: 5.3.1. Configuring the Agent to Discover EAP 6 Instances Describe the issue: This chapter is valid for both EAP6 and EAP7 so both versions should be mentioned.
From Scott: Edited topic 43725 "Configuring the Agent to Discover EAP 6 Instances" [1] so it no longer refers to EAP 6 specifically (under the assumption that the content is as valid for the EAP 7 plugin as it is for version 6) 1: http://docbuilder.usersys.redhat.com/23086/#special-discovery
Turned out that original description is incorrect. run.jar file is available only on EAP5 and earlier. Whole chapter could look like this: ------- 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 EAP5 and earlier the agent must have read permissions to the run.jar file, plus execute and search permissions for every directory in the path to the run.jar file. For EAP6/EAP7 the agent must have read permissions to the EAP6/7 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. ------- Also referenced Table 4.1. Cheat Sheet for Agent and Resource Users should be updated accordingly as well.