websphere MCS Profile Type Configuration

A monitoring administrator uses the Monitoring Configuration Service (MCS) to create monitoring configuration profiles and deploy probes to target devices. Use the Webshpere Monitoring profile type to configure monitoring for Websphere resources.
You cannot configure a probe through the probe configuration GUI after you apply the MCS profile type to an instance of the probe. We recommend that you test your configuration before applying the configuration to many systems. To delete the configuration that is applied by MCS, you must delete the profile in MCS and then manually delete the probe. When you delete a profile, a lock icon might appear during the deletion process. Do not delete the probe until the profile is removed. Once the MCS configuration is deleted, you can manually redeploy the probe and configure monitoring through the probe configuration GUI.
Verify the following information before you create a monitoring configuration profile:
  • Download websphere_mcs_templates and websphere probe to your local archive. Deploy the websphere_mcs_templates on primary robot.
  • Verify that your CA UIM version is at least version 8.5.1 - required by the MCS profile types.
  • Verify that your archive contains websphere probe that is at least version 1.75.
  • Verify that all the dependent jre versions are available in archive. For example, java_jre, jre_solaris, jre_zlinux
  • Complete any probe-specific prerequisites.
  • Verify that you meet the minimum hardware and software requirements before you deploy a monitoring configuration profile.
  • Verify that you have a valid license for the probe.
To use the enhanced profiles, you need the following software environment:
  • CA Unified Infrastructure Management version 9.0.2
  • Monitoring Configuration Service (MCS) version 9.02 (or later)
  • Metrics plug-in version 7.96 (or later)
  • Robot version 7.96 (or later)
Enhanced Profiles in MCS
CA UIM 9.0.2 includes a new type of Monitoring Configuration Service (MCS) profile, called an enhanced profile. Enhanced profiles provide a consistent way to configure alarms using MCS. Enhanced profiles enable you to configure metrics, baselines, alarm thresholds, Time Over Threshold alarms, and create custom alarm messages, all within a single MCS profile. 
You can convert your existing MCS profiles to enhanced profiles. We recommend that you first migrate existing profiles to the latest available version and then convert them to enhanced profiles.
Profile Types
Use the websphere profile types to create configuration profiles for a websphere environment. Some of the profile types contain default monitor and alarm settings. These default settings are provided so you can configure your probes to collect data for the predefined probe dashboards in UMP. The predefined dashboards display the data that we recommend for monitoring various devices and services in your environment. Deploy all the monitoring profiles with default settings to automatically enable the metrics that are required by the predefined probe dashboards.
Profile Name
Setup Websphere
Use this profile for general probe configuration settings. The settings are applied to all resources.
Websphere Monitoring
Use this profile for creating resource/profiles. This profile contains a child template 
Websphere Auto Monitors
 used to enable QoS and Alarms. 
Create  Configuration Profiles
Use the websphere profile types to create configuration profiles. You can configure all instances of the websphere probe with configuration profiles. The quality of service metrics (QoS) that the probe can publish appear in each profile.
 We recommend that you do not activate any profiles until you complete your monitoring configuration. The probe restarts every time you activate a profile.
Follow these steps:
  1. In Unified Service Manager, expand a USM group and select a device OR click a USM group.
    The USM group can be one of the predefined USM groups (for example, the Unix and Windows groups) in a test environment or a test group you created that has one device.
  2. Select the Monitoring tab.
    The profile types that apply to the selected device or USM group appear in the middle column. If you select a device and profile types do not appear in the middle column of the Monitoring tab, deploy a robot to the device.
  3. Hover over the 
    Setup Websphere
     profile type name, and then click '
    ' to create a profile.
     If you see a dialog with a prompt to install the probe, verify that the probe is in the archive and select 
  4. Complete and save the required settings.
    The resource profile type node is added under the Setup Websphere profile. Expand the list to view the node.
  5. To enable auto monitors, expand the resource node under 
    Websphere Monitoring
    , and then select 
    Websphere Auto Monitors
  6. Select the desired QoS metrics and alarms in the Monitor column.
  7. (Optional) Return to any of the profiles and configure any additional metrics and alarms. The available options are:
    Select this option if you do not want to publish data or alarms for the monitor.
     Select this option if you only want to publish alarms for the monitor.
    Alarm and QoS: 
    Select this option if you want to publish both alarms and QoS data for the monitor.
    Choose this option if you only want to publish QoS data for the monitor.
  8. Save any profile changes.
  9. View the 
    Profile Status
     information to verify that the configuration profile was successfully deployed to the target device (or devices in a group if you created a group configuration profile). Profile status information appears at the bottom of the profile configuration page.
Configure Exclude/Include Filters
Use the Exclude/Include filters to allow the probe to generate or ignore alerts for specified entities. By default, the Include and Exclude fields are blank, you must add entities to be included or ignored manually as required. The following points must be considered while specifying entities:
  1. If you want to include or exclude multiple entities, separate the entities with “
    “ after each entity.
  2. Ensure not specifying same entity for both Include and Exclude filter.
 The Include/Exclude filters does not support Regex for filtering.
Examples for Include and Exclude Filters:
  1. beanModule#=LicenseCheckStartup,LicenseCheck#liccheckEJB.jar,ejb.stateless;connectionPoolModule=connectionPoolModule,Derby JDBC Provider (XA)
  2. connectionPoolModule=connectionPoolModule,Derby JDBC Provider (XA)
  3. threadPoolModule=Default
Invalid scenario:
connectionPoolModule=Derby JDBC Provider (XA)
Above entity names are may vary from server to server.
Default Settings
No QoS or alarms are enabled by default.
For more information: