Using Enterprise Manager Cloud Control, you can do the following with JBoss Application Server targets:

• Discover the following for central monitoring and management:

  • JBoss Application Servers

  • JBoss Server Groups and Domains (for version 7.x)

    JBoss Domain is a logical grouping of JBoss Application Servers within your enterprise configuration for JBoss Application Servers version 7.x. JBoss Application Servers are grouped into Server Groups and one or more Server Groups form a JBoss Domain. The Domain Controller runs and manages the collection of JBoss Application Servers within a domain.

    When you discover a JBoss Domain, the JBoss Domain, the JBoss Server Groups and all other up and running JBoss Application Servers that are part of that JBoss Domain get automatically discovered. You can select the JBoss Application Servers that you want to add to Enterprise Manager Cloud Control for monitoring, and the associated JBoss Server Groups are automatically added.

• Monitor the status, the availability percentage, the CPU usage, the heap usage, the Java vendor and version used, and so on.

• Monitor the status and the overall health of the member application servers that are part of JBoss Domains and Partitions.

• Monitor the performance by measuring the load and the request processing time for a given interval.

• Diagnose, notify, and correct performance and availability problems with the help of GUI-rich, intuitive graphs and illustrations.

• Monitor the status of the deployed applications.

• View details about the associated JVM threads and data sources.

• Create or end blackouts as well as notification blackouts to suspend or resume the collection of metric data, respectively.

• View compliance-related information, such as the compliance standards and frameworks associated with the server, the real-time observations, the evaluation results, and so on.

• View a list of metrics, their collection interval, and the last upload for each metric.

1. Log in to https://support.oracle.com/
2. On the My Oracle Support home page, select Certifications tab.
3. On the Certifications page, enter the following search criteria in the Certification Search section.

   • Enter the product name Enterprise Manager Base Platform - OMS in the Product field.

   • Select the release number 13.3.1.0.0 from the Release list.

4. Click Search.
5. In the Certification Results section, expand the Application Server menu to view the certified JBoss Application Server versions.
   
   

   

   
   

1. From the Targets menu, select Middleware.
2. On the Middleware page, from the Add menu, select JBoss Application Server.

   Enterprise Manager Cloud Control displays the JBoss Discovery Wizard.

3. On the Host page, enter details about the host on which the JBoss Application Server is running.

   Figure 27-1 JBoss Application Server Host Page

   
   

   

   
   

   Element	Description
   Version	Select the version of the JBoss Application Server you want to discover.
   Discovery Mode	Select either Standalone or Domain.
   JBoss Application Server Host /JBoss Domain Controller Host	If you have selected standalone server enter the host address where the JBoss Server is running, and if you have selected domain enter the host address where the JBoss Domain Controller is running.
   HTTP Management Port	Depending on wether you have selected a standalone server or domain, specify the HTTP Management port of the JBoss Application Server or the Domain Controller.
   Agent	Select the Management Agent that is installed on the host where the JBoss Application Server is running.
   Authentication Type	Select the authentication type. The available options are None, Basic and HTTP Digest.
   Username	Enter the user name for authentication.
   Password	Enter the password for authentication.

   Click Next.

4. On the Select Server page, view a list of JBoss Domains, JBoss Server Groups and standalone JBoss Application Servers discovered on the host you specified, and to select the ones you want to add and monitor in Enterprise Manager Cloud Control.

   Figure 27-2 JBoss Application Server Select Server Page

   
   

   

   
   

   Column	Description
   Name	Name of the JBoss Domains and Server Groups and standalone JBoss Application Servers discovered on the specified host.
   Select	Select the JBoss Application Server(s) that you want to add and monitor in Enterprise Manager Cloud Control. Note: When you select a JBoss Application Server, the associated JBoss Domain and Server Group also gets selected for monitoring.
   Type	Type of JBoss target discovered on the specified host. They can be either JBoss Domain, JBoss Server Group or JBoss Application Server.
   HTTP Listen Port	The HTTP listener port that is configured.
   HTTPS Listen Port	The HTTPS listener port that is configured.
   Host Name	The name of the JBoss Application Server host.
   Version	Version of the JBoss Application Server discovered on the specified host.

   Click Next.

5. On the Review page, review the details you have provided for discovering and adding JBoss targets to Enterprise Manager Cloud Control. Click Submit to discover the JBoss targets.

This section covers the following:

• Monitoring JBoss Application Servers 7.x

• Administering JBoss Application Servers 7.x

• Monitoring Applications Deployed to JBoss Application Servers 7.x

• Monitoring the Performance of JBoss Application Servers 7.x

• Viewing JBoss Application Server Metrics

• Analyzing Problems Using Metric Correlation

This section covers the following:

• Monitoring JBoss Domains

• Monitoring JBoss Server Groups

• Administering JBoss Domains

• Viewing JBoss Domain Members

• Refreshing JBoss Domains

This section covers the following:

• Monitoring JBoss Partitions

• Administering JBoss Partitions

• Viewing JBoss Partition Members

• Refreshing JBoss Partitions

1. User can download jamagent.war from Setup--> Middleware Management --> Engines And Agents--> Download Jvmd Agent.

   Figure 27-9 Download JVM Diagnostics Components

   
   
   
2. From the Download JVM Diagnostics Components window, select JVMD Agent, then click OK.
3. From the JVM Diagnostics Agent web.xml Parameters window, select the appropriate JVMD manager from the Available Managers list.

   Figure 27-10 JVM Diagnostics Agent web.xml Parameters

   
4. Uncheck the WebLogic Server checkbox, enter a pool name, then click Download.

   This will download the jamagent.war file. You need to copy this file to the target machine (the machine where the JBoss is running).

5. [Optional] Copy the following script to the same location on the target machine where the jamagent.war. file was copied:

   
   #!/bin/sh
   
   
   # Edit this if jamagent.war is not in the current dir & point it to its new location
   
   WARFILE="jamagent.war"
   
   
   #UNPACK="jar xf"
   
   UNPACK="unzip -qo"
   
   #PACK="jar uf"
   
   PACK="zip -q"
   
   
   #if no arguments are passed, print usage statement & exit
   
   [ -n "$1" ] || ( echo "Usage: ${0} [node1] [node2] ... [node n]"; exit 0 ; )
   
   WEBXMLFILE="WEB-INF/web.xml"
   
   SINGLEINDENT="\ \ \ \ \ \ \ \ "
   
   DOUBLEINDENT="\ \ \ \ \ \ \ \ \ \ \ \ "
   
   INSERTPREFIX=
   
   "${SINGLEINDENT}<init-param>\n${DOUBLEINDENT}<param-name>jamjvmid</param-name>\n${DOUBLEINDENT}<param-value>"
   
   INSERTSUFFIX="</param-name>\n${DOUBLEINDENT}<description>The ID of this
    JVM</description>\n${SINGLEINDENT}</init-param>"
   
   INSERTBEFORE="<load-on-startup>" 
   
   # Iterate over each node name (i.e. command line argument)
   
   for NODE_NAME in "$@"
   
   do
   
     echo "Processing ${NODE_NAME}"
   
     # Make a copy of the war file that is node specific
   
     cp ${WARFILE} ${NODE_NAME}-${WARFILE}
   
     # Extract the web.xml file
   
     ${UNPACK} ${NODE_NAME}-${WARFILE} ${WEBXMLFILE}
   
     # Construct the XML block to be inserted using the node name
   
     INSERTBLOCK=${INSERTPREFIX}${NODE_NAME}${INSERTSUFFIX}
   
     # Insert the xml block into web.xml
   
     sed -i "/${INSERTBEFORE}/i ${INSERTBLOCK}" ${WEBXMLFILE}
   
     # Add the web.xml back into the war file
   
     ${PACK} ${NODE_NAME}-${WARFILE} ${WEBXMLFILE}
   
     #tail -15 ${WEBXMLFILE}
   
     # Cleanup all the temp stuff
   
     rm ${WEBXMLFILE}
   
     rmdir WEB-INF/
   
     # TIP: You could try to deploy the war file directly from here using something like
   
     #cp ${NODE_NAME}-${WARFILE} ${DEPLOYMENT-DIR-OF-THIS-NODE}
   
   done

6. Run the script passing the names of the JBoss instances (or whatever names you give to the JVM of each JBoss server). The name has to be unique for each server.

   This script will create a separate jamagent WAR for each name you pass to this script.

7. Deploy each of these created WARs on the respective JBoss server. Typically you can use the admin console or copy the WAR file to the deploy folder.

   If the hot deployment is not enabled, you may have to restart the JBoss server. Once the WAR is deployed successfully, you will see the respective JVM target on the Middleware page.