HP SiteScope Release Notes for the Windows, Solaris, and Linux operating systems Software version: 11.00 Publication date: July 2010 This file provides information about HP SiteScope 11.00. Documentation Updates Installation Prerequisites What's New Enhancement Request Fixes Bug Fixes Notes and Limitations System Requirements Support Matrices HP Software Support Legal Notices Note: For release notes from earlier versions of HP SiteScope, see the root directory on the product installation media. Documentation Updates The first page of this release notes document contains the following identifying information: Version number, which indicates the software version. Publish date, which changes each time the document is updated. To check for recent updates or to verify that you are using the most recent edition, visit this URL: HP Software Product Manuals To retrieve a document, select the: 1. Product name. 2. Version list. 3. Operating System. 4. Preferred Language. 5. Document title. 6. Click Open or Download. You must have Adobe Reader installed to view files in PDF format (*.pdf). To download Adobe Reader, go to the Adobe web site. Installation Prerequisites You can upgrade SiteScope versions 10.x directly to SiteScope 11.00. For versions of SiteScope earlier than 10.00, you must first upgrade to SiteScope 10.x. For versions of SiteScope earlier than 9.x, you must first upgrade to SiteScope 9.x. What's New What's New Movies View guided and narrated demonstrations of some of the new features of SiteScope 11.00. These movies are located in the <SiteScope installation directory>/sisdocs/movies directory and can be accessed by opening the corresponding folders and pages listed below. What's New in SiteScope 11.00: /SiteScope_11_00_Whats_New/SiteScope_11_00_Whats_New.html SiteScope Event Integration: /SiteScope_Event_Integration/SiteScope_Event_Integration.html SiteScope Metrics Integration: /SiteScope_Metrics_Integration/SiteScope_Metrics_Integration.html SiteScope-BSM Downtime: /SiteScope_BSM_Downtime/SiteScope_BSM_Downtime.avi Improved Integration with Operation Manager Products Enhanced event integration enables event data to be sent to the HPOM management server or to Operations Management in BSM. Events are sent using the HP Operations agent that is supplied with SiteScope. Enhancements include: Events triggered by monitor metric status changes (in addition to alerts being triggered). Improved scalability and usability, and support for automatic node creation on the HPOM management server. Generated events also affect Service Health and Service Level Management in BSM. Integration Viewer user added for drilling down from HPOM events. Metrics integration provides visibility of SiteScope monitor metrics to HP Performance Manager and the Graphing component of Operations Management (in BSM) using the HP Operations agent. SiteScope collects metrics data, and logs it to the agent data store, which is installed on the SiteScope host. Note that reporting metrics to HP Performance Manager using the HP Operations agent is supported on HP Performance Manager 9.0 or later. Business Service Management (BSM) Integration Enhancements Customize topology reporting. Added the ability to customize topology settings for monitors that report topology to BSM. This includes selecting the CI type associated with the monitor and entering values for the CI type key attributes. Indicator changes. SiteScope monitor metrics are assigned indicators, which provide a more detailed view of the health of a configuration item (CI) when SiteScope reports data to BSM. Monitors of supported environments and monitors with a defined topology have indicators mapped to metrics by default. You can add new metric mappings or edit settings for existing mappings. For monitors that do not have default indicator metric mappings (monitors without CI type defined by default), you can map metrics to the appropriate indicators for the CI type linked to the monitor. Indicators are stored and managed in a central Indicator Assignments repository in System Availability Management, making it easier to manage large numbers of SiteScopes and monitors. Changes to indicators in the Indicator Assignments repository can be published to all SiteScopes that are connected to BSM. Indicator assignments modified on a local SiteScope server are not overridden by the centralized assignments. CI Downtime. Centralized Downtime Management allows configuring downtime for your IT infrastructure from one place in BSM. SiteScope is affected by downtime if a SiteScope monitor, measurement, or group CI is directly linked to a CI that BSM detects is in downtime. The action taken in SiteScope during the downtime depends on the downtime configuration in BSM. Downtime can affect monitoring, alerts, reports, and KPIs. Removal of monitor CIs from System Hardware Monitoring and System Software Monitoring views. SiteScope Failover Manager Solution Replaced SiteScope Failover with a more robust failover mechanism that includes the following features: SiteScope Configuration sharing: SiteScope is installed on a shared resource that is accessible to the failover machine. When a primary SiteScope is down, the SiteScope Failover process activated by SiteScope Failover Manager continues monitoring from the exact point where the primary SiteScope left off. No data loss in reports. No configuration copying (configuration changes between primary and failover servers are transparent). Configuration changes made on SiteScope Failover Manager are available on the primary SiteScope. New SiteScope Failover Manager installation: Standalone management application with no user interface. Installed on a local disk (not on the shared resource). Responsible for managing primary and failover instances. SiteScope Failover Manager is able to monitor multiple primaries simultaneously from a single Failover Manager machine. New SiteScope Failover license is provided free of charge. Microsoft Cluster solution was certified as an additional failover solution. Note: This solution is not backwards compatible with older versions of SiteScope Failover, and all SiteScopes monitored by the new solution must be upgraded to SiteScope 11.00. SiteScope Enterprise Readiness Improvements Eliminated the need to restart SiteScope on a daily basis. The default for SiteScope restart schedule option was changed to Off in Preferences > General Settings > Main Panel. Skip monitors. Improved skip monitor handling in SiteScope by adding a new Skip Monitor Settings pane to Preferences > Infrastructures Preferences. You can configure a maximum number of skips for a monitor. Based on this, SiteScope performs the following steps: If Shutdown on monitor skips is selected, SiteScope restarts. Otherwise it disables the problematic monitor for the period defined in Disable period of skip monitor. If the Send email to administrator if monitor is disabled after skip option is selected, SiteScope sends an email to the administrator if a monitor is disabled after the maximum number of consecutive monitor skips has been exceeded. Added the skip_monitor.log file to <SiteScope root directory>\logs which can be used to troubleshoot monitor skip problems. Installation and Licensing HP Operations agent is required for BSM and HP Operations Manager integrations. SiteScope Configuration Tool supports install and uninstall of the HP Operations agent. Added the ability to change all ports assigned to SiteScope from the SiteScope Configuration Tool. A new procedure is available for silent installation. The license mechanism has changed. License keys from previous versions of SiteScope are not compatible with this version. License key delivery can be fulfilled automatically via http://webware.hp.com. Existing customers should use the following link to retrieve an updated license: https://h20575.www2.hp.com/usbportal/softwareupdate.do The Evaluation license includes the following optional features for 60 days: Web Script, Exchange, WebSphere MQ, SAP, and Siebel. System monitors can be licensed by OS instance instead of points. For the list of system monitors supported for this licensing, refer to the HP SiteScope Deployment Guide Added license node locking. Added a license usage report. Business Process Monitor Support Installation of SiteScope and Business Process Monitor 9.00 is supported on a single server with no need for any manual configuration. New Supported Operation Systems for SiteScope Installation Microsoft Windows Server 2008 R2 (64 and 32 bit) environments Microsoft Windows Server 2008 R2 Hyper-V Microsoft Cluster (for SiteScope Failover installations only) New Supported Monitoring Capabilities Added the Amazon Web Services monitor that enables monitoring of Amazon Web Service cloud resources. The Amazon CloudWatch Service is required to monitor Amazon Web Services. Added the Microsoft Hyper-V monitor that enables monitoring of Microsoft Hyper-V hosts and virtual machines. Added the HP iLO (Integrated Lights-Out) monitor which enables monitoring of hardware health on supported HP ProLiant servers. The HP iLO monitor supports monitoring HP iLO 2 and 3 versions. Added the Connection Statistics monitor that collects data on SSH and Telnet connection behavior, and statistics for the Perfex and Perfex_dispatcher pool. Apache Server monitor supports monitoring on Apache HTTP Server 2.2. Citrix monitor supports monitoring on Citrix XenApp 4.6. MAPI monitor supports monitoring on Outlook 2007. Microsoft Exchange monitor supports monitoring on Microsoft Exchange 2010. Microsoft IIS Server monitor supports monitoring on Microsoft IIS Server 7.0. Microsoft SQL Server monitor supports monitoring on Microsoft SQL Server 2008 R2. Microsoft Windows Resources monitor supports monitoring on Windows Vista, Windows 7, and Windows Server 2008. WebLogic Application Server monitor supports monitoring on WebLogic 11g. Virtualization Support Microsoft Hyper-V Monitor supports monitoring on Microsoft Windows Server 2008 R2 Hyper-V. SiteScope reports near real-time Virtual server change topology to BSM for VMware Performance monitor and Solaris Zones monitor (moving of VM's between ESX servers; changes in zones configuration). Windows SSH Monitoring from SiteScopes Running on UNIX SiteScopes installed on UNIX servers include extended support for monitoring Microsoft Windows remote servers. The Windows remote server being monitored must be configured for SSH. The following monitors running on UNIX SiteScopes are now supported to monitor non-perfex based Windows SSH: Citrix, ColdFusion, Microsoft ASP Server, Microsoft IIS Server, Microsoft SQL Server, Microsoft Windows Media Server, Microsoft Windows Resources, and Real Media Server. (Only CPU, Disk Space, and Memory monitors were previously supported.) The following monitors running on UNIX SiteScopes are supported to monitor Windows SSH: Microsoft Windows Event Log and Microsoft Windows Services State. Note: Microsoft Windows Dial-up and Microsoft Exchange monitors are not supported on Windows SSH. The Allow Unix to NT setting was removed from Preferences > Infrastructure Preferences > General Settings. IP Version 6 Addressing Added support for IP version 6 on Windows and UNIX based SiteScopes for the following monitors: Citrix, ColdFusion Server, CPU, Database Counter, Database Query, DB2 8.x and 9.x, Disk Space, Log File, Memory, Microsoft ASP Server, Microsoft IIS Server, Microsoft SQL Server, Microsoft Windows Event Log, Microsoft Windows Resources, Microsoft Windows Media Server, Oracle Database, Ping, Port, Real Media Server, Service, UNIX Resources, URL, URL Content, URL List, URL Sequence, and Web Service monitor. Remote Server Enhancements Added option to test the connection to multiple remote servers. The test is performed in the background so you can continue to use SiteScope. In addition, it is possible to perform the same test on a template with remote server deployment. Alert Template Enhancements Added the <tag:[tagName]> property to alert templates to enable including values in the filter tag as parameters in alerts. This provides similar functionality to the custom properties mechanism that was removed in SiteScope 10.00. For example, you have a tag named AppServer with value Apache assigned to a monitor, and you include <tag:AppServer> in the alert template configured for that monitor. If an alert is triggered, the new property is replaced with Apache in the alert text. User interface performance improvements. Template Enhancements Added support for the Web Script monitor in template mode. Solution Template Enhancements Added support to the Microsoft SQL Server solution template for Microsoft SQL Server 2008 and 2008 R2. Added support to the Microsoft Exchange 2007 solution template for Microsoft Exchange 2010 servers. User Preferences Added Common Event Preferences to manage the templates used to define the attributes in the event flow. Added support for specifying multiple LDAP service providers when logging in to SiteScope using LDAP authentication. Previously, the IP address of the available server had to be specified, which meant that only one server could be searched. To use, enter the domain name of each LDAP service provider separated by a semi-colon (";") in the LDAP service provider field in User Management Preferences. SiteScope reads the list of LDAP service providers and searches for the available provider from the list. MG Files SiteScope no longer supports the SiteScope group MG files. The Enable configuration files option was removed from the user interface (Preferences > Infrastructure Preferences > General Settings). Instead, you can use the SiteScope API that was enhanced to replace this functionality. SiteScope Configuration API To help manage dynamic large environments, such as those that exist in private clouds, SiteScope introduced an extended SOAP-based API that supports the actions listed below. Sample Java code for utilizing the API is available. Each API call can be run from the command line on a Windows or UNIX platform. SiteScope Object Action Templates Template management (create/delete template, create/delete template container, import template) Template deployment (monitor, group, alert, remotes creation) Update deployment (groups, monitors, alerts, remotes) via template update Groups Enable/disable groups, delete groups Monitors Enable/disable, delete monitors, run monitors Alerts Enable/disable alerts Remote Servers Delete remote server preferences Status Get SiteScope server status (active monitoring, booting ...) statistics Configuration Get SiteScope configuration SiteScope Configuration API is a SOAP API that can be invoked by any known Web Services invocation framework such as Axis or WSIF, or by any client application. Using a SiteScope login name and password, you can call APIs and perform configuration changes and various other actions. Some API operations can be disabled on the server. This supports a read-only mode, such that the configuration cannot be changed remotely via the API. SiteScope API examples are available from the <SiteScope installation directory\examples\integrations\api directory. For details of APIs included with SiteScope, see the HP SiteScope API Reference located in <SiteScope installation directory\examples\integrations\api\doc\javadoc.zip. A user name and password are required by default when working with the extended SiteScope API. The API that was available with earlier versions of SiteScope has been deprecated. System Availability Management (SAM) The Link Monitor to CI Settings pane is not supported in BSM 9.00 or later and was removed from SAM Administration page. This functionality was replaced in SiteScope by the customizable report topology feature in the HP Integration Settings pane of the monitor properties. Added a SAM license report to BSM (Admin > Platform > License Management) that provides information on the number of SAM points consumed compared to the number purchased. EMS Integration Monitor Enhancements The EMS concept was not changed in SiteScope 11.00, but the flows were modified to be compatible with the new BSM 9.00 health indicator and KPI concepts. The main changes were in the EMS integration user interface in BSM 9.00. The XML can no longer be edited. The new user interface has all available configuration options in a user-friendly graphic format. The HP OM Event monitor is no longer available when SiteScope is connected to BSM version 9.00 or later (unless the monitor was created in an earlier version of SiteScope that was upgraded to SiteScope 11.00), since OM events can be forwarded to BSM 9.00 provided you have an Event Management Foundation license and the HP Operations Manager integration is configured. After selecting a field mapping, only the appropriate topology scripts are available for selection. For Events field mapping: Hosts, Host - Software elements, or Custom script For Measurements field mapping: SiteScope Topology, No Topology or Custom script For Tickets field mapping: Tickets or Custom script New Performance Center Integration The new integration with Performance Center 11.00 provides the following new functionality which eliminates many drawbacks from previous integrations. SiteScope user interface is hosted in Performance Center. This enables leveraging SiteScope functionality in a use case oriented approach, without requiring additional monitor configuration on the Performance Center side. Monitors can be run outside the context of the performance test. This contributes to the scalability of the SiteScope server, and reduces network noise when no tests are running. Performance Center enables monitor template deployment using the SiteScope API, without interacting with the SiteScope user interface. SiteScope data is displayed in different graphs in the Performance Center run screen. Measurement names can be easily identified and filtered. Measurement thresholds configured in SiteScope are utilized by the Performance Center run screen to indicate possible bottlenecks during the test run. Lightweight Single Sign-On (LW-SSO) authentication was embedded in SiteScope to enable integration with Performance Center. After installing SiteScope, you should immediately change the initString default value. In Performance Center, locate the lwssofmconf.xml file and change the value directly in that file. In SiteScope, you can do this directly in the <SiteScope root directory>\conf\lwsso\lwssofmconf.xml file (only before the first time the service is loaded). You can also change the value in SiteScope Preferences (Preferences > General Preferences > LW SSO Settings). Note: For limitations, security warnings, and general reference on using LW-SSO, see the Lightweight Single Sign-On Authentication section in the Using SiteScope guide. Documentation Changes SiteScope documentation is available as a standalone help system that contains the "Using SiteScope" and "SiteScope Monitor Reference" guides. It is no longer a part of the BSM Documentation Library. The "Using System Availability Management" guide in the BSM Documentation Library contains documentation on System Availability Management topics only (it no longer contains SiteScope-related information). The following information supplements the current SiteScope documentation on "Working with Operations Manager Products": Sizing Recommendations for SiteScope-Operations Manager Metrics Integration While the default SiteScope configuration allows running thousands of monitors, sizing is important for planning the maximum number of monitors, metrics, and monitors types that can be stored within the SiteScope-HPOM metrics integration. The sizing should not exceed: Maximum insertion rate of 1000 metrics per minute. Total retention storage of 1 GB. Total retention period of 5 weeks. Definitions The following are definitions of the terms used in the validation calculations below: Monitors. The number of monitors that report metrics to HPOM Performance Manager. Metrics. The average number of metrics of the above mentioned monitors that report to HPOM Performance Manager. Frequency. The average frequency at which the above mentioned monitors feed data into the integration. Validation When choosing the specific SiteScope monitors and metrics to store within the SiteScope-HPOM metrics integration, you should validate that the insertion and retention rates do not exceed the recommendations. You can do that using the formulae below: Supported Insertion Rate Validation: (Monitors * Metrics) / Frequency <= 1000 metrics/minute Supported Retention Period Validation: (1000 MB) / ((Monitors * Metrics / Frequency) * 0.07 MB) = configured retention period in days (which should be less than the maximum retention period of 5 weeks) where 0.07 MB is the storage size for each metric/minute per day. Example If you have 2500 monitors that report data using the HPOM metrics integration, and every monitor has 4 metrics, the frequency of these monitors is every 10 minutes, and the average metric storage size per day is 0.07 MB, you will be able to store your historical data for 14 days. Validation calculations: Insertion Rate Validation: (2500 monitors * 4 metrics) / 10 minutes = 1000 <= 1000 metrics/minute Retention Period Validation: 1000 MB / (((2500 * 4 Metrics) / 10 minutes) * 0.07 MB) = 14.28 days (<= 5 weeks) Enhancement Request Fixes Description CR ID or SR/E-Sar Number Area Added the <allThresholds> property that returns all the thresholds for the monitor that triggered the alert. The existing <_classifier> property returned the first threshold only in the email alert. QCCR1I33010 Alerts Added the <tag:[tagName]> property to alert templates to enable including values in the filter tag as parameters in alerts. This provides similar functionality to the custom properties mechanism that was removed in SiteScope 10.00. For example, you have a tag named AppServer with value Apache assigned to a monitor, and you include <tag:AppServer> in the alert template configured for that monitor. If an alert is triggered, the new property will be replaced with Apache in the alert text QCCR1I 34927 Alert Templates Added support for connect to server and user login in the auto template deployment XML file. The user name and password can be encrypted with the external encryption tool that is used for encrypting variables. QCCR1I37452 Auto Template Deployment Added support in auto template deployment for verifying monitor properties with the remote server by setting the _accessControlled attribute to true in the XML file. QCCR1I39368 Auto Template Deployment Output from the Tomcat Console is available in the tomcat.log file under <SiteScope_root_directory>\logs. This information can be useful for troubleshooting JVM related issues, which might otherwise require restarting SiteScope from the go.bat file. QCCR1I46839 Configuration Added support for installing SiteScope on Microsoft Windows Server 2008 R2 (64 and 32 bit) environments. QCCR1I28202 Installation In earlier versions of BSM, every action triggered under a SiteScope alert was logged to the Event Log, which led to duplicate events being logged for the same trigger condition when multiple actions were defined under a single SiteScope alert. Alerts that are sent as events in SiteScope 11.00 do not have this problem in BSM 9.00. QCCR1I43816 / 4612120197 Integration - BSM Information in the SiteScope Monitor description field can be reported to BSM and displayed in Service Health by performing the following (provided you have BAC version 7.0 or later): 1) Export the SiteScope Monitor CIT definition to XML. 2) Add the data_description attribute to the <Attribute-Overrides> section as follows: <Attribute-Override name="data_description" is-partially-override="true"> <Attribute-Qualifiers> <Attribute-Qualifier name="DASH_ATTRIBUTE"/> </Attribute-Qualifiers> </Attribute-Override> 3) Import the new XML. 4) Select Admin > Service Health > Repositories > Business Rules. 5) Override the tooltip of the rule on the KPI for which you want to see this information by right-clicking the rule, and selecting Edit Rule. 6) Edit the overridden tooltip and add a new parameter: Display Label: <choose name> Value source: NODE.PROPS.data_description QCCR1I34206 / 4602808076 Integration - BSM When SiteScope 11.00 is connected with BSM 9.00 and event integration is enabled, if an alert is triggered in SiteScope, the threshold that triggered the alert is included in the event that is forwarded to OM. In earlier versions of SiteScope and BSM, it was not possible to include thresholds created for monitors in alerts. QCCR1I 965 / 41716/ 40959 Integration -OM/BSM SiteScope now sends the label name for content match values found in URL Content monitor to the Generic Data and Diagnostics integrations. QCCR1I36751 Integration - Generic Data / Diagnostics When SiteScope is integrated with Performance Center, you can add new monitors and groups to SiteScope, and perform administrative tasks without having to unregister the SiteScope in the Performance Center and delete certain properties. QCCR1I40164 Integration -Performance Center The HP OM Event monitor supports HP Operations Manager versions 9.0 or later when installed on Red Hat Linux. QCCR1I39611 Monitors Added support for specifying multiple LDAP service providers when logging in to SiteScope using LDAP authentication. To use, enter the domain name of each LDAP service provider separated by a semi-colon (";") in the LDAP service provider field in User Management Preferences. SiteScope reads the list of LDAP service providers and searches for the available provider from the list. (Previously, the IP address of the available server had to be specified, which meant that only one server could be searched.) QCCR1I34520 / 4603948909 Preferences Added the Mask secondary response check box to UNIX remote server properties. If selected, this enables the root password and initialization parameters in the Secondary response field to be hidden behind asterisks. QCCR1I 4189 Remote Servers Added time values to the graph's tooltip in Server-Centric Reports. QCCR1I46698 Server-Centric Reports The following enhancements were implemented as part of the new SiteScope Failover solution: Support for LDAP authentication Automatic synchronization of the primary master.config file with the default.config file. (Previously, the <SiteScope >\WEB-INF\classes\default.config file had to be manually updated with the primary <SiteScope>\groups\master.config file to make sure that it was current.) QCCR1I44242 / 4613896196 / QCCR1I37388 SiteScope Failover The issue of SiteScope Failover copying the restart schedule from the primary SiteScope no longer exists in the new SiteScope Failover solution. In addition, configuration problems caused by SiteScope daily restart no longer exist, since daily restart was eliminated. QCCR1I38537 SiteScope Failover Fixed issue in Quick reports and Management reports of SiteScope displaying "time in error" using the most appropriate time unit (for example, hours rather than days when the time in error is greater than 24 hours). QCCR1I34668 SiteScope Reports You can control the location of the ellipsis ("...") used in long labels in System Availability Management Reports. This enables you to move the ellipsis from the end to the middle of the label. For details, see "Long Labels Used in Reports" in Using System Availability Management in the Business Service Management documentation Library. QCCR1I25562 System Availability Management Reports Added the ability to map metrics to System Availability KPIs when SiteScope 11.00 is integrated with BSM 9.00. SiteScope metrics are mapped to Health Indicators, which are in turn mapped to System Performance and System Availability KPIs. The metrics-to-indicator mappings can be customized if necessary. QCCR1I36330 System Availability Management Reports Bug Fixes Description CR ID or SR/E-Sar Number Area Fixed issue of subject field of Email alerts not supporting non-English characters by selecting International version in Preferences > General Preferences. QCCR1I38533 Alerts Fixed issue of the WebSphere MQ Status monitor causing performance problems in the WebSphere MQ administrative console when the monitor is running. QCCR1I34016 3605053574/ 3604293653 Monitors The Composite monitor is not supported in template mode, and an error message is displayed when attempting to copy this monitor to a template. QCCR1I27803 Templates Fixed issue of Directory monitor not correctly monitoring directories on Microsoft Windows remote servers when using an SSH connection (provided you have credentials for the directory that needs to be monitored). QCCR1I42223 Monitors Escalation Fixes CR ID or SR/E-Sar Number Description Area QCCR1I35883 232544 Fixed issue of being unable to use a variable in the Server field of a script alert. Alerts QCCR1I35716 / 232116 Fixed issue of content match not working correctly with the Web Service monitor. To enable Web Service monitors defined prior to an upgrade to match the correct value, select the Web Service Monitor use common content match option in Preferences > Infrastructure Preferences > Monitor Settings. This means that Web Service monitors behave in the same way as other monitors where content matching is used. Clear the setting to revert to the old content match behavior. Monitors QCCR1I39313 / 230919 Fixed issue in MAPI monitor of being unable to use an account (other than the mailbox account), for logging in to the SiteScope server. Monitors QCCR1I39306 / 4604512677 Fixed issue with the Microsoft Windows Resources monitors of counter values that are available when running the monitor using the Microsoft Windows PDH Library collection method, not being available when using the Direct registry queries method. Monitors QCCR1I39950 / 4608827922 Fixed issue of being unable to create a Network Bandwidth monitor when working with Cisco 650x series switches. Monitors QCCR1I34520 / 4603948909 Fixed issue of being unable to specify more than one LDAP service provider when logging in to SiteScope using LDAP authentication by adding support for a multiple providers list. For details, see User Preferences. User Preferences Notes and Limitations Description CR ID or SR/E-Sar Number Area The Running Software CI which is reported by both SiteScope and Real User Monitor is not reconciled, since SiteScope does not report the IpServiceEndpoint CI that should be linked to the Running Software CI. QCCR1I39607 BSM Integration If you upgrade to BSM 9.10 (when it is available), you should manually resynchronize SiteScope instead of waiting for topology data to be sent to BSM based on the Topology resynchronization time interval value. QCCR1I39744 BSM Integration When SiteScope versions earlier than 10.00 are connected to BSM 9.00, EMS integrations reporting the Application CI (HP OVO, NetScout, and generic integrations) fail since the application_id attribute was removed from the Application CI in BSM 9.00. QCCR1I28808 BSM Integration Sending topology fails for some monitors deployed from solution templates (since not all monitors have the report topology to BSM option selected by default). Workaround: After deploying a monitor using a solution template: 1) Expand HP Integration Settings in the monitor properties. 2) Select Enable reporting monitor status and metrics (in the BSM Integration and Data and Topology Reporting section) to enable the monitor to report to BSM. QCCR1I48052 BSM Integration To improve performance, SiteScope uses a topology cache when sending topology data to the ODB. If SiteScope attempts to send an existing CI to the ODB, the CI may not be sent or be created in the ODB for up to a week because of the way the topology cache works. This could happen in the following circumstances: When cutting and pasting a monitor from one group into a new group (so the original group is left empty), and then cutting and pasting the monitor from the new group back into the original group.   When disabling data and topology reporting for a monitor and then enabling it again in HP Integration Settings. After a CI has been manually deleted from the ODB, it is not created again until the cache is cleaned out. (EMS flow - Deleting EMS monitors from the ODB) Workaround: If you cannot wait approximately one week to see the CIs, you can manually synchronize the data as follows: In Preferences > Integration Preferences, edit the relevant integration and in the BSM Preferences Available Operations area, click Re-synchronize.   BSM Integration Deploying SiteScope templates while registering a SiteScope to BSM may cause a loss of topology data reported to BSM. It is recommended to avoid making configuration changes while performing BSM registration.   BSM Integration If SiteScope restarts for any reason while SiteScope is connected to BSM, some topology data that SiteScope forwards to BSM may be lost. Workaround: If not all topology data was forwarded to BSM, manually synchronize the data as follows: 1) In Preferences > Integration Preferences. 2) Edit the relevant integration. 3) In the BSM Preferences Available Operations area, click Re-synchronize.   BSM Integration When working under high load conditions, you should suspend all monitors before connecting to BSM for the first time.   Capacity Limitations When SiteScope is integrated with BSM, performing various very high load operations might cause problems in SiteScope. Use the following guidelines: Do not run the Publish Template Changes Wizard for over 3,000 monitors at once. Do not run the Monitor Deployment Wizard to create over 3,000 monitors at once. Do not copy/paste over 3,000 monitors in a single action. Do not perform a Global Search and Replace to modify BSM integration properties for over 2,500 monitors at once. QCCR1I30633 Capacity Limitations If applet loading fails with a "NoClassDefFound" exception, select the Keep temporary files on my computer option in your client Java configuration (Control Panel > Java > General Tab > Temporary Internet Files > Settings). If security issues require it, delete the temporary files manually when you finished using the SiteScope applet: 1) Close the SiteScope applet. 2) Select Control Panel > Java > General Tab > Temporary Internet Files, and click Delete Files. QCCR1I37003 Configuration If SiteScope is installed on Microsoft Windows Server 2008, you should manually define the time zone offset in Preferences > Infrastructure Preferences > General Settings > Time Zone offset, in hours, from Greenwich Mean Time (GMT). For example, if the time zone is GMT +2, type "-2" as the time zone offset. If the time zone is GMT -5, type "5" as the time zone offset. For GMT, type "-999" or "0". 4605889641 (SR) Configuration When creating a Diagnostics Integration in Integration Preferences, if you select the Include additional data option, all other Diagnostics and Generic Data integrations are affected (the data SiteScope forwards to these applications also contains this additional data). It is recommended to select this option only if you require this additional data for all your Diagnostics and Generic Data integrations. For details on the option, refer to the "Diagnostics Integration Preferences Dialog Box" in the "Integration Preferences User Interface" section of the Using SiteScope help.   Diagnostics Integration The Dashboard column layout in the Monitor History view cannot be saved during user sessions. QCCR1I20806 Dashboard When using Global Search and Replace, unable to replace Credentials values that are used in remote servers and monitors. QCCR1I42998 Global Search and Replace Custom topology (CI type selection and CI attributes) is not supported (and not available) in Global Search and Replace. QCCR1I39602 Global Search and Replace Indicator Settings are not supported, and are not available, in Global Search and Replace. QCCR1I45045 Global Search and Replace The Review Summary page displays the real host name of the monitored server instead of the name by which the remote machine should be known in SiteScope. This means that you cannot differentiate between multiple remote servers created for the same host machine (for example, where one remote server uses the WMI connection method and another uses NetBios).   Global Search and Replace When performing a global search and replace operation in a load environment of over 1,000 monitors, you may encounter an out-of-memory error in the Java applet on the client machine performing the global search and replace. Workaround: Increase the heap size of the Java applet on the client machine. 1) Click Start > Control Panel > Java > Java tab. 2) View the Java Applet Runtime Settings and enter the following in the Java Runtime Parameters field: -Xmx128m (default is 64m). QCCR1I27880 Global Search and Replace When using Global Search and Replace, the Server property is available only when monitors from the following group are selected: CPU monitor, Disk Space monitor, Memory monitor, Microsoft Windows Performance Counter monitor, Web Server monitor, or Service monitor. For other monitors, the Server property can only be changed by selecting that specific monitor subtype in the Select Subtype page. For example, if a CPU monitor is selected with a Web Server monitor, the Server property is available. If a monitor, not from this group, is also selected, the Server property is not available. QCCR1I36248 / 4605639358 Global Search and Replace When installing SiteScope with the HP Operations agent on a UNIX environment that previously had the agent installed (even if it was uninstalled), the newly-installed agent is unable to connect to OM or Operations Management (in BSM). Workaround: Before installing SiteScope with the HP Operations agent on a UNIX environment, delete the following folders: opt/OV and var/opt/OV. QCCR1I47566 Installation SiteScope installation fails if installing in Korean. Workaround: Use an English installation (select "English" instead of "Korean" in the Choose Locale screen during installation). QCCR1I48272 Installation When using the SNMP Browser Tool or the XSL Transformation Tool, the results may not be readable in languages other than English. Workaround: Click the Save To File button, save the results to an external file, and open the file with an external editor. QCCR1I32444 I18N When installing SiteScope in a Chinese, Japanese, or Korean environment, some component names are missing in the installation Details tab, and not all characters are displayed correctly in the status line. QCCR1I47816 I18N When installing SiteScope in a Chinese, Japanese, or Korean environment, there is no SiteScope folder in the Start > Programs menu. QCCR1I37237 I18N SiteScope Failover Manager installed on a non-English environment is unable to register a service for SiteScope. QCCR1I50617 I18N When changing the custom topology from reporting Unix to Windows CI type (for reporting the same IP), the old CI and link are not deleted from the monitor's topology. QCCR1I42212 Integration Monitors Publishing changes after changing custom topology in an EMS monitor template does not affect a monitor's custom topology in BSM. QCCR1I48048 Integration Monitors For the SiteScope user interface to start, Java Runtime Environment (JRE) must be installed on the SiteScope client machine. If you are using JRE 5, you might get Java script validation errors when opening dialog boxes in SiteScope. Using Firefox 3.0 with JRE 5u14, 5u15, or 5u16 causes the applet to freeze any operation until the browser is closed. Workaround: Configure you browser to use JRE 1.6.0_14 or later. QCCR1I20599, QCCR1I22818, QCCR1I24623 Installation and Upgrade The SiteScope user interface does not start and the following error message is displayed: "Several Java Virtual machines running in the same process caused an error". This is a known Java defect (http://bugs.sun.com/view_bug.do?bug_id=6516270) that might occur when using Internet Explorer 7. Workaround: Either: Use a browser other than Internet Explorer 7. Upgrade to Java 6 update 10 or later. (3). In the Add or Remove Programs dialog box (Start > Control Panel > Add or Remove Programs), remove all Java/Java Runtime Environment installations except for the latest version.   Installation and Upgrade The SiteScope user interface does not start and an error message is displayed while starting the SiteScope applet (for example: "The Java Runtime Environment cannot be loaded"). Workaround: Perform the steps below. After each step, try to reopen SiteScope. If SiteScope fails again, proceed to the next step. 1) Close all the browser's windows. 2) End all remaining browser processes (if any remained) using Windows Task Manager. 3) Clean the local Java applet cache. Select Start > Control Panel > Java, and in the General tab, click Delete Files and then click OK. 4) Clean the local Java applet cache by deleting the content of the following folder: C:\Documents and Settings\<user_name>\Application Data\Sun\Java\Deployment\cache.   Installation and Upgrade After upgrading from SiteScope 7.5.x to 9.0 and then to 10.1x, if 7.5.x contained an administrator user and a regular user and the username and password for the administrator was blank, some or all of the monitors and alerts may not be displayed in the user interface after the upgrade. Workaround: After upgrading to SiteScope 9.0, enter the username and password for the administrator user in Preferences > User Management Preferences in the user interface. QCCR1I32727 Installation and Upgrade The SiteScope menu bar opens but the applet fails to start, and you see a blank screen or an "x" image. Workaround: Perform the following: 1) Click Start > Control Panel > Java. 2) In the Java Control Panel, click the Advanced tab. 3) Expand the Default Java for browsers folder (or <APPLET> tag support if you are using Java 5), and make sure that Microsoft Internet Explorer and Mozilla family are selected. 4) Click Apply and then click OK.   Installation and Upgrade The ability to report topology data to BSM was enhanced with several complex topologies (such as WebSphere, WebLogic, and so forth). SiteScope must collect the properties for these topologies on the first start after an upgrade. This may take some time because it means connecting to the monitored servers and getting the additional data. A problem may arise during the first restart if it takes longer than 15 minutes because SiteScope automatically restarts if there are no monitors running within this time. Workaround: 1) After an upgrade, use the following batch file to start SiteScope for the first time: <SiteScope root directory>/bin/go.bat. 2) Once SiteScope is started, for any monitors that are monitoring environments that are not running, select Disable reporting metrics to BSM under BSM Integration Data and Topology Settings in HP Integration Settings. This saves wasting time waiting for the monitored servers to reply.   Installation and Upgrade An Internet Explorer exception error message is thrown inside SiteScope pages, indicating Operation aborted. Workaround: Remove or disable the Skype add-ons on your system. For further details, see http://support.microsoft.com/default.aspx/kb/927917.   Installation and Upgrade Templates and solution templates might be missing from the Templates context after installing SiteScope. Workaround: Copy all the templates from the <SiteScope root>\export directory to the <SiteScope root directory>\persistency\import directory (you might need to create this folder if it does not exist).   Installation and Upgrade When logging to SiteScope using LDAP authentication, unable to generate a Management Report due to authentication issues. Workaround: Define the user password in SiteScope to be the same as the one used in LDAP. QCCR1I31883 LDAP Authentication Monitor Thresholds. If you clear or add a counter (from the counters tree in the Monitor Settings panel) that has corresponding thresholds defined in the Threshold Settings panel, the counter might be replaced in the Threshold Settings with the next selected counter in the counter tree, replaced by the default counter, or removed from the Threshold Settings panel. This limitation applies to all browsable monitor counter types in template mode only, and to the Microsoft Windows Resources, Apache, and Health monitors in normal and template mode.   Monitors Monitor Tree. If there is a large space between group containers in the SiteScope monitor tree, refresh your browser.   Monitors Monitor Thresholds. If, in the counters tree in the Monitor Settings panel, you clear or add a counter that has corresponding thresholds defined in the Threshold Settings panel, the counter might be: Replaced in the Threshold Settings with the next selected counter in the counter tree. Replaced with the default counter. Removed from the Threshold Settings panel. This limitation applies to all browsable monitor counter types in template mode only, and to the Microsoft Windows Resources, Apache, and Health monitors in normal and template mode.   Monitors Disk Space monitor. The Disk Space monitor displays slightly different results depending on the protocol that is used (NetBIOS, WMI or non-perfex based SSH). QCCR1I28593 Monitors File monitor. If Telnet is used as the connection method for UNIX remote servers running on an HP-UX or Linux operating system, and either (1) the LANG environment variable is unset, or (2) "set -u" is in effect and the LANG or LC_ALL environment variables are unset, the File monitor will not work regardless of the file it is monitoring. Workaround: Permanently set the LANG and LC_ALL environment variables to the default shell for the SiteScope user. QCCR1I23798 Monitors Database Query monitor. The Database Query monitor status is shown according to the server locale. If there are any specific messages from the database, such as error messages, this information might not be displayed properly in the status field where the server locale is different from the client locale, and the information contains non-Latin characters. QCCR1I41201 Monitors Microsoft Windows Event Log monitor. The Microsoft Window Event Log monitor is only able to retrieve partial data when monitoring the event log on a Windows Server 2008 because it cannot read the message DLL file. QCCR1I30719 Monitors Microsoft Windows Event Log monitor. The Microsoft Windows Event Log monitor is unable to monitor "Critical" event types on Windows 2008 servers. This is because the event type is not supported in the Event Type list. This limitation is relevant for SiteScopes installed on Windows Server 2008 only. QCCR1I32441 Monitors Microsoft Windows Media Server monitor. The Microsoft Windows Media Server monitor is unable to get counters from the remote server when monitoring on Windows Server 2008 (64bit). QCCR1I34286 Monitors Ping monitor. When SiteScope is installed on Solaris, the Ping monitor might take longer than expected to run, and might exceed the timeout for displaying the monitor status in the popup window (the default timeout is 5 seconds). Workaround: In the Ping Monitor Settings panel, increase the value in the Timeout (milliseconds) field. QCCR1I26236 Monitors Script monitor. When defining a Script monitor to monitor a Linux remote server using the Telnet connection and the script is defined as USE COMMAND, the match expression may not work properly. This could be caused by a limitation in the number of characters that can be used to run the USE COMMAND. By default, the terminal command line has a length limitation on the size of the command per line. Workaround: Change the connection method to SSH on the defined Linux remote server. QCCR1I30899 Monitors SNMP monitor. When the SNMP monitor is integrated to report data to HP Diagnostics, the measurement label is sent as a name instead of the real measurement name. Workaround: Use the SNMP by MIB monitor instead.   Monitors Technology Integration monitor. When creating a Technology Log File Integration monitor, it is recommended to perform the Test Script (during monitor configuration, in the Topology Settings area, select a topology script in the Script field and click Test Script) of the topology script using a short log file. If a long log file is used for testing the topology script, it may take several minutes. QCCR1I25754 Monitors Date and time format for monitor status is shown according to the server locale instead of the browser locale. QCCR1I41203 Monitors 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 Monitor Deployment Wizard Non-English characters are displayed correctly in HPOM/Operations Management if they are named with the HP Operations agent machine locale only. HP Operations agent machine locale should be the same as the HPOM management/BSM Gateway server machine. QCCR1I43630 OM Integration When SiteScope is integrated with Operations Manager, the HP Operations agent included with SiteScope requires an OS Instance Advanced license. Nodes registered in Operations Manager through the node discovery policy might also (falsely) request a Target Connector license. For details on Operations Manager licensing requirements, refer to the Operations Manager documentation.   OM Integration SiteScope does not support HP Operations agent version 11.00 when integrating with Operations Manager.   OM Integration After changing the user name or password of a credential profile, any open connections that are using this credential remain open and are not reconnected. Workaround: Restart SiteScope. QCCR1I30651 Preferences Plink support was removed from SiteScope in 11.00   Remote Servers/SSH Due to a bug in Sun Java, SiteScope installed on Solaris 10 is unable to connect to a remote UNIX server via SSH using Internal Java Libraries. Workaround: In the file <SiteScope root directory>\bin\start-monitor, add the following to the argument list of the JRE (just before the -Dflipper.param.file argument): -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch. PollSelectorProvider   Remote Servers If a Monitor Summary report is created using an Internet Explorer browser, and Export to file and Comma-delimited (csv) are selected in the Export Settings, an authentication popup window is displayed after clicking Generate Report. Workaround: In the authentication window, click Cancel and the file opens in Microsoft Excel. QCCR1I30696 Reports 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. Workaround: Restart BSM. QCCR1I44570 System Availability Management Administration Copying and pasting from SiteScope 11.00 to earlier versions of SiteScope is not supported. QCCR1I30669 System Availability Management Administration When copying monitors, groups, or other entities between multiple SiteScope instances, tag assignments are lost even if the tags that were assigned to the copied entities on the source SiteScope are present on the target SiteScope. QCCR1I32039 System Availability Management Administration When copying and pasting a SiteScope monitor into a group, the monitor data can take up to an hour before it is displayed in Service Health in HP Business Service Management.   System Availability Management Administration When copying and pasting a monitor that includes a script alert from one SiteScope into another, the remote server of the script alert may not correctly copy into the target SiteScope. Workaround: If you are copying script alerts from one SiteScope to another, ensure that the remote server accessed by the script alert exists in the target SiteScope before copying. QCCR1I32040 System Availability Management Administration The Technology Log File Integration monitor cannot be copied from one SiteScope to another. Workaround: Create an identical monitor on the target SiteScope (copy all monitor values to it from the original monitor). To copy a sub-tree containing Technology Integration monitors: 1) Copy the sub-tree to a temporary location in the same SiteScope. 2) Delete the Technology Integration monitors. 3) Copy the new sub-tree from the temporary location to the other SiteScope. 4) Delete the temporary location. 5) Create the Technology Integration monitors in the other SiteScope QCCR1I30759 System Availability Management Administration If you experience monitor skips when using the SSH retries mechanism on a UNIX remote server, check the monitor run frequency and the _numberOfRepeatExecForSSHConnection and _UNIXSSHTimeoutSeconds property values in the master.config file to make sure they are not the cause of the skips (for example, if monitor frequency equals the SSH timeout). Note that time is used from _UNIXSSHTimeoutSeconds for every unsuccessful retry. Therefore, if the number of retries is set too high (so that it is longer than the monitor run frequency), this can increase the number of monitor skips and result in SiteScope restarting.   SSH F-Secure is no longer officially supported when monitoring remote servers using SSH.   SSH The SiteScope installer might not work on Linux 64-Bit environments using the graphical user interface wizard. Workaround: Install SiteScope using the console mode instead. QCCR1I43277 SiteScope Installation If a template contains an invalid dependency (the template contains a dependency that existed once but no longer exists in the imported template), no dependency is shown in the template deployment. When running the Publish Template Changes wizard, the Depends on property is displayed as a difference in the Content Changes page even though there is no dependency displayed in the template. Workaround: Add a new dependency in the template, remove it, and then click Save. This removes the non-existent dependency. QCCR1I32397 Templates If the Method or Operating system values in a template remote server contain an incorrect value or are not entered using the same case that is displayed in the drop-down list when configuring a remote server, verification does not work properly, and the first value in the drop-down list is inserted instead. Workaround: Enter the value exactly as it is displayed in the tooltip on the Remote Servers page in the template.   Templates When using the Event Log Tool, if DNS is selected in the Log name box and the target server does not have a DNS server on it, the Application log content is displayed in the Results panel. QCCR1I32543 Tools When using the Database Connection Tool to apply properties to the Database Query monitor or Technology Database Integration monitor, the credential data is lost if a credential profile is selected instead of entering the credentials manually. QCCR1I32050 Tools When opening the same SiteScope server user interface in more than one tab of a browser window, SiteScope hangs when trying to navigate between the SiteScope server tabs. Workaround: Close the redundant tabs, and make sure that only one tab is open for the same SiteScope server user interface. Alternatively, open a new browser window. QCCR1I36524 User Interface System Requirements Below are the minimum system requirements and recommendations for running SiteScope, based on the various supported operating systems. System Requirements for Windows Computer/Processor 800 MHZ or higher Operating System Microsoft Windows 2003 Standard/Enterprise editions SP1, SP2 Microsoft Windows Server 2003 Enterprise R2 SP1, SP2 Microsoft Windows Server 2008 Standard/Enterprise R2, SP2 Microsoft Windows Server 2008 R2 Hyper-V Memory 1 GB minimum (2 GB+ recommended) Free Hard Disk Space 2 GB or more (10 GB+ recommended) Java Plug-in (to view applets) Recommended: 1.6.0_14 or later System Requirements for Solaris Computer/Processor Sun 400 MHz UltraSparc II Processor or higher Operating System Sun Solaris 9 or 10 (with latest recommended patch cluster) Memory 1 GB minimum (2 GB+ recommended) Free Hard Disk Space 2 GB or more (10 GB+ recommended) Java Plug-in (to view applets) Recommended: 1.6.0_14 or later System Requirements for Red Hat Linux Computer/Processor 800 MHZ or higher Operating System RedHat ES/AS Linux 4, 4.3, 5.2 Memory 1 GB minimum (2 GB+ recommended) Free Hard Disk Space 2 GB or more (10 GB+ recommended) Java Plug-in (to view applets) Recommended: 1.6.0_14 or later Note: SiteScope can be installed as a 32-Bit application over 64-Bit environments for the supported operating systems listed above. System Requirements for VMware The following VMware environments are supported in SiteScope according to the configurations tested below: Supported and Tested Environments VMware ESX 3.0 VMware VirtualCenter 3.0 Supported Environments Only VMware VirtualCenter 2.x VMware ESX 3.x VMware ESX 2.5 via VirtualCenter 2.x VMware ESX 3.x via VirtualCenter 3.x VMware vCenter Server 4.0VMware ESXi 4.0 VMware ESX 4.0 VMware Configuration Tested 4 VMware Virtual Machines (VM) on one physical server Each VM with 2 CPUs at 2.39Ghz, 8 GB memory, and 40 GB disk space Storage used is HP EVA 8400/22G Physical server: ESX host is HP BL490c G6 with 8x Intel Xeon x5570 CPU, 72GB RAM with VMware ESX 4.0 U1 No other VMs resident on this physical server VMTools installed SiteScope Configuration Tested Each SiteScope monitors: 33 SUN remote servers 2 Linux remote servers ~100 servers in domain (Microsoft Windows Resources Monitor) 696 Microsoft Windows remote servers Around 8880 monitors of the following type were created on each SiteScope: CPU Memory DiskSpace Microsoft Windows Resources Microsoft Windows Event Logs Microsoft Windows Services State Microsoft Windows Performance Counters Ping Post Service UNIX Resources Around 900 monitor runs/min Use these minimum system requirements when installing SiteScope on VMware environments (note that these are recommendations based on a tested environment, and are not support limitations): Computer/Processor 4 Intel Xeon physical processors, 2 GHz each Operating System Microsoft Windows 2003 Standard/Enterprise SP1 (note that all operating systems supported on the physical server are supported on the VM server) Memory 4 GB Free Hard Disk Space 20 GB (Hard Disk speed: 7200 rpm) Network Card 1 physical gigabit Network Interface Card Java Plug-in (to view applets) Recommended: 1.6.0_14 or later Other Software VMTools must be installed Note: Monitor capacity and velocity can be significantly impacted by numerous factors including, but not limited to the following: SiteScope server hardware, operating system, patches, third-party software, network configuration and architecture, location of the SiteScope server in relation to the servers being monitored, monitor types and distribution by type, monitor frequency, monitor execution time, BSM integration, and Database Logging. The published maximums should not be assumed to be possible in every environment. Certified Configuration The following configuration has been certified in a high load environment for an installation of SiteScope that was integrated with BSM. This configuration replaces the recommended configuration that appears in the SiteScope Deployment Guide. Operating System Microsoft Windows Server 2003, Enterprise Edition Version: 5.2.3790 Service Pack 2 Build 3790 System Type x86-based PC CPU 4 Intel Xeon 5160 physical processors, 3 GHz each Total Physical Memory 16 GB Java Heap Memory 1024 MB Total Number of Monitors 16,000 Total Number of Remote Servers 1,250 Monitor Runs per Minute 2,000 Client System Requirements SiteScope client is supported by the following: All Microsoft Windows operating systems (including Microsoft Windows 7) using Microsoft Internet Explorer 7.x-8.0. Firefox 3.0x (certified on clients running on Windows environments only. HP SiteScope Support Matrices HP Business Service Management Integration Support Matrix HP SiteScope Version HP Business Service Management Version 9.00 8.0x 8.00 7.5x 7.0x SiteScope 11.00 √ (Recommended) √ √ √ Not supported HP Operations Manager Integration Support Matrix Integration Matrix HP Operations Manager for UNIX 9.0x HP Operations Manager for Windows 8.1x SiteScope 11.00 √ Certified √ Certified HP Software Support This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online. 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 2010 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 Open Source and Third-Party Software License Agreements document in the HP Product Manuals Web Site (http://h20230.www2.hp.com/selfsolve/manuals). 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 US trademark of Sun Microsystems, Inc. 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 (www.apache.org/). This product includes software developed by the JDOM Project (http://www.jdom.org/). If you have any comments or suggestions regarding this document, please send them by e-mail to SW-Doc@hp.com. © Copyright 2010 Hewlett-Packard Development Company, L.P.