HP Operations Smart Plug-in for SAP Release Notes

for HP Operations Manager for Windows® operating system

Software Version: 12.05

Publication date: June 2013

This document provides an overview of the changes made to the HP Operations Smart Plug-in for SAP (SPI for SAP) 12.05 for HP Operations Manager (HPOM) for Windows 9.00 version. Release notes contain important information not included in the product manuals or Online Help.

What's New in This Release?
Documentation Updates
Installation Notes
Known Problems and Workarounds
Enhancements and Fixes
Verified Environments
Documentation Errata
Local Language Support
Support
Legal Notices

Hidden Text

To simplify navigation, individual Enhancement and Fix items are hidden until you click the link to expand the collapsed text.

Hidden text example

This text was hidden. Now it is visible. Click the link to hide the text.

Hidden text does not print. To print this document, you can expand selected links before you print or click the Show All button to expand all links. If you use Assistive Technology Tools, activate the Show All button to display all text.

What's New in This Release?

This version of the SPI for SAP includes new features, feature enhancements, and other changes.

Enhanced Support for SAP Solution Manager 7.1

The SPI for SAP supports SAP Solution Manager 7.1 Technical Monitoring in addition to existing functionalities. The SPI for SAP support for Solution Manager 7.1 enables you to forward the SAP Solution Manager 7.1 alerts to the HPOM console. For more information about SPI for SAP support for Solution Manager 7.1, see SPI for SAP to Support Solution Manager 7.1 section in HP Operations Smart Plug-in for SAP Online Help pdf.

New Policies, Policy Group, and Solmanrfc Configuration File

The SPI for SAP contains new policy group, policies, and solmanrfc.cfg configuration file. You must configure the SPI for SAP to enable forwarding alert messages from Solution Manager to HPOM. For more information about configuring SPI for SAP policies and solmanrfc.cfg configuration file, see Configuring the SPI for SAP section in HP Operations Smart Plug-in for SAP Online Help pdf.

Documentation Updates

The first page of this release notes document contains the following identifying information:

To check for recent updates or to verify that you are using the most recent edition, visit the following URL:

http://h20230.www2.hp.com/selfsolve/manuals

  1. In the Product list, click the product name.
  2. In the Version list, click the version number.
  3. In the OS list, click the OS type.
  4. In the document list, click the document title.
  5. To retrieve the document, click Open or Download.

NOTE: To view files in PDF format (*.pdf), Adobe Acrobat Reader must be installed on your system. To download Adobe Acrobat Reader, go to the following URL: http://www.adobe.com

Installation Notes

Instructions to install the patch are available in the patch text.

SPI for SAP Transport Numbers

Known Problems and Workarounds

This release of the SPI for SAP contains the following Known Problems:

  1. SPI for SAP Patch installer prompts for reboot:

    SYMPTOM: The SPI for SAP Patch installer prompts for reboot, but the installation does not require reboot.
    SOLUTION: Ignore the prompt for reboot. For more information about installing SPI for SAP Patch, see Patch Text.

  2. SPI for SAP Patch installer prompts for directory selection:

    SYMPTOM: During installation the SPI for SAP installer prompts for directory selection, but the SPI for SAP patch cannot be installed on non-default location.
    SOLUTION: Ignore the prompt for directory selection and click next to continue with patch installation. For more information, see QCCR1A161999.

  3. SPI for SAP instance license count scripts are not reporting correct instance numbers:

    SYMPTOM: SPI for SAP licensing scripts does not report correct instance numbers.
    SOLUTION: For more information, see QCCR1A163084.

  4. Help on ConfigFile button opens page with incorrect information:

    SYMPTOM: When you click the Help on Configfile button {SPI for SAP -> Policies -> global_solmanrfc -> global_solmanrfc (configFile)} in the Solution Manager policy config editor window, page opens with incorrect information.
    SOLUTION: To view the content related to solution manager configuration, see Configuring the SPI for SAP section in the HP Operations Smart Plug-in for SAP Reference, version 12.05. To download pdf version of help documents, go to: http://h20230.www2.hp.com/selfsolve/manuals. For more information, see QCCR1A162706.

  5. SAP GUI must be installed separately:

    SYMPTOM: The SAP GUI is needed for many operator-initiated actions defined in the SPI for SAP, but it is not part of the SPI for SAP installation media.
    SOLUTION: Install the SAP GUI on the HPOM management server and any remote consoles. The SAP GUI is included on the SAP Presentation CD. For more information, see Installing the SAP GUI section in HP Operations Smart Plug-in for SAP Installation and Configuration Guide.

  6. User Monitor values does not match the values in SAP transaction SM04:

    SYMPTOM: The number of logged in users reported by the collector does not match to the number of users reported in the SAP transaction SM04.
    SOLUTION: The collector counts the itouser as a fully logged-in user. Therefore, some differences may occur.

  7. Message duplication and slow performance if host configured twice:

    SYMPTOM: Monitors of type snapshot send duplicate messages to the message browser and the overall performance of the SPI for SAP is very slow.
    SOLUTION: Check to see if you entered a managed node twice in any of the configuration files, for example: once using a short host name (sapsystem) and once using a fully qualified name (sapsystem.domain.company.com). If there are two entries, the monitor binaries will open two connections to the SAP system for each monitor call, thus consuming more resources and sending messages twice.

    Each system must be configured only once in the configuration files, preferably with its fully qualified name.


  8. SPI for SAP creates service tree for each physical node in a SAP high-availability cluster:

    SYMPTOM: The HPOM for Windows service tree shows multiple subtrees for a virtual SAP instance inside a cluster, even though the new Host-Mapping feature is used to virtualize the cluster instance. A subtree is shown for each physical node of the cluster.
    SOLUTION: In the current release, there is no solution to this problem.

  9. Service discovery fails to discover SAP instances on Microsoft Windows managed nodes:

    SYMPTOM: If the service-discovery tool, r3sd, is running under the system account and the SAP installation directory is specified in UNC syntax. For example, \\server..., SAP instances are not discovered for managed nodes running Microsoft Windows, and the R3-Info tool completes its run but does not produce any output.
    SOLUTION: Either specify a local path to the SAP installation using the environment variable SAPOPC_SAPPROFILEDIR (only possible on SAP central instances), or configure the HPOM agent to run under a different user account to enable it to access network paths using the UNC notation.

  10. Multiple thresholds not allowed with r3monjob:

    SYMPTOM: You cannot configure r3monjob to send a WARNING message if the run time for a batch job exceeds 5 minutes and then a CRITICAL message if the run time for the same batch job exceeds 10 minutes.
    SOLUTION: With the current version of the SPI for SAP, it is not possible to configure more than one threshold with the same alert type for a given batch job.

  11. Policies are not removed from the management server after removing the SPI for SAP:

    SYMPTOM: SPI for SAP policies resides on the management server even after you remove the SPI. These policies can be accessed from the Agent policies grouped by type group.
    SOLUTION: After removing the SPI for SAP, remove the policies manually from the Agent policies grouped by type group.

  12. Multiple instances are not supported on SAP Netweaver 7.0:

    SYMPTOM: Multiple instances are not supported on SAP Netweaver 7.0 .
    SOLUTION: The SAP Netweaver 7.0 java instance monitoring is possible through remote monitoring, but not multiple instance support. For more information, see QCCR1A91931.

  13. Files missing when the Version Verify tool is run:

    SYMPTOM: Few files are missing when you execute the Version Verify tool.
    SOLUTION: For more information, see QCCR1A99193.


Enhancements and Fixes

This release of the SPI for SAP contains the following enhancements and fixes.

NOTE: Some information is available only on the HP Support web site, which requires an HP Passport login ID for access. For more information about HP Passport IDs, see Support.

To display information about a problem that has been fixed for this release, click the appropriate reference-number link in the following list:

Enhancements

  • QCCR1A156003 - SPI for SAP Integration with SAP Solution Manager 7.1.
  • Fixes

    1. QCCR1A144841 - Wrong document for Selecting the Performance-data Source.
    2. QCCR1A145148 - java.lang.NoClassDefFoundError when configuring NW monitoring.
    3. QCCR1A128012 - Document clarification about required JAR files for NW monitoring.
    4. QCCR1A142782 - r3instcon fails after successful transfer of files.
    5. QCCR1A147146 - NODE line in SiteConfig requires exactly one space around the = sign.
    6. QCCR1A148796 - r3mondisp fails in dpmon -help for 2nd and subsequent SIDs.
    7. QCCR1A148797 - r3monsec comparison is not correct.
    8. QCCR1A153709 -r3mondisp and r3status coredump on Solaris server (cluster).
    9. QCCR1A153825 - Error from ovosysdetect_SAPSPI.pl
    10. QCCR1A147160 - Removal transport WBPK900014 does not remove all objects from a 7.3 system.
    11. QCCR1A160696 - Metrics SPISAP_0209 and SPISAP_0221 displays Unknown monitor error.

    Verified Environments

    For information about the platforms, operating systems, and product versions which the Smart Plug-in for SAP supports, see the Installation Requirements section in the HP Operations Smart Plug-in for SAP Installation and Configuration Guide.

    Documentation Errata

    The following documentation items are incorrect.

    Following are the issues related to WLSUM performance monitor which could not be documented in the HP Operations Smart Plug-in for SAP Online Help.

    Performance Metrics: WLSUM_PERF and DOCTSTAT:

    SYMPTOM: The new SPI for SAP performance monitors, DOCSTAT and WLSUM_PERF, do not collect any data.
    SOLUTION: In order to collect useful data from the SAP performance component, you must schedule the SAP report RSCOLL00 to run once an hour on your SAP R/3 system. For more information about how to schedule standard reports or jobs in a SAP component, see the SAP OSS note 16083.

    Reports do not show data from the hour between 00:00 and 01:00:

    SYMPTOM: Work-load and user reports using data gathered by the SPI for SAP performance monitor WLSUM_PERF do not show any results for the period between midnight 00:00 and 01:00 (1 A.M.).
    SOLUTION: This is due to a difference between the way SAP and the SPI for SAP handle time. Try to avoid scheduling reports to start between 00:00 and 01:00 (1A.M.): schedule reports to run after 01:30 instead.

    SPI for SAP WLSUM reports show irregular values for continuous data:

    SYMPTOM: The SPI for SAP WLSUM reports show irregular values for data that should be continuous. For example, a report for an SAP system normally shows around 1000 dialog steps per hour, but for one hour it shows no steps at all, and for the following hour it shows 2000 steps, which is double the usual amount.

    SOLUTION: The data collection for the WLSUM monitor is based on the internal SAP job COLLECTOR_FOR_PERFORMANCEMONITOR. If this job does not run correctly or at the correct time, the data usually collected by the WLSUM_PERF monitor run will only be picked up by subsequent runs of the SPI for SAP performance monitor and, as a result, displayed in the wrong place. Note that you can use the SPI for SAP job monitor, r3monjob, to monitor the behavior of the internal SAP performance-collector job COLLECTOR_FOR_PERFORMANCEMONITOR.

    Local Language Support

    In addition to the English-language version, SPI for SAP 12.05 is also available for the following environments:

    The Japanese-language version of the SPI for SAP 12.05 provides the following localized elements:

    To activate the Japanese environment, follow these steps:

    1. When specifying the SAP systems to be monitored in the Specifying SAP Systems to Monitor section of the HP Operations Smart Plug-in for SAP Installation and Configuration Guide, you must specify the Japanese language in order to activate the full Japanese localization. For all supported versions of SAP, use JA.
    2. When you are performing the instructions as documented in the Applying the SAP Transport section of the HP Operations Smart Plug-in for SAP Installation and Configuration Guide, apply the additional Japanese transports on the managed node (SAP server). For a list of the SAP R/3 transport numbers provided with the SPI for SAP, see the following file on the HPOM for Windows management server after installing the SPI for SAP software:
    3. For a list of the SAP R/3 transport numbers provided with the SPI for SAP, see the following file on the HPOM for Windows management server after installing the SPI for SAP software:
    4. On managed nodes where CCMS-alert monitor r3monal connects to a Japanese SAP server with Japanese as the connection language, set the environment variable SAP_CODEPAGE=8000 to ensure that the messages that r3monal sends display Japanese characters correctly.

    Support

    Please visit the HP Software support web site at:

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

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

    HP Software online 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 valuable support customer, you can benefit by being able to:

    NOTE: Most of the support areas require that you register as an HP Passport user and log in. Many also require an active support contract. To find more information about support access levels, go to the following URL:

    http://h20230.www2.hp.com/new_access_levels.jsp

    To register for an HP Passport ID, go to the following URL:

    http://h20229.www2.hp.com/passport-registration.html

    Legal Notices

    ©Copyright 1998 - 2011, 2013 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.

    Trademark Notices