websphere AC Configuration

The following diagram outlines the process to configure the probe.
uimpga-ga
websphere_AC
This article describes the configuration concepts and procedures to set up the WebSphere Monitoring (websphere) probe. The probe is configured to monitor entities such as Java Virtual Machine, Enterprise Java Beans, Servlets, and Java Server Pages. You can create profiles and configure monitors to generate QoS and alarms once the probe establishes a connection with the IBM WebSphere Application Server (WAS).
The following diagram outlines the process to configure the probe.
configuring websphere on AC
configuring websphere on AC
 
Contents
 
 
 
2
 
 
Verify Prerequisites
Verify that required hardware and software is available, and other prerequisites are met before you configure the probe. For more information, see websphere (Websphere Monitoring) Release Notes.
Configure General Properties
You can configure the general properties to set up the probe environment for monitoring. You can also configure the log properties to define the amount of log information to maintain.
 
Follow these steps:
 
  1. Click the 
    websphere
     node.
    The 
    Probe Information 
    section provides information about the probe name, probe version, start time of the probe, and the probe vendor.  
  2. Specify the following information under 
    WebSphere Environment
    , as required:
    •  
      Version
      : specifies the WAS version to be monitored.
    •  
      Libraries
      : defines the WebSphere libraries path.
    •  
      Java Home
      : defines the Java runtime environment path.
  3. Click 
    Actions
    Test Environment
     to validate the specified paths.
    If either of the paths are incorrect, a validation error appears. The probe also stops working when you save the configuration with incorrect paths.
  4. Specify the following information under 
    General Configuration
    , as required:
    •  
      Log Level
      : specifies the level of information that is written in the log file.
      Default: 0 - Fatal
      Log as little as possible during normal operation to minimize disk consumption, and increase the amount of detail when debugging.
    •  
      Log Size
      : specifies the maximum size of the probe log file in kilobytes.
      Default: 100 
    •  
      Client Trust Password
      : defines the trust password to read client security files.
    •  
      Client Key Password
      : defines the key password to read client security files.
       The client trust and key passwords are required only if your client security files on the WAS are password-protected.
  5. Click 
    Save
    .
Add a Resource
A resource is a monitored WAS instance, and is identified with either the host name or the IP address. You can also add a cluster of the WAS as a resource to monitor. 
 
Follow these steps:
 
  1. Click the 
    (Options)  icon
     next to the 
    websphere 
    node.
  2. Select 
    Add New Resource
    .
    The 
    Add New Resource
     dialog appears.
  3. Specify the following information of the monitored WAS:
    •  
      Resource Name
      : defines a unique name for the monitored resource.
    •  
      Hostname or IP Address
      : specifies the host name or the IP address of the server.
    •  
      Port
      : specifies the port number that the probe uses to connect to the server.
      Default: 8880
       Specify 8879 for clustered environments.
    •  
      Username
      : specifies the username with administrative privileges to connect to the server.
    •  
      Password
      : specifies the password of the defined 
      Username
      .
    •  
      SSL
      : allows the probe to use HTTPS to connect to the server.
      Default: Selected
    : Connection to the WAS retrieves data only when you provide correct login credentials.
  4. Click 
    Submit
     to create the resource and reload the configuration.
    The profile is created as a 
    Profile -
     
     
    Resource 
     
     node under the 
    websphere 
    node.
     The host name is displayed when you add a resource using the host name. Similarly, the IP address is displayed when you add a resource using the IP address.
     
  5. Navigate to the 
    Websphere
     node of your 
    resource name
     node.
  6. Specify or modify the following information under 
    Host Configuration
    , as required:
    •  
      Active
      : activates the resource for monitoring, on creation.
      Default: Selected
    •  
      Resource Name
      : defines the unique name of the monitored resource. This field is read-only.
    •  
      Hostname or IP Address
      : specifies the hostname or IP address of the monitored server.
    •  
      Port
      : specifies the port number that the probe uses to connect to the server. 
    •  
      Check Interval
      : specifies the interval after which the probe again retrieves the data from the server.
      Default: 5
      Reduce this interval to generate alarms and QoS frequently. A shorter interval can also increase the system load.
    •  
      Check Interval Unit
      : specifies the unit of the 
      Check Interval
      .
      Default: minutes
    •  
      Alarm Message
      : specifies the message that is generated when the probe is unable to connect to the server.
      Default: Resource Critical 
    •  
      Username
      : specifies the username with administrative privileges to connect to the server.
    •  
      Password
      : specifies the password of the defined 
      Username
      .
    •  
      Activate Statistic Set Automatically on PMI
      : sets the Performance Monitoring Infrastructure (PMI) to a level so that the probe can access all the monitors. By default, the PMI level that the WebSphere server administrator defines might deny the probe access to some monitors.
      Default: Not Selected
      CA recommends that you ensure that PMI level settings do not affect the WebSphere server performance. Check with the WebSphere system administrator first.
    •  
      Advanced Alarming
      : specifies the minimum number of profiles when the same monitor exceeds the defined alarm threshold before an alarm is sent.
      Default: 1
      • The probe generates only one alarm when the same monitor exceeds threshold for the configured minimum number of profiles.
      • A monitor does not send any alarm if the monitor does not exceed threshold for the configured minimum number of profiles.
      • If 
        Alarm Always 
        option
         
        is enabled for a monitor, this parameter is overridden and alarm is always sent if the threshold is breached.
      • If the value is configured as 
        1
        , individual alarms from all the profiles are sent if the threshold is breached (similar to configuring 
        Alarm
         
        Always 
        for all the monitors).
  7. Click 
    Actions
     > 
    Test
     to validate the resource properties. 
  8. Click 
    Save
    .
To delete a resource, click the 
Options (icon)
 on the 
Profile -
Resource Name
 
 node and select 
Delete Host
.
Add Profiles to a Resource
A profile represents a node of the WebSphere cluster, which contains the monitors for monitoring the IBM WAS. You can add a profile by selecting it from the 
Available 
list to the 
Selected 
list. 
 
Follow these steps:
 
  1. Navigate to the 
    Websphere
     node of your 
    resource name
     node.
  2. Under the 
    Profiles
     section, select a profile from the 
    Available
     list to add it to the 
    Selected
     list.
     The profile name is taken at runtime and it depends on the IBM WAS configuration.
  3. Click 
    Save
    .
    The profile is added as a sub node of the 
    Websphere 
    node. The probe populates the list of monitor groups and their associated monitors under each group.
Create a Profile
You can create a profile for a specific node of the WebSphere cluster, as required.
 
Follow these steps:
 
  1. Click the 
    Options (icon)
     next to the 
    Websphere 
    node.
  2. Select 
    Add New Profile
    .
    The 
    Add New Profile
     dialog appears.
  3. Specify the following information, as required:
    •  
      Active: 
      activates the profile for monitoring, on creation.
      Default: Not Selected
    •  
      Name:
       defines a unique name for the profile.
    •  
      Node:
       defines the node name in the cluster.
    •  
      Server:
       defines the server name in the cluster.
    •  
      Alarm Message:
       specifies the alarm message that is generated when the profile does not respond.
  4. Click 
    Submit.
    The profile is created as the node.
  • Navigate to the 
    Profiles
     section under 
    Websphere
     node, and move the profile from the 
    Selected
     list to the 
    Available
     list to:
    • Deactivate a default profile from monitoring.
    • Delete a custom profile from the probe.
  • To delete a profile, click the 
    Options (icon)
     on the 
     
    Profile Name
     
     node and select 
    Delete Profile
    .
Configure Monitor Properties
After you create a profile, activate the required monitors to retrieve monitoring data. These monitors allow you to generate alarms and QoS data when the specified thresholds are breached.
 
Follow these steps:
 
  1. Navigate to the 
    Monitors
     node under the 
    profile name
     node.
  2. Select the desired monitor from the 
    Monitors
     section.
    The related fields of the monitors are displayed below the 
    Monitors
     section.
  3. Select the
     Publish Data
     and 
    Publish Alarms
     to retrieve QoS data and generate alarm messages, respectively.
  4. Specify or modify the following information, as required:
    •  
      QoS Name:
       indicates that the monitor uses default QoS only.
    •  
      Active:
       activates the monitor.
    •  
      Name:
       indicates the monitor name.
    •  
      Key:
       indicates a unique monitor key. By default, its value is mapped from the monitor name.
    •  
      Value Definition:
       specifies the value to be used for alarms and QoS.
    •  
      High Operator:
       select an operator to match the retrieved value with the threshold for the maximum limit.
      Default: !=
    •  
      High Threshold:
       specifies the maximum threshold for the monitor.
    •  
      High Message Token:
       specifies the alarm message to display when the threshold breaches the maximum limit.
      Default: MonitorError
    •  
      Low Operator:
       select an operator to match the retrieved value with the threshold for the minimum limit.
      Default: disable (indicates that the low threshold alarm is disabled)
    •  
      Low Threshold:
       specifies the minimum threshold for the monitor.
    •  
      Low Message Token:
       specifies the alarm message to display when the threshold breaches the minimum limit.
    •  
      Key not found alarm:
       sends an alarm when no key is found.
    •  
      Alarm Always:
       sends an alarm if the monitor value on this profile breaches the threshold, irrespective of the monitor value on other profiles.
    •  
      Compute Baseline:
       sends runtime information to the 
      baseline_engine 
      probe to generate dynamic threshold values for the monitor. This option might not be available depending on your CA Unified Infrastructure Management configuration. For more information, see Configuring Alarm Thresholds.
  5. Click 
    Save
    .
View Message Pool
You can view the properties of alarm messages that are configured in the probe.
 
Follow these steps:
 
  1. Click the 
    websphere
     node.
  2. Navigate to the Messages section and select the required alarm message.
    The following fields display the configured values of the selected alarm message.
    •  
      Message ID:
       indicates the unique name of the message.
    •  
      Message Text-Error:
       indicates the error message text.
    •  
      Message Text-OK:
       indicates the clear message content.
    •  
      Subsystem:
       indicates the alarm subsystem ID that defines the alarm source.
    •  
      Token:
       indicates the message token.
    •  
      Severity:
       indicates the alarm messages severity level.
    •  
      i18n_token-Error: 
      indicates the predefined error alarms.
    •  
      i18n_token-OK:
       indicates the predefined clear alarms.