The following are other known limitations in WebSphere® Business Monitor.
- Running Launchpad from CD-ROM: When running Launchpad from a CD-ROM,
you will need to access the prerequisites from a hard drive. The Launchpad
CD cannot be ejected while the Launchpad application is running. If you prefer
to install the prerequisites from CDs, first copy the Launchpad CD to a local
hard drive, and then execute the Launchpad.bat from the hard drive
location.
- Installer quits without warning: When using the WebSphere Business Monitor Launchpad
to install the WebSphere Process
Server or
the WebSphere Application
Server, you may notice
the installer quits without warning. This can occur if you have manually
edited the contents of your vpd.properties file stored in the %WinDir%
directory. If your vpd.properties file contains only white space,
it can cause the Launchpad to throw an exception. The solution is to delete
the vpd.properties file entirely.
- Switching JetStream's use of Database Providers from Cloudscape to
DB2: When WebSphere Process
Server is
installed, by default it uses Cloudscape as the persistent datastore
for the Messaging engines such as the SI bus. Cloudscape is not the
optimal solution for scalability, reliability and performance reasons. To
replace the Cloudscape datastore with a DB2 database,
follow the steps listed in this article:WPS Messaging using DB2 instead of Cloudscape
- Additional installation step required when installing the Dashboard
Client component: An error may occur when attempting to configure Active
Instances view when a Maximum Duration is defined for the monitored process
and the Process Is Delayed business measure is selected. To avoid this error,
after the installation of the Dashboard Client component you must copy DDbE.jar
file from <WAS_Root>\lib directory (on the machine where Monitor Server
is installed) and paste it in the <WAS_Root>\lib directory on the machine
where Dashboard client is installed. You can also clear the selection of the
Process Is Delayed business measure during the Active Instances view configuration.
- Required steps before manually creating the State, Runtime, and Historical
databases: If you create the databases manually, or when the part of database
creation that updates the Repository database does not complete successfully,
the Database_Characteristics table in the Repository database will not be
updated. When you use the Launchpad to create the databases, the Launchpad
updates that table. Refer to the topic named Creating WebSphere Business Monitor databases under WebSphere Business Monitor installation instructions to
determine the information that needs to be inserted into the Database_Characteristics
table. If you are creating the State, Runtime, or Historical database manually,
you must put the DB2 user's password in the DDL file associated with the database
as follows:
- Edit the DDL file that is used to create each database.
- Search for "connect to" and "CONNECT TO". There may be several lines that
contain these strings.
- After the word using there will be a string of asterisks ("********").
Replace the asterisks with the DB2 user's password.
- Save the DDL file.
- Calculation of Elapsed and Working durations: The predefined metrics,
Elapsed Duration and Working Duration, are implemented as timers. When the
timer is ongoing (not stopped), the values are not accurate. The timer is
exact only after a stop or reset. The expected behavior is as follows:
- The Working Duration value is exact whenever a child activity instance
is completed.
- The Elapsed Duration value is exact when the process instance is completed.
- Metrics of Type Time: Metrics of type Time should not be
populated from events; the Monitor Server may throw an IllegalArgumentException.
- DB2 Alphablox 8.3 update: To obtain the required Alphablox maintenance,
complete the Alphablox installation via Monitor Launchpad, then go to the
following URL and follow the instructions. http://www-1.ibm.com/support/docview.wss?rs=2026&context=SSCPX3&dc=D600&uid=swg21227687&loc=en_US&cs=UTF-8&lang=en
- Truncated messages in Russian: When using the product in Russian language, two messages in the Dashboards Organizations view appear truncated. A technote is made available on the support site with the required fix.