IBM WebSphere Application Server

Application Version and Upgrade Details

Introduction

IBM WebSphere Application Server is a flexible, secure Java server runtime environment for enterprise applications. Deploy and manage applications and services regardless of time, location, or device type. Integrated management and administrative tools provide enhanced security and control, while support for multi-cloud environments allows you to choose your deployment method. Continuous delivery capabilities and services help you respond at the speed your business needs.

In the WebSphere Application Server product, an application server collaborates with a web server to handle requests for web applications. The application server and web server communicate using a WebSphere HTTP plug-in for the web server.

Prerequisites

• OpsRamp Classic Gateway 14.0.0 and above.

• OpsRamp NextGen Gateway 14.0.0 and above.
  Note: OpsRamp recommends using the latest Gateway version for full coverage of recent bug fixes, enhancements, etc.

• For Applications Manager to collect data from WebSphere Application Server, configurations are required at the Performance Monitoring Infrastructure (PMI) specification level.

• Change the Performance Monitor Interface (PMI) Monitoring statistics from “None” to “Extended”. Deploy the perfServletApp.ear file in which is the PMI infrastructure to retrieve the performance information from WebSphere Application Server, and then restart the WebSphere Application Server.

• Enable Performance Monitor Interface (PMI) Monitoring:

  1. Enable Performance Monitoring Infrastructure (PMI) in the application servers you want to monitor.
  2. Go to the IBM WAS Console, then navigate to Servers > All servers.
  3. Click the server name, then “Performance Monitoring Infrastructure (PMI)” under the “Performance” tab.
  4. Select the Enable Performance Monitoring Infrastructure checkbox and then check the Extended button under Currently monitored statistic set.
  5. Click Apply.
  6. Click Save and restart the server.

• To deploy perfServletApp.ear:

  The performance servlet is deployed exactly as any other servlet. Deploy the servlet on a single application server instance within the domain.

  1. Open the IBM WAS Admin console.
  2. Go to Applications on the left-side tree, then navigate to Application Types > WebSphere Enterprise applications.
  3. Click Install.
  4. Select Local File system and then browse the perf servlet application ear file.
  5. Click Next.
  6. The default path is <WAS_INSTALLED_PATH>/<APP_SERVER_NAME>/installableApps/PerfServletApp.ear.
  7. Accept all default options and click Next until finish.
  8. Click Save.
  9. After successful installation, restart the node server once in order to make the perf servlet work correctly.
  10. If global security is enabled in Websphere, make sure that a WebSphere Admin User is added to the monitor group of the perfservletApp.
  11. Navigate to IBM WebSphere Admin console → Applications → Installed Applications → Choose perfservletapp → Security role to user group mapping → Choose Monitor Role → Associate the admin user → Save directly to the master configuration.

  Note: To ensure whether the PMI & perfServletApp are configured properly in WebSphere, invoke the below URL & check whether the data is returned in XML format. http://localhost:<PORT>/wasPerfTool/servlet/perfservlet - 9080 (Default)

  Refer: Retrieving performance data with PerfServlet for more information.

Hierarchy of IBM WebSphere Application resources

For IBM WebSphere Application:

        • IBM WAS Node

                • IBM WAS Server
                        • IBM WAS Application

Supported Metrics

Default Monitoring Configurations

IBM Websphere Application Server has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. Users can customize these default monitoring configurations as per their business use cases by cloning respective global templates and global Device Management Policies. OpsRamp recommends doing this activity before installing the app to avoid noise alerts and data.

1. Default Global Device Management Policies

   OpsRamp has a Global Device Management Policy for each Native Type of IBM Websphere Application Server. You can find those Device Management Policies at Setup > Resources > Device Management Policies, search with suggested names in global scope. Each Device Management Policy follows below naming convention:

   {appName nativeType - version}

   Ex: ibm-websphere IBM WAS Server - 1(i.e, appName = ibm-websphere, nativeType = IBM WAS Server , version = 1)

2. Default Global Templates

   OpsRamp has a Global template for each Native Type of IBM Websphere Application Server. You can find those templates at Setup > Monitoring > Templates, search with suggested names in global scope. Each template follows below naming convention:

   {appName nativeType 'Template' - version}

   Ex: ibm-websphere IBM WAS Server Template- 1(i.e, appName = ibm-websphere, nativeType = IBM WAS Server, version = 1)

3. Default Global Monitors

   OpsRamp has a Global Monitors for each Native Type which has monitoring support. You can find those monitors at Setup > Monitoring > Monitors, search with suggested names in global scope. Each Monitors follows below naming convention:

   {monitorKey appName nativeType - version}

   Ex: IBM WAS Application Monitor ibm-websphere IBM WAS Server 1 (i.e, monitorKey = IBM WAS Application Monitor, appName = ibm-websphere, nativeType =IBM WAS Server,version = 1)

Configure and Install the IBM WAS Integration

1. From All Clients, select a client.
2. Go to Setup > Account.
3. Select the Integrations and Apps tab.
4. The Installed Integrations page, where all the installed applications are displayed.
   Note: If there are no installed applications, it will navigate to the ADD APP page.
5. Click + ADD on the Installed Integrations page. The Available Integrations and Apps page displays all the available applications along with the newly created application with the version.
   Note: You can even search for the application using the search option available. Also you can use the All Categories option to search.

6. Click ADD in the IBM Websphere Application Server application.
   Note: Select the version from the drop down menu.
7. In the Configurations page, click + ADD. The Add Configuration page appears.
8. Enter the below mentioned Basic Information:

Notes:

• By default the Is Secure checkbox is selected.
• Host Name/IP Address and Port should be accessible from Gateway.
• Select the following:
  • App Failure Notifications: if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.

9. Select the below mentioned Custom Attribute:

Note: The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).

10. In the RESOURCE TYPE section, select:

    • ALL: All the existing and future resources will be discovered.
    • SELECT: You can select one or multiple resources to be discovered.

11. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:

    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly

12. Click ADD.

Now the configuration is saved and displayed on the configurations page after you save it.
Note: From the same page, you may Edit and Remove the created configuration.

13. Under the ADVANCED SETTINGS, Select the Bypass Resource Reconciliation option, if you wish to bypass resource reconciliation when encountering the same resources discovered by multiple applications.

    Note: If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries.

14. Click NEXT.

15. (Optional) Click +ADD to create a new collector by providing a name or use the pre-populated name.

16. Select an existing registered profile.

17. Click FINISH.

The application is installed and displayed on the INSTALLED INTEGRATION page. Use the search field to find the installed integration.

Modify the Configuration

• See Modify an Installed Integration or Application article.

  Note: Select the IBM WebSphere Application application.

View the IBM Websphere Application Server Details

1. Navigate to Infrastructure > Search > MIDDLEWARE > IBM Websphere Application Server.
2. The IBM Websphere Application Server page is displayed, select the application name.
3. The RESOURCE DETAILS page appears from the right.
4. Click the ellipsis (…) on the top right and select View details.
5. Navigate to the Attributes tab to view the discovery details.

6. Click the Metrics tab to view the metric details for IBM Websphere Application Server.

Resource Filter Input Keys

IBM Websphere Application Server application Resources are filtered and discovered based on below keys:

Supported Alert Custom Macros

Customize the alert subject and description with below macros then it will generate alert based on customisation

Supported macros keys:

Risks, Limitations & Assumptions

• Application can handle Critical/Recovery failure alert notifications for below two cases when user enables App Failure Notifications in configuration
  • Connectivity Exception
  • Authentication Exception
• Application cannot control monitoring pause/resume actions based on above alerts. Metrics can be used to monitor PowerMax resources and can generate alerts based on the threshold values.
• Component level thresholds can be configured on each resource level.
• No support of showing activity logs.
• The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.
• Application will send any duplicate/repeat failure alert notification for every 6 hours.
• Latest snapshot metric is available from Gateway version 14.0.0.
• This application supports both Classic Gateway and NextGen Gateway.