11.2. Enabling Remote Access to JMX and Profile Service
Management tasks like monitoring and running operations require that the agent is able to connect to the JMX server for the JBoss EAP/AS instance. This means that remote JMX access must be enabled.
- Verify that the JBoss Naming Protocol server (JNP) is deployed. (It is deployed by default.)Open the
jboss-service.xmlfile:[root@server ~]# vim jbossInstallDir/server/config/conf/jboss-service.xml
Then, make sure that there is a line enabling the JNP connector.<mbean code="org.jboss.naming.NamingService"> ... </mbean>
- While not required, it is recommended that you enable authentication for the JNP service. (This is enabled by default.)
- Open the
jmx-invoker-service.xmlfile.[root@server ~]# vim jbossInstallDir/server/config/deploy/jmx-invoker-service.xml
- Add a line for the JMX connector authentication.
<interceptor code="org.jboss.jmx.connector.invoker.AuthenticationInterceptor" securityDomain="java:/jaas/jmx-console"/> - Make sure that the admin user is listed in the JMX users properties file. When a new JBoss EAP resource is discovered, the agent reads the JMX username and password from this file and stores them in the discovered JBoss EAP resource's connection settings. These settings are then used to connect to the EAP server's JNP service.
[root@server ~]# vim jbossInstallDir/server/config/conf/props/jmx-console-users.properties
- Uncomment or add the user information. This is a simple key/value pair, username=password. For example:
admin=admin
- Restart the JBoss EAP/AS server.
