Monitor model is not receiving events and instances are not viewable on the dashboard

Technote (troubleshooting)


Problem(Abstract)

You are working in a network deployment cell, your Common Event Infrastructure (CEI) server does not have IBM Business Monitor or WebSphere Business Monitor installed on it, and you have installed WebSphere Application Server V6.1.0.15 or higher on that CEI server.

Your monitor model is not receiving events and you cannot view instances on your dashboards.

Symptom

Your monitor model is not receiving events and you cannot view instances on your dashboards.

Additionally, the following error messages in the CEI server log might also indicate the problem described:

[9/25/09 14:25:30:764 EDT] 0000003d EventGroup E com.ibm.events.distribution.impl.EventGroup EventGroup CEIES0076E Failure to initialize custom event selector filter.
Class :null

[9/25/09 14:25:30:782 EDT] 0000003d EventGroup E com.ibm.events.distribution.impl.EventGroup EventGroup CEIES0076E Failure to initialize custom event selector filter.
Class :class com.ibm.events.util.xpath.EventSelectorFilter


Cause

The plugins do not exist on the CEI server, and need to be copied to the CEI server as part of the installation and configuration of the environment. To receive events to your monitor model and view instances on your dashboards, the plugins must reside on the CEI server, and you must run the osgiCfgInit command on the CEI server.


Resolving the problem

Complete the steps below to receive events and view instances on your dashboards when you are running WebSphere Business Monitor (V6.1.1, V6.1.2, V6.2, or V7.0), or IBM Business Monitor (V7.5, V7.5.1, V8.0, V8.0.1) in a network deployment cell with WebSphere Application Server V6.1.0.15 or higher (including all levels of V7.0) on your CEI server.

  1. Depending on the version of WebSphere Business Monitor or IBM Business Monitor, you will need to copy files from the Monitor server to each CEI server or cluster member (and possibly, delete or extract files on each server or cluster member).
    1. For WebSphere Business Monitor V6.1.1 or V6.1.2:

      Copy the following plug-ins from the <WAS_root>/plugins directory on the WebSphere Business Monitor server to the <WAS_root>/plugins directory on each CEI server or cluster member:

      com.ibm.wbimonitor.xsp.cei.extensions_6.1.x.jar
      com.ibm.wbimonitor.xsp.evaluator_6.1.x.jar
      com.ibm.wbimonitor.xsp_6.1.x (followed by the date and time, for example, 200711131700).jar
      com.ibm.wbimonitor.xml.expression_6.1.x (followed by the date and time) (the entire directory)

      For WebSphere Business Monitor V6.1.2.4 (and higher V6.1.2 levels), you also need to copy the following plug-ins:

      com.ibm.wbimonitor.xml.foundation_6.1.2 (followed by the date and time) (the entire directory)
      com.ibm.wbimonitor.ceiutil_6.1.0.0.jar
      com.ibm.wbimonitor.util_6.1.0.0.jar

    2. For WebSphere Business Monitor V6.2:

      Copy the following plug-ins from the <WAS_root>/plugins directory on the WebSphere Business Monitor server to the <WAS_root>/plugins directory on each CEI server or cluster member:

      com.ibm.wbimonitor.xsp.cei.extensions_6.2.x.jar
      com.ibm.wbimonitor.xsp.evaluator_6.2.x.jar
      com.ibm.wbimonitor.xsp.eventselector_6.2.x.jar
      com.ibm.wbimonitor.xsp_6.2.x (followed by the date and time, for example, 200809221700).jar
      com.ibm.wbimonitor.xml.expression_6.2.x (followed by the date and time) (the entire directory)
      com.ibm.wbimonitor.util_6.2.x.jar

      For WebSphere Business Monitor V6.2.0.1 (and higher V6.2 levels), you also need to copy the following plug-ins:

      com.ibm.wbimonitor.xml.foundation_6.2.x (followed by the date and time) (the entire directory)
      com.ibm.wbimonitor.ceiutil_6.2.x.jar

    3. For WebSphere Business Monitor V7.0:

      i. Delete all files named <WAS_root>/plugins/com.ibm.wbimonitor.monresources_7.0*.jar ('*' is a wildcard character representing any pattern of characters between "7.0" and ".jar") from each CEI server or cluster member.

      ii. From the <WAS_root>/scripts.wbm/crosscell folder on the WebSphere Business Monitor server, locate the appropriate file depending on your operating system and WebSphere Application Server version:

      Linux or Unix: monitorCommunicationWithWAS70BasedCells.tar or monitorCommunicationWithWAS61BasedCells.tar
      Windows: monitorCommunicationWithWAS70BasedCells.zip or monitorCommunicationWithWAS61BasedCells.zip

      Copy the appropriate file to the <WAS_root>/plugins folder of each CEI server or cluster member, and extract the contents.

    4. For IBM Business Monitor V7.5 or V7.5.1:

      i. Delete all files named <WAS_root>/plugins/com.ibm.wbimonitor.monresources_7.5*.jar ('*' is a wildcard character representing any pattern of characters between "7.5" and ".jar") from each CEI server or cluster member.

      ii. From the <WAS_root>/scripts.wbm/crosscell folder on the IBM Business Monitor server, locate the appropriate file depending on your operating system:

      Linux or Unix: monitorCommunicationWithWAS70BasedCells.tar
      Windows: monitorCommunicationWithWAS70BasedCells.zip

      Copy the appropriate file to the <WAS_root>/plugins folder of each CEI server or cluster member, and extract the contents.

    5. For IBM Business Monitor V8.0 or V8.0.1:

      i. Delete all files named <WAS_root>/plugins/com.ibm.wbimonitor.monresources_8.0*.jar ('*' is a wildcard character representing any pattern of characters between "8.0" and ".jar") from each CEI server or cluster member.

      ii. From the <WAS_root>/scripts.wbm/crosscell folder on the IBM Business Monitor server, locate the appropriate file depending on your operating system:

      Linux or Unix: monitorCommunicationWithWAS80BasedCells.tar
      Windows: monitorCommunicationWithWAS80BasedCells.zip

      Copy the appropriate file to the <WAS_root>/plugins folder of each CEI server or cluster member, and extract the contents.

  2. Stop all processes (servers and node agents) for each profile that contains a CEI server or cluster member that needs to be updated.

  3. Run the following command for each profile that contains a CEI server or a cluster member:

    Windows:
    <profile_name>\bin\osgiCfgInit.bat
    Linux or Unix: <profile_name>/bin/osgiCfgInit.sh

  4. Verify that the plug-ins were installed correctly by performing the following steps on each profile that contains a CEI server or a cluster member:
    1. Run the following command:

      Windows:
      <profile_name>\bin\osgiConsole.bat
      Linux or Unix: <profile_name>/bin/osgiConsole.sh

    2. At the osgi> command prompt, run the ss command.
    3. Make sure that all plug-ins whose names begin with com.ibm.wbimonitor are listed as RESOLVED.
      • If they are not listed, ensure that steps 1 through 3 were performed correctly.
      • If they are listed as INSTALLED, run the command diag xxx (where xxx is the number that corresponds to that plug-in) on each plug-in listed as INSTALLED. The response should list any unresolved constraints. If there are no unresolved constraints, repeat steps 2 and 3, then check again to see if the plug-ins are listed as RESOLVED.
      • Start each of the processes that you stopped in step 2, above.

Related information

A simplified Chinese translation is available

Cross reference information
Segment Product Component Platform Version Edition
Business Integration IBM Business Monitor Monitor Configuration AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Business Monitor
Monitor Configuration

Software version:

6.1.1, 6.1.2, 6.2, 7.0

Operating system(s):

AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows

Reference #:

1298137

Modified date:

2009-01-14

Translate my page

Machine Translation

Content navigation