Skip Headers
Oracle® Enterprise Manager Cloud Control Oracle Fusion Middleware Management Guide
Release 12.1.0.6

E24215-12
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

35 Discovering and Monitoring JBoss Application Server

JBoss Application Server is the market-leading, open source Java Platform, Enterprise Edition (Java EE) application server, delivering a high-performance and enterprise-class platform for e-business applications. JBoss provides enterprise-class security, transaction support, resource management, load balancing, and clustering.

JBoss Partition is a logical grouping of JBoss Application Servers within your enterprise configuration. The status of JBoss Partition depends upon the status of all its members, that is the JBoss Application Servers within the partition.

Enterprise Manager Cloud Control enables you to discover JBoss Application Servers and JBoss Partitions in your environment, and add them for central monitoring and management.

This chapter describes how you can discover and monitor these JBoss Application Server targets in Enterprise Manager Cloud Control. In particular, this chapter covers the following:

35.1 About Managing JBoss Application Servers and JBoss Partitions

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 Partitions

      When you discover a JBoss Application Server that is part of a JBoss Partition, the JBoss Partition and all other JBoss Application Servers that are part of that JBoss Partition gets automatically discovered and added to Enterprise Manager Cloud Control.

  • 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 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.

  • Monitor the Servlets and JSPs running on the application servers, including the most requested Servlets in the last 24 hours.

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

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

  • Monitor and manage configuration details that were last collected and also the ones that were saved at a given point of time.

  • Compare the configuration between:

    • A last collected configuration of a server instance with a saved configuration of the same server instance or a different server instance.

    • A last collected configuration of a server instance with a last collected configuration of a different server instance.

    • A saved configuration of a server instance with another saved configuration of the same server instance or a different server instance.

    • A saved configuration of a server instance with a last collected configuration of the same server instance or a different server instance.

  • 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.

35.2 Supported Versions for Discovery and Monitoring

To search for the JBoss Application Server versions that are supported for discovery and monitoring in Enterprise Manager Cloud Control, follow these steps:

  1. Log into 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 12.1.0.4.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.

    JBoss Certified Versions

35.3 Prerequisites for Discovering JBoss Application Servers and JBoss Partitions

Meet the following prerequisites for discovering JBoss Application Servers and JBoss Partitions.

  • Ensure that you use only Oracle Management Agent 12c Release 3 (12.1.0.3) or higher for discovery.

  • Ensure that you download and extract the JBoss Application Server ZIP file, and set the JBOSS_HOME and PATH environment variables as follows:

    setenv JBOSS_HOME <jboss_install_location> 
    setenv PATH "${PATH}:/${JBOSS_HOME}/bin"
    
  • If you are adding JBoss Application Server 4.x or 5.x, then ensure that you meet the following prerequisites:

    1. In the run.conf file that is present in the $<JBOSS_INSTALL_HOME>/bin directory, add the following entries:

      JBoss Application Server 4.x

      Make a note of the port used here, as the same port must be used for discovery.

      JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=<any_unused_port>"
      JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.authenticate=false"
      JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.ssl=false"
      JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"
      JAVA_OPTS="$JAVA_OPTS -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl" 
      

      JBoss Application Server 5.x

      JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver" 
      
    2. Restart the JBoss Application Servers.

  • Ensure that you start the JBoss Application Server or the JBoss Partition by running the following command from the bin directory:

    ./run.sh -c <deployment_profile> -b <binding_address> [-Djboss.partition.name=<partition_name>] 
    

    Here, <deployment_profile> indicates whether you are starting a standalone JBoss Application Server or a JBoss Partition. The <binding_address> is the host name or the IP address running the JBoss Application Server. The <partition_name> is the partition name from where the JBoss Application Servers must start. By default, they start as part of DefaultPartition.

    For example,

    ./run.sh -c node1 -Djboss.service.binding.set=ports-01 -b example.oracle.com
    

    Note:

    • To start a standalone JBoss Application Server, set the <deployment_profile> to default.

      For example,

      ./run.sh -c default -b <binding address>
      
    • To start a JBoss Partition, enable the JBoss clustering service, set the <deployment_profile> to all.

      For example,

      ./run.sh -c all -b <binding address>
      
    • To start multiple server instances on the same host, complete the following:

      (a) Create multiple deployment profiles as per your requirements.

      (b) Use a different port-set to start the individual servers. Note that ports-01, ports-02, ports-03, and ports-04 are predefined port-sets.

      For example,

      -Djboss.service.binding.set=ports-01 
      

35.4 Discovering JBoss Application Servers and JBoss Partitions

Note:

Discovery is not supported if the JBoss Application Server is monitored with Oracle Management Agent 12c Release 2 (12.1.0.2) or lower.

To discover JBoss Application Servers and JBoss Partitions, follow these steps:

  1. From the Targets menu, select Middleware.

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

  3. Click Go.

    Enterprise Manager Cloud Control displays the JBoss Discovery Wizard.

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

    Figure 35-1 JBoss Application Server Host Page

    JBoss Application Server Host Page
    Element Description
    JBoss Application Server Host Enter the name of the host where the JBoss Application Server is running.
    JMX Connector Port Enter the JMX connector port number.
    Agent Select the Management Agent that is installed on the host where the JBoss Application Server is running.
    Version Select the version of the JBoss Application Server you want to discover.
    Username Enter the JMX user name for authentication.
    Password Enter the JMX password for authentication.

  5. On the Select Server page, view a list of JBoss Partitions 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 35-2 JBoss Application Server Select Server Page

    JBoss Select Server Page
    Column Description
    Name Name of the JBoss Partitions and standalone JBoss Application Servers discovered on the specified host.
    Select Select the JBoss Partition or standalone JBoss Application Server that you want to add and monitor in Enterprise Manager Cloud Control.

    Note: When you select a JBoss Application Server, the associated JBoss Partition also gets selected for monitoring.

    Type Type of JBoss target discovered on the specified host. They can be either JBoss Partition or JBoss Application Server.
    Port Enter the JMX connector port of the JBoss Application Server. By default, the port number appears for a JBoss Application Server target if you entered it in the previous page of the wizard. Otherwise, the field is blank.
    Username Enter the JMX user name for authentication.
    Password Enter the JMX password for authentication.
    Version Version of the JBoss Application Server discovered on the specified host.

    Note:

    Enterprise Manager Cloud Control does not validate the values you provide for User Name and Password. So if you provide incorrect values, Enterprise Manager will add the JBoss target without displaying any errors now, but will eventually show the status as Down.
  6. 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.

Note:

When you discover a JBoss Application Server that is part of a JBoss Partition, the JBoss Partition and all other JBoss Application Servers part of that partition get automatically discovered and added to Enterprise Manager Cloud Control. At any point after discovering a JBoss Partition, if new JBoss Application Servers are added to the partition, then you can refresh the JBoss Partition as described in Section 35.7.3.

35.5 Migrating to JMX-Based Monitoring of JBoss Application Servers

JBoss Application Server monitoring with Enterprise Manager Cloud Control 12c Release 3 (12.1.0.3) or lower with Oracle FMW Plug-in 12.1.0.5 or lower was essentially based on Java EE Management EJB (MEJB), a JSR-77 standard way of exposing enterprise management functionality. However, starting from Enterprise Manager Cloud Control 12c Release 4 (12.1.0.4), the JBoss Application Server monitoring is based on Java Management Extensions (JMX) technology.

With this change in technology, Enterprise Manager Cloud Control now eliminates the need for deploying the MEJB JAR file (ejb-management.jar) on hosts where JBoss Application Servers are running, which was earlier a prerequisite for discovery. In addition, Enterprise Manager Cloud Control now offers new, additional, enhanced metrics.

Oracle strongly recommends that you move to JMX-based monitoring so that you benefit from the enhancements the new approach offers. Otherwise, the monitoring of JBoss Application Servers will continue to be done using MEJB, the newly introduced metrics will not appear, and the prerequisite on deploying the MEJB JAR file as a prerequisite for discovery will continue to exists.

For JBoss Application Servers Already Discovered and Monitored in Enterprise Manager

For JBoss Application Servers already discovered and monitored in Enterprise Manager Cloud Control 12c Release 3 (12.1.0.3) or lower with Oracle FMW Plug-in 12.1.0.5 or lower, do the following:

  1. Upgrade both Oracle Management Service and Oracle Management Agent to 12c Release 4 (12.1.0.4) or higher.

  2. Upgrade the Oracle FMW Plug-in to 12.1.0.6 or higher.

  3. Migrate to JMX-based monitoring.

    1. From the Targets menu, select Middleware.

    2. On the Middleware page, do one of the following:

      For Standalone JBoss Application Servers

      (i) On the Middleware page, click the desired JBoss Application Server.

      (ii) On the JBoss Application Server home page, from the JBoss Server menu, select Target Setup, then select Migrate to Use JMX.

      (iii) On the Migrate to Use JMX page, enter the JMX port to be used for the selected JBoss Application Server.

      (iv) Click Submit. For JBoss Application Servers that are grouped in a JBoss Partition

      (i) On the Middleware page, click the JBoss Partition.

      (ii) On the JBoss Partition page, from the JBoss Partition menu, select Target Setup, and then select Migrate to Use JMX.

      (iii) On the Migrate to Use JMX page, enter the JMX ports to be used for all the JBoss Application Servers that are part of the partition. (iv) Click Submit.

Note:

If your Enterprise Manager Cloud Control is currently at 12c Release 1 (12.1.0.1), 12c Release 2 (12.1.0.2), or 12c Release 3 (12.1.0.3), and if you are unwilling to upgrade your OMS and Management Agent to 12c Release 4 (12.1.0.4) or higher, then in the current release, do the following for each of the discovered JBoss Application Servers so that they show the accurate status in their Home pages.
  1. On the JBoss Application Server Home page, from the JBoss Server menu, select Target Setup, then Monitoring Configuration.

  2. Enter the library path you provided while discovering the JBoss Application Server, and click OK.

  3. Restart the Management Agents.

For New JBoss Application Servers to Be Discovered in Enterprise Manager

For new JBoss Application Servers to be discovered and monitored in Enterprise Manager Cloud Control 12c Release 4 (12.1.0.4), do the following:

  1. Upgrade both Oracle Management Service and Oracle Management Agent to 12c Release 4 (12.1.0.4) or higher.

  2. Upgrade the Oracle FMW Plug-in to 12.1.0.6 or higher.

  3. Deploy a Management Agent on the host where the JBoss Application Server to be discovered is running. For instructions, see Installing a Fresh Oracle Management Agent.

  4. Add the JBoss Application Server to Enterprise Manager Cloud Control. For instructions, see Adding JBoss Application Server.

35.6 Monitoring JBoss Application Servers

This section covers the following:

Note:

To view a visual demonstration on how to monitor and manage JBoss Application Server targets, access the following URL and click Begin Video. The monitoring and management described in this visual demonstration is based on Enterprise Manager Cloud Control 12c Release 3 (12.1.0.3).

http://apex.oracle.com/pls/apex/f?p=44785:24:0::::P24_CONTENT_ID,P24_PREV_PAGE:8530,1

35.6.1 Monitoring JBoss Application Servers

To monitor JBoss Application Servers, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired JBoss Application Servers.

  3. On the JBoss Application Server Home page, you can view a summary of the most critical information pertaining to JBoss Application Server. You can view general information about the server, information about the Servlets and JVM threads running on the server, and performance summary in terms of load and response time.

    JBoss Application Server Home Page

The JBoss Partition Home page has the following sections:

General Section

Element Description
Up/Down/Pending Since Date and time when the status was last determined.
Availability (%) Indicates whether the JBoss Application Server is available and the availability percentage over the last 24 hours. To drill down to the Status History (Availability) page, click the link. The Status Histroy page displays the availability of the JBoss Application Server along with the availability history of the constituents that are used to compute its availability.
Version Version of the JBoss Application Server.
Status Current status of the JBoss Application Server. The status can be down even if incorrect JMX credentials were provided while discovering the JBoss target.
Server CPU Usage (%) Percentage of CPU time used by the JBoss Application Server.
Heap Usage (MB) Amount of heap space (in MB) used by the JBoss Application Server over a given interval.
Java Vendor Vendor of the Java Virtual Machine that this JBoss Application Server runs.
Java Version Version of the Java Virtual Machine that this JBoss Application Server runs.

Servlet Section

Element Description
Active Sessions Number of active servlet sessions.
Request Processing Time (ms) Average time taken (in milliseconds) to service a request in the last 24 hours.
Requests (per min) Number of requests serviced per minute in the last 24 hours.

JVM Threads

Element Description
JVM Threads - Active Threads Number of active JVM threads, including both daemon and non-daemon threads.
JVM Threads - Peak Threads Number of peak active JVM threads since the Java Virtual Machine started or peak was reset.
JVM Threads - Active Daemon Threads Number of active daemon JVM threads.
JVM Threads - Threads Created (per min) Number of JVM threads created per minute.

Datasource

Element Description
Total connections in Use Number of active database connections in this instance of the data source since the data source was instantiated.
Total connection Pool Size Total size of the connection pool.
Total connections Created (per min) Number of connections created per minute for this data source.
Total connections Destroyed (per min) Number of connections closed per minute for this data source.

Response and Load Section

Provides a graphical representation of the server's performance, measuring request-processing time for a given interval. To switch to a tabular format, click Table View. To drill down and view more detailed metric-related information and to diagnose issues by looking at other related infrastructure metrics, click the metric names in the legend and select an appropriate option in the Additional Information message.

Most Requested Servlets (last 24 hours)

Provides details of the most requested servlets in the last 24 hours.

35.6.2 Administering JBoss Application Servers

To administer JBoss Application Servers, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired JBoss Application Server.

  3. On the JBoss Application Server Home page, you can view high-level information pertaining to the selected JBoss Application Server.

    To perform administrative tasks on the JBoss Application Server, from the JBoss Server menu, select any of the following according to your needs:

    • Monitoring, to monitor the performance of the target, view metric details, view status information, view incidents and alerts raised so far for the target, and view blackouts created for the target.

    • Diagnostics, to analyze and diagnose performance issues.

    • Control, to create or end blackouts.

    • Job Activity, to view details of the jobs created for the target.

    • Information Publisher Reports, to view reports.

    • Configuration, to search, view, and compare configuration details.

    • Compliance, to view and create compliance standards.

    • Target Setup, to view monitoring configuration details and target properties, to remove the target or add it to a group, to migrate and use JMX.

    • Target Sitemap, to view the overall topology of the target.

    • Target Information, to view general information about the target.

35.6.3 Monitoring the Applications Deployed to JBoss Application Servers

To monitor the applications deployed to JBoss Application Servers, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the JBoss Application Server where the Servlets and JSPs are deployed.

  3. On the JBoss Application Server Home page, from the JBoss Server menu, select Monitoring, then select Performance Summary.

  4. On the Performance Summary page, scroll down to the Applications section.

35.6.4 Monitoring the Performance of JBoss Application Servers

Enterprise Manager Cloud Control helps you monitor the overall performance of JBoss Application Servers. You can view the graphs that depict their memory usage and heap usage, and see details about the servlets and JSPs. This helps you gauge the performance and perform a root cause analysis to drill down to the problem areas and fix them before they affect the end users.

To monitor the performance of a JBoss Application Server:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the JBoss Application Server whose performance you want to monitor.

  3. On the JBoss Application Server Home page, from the JBoss Server menu, select Monitoring, then select Performance Summary.

  4. On the Performance Summary page, you can do the following:

    • View a set of performance charts, monitor the performance over a given interval, and diagnose and correct problems.

    • Customize the set of performance charts that appear on the page. To do so, click Show Metric Palette, and select the charts you want to add to the page.

    • Show or hide the Metrics Palette. To do so, click Show Metric Palette or Hide Metric Palette, respectively.

    • Reorder the performance charts. To do so, from the View menu, select Reorder Charts.

    • Customize the performance charts to show or hide availability and threshold details, and grid lines. To do so, from the View menu, select Availability, Thresholds, or Grid Lines, respectively.

    • Draw a comparison with another IBM WebSphere Application Server's performance, or with the previous day's performance. To do so, from the Compare menu, select With Another IBM WebSphere Application Server or Today with Yesterday, respectively.

    • Remove comparison. To do so, from the Compare menu, select Remove Comparison.

    • Create or delete baselines. To do so, from the Compare menu, select Create Baseline or Delete Baseline, respectively.

    • Delete metric performance charts either by clicking the close button on the chart itself, or by deselecting the metric name in the Metric Palette.

    • Change time frames using the slider, or set a default value.

    • Create new metric performance charts by selecting the preferred metrics from the Metric Palette. The charts are automatically created once the metrics are selected.

    • Drag and drop the metrics from a particular metric group to the same chart.

35.6.5 Monitoring the Servlets and JSPs Running on JBoss Application Servers

Enterprise Manager Cloud Control helps you monitor the Servlets and JSPs that are running on JBoss Application Servers. You can not only view high-level information about them but also a performance summary that reflects their response time and load. You can also dirll down and diagnose issues by viewing related infrastructure metrics, alert history, and so on.

To monitor the Servlets and JSPs running on JBoss Application Servers, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the JBoss Application Server where the Servlets and JSPs are deployed.

  3. On the JBoss Application Server Home page, do these:

    1. To view high-level information about the Servlets, see the Servlets region. To understand the metric details displayed in this region, click Help.

    2. To monitor the performance of Servlets and JSPs, see the response and load graphic.

    3. To drill down and diagnose issues, click a metric name in the legend. From the pop-up message, click Problem Analysis.

    4. To view metric statistics, thresholds, and metric value history, click a metric name in the legend. From the pop-up message, click Metric Details.

35.6.6 Viewing JBoss Application Server Metrics

To view all JBoss Application Server metrics, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired JBoss Application Server.

  3. On the JBoss Application Server Home page, from the JBoss Server menu, select Monitoring, then select All Metrics.

35.6.7 Analyzing Problems Using Metric Correlation

For information on spikes in the performance of metrics, you can use the Problem Analysis page to compare results between the source metric and related metrics. Currently, problem analysis is only available for the following metrics.

  • Server CPU Usage

  • Servlet and JSP - Request Processing Time

To access the Problem Analysis page, follow these steps.

  1. From the Performance Summary page, click the name of the metric next to the performance chart.

  2. From the window that pops up, select Problem Analysis.

    problem_analysis
  3. On the Problem Analysis page, you can compare the results of the Source Metric and the Related Metrics.

    problem_analysis_main

35.7 Monitoring JBoss Partitions

This section covers the following:

35.7.1 Monitoring JBoss Partitions

To monitor JBoss Partitions, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired JBoss Partition.

  3. On the JBoss Partition Home page, you can do the following:

    • View a summary of the most critical information pertaining to the JBoss Partition.

    • Monitor the status and availability of all the members within the JBoss Partition.

    • View the refresh status on the partition membership.

Using the JBoss Partition Home page, you can not only monitor the collective status of the partition but also the individual status of each of the members. You can also refresh the partition to update the membership and reflect the current deployment state. You can also view the member application servers' resource usage, availability, performance, configuration information, and reports with or without historical data.

The JBoss Partition Home page has the following sections:

General Section

The General section provides general information about JBoss Partition.

Element Description
Up/Down/Pending Since Date and time when the status was last determined.
Availability (%) Availability rate for the last 24 hours, considering the status of all the members of the JBoss Partition. For example, if there are four JBoss Application Servers within a partition, and if only three of them are up, then the pie chart shows 75% up and 25% down status.
Version Version of the JBoss Application Servers that are part of the JBoss Partition.
Agent Management Agent used for discovering the JBoss Application Servers that are part of the JBoss Partition. To drill down to the Management Agent home page, click the link.

Refresh Partition Section

The Refresh Partition section displays the date when the JBoss Partition was last refreshed. To refresh the membership of the JBoss Partition and to reflect the current deployment state, click Update the Partition.

Servers Section

The Servers section provides a real-time view of the status and availability of all the members within the JBoss Partition. For example, if there are four JBoss Application Servers within a JBoss Partition, and if three of these are up, then the pie chart shows 75% up and 25% down status. Accordinlgy, the legend shows 3 against the Up status to indicate the JBoss Application Servers that are up, and 1 against the Down status to indicate the server that is down.

The table provides high-level details of the JBoss Application Servers that are part of the JBoss Partition. To drill down and view information about a JBoss Application Server, click the JBoss Application Server name. To view more information about the status, click the status icon.

35.7.2 Administering JBoss Partitions

To administer JBoss Partitions, follow these steps:

  1. From the Targets menu, click Middleware.

  2. On the Middleware page, click the desired JBoss Partition target.

  3. On the JBoss Partition Home page, you can view high-level information pertaining to the selected JBoss Partition.

    To perform administrative tasks on the JBoss Partition, from the JBoss Partion menu, select any of the following according to your needs:

    • Monitoring, to monitor the performance of the target, view metric details, view status information, view incidents and alerts raised so far for the target, and view blackouts created for the target.

    • Diagnostics, to analyze and diagnose performance issues.

    • Control, to create or end blackouts.

    • Job Activity, to view details of the jobs created for the target.

    • Information Publisher Reports, to view reports.

    • Members, to view details of the JBoss Application Servers that are part of the JBoss Partition.

    • Configuration, to search, view, and compare configuration details.

    • Compliance, to view and create compliance standards.

    • Target Setup, to view monitoring configuration details and target properties, to remove the target or add it to a group, to migrate and use JMX.

    • Target Sitemap, to view the overall topology of the target.

    • Target Information, to view general information about the target.

35.7.3 Refreshing JBoss Partition

Enterprise Manager Cloud Control allows you to refresh the membership of a JBoss Partition so that it can reflect the current deployment state. This helps you add additional JBoss Application Servers to the existing JBoss Partition.

To refresh a JBoss Partition, follow these steps:

  1. From the Targets menu, click Middleware.

  2. On the Middleware page, click the desired JBoss Partition target.

  3. On the JBoss Partition Home page, in the Refresh Partition section, click Refresh Partition.

    Enterprise Manager Cloud Control takes to the Refresh Partition Host Credentials page. For information on this page, click Help on the page. On the Refresh Partition Agent Host Credentials page, provide the credentials of the host where Management Agent, which was used for discovering the existing JBoss Application Server members, is running. On the Refresh Partition Add Members page, select the standalone JBoss Application Servers that should be added to the JBoss Partition.

35.7.4 Viewing JBoss Partition Members

Enterprise Manager Cloud Control helps you view the members of a JBoss Partition. You can see what type of members form the partition, monitor their status, and perform various administrative operations

To view a list of members, follow these steps:

  1. From the Targets menu, click Middleware.

  2. On the Middleware page, click the desired JBoss Partition target.

  3. On the JBoss Partition Home page, from the JBoss Partition menu, select Members, then select Show All to view the following details of the members.

    Column Description
    Name Name of the JBoss Application Server that is part of the JBoss Partition. Click the name to access the home page of that JBoss Application Server.
    Type Type of the member.
    Status Current status of the member. Click the status icon to see a consolidated availability summary. You can see the current and past availability status within the last 24 hours, 7 days, or month (31 days).
    Incidents Number of critical, warning, and error alerts generated for the past 24 hours. Click the alert links to drill down and see more detailed information.

    To search for a particular member, use the Search menu.

    By default, all members of the JBoss Partition are listed in the table. To refresh the table and view only a particular type of members, select either Direct Members or Indirect Members from the View section.

    To capture the membership configuration details in a spreadsheet, click Export.

35.8 Deploying JVM Diagnostics on JBoss Application Server to Diagnose Issues

Oracle Enterprise Manager Cloud Control 12c's JVM Diagnostics enables administrators to diagnose performance problems in a Java application in the production environment. By eliminating the need to reproduce problems, it reduces the time required to resolve these problems. This improves application availability and performance. The correlation between the JBoss target and the JVMD/JVM target enables administrators to navigate to the JVM in context of a JBoss Application Server.

To deploy JBoss on JVMD, complete the following:

  1. From the Setup menu, select Middleware Management, then select Application Performance Management.

  2. On the Application Performance Management page, select JVM Diagnostic Engines, and then click Configure.

  3. From the JVMs and Pools tab, click Downloads.

    Figure 35-3 Download JVM Diagnostics Components

    download
  4. From the Download JVM Diagnostics Components window, select JVMD Agent, then click OK.

  5. From the JVM Diagnostics Agent web.xml Parameters window, select the appropriate JVMD manager from the Available Managers list.

    Figure 35-4 JVM Diagnostics Agent web.xml Parameters

    JVM Diagnostics Agent web.xml Parameters
  6. 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 the JBoss is running).

  7. Copy the script contained at the following location to the same location on the target machine where the jamagent.war. file was copied:

    https://stbeehive.oracle.com/content/dav/st/NonOracle%20MW/Public%20Documents/makeJAMagents.sh
    
  8. 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.

  9. 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.

35.9 Troubleshooting JBoss Application Server Discovery and Monitoring Issues

This section provides troubleshooting tips for the issues encountered while discovering or monitoring JBoss Application Servers.

35.9.1 Troubleshooting Monitoring Issues

  • If the target status is DOWN after discovery, check the Monitoring properties page for the JBoss Application Server and verify the following:

    • Local discovery: only JBoss home is present

    • Remote discovery: only Library path is present

  • If the target status is PENDING (due to a metric collection error) after discovery, ensure that no other application server is being monitored using the same Management Agent (such as Weblogic).

    The following are the various log locations:

    • JBoss server logs: $JBOSS_HOME/server/<config_mode>/log

    • OMS logs: emoms.trc (under $OMS_HOME)

    • Agent logs: $AGENT_STATE_DIR/sysman/log

35.9.2 Troubleshooting Discovery Issues

In the case of JBoss discovery failure, provide the library path along with the install home and try again.

For discovery related issues, manually run the discovery script to check the output, which should look similar to the following:

java -Doracle.home=<AGENT_PLUGIN_LOCATION> \
 -cp \
<AGENT_PLUGIN_LOCATION>/lib/xmlparserv2.jar:\
<AGENT_PLUGIN_LOCATION>/jlib/emConfigInstall.jar:\
<AGENT_PLUGIN_LOCATION>/sysman/jlib/log4j-core.jar:\
<AGENT_PLUGIN_LOCATION>/modules/oracle.http_client 11.1.1.jar:\
<DISCOVERY_PLUGIN_LOCATION>/archives/em-as-thirdparty-discovery.jar \
   oracle.sysman.emas.thirdparty.discovery.jboss.JBossDiscovery \
   <JMX_PORT> <SERVER_HOST> ""

35.9.3 Additional Useful Resources

Useful troubleshooting information can also be found by checking the following:

  • Monitoring Configuration page

  • Targets.xml on the agent

  • OMS and Agent logs

  • Agent metric browser

  • JBoss JMX Console

  • JConsole

  • JBoss server logs