HP OpenView Business Process Insight

Release Notes

14th December 2006

This document provides an overview of the changes made to HP OpenView Business Process Insight (OVBPI) for OVBPI version 2.10. It contains important information not included in the manuals or in the online help.

In This Version
Installation Notes
Known Problems, Limitations, and Workarounds
Problems with Associated Software
Support
Legal Notices

In This Version

OVBPI version 2.10 includes the following new and revised features. If you have not installed OVBPI before, you do not need to read this section:

• New version of the J2SE.

  OVBPI version 02.10 supports the JDK version 1.5, update 8 (jdk1.5.0_08). You must make sure that you install this version of the JDK before installing the new version of OVBPI. You also need to make sure that you select the correct version of the JDK during the installation.

• New installation option There is a new installation option offered, which is:

  Dashboards Only

  Use this option to install the Business Process Dashboard on a machine that is remote from the OVBPI Server components. You might want to do this in scenarios where the Dashboard is using a significant amount of the machine’s resources to complete searches and display flow instance data. By installing the Dashboard on a different machine, you can increase the system resources that are available to the OVBPI Server components.

• Changes to Installation Program to Remove Some Options for Installing

  The OVBPI Installation Procedure has been modified to allow only valid installation options to be presented for a reinstallation scenario.

  In versions of OVBPI prior to version 2.10, it was possible to select options that were not valid and that could not be completely removed by the OVBPI Uninstall procedure.

  The OpenView Business Process Insight Installation Guide lists the options that are now valid in the case of reinstalling OVBPI.

• Database schema changes

  There are two minor changes to existing database tables as follows:

  In table Resources and Nodes2Resources, the length of the Resource_ID column has been increased from 260 to 296 characters. This is to take account of the new Service Sources that can be defined and allows up to 40 characters for the name of the Service Source. The tables are described in the OpenView Business Process Insight Reference Guide.
• New and revised pages in the Administration Console:

  Changes have been made to the following Administration Console pages:

  • Status
  • Metric Engine
  • OVO Interoperability
  • OVIS Interoperability
  • Port Numbers
  • Logging
  The following pages are new for OVBPI version 2.10:
  • Operational Service Source
  • OVO Adaptor
  • Security
  These changes are described in more detail in the OpenView Business Process Insight Installation Guide.
• Select Access integration

  You can secure access to the OVBPI interfaces using HP OpenView Select Access. HP Select Access is part of the HP Identity Management suite of products; it provides policy-based authentication and authorization for your applications; for example, OVBPI Repository Explorer. Using HP Select Access is described in the OpenView Business Process Insight Administration Guide.

  HP OpenView Select Access is not part of the OVBPI version 2.10 distribution media and must be purchased separately.

• SOA Manager integration

  HP OpenView SOA Manager enables you to manage your service oriented architecture (SOA) resources. OVBPI version 2.10 provides new adapters to enable you to integrate with OpenView SOA Manager as follows:

  • using the SOA Manager service model to provide the status of SOA Manager business services to OVBPI. This is described in the OpenView Business Process Insight Reference Guide.
  • enabling OVBPI to receive business events from SOA Manager for the OVBPI business flows that it is monitoring. This is described in the OpenView Business Process Insight Integration Training Guide - Business Events.

  HP OpenView SOA Manager is not part of the OVBPI version 2.10 distribution media and must be purchased separately.

• OV Dashboard integration

  The OpenView (OV) Dashboard is an OpenView-wide Dashboard and should not be confused with the OVBPI Business Process Dashboard, which is a Dashboard for use only with OVBPI.

  OVBPI version 02.10 enables you to link the OVBPI service impact information into the OpenView Dashboard. Refer to the OpenView Dashboard documentation for more details of the features and functions offered and how to add links to the OVBPI Business Process Dashboard. The OpenView Business Process Insight Reference Guide also provides information on how OVBPI integrates with OV Dashboard.

  HP OpenView Dashboard is not part of the OVBPI version 2.10 distribution media and must be purchased separately.

• New administration parameters for Metric Engine
  • Java Virtual Machine settings

    These parameters enable you to modify the amount of memory heap available to the JVM for the Metric Engine.

  • Threshold Alert Notification settings

    These parameters enable you to control how often the Metric Engine polls its data, and the maximum number of alert notifications delivered within a particular polling interval.

  These new parameters are fully described in the OpenView Business Process Insight Administration Guide.
• New and revised methods for Notification Server templates have been introduced for OVBPI version 2.10:

  A full list of the new methods is described in the OpenView Business Process Insight Installation Guide.

• You can configure and run OVO Adapter on same machine as the OVBPI Server.

  You can now run the OVO Adapter on the same machine as the OVBPI Server. In previous versions of OVBPI this configuration set up was not supported. You add the OVO Adapter to your OVBPI configuration using the new OVO Adapter option in the Administration Console.

• OVBPI Modeler and BPEL import

  OVBPI version 02.10 enables you to import version 1.1 Business Process Execution Language (BPEL) definitions into the Modeler and use these BPEL definitions as the start point of your Flow definition. Refer to the OpenView Business Process Insight Integration Training Guide - Importing BPEL, for more information on the options for importing BPEL definitions.

• Support for Microsoft Server Clusters to provide high availability capabilities.

  You can install and set up OVBPI version 02.10 to operate in a Microsoft Server Cluster environment (in an Active/Passive mode). This is described in the OpenView Business Process Insight System Administration Guide.

• Introduction of Junction Nodes in OVBPI Modeler

  OVBPI 02.10 has introduced a new type of node in the OVBPI Modeler, the Junction Node. This new node is used to visually define the structure of a business flow.

  In particular, when you import a BPEL process, the OVBPI Modeler creates a Junction Node for the start and end of each BPEL structural element.

  Note: As this is a new type of node, you might see some anomalies when using a Business Process Dashboard that is pre OVBPI version 02.10 with Business Flows that are created using OVBPI version 02.10 and that include Junction Nodes.

  When displayed in pre OVBPI version 02.01 Business Process Dashboards, a Junction Node is displayed as a red square. This does not have an effect on the behavior of the Business Process Dashboard, it is a presentation anomaly only and can be ignored.

• Support of Self-Healing services

  HP Self-Healing Services, as used by OVBPI version 02.10, automates some of the steps involved in collecting information about a problem and then packaging the information to send it to HP.

  OVBPI version 02.10’s use of the Self-Healing services is described in the OpenView Business Process Insight Reference Guide.

• New documents in the OVBPI documentation set:
  • OpenView Business Process Insight Reference Guide
  • OpenView Business Process Insight Integration Training Guide - Importing BPEL
  • OpenView Business Process Insight Metric Definer Online Help

Installation Notes

Installation requirements and instructions for installing OVBPI are documented in the HP OpenView Business Process Insight Installation Guide. This guide is provided in Adobe Acrobat (.pdf) and Web (.htm) format on the product's distribution media.

Be aware that OVBPI has a requirement on J2SE; OVBPI 2.10 supports J2SE version 1.5, update 8 (jdk1.5.0_08). This version of the J2SE can be downloaded from the following location:

http://java.sun.com/products/archive/

OVBPI Uses Nodelocked Licensing

You must have a license key password to use OVBPI, specifically the OVBPI Server. Following your initial installation, you are automatically assigned a 60-day trial license. Within this 60 day period, you must obtain either a trial license extension, or a permanent license key password. OVBPI uses a Nodelocked license based on the short hostname (not the fully-qualified hostname) of the machine where the OVBPI Server is installed. You must supply a short hostname for the machine where you intend to run OVBPI when completing your license request form. You can obtain the short hostname using the following command from a Windows Command Prompt:

hostname

Do not supply an IP Address when applying for your license key as you will not be able to use the generated password to unlock your OVBPI installation.

The following is an example of a short host name:

server1

The following is an example of a fully-qualified hostname:

server1.hp.com

The following is an example of an IP Address:

111.222.333.444

Installation Problems

Installation Procedure Failure Due with Error Indicating a Service is Still Running

If you are installing OVBPI and the installation notifies you that there is a service running that you cannot detect using the Administration Console, you can check for active services as follows:

• On HP-UX:
  1. Login to an account that has root privileges
  2. Enter the following command:
     
     /etc/fuser /opt/OV/OVBPI/java/bia-common.jar
  
  
  The result of this command is the file name followed by a list process identifiers (pid) that have the bia-common.jar file locked open.
  3. Use the process identifier listed from the fuser command to list the process and to subsequently kill the process; for example:
     
     ps -fp pid

kill pid

  You must kill the process before you can continue with the installation.

• On Windows this is most likely to occur when you stop the OVBPI components individually on the Administration Console Status page. To resolve this problem, select the Stop All option on the Status page.

JDK Must Not be Installed into a Non-ASCII Directory

Due to restrictions in the version of the J2SE used by OVBPI, it is not possible to use a non-ASCII directory name for your J2SE (JDK) installation. The home directory for the J2SE installation must consist only of ASCII characters.

If you do install the J2SE into a non-ASCII directory, the OVBPI installation procedure is successful, but the OVBPI components fail to start.

Using the Back Button During Installation

There is a problem with the installer and using the Back button to make changes to previously entered values in the installation.

If you progress through the installation questions, and then decide to go back and modify a value of a parameter already entered, and the parameter is used as part of subsequent answers, the subsequent answers shown might not reflect the modified values. In this case, you need to correct the values as appropriate and continue with the installation.

Adjusting Logging Levels for OVBPI

You can adjust the logging levels for the OVBPI components as described in the HP OpenView System Administration Guide. However, if you set the logging levels to be FINE or FINER, a significant amount of logging information is generated that can quickly fill up disk space. Much of this logging information is RMI logging information.

You can selectively set the RMI logging information to the INFO level, and keep the OVBPI component logging at FINE or FINER, to significantly reduce the amount of information produced.

To do this, modify each of the OVBPI component logging property files (listed in the HP OpenView System Administration Guide) and add the following lines:

# This is intended to turn off RMI logging.  RMI only logs at FINE or FINER, so setting these to 
# INFO effectively turn off RMI logging.
sun.rmi.server.level=INFO
sun.rmi.loader.level=INFO
sun.rmi.server.level=INFO
sun.rmi.client.level=INFO
sun.rmi.dgc.level=INFO
sun.rmi.loader.level=INFO
sun.rmi.transport.level=INFO
sun.rmi.transport.tcp.level=INFO
sun.rmi.transport.proxy.level=INFO

You also need to change the template file for the OVBPI logging property files. If you do not, the changes that you made are reset by the contents of the template file whenever you apply changes to OVBPI components through the OVBPI Administration Console.

The template logging property files are located as follows:

OVBPI-install-dir\newconfig\DataDir\conf\bia\...

You now need to run the following file to make the changes to the configuration file, or files, active on your OVBPI system:

• On Windows
  
  ovbpi-install-dir\bin\biaadmin.bat applyconfig



• On HP-UX
  
  ovbpi-install-dir/bin/biaadmin.sh applyconfig

Note that if you reinstall OVBPI for any reason, the template logging property files are overwritten and you will need to reapply your changes.

Related Documents

You can access the complete set of documentation and training material for HP OpenView Business Process Insight on the distribution media. The documents include:

• Release Notes (this document)
• Installation Guide, which describes how to install all the OVBPI components.
• Concepts Guide, which describes OVBPI and the concepts on which it is based.
• System Administration Guide, which includes details of how to manage your OVBPI components.
• Reference Guide, which includes details of the architecture of the OVBPI system and how OVBPI integrates with other products. It also contains reference information, such as database tables used by OVBPI.
• Problem Solving Guide, which includes details of how to trouble shoot your OVBPI system.
• Integration Training Guide - Customizing Dashboards, which provides detailed information about the JSP custom tags that are available for modifying the existing Dashboard and developing your own Dashboard.
• Integration Training Guide - Business Events, which provides detailed information about creating adapters to accept events from underlying business applications into your OVBPI system.
• Integration Training Guide - Modeling Flows, which provides detailed information about how to create Flows and link them to underlying operational and business events.
• Integration Training Guide - Defining Business Metrics, which provides detailed information about how design and create business process metrics and metric thresholds for your business flows.
• Integration Training Guide - Importing BPEL, which provides information about how import BPEL definitions into the OVBPI Model Repository.
• Integration Training Guide - Monitoring Service Desk, which provides detailed information about how implement the example flows and adaptors, provided with OVBPI version 2.10, to link OVBPI to Service Desk Help Desk and Change Management modules.

Known Problems, Limitations, and Workarounds

The following are known problems and restrictions that apply to HP OpenView Business Process Insight:

OVBPI Server Restrictions

This section covers restrictions related to the OVBPI Server components:

• Severe Error in Web Services Provider Error Log When Configuring the OVBPI Adapter from Within OV Dashboard

  If you find an error message similar to the following in the Web Services Provider log file and following a new installation of OVBPI, it could be due to a known problem with the OVBPI integration with OV Dashboard:

  Fail to create XML registration file:C:\Program Files\HP OpenView\OVBPI\data\datafiles\ovbpi_registration.xml
  com.hp.ov.ed.adapter.datasource.InitializationException: Fail to create XML registration file:C:\Program Files\HP OpenView\OVBPI\data\datafiles\ovbpi_registration.xml
  	at com.hp.ov.ed.adapter.util.ServiceRegistrationHandler.(Unknown Source)
  

  This error occurs only once when you configure the OVBPI Adapter for the first time. The error is reported because the first time that the OVBPI Adapter is configured and created from within OV Dashboard, the Registration file does not exist.

  The error can be ignored as it does not have an impact on the integration with OV Dashboard or the operation of the OVBPI system.

• Unsupported Versions of Prerequisite Products

  The following product versions are not supported with OVBPI version 02.10:

  • HP OpenView Service Desk versions beyond version 4.5.

    Be aware that OVBPI version 2.10 does not support versions of OVSD later than version 4.5. If you try and use later versions of OVSD, you receive an error when you attempt to links to OVSD Service Calls and Incident reports for impacted instances from the Business Process Dashboard.

    This restriction does not affect HP Service Desk Process Insight, which does support later versions of OVSD. Check the OVBPI Installation Guide for details of the exact versions of OVSD that are supported.

  Refer to the OpenView Business Process Insight Installation Guide for full details of the OVBPI prerequisite hardware and software.

• Servlet Engine Appears not to Start Following System Restart

  Very occasionally, following a system restart, the Servlet Engine appears not to have started, both within the OVBPI Administration Console and as a Windows Service. The Servlet Engine service is actually in the processes of starting, but is taking a long time, possibly due to other applications causing delay; for example, the database can take a long time to start when it is very full.

  As a result of this scenario, the display of the status of the Servlet Engine service is not correctly synchronized through the Administration Console and the Windows Services. This is not a problem for your OVBPI system as the Servlet Engine is running and the displays will correct themselves following another system restart; however, if you want to resynchronize your displays immediately, complete the following steps:

  1. From the Status screen on the Administration Console, click the Start button for the Servlet Engine.
  2. Click the Stop button for the Servlet Engine as soon as it is enabled.

  Your Servlet Engine services are now synchronized and the Servlet Engine is not started. You can now restart the Servlet Engine as normal.

• Cannot Subtract Dates in Filter/Binding Expressions

  There are restrictions when entering filter/binding expressions where you want to subtract dates.

  If you see the following error in the OVBPI Engine log file, it is because you have used an expression that the Engine is unable to process:

  Invalid operator for data type. Operator equals multiply, type equals datetime, 

  Check the binding expressions that you have entered through the OVBPI Modeler, for example, you should be able to use a binding expression as follows:

  (event.dateProp - this.dateProp) > days (2) + hours (12)

  This expression tests whether the difference between two dates is greater than two days and 12 hours. However, the OVBPI Engine cannot process expressions where one date is subtracted from another date. In order to work around this restriction, you need to change the above expression to:

  (this.dateProp + days (2) + hours (12) > event.dataProp

  In this case, the duration is added to one date and tested against the second date to achieve the same result.

• Unable to Contact OVBPI RMI Registry During Component Startup

  If you receive an error message indicating that OVBPI is unable to contact the RMI Registry on port 44,000, this is likely to be due to a port number clash.

  The OVBPI RMI Registry uses port 44,000, and if another application or service is temporarily using this port, then the RMI Registry cannot start. To resolve this problem, you can:

  • wait and attempt to restart the OVBPI components again
  • use the OVBPI Administration Console to modify the port number for the RMI Registry.

    Select the Port Numbers tab from the OVBPI Administration Console to change the RMI Registry port number from 44,000.

• Cannot Start OVBPI on Windows 2000 if Not Connected to Network

  If you are using a Windows 2000 system and you attempt to start all the OVBPI components through the OVBPI Administration Console from a system that is not connected to the Network, some of the components fail to start.

  This is not specifically an OVBPI problem, as it is the Windows 2000 system failing when attempting to make connections. The Windows 2000 system does not recognize that the network is not available and waits for a response from the DNS server and eventually times out, but not before OVBPI has also timed out.

  You can resolve the problem by removing the configuration of the DNS server so the Windows 2000 system does not attempt to contact the DNS server. You do this through the Properties option for the TCP/IP connection in My Network Places.

  You also need to modify any openadaptor adapters that use the SocketSink class to use the IP address 127.0.0.1 in place of the string localhost.

• Performance Issues with Large Numbers of Flow Instances When Using a SQL Server Database

  There is a potential problem with the performance of your OVBPI system if you are using Microsoft SQL Server and have a large number of instances in the database. You might become aware of this problem when using the Business Process Dashboard and it seeming not to respond, or timing out.

  If you have more than 200,000 instances, you are likely to experience this problem.

  You need to minimize the number of instances in the database using the Engine instance cleaner Settings. You can configure the Flow and Data instance cleaner settings using the OVBPI Administration Console.

  As an example, if you have a ten-node flow that creates 10,000 instances a day, you need to make sure that you clean out the instances at least every ten days.

  Be aware that there will be some variation of performance according to your system configuration, the number of flows you have defined and how the database is tuned.

• Failure to Draw Service Map through OVBPI Dashboard

  If the OVBPI Dashboard does not display a service map for a Service that OVBPI is configured to use, it could be because the Dashboard is trying to access the OVO Root_Services service.

  The default OVBPI dashboard is unable to display a service map image for the OVO Root_Services Service in the ServiceHealth.jsp page.

  Make sure that OVO service that you synchronize with through the OVBPI Modeler is not the OVO Root_Services service.

• Failure to Display SOA Manager Service within OVBPI Dashboard

  If the OVBPI Dashboard returns an error similar to the following when you attempt to link to a SOA Manager-defined Service, it is likely to be because you are using a version of the Business Process Dashboard that does not recognize the Service definition:

  File: dash1-1_error.gif
  

  In this example, you are running a Business Process Dashboard based on OVBPI version 01.01. The integration with SOA Manager was introduced in OVBPI version 2.10. As a result, the OVBPI Dashboard version 01.01 does not understand the SOA Manager Service and is not able to render it.

  If you want to show SOA Manager Services, you need to upgrade your Business Process Dashboard to version 02.10.

OVBPI Metric Definer Restrictions

This section covers restrictions related to the OVBPI Metric definer component:

• Flow Fails to Progress When Common Data and Event Definitions Split Out From Single Flow
  The following scenario results in a Flow definition that cannot be progressed.

  1. Create and deploy two Flow definitions, each linked to the same Data definition.
  2. Separate the Flows completely by creating a new Data definition with identical properties to the first Data definition.
  
  One of the Flow definitions is now linked to the newly created Data definition and no changes are made to the progression rules.
  
  In this case, the Modeler should detect that the progression rules are referencing a different Data definition, but it does not and as a result, no flow instances are created.

  It is very time consuming to resolve this situation, therefore you are advised to use the Export and Import options within the Modeler to make a copy of a Flow definition. You must also rename the definitions (not overwrite them).

  Refer to the OpenView Business Process Insight Administration Guide for details of making copies of your Flow definitions.
• Illegal Exception Reported when Committing a Modification to Metric Definer

  The following error can be reported by the Metric definer, most likely when you are attempting to create or modify a Filter, Metric or Threshold definition:

  java.lang.IllegalStateException: Cannot forward after response has been committed.
  

  This is a transient error. If you receive this error, click the OK button to dismiss the error page, re-select Flow that you were modifying and repeat your modifications.

• Warnings in Metric Definer Log File

  Each time a Business Metric is created with an associated Metric Threshold or Group, a warning is generated in the Business Process Engine log file. This warning is added by Hibernate and can be ignored; there is not a problem with the Business Metric.

OVBPI Modeler Restrictions

This section covers restrictions related to the OVBPI Modeler component:

• Metrics Definitions Ignored When Importing a Flow Definition

  If you try to import a previously exported Flow definition into an OVBPI version 2.10 Modeler and the Flow definition contains version 01.01 style business process metric definitions, these business metric definitions are ignored on import.

  If you export a business flow using the OVBPI version 01.01 Modeler, and the definition includes one or more business metric definitions, you cannot then import the business metric (or metrics) using your OVBPI version 2.10 Modeler.

  This is because the business metric definitions have been moved from the OVBPI Modeler into the Metric definer, and the Modeler no longer has knowledge of business metrics.

  When you upgrade your OVBPI system, all the business flows and business metrics, which are defined within the Modeler, are migrated. As a result, your business metrics are moved to the new Metric definer where they can be managed. However, business flows that have been exported from the Modeler in OVBPI version 01.01 cannot be migrated when they are imported into your OVBPI 2.10 system. As a result, these business metrics have to be redefined using the OVBPI 2.10 Metric definer. OVBPI version 01.01 business flows can be successfully imported, this restriction impacts only the metric definitions.

• Multiple Concurrent Users of Modeler/Repository Not Supported

  You can start multiple OVBPI Modelers each connected to the same Model Repository; however, the Model Repository is unable to coordinate the changes to the same definition made by these multiple Modeler sessions.

  As a result, if more than one person is working on the same definition from different Modeler sessions, the last set of changes saved to the Repository overwrites those changes already saved for that definition from any other Modeler connected to that Repository.

  You are advised to run only one Modeler for each Modeler Repository, to prevent changes to definitions from being overwritten.

• Empty String Values and Null String Value Evaluation Within Oracle

  When entering property values for subscriptions within the Modeler be aware that the Oracle Server does not distinguish between a zero-length string and a string with a value that has not been assigned (null string). This means that if you want to test a zero length string within a subscription, you are advised to use a single blank space (“ “), and not an empty string (““).

• OVBPI Modeler Unable to Follow Expressions in Parenthesis with Function Calls

  In this release of the OVBPI Modeler, you cannot enter an expression, which is contained in parenthesis, and follow it with one or more function calls. For example, the following expression is not accepted by the OVBPI Modeler:

  (this.property).after() > 3;

  The following shows the same example in a form that is acceptable to the OVBPI Modeler:

   this.property.after() > 3;

• Modeler Performance Degradation

  There is a restriction with the OVBPI Modeler, where its performance is impacted by having too many definitions open simultaneously.

  If you find the OVBPI Modeler is not responding in a timely manner, try closing some of the definition windows that you have open in the OVBPI Modeler. You can see how many definitions are currently open using the Windows menu option, or the status bar.

• Using Semicolons in Subscription Actions

  You cannot include semicolons as part of an action expression for Data definition Event subscriptions as a semicolon is always assumed to be an expression separator. Make sure that you use semicolons only to separate the expressions for the Data Definition Event Subscription actions.

• Renaming a Definition to Name of Existing Definition

  If you rename a Flow, Data, Event or Service definition to be the same name as an existing definition, the OVBPI Modeler does not warn you that the definition name already exists. The result is that you have two definitions with the same name.

  When you subsequently attempt to save the renamed definition, you receive an error message similar to the following (depending on the definition type that you are renaming):

  Could not save the event definition. Please refer to the log files for more details.

  In addition, if you rename a Flow, Data, Event or Service definition and subsequently try to create a definition using the name of the original, you receive an error message similar to the following:

  Could not create the event definition as name eventName1 already exists.

  For example:

  1. Create an Event definition called EventName1
  2. Rename the Event definition to EventName2
  3. Create a new Event definition name called EventName1

  To avoid this problem, make sure that you save your changes immediately following step 2, when you have renamed the definition and before you try to create the new definition.

Installation Integrity Checker Restrictions

This section covers restrictions related to the OVBPI Integrity Checker component:

• Errors Reported When Using the Integrity Checker on HP-UX

  Before running the Integrity Checker on HP-UX, you must make sure that all the OVBPI components on the HP-UX system are shut down. If you do not, the Integrity Checker returns errors indicating that there are files marked as read-only that should have write access.

Using OVBPI Across Multiple Locales

This section covers restrictions related to the use of OVBPI across more than one locale. The subsections cover specific problems that have been identified; however, be aware that there are likely to be other cases where using locale-specific character sets for file names can cause similar problems with your system.

If you plan to change the locale of the system where OVBPI is running, or if you intend to move files across systems that have different locales, you are advised not to use locale-specific character sets, as these character sets might not be readable on systems with different locales configured.

• Error in Modeler When Attempting to Import a Flow Definition

  If you see an error message similar to the following when importing a Flow definition into the OVBPI Modeler, it is possible that you are attempting to import a Flow definition with a name that contains characters that are locale-specific:

  The file flow-defn-name.zip is not a valid import file. Please see the log file
  for more information.
  

  where flow-defn-name is the filename, based on the Flow definition name.

  There are restrictions in the use of locale-specific character sets, whereby a .zip file name can contain characters only from the character set of the system locale where the OVBPI Modeler is running. The content of the file can contain any characters, but the file name is limited by the character set of the Windows system that is reading or writing the file. In the case of the zip archive files for exporting and importing flows, the zip archive file name is based on the Flow definition name. Therefore, if you want to export a Flow definition, you have to consider where you will be importing the file. If you plan to move the file across locales, you are advised to use only ASCII characters for the Flow definition name to ensure the file can be read on any configured locale.

  This problem can also occur if you change the locale of the Windows system where you have created the flow definitions.

• Changing the Locale of a System Where OVBPI is Installed

  If you modify the locale for a system where the OVBPI Server is installed, you might find that you cannot start the OVBPI Administration Console when you reboot your system. The Administration Console also returns an error indicating that it cannot find the main class and that the program will exit.

  This can happen in cases where OVBPI is installed into a directory, which is named using locale-specific characters. If the locale for the system is then changed, it is not always possible for the directory and file names to be readable using the character set of the new locale.

  If you have changed the locale of the system where OVBPI is installed and you are experiencing this problem, you need to:

  • revert to the original locale and continue to use OVBPI.
  • revert to the original locale, uninstall OVBPI, configure the new locale, and then reinstall OVBPI into a new directory.

Documentation Errors

This section covers restrictions related to the OVBPI documentation:

• Self-Signed Certificate Not Provided with OVBPI

  There is a documentation error in the OVBPI System Administration Guide.

  In the context of the Servlet Engine and HTTPS, the documentation currently references self-signed certificate, which is provided with OVBPI at the following location:

  ovbpi-install-dir/misc/bia/OVBPIKeyStore
  

  This certificate does not exist and OVBPI does not provide one. You need to obtain a certificate from the appropriate authority to use with OVBPI, or generate your own key using the Java Keytool as described in the OVBPI System Administration Guide.

Problems with Associated Software

This section describes restrictions with software that OVBPI requires where the restriction has an impact on OVBPI.

• Potential Memory Leak in JDK Version 1.5.0_08

  If you frequently move between tabbed-dialog boxes when using the Administration Console or the OVBPI Modeler, your machine can begin to exhibit memory usage problems. If you are experiencing this problem, the likely symptoms are that the Administration Console or the Modeler become very slow in their response time, and eventually fail. When they fail, a message similar to the following is written to the appropriate log file:

  SEVERE: Stack dump: Java heap space
  java.lang.OutOfMemoryError: Java heap space
  

  If you are experiencing this problem, you need to move to a later version of the JDK; for example, the memory problem appears to be resolved in JDK Version 1.5.0_09.

• Running the OVBPI Installation on Turkish Locale Causes Exception Error

  If you attempt to run the OVBPI Installation procedure using a Turkish locale, the installer does not present the installation screens correctly and, as a result, you cannot answer the installation questions. This is a problem related to the InstallAnywhere software and details of the problem can be found at the following URL:

  http://support.installshield.com/kb/view.asp?articleid=Q110959

  In order to complete the installation successfully, you need to temporarily set the locale to a United States locale. When you have complete the installation, you can reset the locale to Turkish.

• OVIS Configuration Manager Accepts Only 8-Bit Characters

  This restriction is related to versions of HP OpenView Internet Services supported by OVBPI.

  The HP OpenView Internet Service (OVIS) Configuration Manager utility is not able to accept anything other than 8-bit character sets in its dialog boxes. As a result, if you intend to create OVBPI custom probes, the OVBPI Flow names, Node names and Metric names that you want these probes to monitor must have names that comprise only 8-bit characters.

• Do Not Use Non-ASCII Characters for the Oracle Database Data Directory

  If you enter non-ASCII characters for the Oracle database data directory during the OVBPI installation, the installation fails with a Database Setup error. The error indicates that Oracle is unable to create the database instance or a database table.

  If the OVBPI installer reports a Database Setup Error, and you have used non-ASCII characters for the name of the database data directory, you need to reinstall (overinstall) OVBPI into the same location, this time using a database data directory name that contains only ASCII characters.

• Using Remote Oracle Connections when Configuring OVIS Custom Probes

  There is a problem importing and exporting information from an Oracle Server database.

  If you see the following Oracle error in the OVIS Probe log file, you are likely to be experiencing a known problem with Oracle:
  
  ORA-12640: Authentication adapter initialization failed
  
  To resolve this problem, you need to modify the following line in the file sqlnet.ora:
  
  SQLNET.AUTHENTICATION_SERVICES= (NTS)
  
  Change the line to be as follows:
  
  SQLNET.AUTHENTICATION_SERVICES= (NONE)

• Microsoft SQL Server and Unique Properties in Data Definitions

  If you are using Microsoft SQL Server and you see an error message similar to the following, it could be a problem with unique properties in a Data definition:

  com.inet.tds.SQLException: Msg 2627, Level 14, State 2, Line 1, Sqlstate 23000
  Violation of UNIQUE KEY constraint 'UQ__u32Unique1008a5e__7EF6D905'. 
  Cannot insert duplicate key in object 'u32Unique1008a5e1556d'.
  

  The names of the constraint and the object vary according to the name of your Data definition.

  If you create a Data definition that has more than one property marked as unique, you must make sure that when the properties are created that they are assigned a value. If you do not, the Engine reports an error when it attempts to create a second Data instance.

  The error occurs because the properties that have not been explicitly assigned a value are assigned an internal value of null, and multiple values of null violates the unique constraint on the column in the SQL Server database. This is a known problem with SQL Server.

  You must make sure that when you create a Data definition that has more than one property marked as unique, that these properties are assigned values when they are created. For example, you could set a temporary value obtained from another property.

• InstallAnywhere Uninstaller Stops Responding

  Many errors encountered when the InstallAnywhere uninstaller is running, for example, a missing JVM, causes the uninstaller to stop responding, or hang.

  If you experience a problem where the OVBPI uninstaller stops responding, you need to complete the following tasks according to what you have installed:

  • Stop the uninstaller process, which is still running on your system. For example, on a Windows system use the Task Manager.
  • If you are removing an OVBPI Server, Modeler or OVO Adaptor installation, delete the OVBPI files under the OVBPI installation directory.
  • If you are removing the OVBPI Custom Probes for OVIS installation:
    • remove the following directory and all its content:
      
      hp-ovbpi\UninstallData\bia
      
      where hp-ovbpi is the OVBPI installation directory.
    • remove any files that include ovbpi or ovis-probes in their name from the following directory:
      
      hp-openview-install-dir\UninstallData
      
      where hp-openview-install-dir is the directory where HP OpenView Operations is installed.
  • Modify the Zerog Global Registry (an InstallAnywhere file) as follows:
    • Open the registry file, which is usually located as follows:
      
      c:\Program Files\Zero G Registry\.com.zerog.registry.xml (Windows)
      
      /var/.com/zerog.registry.xml (HP-UX)
      
      Note that on Windows the registry file is located in a hidden directory, so you might have to configure your system to display hidden directories and files.
    • If the registry file contains only entries for the product that you are attempting to uninstall (OVBPI or OVBPI OVIS PROBES), you can rename the file. However, if there are multiple product installations, or multiple instances of one product installation, you need to edit the file as described in the following step.
      
      If the registry file contains entries in addition to those for OVBPI or OVBPI OVIS PROBES, edit the file to remove the following entries:
      • The product elements for OVBPI or OVBPI OVIS PROBES. Make sure the element references the directory where the files are located that you want to uninstall.
      • The components elements for OVBPI or OVBPI OVIS PROBES. Make sure the component element references the the directory where the files are located that you want to uninstall.
• Restrictions When Using Autopass

  The following are restrictions that you need to be aware of when using Autopass (HP OpenView's licensing mechanism) with OVBPI:

  1. Autopass is a separate product and has its own requirements with respect to local language support. It is possible that versions of Autopass are available in languages that differ from the languages supported by OVBPI. In this case, you might see a mixture of US English and local language for each of the products.
  2. Autopass does not support the use of non-ASCII characters in entry fields; for example, you cannot enter customer details using non-ASCII characters. Refer to the Autopass product information for more details.

Support

Please visit the HP OpenView support web site at:

http://www.hp.com/managementsoftware/support

This web site provides contact information and details about the products, services, and support that HP OpenView offers.

HP OpenView online software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:

• Search for knowledge documents of interest
• Submit and track progress on support cases
• Submit enhancement requests online
• Download software patches
• Manage a support contract
• Look up HP support contacts
• Review information about available services
• Enter discussions with other software customers
• Research and register for software training

Legal Notices

©Copyright 2006 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Java™ is a US trademark of Sun Microsystems, Inc.
Microsoft® is a US registered trademark of Microsoft Corporation.
Oracle ® is a registered US trademark of Oracle Corporation, Redwood City, California.
UNIX® is a registered trademark of The Open Group.