SAP Sybase Legacy License Audit Process & Methodology

Transcription

1 SAP Sybase Legacy License Audit Process & Methodology Version 2.0 December 2015

2 TABLE OF CONTENTS MISSION STATEMENT PURPOSE OF THE SAP SYBASE LEGACY LICENSE AUDIT SCOPE METHODOLOGY PROCESS PRINCIPLES AND LICENSE MODELS INVENTORY REPORT DATA COLLECTION BEST PRACTICE WHEN VERIFYING MACHINE CAPACITY AND NUMBER OF DEVICES APPENDIX

3 This Guide contains supplementary information about SAP SE s and Sybase Inc. s product licensing, providing additional information about the SAP SE and Sybase Inc. price lists and your SAP software contract and Sybase Inc. License Agreement. If there are any contradictions with the terms of your SAP or Sybase software contract, then the terms of your contract and the SAP Sybase Inc. price list that your contract is based on apply. 3

4 MISSION STATEMENT Our goal is to work with our customers on an ongoing basis to ensure they are properly licensed and to help our customers accurately manage their use of SAP Sybase Legacy Program Licenses. We have well-defined processes and approaches that we follow. We strive for consistent and efficient audit processes. All information requested during the audit process is directly related to verifying the customer s use of their SAP Sybase Legacy Program licenses with the mutually agreed upon agreement terms and conditions. This process description is intended as a general overview of the SAP Sybase Legacy License Audit methodology. Note: This process may be changed without notice as required. 1 PURPOSE OF THE SAP SYBASE LEGACY LICENSE AUDIT As part of our standard license review process, the SAP Global License Auditing Services Team periodically reviews our customers use of Sybase Legacy Programs to verify that customers are appropriately licensed. To facilitate the license review, we request that customer self-report their use of Sybase Programs. The completed self-declaration documents will assist us in determining whether customer is appropriately licensed, has the suitable support profile, and help determine whether further review is necessary. 2 SCOPE Relevant for license audit are all SAP Sybase products licensed by the customer under the Sybase Legacy End User License Agreements (EULA). Product Names are as listed in the customer s inventory report template provided or on the customer s latest maintenance quote. Territories in scope are all countries and subsidiaries using the licensed products. Licenses in scope are all license types and metrics in use by the customer. Time Period covered in the audit scope are all Sybase Program licenses currently installed unless there are special contract agreements such as Copy Pool or Site License Agreements. Audits involving special contract agreements will be specified by the SAP License Audit team. 3 METHODOLOGY To facilitate the license review, we request the customer to self-report their use of Sybase Programs and send the completed Inventory Report template to SAP Sybase License Audit Team. 4

5 4 PROCESS To facilitate the license review, we request customer to self-report the use of Sybase Programs: A. Accurately and fully complete and sign the attached Inventory Report identifying the installation and use of Sybase programs. The Inventory Report is included with the license audit request . B. Send the completed and signed Inventory Report to: C. A Verification Call will be scheduled once the inventory is received and SAP Sybase License Audit team has reviewed the inventory. The Verification Call with the Customer ensures that there is a mutual understanding of the information provided. This may result in a request for additional information from the SAP License Audit team. As part of the review, the SAP License Audit team will require the customer s IT administrators and DBAs, who worked on completing the inventory report, to be present during the Verification call. This reduces any misunderstanding on the information provided and allows for a more efficient audit. SAP reviews the reports to ensure all licenses deployed are consistent with the entitlements, Terms and Conditions of the Agreements. During this call, proposals to collect any additionally required information to verify the use of the reported licenses may be put forward. Any additional information that may become available after the verification call, may include - but is not limited to - running some basic scripts to confirm the native Operating System and number of physical cores in the machine (or partitions in some cases) as specified by the license contract type(s) of the program(s) that are audited. D. Onsite Verification (Potential) As part of the SAP Sybase Audit Best Practices, SAP may request and perform an Onsite Verification to ensure accuracy of the audit information and to avoid misunderstandings. The agenda of the Onsite Verification will result from the Inventory Report Verification. The topics of the Onsite Verification may require technical support. Note - for a successful Onsite Verification: The SAP License Audit team will need contact person(s) on customer s side with the required technical knowledge and authorizations to access the physical machines that run the Sybase Programs as necessary, including running several spot checks per location. All verification activities are to be performed by customer s employees and not by the SAP License Audit team. E. Once all mandatory and essential information and data are available, the SAP Sybase license audit can be completed. 5

6 5 PRINCIPLES AND LICENSE MODELS As per the Terms and Conditions of the Sybase Legacy Agreement, the licenses granted are to be used for customer s internal business purposes by customer s employees, agents and contractors and on the Operating System and locations specified on the signed agreement. Additionally, the licenses are non-transferable, i.e. they may not be used by a Third Party without prior consent given by Sybase/SAP. Sybase s two standard license models are machine-based and device-based. The License Type (also called License Contract Type) is the metric used to determine how a product is licensed, i.e. whether it is machine or devise based. Sybase Standard License Models The machine-based license model covers the entire physical machine per CPU, Chip or MSU (Mainframe) for both internal and external devices. The device-based model licenses a Server and Networked Seats or a Server and Concurrent Users. Find below some key elements of the Sybase Legacy Licensing principles based on the standard Sybase License contract. For further information regarding license metrics, license types and their definitions, review your signed Sybase Legacy License Agreement, Exhibit A. Note: Additional Product Specific License Terms may apply: While the license keys are of great importance for many reasons, they do not represent any kind of final statements regarding the compliancy to your license agreement. 5.1 Machine and Server The definitions of Machine and Server are the main components of the License Contract Types. The terms Server and Machine may be used interchangeably in some cases. As per Sybase Legacy License Agreement, A Machine is as a single computer hardware system, running a single copy of the Operating System Software where the Sybase Program Software is in Use. A Server is as a Machine containing software, which permits it to await and fulfill services to other computers. In case of a cluster or grid computing environment, each node or host Machine is considered an individual Server. 5.2 CPU License Contract Types The CPU License Types define the licensing and usage of the Sybase CPU licensing model. It is the unit of measurement used in the CPU License types for Sybase Programs. For Sybase Programs, the number of CPUs is equal to the number of Processors or Cores on a Machine that runs the software. As all the CPU Cores on a Machine are relevant and as a Machine is defined as a single computer hardware system, all the physical CPU Cores on the Server are to be counted. 6

7 Note: Virtual cores are not relevant measurement/license metric under the Sybase legacy contract agreements. This license metric includes external usage by Seats outside of the Customer's organization accessing the Program via the Internet ("Internet Users"). In the event that the number of CPUs on a Server is increased, Customer shall report such increase as additional licenses may be required. Refer to your Sybase Legacy agreement, Exhibit A Part 2 for the complete list and definition of CPU License types. Find further information about metrics and definitions in your Sybase Legacy Agreement, Exhibit A Regarding Sub-Capacity licensing There are multiple types of Partitioning, Virtualization and Resource Management technologies available. Not all of these methods are offered or supported by Sybase (see Appendix 1 for overview). Sub-Capacity licensing refers to licensing a subset of the physical cores available on a physical machine. Note: Virtual cores are not relevant measurement/license metric under the Sybase legacy contract agreements. From a technical support perspective, refer to the Release Bulletin or other technical documentation for the specific product in question for the latest list of supported eligible environments. Whether you are entitled to run your Machine in a Sub-Capacity environment, i.e. license the physical cores in use by the containment level in a partition or resource level etc. depends on your Sybase Legacy agreement. 5.3 Server/Networked Seat License Model Within the Sybase Legacy Agreement, a Server License is the limited right to Use the Program on a Server, for access solely by licensed Seats or licensed Concurrent Users, as applicable. A Networked Seat license or a Concurrent User license is defined as a specific, identifiable, unique input/output device capable of directly or indirectly accessing and using a Program such as (without limitation) a terminal, personal computer, single user workstation, personal digital assistant ("PDA"), wireless device or real time device. Networked Seat and Concurrent Users are for the customer s internal use only. Note: External (non-employee) access to the licensed Sybase program is not included in this licensing model. Refer to your Sybase Legacy agreement, Exhibit A Part 2 for the complete list and definition of the Sybase License types. 7

8 6 INVENTORY REPORT DATA COLLECTION The Inventory Report is a report of all programs in use at a given time and should reflect the use of Sybase programs within Customer s environment unless specified otherwise. This report is not an entitlement report. The standard inventory report template may request the listed information below from the customer. The standard inventory report template may be enhanced by additional information as required, depending on the customer s licensed Sybase products and License Contract Types. It may not be limited to the listed information below. Contact your SAP License Audit team for details and further information at sybaseauditemea@sap.com Item/Category Description Example Name of Sybase Program/ Options, Version Program Install Date (M-YYYY) Site Location Host Name Host ID Machine Provide Name, Version and Bit of the Sybase program and any licensable Sybase Option in use Enter the original installation date of the Sybase program, not the date of installation on current hardware or last update. This date should allow identifying the order that corresponds to that license. Enter the City and Country where the Server with the Sybase program are located. Enter the Host Machine name. This information is required to verify the information provided, for example if there may be multiple instances of ASE installed on a host. The ASE server should be counted only once but we need to ensure the Seats are identified and counted appropriately across all instances. The Host ID is a unique identifier for a particular machine. Enter the physical machine's Host ID regardless of any sub-capacity environment in place. To determine the Host ID of the machine, run the lmutil utility. The type of Host ID returned by lmhostid utility will depend on the platform. You can also determine the Host ID using native operating system commands Enter the Hardware Make & Model of the physical machine ASE Enterprise Edition 64 Bit version 12.5 ASE Enterprise Partitions Option May-2010 Walldorf, Germany RedwoodPROD A4-16-9B-A2 Sun Fire X4140 8

9 Item/Category Description Example Operating System Use Type Enter the Operating System version and bit in Use on the Machine that runs the Sybase Program Enter the system type and environment in use like Production, Development, Test or Standby system Solaris 10 64bit Production Logical Cluster Name Indicate as appropriate abtorf-pr1 Physical Cluster Name Indicate as appropriate abtorf Type of Partitioning Used Partitioning/ Virtualization Total # of Seats Externally Accessed Number of Physical CPU s Number of Physical Cores Virtual Machine Deployed in SAN Middleware Only (Source and Target) Enter the type of Partitioning and/or Virtualization Technology in Use Enter each part separate with number of physical CPU & Cores per partition Enter the total number of unique devices such as Laptops, PCs, PDA's or real-time devices that have direct or indirect access to the Sybase Program on the Server Indicate whether the Sybase Program is accessed by persons who are not employees, agents or independent contractors Provide the total number of all physical CPUs on the entire Machine, irrespective of the number of CPUs used by the Program Provide the total number of all physical cores on the entire Machine, irrespective of the number of Cores used by the Program Indicate the Use of Virtual Machine (Yes/No) Indicate if deployed in Storage Area Network (Yes/No) This is required to verify the information provided and avoid miscounting when Middleware products are licensed like Replication Server, ECDA, Mainframe Connect, etc. Enter the Source and the Target ASE Host Name for Rep Server, ECDA, MFC, etc. LPAR LPAR1= 2CPU/ 4 Cores LPAR 2= 2 CPU/ 4 Cores 53 Y 2 4 Y Y [Source] A4-16-9B-A2 [Target] A4-18-9C-A6 9

10 Item/Category Description Example Business Description of Use Enter a high-level application description that is using the Sybase Product. This information is required to make sure the information provided appears accurate and to understand how the program is being used in order to validate the information reported. Customer Banking Inquires 10

11 7 BEST PRACTICE WHEN VERIFYING MACHINE CAPACITY AND NUMBER OF DEVICES As part of the review, additional information will be required for data verification. The type of information requested depends on the License Contract Type in use. Find below some of the additional information that may be requested as required and appropriate. 7.1 Machine Based License Contract Type per CPU, Chip or MSU To verify the full machine capacity, the SAP License Audit team may request that customer run some basic scripts or commands. If a SySAM enabled Sybase Product is in use: Run <cpuinfo-v> on the physical Machine For all other cases, native Operating System are available as required and as appropriate. 7.2 Device Based License Contract Type per Server/Seat To verify the number of Servers the (physical) Machine, Host Name and Machine Host ID and other factors will be taken into account. For the total number of Seats that access the Server and to verify the type of access, the SAP License Audit Team requires an accurate Business Use Description. This includes - but is not limited to - a description of customer s application used by customer to access the Server. Additionally, a high-level architectural diagram of customer s Sybase landscape may be requested. 11

12 APPENDIX 1 Refer to the Release Bulletin for each product for the specifically supported environments: 12

13 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.