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

34 Discovering and Monitoring IBM WebSphere Application Servers, Clusters, and Cells

IBM WebSphere Application Server is an application server developed and maintained by IBM Corporation. It offers options for a faster, more flexible Java application server runtime environment with enhanced reliability and resiliency. It supports single server environments and medium-sized configurations, as well as dynamic web applications requiring web tier clustering over multiple application server instances.

IBM WebSphere Application Server Cell is a high-level, logical grouping of IBM WebSphere Application Server Clusters within your enterprise configuration. Each IBM WebSphere Application Server Cluster is a composite target, or in other words, a logical target, comprising one or more individual IBM WebSphere Application Servers.

Enterprise Manager Cloud Control enables you to discover IBM WebSphere Application Servers, IBM WebSphere Application Server Clusters, and IBM WebSphere Application Server Cells in your environment, and add them for central monitoring and management.

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

34.1 About Managing IBM WebSphere Application Servers, Clusters, and Cells

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

  • Discover the following for central monitoring and management:

    • IBM WebSphere Application Servers

    • IBM WebSphere Application Server Clusters

      When you discover an IBM WebSphere Application Server that is part of an IBM WebSphere Application Server Cluster, the IBM WebSphere Application Server Cluster and all other IBM WebSphere Application Servers that are part of that cluster get automatically discovered and added to Enterprise Manager Cloud Control.

    • IBM WebSphere Application Server Cells

      When you discover an IBM WebSphere Application Server that is part of an IBM WebSphere Application Server Cell, the IBM WebSphere Application Server Cell and all other IBM WebSphere Application Server Clusters and IBM WebSphere Application Servers that are part of that cell get automatically discovered and added to Enterprise Manager Cloud Control.

  • Monitor the status, the availability percentage, the CPU usage, the heap usage, and so on.

  • View a summary of incidents and problems occurred for a given interval.

  • Monitor the status and the overall health of the member application servers that are part of IBM WebSphere Application Server Clusters and IBM WebSphere Application Server Cells.

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

  • Monitor the status of deployed applications.

  • Monitor the status of most requested Servlets, EJBs, and JSPs in the last 24 hours.

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

34.2 Supported Versions for Discovery and Monitoring

To search for the IBM WebSphere 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 IBM WebSphere Application Server versions.

    Certified IBM WAS versions

34.3 Prerequisites for Discovering IBM WebSphere Application Servers, Clusters, and Cells

Meet the following prerequisites for discovering IBM WebSphere Application Server, IBM WebSphere Application Server Clusters, and IBM WebSphere Application Server Cells.

  • For IBM WebSphere Application Server Cell-based installation, ensure that the Deployment Manager is running.

  • For standalone IBM WebSphere Application Servers, ensure that the particular Server is running.

  • Ensure that the Oracle Management Agent (Management Agent), which will be used for discovering the IBM WebSphere Application Server (and its associated cluster and cell), is not monitoring any other J2EE application server such as Oracle WebLogic Server, Apache Tomcat, and so on.

    If the Management Agent is monitoring other application servers, and the targets are not required to be monitored using this particular Management Agent, then Oracle recommends that you delete the targets from Enterprise Manager Cloud Control. Alternatively, you can also use a different Management Agent for monitoring them.

  • Ensure that the SOAP connector port of the IBM WebSphere Application Server or the Deployment Manager is open to the Management Agent host.

    To find the SOAP connector prts, perform the following searches:

    • Search for the keyword SOAP_CONNECTOR_ADDRESS in the following location:

      $<WEBSPHERE_HOME>/AppServer/profiles/<PROFILE>/config/cells/<cellname>/nodes/<nodename>/serverindex.xml

    • Search for the keyword SOAP_CONNECTOR_ADDRES in the following location:

      $<WEBSPHERE_HOME>/AppServer/profiles/<PROFILE>/config/cells/<cellname>/nodes/<nodename>/serverindex.xml

  • Ensure that the PMI Service is enabled. To do so, follow these steps:

    • For IBM WebSphere Application Server 5.1.x

      • Log in using the IBM WebSphere Application Server Administrator Console, and select Application Servers.

      • From the list of servers that are a part of the IBM WebSphere Application Server Cell, select the required server.

      • From the Additional Properties menu, select Performance Monitoring Service.

      • Select the check box for Startup, and set the Initial Specification Level to Standard, and click Apply.

      • Once the changes are applied, restart the server.

    • For IBM WebSphere Application Server WebSphere 6.0 and 6.1

      • Log in using the IBM WebSphere Application Server Administrator Console, and select Application Servers.

      • From the Servers menu, select Application Servers.

      • From the list of servers that are a part of the IBM WebSphere Application Server Cell, select the required server.

      • On the Configuration tab, under Performance, select Performance Monitoring Infrastructure (PMI).

      • Enable PMI by select the check box for Enable Performance Monitoring Infrastructure (PMI), and under Currently Monitored Statistic Set, select All.

      • Click Apply, and once the changes are applied, restart the server.

    • For IBM WebSphere Application Server 7.x

      • Log in to the Integrated Solutions Console.

      • From the Monitoring and Tuning menu, select Performance Monitoring Infrastructure (PMI).

      • Select the application server instance.

      • From the Configuration tab, under General Properties, enable PMI by select the check box for Enable Performance Monitoring Infrastructure (PMI).

      • From Currently Monitored Static Set, select Custom. Click the Custom link, and specify the list of metrics that are to be enabled. Click OK.

      • Click Save, and restart the server.

        Note:

        For a clustered configuration, enable PMI for each server individually.
  • Ensure that when Administrative Security is enabled with the absolute path, a Java Trust Keystore is provided during the discovery.

  • For local monitoring, you must have read privileges over the following IBM WebSphere directories and JAR files:

    • For IBM WebSphere 6.0.x

      $<WEBSPHERE_HOME>/lib.

      Many jar files under this directory are required to perform discovery, and these JARs are then made part of the Management Agent class path to enable metric collection.

    • For IBM WebSphere 6.1

      $<WEBSPHERE_HOME>/runtimes/com.ibm.ws.admin.client_6.1.0.jar

      $<WEBSPHERE_HOME>/plugins/com.ibm.ws.runtime_6.1.0.jar

    • For IBM WebSphere 7.0

      $<WEBSPHERE_HOME>/runtimes/com.ibm.ws.admin.client_7.0.0.jar

  • For remote monitoring, you must copy the required WebSphere JARs and the Trusted Keystore file to a folder on the remote Management Agent.

    • For IBM WebSphere 6.0.x, perform the following steps.

      • Create a dummy WebSphere home directory on the remote Agent host; for example /scratch/WebSphere6Jars/AppServer and under it, create the following directory structure:

        WAS_HOME

        /trustedKeyStore

        /lib

        /java

        /java/jre

        /java/jre/lib

        /java/jre/lib/ext

        /java/jre/lib/endorsed

      • Copy the jar files listed below from the WebSphere host to the remote Agent host (in the similar locations of the actual WAS_HOME):

        WAS_HOME/lib

        admin.jar

        bootstrap.jar

        classloader.jar

        emf.jar

        ffdc.jar

        idl.jar

        iwsorb.jar

        j2ee.jar

        mail-impl.jar

        management.jar

        ras.jar

        runtime.jar

        sas.jar

        security.jar

        soap.jar

        utils.jar

        wasjmx.jar

        wasproduct.jar

        wlmclient.jar

        wsexception.jar

        wssec.jar

        WAS_HOME/java/jre/lib

        ibmcertpathprovider.jar

        WAS_HOME/java/jre/lib/ext

        ibmjceprovider.jar

        WAS_HOME/java/jre/lib/endorsed

        Ibmcertpathprovider

      • If Admin Security is enabled:

        Copy the trusted keystore file from its location on the WebSphere host. For example, WAS_HOME/profiles/Dmgr01/etc, to the WAS_HOME/trustedKeyStore directory on the remote Agent host.

    • For IBM WebSphere 6.1

      • Create a dummy WebSphere home directory on the remote Agent host; for example /scratch/WebSphere6Jars/AppServer and under it, create the following directory structure:

        WAS_HOME

        /trustedKeyStore

        /runtimes

        /plugins

        /java/jre/lib/ext

      • Copy the jar files listed below from the WebSphere host to the remote Agent host (in the similar locations of the actual WAS_HOME):

        WAS_HOME/runtimes

        com.ibm.ws.admin.client_6.1.0.jar

        WAS_HOME/plugins

        com.ibm.ws.runtime_6.1.0.jar

    • If Admin Security is enabled:

      Copy the following jar file to WAS_HOME/java/jre/lib/ext directory:

      ibmkeycert.jar

      Copy the trusted keystore file from its location on the WebSphere host, for example, WAS_HOME/profiles/Dmgr01/etc, to the WAS_HOME/trustedKeyStore directory on the remote Management Agent host.

    • For IBM WebSphere versions 6.1.0.13 and 6.1.0.15:

      Copy the following jar file to WAS_HOME/plugins directory

      <WASHOME>/pluginsorg.eclipse.osgi_3.2.1.R32x_v20060919.jar

    • For IBM WebSphere 7.0.x

      • Create a dummy WebSphere home directory on the remote Agent host; for example /scratch/WebSphere7Jars/AppServer and under it, create the following directory structure:

        WAS_HOME

        /trustedKeyStore

        /runtimes

        /plugins

        /java/jre/lib/ext

      • Copy the jar files listed below from the WebSphere host to the remote Agent host (in the similar locations of the actual WAS_HOME):

        WAS_HOME/runtimes

        com.ibm.ws.admin.client_7.0.0.jar

        WAS_HOME/java/jre/lib/ext

        ibmkeycert.jar

        WAS_HOME/java/jre/lib

        ibmjgssprovider.jar

      • If Admin Security is enabled:

        Copy the trusted keystore file from its location on the WebSphere host, for example, WAS_HOME/profiles/Dmgr01/etc, to the WAS_HOME/trustedKeyStore directory on the remote Management Agent host.

    • For IBM WebSphere 8.0.x

      • Create a dummy WebSphere home directory on the remote Agent host; for example /scratch/WebSphere8Jars/AppServer and under it, create the following directory structure:

        WAS_HOME

        /trustedKeyStore

        /runtimes

        /plugins

        /java/jre/lib/ext

      • Copy the jar files listed below from the WebSphere host to the remote Agent host (in the similar locations of the actual WAS_HOME):

        WAS_HOME

        /runtimes

        com.ibm.ws.admin.client_8.0.0.jar

        WAS_HOME/java/jre/lib/ext

        ibmkeycert.jar

        WAS_HOME/java/jre/lib

        ibmjgssprovider.jar

        ibmorb.jar

      • If Admin Security is enabled:

        Copy the trusted keystore file from its location on the WebSphere host, for example, WAS_HOME/profiles/Dmgr01/etc, to the WAS_HOME/trustedKeyStore directory on the remote Management Agent host.

34.4 Discovering IBM WebSphere Application Servers, Clusters, and Cells

Enterprise Manager Cloud Control enables you to discover and add IBM WebSphere Application Servers (and their associated clusters and cells) for central monitoring and management.

To add an IBM WebSphere Application Server (and their associated clusters and cells), follow these steps:

  1. Meet the prerequisites. More

  2. From the Targets menu, select Middleware.

  3. On the Middleware page, from the Add menu, select IBM WebSphere Application Server.

  4. Click Go.

    Enterprise Manager Cloud Control displays the IBM WebSphere Application Server Discovery Wizard.

  5. On the Host page, enter the details of the host on which the IBM WebSphere Application Server and Oracle Management Agent are running. In case of IBM WebSphere Application Server Cell-based installation, enter the details of the Deployment Manager so that all IBM WebSphere Application Servers present under the cell are automatically discovered.

    Figure 34-1 IBM WebSphere Application Server Host Page

    IBM WAS Server Host Page
    Link Description
    WebSphere Application Server Host Enter the name of the host on which the IBM WebSphere Application Server or the IBM WebSphere Deployment Manager is installed.
    SOAP Connector Port Enter the SOAP connector port on which the IBM WebSphere Application Server or the IBM WebSphere Deployment Manager is listening.
    Version Select the version of the IBM WebSphere Application Server.
    User Name Enter the user name to access the IBM WebSphere Application Server or the IBM WebSphere Deployment Manager.
    Password Enter the password to access the IBM WebSphere Application Server or the IBM WebSphere Deployment Manager.
    Trusted Keystore Filename If the port is SSL enabled, then enter the absolute path to the trusted keystore file. Keystore is a protected database that holds keys and certificates for an enterprise. Ensure that the path leads up to the file name.

    For example, /net/host1/software/IBM/WebSphere/AppServer/profiles/Dmgr01/etc/DummyClientTrustFile.jks

    Server Home Directory Enter the absolute path to the Oracle home directory where the IBM WebSphere Application Server or the IBM WebSphere Deployment Manager is installed.

    For example,

    /net/host1/software/IBM/WebSphere/AppServer/

    Agent Click the search icon and select the Oracle Management Agent (Management Agent) that is monitoring the IBM WebSphere Application Server or the IBM WebSphere Deployment Manager. The Management Agent can be local or remote to the IBM WebSphere Application Server or the IBM WebSphere Deployment Manager.

  6. On the Select Servers page, select the IBM WebSphere Application Servers and/or the IBM WebSphere Application Server Clusters that you want to monitor in Enterprise Manager Cloud Control.

    On selection of an IBM WebSphere Application Server Cluster, all the IBM WebSphere Application Servers that are part of the cluster are automatically selected and added to Enterprise Manager Cloud Control for monitoring.

  7. On the Review page, review the information you have provided in the previous screens for discovering IBM WebSphere Application Servers and IBM WebSphere Application Server Cells.

    If you want to modify any information, click Back repeatedly to reach the page where you want to make some changes. If you are satisfied with the information, click Submit.

34.5 Monitoring IBM WebSphere Application Servers

This section covers the following:

34.5.1 Monitoring IBM WebSphere Application Servers

To monitor IBM WebSphere Application Servers, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired IBM WebSphere Application Server.

  3. On the IBM WebSphere Application Server Home page, you can monitor the availability, usage, and performance of the selected server at a high level.

    IBM WAS Home Page

The IBM WebSphere Application Server Home page has the following sections:

General Section

Provides general information about the health of the server.

Element Description
Up/Down/Pending Since Date and time when the status was last determined.
Availability (%) Percentage of time that the server was up during the last 24 hours. Click the percentage link to view availability details for the past 24 hours.
Version Version of the server that is being monitored.
State Current state of the server, whether it is running or shut down.
CPU Usage (%) CPU consumption as a percentage of CPU time at any given moment in time. Click the percentage link to view availability details for the past 24 hours
Heap Usage (MB) Current JVM Memory heap Usage in MB as per the last Metric collection

Monitoring and Diagnostics Section

Provides a summary of incidents and configuration changes made to the server. Use this information to diagnose and troubleshoot performance issues with the server.

Element Description
Incidents Number of unresolved issues that require your attention and corrective action. Click the value to drill down and view more detailed information.
Configuration Changes Number of incidents related to the applications. The displayed integer is also a link to the Incident Manager page. Click the value to drill down and view more detailed information.

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 server names in the legend and select an appropriate option in the Additional Information message.

Applications Tab

Provides critical information about the applications deployed to the server. For more details, see Section 34.5.4.

Servlets and JSPs Tab

Provides details of the most requested Servlets and JSPs in the last 24 hours.

EJBs Tab

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

34.5.2 Administering IBM WebSphere Application Servers

To administer IBM WebSphere Application Servers, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired IBM WebSphere Application Server.

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

    To perform administrative tasks on the IBM WebSphere Application Server, from the WebSphere Application 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.

    • Administer, to directly administer the IBM WebSphere Application Server using the IBM WebSphere Application Server Console.

    • 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 view the properties of the target.

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

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

34.5.3 Monitoring the Performance of IBM WebSphere Application Servers

Enterprise Manager Cloud Control provides several key performance charts that can help you quickly assess the health of your IBM WebSphere Application Server.

To check the performance of an IBM WebSphere Application Server, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired IBM WebSphere Application Server.

  3. On the IBM WebSphere Application Server Home page, from the WebSphere Application 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.

34.5.4 Monitoring the Applications Deployed to IBM WebSphere Application Servers

To monitor the applications running on a IBM WebSphere Application Server, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired IBM WebSphere Application Server.

  3. On the IBM WebSphere Application Server Home page, in the Deployments section, in the Applications region, view the following details about applications deployed to the server.

    Column Description
    Name Name of the application deployed to the server.
    Status Status of the application, either Up or Down.
    Number of Requests Processed Total number of requests processed by the application in the last 24 hours.
    Average Request Processing Time Average time taken to service the requests.
    Average Request Processing Time by EJB Method Average time taken by the EJB methods to service the requests.

34.5.5 Viewing the Top EJBs of IBM WebSphere Application Servers

To view the top or the most requested EJBs of an IBM WebSphere Application Server, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired IBM WebSphere Application Server.

  3. On the IBM WebSphere Application Server Home page, in the EJBs section, view a list of EJBs that were most requested in the last 24 hours.

34.5.6 Viewing the Top Servlets and JSPs of IBM WebSphere Application Servers

To view the top or the most requested Servlets and JSPs of an IBM WebSphere Application Server, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired IBM WebSphere Application Server.

  3. On the IBM WebSphere Application Server Home page, in the Servlets and JSPs section, view a list of Servlets and JSPs that were most requested in the last 24 hours.

34.5.7 Viewing IBM WebSphere Application Server Metrics

To view all IBM WebSphere Application Server metrics, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired IBM WebSphere Application Server.

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

34.6 Monitoring IBM WebSphere Application Server Clusters

This section covers the following:

34.6.1 Monitoring IBM WebSphere Application Server Clusters

To monitor IBM WebSphere Application Server Clusters, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired IBM WebSphere Application Server Cluster.

  3. On the IBM WebSphere Application Server Cluster Home page, you can monitor the availability, usage, and performance of the selected cluster at a high level.

    The status of an IBM WebSphere Application Server Cluster depends on the status of all its members, that is the individual IBM WebSphere Application Servers within the cluster. IBM WebSphere Application Server is an application server developed and maintained by IBM Corporation.

The IBM WebSphere Application Server Cluster Home page has the following sections:

Summary Section

Provides a quick, high-level, graphical summary of the availability of the cluster in the last 24 hours.

To view the status (either up or down), hover your mouse over the timeline bar. To zoom in and review the hours of a particular time period, place the cursor at one particular hour of the timeline bar, and with the mouse key pressed, drag the cursor to another hour of interest. You will see that the timeline bar zooms in and displays the hours, minutes, and seconds within that particular time period. This helps when you want to identify the exact time when the cluster went down.

Monitoring and Diagnostics Section

Provides a summary of incidents, descendant target incidents, and configuration changes made to the server. Use this information to diagnose and troubleshoot performance issues with the server.

Element Description
Incidents Number of unresolved issues that require your attention and corrective action. Click the value to drill down and view more detailed information.
Descendant Target Incidents Number of changes made to the server configuration in the last 7 days. Click the value to drill down and view more detailed information.
Configuration Changes Number of incidents related to the applications. The displayed integer is also a link to the Incident Manager page. Click the value to drill down and view more detailed information.

Servers Section

Provides information about the members of the cluster, mainly the IBM WebSphere Application Servers that are part of the cluster.

Column Description
Name Name of the IBM WebSphere Application Server that is part of the cluster. To navigate to the home page of the server, click the member or server name.
Status Current status of the IBM WebSphere Application Server. To drill down to the Status History page, click the status icon. You will be taken to the Status History (Availability) page, which shows the availability of the server along with the availability history of the constituents that are used to compute its availability.
Active Sessions Total number of active or live HTTP sessions in the server over 24 hours. The value appears as a link. To view the number of active sessions for each hour of the 24-hour scale, click the value (link). A graph appears depicting the active sessions for each hour. To drill down further and view more detailed metric-related information, click Metric Details.
Request Processing Time (ms) Average time taken (in milliseconds) to service a request in the last 24 hours.

Resource Usage Section

Provides a graphical representation of the CPU utilization rate and the memory used by JVM 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 server names in the legend and select an appropriate option in the Additional Information message.

34.6.2 Administering IBM WebSphere Application Server Clusters

To administer IBM WebSphere Application Server Clusters, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired IBM WebSphere Application Server Cluster.

  3. On the IBM WebSphere Application Server Cluster Home page, you can view high-level information pertaining to the selected server.

    To perform administrative tasks on the IBM WebSphere Application Server Cluster, from the WebSphere Cluster 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 and monitor the health of the members of the IBM WebSphere Application Server Cluster. The members are typically the IBM WebSphere Application Servers that are part of the cluster.

    • 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 view the properties of the target.

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

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

34.6.3 Viewing IBM WebSphere Application Server Cluster Members

Enterprise Manager Cloud Control helps you view the members of an IBM WebSphere Application Server Cluster. You can see what type of members form the cluster, monitor their status, and perform various administrative operations.

To view the members of an IBM WebSphere Application Server Cluster, follow these steps:

  1. From the Targets menu, click Middleware.

  2. On the Middleware page, click the desired IBM WebSphere Application Server Cluster.

  3. On the IBM WebSphere Application Server Cluster Home page, from the WebSphere Cluster menu, select Members, then select Show All to view the following details of the members.

    Column Description
    Name Name of the IBM WebSphere Application Server that is part of the IBM WebSphere Application Server Cluster. Click the name to access the home page of that IBM WebSphere Application Server.
    Type Type of the member. Typically, IBM WebSphere Application Server.
    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 fatal, critical, and warning incidents that occurred for the member server. To drill down to the Incident Manager page and view more detailed information about the incident, click the count.

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

    By default, all members of the IBM WebSphere Application Server Cluster 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 save the information about members in a file and to download that file to your local disk, click Export.

34.6.4 Viewing IBM WebSphere Application Server Cluster Metrics

To view all IBM WebSphere Application Server metrics, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired IBM WebSphere Application Server Cluster.

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

34.7 Monitoring IBM WebSphere Application Server Cells

This section covers the following:

34.7.1 Monitoring IBM WebSphere Application Server Cells

To monitor IBM WebSphere Application Server Cells, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired IBM WebSphere Application Server Cell.

  3. On the IBM WebSphere Application Server Cell Home page, you can monitor the availability, usage, and performance of the selected cell at a high level.

    The status of an IBM WebSphere Application Server Cell depends on the status o f all its members, that is the individual IBM WebSphere Application Server Clusters within the cell. The status of each IBM WebSphere Application Server Cluster depends on the status of each IBM WebSphere Application Server within that cluster.

The IBM WebSphere Application Server Cell Home page has the following sections:

General Section

Column Description
WebSphere Cell Name of the IBM WebSphere Application Server Cell.
Deployment Manager Name of the Deployment Manager that manages the operations of the IBM WebSphere Application Server Cell being monitored.
Deployment Manager Host Name of the host where the Deployment Manager is running.
Deployment Manager SOAP Connector Port SOAP connector port number used to connect to the Deployment Manager.
WebSphere Cell Refreshed Date and time when the membership of the IBM WebSphere Application Server Cell was last refreshed.

Incidents Summary Section

Provides a summary of the fatal, critical, warning, and escalated incidents and problems that occurred on the IBM WebSphere Application Server Cell.

To filter and view a particular category of incidents and problems, from the Category list, select a particular category. The table automatically refreshes and lists the incidents and problems pertaining to the selected category.

To hide, unhide, and reorder columns, and to filter and view either all incidents, all incidents without symptoms, or only causes, from the View menu, select an appropriate option.

Column Description
Summary Intuitive message indicating what the incident is about.
Target Target type on which the incident or problem occurred.
Severity Severity of the incident or problem. The severity is either Fatal, Critical, or Warning.
Status Status of the incident or problem. The status can be either New, Work in Progress, Closed, or Resolved.
Escalation Level Escalation level signifying the level of attention required on the incident. The escalation level can be either None, which means it is not escalated, or Level 1 through Level 5.
Type Type of incident or problem being reported.
Time Since Last Update Date and time the incident was last updated or when the incident was closed.

Clusters Section

Provides availability information about the IBM WebSphere Application Server Cluster member targets that are part of the IBM WebSphere Application Server Cell.

Column Description
Name Name of the IBM WebSphere Application Server Cluster member target that is part of the IBM WebSphere Application Server Cell. The navigate to the home page of the cluster, click the cluster name.
Status Current status of the IBM WebSphere Application Server Cluster member target.
Number of Servers Number of IBM WebSphere Application Servers that are part of the IBM WebSphere Application Server Cluster.

Servers Section

Provides availability information about the IBM WebSphere Application Server member targets that are part of the IBM WebSphere Application Server Cell.

Column Description
Name Name of the IBM WebSphere Application Server member target that is part of the IBM WebSphere Application Server Cell. To navigate to the home page of a member target, click the member name.
Status Current status of the IBM WebSphere Application Server member target.
Cluster Name of the IBM WebSphere Application Server Cluster to which the IBM WebSphere Application Server member target belongs. This column applies only to server targets that are part of a cluster target.

34.7.2 Administering IBM WebSphere Application Server Cells

To administer IBM WebSphere Application Server Cells, follow these steps:

  1. From the Targets menu, select Middleware.

  2. On the Middleware page, click the desired IBM WebSphere Application Server Cell.

  3. On the IBM WebSphere Application Server Cell Home page, you can view high-level information pertaining to the selected cell.

    To perform administrative tasks on the IBM WebSphere Application Server Cell, from the WebSphere Cell 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 and monitor the health of the members of the IBM WebSphere Application Server Cell. The members are typically IBM WebSphere Application Cells, IBM WebSphere Application Server Clusters, and IBM WebSphere Application Servers that are part of the cell.

    • 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 view the properties of the target.

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

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

34.7.3 Viewing IBM WebSphere Application Server Cell Members

Enterprise Manager Cloud Control helps you view the members of an IBM WebSphere Application Server Cell. You can see what type of members form the cell, monitor their status, and perform various administrative operations.

To view the members of an IBM WebSphere Application Server Cell, follow these steps:

  1. From the Targets menu, click Middleware.

  2. On the Middleware page, click the desired IBM WebSphere Application Server Cell.

  3. On the IBM WebSphere Application Server Cell Home page, from the WebSphere Cell menu, select Members, then select Show All to view the following details of the members.

    Column Description
    Name Name of the IBM WebSphere Application Server Cluster or the IBM WebSphere Application Server that is part of the IBM WebSphere Application Server Cell. To navigate to the home page of a member, click the member name.
    Type Type of the member. Typically, IBM WebSphere Application Server Cluster or IBM WebSphere Application Server.
    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 fatal, critical, and warning incidents that occurred for the member server. To drill down to the Incident Manager page and view more detailed information about the incident, click the count.

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

    By default, all members of the IBM WebSphere Application Server Cell 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 save the information about members in a file and to download that file to your local disk, click Export.

34.8 Troubleshooting IBM WebSphere Application Server Discovery and Monitoring Issues

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

34.8.1 Troubleshooting Discovery Issues

  1. Problem Description

    The discovery of a target IBM WebSphere fails at the Host Credentials phase. The discovery of IBM WebSphere fails when you click next after having entered valid target properties for discovery with the following error message.

    Could not find the required library, specify the home directory.

    This message is expected at this step as the Agent does not know the WAS_HOME directory. However when you enter the WAS_HOME directory, you still get the same error.

    Root Cause

    This issue is a known issue.

    Action

    Apply the following workaround.

    1. Create a directory without any space in it and copy the jar files required for discovery in this directory as mentioned in Section 34.3. Remember to create these directories logged as the OS user you defined in the Agent Host Preferred Credentials.

    2. Check the box "Agent is running on a host other than the Deployment Manager" as if it was remote monitoring and provide the correct path to the jar files.

  2. Problem Description

    The IBM WebSphere Application Server still reports Metric Collection errors even after the Agent has been stopped and re-started.

    Root Cause

    The PMI Service for IBM WebSphere Application Server has not been enabled or the same agent is used to monitor other application servers like WebLogic or tomcat.

    Action

    Enable the PMI Service for the WebSphere server that is being Monitored.

    Make sure the same agent is not already in use to monitor other application servers like WebLogic or tomcat. Use a different agent or install a new agent to monitor WebSphere server.

  3. Problem Description

    In the server home page, select the Applications tab from the IBM WebSphere Application Server Home Page then Applications, you do not see any application listed.

    Also, in the all metrics page when you click on a particular metric, you see no data instead of some values.

    Root Cause

    If you don't see any data in the applications tab or in any particular metric, it just means that there is no load on the Deployed Applications. But, if the load is there and still the data is not seen, the required resources are not created on the server.

    Action

    None except if there is load on Deployed Applications.

    Else enable the option "Create MBeans for Resources" for the application in question from the IBM WebSphere Console.

  4. Problem Description

    The discovery of IBM WebSphere Application server (as well as other Third Party Application Servers) passes successfully all discovery phases.

    It fails only when the button "Finish" is pressed and the following error is displayed:

    Discovery failed unknown error.

    You may be redirected automatically to the first step of the Discovery Wizard.

    Root Cause

    You were not logged in Cloud Control as a Super User. As stated in the Pre-Requisites, you must be logged with a Super User account (like SYSMAN) in order to successfully discover a target IBM WebSphere Application Server (Cell or Standalone).

    Action

    Logout of Cloud Control and Login with a Super User account.

  5. Problem Description

    The discovery of IBM WebSphere Application Server or Application Server Cell fails with the following message displayed:

    Error:

    No application servers were found on the host <host>. If the port is SSL enabled, specify the port number and the Trusted Keystore file name.

    The OMS trace file $ORACLE_HOME/sysman/log/emoms.trc includes:

    Caused by: com.ibm.websphere.management.exception.ConnectorNotAvailableException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: No trusted certificate found; targetException=java.lang.IllegalArgumentException: Error opening socket: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: No trusted certificate found]

    at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:344)

    at com.ibm.ws.management.connector.soap.SOAPConnectorClient.<init>(SOAPConnectorClient.java:177)

    ... 6 more

    Caused by: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: No trusted certificate found; targetException=java.lang.IllegalArgumentException: Error opening socket: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: No trusted certificate found]

    Potential Cause

    The SOAP port provided for the discovery process could be incorrect.

    Action

    Find the correct SOAP port for the node or cell that needs to be discovered.

    <WAS_HOME>/profiles/<PROFILE>/config/cells/<CELL_NAME>/nodes/<NODE_NAME>/serverindex.xml

    The SOAP port is defined within the following XML tags:

    <specialEndpoints xmi:id="NamedEndPoint_4" endPointName="SOAP_CONNECTOR_ADDRESS">

    <endPoint xmi:id="EndPoint_4" host="celtpvm4.us.oracle.com" port="8879"/>

    </specialEndpoints>

    In this example the node or cell SOAP port is 8879.

    This is the value that should be used for 'SOAP connector port' in the discovery form.

  6. Problem Description

    After having discovered the WebSphere instance, the following metric collection error is returned:

    oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.lang.NoClassDefFoundError:

    Could not initialize class com.ibm.websphere.management.AdminClientFactory

    Root Cause

    Caused by an incorrect class path used during discovery

    Action

    From the Targets tab, select Middleware, and then select IBM WebSphere Server Target.

    From the Target Setup menu, select Monitoring Configuration, and enter the correct WebSphere Home path, and click OK.

  7. Problem Description

    The discovery of IBM WebSphere Application Server or Application Server Cell fails with unknown error.

    After following the above trouble shooting sections if the discovery issue is still not resolved, we recommend to run the discovery from UI with the following property set on the agent.

    Potential Cause

    There could be various causes for the discovery failure; looking at the log file - emagent_perl.trc with the following property set, will help to identify the root cause for the discovery failure.

    Action

    1. Add the following property in the file $AGENT_INSTALL_HOME/sysman/config/emd.properties:

      EMAGENT_PERL_TRACE_LEVEL=DEBUG

    2. Perform the discovery from the UI.

    3. Look at the log file $AGENT_INSTALL_HOME/sysman/log/emagent_perl.trc.

      for the xml output beginning with the tag

      <Targets>

      ……

      </Targets>

      The error message encoded in the xml output will help identify the root cause of the discovery.

34.8.2 Troubleshooting Monitoring Issues

The names of the IBM WebSphere Application Servers discovered in Enterprise Manager Cloud Control 12c Release 2 (12.1.0.2) or lower, appear only with the server name. For example, testserver_1_1. However, the names of the IBM WebSphere Application Servers discovered in Enterprise Manager Cloud Control 12c Release 3 (12.1.0.3) or higher, appear with the node name and server name. For example, exampleNode01.testserver_1_2. See Figure 34-2.

Figure 34-2 Issue with the Display Name of IBM WebSphere Application Server

Issue with Display Name