HP Business Service Management Readme
for the Windows operating system
Software version: 9.00
Publication date: July 2010 (Updated Feb. 2011)
This file provides information about HP Business Service Management (BSM) 9.00:
Documentation Updates
The first page of this document contains the following identifying information:
To check for recent updates or to verify that you are using the most recent edition, visit this URL (requires HP Passport credentials): HP Software Product Manuals
To retrieve a document, select the:
You must have Adobe Reader installed to view files in PDF format (*.pdf). To download Adobe Reader, go to the Adobe web site.
What's New
To view a list of new features for this release, select Help > What's New in BSM, or double-click whatsnew.html from the root directory of the BSM DVD.
System Requirements
To view a complete list of system requirements, see the HP Business Service Management Deployment Guide.
Notes and Limitations
General and Deployment
- A consolidated patch over HP Business Service Management 9.00 will be available on the HP Software Support Web site (http://support.openview.hp.com/selfsolve/patches) to address a number of critical issues. For a description of the issues resolved by the patch, refer to the specific patch notes.
- TransactionVision-specific patches are not included in the HPBsm900SRP. Please contact HP Customer Support to obtain TransactionVision hotfixes for release 9.00.
- The HPBsm900SRP patch installation may fail to install on Windows 2008 R2 Server if there is an active antivirus software program on the same machine at the time of install.
Workaround: Before installing the HPBsm900SRP patch you should disable any antivirus software installed on the machine. You can reactivate the antivirus software after the patch installation. (QCCR1I48717)
- Capacity Calculator. The capacity calculator Excel sheet, BSM_9_Deployment_and Capacities.xls, can be found in the Documentation folder in the main BSM installation DVD. The latest version can also be downloaded from the HP Software Product Manuals site.
You use this Excel sheet to input information regarding the scope of your deployment (applications, number of users, expected data) and the capacity calculator then calculates the required memory and determines the size of your deployment. You then use this information to determine your hardware requirements and deployment configuration. You can upload the data from the capacity calculator Excel sheet while running the Setup and Database Configuration Utility in the Server Deployment page. For details, see "Using the Capacity Calculator" in the HP Business Service Management Deployment Guide.
- Authentication: BSM's default authentication strategy is Lightweight Single Sign-On (LW-SSO). When LW-SSO is enabled, you must use a fully qualified domain name (FQDN) to access BSM. This will enable integration among supported HP applications with a Single Sign-On manager, as well as working with BSM ODB. If you are not able to provide an FQDN, it is still possible to use IP addresses for LW-SSO-trusted hosts. For details on working with IP addresses, see "Authentication Strategies" in the Platform Administration guide.
- Licenses. When importing a license file that includes licenses for several BSM applications, an error message may open indicating that some licenses are invalid. You can ignore this error message. The error message is a result of invalid comments in the license file that do not affect the actual licenses. The licenses will still be imported.
Note that whenever you import new licenses, you must go to the Server Deployment page to activate the applicable applications. (QCCR1I48587)
Workaround: Create a duplicate path on the C:\ drive by copying E:\<HP BSM root directory>\conf\settings to C:\HP BSM root directory>\conf\settings. (QCCR1I47337)
- If the management database was down or unreachable and the connection has been restored, you may have to restart BSM. (QCCR1I46504)
- When using Java version 1.6.19 and higher in a secure environment (SSL) using basic authentication, you are prompted to enter credentials for each applet every time the applet is loaded. This is a known issue by Sun.
Workaround (as suggested by Sun): When each applet loads the first time, select Remember password. There is no security concern with this workaround since the applets are also protected by the browser and you are prompted for your credentials once every time you log into BSM through the browser using basic authentication. (QCCR1I45194)
Workaround: Add the parameter -Dsun.security.ssl.allowUnsafeRenegotiation=true to the Java client. (QCCR1I44883)
- High Availability: If there is a problem with one of the marble_* processes (for example, one of the processes cannot start), you must disable the marble_supervisor process. If this process is not disabled, the High Availability Controller (HAC) cannot move the process' services (such as the DASHBOARD service that controls Service Health) to another Data Processing Server if there is a problem with the primary server. (QCCR1I46345)
- In a reverse proxy environment, if you attempt to log into BSM directly bypassing the reverse proxy, you may encounter errors when trying to access Admin > ODB Administration pages. If your BSM is in a reverse proxy environment, always log in via the reverse proxy. For details on using a reverse proxy, see the HP Business Service Management Hardening Guide. (QCCR1I45985)
- When BSM is running on a machine with less memory than recommended, the Nanny Status page (accessed from Start > Programs > HP Business Service Management > Administration > HP Business Service Management Status) may display missing memory in MB that is different from the memory that is displayed in the Server Deployment page (accessed in the BSM interface from Admin > Platform > Setup and Maintenance > Server Deployment). (QCCR1I48113)
- BSM comes with Lightweight Single Sign-On (LW-SSO) capability, which enables you to log in to a single application and then permits you to access other supported applications configured in the original application's group. For limitations, security warnings, and general reference on using LW-SSO, see the Lightweight Single Sign-On Authentication - General Reference section in the Platform Administration guide of the BSM Documentation Library.
- An Internet Explorer exception error message is thrown inside BSM pages (usually on login page or in MyBSM), indicating Operation aborted. To resolve this issue, remove the Skype add-ons on your system. For further details, see http://support.microsoft.com/default.aspx/kb/927917 .
Platform
- When you use the Server Deployment page (Admin > Platform > Setup and Maintenance > Server Deployment) to change the capacity level of Metric data, the message broker must be reconfigured for the new memory allocation to take effect. The change in server deployment requires disabling and enabling BSM on all servers. Before enabling BSM on each server, you must reconfigure the Message Broker as follows:
- If your environment contains a reverse proxy secured with the SSL protocol and the BSM server behind the reverse proxy is not secured with SSL:
Replace the file: <HPBSM root directory>\AppServer\webapps\site.war\WEB-INF\flex\services-config.xml with the following file found in the same directory: services-config(for-reverse-proxy-env).xmlThen use this new services-config.xml to replace the services-config.xml file found in each of the following folders on the BSM Gateway Server:<HPBSM root directory>\AppServer\webapps\tvb.war\WEB-INF\flex
<HPBSM root directory>\AppServer\webapps\bpi.war\WEB-INF\flex
If this is not done, you may see errors when loading pages with Adobe Flex components (for example, Application Status report in EUM).
After replacing "services-config.xml" in all locations, restart BSM. (QCCR1I40830)
- Downtime. If the Data Processing Server is down for any reason, notifications of downtime starting and ending may not be sent. Notifications sent to recipients regarding downtimes are configured during downtime creation. (QCCR1I44964)
- Platform Administration (Windows Server 2008): On Windows Server 2008 SP2 or R2, when viewing files using Windows Explorer, the size of Business Service Management log files might be displayed as 0 bytes even though there may be information in the logs, or as a smaller number of bytes than represents the quantity of data in the logs. Refreshing the Explorer view may solve the issue.
- Platform Administration (Windows Server 2008): On Windows Server 2008 R2, if the Business Service Management root directory is defined as a shared folder, when attempting to open Business Service Management in a browser to log in, an HTTP 401.3 server error is displayed and it is not possible to log into the application. Workaround: Grant full control for IUSR account and IIS_IUSRS group on Business Service Management root directory (by default, called HPBSM). Then restart IIS using iisreset /RESTART.
- Authentication: When HP Business Service Management is installed with an Oracle Database and User Synchronization enabled with an LDAP Active Directory server, ensure that you login to HP Business Service Management with the correct-case UID (uppercase or lowercase), as configured on the LDAP server. This is because while the Oracle Database is case-sensitive, the LDAP Active Directory is not case sensitive, and logging in with an incorrect case UID can create undesirable results.
For example, if a user called testuser exists on the LDAP Active Directory server and logs into HP Business Service Management, he is automatically created as HP Business Service Management user testuser, who can be assigned permissions in the HP Business Service Management User Management interface. If you then login to HP Business Service Management as Testuser, the LDAP Active Directory server sends an acknowledgement that the user exists (because Active Directory is not case sensitive) and he is allowed entry to HP Business Service Management. However, since the Oracle Database does not identify this user as testuser (because the Oracle Database is case sensitive), the user Testuser is treated as a new user, without the permissions that were assigned to testuser.
Integrations
- BSM integration with Release Control is not supported in BSM 9.00. For details on Release Control support in BSM, check future versions of this document or the Release Control release notes.
- To enable the integration between Operations Orchestration and BSM, you must follow the procedure documented in the task "How to Integrate BSM and OO" in the Solutions and Integrations Guide and perform the following additional steps while importing the OO server certificates to BSM:
- When invoking an Operations Orchestration runbook, a dialog box opens with the list of invokable runbooks. At the top, you may edit the parameters, however if you invoke the runbook from the Edit window, you will need to retype the password (even though it looks the like passwords field is completed). (QCCR1I48719)
- More than one HPOM (formerly HP OVO) monitor can be created on the same port using the Copy function, resulting in duplicate HPOM events. In such cases, delete the copied monitor. Note that the HPOM Event monitor is not available when SiteScope 11.00 is connected to BSM 9.00, unless the monitor was created in an earlier version of SiteScope that was upgraded to SiteScope 11.00.
- The maximum size of an expression in the EMS Integration configuration file is 4000 characters.
- An EMS monitor may not find its configuration file when upgrading the SiteScope version. In such cases, manually copy the contents of the configuration file to the EMS monitor configuration in the user interface.
- For the HP Service Manager Federated integration, the Service Health application sometimes displays only partial results for Changes.
Workaround: Use the Incidents and Changes option in the Service Health application without the Show data for child CIs option. (QCCR1H29078)
- The following procedure for activating an out-of-the-box integration point (CMStoODBSync or ODBtoODBSync) sometimes does not work:
- In the Create New Integration Point dialog box, enter the required parameters for your integration point but do not select the Is Activation Enabled check box.
- Save the integration point and click the Full Integration Refresh icon.
- Click the Edit Integration Properties icon and select the Is Activation Enabled check box.
Workaround: Create a new integration point. (QCCR1H29077)
Reports and Reporting
- The TransactionVision data is not supported as a data source in Service Reports in BSM 9.00. (QCCR1I45415)
- The Business Process Insight Data is not supported as a data source in Service Reports in BSM 9.00. (QCCR1I45130)
- It is not possible to search charts inside reports exported to PDF (since the charts are saved as images). It is possible to search inside tables.
- It is not possible to export chart reports to Excel and XML (CSV is supported).
Service Health
Administration
Workaround: Define an additional condition, whereby the value is not null. (QCCR1I47794)
- In general, when you manually edit an HI on a CI using the CI Indicators tab (for example to use a different calculation rule), the assignment mechanism does not override these changes. However, if you modify an HI from being fed by metrics to being fed by events, the assignment mechanism does not recognize this change, and the HI is restored to its original setting. Note: This scenario is not likely in typical usage of BSM. (QCCR1I42865)
- Modifying Breakdowns: If you have configured a breakdown in a local impact view (for example, transaction by location), and you want to change the breakdown type (for example, to location by transaction), you must perform the below steps:
- If you delete a local impact view from the ODB while the local impact view service (LIV_SERVICE) is down, the service will not be able to start again. An error message is displayed in the following log file: HPBSM\log\businessImpact_service\liv.log, containing the name of the missing view.
Workaround: Create a new view in the ODB that is identical to the deleted view; note that the view name is case-sensitive. (QCCR1I47983)
- Within View Builder, if you create a folder whose name includes an apostrophe, View Builder fails. Do not use apostrophes in folder names. (QCCR1I48095)
- If an HI does not have a valid rule assigned, and you change the HI's definition in the CI Indicators tab from Metrics and Events to Events Only, an exception occurs. This change cannot be saved. (QCCR1I38813)
- Within the View Builder, you cannot create a template-based local impact view. If you create such a view, a global view is created instead. (QCCR1I47527)
- When you create a perspective-based view in View Builder, the view usually takes up to a minute to be calculated, and CIs and KPIs for the view are not displayed during this time. To see the CIs and KPIs in the Service Health Administration tabs, reload the view manually after a minute has passed. (QCCR1I48364)
- When you edit a perspective-based view in View Builder, and you deselect the Apply Over Model Hierarchy checkbox in the Perspective selection area, when you save your view the following error message appears: Failed to load view. This error is caused by the fact that View Builder takes up to a minute to calculate the new view. Despite this message the view is created properly, and the message can be ignored. (QCCR1H28745)
- Generally, when a CI matches more than one assignment, the assignment mechanism activates the assignment that is the most specific (on a lower-level CIT). For example, if a CI fits assignments both on the Host and UNIX CITs, the UNIX one is activated and not the Host one, because UNIX is a more specific (lower-level) CIT.
However, this sorting fails when an assignment is stopped. If an assignment that matches a CI is stopped on a lower-level CIT, even though there may be an assignment on a higher-level CIT that matches this CI, it will not be applied, and no assignments will run for the CI. (The exception for this is if there is another valid and running assignment on the lower-level CIT, in which case this assignment will run.) (QCCR1I47762)
- When the status of a health indicator changes, and an event is generated as a result of this change, the Close Key Pattern that is defined for the HI in the Indicator Repository is sometimes not created for the generated event. As a result, when an event is generated by the HI's status change, it fails to close the event which was generated by the previous status change.
Workaround: Open the HI for editing in the Indicator Repository. Click Configure Events to open the Event Configuration dialog box. Verify that the Submit close key condition checkbox is selected; click OK, and save. (QCCR1I48526)
- The Rules API that was introduced in Business Availability Center version 8.00 enables you to create new business rules for Service Health and Service Level Management, using the Groovy scripting language. The BSM documentation contains basic examples of API rules. Additional examples of rules based on customer requests can be found in the Self-Solve knowledge base, in document KM778069. This document is intended to be collaborative, and more API rules will be added to it based on customer input. If you have any comments on existing rules or suggestions for new rules, please provide feedback on the document within the knowledge base. Your feedback will then be included within the document.
- When editing a parameter for a rule in the Business Rules repository, changing the value in the Name box actually changes the value of the reference key for the parameter. Since the reference key is used for the rule calculation in the Business Logic Engine, changing the value may cause the calculation to fail. Do not edit the display name for a parameter.
Application
- When a view contains CIs that are nested in many hierarchy levels, Top View sometimes does not show the expand button (+) next to a CI even though there are lower-level CIs that should be available for display. You can see if there are more levels under the selected CI by accessing the menu command Show > Find Visible and Hidden Child CIs.
Workaround: From the CI's menu commands, select Show > Expand More Levels (or, if the CI is a virtual CI, access the menu command on its parent CI). (QCCR1I46578)
- The Hierarchy component cannot dynamically add KPIs to a CI. If a KPI such as Unresolved Events is dynamically added to a CI based on an event from Operations Management, the Hierarchy component does not show this KPI until you exit and enter the view again. Note that this only occurs if the KPI did not previously exist on any CI in the view. (QCCR1I39552)
- After the BLE is restarted, each HI's state is set to the default state, according to its status. This is an issue if you have multiple states mapped to a single status. (QCCR1I47246)
- If you are working with High Availability and a load balancer, if the management database goes down, the 360° View suffers a fatal error. To resolve, log out of BSM and then log in again. (QCCR1I46512)
- If you are working with High Availability and a load balancer, if the BLE online process goes down, an error message is generated. In some cases, this message does not disappear until you close the active page, and open it again. (QCCR1I46521)
- Within the 360° View, if you select the Filter icon on the toolbar, and then click the Configuration Items link, the Configuration Items dialog box opens. If you move this dialog box within the screen, the UI can freeze. When you reselect the component, it is again enabled. (QCCR1I42825)
- If a group CI contains special characters, and a filter within the Hierarchy component returns a CI that is contained within such a group, when you click on a CI that is a child of that group, an error occurs. (QCCR1I46190)
- If no new samples were received after a breakdown was defined in a view, if samples were received from only some of the locations, the view can show inconsistent worst statuses on the locations. (QCCR1I47502)
- In the Geographical Map component in non-Virtual Earth mode, when you select a view using the component filter and then click a CI in this view within another component on the page, an error occurs. (QCCR1I48032)
- Local impact views that contain virtual CIs and also have a breakdown defined, are not supported in Service Health application. Such views will cause internal errors. (QCCR1I47819)
- In a local impact view with breakdown defined, when a KPI is based on samples that do not contain the relevant breakdown information, the KPI may contain misleading data. For example, you may have a breakdown of location by application, and an application CI shows Worst Status of the System KPI from two business transactions. If these BTs are in two locations, and the KPI is Critical in one of the two, each location will show the application as Critical, even though the BT is Critical in only one of the locations. (QCCR1I47561)
- Attempting to view federated incidents and actual changes in the Service Health application sometimes fails. Workaround:
Note: You may have to enter user credentials to access the JMX console; if you do not know them, ask your system administrator. (QCCR1I47931)
- The PNR KPI in Service Health does not have persistency in case of a Data Processing Server failure or a system restart. The PNR KPI shows an initialized status until the SLA is recalculated, at which time the PNR value is updated.
- Reports that include the time period during which a Daylight Savings Time (DST) change took place (change to or change from DST) will either be missing one hour (in cases where clocks are moved forward) or have two sets of data for the same hour (in cases where clocks are moved back).
- If a report's time range includes the time of a Daylight Savings Time (DST) change, the data for the period after the DST time change is incorrect. To obtain correct data for the entire time range, print two separate reports, one for the time range before the DST time change and one for the time range after the DST time change.
MyBSM
This message is not indicative of a problem. Any changes you made in MyBSM are saved, and MyBSM continues to work correctly.
Workaround: To prevent this message from appearing, within Internet Explorer access the Internet Options > Advanced tab, and clear the Display a notification about every script error checkbox. (QCCR1I47291)
Service Level Management
Workaround: Define an additional condition, whereby the value is not null. (QCCR1I47794)
- If a CI has more than one parent CI, only one of the parent CIs is shown in the HI CI Summary report. (QCCR1I46997)
- If a CI has more than one parent CI, in some cases the CI Summary report displays the wrong CI as the parent CI. (QCCR1I46998)
- After BSM restart, the automatic linkage of Business Transactions to SAP Transactions is disabled. To enable this linkage mechanism, restart the VERTICALS service in the MercuryAS process. (QCCR1I47274)
- If the ETL tasks on the TRANSACTIONS_DIM or LOCATIONS_DIM tables do not progress because of a failure, the offline engine will also not perform SLA calculation tasks, until the ETL tasks for the same time period have been executed. (QCCR1I43943)
- When you create a new health indicator template in the Indicator Repository, if you define the HI as applicable for Service Level Management only, this may cause problems in the internal operation of the HI assignment mechanism. To prevent these problems, define new HIs as applicable for both Service Health and SLM (or for Service Health only), but not for SLM only. (QCCR1I44620)
- The Rules API that was introduced in Business Availability Center version 8.00 enables you to create new business rules for Service health and Service Level Management, using the Groovy scripting language. The BSM documentation contains basic examples of API rules. Additional examples of rules based on customer requests can be found in the Self-Solve knowledge base, in document KM778069. This document is intended to be collaborative, and more API rules will be added to it based on customer input. If you have any comments on existing rules or suggestions for new rules, please provide feedback on the document within the knowledge base. Your feedback will then be included within the document.
- In Service Level Management, you cannot attach more than one PNR KPI (defined in Service Health) to a CI.
- Stepping into the Configure SLA Indicators step of the SLA wizard may take a while for large SLAs.
- You cannot add a CI to an SLA when the CI includes a copy of itself in the original definition in the ODB. This is because nesting is meaningless in the SLA calculation (Service Level Management cannot calculate a CI using the CI result as a value). If you do so, your operation will fail with a general error. However, you can add the same CI to an SLA more than once if the CI does not include a descendant of itself. In this case, Service Level Management calculates the CI only once, so the objectives are the same no matter where the CI appears in the SLA hierarchy.
Operations Management/Operations Manager i (OMi)
Administration
- When selecting a correlation rule that contains only one CI type (the causes and symptoms are defined on the same type) the "Find Matching CIs" popup looks as if it only shows a list of the symptoms, but the causes are included in the same list. The interface does not correctly separate the causes and symptoms, but mixes both in the "Symptoms" entry. If there is only a "Symptoms" entry, this entry also contains all CIs and indicators for the cause.
Workaround: Look at the correlation rule to identify the "cause" CIs. (QCCR1A108805)
Workaround: Reload the page by pressing F5. (QCCR1A108915)
- The Correlation Rules manager and the Correlation Generator both require the user to have ETI Mappings permissions (in addition to the Correlation Rules permissions). Both these resources appear under the Administrative UIs resource in the Operations Management context in Users and Permissions. A user who does not have permissions for both resources will not be able to view indicators in the Administration UIs, nor use them for setting symptoms and causes.
Workaround: Give users who are allowed to work with Correlation Rules manager and the Correlation Generator permissions for ETI Mappings. (QCCR1A108990)
Workaround: Use the following command to create a snapshot of a content pack:
ContentManager.bat -snapshot -o c:\snapshot.xml -username admin -password admin (QCCR1A109193)Workaround: As the rule has already been saved, it is safe to click cancel, and then cancel the rule creation. When you refresh the correlation rule list, the new rule appears in the list. (QCCR1A109171)
Authorization
Workaround: After the refresh interval of 10 minutes, log off and back on again. The deleted users and groups will not appear and any added users and groups should be available. (QCCR1A91299)
CI Resolution
- BSM uses TQL queries to describe what CIs to get from the ODB in order to relate the CIs to the events that BSM receives. The out-of-the-box queries that BSM provides are necessarily broader than you probably need. You can improve performance by narrowing the scope of the out-of-the-box query so that it pulls only the CIs that you require from the ODB. The resolver tries to identify the most appropriate CI from the ODB by comparing event attributes and event resolver hints with attributes of discovered CIs in the resolver cache. Because no two managed environments are identical, there is no universal resolver definition. Instead, you should try to include only those CIs in your custom resolver cache to which you expect to map events. If you never (or rarely) expect to match other CI types, there is no need to include that CI type in the resolver TQL at all. (For example, if you are only concerned with managing Oracle databases, you should exclude databases of other types).
You modify TQL queries using the ODB Modeling Studio, which provides a graphical representation of the query. You can add or remove information from the query so that it pulls only those CIs from the ODB that you decide are important for your management environment. Generally, the procedure for modifying a query is as follows:
Start the Modeling Studio: Administration > ODB Administration > Modeling StudioUse the ODB online help to familiarize yourself with the features of the Modeling Studio.Download the TQL sample query from HP Software Product Manuals. The sample query is located with the Business Service Manager documentation.
Modify the query to select only the CIs that you need.Use the count button, which shows the CIs and CI types per node, to evaluate if your changes reduce the number of CIs.Rules for Modification
The modification process is not difficult, but it takes some time to understand what to modify to get the results that you expect. You should read the Topology Query Language chapter of the HP Universal CMDB document "Model Management" to get a general introduction to TQL concepts. Especially important are the concepts of containment, cardinality, attributes, and relationships. Then read the rules below to help get an understanding of the factors that may have an influence on how to modify the query.
When selecting a DNS name, use the attribute Primary DNS Name in BSM 9.00.Every CI that is part of a host must have a containment relationship (container_f) to its host. In other words, the containment relationship to a host is required to differentiate between multiple instances of a CI type that may be named identically, or have other identical attributes (for example, "disk drive C:"), but are associated with different parent CIs ("Computers": "C: drive on server1" as opposed to "C: drive on server2").Every host in your TQL query must have one or more of the following attributes enabled:
A host host_dnsname attribute. Make sure that the attribute is enabled. To do so:
- Open the CI Type Manager.
- Select the host CI type, and select the Attributes tab.
- Double-click the host_dnsname attribute.
- Select the Advanced Tab and select the Visible flag.
- Go back to your TQL query and select Node Properties from the host context menu.
- Click Advanced layout settings and enable the host_dnsname attribute again.
One or more ip_address CIs that are related to the host by a contains relationship. Here, enable ip_address and ip_dnsname attributes in your TQL query as follows:All the CI attributes in your TQL query that are needed for CI resolution must be visible (for example, the labels "C:", "Company Portal", and so on). Usually, the name attribute is enough, but sometimes another attribute (such as an ID) is required.Business Services usually are not hosted on a system, so there is no need for a containment relationship. It is sufficient for the services to be a part of the TQL.The hosted on information is crucial for CI resolution. Make sure that host_dnsname and ip_dnsname are visible either for the host or for the ip_address. Without these attributes, the CI Resolver will not work reliably. (QCCR1A109370)Configuration
Workaround: Manually configure your firewall to allow access on port 383. (QCCR1A105814)
Workaround: Ports 1098-1099 must be reserved for BSM in one block, and not individually (specify 1098-1099, not 1098-1098, 1099-1099). Use the instructions in the following Microsoft support article: http://support.microsoft.com/kb/812873 to reserve the ports. (QCCR1I48115)
- Various symptoms occur, including the following: log files fail to be written, events stop appearing the Event Browser, and the log file (%HPBSM%\log\bus\_MessageBroker.log) indicates an out-of-memory exception from Sonic due to a high number of events waiting to be processed by BSM (typically several tens of thousands of events).
Workaround: Prevent this problem by reducing the maximum size of the queue opr_gateway_queue_1:
Content Packs
Workaround: Use HP Data Flow Management discovery for cluster infrastructure. (QCCR1A99688)
Content Packs: Active Directory
- When configuring Dynamic Topology Synchronization on an HP Operations Manager for Windows management server with all domain controllers and their roles discovered, all required CIs are created appropriately. But if you add a new domain controller as a node and discover it using the Smart Plug-in for Active Directory, then only the domain controller CI is created in the ODB. The role CIs are not created.
Workaround: Run the command ovagtrep -publish all on the newly discovered node. This will push all the roles to the ODB. As running this command manually every time is not feasible, you can also create a scheduled task policy that runs the command ovagtrep -publish all once per day, and deploy that policy on all Domain Controllers. (QCCR1A108011)
Content Packs: Exchange
EPI Server
- When uploading a jar file (for example, for use with a custom action), classes which have already been added to the class path will not be loaded from the new jar file. As a result, attempts to instantiate the class in the uploaded jar file will access the previously loaded class. If the classes are identical, no errors will result. However, if the classes are different in any way, unpredictable errors may occur. There is no workaround. (QCCR1A103827)
Event Browser
- It is generally possible to control the Operations Management user interface using keyboard navigation. In some cases, however, a pointing device of some kind is required. For example, when an event is selected in the browser using the keyboard (arrow keys + space) the event details are updated, but the event is not delivered to other portions of the user interface. Other examples include switching between tabs and activating context menus.
Workaround: Use a pointing device when keyboard navigation is not possible or does not function correctly. (QCCR1A4280, QCCR1A109104)
Workaround: Reopen the configuration dialog and directly select the range that you want to use. (QCCR1A108798)
Workaround: Re-open the event on the HP Operations Manager management server where it is owned (QCCR1A109029)
- The search function in the Event Browser does not search the contents of the CI Type column. There is no workaround. (QCCR1A102810)
- When changing the severity of an event or reopening a closed event, the event will be assigned to the operator who made the change. If there are any related events, they are not assigned to that operator, but retain their original assignment:
Workaround: Manually change the assignment of the related events so that they have the same assignment. (QCCR1A108698, QCCR1A108700)
Event Details
Workaround: Select a different event and then the original event to display the annotation. (QCCR1A107300)
Event Forwarding
Workaround: Set the Assigned User of the event to the blank entry and save your changes. Then start the action again. (QCCR1A103514)
Event Processing Pipeline
Workaround: Use opr-close-events.bat to close the events manually (QCCR1A107752)
Event Synchronization
- The Forwarding Rules manager allows the creation of a forwarding rule specifying two target connected servers of type External Event Processing supporting the forwarding type "Synchronize and Transfer Control". Event forwarding to one of the specified servers fails, but it is not possible to determine which one.
Workaround: Do not create forwarding rules with two target servers. (QCCR1A109783)
- For forwarding rules, the Forwarding Rules manager does not display the Forwarding Type for the selected connected servers. In addition, you cannot edit the Connected Server entry unless you first add another connected server to the rule. Only after adding another connected server, do you see the Forwarding Type and can edit the existing entries.
Workaround: To view the Forwarding Type of the target connected servers in a forwarding rule, first ensure you have another Connected Server configured that is not a target of the rule, then edit the rule and add the new connected server. You will now be able to see the rule forwarding types. You can then cancel the edit. (QCCR1A109781)
Event Web Services
previous_user_name = display name
previous_user_display_label = user login name
current_user_name = display name
current_user_display_label = user login name
These values are reversed, and should be:
previous_user_name = user login name
previous_user_display_label = display name
current_user_name = user login name
current_user_display_label = display name
There is no workaround. (QCCR1A109532)
Other
- During CI reconciliation, if there are two or more servers discovered with the same name and same port number, these servers are reconciled in the ODB as a single server with the same name and port number. There is no workaround. (QCCR1A103328)
- If the HP Operations Manager for Windows user name is longer than 20 characters, the user name is truncated and the complete name is not displayed in the Event Browser. This occurs when HPOM for Windows is configured to use UNIX compatibility mode, which truncates the name to accommodate older versions of HPOM for UNIX.
Workaround: Set the compatibility mode to false. Refer to the HPOM for Windows online help for instructions. (QCCR1A96400)
Workaround: Set the locale of the server to any locale other than those listed above to get the original English text. (QCCR1A105849)
Workaround: Locate the CI directly in one of the perspective views and invoke the context menu there. (QCCR1I46408)
ERROR: (sec.cm.client-55) Call to server failed. (sec.core-116) An SSL connection IO error has occurred. This may be due to a network problem or an SSL handshake error. Possible causes for SSL handshake errors are that no certificate is installed, an invalid certificate is installed, or the peer does not trust the initiator's certificate.
Workaround: Use the following procedure to correct the trust relationship:
I. Preparation
Keystore Content
Certificates:
<dps_coreId> (*)
Trusted Certificates:
CA_<omw_coreId>
<dps_coreId> (*) - issued by HP Operations Manager for Windows (check the issuing HPOM for Windows management server with this command: ovcert -certinfo <dps_coreId>)
Keystore Content (OVRG: server)
Certificates:
<dps_coreId> (*)
Trusted Certificates:
CA_< dps_coreId >
<dps_coreId> (*) - issued by the BSM DPS (check the issuing BSM DPS with this command:ovcert -certinfo <dps_coreId> -ovrg server)
Evaluate the core id on the HPOM management server and BSM DPS:
ovcoridExport the trusted CA certificate on the HPOM management server:
ovcert -exporttrusted -file om.trust -alias CA_<om_coreId> -ovrg serverExport the trusted CA certificate on the primary BSM DPS:
ovcert -exporttrusted -file dps.trust -alias CA_<dps_coreId> -ovrg serverExport the certificate issued by the BSM DPS on the primary BSM DPS:
ovcert -exportcert -file dps.cert -alias <dps_coreId> -pass <passphrase> -ovrg serverII. Configuration Steps on the HPOM Management Server
Import the trusted CA certificate issued by the BSM DPS into the client store:
ovcert -importtrusted -file dps.trust -ovrg serverIII. Configuration Steps on the Primary BSM DPS
Set the certificate server property:
ovconfchg -ns sec.cm.client -set CERTIFICATE_SERVER <DPS_FullQualifiedDNSName>Delete the certificate issued by the HPOM management server:
ovcert -remove <dps_coreId>Delete the CA certificate issued by the HPOM management server:
ovcert -remove CA_<om_coreId>Import the CA certificate issued by the BSM DPS:
ovcert -importtrusted -file dps.trustImport the certificate issued by the BSM DPS:
ovcert -importcert -file dps.cert -pass <passphrase>Import the trusted CA certificate issued by the HPOM management server into the client store:
ovcert -importtrusted -file om.trustRestart the Certificate Server:
ovc -restart ovcsOn all Gateway Servers, the Certificate Store on the BSM DPS should now look like this:
ovcert -list
Keystore Content
Certificates:
<dps_coreId> (*)
Trusted Certificates:
CA_< dps_coreId >
CA_<omw_coreId>
<dps_coreId> (*) - issued by the BSM DPS
Keystore Content (OVRG: server)
Certificates:
<dps_coreId> (*)
Trusted Certificates:
CA_< dps_coreId >
CA_<omw_coreId>
<dps_coreId> (*) - issued by the BSM DPS
Verify that the Certificate Server is running using the following command:
ovc
...
ovcs OV Certificate Server SERVER <PID> Running
Listing Pending Certificate Requests should not fail:
ovcm -listpendingVI. Configuration Steps on All Gateway Servers
Update the trust chain:
ovcert -updatetrusted(QCCR1A108975)
Operations Orchestration Flows
- Instructions for uploading Operations Orchestration (OO) Flows available with Operations Management content packs is not included in the BSM documentation. The instructions are as follows:
On the HP Business Service Management system where the content packs have been installed, go to the directory: <HPBSM Root Directory>/conf/opr/ooCopy the required OO jar file to a temporary location on a system where HP OO Studio (version 07.51.02 or greater) is installed. The file names take the following form: HPOprOO<content_name>.jarFor example:
For example:
java -jar "<temp>\HPOprOOMss" -centralPassword <centralpassword>
Using HP OO Studio, the uploaded OO flows are accessed under:
../Library/Operations Management
Admin > Integration > Operations Orchestration
and map the OO flow input variables to CI attributes. (QCCR1A110072)
Topology Synchronization
[main] WARN CmdbAttributeMappingAction.map(135) - The attribute "mount_point" was not mapped because the value was empty. "" for the CI "Logical Disk Drive C:(TYPE:file_system, ID:SI:filesystemcollection:C:@@test.deu.net)"
Workaround: Contact your HP Support engineer for a hotfix (QCCR1A109397)
Required Patches for Smart Plug-Ins
To use content packs with HP Operations Manager (HPOM) Smart Plug-ins, you must install the corresponding Smart Plug-in patches on the HPOM management server that is connected to BSM. The patch numbers are listed in the table below. The patches for HPOM Linux are not yet available. Perodically check the HP Software Support web site for new patches. No patches are required for Smart Plug-ins on Solaris.
Download the patch files from: http://www.hp.com/go/hpsoftwaresupport
End User Management
- A triggered EUM alert with the Include output in alert email option selected in the Run executable file alert action is not logged to the database and is not displayed in the relevant EUM alerts reports. However, the action is executed. (QCCR1I48069)
- The drilldown from the End Users by Action report to the Transaction Management Transaction Tracking report does not work and an Internal error has been received message is displayed. (QCCR1I47982)
- The End Users by Action report is not described in the Using End User Management guide. Documentation for this report will be available in BSM 9.01.
- In the End Users by Action report, the tooltip for the View Transaction Tracking data icon is erroneously labeled View Diagnostics details. (QCCR1I47980)
Business Process Monitor
- When you run a script written in VuGen that uses proxy settings from an automatic configuration script (.pac file) configured in the run-time settings of the script, if one of the proxies in the .pac file is unavailable, replaying the script in either VuGen or Business Process Monitor may result in a high response time and, in some instances, the script may fail due to a timeout. The script can be run in Internet Explorer without this problem, as it ignores the unavailable proxy.
- Business Process Monitor registers with BSM using http://<BSM Gateway Server name>/topaz, and not with HPBAC or MercuryAM at the end of the URL. You must use this format when creating instances for Business Process Monitor.
- Large scripts (larger than 10 MB) cannot be uploaded to the database.
- When running a page component breakdown (from End User Management or Business Process Monitor), the target URL is limited to 144 characters.
Real User Monitor
- In the RUM Session Analyzer report, any end user that does not belong to a configured end-user subgroup (that is, an end-user subgroup that exists in the ODB) is displayed as part of an end-user subgroup called Others. (QCCR1I45317)
- When Business Service Management is working with SSL and requires client-side certificate, Real User Monitor session replay will not work
System Availability Management and SiteScope
- The Monitor Deployment Wizard only supports topology reporting for monitors that have a default topology defined. This means you can select to add a template to a CI only if the CI type is the default CI type for all the monitors in the template. (QCCR1I39697)
- The Link Monitor to CI Settings pane is not supported in Business Service Management 9.00 or later and was removed from Business Service Management's System Availability Management Administration page. To use this functionality, upgrade to SiteScope 11.00 or later, and use the report custom topology feature in HP Integration Settings > BSM Integration Data and Topology Settings in the monitor properties.
- After JBoss Application Server recovers from a server crash, the information in the right pane of the Summary tab in SAM Administration does not show any data until BSM is restarted. (QCCR1I44570)
- When SiteScope 10.x is connected to BSM 9.00 and Hosts-Software Elements topology is used in the event flow, if the monitored CI is Node (and not running software), no health indicator or KPI is assigned to the EMS monitor or to the node it monitors. (QCCR1I39918)
- When SiteScope 10.00 is connected to BSM 9.00, topology data is not reported to BSM.
Workaround: Contact customer support for a workaround to be supplied on top of SiteScope 10.00, or upgrade your version of SiteScope to 10.10 or later. (QCCR1I47810)
- If a SiteScope is restarted while being accessed in System Availability Management Administration, you may receive an error and have to renavigate to the SiteScope to properly access the SiteScope server.
- If you are copying from a SiteScope version 10.00 to another SiteScope version 10.00 using the copy/paste functionality in System Availability Management Administration, there may be a delay of up to a minute until the pasted object appears in the target SiteScope. This is because the monitor tree in the new SiteScope user interface refreshes by default five seconds after a paste operation completes. If the paste operation takes longer than 5 seconds, it will miss this automatic refresh and the pasted objects appear only after the regularly scheduled refresh (by default 60 seconds).
- In System Availability Management Administration, when copying objects from one SiteScope to another, there is no dependency check. This means that you can copy an object that depends on another object to a different SiteScope, even though the object on which it depends does not exist on the target SiteScope.
- In System Availability Management Administration, when the SiteScope service is down, instead of receiving an error to this effect, you will see a Page cannot be displayed error.
- If a SiteScope is being reset when BSM is not running, the SiteScope will appear as registered with a configurable profile in System Availability Management Administration once BSM is running again. The SiteScope must be reset when BSM is running.
- On the New Monitor page, the Recently Used Monitors list is not saved when you exit System Availability Management Administration.
- When creating a SiteScope profile in System Availability Management Administration, if you change the profile display name after having received any error during the profile creation process, the default profile name is not changed accordingly. Ensure that the profile name and SiteScope agent machine location fields contain the desired values.
- In System Availability Management Administration, there is no notification for successful actions in the user interface.
- SiteScope: In SiteScope, Solution Templates can only be deployed from the template tree.
- SiteScope: Refer to the SiteScope release notes for all SiteScope limitations.
- SiteScope: SiteScope documentation is available only as a standalone help system. It is no longer a part of the BSM Documentation Library.
Transaction Management/TransactionVision
- Customers installing TransactionVision directly from the BSM DVD set should note that the shared Diagnostics/TransactionVision Java Agent and .NET Agent install packages can only be found on the Diagnostics DVD, as they are not included on the TransactionVision DVD. All other TransactionVision specific Agents are included on the TransactionVision DVD.
- The default data collection filter section is incorrect in the Using Transaction Management Guide. The corrected section appears below.
The Default Filter
If no data collection filter is specified, then the default filter is used. This filter can be customized but has the following initial settings:
For WebSphere MQ: Only MQGET, MQPUT, and MQPUT1 API names are included. Do not send browsing MQGET is set.
For JMS: send, receive, receiveNoWait, publish, and onMessage methods are included.
For Servlet: only the first 1024 bytes of HTTP request and response data are included.
The JDBC technology is off.
For all technologies: event packaging is enabled and the number of events to package is set to 10 events.
- Customers using the TransactionVision WMQ CICS Agent for z/OS need to relink module SLDPXADM as serially reusable instead of re-entrant in order to avoid an ASRA at location +x23C within module SLDPXADM, part of the WMQ CICS Administrative UI component . The following JCL can be used for this purpose:
//LKEDREPL EXEC PGM=HEWLH096,REGION=0M
//*
//* Please make a copy of SLDPXADM before executing
//*
//SYSLIB DD DSN=custHLQ.SSLDLOAD,DISP=SHR
//SYSLMOD DD DSN=custHLQ.SSLDLOAD,DISP=SHR
//SYSPRINT DD SYSOUT=*
//*
//SYSLIN DD DDNAME=SYSIN
//SYSIN DD *
INCLUDE SYSLIB(SLDPXADM)
SETOPT PARM(REUS=SERIAL)
NAME SLDPXADM(R)
/*
(CR QCCR1I47728)
Workaround: Either click the Refresh button on the main configuration tree or re-login to BSM. (QCCR1I47915)
- The SQL Alerts custom job is not supported in this release. References to this feature in the documentation should be ignored. For example, the SQL job bean example shown in the TransactionVision Advanced Customization Guide will not work. (QCCR1I47859)
- If the HP Business Service Management Servers are using an SSL configuration with client authentication, manual configuration of the TransactionVision Processing Servers is required as follows.
Set javax.net.ssl.keyStore and javax.net.ssl.keyStorePassword properties by un-commenting and optionally updating (if not using default <TVISION_HOME>/jre/lib/security/cacerts as a keystore) the SSL_PROPERTIES variable in the <TVISION_HOME>/bin/set_env script on each TransactionVision Processing Server host. For example, below is the un-commented SSL_PROPERTIES variable in the unix set_env.sh script.
SSL_PROPERTIES=-Djavax.net.ssl.keyStore=$TVISION_HOME/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.keyStoreType=JKS
After modifying the file, restart all processing server components by using the SupervisorStop and SupervisorStart scripts. (QCCR1I45864)
- The Transaction Tracing Rules Configuration page and Rule Creation wizard have an advanced parameters area. The "Attribute evaluation occurs within classify section" option on in this area is working incorrectly. Setting this should include the rule in the classify section, and vice versa, but it does not.
Workaround: Use the opposite settings: To include a rule in the classify section, set the option to off. Conversely, to put a rule outside classify section, set the option to On. (QCCR1I47857)
Workaround: Customer could start multiple TVISION Manager components, one for just the WMQ-BATCH agent, and the other for all other types of agents. This would allow the WMQ-Batch agent to be brought down gracefully, by issuing a stop command to its TVISION Manager independent of the other TVISION Manager and its agents. (QCCR1I47690)
- A known issue exists for the TransactionVision product where the current license capacity "used" value is incorrectly displayed in the Capacity Details section of the License Management report. (QCCR1I47012)
- If the TransactionVision content pack is deployed, duplicate entries might be observed in Admin>Service Health>Repositories, such as duplicate rules, context menus and actions. (QCCR1I47660)
- There is very limited support for the new WebSphere MQ 7.0 Publish/Subscribe feature. As part of this limitation, MQPUT and MQGET API using topics will not be correlated. (QCCR1I45059)
- You may see two EJB or servlet nodes in the Component Topology or Instance topology view that only differ in application server name. For example, one with a short name such as "server1" and the other with a long name such as "cell1,node1,server1". This is the result of some events that do not have full application server information. (QCCR1I47198)
- The User Reports feature available in TransactionVision 8.0 is not available in 9.00. (QCCR1I41146)
- Some of the "Correlation Measurement" metrics in the Transaction Over Time report's filter may not be applicable for Diagnostic Transactions. (QCCR1I47941)
- A "Drill to Transaction Tracking Report" button will be enabled in the Transaction Over Time report even though there is no TransactionVision data present. This button should be disabled. (QCCR1I47940)
- In the Processing Server Configuration section of the Admin UI, the Sync Interval field does not display the units of the field, which are in minutes. (QCCR1I42973)
- The Java Agent will continue to collect events even after Configuration Messages have expired or the Analyzer, SonicMQ or the TV database are not accessible. (QCCR1I47532)
- Host consolidation in ODB is mismatched with respect to z/OS host names. In order for proper host consolidation in ODB, the hostnames provided by TV events from z/OS agents need to be fully qualified domain names. (QCCR1I41816)
- Functionality of the TransactionVision WMQ CICS Agent Version 9.00 is adversely affected by IBM APAR PK70901 for IBM CICS Transaction Server V3.2. Please check the maintenance level of your CICSTS32 system to see if APAR PK70901 has been applied. If so, please contact Hewlett Packard Technical Support for further assistance before enabling the WMQ CICS Agent V9.00 within your CICSTS32 environment(s). (QCCR1I38314)
- If modifying default Time Slice Delta and/or Sample Delta settings in the "BSM Aggregate TV Data Sample" job, the Collection Interval and Aggregation Delta settings in CIs need to be set to the same value respectively. This is required for proper functioning of CI status display in BSM Service Health. (QCCR1I48216)
- The TransactionVision Advanced Customization Guide is not fully updated with respect to the new 9.00 TransactionVision APIs. Please check for an update to this manual on the HP Software Product Manuals site.
- The following drilldowns from TransactionVisions reports to End User Management reports do not work, and a No data was found error is displayed:
- When running TransactionVision components together with Business Service Management and/or Business Process Insight and/or Diagnostics, all software versions must be the same - for example if running Transaction Management from Business Service Management 9.00, installed TransactionVision components must be version 9.00, Business Process Insight (if installed) must be 9.00, and Diagnostics (if installed) must be 9.00.
- On WebLogic application server platforms, in rare scenarios, it is possible that some transactions have abnormal transaction duration time due to the JMS API acknowledge calls that take many minutes to complete. Solution: Change the Data Collection filter of your Communication Links to filter out these JMS acknowledge events.
- The following information applies to customers installing TV 9.0x agents on z/OS that do not have either CICS or IMS installed on the target z/OS system.
In general, the intent of this modification is to create and make available dummy interface modules for IMS and/or CICS by assembling and linking them into the TransactionVision SSLDLOAD library and then make all references to the SDFHLOAD (CICS) or SDFSRESL (IMS) libraries refer to the TV SSLDLOAD library.
Select one of the following dependent on the type of install.
SMP/E Installation:
Within installation JCL member SLDDDDEF, adjust the %cicshlq and %imshlq substitution values and suffix constants .SDFHLOAD and .SDFSRESL respectively, replacing these values and constants as necessary to generate the dataset name produced by the concatenation %tvhlq..SSLDLOAD.Immediately preceding the execution of JCL member SLDDDDEF, execute JCL members DUMYCICS and DUMYIMS as needed (if for example CICS is installed, but IMS is not, then only execute DUMYIMS). Load modules output from either of the DUMY* jobs need to target the library %tvhlq..SSLDLOAD. Also, if DUMYIMS is being used, please insert the following two lines immediately after the line starting with '//L.SYSLMOD DD '://L.SYSIN DD *
ALIAS DFSLI000Non-SMP/E Installation:
Within installation JCL member SLDINSTL, after the DEFINE step, insert JCL members DUMYIMS and DUMYCICS as needed (if for example CICS is installed, but IMS is not, then only insert DUMYIMS). Tailor the DUMY* JCL member(s) to output load modules targeting library %tvhlq..SSLDLOAD. Also, if DUMYIMS is being used, please insert the following two lines immediately after the line starting with '//L.SYSLMOD DD '://L.SYSIN DD *
ALIAS DFSLI000
Within installation JCL member SLDINSTL, after the DEFINE step, insert JCL members DUMYIMS and DUMYCICS as needed (if for example CICS is installed, but IMS is not, then only insert DUMYIMS). Tailor the inserted JCL to output load modules to target library %tvhlq..SDFHLOAD.Tailor SLDINSTL replacing references to %cicshlq and %imshlq substitution values and suffix constants .SDFHLOAD and .SDFSRESL respectively, replacing these values and constants as necessary to generate the dataset name produced by the concatenation %tvhlq..SSLDLOAD.Execute JCL member SLDINSTL.Repeat the above steps when performing non-SMP/E installation of the SLM product code, tailoring SLMINSTL, and substituting SLM for SLD as necessary.
- Java Agent installation and Setup Module response files generated with version 8.00 cannot be used to perform a silent installation of the 9.0x version of the Java Agent installation and Setup Module. Response files generated with 8.01 and later will work with 9.0x releases.
- On Solaris hosts, the TransactionVision Processing Server may fail to start upon installation. This occurs when this component is installed by a root user and Business Service Management was started under another user/group on the same host. Therefore the Business Service Management nanny process does not have permission to execute the TransactionVision components.
Workaround: Change the user/group of the /opt/HP/TransactionVision directory to the same as that being used by Business Service Management by using the following commands: chown -R <bsmuser> /opt/HP/TransactionVision and chgrp -R <bsmgroup> /opt/HP/TransactionVision (where <bsmuser> and <bsmgroup> are the user/group of the Business Service Management installation directory). Alternatively, you can grant write permissions for all users/groups to the TransactionVision directory by using the command: chmod -R a+w /opt/HP/TransactionVision, but this alternative would open up read/write access for the TransactionVision installation files to all users and may pose a security risk.
- The TransactionVision Processing Server is installed under /opt/HP/TransactionVision on Solaris and RedHat Enterprise Linux, and under /usr/lpp/HP/TransactionVision on AIX. While it is not possible to change the installation path, it is possible to create soft-links to ensure that the product files are placed on a drive or partition with available space. Under normal circumstances, customers may create a soft-link from /opt/HP/TransactionVision or /usr/lpp/HP/TransactionVision to a new location prior to running the tvinstall_900_unix.sh installation script. However, due to a limitation in the SonicMQ installation with respect to soft-links, the SonicMQ files must be installed under the default /opt/HP/TransactionVision/Sonic or /usr/lpp/HP/TransactionVision/Sonic directory. If space is a concern, customers may still create soft-links for other higher capacity directories (such as jre, jre64, java, docs, and logs) under the TransactionVision installation directory.
- On AIX systems, after the Java Agent installation, the following message will appear:
The Installation Wizard has successfully installed HP Diagnostics/TransactionVision Agent for Java. Choose next to continue the wizard.
However, on some systems, the following warning is also generated: o null.
In this case, the installation has succeeded and the message can be ignored.
- When starting HP Business Service Management on Solaris systems using the "run_topaz start" command, "Bad String" errors may be seen if the LANG environment variable is not set properly. These errors can be eliminated by setting LANG to the proper locale prior to starting BSM. For example, run the command "export LANG=en_US.UTF-8" to set LANG for U.S. English.
- Customers who plan to enable the TransactionVision IMS sensor on z/OS should ensure that they are not already using the IMS OTMA Input/Output exit (DFSYIOE0) for some other non-TransactionVision purpose before proceeding with the IMS sensor configuration. If DFSYIOE0 is already being used for customer internal purposes or by another vendor product, please contact TransactionVision customer support for detailed instructions on how to modify DFSYIOE0 source code to invoke the TransactionVision IMS sensor (SLMYIOE0).
- Starting with z/OS version 1.9, the default setting for system parmlib DIAGnn member statement VSM ALLOWUSERKEYCSA has changed to "NO." This parameter disallows User Key CSA storage for security reasons. In order for TransactionVision 9.0x Agents to execute successfully under z/OS, the VSM ALLOWUSERKEYCSA parameter value must be set to "YES."
- When using the Diagnostics/TransactionVision Agent to monitor WebLogic 9.2.2 and 9.2.3 on Linux, the following error may be seen due to a problem with the version of the JVM shipped with that version of WebLogic, which causes the server to not start:
<Dec 3, 2008 5:41:17 PM PST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.t3.srvr.SubsystemRequest.action(SubsystemRequest.java:79)
at weblogic.t3.srvr.SubsystemRequest.start(SubsystemRequest.java:51)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:372)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:125)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:630)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:402)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:67)
To work around this problem, the following steps should be performed:
<ClassName name="weblogic.management.configuration.DomainMBeanImpl">
<Action name="ForwardMethodCall">
<SensorFlagName name="com.bristol.tvision.sensor.CheckSensor.servletSensorInstalled"/>
<SensorClass name="com.bristol.tvision.sensor.servlet.ServletSensor"/>
<SensorMethodPrefix name="DomainMBeanImpl_"/>
<MethodSignature name="void setName(java.lang.String)"/>
</Action>
</ClassName>
; com.hp.j2ee.domain.name=your_weblogic_domain_name
Note that the WebLogic domain name is usually the directory containing your server.
Business Process Insight
- BPI does not support Oracle 11g RAC. (QCCR1I33021)
- When creating a Business Process Model in the Modeler, the Process Definition Name and the Data Definition Name cannot be identical. Be sure that the Data Definition Name string is different from the Process Definition Name for all Business Processes.
Workaround: Change the Data Definition Name using the Modeler if necessary. (QCCR1I48053)
Workaround: Once this problem is encountered, click on the Reports tab and reselect the report from the menu. The next drill-down will work correctly. (QCCR1I47654)
- In the BPI Monitors Over Time and Business Activity Over Time report, the CI filter (BPI Monitors or Activities) displays a non-existent CI named Error at the bottom of the tree with icon_n instead of an icon. This CI should not be present, and can be ignored by the user. (QCCR1I47653)
- If the BPI content pack is deployed, duplicate entries might be observed in Admin > Service Health > Repositories, such as duplicate rules, context menus and actions in repositories. (QCCR1I47659)
- The Business Health tab in the Health page displays a gauge for all KPIs that have configured objectives. Any KPIs that contain multiple related Health Indicators, however, will not be displayed.
Workaround: Create a unique KPI for each Health Indicator. (QCCR1I38672)
- In the Monitor Over Time report, a Filter Validation Error occurs if you did the following: 1) opened the Monitor Over Time report immediately before you created a monitor, 2) navigated directly to BPI > Admin > Monitor Definer and added a monitor, and 3) navigated back to BPI Applications through the application menu Application > Business Process Insight, which reopens the Monitor Over Time report and the Filter Validation error.
Workaround: If you go out of the Monitor Over Time report by navigating to another report, or to the site map, and then reopen the Monitor Over Time report, the error is resolved. (QCCR1I47399)
Workaround: Close all open browsers and reopen the BSM user interface. (QCCR1I34412)
Workaround: Define the same Group property for both the Business Process and Business Process Monitor to see the group breakdown in the landing pages. (QCCR1I35230)
- When launching the BPI Modeler, you may see any of the following security warning messages, which can safely be ignored:
The application's digital signature cannot be verified.Part of the application is missing a digital signature. Only run if you trust the origin of the application.And after clicking on More Information,
Although the application has a digital signature, the application's associated file (JNLP) does not have one. (QCCR1I38624)- On the BPI Health page, when you specify a non-default process grouping (other than All), the list in the Business Health tab at the bottom of the BPI Health page includes both the Business Process Monitors that match the grouping criteria and the Business Process Monitors that have no Process Definition Group Property specified.
Workaround: If you want to segregate all Business Process Monitors by groups, then designate a group value for each of the Business Process Monitors when you create or update the Business Process Monitors in the Monitor Definer. (QCCR1I35229)
Workaround: Use up to a maximum of 16 characters for the BPI Instance database name and the user name. (QCCR1I41558)
Workaround: Open the Process/Activity filter, and remove all but one selection. (QCCR1I47394)
Workaround: Remove the Business Process Diagram component from the page and add it back in from the Component Gallery. (QCCR1I47606)
Workaround: Re-create a Business Process model with no Data definitions. (QCCR1I45844)
- When installing the BPI instance database on an Oracle database where pre-existing BPI tables exist (from a previous BPI installation where the Keep BPI data option was selected during the previous version uninstall), errors may occur if the database setup is conducted by a non-admin Oracle database user.
Workaround: When installing BPI against an Oracle database where legacy BPI database data has been retained from a previous installation, perform the BPI Instance database setup on the Oracle database as the Admin Oracle database user. (QCCR1I42012)
Workaround: Grant each user the SystemViewer role in addition to BPIUser or BPIRestrictedUser. Without the SystemViewer role, filtering can only be done in the reports by doing drill downs from the Business Process Summary report. (QCCR1I48215)
Workaround: Grant the user with the BPIAdministrator role the additional roles of BPIUser and SystemViewer. (QCCR1I48256)
- Instance violation counts are always zero on the Health page. The Business Health tab in the lower- right pane of the BPI Health page shows how many BPI monitor threshold violations there have been within the most recent sample period. The sample period corresponds to the period at which data samples are sent to BSM. If the sample period is too short, or the clocks are not synchronized between the database and BPI Server hosts, the violation counts may always be zero. If the violation counts on the BPI Health page remain zero when you expect there to be violations, check the following:
- Deadline thresholds for Business Process monitors cannot be calculated if the name of the deadline property has greater than ten characters and the BPI Instance Database is on an Oracle server.
An error can occur when calculating the deadline or status for deadline thresholds on Business Process monitors if the BPI Instance Database is on an Oracle server. This error appears in one of two ways:
WARNING: Monitor generation failed for... ORA-00972: identifier is too long: ...
WARNING: Monitor generation failed for... ORA-00904: ... invalid identifier...
Workaround: Change the name of the deadline property to 10 or fewer characters.
Unlike other monitors, those with a type of Absolute Duration raise violations before an instance has completed. When there is a combination of a short absolute threshold duration and the event which completes the instance is constantly delayed, violations are incorrectly raised for every instance. For example, a combination of a critical threshold of 30 seconds and a latency of five minutes for the end events cause a violation.
Workaround: Disable the violation detection for instance duration monitors that have yet to complete. This is achieved by altering the relevant stored procedures (METRIC_THRESH_ACTIV_INSTS_OVER and METRIC_THRESH_ACTIVE_OVERDUE) to not match on active instances:
For MS SQL, this can be done by doing the following:
Run Microsoft SQL Server Management Studio (or equivalent).Connect to the BPI Instance database (default is hpbpischema).Navigate to the Stored Procedures (for example, Programmability > Stored Procedures).Select the stored procedure called METRIC_THRESH_ACTIV_INSTS_OVER.Select Modify (or equivalent) to modify the stored procedure.Replace Active with Never in the stored procedure.Click Execute on the toolbar (or equivalent) to apply the change.For Oracle, this can be done by doing the following:
Run Oracle Enterprise Manager (or equivalent) and connect to the BPI Instance database.Navigate to the Stored Procedures section (for example, Administration >Procedures) and display the list of stored procedures for the BPI schema.Select the stored procedure called METRIC_THRESH_ACTIV_INSTS_OVER.Select Edit (or equivalent) to modify the stored procedure.Replace Active with Never in the stored procedure.Click Apply (or equivalent) to apply the change.Note: The caveat to the above workaround is that if there are process instances experiencing issues, the absolute duration violations will not be triggered until after the monitor scope for the process instances is complete. Therefore, the absolute duration violations may not be triggered if the active process instances are blocked on a particular Activity within the Business Monitor span and none complete the monitor scope. This workaround should only be used if the implications of this are acceptable.
- The processing and display of Business Process Insight monitor instance values is only done to a precision of 6 or 7 digits, and not to the precision of 15 digits used for process values. This can mean that large integer values may not show their exact value. For example, $123,000,000 could show as $123,000,064.
- Business Process Insight Landing pages are not displaying monitor values and statistics to double precision.
- Business Process Insight instance pages fail when first accessed in a multi-domain LWSSO configuration.
Workaround: Access the Process Repository Explorer under the Business Process Insight Admin area in Business Service Management (Admin->Business Process Insight->Process Repository Explorer). After doing this, the process instance pages can be accessed normally.
If you start Business Process Insight while TransactionVision's JMS Event Queue services for sending events to Business Process Insight are unavailable, or if the JMS Event Queue services become unavailable once Business Process Insight has started, the OVBPIJmsEventHandler Service stops. To solve this problem, you need to configure the Windows Service for the OVBPIJmsEventHandler Service under Control Panel > Administrative Tools > Services. You should configure the service in the same way as is described for adapter Windows Services in the Integration Training Guide - Business Events, by selecting the Recovery option and setting each of the First, Second and Subsequent Failures to the value of Restart the Service.
If you intend to modify the Servlet Engine (Tomcat) configuration files, you need to be aware that changes made directly to the Servlet Engine files are overwritten by Business Process Insight configuration files. Refer to the Business Process Insight Server Administration Guide for more details.
If you see an error indicating that one or more Business Process Insight Infrastructure settings is missing, make sure that you have specified a value for the Microsoft SQL Server database name:
Instance Database Settings: Database Name.
You need to provide a value for this setting even if you are configuring the settings for an Oracle database. It can be any string, but you cannot leave the field blank; if you do, you receive an error when accessing the Business Process Insight Application pages.
Very occasionally, following a system restart, the Servlet Engine appears not to have started, both within the Business Process Insight 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.
If you think that you are experiencing this problem:
If you receive an error message indicating that the Business Process Insight Server is unable to contact the RMI Registry on port 44,000, this is likely to be due to a port number clash.
The Business Process Insight 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:
Select the Port Numbers tab from the Business Process Insight Server Administration Console to change the RMI Registry port number from 44,000. If you change the value for the port number, you need to make sure that any other configuration affected by this change is also modified, for example, the Business Process Insight Infrastructure settings.
The following scenario results in a Process definition that cannot be progressed:
One of the Process definitions is now linked to the newly created Data definition and no changes are made to the progression rules. In this case, the Business Process Insight Modeler should detect that the progression rules are referencing a different Data definition, but it does not and as a result, no process instances are created.
To resolve this problem, use the Export and Import options within the Business Process Insight Modeler to make a copy of a Process definition. Use the option to rename the definitions (not overwrite them).
See "How to Manage the BPI Modeler" in the Using Business Process Insight guide for details of making copies of your Process definitions.
When entering property values for subscriptions within the Business Process Insight 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 ("").
If you see an error message similar to the following when importing a Process definition into the Business Process Insight Modeler, it is possible that you are attempting to import a Process definition with a name that contains characters that are locale-specific:
The file proc-defn-name.zip is not a valid import file. Please see the log file for more information.
where proc-defn-name is the filename, based on the Process 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 Business Process Insight 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 processes, the zip archive file name is based on the Process definition name. Therefore, if you want to export a Process 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 Process 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 Process definitions.
If you modify the locale for a system where the Business Process Insight Server is installed, you might find that you cannot start the Business Process Insight 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 Business Process Insight 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 Business Process Insight is installed and you are experiencing this problem, you need to:
If you attempt to run the Business Process Insight 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 installation software.
In order to complete the installation successfully, you need to temporarily set the locale to a United States locale. When you have completed the installation, you can reset the locale to Turkish.
If you enter non-ASCII characters for the Oracle database data directory during the Business Process Insight 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 Business Process Insight 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) Business Process Insight into the same location, this time using a database data directory name that contains only ASCII characters.
If you are using Microsoft SQL Server 2005 and you are aware that you are having problems with database checkpoint I/O requests, you are experiencing a known problem with SQL Server 2005. The problem has been fixed by Microsoft and has the following Microsoft defect number: 50000708.
Microsoft provided a solution for this problem in their Service Pack 2 for SQL Server 2005. You need to make sure that you have installed Service Pack 2. Microsoft also recommends that you use the -k3 startup parameter to limit the I/O requests generated by the checkpoint process. Refer the defect text provided by Microsoft, or the Microsoft documentation for details of using startup parameters.
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 Business Process Insight 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 a Business Process Insight Server, delete the Business Process Insight files under the Business Process Insight installation directory.Modify the Zerog Global Registry (an InstallAnywhere file):If the registry file contains only entries for the product that you are attempting to uninstall, 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 Business Process Insight, edit the file to remove the following entries:
The product elements for Business Process Insight. Make sure the element references the directory where the files are located that you want to uninstall.The components elements for Business Process Insight. Make sure the component element references the directory where the files are located that you want to uninstall.Application Management for SAP
ODB
Modeling and Application
- On all ODB pages, there is a Help link in the lower menu (below the tabs) in addition to the Help link in the main menu at the top of the screen. The lower Help link opens documentation for a different product and should not be used. Additionally, the Help buttons in all ODB dialog boxes open incorrect documentation pages.
Workaround: Open the BSM Help from the upper menu and navigate to the page for the relevant dialog box.
- When creating an instance based model in the Modeling Studio, an error is generated if you try to add related CIs before saving the model. You should create the model, save it, and then add the related CIs.
- In the Modeling Studio, when you select View in the Main menu and try to hide one of the tabs in the Left pane (Resources, CI Selector, or CI Types), all of the tabs are hidden.
- In Modeling Studio, the Changed during or Unchanged during operators for date attributes are supported only if you change the query to ACTIVE. By default, once these operators are added, the query is automatically set to NOT ACTIVE. (Note: Even though these types of Correlation rules are upgraded, they are not functional.)
- In IT Universe Manager, when you try to create an empty model CI (a CI of type Business Service or CI Collection), an error is generated.
- When working with federated CITs in the Modeling Studio, the Add Related Query Node wizard does not identify CITs with instances. If the Show only CITs with instances check box is selected, no tree is displayed. If you clear the Show only CITs with instances check box, a CIT tree is displayed with zero instances showing for all CITs, even though there may be instances for some CITs.
- The Get Related CIs Report in IT Universe Manager is not available in version 9.01. To work around this limitation, export the results of the related CIs in text mode.
- In IT Universe Manager, the Export Data to File option does not work in Text mode for CSV, Excel, or XML reports from the View Results tab. You can export data to a PDF file from there. In the Related in View and Related in DB tabs, all the export options work.
- In the CI Lifecycle module, the Filter option is not supported and the Clear Filter button is not active.
- The Direct Links functionality to a perspective-based view is not supported.
- When deleting a template in the Modeling Studio, there is no option to detach the dependent views from the template.
- When deleting a template in the Modeling Studio, the TQL query on which it is based is not automatically deleted.
- When deleting a perspective in the Modeling Studio, there is no option to detach the dependent views from the perspective.
- When deleting a perspective-based view in the Modeling Studio, the TQL query on which it is based is not deleted.
- The View Snapshot and View Statistics functionality is missing in the View Change report.
- When accessing the ODB through the IIS Web server, the UCMDB JMX Console cannot be accessed through the IIS Server URL. You must access the UCMDB JMX Console directly using the following URL: http://<server_name>:21212/jmx-console, where <server_name> is the name of the machine on which HP Business Service Management is installed.
- In the Query Node Grouping dialog box in the Modeling Studio, the Minimum in Group field is replaced by the Expression capture group index field, which is used to indicate which portion of the regular expression is relevant for the grouping. Enter 0 to indicate that the entire expression is relevant.
- To designate a view as a hidden view that does not appear in IT Universe Manager, define a bundle for hidden views, as follows:
In the Infrastructure Settings Manager, select Hidden Bundles Names in CI Selector.Enter the name of the new bundle as the default value and save the setting.In the Modeling Studio, open the relevant view and click View Definition Properties in the toolbar.In the View Definition Properties dialog box, select the hidden views bundle and assign the view to it.- When you update an adapter package, use Notepad++ rather than Notepad to edit the template files. This prevents the use of special symbols, which cause the deployment of the prepared package to fail.
- Changing an integration TQL can result in data loss. To avoid data loss:
- Before making changes to a TQL, run diff replication. This step is needed to avoid losing removed data when running a full replication (the next step).
- After making changes to a TQL, run full replication. This step is needed to retrieve all the data for a second time, to differentiate between new data (that must be retrieved) and existing data (that does not need to be retrieved).
- The ODB in BSM 9.00 uses an applet that is run by a JRE. The supported JRE versions are 6u11 and later (6u20 recommended).
- After finding the relevant CI in the CMDB Search, the context menu on the left-hand side is synchronized only after selection.
- If you run get result count over a TQL with an invisible multiple data store element, the count for the element will not include the CMDB objects satisfying the query for that element. If you have a view based on such a TQL, you will not be able to run discovery based on this view (via IT Universe Manager > View Browser > Show Discovery Status and Changes of View) if the view's result contains data only from the CMDB in the multiple data store node, and no objects in the view's other nodes.
- Only an integration user can connect to the ODB through the UCMDB Java API set. A connection attempt by other types of users may cause errors, even when using LDAP verification.x
Data Flow Management
- If Discovery fails during Shell-based jobs execution with error message "Failed to create System32 junction point" it usually means that the junction point already exists and system doesn't allow to re-create it. In order to resolve this issue, user needs to log-in to destination machine and remove the junction point by running the command: rmdir %SystemDrive%\Data Flow Management_link_system32
Note: The command should be rmdir and not del or deltree, as otherwise Windows system32 folder will be deleted. (QCCR1H27867)
- Enable SSL Between BSM Server and the Data Flow Probe with Mutual Authentication: In version 9.01, this functionality is not supported, but will be added in a future release.Instead, you should use basic authentication. For details, see "Enable SSL on the Data Flow Probe with Basic Authentication" in the ODB Data Flow Management Guide .
- When a Probe Gateway works with two Probe Managers, the request to receive the communication log from the system sometimes fails. Instead, you can retrieve the log file from the relevant Probe Manager file system.
- When running the J2EE or Database wizard, you cannot upload jar files from the Wizard to the Probe. You must manually copy the files to the Probe file system and restart the Probe.
- If the Data Flow Probe's My SQL database shuts down or encounters an error, the Probe may appear to be disconnected. Restore the My SQL database then restart the Data Flow Probe.
- Fail entire bulks due to invalid CIs. If a set of objects (for example, 1,000 objects) includes even one invalid CI (for example, a node cannot be identified because of missing topological information), the reconciliation engine drops the entire set and does not send it to the ODB. This is the default behavior.
Clear the check box to have the results sent to the ODB with only the invalid CIs (and their topology) dropped from the results. In the above example, 999 objects would be processed. BSM displays an error message when you view the results.To access this check box: Data Flow Management > Packages > <package name> > select a specific adapter in the Resources pane > click the Adapter Management tab. This check box is the opposite of the Boolean value of the ignoreMissingReconciliationRules parameter.- Version 9.01 includes a new purging mechanism for managing old Discovery result statistics. This mechanism enables faster display of the discovery results statuses. That is, the old statistics records are merged and therefore they are still available for the user. The new feature is controlled by two system parameters:
appilog.collectors.ResetDiscoveryStatisticsIntervalHours.name=Reset Discovery Statistics Interval by Hours. This property defines the interval of merging discovery statistics (the interval for running the purging mechanism).appilog.collectors.DiscoveryStatisticsArchiveDays.name=Discovery results statistics archive period. This property defines the number of days after which results statistics are being archived (the number of days after which the statistics are considered old).Integration
- The status of a population job can be displayed as Running even though the job is not displayed.
- If CIs are merged or deleted during population from another ODB, reconciliation data cannot be received for those CIs and a population job containing those CIs may fail. Rerun the job to work around the issue.
- You cannot edit the values of attributes that are configured to be retrieved from both an external data repository and ODB during federation.
- When defining a new integration point in Integration Studio, if the name contains illegal characters (for example, a period), an error message is displayed and the information in the Create New Integration Point dialog box is lost.
- The link to a federated CI in an exported report fails to return the user to ODB.
- A node is sometimes created without either an IP_ADDRESS or INTERFACE property.
- Service Manager 7.1x adapter is now called the Service Manager 7.1x-9.2x adapter, since integrations with Service Manager 7.2 and later can be performed.
- The Federation Tab of the Integration Studio displays only those CI Types and attributes that can be federated from the selected data repository.
- Automatic completion of reconciliation data:
Integration Users
Discovery and Integration Content
- The document ODBDataFlowContent.pdf, included with BSM 9.00, is not a complete and up-to-date version of this document. For details on working with DFM content, see the HP Universal CMDB Discovery and Integration Content Guide PDF. This book is available on the HP Software Product Manuals Web site (http://h20230.www2.hp.com/selfsolve/manuals) under the Universal CMDB (Application Mapping) product.
- If Discovery fails during Shell-based jobs execution with error message "Failed to create System32 junction point" it usually means that the junction point already exists and system doesn't allow to re-create it. In order to resolve this issue, user needs to log-in to destination machine and remove the junction point by running the command: rmdir %SystemDrive%\ddm_link_system32
Note: The command should be rmdir and not del or deltree, as otherwise Windows system32 folder will be deleted. (QCCR1H27867)
- Previously-discovered Layer 2 topology is not upgraded to version 9.01, so you must rediscover this topology. You can either delete existing Layer 2 links manually or rely on the aging mechanism to delete them.
- Siebel discovery. If the Data Flow Probe is installed on a 64-bit machine on a Windows platform, place the ntdll.dll, MSVCR70.DLL, and msvcp70.dll drivers together with the Siebel drivers in the Siebel driver folder on the Probe machine. You enter details of this folder in the Siebel set of credentials (Path to Siebel Client). For details, the ODB Data Flow Management Guide. These drivers usually exist on a 32-bit machine and can be copied to the 64-bit machine.
- SAP discovery. If the Data Flow Probe is installed on a 64-bit machine on a Windows platform, place the standard librfc32.dll and sapjcorfc.dll drivers under the Windows installation folder (for example, C:\windows\SysWOW\). Place the msvcp71.dll and msvcr71.dll drivers under the Probe installation directory: C:\hp\UCMDB\DataFlowProbe\content\dll\. These drivers usually exist on a 32-bit machine and can be copied to the 64-bit machine.
- When using the NTCMD credentials to run discovery, if the following error is displayed, the Windows machine is configured to prevent interactive services from running:
To avoid this error, open the Registry Editor and edit the following registry key:
- You can configure discovery so that any object reported by the job and whose CIT is not defined in the adapter's discovered CITs list is marked in red. To set this parameter:
- The MQ (Microsoft Message Queue) model has been changed and the following resources are no longer available. The following CITs have been deprecated:
CIT: mqaliasq, display name: IBM MQ Queue AliasCIT: mqalias, display name: IBM MQ AliasCIT: mqchannelof, display name: IBM MQ Channel OfCIT: mqchannel, display name: IBM MQ ChannelCIT: mqchclntconn, display name: IBM MQ Client Connection ChannelCIT: mqchclusrcvr, display name: IBM MQ Cluster Receiver ChannelCIT: mqchclussdr, display name: IBM MQ Cluster Sender ChannelCIT: mqchrcvr, display name: IBM MQ Receiver ChannelCIT: mqchrqstr, display name: IBM MQ Requester ChannelCIT: mqchsdr, display name: IBM MQ Sender ChannelCIT: mqchsvrconn, display name: IBM MQ Server Connection ChannelCIT: mqchsvr, display name: IBM MQ Sender ChannelCIT: mqcluster, display name: IBM MQ ClusterCIT: mqmqichannel, display name: IBM MQ MQI ChannelCIT: mqmqilink, display name: IBM MQCIT: mqmsgchannel, display name: IBM MQ Message ChannelCIT: mqmsglink, display name: IBM MQ MessageCIT: mqmsgreceiverchannel, display name: IBM MQ Message Receiver ChannelCIT: mqmsgsenderchannel, display name: IBM MQ Messanger Sender ChannelCIT: mqqueuelocal, display name: IBM MQ Local QueueCIT: mqqueuemanager, display name: IBM MQ Queue ManagerCIT: mqqueueremote, display name: IBM MQ Remote QueueCIT: mqqueue, display name: IBM MQ QueueCIT: mqrepository, display name: IBM MQ RepositoryCIT: mqresolve, display name: IBM MQ ResolveCIT: mqxmitq, display name: IBM MQ Transmission QueueCIT: webspheremq, display name: IBM WebSphere MQThe following resources have been removed:Enrichment rule: Create_Msg_Channel_Link_HostEnrichment rule: Create_Msg_Channel_Link_IPEnrichment rule: Create_RemoteQueue_LinkEnrichment rule: Host_Depend_By_MQView: MQ_All_ObjectsView: MQ_ChannelsView: MQ_ClustersView: MQ_Network_ObjectsView: MQ Queue MapTQLs: All TQLs corresponding to the above Enrichment rules and ViewsMultilingual Support
- When an unsupported browser locale is used, the ODB Administration pages are shown translated, though they should appear in English. (QCCR1I47808)
- For compatibility purposes, Integration Points names and Data Flow Management job names can include only English letters, numbers, and the underscore character (_).
- Because the maximum string length for many ODB parameters is defined and documented in bytes, the real acceptable value length is shorter when multi-byte or language-specific characters are used. For example, Asian characters with UTF-8 encoding use 3 bytes, whereas some European language characters use 2 bytes.
- When exporting a report or other data which contains language-specific characters to a PDF file, multi-byte characters (such as Japanese, Chinese, Korean, and so on) are not displayed in the PDF file.
- XML files cannot be edited in Adapter Management when the user interface uses a Chinese, Korean, or Spanish locale.
- On localized hosts, Data Flow Probe Uninstaller may leave product files and folders on the disk.
- In Enrichment Manager, required attributes in the Node Definition dialog box are not marked in bold for the Japanese, Chinese, and Korean versions.
- If a report is attached to email, the report's file name changes to gibberish or other characters if the original file name includes multi-byte characters.
- CSV Format Export Troubleshooting: If any content in Japanese language is exported using the CSV format, when the report is opened in Microsoft Excel, the Japanese words are shown as gibberish
Workaround: Import the CSV list into Microsoft Excel, instead of opening the file directly. For details, see "Report Issues" in Reference Information.
Documentation Library
- The document ODBDataFlowContent.pdf, included with BSM 9.00, is not a complete and up-to-date version of this document. For details on working with DFM content, see the HP Universal CMDB Discovery and Integration Content Guide PDF. This book is available on the HP Software Product Manuals Web site (http://h20230.www2.hp.com/selfsolve/manuals) under the Universal CMDB (Application Mapping) product.
- If you experience a JavaScript error when opening the BSM Documentation Library online help system, disable the "Show Exception Dialog Box" in the Java Console and open the help again.
BSM Support Matrixes
This section describes matrixes for various environments and components supported by BSM versions. For complete system requirement information, see the HP Business Service Management Deployment Guide.
BSM Component Support Matrixes
BSM 9.00 System Support Matrix
Virtualized Environments
Platform Brand Version BSM 9.00 servers VMware ESX 3.x4.x Microsoft Hyper-V Windows Server 2008 R2 Hyper-VDatabase Support Matrixes
For complete details on database support, see the HP Business Service Management Database Guide.
Software Requirements - Oracle Server
The following table lists the Oracle servers supported for working with Business Service Management. A supported option means that HP quality assurance personnel have successfully performed basic tests on that option.
Examples of Tested Deployments - Oracle Server
The following table details the deployment environments that have been rigorously tested by HP quality assurance personnel.
Software Requirements - Microsoft SQL Server
The following table lists the Microsoft SQL Servers supported for for working with Business Service Management. A supported option means that HP quality assurance personnel have successfully performed basic tests on that option.
Examples of Tested Deployments - Microsoft SQL Server
The following table details the deployment environments that have been rigorously tested by HP quality assurance personnel.
BSM Component Support Matrixes
In each Table, √=supported, X=not supported.
Business Process Monitor 9.00 System Support Matrix
Business Process Monitor Compatibility Matrix
Business Process Monitor/QuickTest Professional (QTP) Compatibility Matrix
Business Process Monitor Protocol Support Matrix
SiteScope 11.00 System Support Matrix
SiteScope Compatibility Matrix
Real User Monitor 9.00 System Support Matrix
Real User Monitor Compatibility Matrix
Data Flow Probe 9.00 System Support Matrix
Data Flow Probe Compatibility Matrix
TransactionVision Agent Compatibility Matrix
Business Process Insight Compatibility Matrix
Business Process Monitor 9.00 System Support Matrix
Business Process Monitor - Operating Systems Windows Windows XP Professional 32-bit (SP2, SP3)Windows 2003 Standard/Enterprise editions 32-bit (SP2, SP2-R2)Windows Vista 32-bitBusiness Process Monitor Compatibility Matrix
For each BPM version, the latest supported VuGen version is mentioned. All previous versions of VuGen are supported as well.
Business Process Monitor/QuickTest Professional (QTP) Compatibility Matrix
Note: HP Quick Test Professional 10.0 can be obtained from HP BTO Software Web site. The link is accessible from HP QuickTest Professional software page (look for HP QuickTest Professional 10.0 Evaluation). You can also use the direct link.
Business Process Monitor Protocol Support Matrix
The following table describes the supported protocols for each platform on which you can install Business Process Monitor.
SiteScope 11.00 System Support Matrix
SiteScope Compatibility Matrix
Real User Monitor 9.00 System Support Matrix
Real User Monitor Compatibility Matrix
Note: Real User Monitor 7.01 (probe and engine) works only with Business Availability Center 7.01.
Data Flow Probe 9.00 System Support Matrix
Data Flow Probe - Operating Systems Windows Windows 2008 Standard/Enterprise editions, SP2 and R2Windows 2003 Standard/Enterprise editions (SP1, SP2)Data Flow Probe Compatibility Matrix
Note: Discovery Probe 7.51 works only with Business Availability Center 7.51.
TransactionVision Agent Compatibility Matrix
Note: All TransactionVision 8.0x Agents are compatible with all versions of TransactionVision Processing Server 9.0x.
Business Process Insight Compatibility Matrix
Verticals Support Matrixes
Application Management for SAP Component Support Matrix
Application Management for SAP works with SiteScope 10.x and SiteScope 11.0.
SAP Version Limitations SAP R/3 4.6SAP R/3 4.7 ERP 2004 (ECC 5.0)ERP 2005 (ECC 6.0) The following reports are not supported:Integration Matrixes
In each Table, √=supported, X=not supported.
BSM 9.00/HP Operations Manager (HPOM) Support Matrix
SiteScope/HPOM Integration Matrix
BSM/HP Diagnostics Integration Matrix
BSM/HP Network Node Manager (NNMi) Integration Matrix
BSM/HP Service Manager Integration Matrix
BSM-CMS Synchronization Integration Matrix
BSM/HP Operations Orchestration (OO) Integration Matrix
BSM 9.00/HP Operations Manager (HPOM) Support Matrix
HPOM Version
Required Patches
HP Operations Manager for Windows
8.16*
Server Patch OMW_00062 or higher
Accessories Patch OMW_00057
OMi enablement Patch OMW_00071
Agent Hotfix: QCCR1A100254
*If you are currently using HPOM for UNIX or HPOM for Windows in an HPOM manager of manager scenario you can use the following strategies to integrate information from these installations to BSM 9.00:
- Topology Synchronization
With an OMi-ready SPI on HPOM, use Configuration Upload to move topology information to HPOM for Windows version 8.16. Then use Basic or Dynamic Topology Synchronization to synchronize with BSM 9.00Use other discovery technologies such as HP Data Flow Management (formerly known as the HP Discovery and Dependency Mapping) using the Data Flow Probe- Event Forwarding
- Events may be sent from an HPOM system to an HPOM for Windows version 8.16 system, and from there to BSM. Note that events can only be related to CIs and set ETIs if they contain corresponding information, and if the CIs exist in the ODB.
SiteScope/HPOM Integration Matrix
Integration Matrix
HP Operations Manager for UNIX 9.0x
HP Operations Manager for Windows 8.1x
SiteScope 11.00
√
Certified
√
Certified
BSM/HP Diagnostics Integration Matrix
BSM/HP Network Node Manager (NNMi) Integration Matrix
1 Required Patches: HP-UX: PHSS_40612; Linux: NNM900L_00001; Solaris: NNM900S_00001; Windows: NNM900W_00001
BSM/HP Service Manager Integration Matrix
Note: For integration with Service Manager to function properly, additional setup is required in both Business Service Management and Service Manager. See the Business Service Management documentation for details.
Note: For the support matrix of the integration of Business Availability Center 8.x with Service Manager and ServiceCenter, see the Business Availability Center 8.x readme.
BSM-CMS Synchronization Integration Matrix
Integration Matrix
CMS 9.01
BSM 9.00
√
BSM/HP Operations Orchestration (OO) Integration Matrix
Integration Matrix
OO 7.6
OO 7.51
BSM 9.00
√
√
HP Software Support
You can visit the HP Software support web site at:
www.hp.com/go/hpsoftwaresupport
This web site provides contact information and details about the products, services, and support that HP Software offers.
HP 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
To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.
Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.
To register for an HP Passport ID, go to: HP Passport Registration.
Legal Notices
© Copyright 2005 - 2011 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.
For information about third-party license agreements, see the Third_Party_Agreements directory on the product installation media.
For information about open source license agreements, see the Open_Source_Agreements directory on the product installation media.
Trademark Notices
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
AMD and the AMD Arrow symbol are trademarks of Advanced Micro Devices, Inc.
Google™ and Google Maps™ are trademarks of Google Inc.
Intel®, Itanium®, Pentium®, and Intel® Xeon® are trademarks of Intel Corporation in the U.S. and other countries.
Java is a registered trademark of Oracle and/or its affiliates.
Microsoft®, Windows®, Windows NT®, Windows® XP, and Windows Vista® are U.S. registered trademarks of Microsoft Corporation.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Acknowledgements
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes software developed by the JDOM Project (http://www.jdom.org/).
This product includes software developed by the MX4J project (http://mx4j.sourceforge.net).
If you have any comments or suggestions regarding this document, please send them by e-mail to SW-Doc@hp.com.