SAPS Meter 4-6 Installation and Configuration Guide

SAPS Meter 4.
6
Installation and Configuration Guide
Version 4.6.0
Legal notices
The information contained herein is subject to change without notice. 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.
Copyright Notices
SAPS Meter is an HP-owned and operated technology covered by Hewlett Packard hardware or software support agreements. Copyright 20012011 Hewlett-Packard Development Company, L.P.
Trademarks
Intel, Xeon and Itanium are trademarks of Intel Corporation in the U.S. and other countries. AMD and Opteron are trademarks of Advanced Micro Devices, Inc. Sun, Sun Microsystems, and Solaris are trademarks or registered trademarks of Oracle. in the United States and other countries. AIX, AIX/ESA, AIX/L, AIX 5L, and IBM are trademarks or registered trademarks of International Business Machines in the United States, other countries, or both. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. Linux is a U.S. registered trademark of Linus Torvalds. Novell is a registered trademark and SUSE is a trademark of Novell, Inc. in the United States and other countries.
Revision History
Date
October 2011 January 2012
Revision
4.5 4.6
Changed
Single agent for all platforms Several improvements and fixes
New editions are complete revisions of the manual, incorporating extensive technical changes. Intermediate revisions include minor corrections and updates and do not change the edition number. Provided by: HEWLETT-PACKARD COMPANY 3404 E. Harmony Road Fort Collins, CO 80528 U.S.A.
Copyright Notices ................................................................................................................... 2 Trademarks ............................................................................................................................ 2 1 Overview ................................................................................................................................... 7 1-1 1-2 Coverage ............................................................................................................................ 7 Product Overview ............................................................................................................... 7 SAPS Meter Plus ......................................................................................................... 8
1-2-1 2
Overview ................................................................................................................................... 9 2-1 2-2 Coverage ............................................................................................................................ 9 Product Overview ............................................................................................................... 9 SAPS Meter Plus ....................................................................................................... 10 Agent Version 4.6 ...................................................................................................... 10
2-2-1
2-2-2 2-3 2-4 3
Installation and Registration Overview .............................................................................. 11 Installation process ........................................................................................................... 12
Pre-Installation ......................................................................................................................... 13 3-1 3-2 System Requirements ...................................................................................................... 13 Software dependencies .................................................................................................... 13 HP Performance Agent .............................................................................................. 13 Java ........................................................................................................................... 13
3-2-1 3-2-2 3-3
Information needed during Installation .............................................................................. 14 Customer ID and SAP version ................................................................................... 14 Firewall Settings for https transfer.............................................................................. 14 Data transfer information ........................................................................................... 14 Prerequisites for email transfer .................................................................................. 14 SAP user credentials (SAPS Meter PLUS only) ......................................................... 15 SAP User minimal Authentication (SAPS Meter PLUS only) ............................... 15
3-3-1 3-3-2 3-3-3 3-3-4 3-3-5
3-3-5-1 3-3-6 3-3-7 3-3-8 3-3-9 4
Solaris Zones............................................................................................................. 16 Optional: Processor data ........................................................................................... 16 VMware for Linux or Windows ................................................................................... 17 Registration data ....................................................................................................... 17
Installing the SAPS Meter Software ......................................................................................... 18 4-1 HP Unix ............................................................................................................................ 18 Installation ................................................................................................................. 18 How to Check and Uninstall ....................................................................................... 18
4-1-1 4-1-2 4-2
Linux ................................................................................................................................. 19 Installation ................................................................................................................. 19 How to Check and Uninstall ....................................................................................... 20
4-2-1 4-2-2
4-3
Sun Solaris ....................................................................................................................... 20 Installation Steps .................................................................................................... 20 How to Check and Uninstall ....................................................................................... 20
4-3-1
4-3-2 4-4
IBM AIX ............................................................................................................................ 22 Installation - Steps ..................................................................................................... 22 Known Restrictions ............................................................................................. 22
4-4-1
4-4-1-1 4-4-2 4-5 4-6
How to Check and Uninstall ....................................................................................... 22
Overview on the installed files on all Unix servers ............................................................ 24 Windows ........................................................................................................................... 26 Windows installation .................................................................................................. 26 How to Uninstall......................................................................................................... 29 Overview on the installed files on Windows ............................................................... 30 Files one by one ................................................................................................. 31
4-6-1
4-6-2 4-6-3
4-6-3-1 5
Configuration and Registration................................................................................................. 34 5-1-1 5-1-2 5-1-3 5-1-4 5-1-5 5-1-6 VMware Detected Section ......................................................................................... 34 Basic Configuration Section ....................................................................................... 35 SAP Data Collection Section (PLUS Service) ............................................................ 38 ILO Power Collection Section .................................................................................... 40 Communication Configuration Section ....................................................................... 41 Register Message Section ......................................................................................... 43
Operation and Maintenance ..................................................................................................... 44 6-1 6-2 Update from older versions (<4.2) to new agent versions ................................................. 44 Update from newer agent versions (4.2+) ......................................................................... 44 Update steps for Linux, HP-UX, Solaris, AIX ............................................................. 44 Update steps for Windows ......................................................................................... 46 Prepare .............................................................................................................. 46 Install using script ............................................................................................... 46 Alternative: manual install ................................................................................... 46
6-2-1 6-2-2
6-2-2-1 6-2-2-2 6-2-2-3 6-3
Unix (agent version 4.3+) .................................................................................................. 47 SID exclusion list ....................................................................................................... 47 Utilities ....................................................................................................................... 47 register.sh........................................................................................................... 47 report .................................................................................................................. 47
6-3-1 6-3-2
6-3-2-1 6-3-2-2 6-4
Windows ........................................................................................................................... 48 SID exclusion list ....................................................................................................... 49
6-4-1 6-5
Parm file ........................................................................................................................... 50

5
The Web Portal ........................................................................................................................ 51 7-1 User Registration on the Web Portal ................................................................................. 51
1-1 Adding Servers to Your Report Portfolio ................................................................................ 53 7-2 Viewing Reports ............................................................................................................... 55 Available Reports ...................................................................................................... 57
7-2-1 8
Understanding the Data ........................................................................................................... 58 8-1 Measurements and Values ............................................................................................... 58 Data collected from SAP ............................................................................................ 60 Other measures collected and processed .................................................................. 60
8-1-1 8-1-2 8-2
Data values used in reports .............................................................................................. 60 SAPS ......................................................................................................................... 60 Hour related report values consumption and summary report ................................. 60 Peak value report ...................................................................................................... 61 Detail report ............................................................................................................... 61 Correlation Report. .................................................................................................... 61
8-2-1 8-2-2 8-2-3 8-2-4 8-2-5 8-3 9
Known Limitations ............................................................................................................ 61
Frequently Asked Questions .................................................................................................... 62 9-1 9-2 9-3 9-4 What can I do when no systems or servers are shown in the web service pages? ........... 62 How to validate the email MX domain ............................................................................... 64 What can I do when values in a report are not reasonable?.............................................. 67 What logfiles does the SAPS Meter agent use?................................................................ 68 Windows Agent 4.6 .................................................................................................... 68 Unix Agent 4.6 ........................................................................................................... 68
9-4-1 9-4-2
1 Overview
1-1 Coverage
This document covers the following versions of SAPS Meter Agents:
SAPS Meter Agent version 4.6 for HP UX, Linux, AIX, Windows and Solaris
The version 4.6 has some additional capabilities. Please see the release notes for details. This document describes the installation and configuration of all these versions and gives some additional information about SAPS Meter like the description of collected data. In the FAQ chapter some typical questions and hints are given.
1-2 Product Overview

The SAPS Meter web service is a tool to measure and analyze the resource consumption of consolidated SAP systems in adaptive environments. Like a utility meter the SAPS Meter web service has been designed to enable companies to meter the resource consumption for each SAP solution in a consolidated and virtualized SAP system landscape so they can bill the business departments according to their utilization. This creates an incentive for departments to utilize these resources in a more efficient way. In addition the service allows correlation studies of different resource parameters to find dependencies and enable resource management according to ITIL. The SAPS Meter is a web service consisting of two components:
An agent continuously recording the resource consumption of customer systems A central analysis machine transforming the raw data measured by the agents into the Key Performance Indicators understood by managers, determine correlations and trends, and generating the reports.
The SAPS Meter agent is able to identify which database and SAP application instances belong to which SAP solution and collect the resource consumption of each process. The agent is installed on each server of a SAP system landscape and detects any SAP solution executed. Using HP OpenView Performance Agent (OVPA) functionality, the CPU and memory utilization as well as the I/O throughput are measured continuously. However, OVPA alone is not sufficient to provide all the necessary measurements, such as the number of active cores, which may change dynamically in a virtualized infrastructure. Therefore the SAPS Meter agent uses operating system commands to collect the actual number of active cores for every data set. Every five minutes the averaged values of the measured data are written into a log file. Each agent transmits the gathered raw data once a day to the SAPS Meter analytical machine. The number of consumed SAPS is calculated for each SAP or database instance detected on a server for each data set. The physical SAP system landscape of customer systems is converted into the logical SAP system landscape by adding up the resource consumption of the individual database and application server instances detected on the various servers. This process also considers SAP components which are added, moved between computers or completely removed during the reporting period. Finally the monthly resource consumption reports for each individual SAP solution are generated and either actively sent to customers via e-mail (push mode) or made available on the SAPS Meter web page for download (pull mode). In addition, the analytical machine generates correlation diagrams for each individual SAP solution, showing not only the up and downs of the various KPI's, but also their correlation and dependencies among each other.
1-2-1 SAPS Meter Plus

SAPS Meter Plus is able to collect data directly from SAP, correlate it with the platform values it also collects and finally report this information. The data is collected on each server from each instance of SAP on that server. The collected data is:
Number of active users The response time The number of dialog steps The SAP installation ID
2 Overview
2-1 Coverage
This document covers the following versions of SAPS Meter Agents:
SAPS Meter Agent version 4.6 for HP UX, Linux, AIX, Windows and Solaris
The version 4.6 has some additional capabilities. Please see the release notes for details. This document describes the installation and configuration of all these versions and gives some additional information about SAPS Meter like the description of collected data. In the FAQ chapter some typical questions and hints are given.
2-2 Product Overview

The SAPS Meter web service is a tool to measure and analyze the resource consumption of consolidated SAP systems in adaptive environments. Like a utility meter the SAPS Meter web service has been designed to enable companies to meter the resource consumption for each SAP solution in a consolidated and virtualized SAP system landscape so they can bill the business departments according to their utilization. This creates an incentive for departments to utilize these resources in a more efficient way. In addition the service allows correlation studies of different resource parameters to find dependencies and enable resource management according to ITIL. The SAPS Meter is a web service consisting of two components:
An agent continuously recording the resource consumption of customer systems A central analysis machine transforming the raw data measured by the agents into the Key Performance Indicators understood by managers, determine correlations and trends, and generating the reports.
The SAPS Meter agent is able to identify which database and SAP application instances belong to which SAP solution and collect the resource consumption of each process. The agent is installed on each server of a SAP system landscape and detects any SAP solution executed. Using HP OpenView Performance Agent (OVPA) functionality, the CPU and memory utilization as well as the I/O throughput are measured continuously. However, OVPA alone is not sufficient to provide all the necessary measurements, such as the number of active cores, which may change dynamically in a virtualized infrastructure. Therefore the SAPS Meter agent uses operating system commands to collect the actual number of active cores for every data set. Every five minutes the averaged values of the measured data are written into a log file. Each agent transmits the gathered raw data once a day to the SAPS Meter analytical machine. The number of consumed SAPS is calculated for each SAP or database instance detected on a server for each data set. The physical SAP system landscape of customer systems is converted into the logical SAP system landscape by adding up the resource consumption of the individual database and application server instances detected on the various servers. This process also considers SAP components which are added, moved between computers or completely removed during the reporting period. Finally the monthly resource consumption reports for each individual SAP solution are generated and either actively sent to customers via e-mail (push mode) or made available on the SAPS Meter web page for download (pull mode). In addition, the analytical machine generates correlation diagrams for each individual SAP solution, showing not only the up and downs of the various KPI's, but also their correlation and dependencies among each other.
2-2-1 SAPS Meter Plus

SAPS Meter Plus is able to collect data directly from SAP, correlate it with the platform values it also collects and finally report this information. The data is collected on each server from each instance of SAP on that server. The collected data is:
Number of active users The response time The number of dialog steps The SAP installation ID
2-2-2 Agent Version 4.6

The new agent consists of a main agent shell called MVMA (Multi-Vendor Monitoring Agent) and a SAPS Meter service plugin to the main agent. The new main agent runs all needed. It is also able to handle more services such as TAMS - and provides an automated updated capability, which we will offer in a coming release. In the future is will also offer to use a central node to communicate with HP, thus eliminating the need to connect each server directly with the portal.
OS interface
VM Ware host interface
HP SAPS Meter
(Measureware)
OVPA
Web Portal
Collect
sapsmd service HP MVM Agent
data collection
https or email
Metrics DB
2-3 Installation and Registration Overview

Figure Error! No text of specified style in document.-1 Installation and Registration Overview
1 2 3 4
The HP SAP Competency Center creates the customer account in the SAPS Meter portal and defines the Customer ID (which is usually identical to the SAP Customer Number). An email will be sent to the customer with the portal URL and the Customer ID. The user will install the SAPS Meter agent on each server and enter the processor, SAP version, and the Customer ID. The installation will send the registration data to the portal. All communication between each server contains the hostname, the machine identification string, the processor and SAP version and the customer ID. The daily transmission will also contain collected data. Users create a login and identify themselves with the correct customer ID, hostname of the system and the machine identification string for each system they want to see reports from. These three values prove that the user is authorized to view reports for this system.
11
2-4 Installation process

The SAPS Meter installation usually needs 3 steps.
Check Prerequisites and Collect Required Information
Install Package
Configure and Register Agent (register.s

h)
The Pre-Installation chapter 2 lists the prerequisites and which information is needed during the configuration step. The SAPS Meter agent install package comes in the typical package container for the platform it is installed on. Like depot for HPUX and rpm for Linux. The installation step will create the needed directories and users, copy the files and installs the agent process. This is described in chapter 3, separately for each platform. The configuration and registration in chapter 4 step is identical for all platforms. The agents have the dialog grouped in logical sections. The last sections will configure the connection to HP, then the dialog will perform a connection test and start all needed processes.
To install SAPs Meter please read chapter 3 to understand what is needed upfront, then look into to the platform section of chapter 3 that is relevant for you and then continue with the configuration and registration dialog described in chapter 4. When the prerequisites are there and the software is loaded to the server, the entire installation should not take more than a few minutes.
3 Pre-Installation
3-1 System Requirements
The current SAPS Meter, version 4, supports:
HP-UX 11i (11.23 and 11.31) on Itanium 64 and PA Risc (11.23 only) Suse Linux 10 Enterprise (64 bit) on Proliant or x86 Blade Servers Suse Linux 10 Enterprise (64 bit) on VMware Vsphere hosted on Proliant or x86 Blade Servers Red Hat Enterprise 5.2 or 5.4 (64 bit) on Proliant or Blade Servers Red Hat Enterprise 5.2 or 5.4 (64 bit) on VMware Vsphere ESX 4.0 hosted on Proliant or x86 Blade Servers Solaris (5.9, 5.10) on Sparc or Proliant or x86 Blade Servers AIX 6.1 on Power Processors Windows Server-64 bit (2003 and 2008) on Proliant or x86 Blade Servers Windows Server-64 bit (2003 and 2008) on VMware Vsphere ESX 4.0 hosted on Proliant or x86 Blade Servers
Not supported or untested are
HP UX 11.11 Solaris VM and Solaris Zones AIX 7.1 and AIX LPARS
3-2 Software dependencies

3-2-1 HP Performance Agent
The SAPS Meter uses the HP Performance Agent to collect application resource consumption data from all the supported platforms. The HP Performance Agent is also known as
MeasureWare OpenView Performance Agent HP Performance Agent Performance Component ScopeUX
The current versions of the SAPS Meter Agent works best with the performance agent versions 4.7 to 11. NOTE: a version of the Performance Agent MUST be installed. The SAPS Meter will not work without it. The SAPS Meter processes need to have wite access right to the parm (parm.mwc) file, and execute access to restart the Performance Agent and call the Extract utility.
3-2-2 Java
All SAPS Meter Agents require Java 1.5 or newer to be installed on the server. The install process will verify the version and stop the installation when Java cannot be found. The SAPS Meter ftp 13
server will also provide install packages which include Java, which then will be automatically installed in a separate private path. The packages including Java are significantly larger. Please use this to avoid version conflicts.
3-3 Information needed during Installation

Below is a list of information that you will be asked for as part of the installation process:
3-3-1 Customer ID and SAP version

Customer ID The Customer ID is sent to the customer by the SAP Competence Center. It is usually identical to the customer's SAP customer number. This unique identifier is usually identical to the customers SAP number. SAP Basis Version (such as R/3 4.6, R/3 4.7, ECC 5.0, ECC 6.0, ECC 6.4)
NOTE: For other solutions like BW, CRM, SCM and SRM equivalents of the above will be available to select from.
3-3-2 Firewall Settings for https transfer

Please allow the measured data to be sent to:
Destination address https:// h30081.www3.hp.com
If you cannot use the above url in you firewall settings, this url links with 2 environments as
we have a load balance/failover configuration on different sites.
15.216.12.77 15.217.53.94 Please configure both addresses as valid targets.
Port 443 Protocol HTTPS Outbound only
3-3-3 Data transfer information
Network Proxy information when using https connection If your environment requires the use of a proxy please collect the following information for the installation of the measurement package on each server:
Proxy Address Proxy User ID Proxy Password

NOTE: After installation, please run a connection test to verify that the proxy configuration is working as expected (see Section 2-1-1 page 20).
Email domain information when using email transfer The correct email domain is needed to allow emails to be sent by your email server to HP. Usually the email address looks like this: mailbox@domain. The correct domain value is needed.
3-3-4 Prerequisites for email transfer

The following prerequisites are needed to enable the email transfer
Unix sendmail is installed and configured on each server Encrypted emails are permitted to be sent do utilitymeter@hp.com
3-3-5 SAP user credentials (SAPS Meter PLUS only)

To collect data directly from SAP, the SAPS Meter must log into each SAP instance as a regular user. During installation the user credentials are required to enter. This information is exactly the same as the user credentials for a manual login to SAP. For each SAP system the following user credentials are required:
SID Application Server address - this can be the local host as SAPS Meter is usually installed on the same server = 127.0.0.1 System Number Client Username Password Passwords will be stored encrypted in SAPS Meter The SAP host and/or cluster names
3-3-5-1 SAP User minimal Authentication (SAPS Meter PLUS only)

In production environments it is not reasonable to use a user logon for the SAPS Meter which has the SAP_All access rights. As the default users differ from the SAP application it is not possible to suggest a common default user with the right access rights. Please consider creating a specific role for a user for the SAPS Meter or find a user which has the minimal requirements below. The user must have at least the following authentication rights:
Table Error! No text of specified style in document.-1 SAP Authentication needed for SAPS Meter Object Permissions
RFC_TYPE S_RFC FUGR
(function group)
RFC_NAME SYST RFC1 SDIFRUNTIME SXMI SALX SYSU
ACTVT 16
(execute)
EXTCOMPANY S_XMI_PROD HP
EXTPRODUCT SAPS-Meter
INTERFACE XAL
15
The example above demonstrates the role Z_SAPSMETER for user SAPS-Meter
3-3-6 Solaris Zones

During the installation of SAPS Meter into a local zone it is not possible to read out the server model. Therefore the SAPS Meter will ask for a login to the global zone. Needed is
The global zone network address (hostname or IP address) A global zone user name and the password for this user the user should be able to use the prtdiag command.
3-3-7 Optional: Processor data

In specific circumstances it is possible that the automatic detection of processor data may not work correctly. In this case please collect the values separately and enter them manually. Please contact HP Support to ensure that the data is correct.
Processor Type Can be discovered by running the machinfo command. Processor Speed Can be discovered by running the machinfo command. Enter the value in MHz. Processor Cache Can be discovered by running the machinfo command.
NOTE: The machinfo command works for Itanium processors. To find the above information for other processors please contact HP Support. For older PA Risc machines the agent can not autodetect these values please use only the following values, using other values will result in incorrect SAPS calculation. Processor Type Processor Speed PA8900 1100, 1000, 800 always 0 PA8800 1000, 900, 800, PA8700+ 875, PA8700 750, 650, PA8600 540, PA8500 440, 360,
Processor Cache
model:
usually it starts with rp then four numbers, Superdomes are SD32A, very old models may have other codes
If you have a very old model and a processor not listed here, please contact HP Support.
3-3-8 VMware for Linux or Windows

The installation of SAPS Meter on VMware is basically identical to the installation on a normal OS. SAPS Meter will automatically detect that there is a VMware environment, install the necessary additional modules and ask for the additional information during the installation. SAPS Meter will reach to the ESX host system to collect physical utilization data. To get these information SAPS Meter has to have authorization with a read only access. Please use Read Only role user for the SAPS-Meter agent, you can create the user in the vSphere Client. The definition of this role is: View the state and details about the object. View all the tab panels in the vSphere Client except the Console tab. Cannot perform any actions through the menus and toolbars.
To install SAPS Meter on a Guest Linux operating system the following prerequisites have to exist:
Environment
VMware ESX 4.0 Linux or Windows Guest OS
Configuration Parameter requirement:
$hostname : vSphere IP name $username: variable VI_USERNAME $password: variable VI_PASSWORD $guestname: guest os name on vShpere (this is the name you see in vClient)
3-3-9 Registration data

For registering a new SAP server please obtain the following:
Machine ID You will need to know your machine ID for when you register a new SAP server to your account on the web portal.
HP-UX: The getconf MACHINE_IDENT command will give the machine ID. LINUX: ~ # dmidecode | grep UUID
results in: UUID: 5E72ECE7-B942-DB11-BBDA-71700C490018
Other Platforms: the server Serial number is used as Machine ID
17
4 Installing the SAPS Meter Software

4-1 HP Unix
4-1-1 Installation
The following steps will install the SAPS Meter software. These installation tasks should be performed as root. NOTE: Users will need their Customer ID and other information to complete the install (see Section 2-3 on page 13). If you dont have your Customer ID or your Customer ID will not validate, the installation can be terminated and resumed later by running register.sh script
IMPORTANT:
remember that you should enter the full path of the depot package at swinstall please deinstall older versions of SAPS Meter before install the new one. Remember to keep a print out of the sapsmd.conf to have all data ready for the new installation.
Open a terminal window and extract the installation package you require with the following command: HP UX PA Risc with Java HP UX Itanium with Java uncompress sapsm-4.6.0-hpux-pa-jre15.depot.Z swinstall s /<path>/sapsm-4.6.0-hpux-pa-jre15.depot \* uncompress sapsm-4.6.0-hpux-ia64-jre15.depot.Z swinstall s /<path>/sapsm-4.6.0-hpux-ia64-jre15.depot \*
We do not offer packages without Java anymore. 2 Run the installation script after extraction with the following command:
/var/opt/hpmvma/services/sapsm-0/bin/register.sh
Continue with chapter 5 registration and configuration dialog
The list of installed files is in chapter 4.5.
4-1-2 How to Check and Uninstall

To check if the SAPS Meter is installed HP UX # swlist -l fileset | grep -i HPSAPSM
HPSAPSM HPSAPSM.hpmvma Agent
4.6.0
HP SAPS Meter Agent
A.05.65 HP Multi-Vendor Monitoring
When you want to uninstall the SAPS Meter please use these commends to remove the packages HP UX # swremove HPSAPSM
The Performance Agent parm file will not be automatically cleaned up. As users may use the definitions in there for other performance tools, the deinstall leaves the parmfile unchanged. If the user does not want the entries
4-2 Linux
4-2-1 Installation
The following steps will install the SAPS Meter software. These installation tasks should be performed as root. NOTE: Users will need their Customer ID and other information to complete the install (see Section 3-2on page 13). If you dont have your Customer ID or your Customer ID will not validate, the installation can be terminated and resumed later by running register.sh script
IMPORTANT:
please deinstall older versions of SAPS Meter before install the new one. Remember to keep a print out of the sapsmd.conf to have all data ready for the new installation.
Open a terminal window and extract the installation package you require with the following command: Linux Suse/RedHat with Java rpm -ivh /<path>/sapsm-4.6.0-linux-jre15.rpm
Run the installation script after extraction with the following command:
/var/opt/hpmvma/services/sapsm-0/bin/register.sh
The list of installed files is in chapter 4-5.
19

To check if the SAPS Meter is installed Linux Suse/RedHat #rpm -q sapsmd sapsm-4.6.0-1
When you want to uninstall the SAPS Meter please use these commends to remove the packages Linux Suse/RedHat # rpm -e sapsmd
4-3 Sun Solaris

4-3-1 Installation Steps
The following instructions describe the differences to the Linux installation 1 Get the installation media using the appropriate command, for example:
sapsm-4.6.0-solaris-x86_64-jre15.pkg sapsm-4.6.0-solaris-sparc-jre15.pkg
-> for Intel, AMD -> for Sparc
Open a terminal window and extract the installation package you require with the following command: pkgadd -d /<path>/sapsm-4.6.0-solaris-x86_64-jre15.pkg Solaris on x86 Solaris on Sparc pkgadd -d /<path>/sapsm-4.6.0-solaris-sparc-jre15.pkg
IMPORTANT:
Solaris Zones The installation dialog can not extract the model information from the zone. Therefore a login to the global zone is required.

To check if the SAPS Meter is installed
All Solaris
# pkginfo | grep -i HPSAPSM system HPsapsm SAPS Meter Agent on Solaris
When you want to uninstall the SAPS Meter please use these commands to remove the packages All Solaris # /opt/hpmvma/bin/hpmvma stop # pkgrm HPsapsm
21
4-4 IBM AIX

4-4-1 Installation - Steps
The following steps will install the SAPS Meter software. These installation tasks should be performed as root. The bash shell is a IBM package and this step is highly recommended to ensure that the latest version is installed. http://www-03.ibm.com/systems/power/software/aix/linux/toolbox/date.html 1 Open a terminal window and extract the installation package you require with the following commands: AIX on Power
# rpm -ivh /<path>/bash-3.2-1.aix5.2.ppc.rpm And then # rpm -ivh /<path>/sapsm-4.6.0-1.aix6.1.ppc.rpm
2 3
The rpm sapsm will install the SAPS Meter package. Continue with chapter 5 registration and configuration dialog
4-4-1-1 Known Restrictions
Older AIX operating systems there was no test of older AIX versions and do not know if there will be issues when SAPS Meter is installed. Only therefore HP excludes these from support. AIX partition like LPAR, Micropartitions and virtual machine technologies are not supported. The SAP data collection will not automatically collect the SAP Installation ID. With email transport to HP SSL and authentication are not supported. During uninstall invalid error messages occur.

To check if the SAPS Meter is installed AIX # rpm -q sapsm Sapsm-4.6.0-1
When you want to uninstall the SAPS Meter please use these commends to remove the packages AIX # /opt/hpmvma/bin/hpmvma stop # rpm -e sapsm
Please expect to see the following messages:
# /opt/hpmvma/bin/hpmvma stop # rpm -e sapsm cannot remove /var/opt/hpmvma/services/sapsm-0/var_opt_sapsmd/log directory not empty cannot remove /var/opt/hpmvma/services/sapsm-0/var_opt_sapsmd - directory not empty cannot remove /var/opt/hpmvma/services/sapsm-0/conf - directory not empty cannot remove /var/opt/hpmvma/services/sapsm-0/bin - directory not empty cannot remove /var/opt/hpmvma/services/sapsm-0 - directory not empty cannot remove /var/opt/hpmvma/services - directory not empty cannot remove /var/opt/hpmvma/logs - directory not empty cannot remove /var/opt/hpmvma/conf - directory not empty cannot remove /var/opt/hpmvma - directory not empty
The Performance Agent parm file will not be automatically cleaned up. As users may use the definitions in there for other performance tools, the deinstall leaves the parmfile unchanged. If the user does not want the entries they must be deleted manually, the beginning and the end of the SAPS Meter managed area is marked.
23
4-5 Overview on the installed files on all Unix servers

MVM folder structure.
/var/opt/hpmvma |-- conf | |-- config.xml | |-- config.xml.OLD | `-- hpmvma |-- download |-- logs | |-- MVMA.log | `-- rc.log |-- services | |-- mvm-agent-0 | | |-- conf | | | |-- config.xml | | | |-- perms | | | |-- perms.txt | | | `-- publicKey | | `-- lib | | `-- agent.jar | `-- sapsm-0 | |................(see below) | |-- standalone-service-jar-dir | `-- sapsm-4-6.jar `-- unsent /opt/hpmvma/ |-- bin | |-- .aux | | |-- commonScript | | |-- daemon | | |-- uncommonScript | | `-- version | |-- README | |-- configureCms | |-- configureUser | |-- hpmvma | |--jre | `-- report `-- lib `-- agentLoader.jar
#example
SAPSM folder structure.

/var/opt/hpmvma/services/sapsm-${service-id} |-- bin
Version 4.6.01
24
| |-| | | | | | | | | | | |-| | | | | | | | | | | | | | `--
`-- register.sh conf |-- config |-- logging.conf |-- osMonitoringSpec.xml |-- perms |-- perms.txt |-- sapsmd.conf |-- sapsmd.conf.20110429032520 |-- sapsmd.hp-ux.conf.encrypt |-- sapsmd.linux.conf.encrypt |-- templ.hp-ux `-- templ.linux lib |-- sap | |-- HP-UX | | |-- IA64W | | | |-- libsapjco3.so | | | `-- sapjco3.jar | | `-- PA_RISC2.0W | | |-- libsapjco3.sl | | `-- sapjco3.jar | |-- Linux | |-- AIX | |-- Solaris | |-- Windows | `-- SapInfo.jar `-- service.jar var_opt_sapsmd |-- archive | |-- sap_20110509.dat | |-- server2.hp.com_201105090000.xml | `-- vm_20110509.dat |-- data | |-- sap_20110510.dat | |-- server2.hp.com_201105100000.xml | |-- timestamp | `-- vm_20110510.dat `-- log |-- sapsmd_collector.log |-- sapsmd_register.log |-- sapsmd_service.log |-- sapsmd_cache.log |-- sapsmd_sender.log `-- sapsmd_updateparm.log
#example
#example #example #example #example #example #example #example #example #example #example #example
#example #example #example #example #example #example
The example files do not exist under this name.
Version 4.6.01
25
4-6 Windows
4-6-1 Windows installation
Download sapsm-4.6.0-windows-x86_64.rar and unzip it.
After unzipping the package double click the file HPSAPSMeter.msi. The following window will appear.
Click Next button will open the a folder selection dialog
Version 4.6.01
26
Click Cancel button will allow you to stop the installation here.
Version 4.6.01
27
Click Next button will actually start the installation execution
Next click Close button to exit the SAPS METER installation.
Version 4.6.01
28
The software is now installed on the server, but it is not ready to run before the registration and configuration is done. These steps are separated to allow users to customize the installation. Start Register Dialog
Please start the registration/configuration dialog by executing the Register utility
The register utility will open a command line window which runs the configuration and registration dialog. Please continue in chapter 5.
4-6-2 How to Uninstall

To uninstall the SAPS Meter select the uninstall in the start menue
Version 4.6.01
29
The Windows Installer will start and perform the uninstall task.
Click yes to uninstall and wait until the below window close automatically.
4-6-3 Overview on the installed files on Windows

Please do not edit or change any files unless discussed with SAPS Meter support. Default path C:\Program Files(x86)\HP\SAPSMeter all files of SAPS Meter are in this directory The path can be changed during installation to other disks. <path>\opt\hpmvma\bin <path>\opt\hpmvma\jre<version> executable files, the services and utilities. to avoid any compatibility issues, SAPS Meter brings its own Java version. It is located here. agentloader.jar which is the Windows Service running the SAPS Meter logfiles for diagnosis and supervision. They are limited in size as configured in ..\conf\logging.conf <path>\ var\opt\hpmvma\services\ sapsm\var_opt_sapsmd\data\ The collected data is stored here until it is sent to the portal. The main collection files in here are named with customer number + server name + date stamp. These files contain all data to be sent to the portal. the files in here have been sent to
<path>\opt\hpmvma\lib <path>\var\opt\hpmvma\services\ sapsm\var_opt_sapsmd\log
<path>\
Version 4.6.01
30
var\opt\hpmvma\services\sapsm\ var_opt_sapsmd\archive\
the portal already. To resend simply move them into the collection path.
4-6-3-1 Files one by one
Agent installation
c:/program files(x86)/hp/SAPSMeter/opt/hpmvma |-| | | | | | | | | | | | | | |-| |-| | | | | | | | |-|-bin |-- 7za.exe |-- awk.exe |-- config.bat |-- INSTSRV.EXE |-- NTEventLogAppender.dll |-- REG.EXE |-- Register.cmd |-- service.cmd |-- SRVANY.EXE |-- StartService.cmd |-- StopService.cmd |-- StanPlus.vbs |-- uninstall.cmd |-- uninstallService.vbs lib |-- agentLoader.jar ico |-- Install_Service.ico |-- Regest.ico |-- ReStart_SAPs_Meter.ico |-- StartSAPSMeterService.ico |-- StopService.ico |-- testConnection.ico |-- Uninstall.ico |-- Uninstall_Service.ico jre150_22.zip vcredist_x64.exe
Agent Framework and SAPS Meter Service

c:/program files(x86)/hp/SAPSMeter/var/opt/hpmvma |-| | | |-| | | |-| |-conf |-- config.xml |-- config.xml.OLD |-- hpmvma logs |-- MVMA.log |-- osMonitoringSpecViolations.log |-- sent.log standalone-service-jar-dir |-- sapsm-windows-4-6.jar unsent
Version 4.6.01
31
|-| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
services |-- mvm-agent-0 | |-- conf | | |-- config.xml | | |-- perms | | |-- perms.txt | | |-- publicKey | |-- lib | | |-- agent.jar |-- sapsm-0 | |-- bin | | |-- register.sh | |-- conf | | |-- appconfig.xml | | |-- config | | |-- logging.conf | | |-- osMonitoringSpec.xml | | |-- perms | | |-- perms.txt | | |-- sapsmd.aix.conf.encrypt | | |-- sapsmd.conf | | |-- sapsmd.conf.20111024005249 | | |-- sapsmd.hp-ux.conf.encrypt | | |-- sapsmd.linux.conf.encrypt | | |-- sapsmd.solaris.conf.encrypt | | |-- sapsmd.windows.conf.encrypt | | |-- templ.aix | | |-- templ.hp-ux | | |-- templ.linux | | |-- templ.solaris | | |-- templ.windows | |-- lib | | |-- service.jar | | |-- sap | | | | -- SapInfo.jar | | | | -- Windows | | | | | -- amd64 | | | | | | -- sapjco3.dll | | | | | | -- sapjco3.jar | | | | | -- Itanium | | | | | | -- sapjco3.dll | | | | | | -- sapjco3.jar | | | | | -- x86 | | | | | | -- sapjco3.dll | | | | | | -- sapjco3.jar | |-- var_opt_sapsmd | | |-- archive | | | |-- xxx_yyyyy_201110230000.xml | | |-- data | | | |-- xxx_yyyyy_201110240000.xml | | | |-- timestamp | | | |-- sap_20111023.dat | | | |-- vm_20111023.dat | | |-- log | | | |-- sapsmd_cache.log | | | |-- sapsmd_collector.log
#example
#example #example #example #example
Version 4.6.01
32
| | | |
| | | |
| | | |
| | | |
|-|-|-|--
sapsmd_register.log sapsmd_sender.log sapsmd_service.log sapsmd_updateparm.log
In the Users Programs Menus:

|-| | | | | HP SAPS Meter |-- Register |-- StartService |-- StopService |-- Uninstall | |-- uninstall
Version 4.6.01
33
5 Configuration and Registration

This chapter describes the configuration and registration dialog. The order of the sections may be different on some platforms, but the questions and their meaning are the same. The dialog will collect all information that is automatically detectable. These differ between platforms. The user can overwrite all collected values by answering the confirmation question at the end of each section or the end of the dialog with no.
IMPORTANT: In the following example dialog you will see some color coded lines: Black = program output - it should help you to understand what the registration
utility is currently doing.
Blue = these lines are questions to the user and expect a user response Amber = example input, Please fill in the information that is asked for. [Values] in square brackets are used if you just hit the enter key. IMPORTANT: When you use a <backspace> during data entry, some operating systems simply add a backspace character into the entry string, when you look at the output or even at the config file you will not be able to see this. Please enter a no at the end of the section and retype any misspelled entry. All automatically collected data items can be manually overwritten when entering a no to the confirmation question.
5-1-1 VMware Detected Section

Skip this section if there is no VMware to detect. This section only applies to Windows and Linux platforms which are installed on VMware guests. It is the first dialog section in these cases as SAPS Meter immediately will collect additional information from the VMware Host (ESX). SAPS Meter will automatically detect that there is a VMware environment, install the necessary additional modules and ask for the additional information during the installation.
You will be asked to enter the following information at the beginning of the configuration dialog: Table 2 VMware Configuration Item
VMware Host IP VMware Host login Username VMware Host login Password VMware Guest Name
Collection Reason for collection

User Input User Input User Input User Input IP address of the ESX host instance, not sent out Host Login user, a user with a read role access to Host HW and Guest OS utilization is needed Login password, stored encrypted and not sent out Name of guest OS instance in the host this is the guest name as seen in vClient
Version 4.6.01
34
Example of the dialog bin/register.sh Start the SAPS-Meter service configuration... #-------------------------------------------# VMware Configuration #-------------------------------------------# Virtual machine detected... vmware host fqdn/ip?[] 192.168.1.100 vmware user name?[]xyzuser vmware password?[]!xyzPwd vmware guest name?[]SuseLinux02 test the connection?(y|n)y connection testing...succeed. ------------------------Vmware settings summary: Vmware host: Vmware user name: Vmware password: Vmware guest name: all settings saved. Start the SAPS-Meter service configuration..... .. 192.168.1.100 xyzuser x****** SuseLinux02
are these settings correct?(y|n)y
5-1-2 Basic Configuration Section

The following data items are collected in this section
Table 3 Basic configuration Item Collection Reason for collection
Customer ID
User entry
The customer ID is the unique identifier which brings together all collected information for one customer. The customer ID is agreed between customer and HP, by default the SAP customer number is used here. For one Customer ID there is always one service level standard SAPS Meter or SAPS Meter Plus Name of the server this is used to name collection files of this server
Host name
automatic
Version 4.6.01
35
Item
Collection
Reason for collection
FQDN
automatic
Fully Qualified Device Name Unique identifier for the server within one customer Unix type or Windows used to configure different collection and path alternatives in SAPS Meter used to verify if OS version can be supported Used to authenticate access to collected data. See chapter 2.3.8 on how to obtain the machine identifier The model defines the certified SAPS value together with the CPU. Therefore the model must exactly match. In virtual machines this is collected from the host. In Solaris Zones SAPS Meter needs to collect this from the Global Zone.
OS Name
automatic
OS Version Machine ID
automatic automatic
Model
automatic
CPU information
automatic
Identify the CPU to calculate the correct SAPS values This may need manual correction with some OS versions and virtual machines If the CPU is able to hyper threading, the measured CPU utilization may significantly differ from the real physical utilization. The more threads are possible the more difference. With enabled correction the SAPs Meter will calculate a correction based on the global_CPU_utilization. The SAPS Meter will automatically detect the OS settings for Hyper threading, but some OS will not support this detection. In this case the corrected data must be entered manually.
Enable Hyper threading correction
User entry
OVPA Version
automatic
Configure different measurement dimension used by the version found Performance correction for SAP version.
Default SAP system version
User entry
If some autodetected values does contain blanks you will receive this warning: WARNING: Some items can't be detected, you have to manually input the value. The dialog will continue to prompt for the missing values. This seem to happen frequently with PA RISC server, please use only these values as listed under 3-3-7:
Section dialog example:

bin/register.sh Start the SAPS-Meter service configuration... #-----------------------------------------# Metadata Configuration #-----------------------------------------# customer ID?[]12345678 Do you want to auto detect OS information?(y|n)[y]y
Version 4.6.01
36
host name/fqdn auto detecting... host name/fqdn auto detected. os name/version auto detecting... os name/version auto detected. machine identifier auto detecting... machine identifier auto detected. model auto detecting... model auto detected. cpu information auto detecting... cpu information auto detected. hyper threading cpu utilization correcting?(y|n)[n]y ovpa version auto detecting... ovpa version auto detected. Select the basis for SAPS calculation on this server (?) - help (7) - ECC 6.05 (6) - ECC 6.04 (5) - ECC 6.0 (4) - ECC 5.0 (3) - R/3 4.7 (2) - R/3 4.6 (1) - R/3 4.5 current value [ECC 6.0] your selection:[5]5 ------------------------metadata settings summary: customer ID: host name: fqdn: oS name: os version: machine identifier: machine model: processor type: processor speed (MHz): processor cache (MB): hyper threading enabled: hyper threading capable: hyper threading per core: hyper threading correcting: 12345678 sapsrv01 sapsrv01.xgroup.mycompany.com Linux SUSE Linux Server 10 (x86_64) 3838-323350523457 ProLiant DL360 G4 Xeon 3400 1 0 0 1 yes
Version 4.6.01
37
ovpa version: SAP version: all settings saved.
05.00.000 ECC 6.0
are these settings correct?(y|n)y
5-1-3 SAP Data Collection Section (PLUS Service)

This section will only appear when the PLUS agent has been enabled by the last question above. For the basic standard agent please skip this section. The following data items are collected in this section
Table 4 SAP configuration Item Collection Reason for collection
Collect SAP data
User entry
For users without the PLUS service the SAP data collection can be skipped. In this case enter no. For each detected instance the user can configure the SAP data collection or deny it. The following questions appear only when a Y is given. This information is needed to log on to SAP - IP address from where the SAP data should be collected from. Usually this is the local host (this server) with IP 127.0.0.1 This information is needed to log on to SAP
Configure SAP instance SID?
User entry
SAP Application server
User entry
SAP system number SAP client SAP user name SAP password
User entry
User entry User entry User entry
This information is needed to log on to SAP This information is needed to log on to SAP This information is needed to log on to SAP - (SAPS Meter stores the password encrypted on the server and does not sent it out) This information is needed to identify the correct system name inside SAP. When CCMS reports are called the system name is the first part of the instance name. The name to enter here is the name of THIS server or the cluster name used inside SAP.
SAP host/cluster User entry name(s)(separated by ,)
Example: server name is here ML37-002, the SID is ERP and the number of the instance is 10. Please enter the the server name only.
Often the host name of the server is used. If you enter multiple server names, the data is added together. If SAPs Meter also runs on those servers, this may cause that data is counted twice.
Version 4.6.01
38
Item
Collection
Collect SAP installation ID Enter SAP <SID> installation ID Are the settings correct?
User entry
Collecting the SAP installation ID is for documentation purpose in this release, there is no function using this This question will be displayed when the automated detection fails
User entry
User Entry Allows you to correct invalid settings.
Do you want to enable the SAPS Meter PLUS data collection:(y|n)[n]y
#-----------------------------------------# SAP Data Collection Configuration #-----------------------------------------#

collect SAP system performance data (y|n)?[n]y SAP instances auto detecting... SAP instances auto detected. 2 instances found. configure SAP instance "B02"?(y|n)y SAP application server:[127.0.0.1] <enter> SAP system number:[]01 SAP client:[]001 SAP user name:[]test SAP password:[]test SAP host/cluster name(s)(separated by ,):[]test, sah3cd02 test SAP instance "B02" settings now?(y|n)n configure SAP instance "SOL"?(y|n)y SAP application server:[127.0.0.1]DL36-359.usa.com SAP system number:[]01 SAP client:[]000 SAP user name:[]DDIC SAP password:[]abc123d SAP host/cluster name(s)(separated by ,):[]DL36-359 test SAP instance "SOL" settings now?(y|n)x input value is invalid! input pattern:y|n test SAP instance "SOL" settings now?(y|n)y Check connection...succeed. ----------------------------------SAP settings summary: collect SAP performance data: SAP instance B02 settings: - application server: 127.0.0.1 yes
Version 4.6.01
39
- system number: - client: - username: - password: - sap host/cluster name: SAP instance SOL settings: - application server: - system number: - client: - username: - password: - sap host/cluster name:
01 001 test t****** test,sah3cd02 DL36-359.usa.com 01 000 DDIC a****** DL36-359
are these settings above correct?(y|n)y Do you want config sap installation id :[y|n][n]y SAP instances auto detecting... SAP instances auto detected. 2 instances found. Enter SAP B02 installation ID :[]12345678 Enter SAP SOL installation ID :[]87654321 Please check the SAP installation IDs: SOL B02 : : 12345678 87654321
Are these settings correct?(y|n)y
5-1-4 ILO Power Collection Section

This section will only appear when the PLUS agent has been enabled by the configuration question above. For the basic standard agent please skip this section. The following data items are collected in this section:
Table 5 Power data collection Item Collection Reason for collection
ILO Server Hostname
User entry
For users without the PLUS service the SAP data collection can be skipped. In this case enter n at the very first question. The ILO host name is the one used by system administrator to access the ILO directly. The SAPS Meter just needs read access.
ILO Server user name ILO Server user password
User entry
This information is needed to log on to the ILO.
User entry
This information is needed to log on to the ILO - (SAPS Meter stores the password encrypted on the server and does not sent it out)
Version 4.6.01
40
Do you want to enable the ILO power data collection:(y|n)[n]y #-----------------------------------------# ILO power Collection Configuration #-----------------------------------------# ILO server(hostname[:port])?[] ilo01.xgroup.mycompany.com ILO user name?[]Administrator ILO password?[]Admin$wd Do you want to test ILO connection now?(y|n)[y]y testing connection to ILO ... succeed. Are these settings above correct?(y|n)[y]y
5-1-5 Communication Configuration Section

The following data items are collected in this section
Table 6 Communication Configuration Item Collection Reason for collection
communication protocol?(email|htt ps)
User Input
Select the communication protocol to connect to HP https recommended connects directly with HPs portal through secure internet protocol as it is used for internet banking. All transmission are directly loaded and this ensures an easy auditable data transfer. To increase the security firewall and proxy settings are usually needed. email this is often used to avoid firewall and proxy settings. The emails are transferred encrypted but the reception by the HP portal cannot be directly verified. Therefore it is not an easy auditable data transfer.
Use Proxy
User Input
A proxy is used as a central communication point in the internet, hiding the sending servers real address. To use a proxy the address of it needs to be entered. If the proxy is secured by passwords, the username and password need to be given too. (SAPS Meter stores the password encrypted on the server and does not sent it out) Answer yes or no when your company does not use a proxy. Enter the proxys own fqdn or IP address here and if there is a specific port add it with the colon. In case a login to the proxy is required, enter the name here, otherwise leave empty. In case a login to the proxy is required, enter the password here, otherwise leave empty.
http proxy server
User Input
http proxy user
User Input
http proxy password
User Input
Version 4.6.01
41
Item
Collection
Email exchange domain
User Input
The email domain is needed to create a vaild from address for the collected data messages. Usually, when a email is sent from the server to another emai address, the domain is the part on the right of the @ sign. SAPS Meter will immediately verify if the domain is valid. If there are difficulties to find this domain please see the hints in 8-1-1.
Email exchange server
Automated proposal
This server is the focal server in an environment for handling the email exchange. SAPS Meter will search for a server which is available in the domain and propose it.
https example : #-----------------------------------------# Communication Configuration #-----------------------------------------# communication protocol?(email|https)[]https use proxy?(y|n)[n] y http proxy server (hostname[:port])?[]web-proxy.mynet.com:8080 http proxy user?[]<enter> http proxy password?[]<enter> -----------------------------communication setting summary: communication protocol: http proxy: http proxy server: http proxy user: http proxy password: are these settings above correct?(y|n)y settings input is complete. saving... all settings saved. https y web-proxy.mynet.com:8080
Email example: #-----------------------------------------# Communication Configuration #-----------------------------------------# communication protocol?(email|https)[https]email Mail eXchange domain name?[]mydomain.com resolving mail exchanger for domain "mydomain.com", depending on your network settings, this may take up to minutes...
Version 4.6.01
42
resolved Mail eXchange server name: "smtp.mydomain.com" Specify your Mail eXchange server(e.g smtp.hp.com, no SSL, no authentication supported now)?[smtp.mydomain.com]smtp1.mydomain.com -----------------------------communication setting summary: communication protocol: Mail eXchanger domain name: Mail eXchanger server name: all settings saved. email mydomain.com smtp1.mydomain.com
are these settings above correct?(y|n)y
5-1-6 Register Message Section

This question will only occur when the transmission method is https.
Table 7 Register section Item Collection Reason for collection
Register Now
User Input
A registration message is sent to the HP portal and the result is presented to the user. A successful registration at the portal proves an successful data transfer. After registration the user can assign this server to his reporting profile. This function needs https transfer.
#-----------------------------------------# Register #-----------------------------------------# Do you want to register now (y/n) y Initializing... Registration succeeded. Please wait for OVPA restart ... OVPA restart completed successfully HPMVMA agent restarted successfully
When the complete message appears or the registration is successful the installation and configuration is complete. If you choose the email communication method there is no registration. Please use the Portal to verify if a server has successfully connected.
Version 4.6.01
43
6 Operation and Maintenance

6-1 Update from older versions (<4.2) to new agent versions
To update from an older version to a Agent with version 4.2 or later it is necessary to uninstall the old agent first and then to reinstall the new agent. It might be helpful to take a copy of the registration dialog of the old version, as most of the questions will appear in the new dialog, too. Under Linux please open the /var/opt/perf/parm file and remove the lines which belong to the application SPM_SAP_IOS and SPM_ORA_IOS. This step can not be automated. The restart of the performance agent happens with the new registration.
6-2 Update from newer agent versions (4.2+)

Updates to new versions of the SAPS Meter in the agent versions 4.2+ to newer versions is significantly simpler than before. Most steps are executed in a provided shell script. It is only necessary to download the install files and then to call the install script. Upgrade version: From 4.2, 4.3, 4.5 to 4.6 Available for OS: Linux, HP-UX, Solaris, AIX
6-2-1 Update steps for Linux, HP-UX, Solaris, AIX

Upgrade version: From 4.2, 4.3, 4.5 to 4.6 Available for OS: Linux, HP-UX, Solaris, AIX
1. Get the appropriate upgrade files from ftp server and download them to the local machine . These jar-packages are available: sapsm-linux-4-6.jar sapsm-hpux-4-6.jar sapsm-solaris-4-6.jar sapsm-aix-4-6.jar
Each jar-package also needs his specific configuration: sapsmd.linux.conf.encrypt sapsmd.hp-ux.conf.encrypt
Version 4.6.01
44
sapsmd.solaris.conf.encrypt sapsmd.aix.conf.encrypt
For automated application and database handling the agent 4.6 needs the rule configuration. And finally the shell script which performs all the commands is needed. These files are the same for all platforms. appconfig.xml upgrade4.6.sh
For example, your OS type is HP-UX, you will need to download the following items into your local directory. sapsm-hpux-4-6.jar sapsmd.hp-ux.conf.encrypt appconfig.xml upgrade4.6.sh Suggested <localDirectory> is /tmp. 2. You now should have downloaded the 4 files into the localDirectory like /tmp. /<localDirectory>/sapsm-hpux-4-6.jar /<localDirectory>/sapsmd.hp-ux.conf.encrypt /<localDirectory>/appconfig.xml /<localDirectory>/upgrade4.6.sh 3. Grant the upgrade script the executable privilege. chmod +x <localDirectory>/upgrade4.6.sh or chmod 500 <localDirectory>/upgrade4.6.sh
4. Call the upgrade script. upgrade4.6.sh (when all files are in /tmp/)
or upgradescript <parm1> <parm2> <parm3> upgrade4.6.sh <sapsm-hpux-4-6 full path> <appconfig.xml full path> <sapsmd.hp-ux.conf.encrypt full path>
IMPORTANT: if you want to collect power consumption data from the HP ILO processors with this agent, you have to run the register.sh after step 4 to enter the credentials for the ILO processor.
Version 4.6.01
45
6-2-2
Update steps for Windows

Upgrade Version: From 4.5 to 4.6 Suitable OS: Windows
6-2-2-1 Prepare 1. Get the appropriate upgrade jar and files from ftp server and download to local machine. The following files are needed from the ftp server: sapsm-windows-4-6.jar appconfig.xml upgrade.4.6.bat
2. copy to C:\tmp or another location 3. note the SAPSMeter path
6-2-2-2 Install using script 4. Use script to perform update: run upgrade.4.6.bat
6-2-2-3 Alternative: manual install 1) Run StopService from the start menu. 2) Add/Replace the existing old files with new in the \HP\SAPSMeter path. The default locations are: C:\Program Files (x86)\HP\SAPSMeter\var\opt\hpmvma\standalone-servicejar-dir\sapsm-windows-4-6.jar C:\Program Files (x86)\HP\SAPSMeter\var\opt\hpmvma\services\sapsm0\conf\ appconfig.xml 3) StartService.
Version 4.6.01
46
6-3 Unix (agent version 4.3+)

6-3-1 SID exclusion list
To exclude SIDs on the local server from being collected and transferred the config file needs to be modified directly. To do that open /var/opt/hpmvma/services/sapsm-0/conf/sapsmd.conf in an editor. Look for the section #exclude sap list. Enter or modify the sap_exclude_list tag with a comma separated list of SIDs. Example: #exclude sap list sap_exclude_list=ABC,T01 Please open the /var/opt/perf/parm file (parm.mwc in Windows) and remove all entries from SAPS Meter which contain the unwanted SIDs. Then finally restart the SAPS Meter agent and the Performance Agent.
6-3-2 Utilities
6-3-2-1 register.sh
The most important utility is register.sh. Register is the one utility to configure and test connections.
6-3-2-2 report
The agent has a feature to simply check the configuration. # /opt/hpmvma/bin/report Script for reporting on configuration of the HP Multi-vendor Monitoring Agent usage: build jre cms check services the build number of the agent installation the version of the JRE parameters for communication with the CMS checks the software installation services currently installed
# /opt/hpmvma/bin/report build Agent installation build number: A.05.65.0373 (build 20110518:1228) A.05.65 = Version
.0373 = build number (build 20110518:1228) = (build [Date]:[Time]) # /opt/hpmvma/bin/report jre JRE path: /usr/java/jre1.5.0_22/bin/java JRE version: java version "1.5.0_22"
Version 4.6.01
47
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22b03) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_22-b03, mixed mode) # /opt/hpmvma/bin/report cms Standalone agent CMS not configured = standalone mode # /opt/hpmvma/bin/report check SM5....T /var/opt/hpmvma/conf/config.xml
Shows all changes since intallation - including deleted files. Config files get changed during the installation, so they are marked. # /opt/hpmvma/bin/report services Directory: sapsm-0 Service name: 'sapsm' Version: 4-2 Description: SAPs Meter
6-4 Windows
Windows comes with a slightly different set of utilities than the Unix packages
File Name 7za.exe awk.exe INSTSRV.EXE, reg.exe, SRVANY.EXE, NTEventLogAppender.dll config.bat Register.cmd service.cmd StartService.cmd StopService.cmd
description Used during install to extract file from zipped container Used to enable scripts to read structured files Use to register the SAPS Meter service as a Windows service Configuration information Agent register command . starts the registration dialog Register agent service as windows service Start SAPS Meter agent service Stop SAPS Meter agent service
Type Tool Tool Windows Resource Kit Tools Agent program Agent program Agent program Agent program Agent program
Version 4.6.01
48
uninstallService.vbs uninstall.cmd SCHEDULETASK
Uninstall agent service Uninstalls the SAPS Meter agent package Windows schedule tasks configuration file
Uninstall script Agent program
6-4-1 SID exclusion list

To exclude SIDs on the local server from being collected and transferred the config file needs to be modified directly. To do that open c:/programfiles(x86)/hp/SAPSMeter/var/opt/hpmvma /services/sapsm-0/conf/sapsmd.conf with an editor. Look for the section #exclude sap list.
Enter or modify the sap_exclude_list tag with a comma separated list of SIDs. Example: #exclude sap list sap_exclude_list=ABC,T01 Please open the parm.mwc and remove all entries from SAPS Meter which contain the unwanted SIDs. The parm.mwc is in newer OVPA versions in a hidden folder within application data, so the Windows search may not show it. Then finally restart the SAPS Meter agent and the Performance Agent.
Version 4.6.01
49
6-5 Parm file

The SAPS Meter will create a section in the Performance Agent parm file ### BEGIN SAPSMETER ### # Section which SAPS Meter adds and maintains ### END SAPSMETER ### This section will contain all SAPS Meter statements. You can also block the SAPs Meter in looking into parts from the parm file ### PROTECT FROM OVERWRITE ### # Section ignored by SAPS Meter ### END PROTECT FROM OVERWRITE ###
WARNING: The use of protect from overwrite should be only executed when the user fully understands how the Performance Agent uses this file. By protecting sections in front of the SAPs Meter section, the Performance Agent may not count all needed applications for SAPS Meter anymore . If the APP_THRESHOLD statement is set inside a protected section the Performance Agent will collect incomplete Data. HP does not recommend to use the protection function.
Version 4.6.01
50
7 The Web Portal

The Web Portal has two major functions:
To define which servers data is used in the reports It is the interface to the reports themselves
IMPORTANT: The portal has an online manual for all functions and reports. Please use the help function for how to and what does this mean questions.
7-1 User Registration on the Web Portal

The user registration is a self service. To register, complete the following: 1 2 Go to the web portal login page: www.hp.com/go/sapsmeter click on the sign-in link.
Figure Error! No text of specified style in document.-1 SAPS Metering Web Portal Homepage
Version 4.6.01
51
Enter your user ID and password and click Sign-in. If you are new to HP Passport please register first. HP Passport allows you to log in too many different HP web portals. When you see the SAPS Meter home page for the first time, please click on the Activate New Account link. This page will not appear in later sessions.
Please confirm your agreement with HPs terms of use, the link to them is at the bottom of the page.
Version 4.6.01
52
Now you will see the home page of the SAPS Meter Portal. It contains a message bulletin area, where important news are displayed.
7-2 Adding Servers to Your Report Portfolio

Users need to add SAP servers to their report view. Each server must be identified using some values which only authorized users know. This protects your report data from unauthorized access. 1 2 Log in to the web portal. Click on Manage SAP Servers in the left menu.
Version 4.6.01
53
Figure 7-2 Manage SAP Servers Page
For each server, enter the Customer ID , the Host FQDN and the machine ID Number and then click on the Submit button. Instead of adding the servers one by one you can upload a list of the servers. Please use the help page for details.
Figure 7-3 Add New SAP Server Page
When you have added servers the page will look like this
Version 4.6.01
54
7-3 Viewing Reports

To view reports, complete the following steps: 1 2 Log in to the web portal. Click on View Reports in the left menu.
Figure 7-4 View Reports Page
Version 4.6.01
55
3 4
Enter the date range. The date entered must be in the order: Year, Month, Day or use the date select buttons on the top. Select the Report Type from the dropdown menu. The selection of available reports is different for the SAPS Meter and the SAPS Meter PLUS service. Refer to the help link for further details. Select File Format from the dropdown menu.
HTML Display the data in the browser window. PDF, EXCEL, RTF Download the format in the selected format.
6 Select a report per server or per SAP instance. Please note that your reports will only contain data from those servers which you had added before. Check the box in front of the server or instance you want to select and then press the Create Report button. The selected report type determines if you can have single or multiple selections most reports allow only one selection. When you have many servers or SIDs the overview on the page will become difficult. For this you may open the Advanced Options section. Here you can apply different filters to the shown items store and retrieve report definitions. For details use the help page.
Version 4.6.01
56
7-3-1 Available Reports

for all SAPS Meter customers
Consumption shows the resource consumption for the selected server or SAP system as a simple graph Peak shows the hourly peak values for the selected server or SAP system as a simple graph Correlation - shows the correlation between IO and SAPS for the selected server or SAP system Detail provides all 5 minute measurements for the selected server or SAP system Summary a table for the selected server or SAP system with all consumption values Inventory a selection of tables for all selected servers and SAP systems with all consumption values and all details known to the portal.
for SAPS Meter PLUS customers
Advanced Detail provides all 5 minute measurements for the selected server or SAP system including SAP data if collected Visual Time series shows all individual 5 minute measurements for all selected servers or SAP systems in a single color pixel graph. When the timeframe exceeds 31 days the values are aggregated into hour values. This report is interactive and offers a number of unique analysis capabilities, significantly faster than analysis per spreadsheet. A specific feature is the simulation mode. Visual Prediction first a platform is selected either from a list of offered servers or from the list of existing servers (upper list). Then all applications/SIDs are selected which are analysed related to that platform. The prediction shows the summed up values from the applications/SIDs in relation to the platform capacity in percent for the past and into a predicted day profile. Distorted Scatterplot this also shows all measurements from the selected servers or SIDs in a 3 value scattergram. There are several unique features to analyse congested data areas. This is a ideal report for a quick before / after analysis.
Version 4.6.01
57
8 Understanding the Data

8-1 Measurements and Values
SAPS Meter measures the following values through HP Performance Agent (aka MeasureWare, OVPA): All these values are collected for each application which is running with the following definition: <SID>adm which is the SAP standard user for all applications belonging to the SAP system with the SID <SID> ORA<SID> - which is the Oracle user belonging to the <SID> The collection configuration is automatically entered into the configuration for the Performance Agent (parm file). The SAPS Meter is using the same collection values by all current agents making the values compareable across platforms. Details from MeasureWare documentation (5.0): APP_CPU_TOTAL_UTIL The percentage of the total CPU time devoted to processes in this group during the interval. This indicates the relative CPU load placed on the system by processes in this group. On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available. Large values for this metric may indicate that this group is causing a CPU bottleneck. This would be normal in a computation-bound workload, but might mean that processes are using excessive CPU time and perhaps looping. If the "other" application shows significant amounts of CPU, you may want to consider tuning your parm file so that process activity is accounted for in known applications: APP_CPU_TOTAL_UTIL = APP_CPU_SYS_MODE_UTIL + APP_CPU_USER_MODE_UTIL
NOTE: On Windows, the sum of the APP_CPU_TOTAL_UTIL metrics may not equal GBL_CPU_TOTAL_UTIL. Microsoft states that "this is expected behavior" because the GBL_CPU_TOTAL_UTIL metric is taken from the NT performance library Processor objects while the APP_CPU_TOTAL_UTIL metrics are taken from the Process objects. Microsoft states that there can be CPU time accounted for in the Processor system objects that may not be seen in the Process objects. APP_MEM_RES On Unix systems, this is the sum of the size (in KB) of resident memory for processes in this group that were alive at the end of the interval. This consists of text, data, stack and shared memory regions. On HP-UX, since PROC_MEM_RES typically takes shared region references into account, this approximates the total resident (physical) memory consumed by all processes in this group. On all other Unix systems, this is the sum of the resident memory region sizes for all processes in this group. When the resident memory size for processes
Version 4.6.01
58
includes shared regions, such as shared memory and library text and data, the shared regions are counted multiple times in this sum. For example, if the application contains four processes that are attached to a 500MB shared memory region that is all resident in physical memory, then 2000MB is contributed towards the sum in this metric. As such, this metric can overestimate the resident memory being used by processes in this group when they share memory regions. Refer to the help text for PROC_MEM_RES for additional information. On Windows, this is the sum of the size (in KB) of the working sets for processes in this group during the interval. The working set counts memory pages referenced recently by the threads making up this group. Note that the size of the working set is often larger than the amount of pagefile space consumed. APP_DISK_PHYS_IO_RATE Not avalable for Linux
The number of physical IOs per second for processes in this group during the interval. In Linux the kernel does not collect the basic information needed for this, therefore the IO rate can only be collected for the entire server. Percentage of time the CPU was not idle during the interval. This is calculated as
GBL_CPU_TOTAL_UTIL = GBL_CPU_USER_MODE_UTIL + GBL_CPU_SYS_MODE_UTIL
GBL_CPU_TOTAL_UTIL
On a system with multiple CPUs, this metric is normalized. That is, the CPU used over all processors is divided by the number of processors online. This represents the usage of the total processing capacity available.
GBL_CPU_TOTAL_UTIL + GBL_CPU_IDLE_UTIL = 100%
This metric varies widely on most systems, depending on the workload. A consistently high CPU utilization can indicate a CPU bottleneck, especially when other indicators such as GBL_RUN_QUEUE and GBL_ACTIVE_PROC are also high. High CPU utilization can also occur on systems that are bottlenecked on memory, because the CPU spends more time paging and swapping. GBL_MEM_USER GBL_MEM_USER_UTIL is a percentage. To make it useable for SAPS Meter it needs to be multiplyed with the systems memory which also needs to be collected for this calculation. The GBL_MEM_USER_UTIL * system memory = GBL_MEM_USER which is than reported in the XML file. The number of physical IOs per second during the interval. Only local disks are counted in this measurement. NFS devices are excluded. On Unix systems, all types of physical disk IOs are counted, including file system IO, virtual memory IO and raw IO. On HP-UX, this is calculated as: GBL_DISK_PHYS_IO_RATE = GBL_DISK_FS_IO_RATE + GBL_DISK_VM_IO_RATE + GBL_DISK_SYSTEM_IO_RATE + GBL_DISK_RAW_IO_RATE On SUN, if a CD drive is powered off, or no CD is inserted in the CD drive at boot-time, the operating system does not provide performance data for that device. This can be determined by checking the "by-disk" data when provided in a product. If the CD drive has an entry in the list of active disks on a system, then data for that device is being collected.
GBL_DISK_PHYS_IO_RATE
Version 4.6.01
59
8-1-1 Data collected from SAP

The SAPS Meter PLUS agent collects from the CCMS the active dialog users, their response time and dialog step values from each instance of SAP installed on the local server. This data is collected in five minute intervals and aligned with the other 5 minute data. The SAPS Meter also collects the installation ID to align SIDs with Installation IDs. IMPORTANT: The data collection from SAP is currently not available for Solaris.
8-1-2 Other measures collected and processed

Every day the processor data is examined. If the processor changes, the next day the new processor data is used. Also the versions of the OS and the collection software are reported once a day, also the hyper threading status of the processor is identified. Every five minutes the number of active cores is collected. On servers where iCap or TiCap are used the SAPS Meter always collects the exact number of active CPUs. This value is used to calculate the correct SAPS.
8-2 Data values used in reports

NOTE: For a more complete and current description of all the reports and data values call the help function on the web portal to see the most recent web portal manual online.
8-2-1 SAPS
SAPS is defined by SAP in the SD Benchmark and is a transaction oriented metric.. SAPS are different based on the characteristic of the benchmark and the SAP version. In general the higher the restrictions on the benchmark and the newer the SAP basic system the higher is the computing power to process the same number of transactions. The SAPS Meter allows the user to select the reference SAP basic system version on each server. With this it uses the SD Benchmark with no unicode and 2 second responsetime.
8-2-2 Hour related report values consumption and summary report

If the values SAPSh, IOPSh or GBh are used, these are calculated from the 5 minute interval samples and represent the hourly consumption equivalents. If MeasureWare is diverting from the exact 5 minute sample pattern, the values are counted to the start of the 5 minute interval. The graphical report then shows the sum of these values for the hour. This is equivalent to an average hour value. For convenience the values are converted to kilo SAPS and kilo IOPS. The blue line showing the total values in the consumption report for the entire server is sometimes lower than the stacked application total. In these cases the total value is taken from a different metric because the same metric unit as for the application is not available
Version 4.6.01
60
from the measurement system and is therefore not comparable. This differs from platform to platform.
8-2-3 Peak value report

The values of SAPS, IOPS and GB represent the peak value of a one hour interval. For each hour the maximum value is displayed. The blue line showing the total values for the entire server is sometimes lower than the stacked application total. In these cases the total value is taken from a different metric because the same metric unit as for the application is not available from the measurement system and is therefore not comparable. This differs from platform to platform.
8-2-4 Detail report

In the detail report the raw data samples are converted for each five minute interval into SAPS, IOPS and MB. They can be exported to csv to load them for further analysis into Excel or other statistic systems. They can also be stored away for audit in billing situations. Detail reports create a vast amount of data.
8-2-5 Correlation Report.

The correlation report shows each 5 minute sample as a dot. The values of SAPS and IOPS define the position in the diagram. The patterns vary by SAP system types and indicate if the system is well configured or if problems occur. More details on how to interpret these patterns will be published in the future.
8-3 Known Limitations

The SAPS Meter is improving its accuracy from version to version. These are known limitations: MeasureWare 32 bit limitations in some older versions of MeasureWare
there are limitations on numbers bigger than 32 bits. The values delivered above that threshold are not valid. Please ensure that you use a patched version of MeasureWare without this limitation.
Version 4.6.01
61
9 Frequently Asked Questions

There are a number of issues which prevent data from showing in the web service. Please refer to the FAQs in this chapter for recommendations on what action you should take.
9-1 What can I do when no systems or servers are shown in the web service pages?
Table 4-1: SAP Systems and servers missing in the web service Possible Causes
View active items flag
What/Where to check
There is only older data in the database (more than 10 days old) , Open advanced options in the report page and check the view active items flag
Recommended Actions
Set flag to no
HTTPS: A firewall or proxy issue prevents the data to be sent to HP
When absolutely no server is visible Verify that the firewall settings are and the SAPS Meter has just been as listed in 3-3-2 installed, this is a highly likely issue. With Agent 4.0: Use the sapsmd_utility connection test With agent 4.3 use the register utility For proxy issues contact HP support for help. If you are using a NTLM proxy from Microsoft please ask for the NTLM proxy service note.
The servers are not registered for the user to view No data received yet, after fresh installation The OV Performance Agent does not collect useful data
On the web service look up Manage Register the missing servers, see section 7-2 SAP Server The data transmission is daily If the installation was less than 48 around midnight. To provide reports hours ago, please wait 2 transmissions are needed. In the /var/opt/perf/parm The data collection is automatically configured during installation and updated afterwards. However some circumstances may lead to parm file configurations which prevent a collection of useful data. Look for application entries with SAP_xxx and ORA_xxx For each SAP application user xxxadm there has to be an entry
application = SAP_xxx user = xxxadm

xxx stands for the SID. There are also similar entries for the Oracle processes. These entries must be in front of all other application entries entered for other purpose to avoid race conditions for the data collection. Ensure that your SAP Meter agent has version date code equal or above 09232008
Version 4.6.01
62
The OV Performance agent is not running The OV Performance agent is running but data is not collected
What/Where to check
ovpa status
Recommended Actions
# /opt/perf/bin/ovpa restart
Check the modification datas on logglob and logappl, is the file zize changing after 5 minutes?
Stop OVPA then delete all log data files from OVPA, it will recreate them after a restart. Warning: the old data in the files is lost.
The SAPS Meter agent is not running
Restart
Agents 4.3 HP-UX:

/sbin/init.d/hpmvma stop /sbin/init.d/hpmvma start
Linux:
/etc/init.d/hpmvmastop /etc/init.d/hpmvmastart
Agents 4.0 Windows: use OS function to

manage services HTTPS: The server registration did not work correctly Has there been any error message during the registration? Agent 4.3 please check log message /var/opt/hpmvma/services/sapsm0/var_opt_sapsmd/log/sapsmd_regi ster.log The server registration submitted unusual system values The Engineering Note: Entering the Please obtain the most recent right values into the configuration version of the service note has not been used config entry.doc and use the values listed there. Repeat SAPS Meter server registration - call the register function
Version 4.6.01
63
FQDN values do not match
What/Where to check
Check if in the etc/hosts The values are in the right order. Correct: (as in main page) <own IP Address> <own full domainname> <alias, e.g. own short hostname> Wrong (example): <own IP Address> <own short hostname> <own full domainname>
Recommended Actions
Correct values and use the exact same FQDN name in the web service registration
EMAIL: wrong MX domain
You have entered a valid MX domain which is still not accepted by the email relay Another likely issue with emails is that the sender function of the SAPS Meter is not permitted to send emails. The sender is called through cron and the default user is root. But root maybe not permitted to send emails. To check this look at the following commands: find / -name cron.allow
Try other valid MX domain see 0
EMAIL: sending user lacks email sending permissions
Change user.
9-2 How to validate the email MX domain

The SAPS Meter Email configuration will ask for the MX domain. There is a test in the installation dialog which tests your entry right away. But only a company internal mail domain would pass this test and if this is used, the emails will not be sent to HP. Therefore it is necessary to ensure that the MX domain is valid externally. We have not found a method to look up a valid external MX domain. Usually the external valid MX domain is part of the email address of employees of the company, or it can be found in the from addresses in a mail.log . To verify if the MX domain is valid use the following steps: Nslookup type=MX <mx domain> The output should look like this: /opt)(root)#nslookup -type=MX mycompany.com
Version 4.6.01
64
Using /etc/hosts on: myserver looking up FILES Trying DNS Non-authoritative answer: mycompany.com preference = 10, mail exchanger = xxx1.mycompany.com mycompany.com preference = 10, mail exchanger = xxx2.mycompany.com mycompany.com preference = 10, mail exchanger = yyy1.mycompany com mycompany.com preference = 10, mail exchanger = yyy2.mycompany.com Authoritative answers can be found from: xxx1.mycompany.com internet address = 18.21.131.11 xxx2.mycompany.com internet address = 18.21.131.12 yyy1.mycompany.com internet address = 18.21.132.11 yyy2.mycompany.com internet address = 18.21.132.12
CAUTION: Please note that the following is not an external valid MX domain:
/opt)(root)#nslookup -type=MX aaa.bbb.mycompany.com Using /etc/hosts on: myserver looking up FILES Trying DNS aaa.bbb.mycompany.com preference = 10, mail exchanger = vvv.aaa.bbb.mycompany.com vvv.aaa.bbb.mycompany.com internet address = 11.222.111.222
The following is an example of a safe test from a remote network (here from a windows cmd line): Microsoft Windows [Version 6.0.6000] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C: >nslookup -type=MX mycompany.com Server: resolver.xx.yyy Address: 16.110.135.51:53 Non-authoritative answer: mycompany.com MX preference = 20, mail exchanger = gmmxz.mycompany.com mycompany.com MX preference = 10, mail exchanger = gmmxa.mycompany.com mycompany.com MX preference = 10, mail exchanger = gmmxb.mycompany com mycompany.com MX preference = 10, mail exchanger = gmmxc.mycompany.com
Version 4.6.01
65
gmmxd. mycompany.com internet address = 12.85.14.10 An invalid MX domain would look like this: C: >nslookup -type=MX aaa.bbb.mycompany.com Server: resolver.hp.net Address: 16.110.135.52:53 *** resolver.xxx.net can't find aaa.bbb.mycompany.com: Non-existent domain
Version 4.6.01
66
9-3 What can I do when values in a report are not reasonable?

Table 4-2: Reasons for values not reported correctly Possible Causes
The OV Performance Agent does not collect useful data
What/Where to check
In the /var/opt/perf/parm
Recommended Actions
For each SAP application user The data collection is automatically xxxadm there has to be an entry configured during installation and application = SAP_xxx updated afterwards. However some user = xxxadm circumstances may lead to parm file configurations which prevent a xxx stands for the SID. There are also similar entries for the Oracle collection of useful data. processes. These entries must be in front of all other application Look for application entries with entries used for other purpose to SAP_xxx and ORA_xxx avoid race conditions for the data collection. Windows look for parm.mwc. Usually it is under BTO Software. Ensure that your SAP Meter agent has a version date code equal or above 09232008 If still in doubt, contact HP SAPS Meter support with your parm file.
The OV Performance agent is not always running
Restart
# /opt/perf/bin/ovpa restart
The SAPS Meter agent is not always running
Restart
HP-UX: sapsmd start Linux: /etc/init.d/sapsmd start Windows: use utility in start
menue
The server registration submitted unusual system values SAPS calculation fails
The Engineering Note: Entering Please obtain the most recent version of the service note the right values into the configuration has not been used config entry.doc and use the values listed there. Register the missing servers
Not all servers of a SAP system are Lookup the list of servers in the registered for report report page. Is it complete? Processes are missing because a uncommon SAP configuration Follow the instructions above under The OV Performance Agent does not collect useful data
Version 4.6.01
67
9-4 What logfiles does the SAPS Meter agent use?

9-4-1 Windows Agent 4.6
All the SAPS Meter logfiles are in the log directory as shown in chapter 3 for each platform. They are configurable by editing logging.conf The logfiles are
9-4-2 Unix Agent 4.6

the saps-meter service log files are at
/var/opt/hpmvma/services/sapsm-0/var_opt_sapsmd/log/
sapsmd_cache.log log message for collecting data like SAP performance data and VMware ESX information sapsmd_register.log log messages during the registration dialog sapsmd_service.log general service log message sapsmd_collector.log log meessage for Performance Agent data collection and writing synchronised data into the collection xml data file sapsmd_sender.log log message for sending data to the HP Portal sapsmd_updateparm.log log message for Performance Agent parm file update and related tasks
Version 4.6.01
68

SAPS Meter 4-6 Installation and Configuration Guide

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

SAPS Meter 4-6 Installation and Configuration Guide

Transféré par

Droits d'auteur :

Formats disponibles

SAPS Meter 4.

Installation and Registration Overview .............................................................................. 11 Installation process ........................................................................................................... 12

3-2-1 3-2-2 3-3

3-3-1 3-3-2 3-3-3 3-3-4 3-3-5

3-3-5-1 3-3-6 3-3-7 3-3-8 3-3-9 4

4-1-1 4-1-2 4-2

4-4-1-1 4-4-2 4-5 4-6

How to Check and Uninstall ....................................................................................... 22

6-2-2-1 6-2-2-2 6-2-2-3 6-3

6-3-2-1 6-3-2-2 6-4

Windows ........................................................................................................................... 48 SID exclusion list ....................................................................................................... 49

Parm file ........................................................................................................................... 50

8-1-1 8-1-2 8-2

8-2-1 8-2-2 8-2-3 8-2-4 8-2-5 8-3 9

Known Limitations ............................................................................................................ 61

1-2 Product Overview

1-2-1 SAPS Meter Plus

2-2 Product Overview

2-2-1 SAPS Meter Plus

2-2-2 Agent Version 4.6

VM Ware host interface

sapsmd service HP MVM Agent

2-3 Installation and Registration Overview

2-4 Installation process

Check Prerequisites and Collect Required Information

Configure and Register Agent (register.s

Not supported or untested are

3-2 Software dependencies

MeasureWare OpenView Performance Agent HP Performance Agent Performance Component ScopeUX

3-3 Information needed during Installation

3-3-1 Customer ID and SAP version

3-3-2 Firewall Settings for https transfer

Destination address https:// h30081.www3.hp.com

15.216.12.77 15.217.53.94 Please configure both addresses as valid targets.

Port 443 Protocol HTTPS Outbound only

3-3-3 Data transfer information

Proxy Address Proxy User ID Proxy Password

3-3-4 Prerequisites for email transfer

3-3-5 SAP user credentials (SAPS Meter PLUS only)

3-3-5-1 SAP User minimal Authentication (SAPS Meter PLUS only)

RFC_NAME SYST RFC1 SDIFRUNTIME SXMI SALX SYSU

3-3-6 Solaris Zones

3-3-7 Optional: Processor data

3-3-8 VMware for Linux or Windows

VMware ESX 4.0 Linux or Windows Guest OS

Configuration Parameter requirement:

3-3-9 Registration data

Other Platforms: the server Serial number is used as Machine ID

4 Installing the SAPS Meter Software

Continue with chapter 5 registration and configuration dialog

The list of installed files is in chapter 4.5.

4-1-2 How to Check and Uninstall

HPSAPSM HPSAPSM.hpmvma Agent

HP SAPS Meter Agent

A.05.65 HP Multi-Vendor Monitoring

Continue with chapter 5 registration and configuration dialog

The list of installed files is in chapter 4-5.

4-2-2 How to Check and Uninstall

4-3 Sun Solaris

-> for Intel, AMD -> for Sparc

Continue with chapter 5 registration and configuration dialog

The list of installed files is in chapter 4-5.

4-3-2 How to Check and Uninstall

01 001 test t test,sah3cd02 DL36-359.usa.com 01 000 DDIC a DL36-359