HP SiteScope Release Notes for the Windows, Solaris, and Linux operating systems Software version: 11.13 Release date: July 2012 This file provides information about HP SiteScope 11.13. Documentation Updates Installation Prerequisites and Instructions Enhancement Request Fixes Bug Fixes Notes and Limitations System Requirements Support Matrices HP Software Support Legal Notices Note: The SiteScope Help provided with SiteScope 11.13 does not include information on new features or updates since SiteScope 11.10. For information on features added in SiteScope 11.12, see the What_New SiteScope 11.12 release notes in <SiteScope installation directory>\sisdocs\pdfs\ReleaseNotes11_x.htm. For information on features added in SiteScope 11.11, including EMS Common Event Flow, VMware Monitor Enhancements, VMware Capacity Management Solution Template, Amazon CloudWatch Metrics Integration, and Classic SiteScope Failover Solution, see the SiteScope 11.11 Documentation Updates PDF, available from <SiteScope installation directory>\sisdocs\pdfs\SiteScopeDocUpdates.pdf. 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 and Instructions Installation Prerequisites SiteScope 11.13 must be installed on top of SiteScope 11.10. It should be installed on standard SiteScope installations only (not on non-standard installations such as System Health or SiteScope Failover Manager). You can upgrade SiteScope 10.x or later versions directly to SiteScope 11.10 by exporting SiteScope configuration data using the Configuration Tool, and then install SiteScope 11.13. 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. When SiteScope 11.10 is installed on a UNC path (a UNC path is a requirement for SiteScope Failover Manager, Windows only), the patch install/uninstall prompts you to provide the UNC installation path log-on credentials. The patch (MSI) install executes its post-install/pre-remove logic scripts as user "NT AUTHORITY/SYSTEM". This user does not have a mapping to any UNC drive, and failure to provide the correct log-on credentials causes the patch installation to fail. The patch uses these credentials to create a mapping to the UNC installation path for user "NT AUTHORITY/SYSTEM" during the patch installation, and removes the mapping at the end of the installation. Installation Instructions Read all information in this section before starting the installation. Before installing SiteScope 11.13, it is recommended that you back up your current SiteScope installation directory and all of the subdirectories within the directory. Before installing SiteScope 11.13, make sure the SiteScope process/service has been stopped. If installing SiteScope on an Oracle Enterprise Linux environment, you must manually configure the environment before performing the installation. For details, see Installing SiteScope on Oracle Enterprise Linux. To install SiteScope 11.13 using a silent installation, follow the Silent Deployment Installation instructions below. To use SiteScope Failover (mirroring) solution, you should use the standard SiteScope installation, and follow the classic SiteScope Failover instructions in Using the Classic SiteScope Failover Solution below). If you already have SiteScope 11.10 installed, install SiteScope 11.13 by double-clicking the setup file and following the on-screen instructions. After installing SiteScope 11.13, restart SiteScope. If you do not yet have SiteScope 11.10 installed, install it according to the instructions in the HP SiteScope 11.10 Deployment Guide. After installing SiteScope 11.10, install SiteScope 11.13 by double-clicking the setup file and following the on-screen instructions. After installing SiteScope 11.13, restart SiteScope. After upgrading to SiteScope 11.13, you can import monitor configuration data from previous versions of SiteScope using the Configuration Tool. Installing SiteScope on an Oracle Enterprise Linux Environment Before SiteScope (64-bit) can be installed on Oracle Enterprise Linux 6.0 (64-bit), the following dependencies must be installed on the environment: glibc-2.12-1.25.el6.i686.rpm glibc-common-2.12-1.25.el6.i686.rpm nss-softokn-freebl-3.12.9-3.el6.i686.rpm libXau-1.0.5-1.el6.i686.rpm libxcb-1.5-1.el6.i686.rpm libX11-1.3-2.el6.i686.rpm You can install the dependencies, using the yum package manager provided in Oracle Enterprise Linux, by running the command: yum install -y glibc glibc-common nss-softokn-freebl libXau libxcb libX11 libXext These dependencies can be found in the default repositories (/etc/yum.repos.d) for all Red Hat-based systems. Silent Deployment Installation To install SiteScope 11.13 using a silent installation, run the installer from the command line with -i silent flag. (The oviinstallparams.ini (answers) file is not required, unlike in a regular installation.) For Windows: HPSiS1113_11.13_setup.exe -i silent For UNIX: HPSiS1113_11.13_setup.bin -i silent SiteScope 11.13 Rollback Instructions (Windows) To uninstall SiteScope 11.13, follow the instructions below. Stop the SiteScope service. Select Control Panel > Add/Remove Programs > Change or Remove Programs, and make sure the Show Updates option is selected to ensure that the service pack version is displayed beneath the root entry. Select HP SiteScope 11.13, click the Change/Remove button, and follow the uninstall wizard instructions. When the uninstall process is complete, restart the machine if requested. To uninstall SiteScope and any service packs installed on top of it: Stop the SiteScope service. From Control Panel > Add/Remove Programs > Change or Remove Programs, select HP SiteScope. When the uninstall process is complete, restart the machine if requested. SiteScope 11.13 Rollback Instructions (UNIX) To uninstall SiteScope 11.13, follow the instructions below. Stop SiteScope by running the stop shell script included in the /opt/HP/SiteScope. An example command line to stop the SiteScope is: /opt/HP/SiteScope/stop Run the uninstall command: In graphic mode: /opt/HP/SiteScope/Uninstall/HPSiS1113/setup.bin In console mode: /opt/HP/SiteScope/Uninstall/HPSiS1113/setup.bin -i console In silent mode: /opt/HP/SiteScope/Uninstall/HPSiS1113/setup.bin -i silent To uninstall HP SiteScope 11.10 and any updates installed on top of it, follow the instructions below. Stop SiteScope by running the stop shell script included in the <install_path>/SiteScope directory. An example command line to run the script is: SiteScope/stop If you work in X Windows mode, run the following command: /opt/HP/SiteScope/installation/bin/sis_uninstall.sh  If you work in console mode, you should:   1. Uninstall SiteScope 11.13 by running the command: /opt/HP/SiteScope/Uninstall/HPSiS1113/setup.bin -i console 2. Uninstall SiteScope 11.10 by running the command: /opt/HP/SiteScope/Uninstall/HPSiteScope/setup.bin -i console Using the Classic SiteScope Failover Solution The classic SiteScope Failover solution was reinstated in SiteScope 11.11 as an alternative to using the SiteScope Failover Manager solution for providing automated failover functionality. This enables you to choose the failover solution that best suits your needs. To change SiteScope to classic SiteScope Failover mode: 1. Open the SiteScope Configuration Tool (Start > Programs > HP SiteScope > Configuration Tool). 2. In the Introduction screen, select the Change to classic SiteScope Failover mode check box, and then click Next. 3. The Change to classic SiteScope Failover mode screen opens. Click Next to complete the change to classic SiteScope Failover operation. 4. Open a Web browser and direct it to open the SiteScope Failover instance. For example, http://localhost:8080/SiteScope. 5. In the left panel, select the Preferences context menu, and click General Preferences. In the Licenses section, click Select and select the SiteScope Failover (High Availability) license key file. 6. In the preferences menu section, click Failover Preferences. The Failover Preferences page opens. Enter the name or IP address and port of the primary SiteScope server and the login credentials as described in "Configuring Failover Preferences" in the HP SiteScope Failover Guide PDF. 7. Click Mirror Configuration Now to continue. SiteScope copies all the files over from the primary machine and restarts when the mirroring operation is complete. 8. After the failover has restarted, refresh your Web browser or redirect your browser to the SiteScope Failover address. If there are SiteScope user names and passwords defined on the primary SiteScope, enter the same user names and passwords to access the failover. For details on using classic SiteScope Failover, see the HP SiteScope Failover Guide PDF, available from <SiteScope installation directory>\sisdocs\pdfs\ClassicSiteScopeFailover.pdf. Note: To use SiteScope in classic SiteScope Failover mode, a valid SiteScope Failover license file is required. If you do not have a valid license file, you can submit a request to renew or upgrade your license using the HP License Key Delivery Service site. If you want to configure HP Operations Manager Integration for SiteScope with a High Availability option, the classic SiteScope Failover solution is recommended. Support for HP Operations Manager (HPOM) metrics integration with Classic SiteScope Failover: Classic SiteScope Failover provides support for HPOM metrics integration. Note that SiteScope Failover reports metrics to its HP Operations agent (not to the primary's agent). Support for HP Operations Manager (HPOM) event integration with Classic SiteScope Failover: To enable classic SiteScope Failover support for HPOM event integration, perform the steps in "How to Enable SiteScope to Send Events to HPOM or BSM" in Using SiteScope in the SiteScope 11.10 help, both for the primary SiteScope and for the SiteScope Failover. Event flow and host discovery flow work without any additional steps. For the Monitor Discovery integration, follow the steps in "How to Enable the SiteScope Monitor Discovery Policy" in Using SiteScope in the SiteScope help for the primary SiteScope only. Enhancement Request Fixes Description CR ID Area The Web Service monitor reports "round trip time" in seconds instead of milliseconds. QCCR1I71089 Monitors Alert Reports now include all alerts, including alerts from parent groups that target the selected object. QCCR1I55656 Reports Bug Fixes Description CR ID Area Fixed issue when using the Log File monitor with Server-side processing via SSH v2 of the monitor failing when its content match was a non-English string (the monitor ignored the UNIX remote server's encoding). QCCR1I40747 I18N/Monitors Fixed issue of start/stop scripts not working on SiteScope running on Solaris in a Japanese environment. QCCR1I61709 Installation Fixed issue when configuring downtime in BSM of data not being read correctly on the SiteScope-side (alerts are not being disabled on SiteScope) by entering a downtime description in BSM. QCCR1I72946 Integration - BSM Fixed issue when SiteScope is integrated with HP Operations Manager for Windows of Operations Manager being unable to show SiteScope groups and monitors if other groups and monitors exist with the same name. QCCR1I69284 Integration - HPOM events By design, the SiteScope monitor history view is unavailable when integrating SiteScope with Performance Center/LoadRunner. To have SiteScope log monitor information and be able to run reports from SiteScope, the SiteScope for Load Testing version must be removed and a regular version of SiteScope must be installed instead. QCCR1I70552 Integration -Performance Center/LoadRunner Fixed issue of Database Query monitor returning: "timer already cancelled" error. QCCR1I64311 Monitors Fixed issue with DNS monitor of not having a value for the status condition in the Indicator State and Severity field when integrated with BSM. QCCR1I71614 Monitors Fixed issue with File monitor remaining in Good status after the monitored file has been deleted. QCCR1I68793 Monitors Fixed issue with FTP monitor of monitor not disconnecting from the session when the SFTP protocol is used. QCCR1I70020 Monitors Fixed issue of HP iLO Monitor not working because the ILO_remote<*>.xml file in <SiteScope root directory>\templates.applications is created with invalid XML characters. QCCR1I66211 Monitors Fixed issue with Log File monitor of the last read position being reset to 0 if a timeout occurs before file size is retrieved from a remote UNIX server. QCCR1I72477 Monitors Fixed issue with Log File monitor of monitor returning a java.lang.NullPointerException against RHEL 5.7 servers (the value of the _logFileMonitorMaxNoCacheSize property was increased to 10000000 in the <SiteScope root directory>\groups\master.config file. QCCR1I69660 Monitors Fixed issue with Log File monitor of Quick report displaying n/a in the Matches column when log entries matches are found. QCCR1I66462 Monitors Fixed issue of Log File monitor returning an error if the file does not exist and the No error if file not found option is selected. QCCR1I62861 Monitors Fixed issue of the Log File monitor displaying incorrect variable data when there are no content matches. QCCR1I67528 Monitors Fixed issue with Memory monitor of monitor displaying incorrect calculation for % memory utilization on environments with a large amount of available memory (160+ GB RAM). QCCR1I69654 Monitors Fixed issue with Memory monitor of monitor reporting incorrect value for the pages/sec metric. QCCR1I69724 Monitors Fixed issue with Memory monitor when running on an AIX environment of monitor reporting "0" for unavailable counter values instead of an error (such as "n/a"). QCCR1I70801 Monitors Fixed issue of Service monitor failing with message: "error while performing inpage operation. QCCR1I68707 Monitors When defining a step for a URL Sequence monitor template, a variable included in the URL field causes step creation to fail, since the results/content of the step is used as data for the next step. During step validation, an informative message is now displayed if such a variable is used. QCCR1I71531 Monitors Fixed issue of URL monitor reporting an error status ("problem while sending data to URL") after the error had been resolved. QCCR1I58175 Monitors Fixed issue with VMware Host/Performance monitor of no reconciliation of VM data in RTSM/CMDB when using both VMware Host and VMware Performance monitors. QCCR1I71041 Monitors Fixed issue with VMware Performance monitors not reporting virtual machines that do not have a defined IP address in the vCenter repository. QCCR1I64875 Monitors Web Service monitor. Fixed issue of not being able to get the content of a WSDL URL through an HTTP proxy by configuring the following properties in the <SiteScope root directory>\groups\master.config file: _webServiceDefaultProxyUrl _webServiceDefaultProxyUser (if Proxy server user name is required to access the URL) _webServiceDefaultProxyPassword (if Proxy server password is required to access the URL) For example: _webServiceDefaultProxyUrl=http:\\proxy.mycompany.com:3128 _webServiceDefaultProxyUser=admin _webServiceDefaultProxyPassword=p@ssw0rd QCCR1I67701 Monitors Fixed issue with SiteScope restarting itself if it takes more than 5 minutes to start up. QCCR1I67673 Performance Fixed issue of being unable to generate an Alert Report from all levels of the hierarchy in the SiteScope tree. QCCR1I65249 Reports Fixed issue of license header summary only being displayed in Quick and Management Reports for an evaluation license, or when the license is invalid or has expired. QCCR1I59194 Reports Fixed issue of Dashboard Settings button being unavailable when opening SiteScope from SAM Administration. QCCR1I70268 SAM Administration When SiteScope is integrated with SiteMinder, you can avoid being logged out of SiteScope after 30 minutes of browser inactivity by changing the _keepAliveFromJSP= property to =true in the master.config file. QCCR1I70103 SiteMinder Integration Fixed issue of not able to log in to SiteScope using LDAP after activating the failover system using the SiteScope Failover Manager (shared drive architecture) solution. QCCR1I70292 SiteScope Failover Fixed issues when publishing changes to templates of the View Differences link being displayed in the Review Compliancy page for objects that did not contain content changes. QCCR1I65937 Templates Fixed issue of the Web Service tool (test_event_client.bat) using a hardcoded port; the port is now a parameter which should be defined when running the tool. QCCR1I69736 Tools Fixed issue of not being able to restart SiteScope after upgrading from SiteScope 11.11 to 11.12. QCCR1I68143 Upgrade Notes and Limitations Description CR ID Area When generating an Alert report from a sub-group, the report does not include alerts for the parent group (indirectly associated alerts). Only alerts for the specific sub-group are displayed. Workaround: Run the Alert report from the parent group. QCCR1I50620 Alerts 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 SiteScope applet must have the Keep temporary files on my computer selected in your client Java configuration (Control Panel > Java > General tab > Temporary Internet Files > Settings). Failing to do so will result in: "NoClassDefFound" exception and applet loading will fail. If security issues require it, delete the temporary files manually when you finish using the SiteScope applet: 1). Close the SiteScope applet. 2). Select Start > Control Panel > Java > General tab. 3). In the Temporary Internet Files section, click Settings and then click Delete Files. QCCR1I37003 Configuration If the SiteScope user interface is not refreshing (repainting), you should upgrade your version of JRE to 1.6.0_27.   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".   Configuration The following configuration file templates will be deprecated from the Operating System template group (<SiteScope root directory>\templates.os) in some later versions of SiteScope: Digital.config SGI.config Tru64.config   Configuration Files The Dashboard column layout in the Monitor History view cannot be saved during user sessions. QCCR1I20806 Dashboard 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 When viewing the online help in an Internet Explorer 8.x browser (32 or 64-bit version), the step numbering might not be incremented. Workaround: 1). Open the html file in a text editor. 2). Search for <div><li> 3). Delete the div tag: <div>. 4). At the end of the same line, delete the </div> (from </li></div>). For example, change: <div><li>Text for step 1</li></div> to <li>Text for step 1</li> (The <div> tags around the <ol>...</ol> tags should remain) 5). Save the html file.   Documentation When using Global Search and Replace, unable to replace Credentials values that are used in remote servers and monitors. QCCR1I42998 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 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 unavailable. QCCR1I36248 Global Search and Replace Unable to display non-English characters in the counters list when configuring the Microsoft IIS Server monitor. QCCR1I21171 I18N Non-English strings are not supported when using the post installation Configuration Tool wizard on a Linux environment. Workaround: Run the post installation Configuration Tool in console mode with parameter "-i console". QCCR1I50695 I18N 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 Run results for some monitors are shown according to the server locale or in English, instead of according to the client locale. QCCR1I30190 I18N When using the Microsoft Windows Resources monitor in a non-English locale, the monitor counters and run status summary is not readable. Workaround: Configure the monitor to use the Direct registry queries collection method. QCCR1I54985/ QCCR1I54978 I18N SiteScope log files do not support Unicode characters-all non-English characters appear corrupted in the logs. Workaround: Use a SiteScope server installed on a corresponding operating system locale. For example, use SiteScope installed on a Japanese Windows operating system for a Japanese locale. QCCR1I35306 I18N When exporting the sitescope.zip package from BSM (Admin > RTSM Administration > Administration > Package Manager) to a local server and modifying topology scripts, make sure the package deployed back to the server consists only of the modified files under the sitescope/discoveryScripts folder. Workaround: If you already deployed the sitescope.zip package with all its contents and you encounter topology reporting problems, perform the following: 1). Stop SiteScope. 2). Delete the content from the %sitescope_home%/discovery/hsqldb folder. 3). Restart SiteScope. 4). Resynchronize topology (in SiteScope, select Preferences > BSM integration Preferences > BSM Preferences Available Operations and click Re-Synchronize. QCCR1I73658 Integration - BSM 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 HPOM 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 - HPOM/OMi Integration When installing the HP Operations agent during a SiteScope installation on UNIX, the installation might hang if the agent is already installed. Workaround: Before installing SiteScope, stop the HP Operations agent using the command: #ovc -kill QCCR1I51731 Installation - HPOM/OMi Integration If there is a problem signing and installing the local policies when configuring Operations Manager event integration, the installation hangs. Workaround: Restart your HP Operations agent, or your SiteScope server. QCCR1I51861 Installation - HPOM/OMi Integration When installing SiteScope from AutoRun, the SiteScope 32-bit version is installed even if you selected the 64-bit installation. Workaround: Close AutoRun, and install SiteScope from the installation DVD by running Windows_Setup\64Bit\HPSiteScope_11.10_setup.exe. QCCR1I59865 Installation and Upgrade SiteScope might fail to install on a Windows machine if the environment variables %TEMP% and %TMP% point to a directory path that contains an empty space. For example, C:\Documents and Settings\Default User\Local Settings\Temp. Workaround: Change the environment variables %TEMP% and %TMP% to point to a directory path that does not contain an empty space. For example, C:\Temp. QCCR1I52241 Installation and Upgrade 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 Installation and Upgrade 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: Install JRE 1.6.0_14 or later and configure you browser to use this version of JRE. 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. 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 Installation on Turkish Locale Causes an Exception: If you attempt to run the SiteScope 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. Workaround: 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. QCCR1I55818 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 If uninstalling SiteScope fails, restart the SiteScope server, and then try to uninstall again. QCCR1I57144 Installation and Upgrade During the SiteScope 11.11 installation, the customized port numbers might be reset. Workaround: To restore the customized ports: 1). Open the backup server.xml file (the path is displayed in the popup window during installation). 2). Copy the customized port data from the backup server.xml file to the new server.xml file (the path is displayed in the popup window during installation). 3). Restart SiteScope. QCCR1I61004 Installation and Upgrade When upgrading to SiteScope 11.10, the templates.os files are overwritten by the upgraded files, including any files you customized in a previous version of SiteScope. If in a previous version you added new configuration files to the templates.os folder, these files are not affected by the upgrade and remain in the folder. Workaround: To restore any customizations that you made to the templates.os files: 1). Make a backup of the original SiteScope 11.10 configuration files, since some configuration files from earlier versions of SiteScope are incompatible with 11.10, and might not work after you make changes to them. 2). Unzip the backup files that were made prior to the upgrade by exporting SiteScope configuration data using the Configuration Tool. 3). Manually make changes to the new files.   Installation and Upgrade Historical data is lost in SAM reports after host DNS resolution if the host is resolved with another name (Topaz ID). Workaround: Manually update the BSM database by searching for the old Topaz ID and replacing it with the new ID for historical data. QCCR1I35093 Integration - BSM 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 Integration - BSM If you upgrade to BSM 9.10, 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(added in 11.00 -) Integration - BSM 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 Integration - BSM 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 Integration - BSM To improve performance, SiteScope uses a topology cache when sending topology data to the BSM's RTSM (Run-time Service Model). 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 panel, click Re-synchronize.   Integration - BSM 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.   Integration - BSM 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 panel, click Re-synchronize.   Integration - BSM When accessing SiteScope from System Availability Management Administration using Internet Explorer 7, a 408 Request Timeout error is displayed. Workaround: To be able to login into SiteScope from BAC/BSM, you must enable the option in Internet Explorer to allow session cookies. 1) In Internet Explorer, select Tools > Internet Options > Privacy tab > Advanced button. 2) Select Override automatic cookie handling, make sure First-party cookies and Third-party cookies are set to Accept, and select Always allow session cookies. QCCR1I49144 Integration - BSM When adding threshold conditions to a monitor that has multiple CIs (SAP CCMS, SAP Work Processes, Siebel Application Server, Siebel Web Server, Solaris Zones, or VMware Performance monitor), the Indicator State and Severity value disappears for all threshold conditions, except for the last condition added. Workaround: Add and configure threshold by threshold, instead of by adding and configuring each threshold individually. When you save the monitor, indicator values for all threshold conditions are displayed. QCCR1I49550 Integration - BSM Monitors do not report to BSM if you: 1). Create a monitor with custom topology, and click Save. 2). Clear the Report monitor and related CI topology check box (in HP Integration Settings), and click Save. 3). Select the Report monitor and related CI topology check box, and click Save. Workaround: Make any change in the monitor properties (for example, change a letter in the monitor name and then change it back), and then click Save. QCCR1I56509 Integration - BSM If you run the node discovery policy when SiteScope is integrated with Operations Manager for Windows 9.0 (HPOM) and the nodes that SiteScope reports exist in HPOM, the node definitions are removed from HPOM and replaced with an empty node object. Workaround: Install the relevant HPOM patch (check the Patches page on the HP Software Support site. After the patch is installed, the HPOM server ignores platform updates from SiteScope. QCCR1I54342 Integration - HPOM/OMi After installing the HP Operations agent, it is recommended to restart the SiteScope server. QCCR1I51638 Integration - HPOM/OMi When SiteScope is installed on the same machine as HP Operations Manager for Windows 9.x (HPOMW), the discovery policy integrations (node and monitor service discovery) do not work and a JVM error file is generated. Note that running the integration batch files from a command line returns the discovery XML results to the console, while running it from the agent agtrep command fails. Workaround: Manually configure the integration scripts to work with Java 32 according to the SiteScope installation. For SiteScope 32-bit: 1). Install SiteScope 32-bit on a machine with HPOMW 9.0 64-bit. 2). Edit <SiteScope root>\integrations\om\bin\om_discovery_hosts.bat by replacing run_api_call_om.bat with run_api_call.bat. 3). Edit <SiteScope root>\integrations\om\bin\om_discovery_monitors.bat by replacing run_api_call_om.bat with run_api_call.bat. For SiteScope 64-bit: 1). Install SiteScope 64-bit on a machine with HPOMW 9.0 64-bit. 2). Download Java 32-bit. 3). In the <SiteScope root>\integrations\om\bin folder, make a copy of the run_api_call.bat file, and name it run_api_call_32.bat. 4). Open run_api_call_32.bat in a text editor, and set the java location to the 32-bit location from where you downloaded it. 5). Edit <SiteScope root>\integrations\om\bin\om_discovery_hosts.bat by replacing run_api_call_om.bat with run_api_call_32.bat. 6). Edit <SiteScope root>\integrations\om\bin\om_discovery_monitors.bat by replacing run_api_call_om.bat with run_api_call_32.bat. QCCR1I58340 Integration - HPOM/OMi When SiteScope is integrated with HP Operations Manager (HPOM), the HP Operations agent included with SiteScope requires an OS Instance Advanced license. Nodes registered in HPOM through the node discovery policy might also (falsely) request a Target Connector license. For details on HPOM licensing requirements, refer to the HPOM documentation.   Integration - HPOM/OMi HP Operations Manager 9.0 for Windows 64-bit console does not support the tree services view (when HPOM is integrated with SiteScope). The tree view is available in the left pane, but not in the service map on the right.   Integration - HPOM/OMi When reporting metrics data to the HP Operations agent in a loaded environment, the system might run out of ports. In SiteScope Health, an error is displayed in the Log Event Checker monitor for the .*Failed to report data to HP OM Agent.* counter. The following error is displayed in the oa_metric_integration.log: "ERROR - Failed to report data to /Hewlett-Packard/OpenView/Coda/ IO error while gettingSingle Object;Address already in use: connect". Workaround: Increase the upper range of ephemeral ports and reduce the client TCP/IP socket connection timeout value in Windows. For details, see http://msdn.microsoft.com/en-us/library/aa560610%28v=bts.20%29.aspx.   Integration - HPOM/OMi When sending events in third party applications to BSM through the HP Operations Manager Event Integration, the sub-component might not be visible in the Operations Management Event Browser. QCCR1I60083 Integration - HPOM/OMi / Integration Monitors All events (on the same counter) that are forwarded from SiteScope to HPOM, are marked as a duplicate of the first event (of the counter) even if their severity is different. Workaround: In Preferences > Common Event Mappings, select Default Settings > Edit Default Monitor Event Mapping, and add ":<<severity>>" to the Key field. QCCR1I64072 Integration - HPOM/OMi 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 When exporting a configuration that contains EMS integration monitors, the scripts (<SiteScope root>\conf\ems\scripts) are exported with absolute path links. When importing this configuration to a SiteScope installed in a different directory, these scripts are unavailable. Workaround 1: Install SiteScope 11.1x into the same directory structure as used in the previous SiteScope installation. Workaround 2: Install SiteScope 11.1x into any supported directory, and then copy scripts from <SiteScope root>\conf\ems\scripts into the same path where they were located on source environment.   Integration Monitors 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 When SiteScope 11.01 is integrated with LoadRunner 9.52, unable to create the Microsoft Windows Resources monitor from the LoadRunner side with the default list of the counters. Workaround: Add the counters manually. QCCR1I49652 LoadRunner Integration 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 SiteScope is unable to retrieve instances and counters from a Microsoft SQL Server 2008. Workaround: You can monitor Microsoft SQL Server 2008 using the Microsoft Windows Resources monitor. QCCR1I53756 Monitors Date and time format for monitor status is shown according to the server locale instead of the browser locale. QCCR1I41203 Monitors The following Virtualization monitors do not support VM instance-based information on HPOM integration events and metrics: VMware Performance, VMware Host CPU/Memory/Network/State/Storage, Solaris Zones, and Microsoft Hyper-V monitors. All HPOM events or Performance Manager metrics generated by these monitors are associated with the monitored target (such as ESX or vCenter), instead of with the actual VM embedded within the relevant metric. Note: When integrating with BSM, events and metrics are correlated with the correct VM CI, based on CI resolution. QCCR1I54666 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 Disk Space monitor. Due to a limitation with WMI, the WMI connection method returns incorrect results when this monitor is used on Windows Server 2008. Workaround: To monitor Windows Server 2008 using WMI, you should install the Microsoft hot fix (http://support.microsoft.com/kb/961435/en-us) on the target Windows system. QCCR1I34224 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 DNS monitor. The DNS Monitor does not work on a Microsoft Windows 2008 Japanese environment. Workaround: In Preferences > Infrastructure Preferences > Monitor Settings, select the Use DNS Java library option. QCCR1I52457 Monitors FTP monitor. Summary status for the FTP monitor is shown according to the server locale instead of the browser locale. QCCR1I41200 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 HP iLO monitor. SiteScope does not support HP iLO version 3. QCCR1I52088 Monitors JMX monitor. The JMX Monitor CPU time measurement reports too long a value which can cause errors in the BSM database field which does not accept values larger than 13 digits. QCCR1I32451 Monitors Log File monitor. The Log File monitor is unable to monitor a file through symbolic links on Linux. QCCR1I39836 Monitors Log File/Microsoft Windows Event Log monitor. Monitor does not run again if it detects an error when Verify error is selected in the Monitor Run Settings panel. QCCR1I64049 Monitors Memory monitor. WMI returns incorrect values for the memory used % and MB free counters when the WMI connection method is used on a Windows Server 2008. This is due to an issue with WMI (not SiteScope).   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 (64-bit). QCCR1I34285 Monitors Microsoft Windows Resources monitor. Unable to receive measurements when monitoring a remote server that contains non-English characters from an English machine using NetBIOS or agent-based SSH. Workaround: Use the same operating system language on both systems. QCCR1I33005 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 Monitor Tree. If there is a large space between group containers in the SiteScope monitor tree, refresh your browser.   Monitors Oracle Database monitor. If you have created Oracle Database monitors in SiteScope and afterwards you connected to BSM and you want the monitor and its related topology to be reported to BSM, you must enter values for the database machine in the Name and Server fields and select the Report monitor and related CI topology check box in HP Integration Settings > BSM Integration Data and Topology Settings. QCCR1I27152 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 Service monitor. Due to a Solaris limitation, SiteScope is only able to display service names up to a maximum length of 80 characters. QCCR1I46193 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 panel, 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 VMware Host State monitor. The incorrect ESX version is returned by the vCenter and displayed by the VMware Host State monitor. When the VMware Host State monitor monitors ESX directly (not via vCenter), the ESX version is correct. QCCR1I55409 Monitors VMware Performance monitor. The CPU shares counter in the resource pool (Resource Pool > summary >config > cpuAllocation > shares > shares) displays a value of "0" instead of the actual number of shares allocated. This value is only set if level is set to custom. If level is not set to custom, this value is ignored. For more details, see the VMware support site (http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.SharesInfo.html). QCCR1I59395 Monitors Inconsistency in VMware Host and VMware Performance monitor topology causes CI duplication in RTSM. QCCR1I59271 Monitors 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 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 Unable to send a Server-Centric report by email using the Export option. Workaround: Save the report as an html file, and then send it manually. QCCR1I57160 Reports In SiteScope 11.10, the VMware Performance and VMware Host monitors displayed the "%" symbol in the SiteScope Dashboard for percentage metrics. Since the "%" symbol is not supported by all browsable monitors and cannot be displayed in SiteScope reports, it was removed from the Dashboard in SiteScope 11.11. The "%" symbol is still displayed in the monitor run status. QCCR1I60974 Reports All SiteScope Web Service API methods that are not protected by a user name and password have been deprecated. All API methods with user and password authentication have been renamed and now have an Ex suffix (for example, enableGroupEx) to avoid the same method names being used with different parameters. QCCR1I4859 SiteScope APIs When SiteScope is registered with BAC/BSM, classic SiteScope Failover does not resend the SiteScope profile topology after the primary SiteScope fails. Workaround: Force SiteScope Failover to resend all topology data to BAC/BSM. In Preferences > Integration Preferences > BSM Preferences Available Operations, click Re-synchronize. Resending the profile topology by SiteScope Failover is important for viewing PMI reports in BSM. QCCR1I60203 SiteScope Failover PMi fails to graph data from Failover SiteScope when working with the classic SiteScope Failover solution. QCCR1I60205 SiteScope Failover 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 Copying and pasting from SiteScope 11.1x 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 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 The Event Log Tool is not available when configuring the Microsoft Windows Event Log monitor from the Use Tools button. The tool is still available from Tools > Operating System Tools > Event Log Tool. QCCR1I56272 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 If you encounter the following error when using the Database Connection Tool to connect to an SQL server database: "Exception Message: [mercury][SQLServer JDBC Driver]NTLM (type-2) Authentication was requested but the required DDJDBCx64Auth04.dll was not found on the path specified by the java.library.path system property." Workaround: Use a third-party driver. Microsoft's JDBC driver does not exhibit this issue, nor does JTDS. Both these drivers can operate in wrapped and unwrapped modes and support Windows Integrated Authentication (http://msdn.microsoft.com/en-us/data/aa937724.aspx).   Tools System Requirements Below are the minimum system requirements and recommendations for running SiteScope, based on the various supported operating systems. System Requirements for Windows System Requirements for Solaris System Requirements for Linux System Requirements for VMware Certified Configuration Client System Requirements System Requirements for Windows Computer/Processor 800 MHZ or higher Operating System 32-bit Support: Microsoft Windows 2003 SP1, SP2 Standard/Enterprise Edition Microsoft Windows Server 2003 R2 SP1, SP2 Enterprise Edition Microsoft Windows Server 2008 SP2 Standard/Enterprise Edition host Microsoft Windows Server 2008 SP2 Standard/Enterprise Edition Hyper-V guest (32 or 64-bit) hosted on Windows Server 2008 R2 64-bit Support: Microsoft Windows Server 2003 SP2 Standard/Enterprise Edition Microsoft Windows Server 2008 SP2 Enterprise Edition Microsoft Windows Server 2008 R2 Standard/Enterprise Edition without Hyper-V Microsoft Windows Server 2008 R2 Standard/Enterprise Edition with Hyper-V enabled Microsoft Windows Server 2008 R2 Hyper-V guests (64-bit) hosted on Windows Server 2008 R2 Standard/Enterprise Edition Microsoft Windows Server 2008 SP2 Standard/Enterprise Edition Hyper-V guests (64-bit) hosted on Windows Server 2008 R2 Standard/Enterprise Edition Memory 1 GB minimum (2 GB+ recommended) Free Hard Disk Space 2 GB or more (10 GB+ recommended) System Requirements for Solaris Computer/Processor Sun 400 MHz UltraSparc II Processor or higher Operating System Solaris 9 (32-bit) with latest recommended patch cluster Solaris 10 (32 or 64-bit) with latest recommended patch cluster Memory 1 GB minimum (2 GB+ recommended) Free Hard Disk Space 2 GB or more (10 GB+ recommended) System Requirements for Linux Computer/Processor 800 MHZ or higher Operating System Oracle Enterprise Linux 6.0 (64-bit) Note: The environment must be manually configured before installing SiteScope. For details, see Installing SiteScope on Oracle Enterprise Linux. Red Hat ES/AS Linux 4, 4.3, 5.2, 5.4 (32-bit) Red Hat ES/AS Linux 5.5 (32 or 64-bit) Note: Red Hat Linux 9 with Native POSIX Threading Library (NPTL) is not supported. Memory 1 GB minimum (2 GB+ recommended) Free Hard Disk Space 2 GB or more (10 GB+ recommended) 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 vSphere 4.1 Supported Environments Only VMware VirtualCenter 2.x VMware ESX 3.x, 4.0 VMware ESX 2.5 via VirtualCenter 2.x VMware ESX 3.x via VirtualCenter 3.x VMware vCenter Server 4.0 VMware ESXi 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 Note: The resources allocated to the SiteScope VM should not be shared with other VMs. SiteScope Configuration Tested 750 remote servers 9000 monitors 900 monitor runs per minute 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 Other Software VMTools must be installed Certified Configuration The following configuration has been certified in a high load environment for an installation of SiteScope that was integrated with BSM. Operating System Microsoft Windows Server 2003 SP2 Enterprise Edition (32-bit) Microsoft Windows Server 2003 SP2 Enterprise Edition (64-bit) System Type x86-based PC ACPI Multiprocessor x64-based PC CPU 4 Intel Xeon 5160 physical processors, 3 GHz each 4 Intel Xeon 5160 physical processors, 3 GHz each Total Physical Memory 16 GB 16 GB Java Heap Memory 1024 MB 2048 - 3072 MB Total Number of Monitors 16,000 24,000 Total Number of Remote Servers 1,250 2,500 Monitor Runs per Minute 2,000 3,500 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). Java Plug-in to view applets: JRE 6 or 7. Note: Later updates may be supported, but may require a workaround. For example, you must perform one of the following workaround steps when using Java 7 update 51: Changing the security level in the Java Control Panel to Medium. Adding the SiteScope server site (http://<server_name>:8080/SiteScope) to the Exception Site List in the Java Control Panel. Creating a "Deployment Rule Sets" jar and deploying it on the client machine. For details, refer to the Oracle Documentation. HP SiteScope Support Matrices HP Business Service Management Integration Support Matrix HP SiteScope Version HP Business Service Management Version 9.10 9.0x 8.0x 7.5x 7.0x SiteScope 11.13 Supported (Recommended) Supported Supported Supported Not supported HP Operations Manager Integration Support Matrix HP Operations Manager Version SiteScope 11.1x Integration Event Integration Node Discovery Integration Monitor Discovery Integration Templates Integration HP Operations Manager for Windows 8.1x (with patch OMW_00071) Supported Supported Supported Not supported HP Operations Manager for Windows 9.0 Supported Supported Supported Not supported HP Operations Manager for Linux/ HP-UX/Solaris 9.0 Supported Not supported Supported Not supported HP Operations Manager for Linux/ HP-UX/Solaris 9.10 Supported Supported with patch 9.10.200 or later Supported Supported with patch 9.10.210 and hotfix QCCR1A125751 or patches later than 9.10.210 HP Operations Agent Support Matrix Operating System HP SiteScope Version HP Operations Agent Version Windows 32/64-bit Linux 32/64-bit Solaris 32/64-bit 11.13 08.60.501 HP Network Node Manager i (NNMi) Support Matrix Integration Supported Versions Event Integration SiteScope version 11.10 or later NNMi version 9.10 or later Metrics Integration SiteScope version 11.10 or later NNMi version 9.10 or later NNM iSPI Performance for Metrics version 9.10 or later 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 2012 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. Intel®, Pentium®, and Intel® Xeon® are trademarks of Intel Corporation in the U.S. and other countries. iPod is a trademark of Apple Computer, Inc. Java is a registered trademark of Oracle and/or its affiliates. Microsoft®, Windows®, Windows NT®, and Windows® XP 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 2012 Hewlett-Packard Development Company, L.P.