Skip Headers
Oracle® Enterprise Manager Cloud Control Getting Started with Oracle Fusion Middleware Management Plug-in
Release 12.1.0.5

E24215-09
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

29 Discovering and Monitoring IBM WebSphere Application Server

IBM WebSphere Application Server (IBM WAS) is one of the non-Oracle application servers that is monitored using Oracle Enterprise Manager Cloud Control. IBM WAS is a software framework and middleware, hosting Java based web applications.

IBM WAS supports single server environments, and medium-sized configurations. IBM WAS also supports dynamic web applications that require web tier clustering over multiple application server instances.

The following sections are covered in this chapter.

29.1 Supported Versions

The supported IBM WebSphere Application Server versions that can be monitored in various, supported Enterprise Manager releases are as follows:

  • 6.0.x

  • 6.1.x

  • 7.0.x

  • 8.0.x

29.2 Prerequisites for Discovering IBM WebSphere Application Server

Perform the following steps to ensure all the prerequisites to discover IBM WAS are met.

  • Ensure that the Deployment Manager for an Application Server Cell is running in order to discover the Application Server Cell.

  • To discover a Standalone Application Server, ensure that the particular Server is running.

  • Ensure that the Management Agent that will be used for discovering IBM WAS is not monitoring any other J2EE Application server like WebLogic and tomcat.

    If the agent is monitoring other application servers, and the targets are not required to be monitored using this particular Management Agent, delete the targets. Alternatively, you can also use a different Management Agent for monitoring

  • Ensure that The SOAP Connector Port of the Deployment Manager or the Standalone Application Server is open to the Management Agent Host.

    To find the SOAP Ports, 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 WebSphere 5.1.x

      • Login using the IBM WAS Administrator Console, and select Application Servers.

      • From the list of servers that are a part of the IBM WAS 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 WebSphere 6.0 and WebSphere 6.1

      • Login using the IBM WAS 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 WAS 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 WebSphere 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 Key Store is provided during the discovery.

  • For Local Monitoring, user should have read privileges over the following IBM WebSphere directories and jar files

    • For IBM WebSphere 6.0.x

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

    • For IBM WebSphere 6.1

      WAS_HOME/runtimes/com.ibm.ws.admin.client_6.1.0.jar

      WAS_HOME/plugins/com.ibm.ws.runtime_6.1.0.jar

    • For IBM WebSphere 7.0

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

29.3 Discovering IBM WebSphere Application Server

A typical IBM WebSphere server installation will lead to one of the following setups:

  • IBM WebSphere standalone application server

  • IBM WebSphere Cell based Network deployment

To discover IBM WAS, perform the steps of one of the following methods based on the IBM setup to be discovered:

29.3.1 Adding IBM WAS Cell

To add an IBM WAS Cell, follow these steps.

  1. On Enterprise Manager Cloud Control, from the Targets menu, select Middleware.

  2. From the Middleware home page, select Add, and then select IBM WebSphere Application Server Cell.

  3. On the Add IBM WebSphere Application Server Cell: Host page, enter the credentials, as displayed in Figure 29-1, and click Next.

  4. On the Add IBM WebSphere Application Server Cell: Select Servers page, select the preferred servers, as displayed in Figure 29-2, and click Next.

  5. Review the details on the Add IBM WebSphere Application Server Cell: Review page, as displayed in Figure 29-3, and click Finish.

Figure 29-1 Add IBM WebSphere Application Server Cell: Host Page

Description of Figure 29-1 follows
Description of "Figure 29-1 Add IBM WebSphere Application Server Cell: Host Page"

Figure 29-2 Add IBM WebSphere Application Server Cell: Select Servers Page

Description of Figure 29-2 follows
Description of "Figure 29-2 Add IBM WebSphere Application Server Cell: Select Servers Page"

Figure 29-3 Add IBM WebSphere Application Server Cell: Review Page

Description of Figure 29-3 follows
Description of "Figure 29-3 Add IBM WebSphere Application Server Cell: Review Page"

29.3.2 Adding IBM WAS Standalone Server

To add IBM WAS Standalone Server, follow these steps.

  1. On Enterprise Manager Cloud Control, from the Targets menu, select Middleware.

  2. On the Middleware home page, select Add, and then select IBM WebSphere Application Server.

  3. On the Add IBM WebSphere Application Server: Host page, enter the credentials, as displayed in Figure 29-4, and click Next.

  4. On the Add IBM WebSphere Application Server: Select Servers page, select the preferred servers, as displayed in Figure 29-5, and click Next.

  5. Review the details on the Add IBM WebSphere Application Server: Review page, as displayed in Figure 29-6, and click Finish.

Figure 29-4 Add IBM WebSphere Application Server: Host Page

Description of Figure 29-4 follows
Description of "Figure 29-4 Add IBM WebSphere Application Server: Host Page"

Figure 29-5 Add IBM WebSphere Application Server: Select Servers Page

Description of Figure 29-5 follows
Description of "Figure 29-5 Add IBM WebSphere Application Server: Select Servers Page"

Figure 29-6 Add IBM WebSphere Application Server: Review Page

Description of Figure 29-6 follows
Description of "Figure 29-6 Add IBM WebSphere Application Server: Review Page"

29.4 Monitoring IBM WebSphere Application Server

You can use the following pages to monitor IBM WAS.

  1. IBM Application Server Cell Home Page: you can use this page to monitor the description of the members and the consolidated status and alerts of the members.

    Description of app_cell_home_page.gif follows
    Description of the illustration app_cell_home_page.gif

  2. IBM Application Server Home Page: you can use this page to view the current status of the target. If the Response and Load section has no data displayed, the next scheduled upload with display the information. Description of app_server_home_page.gif follows
    Description of the illustration app_server_home_page.gif

    For more information on the frequency at which the metrics are evaluated, use the All Metrics page.

  3. IBM WebSphere Application Server Performance Page: you can use this page to view the information on Memory, Resource, Heap and JDBC usage. Description of app_server_performance_page.gif follows
    Description of the illustration app_server_performance_page.gif

  4. IBM WebSphere Application Server All Metrics Page: you can view the list of all metrics, and the collection interval and last upload for each metric. Description of ibm_was_all_metrics.gif follows
    Description of the illustration ibm_was_all_metrics.gif

  5. IBM WebSphere Performance Summary Page: you can monitor the overall performance of IBM WAS Metrics using this page.

    You can use the IBM WebSphere Metric Performance Summary page to do the following:

    • Monitor the Metric performance for preferred metrics

      Using the Performance Summary page, you can monitor the overall performance of the IBM WAS metrics.

      Description of ibm_was_perf_summary.gif follows
      Description of the illustration ibm_was_perf_summary.gif

    • Select a preferred chart set

      From the Chart Set list, select the preferred chart set.

    • Update an existing chart set

      You can customize a chart set according to your requirements, and save changes by clicking Save Charts. You can create a new chart set by using the Save Charts option.

    • Change time frames

      You can use the slider to set the time frame manually, or you can select from the default values provided.

    • Show/Hide the Metrics Palette

      Description of ibm_was_perf_summary1.gif follows
      Description of the illustration ibm_was_perf_summary1.gif

    • Delete metric performance charts

      You can delete metric performance charts either by clicking the close button on the chart itself, or by deselecting the metric name on the Metric Palette.

    • Create new metric performance charts

      You can create new metric performance charts by selecting the preferred metrics. The charts are automatically created once the metrics are selected from the Metric Palette.

    • Drag and drop metrics

      You can drag and drop the metrics from a particular metric group to the same chart.

    • View individual metrics on a chart

      When you hover the cursor over a particular metric on the chart, the other metrics are greyed out.

29.5 Troubleshooting

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