1. Log in to Enterprise Manager.
2. Click Setup, then Add Targets, and finally Add Targets Manually.
3. Select Target Type as JBoss Enterprise Application Platform, select a Monitoring Agent and then click Add Manually.
4. In the Add JBoss Enterprise Application Platform page, enter the following properties:
   • Target Name: Unique target name across all Cloud Control targets, such as JBoss_EAP_Hostname. This is the display name in Cloud Control. It represents this SQL Server target across all user interfaces within Cloud Control.
   • JBoss Monitoring Credentials
     • JBoss JMX Username: The username used to connect via JMX to JBoss. This is optional and should only be used if you are using authentication.
     • JBoss JMX Password:The password for the account used to connect via JMX to JBoss. This is optional and should only be used if you are using authentication.
   • JBoss SSL Truststore Password: The password for the truststore used to connect via JMX to JBoss. This is optional and should only be used if you are connecting with SSL.

     Note:

     The Trust Store path is required under properties.
   • Properties
     • SSL Trust Store: This is the trust path to the trust store being used to connect to JBoss via SSL. This is optional and should only be used if you are connecting using SSL.
     • Service URL: This is the JMX Service URL to connect to JBoss via JMX. This can look different depending on what version of JBoss you are using and if you are connecting using securely or not.

       JBoss Version	Service URL
       JBoss 6 (with SSL)	service:jmx:remote+https://<hostname>:<port>
       JBoss 6 (without SSL)	service:jmx:remote://<hostname>:<port>
       JBoss 7 (with SSL)	service:jmx:remote+https://<hostname>:<port>
       JBoss 7 (without SSL)	service:jmx:remote+http://<host>:<port>

   • Adding Targets with EMCLI

     To add JBoss EAP targets with EMCLI, use the add_target verb, as shown in the following example:

     emcli.bat add_target 
         -name=”JBoss Target” 
         -type=”oracle_jboss” 
         -host=”HostTargetName” 
         -properties=”serviceURL+service:jmx:remote://host:port” 
         -subseparator=properties=”+”

     You will need to specify the following options:

     • Target name: *-name*

       It must begin with an alphabetic character contain only alphanumeric characters, multibyte characters, a space, -, _, ., :, /, (, ) and have a maximum length of 256 characters.

     • Target type: *-type*

       Always use "oracle_jboss" (including the quotes).

     • Host name: *-host*

       Network name of the machine running the Management Agent that is collecting data for this target instance.

     • Target instance Properties: *-properties*

       Name-value pair list of properties for the target instance. The available property names are as follows.

       serviceURL
       JMXUsername
       JMXPassword
       SSLTrustStore
       SSLTrustStorePassword

     • Properties separator delimiter: *-separator=properties*

       Specify a string delimiter to use between name-value pairs for the value of the -properties option. The default separator delimiter is “;”.

     • Properties subseparator delimiter: *-subseparator=properties*

       Specify a string delimiter to use between name and value in each name-value pair for the value of the -properties option. The default subseparator delimiter is “:”.

     Verifying and Validating the Plug-in

     After waiting a few minutes for the plug-in to start collecting data, use the following steps to verify and validate that Enterprise Manager is properly monitoring the plug-in target:

     1. Click the JBoss target link from the All Targets page.
     2. Verify no metric collection errors are reported by clicking Monitoring and then Metric Collection Errors from the Target menu.
     3. Ensure that reports can be seen, and no errors are reported by clicking Information Publisher Reports in the Target menu and viewing reports for the JBoss EAP target type.
     4. Ensure that configuration data can be seen by clicking Configuration and then Last Collected in the Target menu. If configuration data does not immediately appear, click Refresh in the Latest Configuration page.

How to verify and validate the JBoss EAP plug-in for Enterprise Manager.