LicenseKeys_SAPSystems.pdf

7/26/2019 LicenseKeys_SAPSystems.pdf

1/24

SAP White Paper

LICENSE KEYSFOR SAP SYSTEMS


2/24

2

Copyright 2006 SAP AG. 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 AG. The information contained herein may be changed

without prior notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software

vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/

ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries,zSeries, System i, System i5, System p, System p5, System x,

System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere,

Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+,

OpenPower and PowerPC are trademarks or registered

trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are

either trademarks or registered trademarks of Adobe Systems

Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks

of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C, World Wide Web Consortium,

Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc.,

used under license for technology invented and implemented

by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver,

and other SAP products and services mentioned herein as well as

their respective logos are trademarks or registered trademarks of

SAP AG in Germany and in several other countries all over theworld. All other product and service names mentioned are the

trademarks of their respective companies. Data contained in this

document serves informational purposes only. National product

specifications may vary.

These materials are subject to change without notice. These

materials are provided by SAP AG and its aff iliated companies

(SAP Group) for informational purposes only, without

representation or warranty of any kind, and SAP Group shall

not be liable for errors or omissions with respect to the materials.

The only warranties for SAP Group 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.


3/24

3

CONTENTS

SAP Software Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

General Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

SAP NetWeaver 2004s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Processing Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

License Key Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

SAP Service Marketplace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Software running on SAP NetWeaver Application Server ABAP. . . . . . . . . . . . . . . . . . . . . . . . 10

User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Generating a Temporary License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Generating Data for the License Key Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installing the License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

SAP NetWeaver Application Server Java or J2EE Engine Standalone . . . . . . . . . . . . . . . . . . . . 13

User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13


Generating a Temporary License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Generating Data for the License Key Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Installing the License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Applications Running SAP Enterprise Portal (prior to SAP NetWeaver). . . . . . . . . . . . . . . . . . 15

User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

SAP Enterprise Portal (EP) SAP NetWeaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

SAP Enterprise Portal 6.0 SP2 and lower (prior to SAP NetWeaver) . . . . . . . . . . . . . . . . . . . . . . . . . . 15


Generating A Temporary License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

SAP Enterprise Portal SAP NetWeaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

SAP Enterprise Portal 6.0 SP2 and lower . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Generating Data for the License Key Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

SAP Enterprise Portal SAP NetWeaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16


Installing the License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

SAP Enterprise Portal SAP NetWeaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16SAP Enterprise Portal 5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17


4/24

Deletion of SAP Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

SAP Service Marketplace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Deleting an SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Deleting a Further License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Moving a System to a New Installation Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Further SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Validity of the License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Expiration of SAP Enterprise Portal SAP NetWeaver: Permanent License Keys . . . . . . . . . . . . . . . 20

Unique System Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20License Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

High-Availability Clustered Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

SAP NetWeaver (AS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

SAP NetWeaver Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21


SAP Strategic Enterprise Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

System Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Command Line Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

SAP Web AS ABAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

After Expiration of a J2EE Engine License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4


5/24

To prevent unauthorized use of SAP software, its systems will

only work with license keys assigned by SAP. This document

describes how to obtain license keys and their use in SAP systems.

Note:Read this document carefully as the recommendations

given ensure the accessibility of SAP software.

SAP SOFTWARE PROTECTION

5


6/24

To obtain a license key, perform the following steps:

1. Install the software

2. Generate a temporary license key (only necessary for SAP

Enterprise Portal 5.0)

3. Obtain the data required for the license key request

4. Request a permanent license key

5. Install the permanent license key

Authorization To request a license key through the SAP Service

Marketplace, License Key Request authorization is needed.

A separate key per system Each license key is individually

calculated for a specific system. Therefore, a license key generated

for system A will not work in system B.

Copy & paste As typing errors frequently occur, copying andpasting system data onto online request forms reduces the

chance of errors.

SAP NetWeaver 2004 is the first release to have the following

technology components and tools included in the platform right

out of the box:

SAP Business Information WarehouseSAP NetWeaver Portal (Enterprise Portal 6.0 Support Package

Stack 3)

SAP NetWeaver Exchange Infrastructure

SAP Knowledge WarehouseSAP NetWeaver MobileSAP NetWeaver Application Server

Component releases and single products prior to SAP NetWeaver

2004 were the following:

SAP Web Application Server 6.20SAP Business Information Warehouse 3.1SAP Mobile Infrastructure 2.0SAP Exchange Infrastructure 2.0

SAP Enterprise Portal 6.0 on SAP Web Application Server 6.20(Enterprise Portal 6.0 Support Package Stack 2)SAP Knowledge Warehouse

SAP NetWeaver 2004s

Technology components were introduced with the release of

SAP NetWeaver 2004, and come already installed on the SAP

NetWeaver 2004s platform. They are described as usage types on

this newer release to differentiate from previous systems running

one or more of the single products shown before which had to

be installed separately and had separate license keys.

For example, as of SAP NetWeaver 2004 Support Release 1

(including 6.0 SP 9) there is no separate SAP NetWeaver Portal

license key required. As a further example, using the Business

Intelligence (BI) usage type, after the SAP NetWeaver 2004s

release, is equivalent to the SAP NetWeaver Business Intelligence

functionality incorporated in a system. Usage types are so named

to facilitate association with previous products, show their func-

tionality, and accord SAP or its customers a much better pictureof system use. The following usage types and their equivalents

in parentheses are delineated in recent SAP NetWeaver systems:

Business Intelligence (SAP Business Information Warehouse)BI Java component (new category)Enterprise Portal (SAP Enterprise Portal)Mobile Infrastructure (SAP Mobile Infrastructure)Process Integration (PI/XI) (SAP Exchange Infrastructure)Application Server ABAP (SAP Web Application Server)Application Server Java (J2EE Engine, SAP NetWeaver

Developer Studio, J2EE Engine Developer Workplace, and

more)

GENERAL INFORMATION

6


7/24

The SAP NetWeaver 04 Upgrade Master Guide and the Upgrading

Guidelines of the specific components describe how to upgrade

to SAP NetWeaver 04 in detail.

Three License Key Procedures: There are three license key

procedures depending on the SAP software technology group

involved. The appropriate one to use is in accordance with the

software after each heading in the following groups below:

Software running on SAP NetWeaver Application Server ABAP:

mySAP Customer Relationship Management (mySAP CRM)SAP Knowledge Warehouse (SAP KW)SAP R/3 EnterpriseSAP R/3mySAP Enterprise Resource Planning (mySAP ERP)

SAP Strategic Enterprise Management (SAP SEM)mySAP Supplier Relationship Management (mySAP SRM)mySAP Supply Chain Management (mySAP SCM)

SAP NetWeaver 2004 Application Server Java or J2EE Engine 6.30

standalone:

SAP NetWeaver Developer StudioPortal on SAP NetWeaver 2004sJ2EE Engine Developer Workplace

Applications running SAP Enterprise Portal (prior to SAP NetWeaver)

SAP Enterprise Portal EP6 SP2 and lower

Processing Times

Normally, requested license keys are available within an hour,

but can take up to a maximum of three working days. License

keys can only be downloaded after successfully requesting it

from the SAP Service Marketplace (see SAP Note 94998).

Overviews of system landscapes are updated automatically.

7


8/24

The following information is required for a license key request:

Installation number: a ten-digit number supplied by SAPcontract department when an installation is called up also

found on the delivery note for the system. New installations

can be called up via message on component XX-SER-GEN-CONTR

System ID: a three-digit/letter system name such as C11, ABC,and so on

Type of system: such as production or test (see Appendix)SAP product: software product name such as SAP NetWeaverProduct version: such as SAP NetWeaver 2004sTechnical usage: if requiredDatabase: database in operationOperating system: operating system in use such as AIXPlaned productive date: only for test and productive systems

necessary

Request type: such as standard systemHardware key: eleven-character string unique to the hardwareLicense type: standard, J2EE or Portal (see Appendix)E-Mail: e-mail address

To request a license key online, go to the SAP ServiceMarketplace

service.sap.com/licensekeys. The SAP Note 94998 is very helpful

for the license key request:

LICENSE KEY REQUEST

8

SAP Service Marketplace

The Internet address service.sap.com/licensekeys presents the initial

screen for requesting license keys and also offers general infor-

mation about them. Follow these steps to request a key or to

change an existing key:

1. Select Request License Key

2. Select an installation

3. Select New System to request a license key for a newly

installed system or select Change Details for System for an

existing system

4. Add the required system data and hardware data (see

Appendix for the correct license type and/or online informa-

tion button next to the license type.

5. Choose SaveContinue for a new or changed system request

6. Choose Submit to send the license key request to SAP

Figure 1: Requesting a license key

License keys for mySAP Business Suite

This page gives you information on how to apply for a license key for the SAP Business Suite.

License key requests via SAP Service MarketplaceAll of the license key requests are processed automatically. Usually you will receive the license key via email in a short time about 1 hour, maximum 3 working days.

NotesTo use the application, you must have the Request License keys authorizan. To request it, please contact the

SAP System Administrator in your companyIf you have any question, please read our Frequently asked questionsor a message with the XX-SER-LIKEY

component using the message wizard

Digitally encrypted license keys as of WEB AS 7.0

After you upgrade using the Basis Web Application Server 7.0 (ABAP), we recommend that you request and install the new digitally encrypted license key,Performance is improved due to the new digitally encrypted license key, since we do not require additional database access. When yoou make the request,ensure that you make it for the existing system and with the standard license type and that you choose WEB AS 7.0 as the Basis release. Please have alook at SAP Note 870871for further license key installation information.

Documentation

Service Corner

Request license key

Display license keysrequested by me


9/24

High-Availability Clustered Environment

A further license key for a high-availability environment can

be requested via the Internet addressservice.sap.com/licensekeys

(see SAP Note 181543). Proceed in the following way:

1. Request License Key

2. Select an installation

3. Select Change Details for System to request an additional

license key for a system

4. Enter the new hardware key

5. Choose SaveContinue

6. Choose Submit to send the license key request to SAP

All software dependent details and information can be found in

the following three chapters. You will find the information

relevant to you in the chapter that is assigned to the software you

have installed. Software running on SAP NetWeaver Application Server

ABAP

Software running on SAP NetWeaver Application Server Java

or J2EE Engine 6.30 standalone

Application running SAP Enterprise Portal (prior to SAP

NetWeaver)

9


10/24

User Interface

Both a graphical user interface (GUI) from SAP Basis Release 4.6C

onwards and a command line interface for SAP Basis Release 4.6B

or lower are available for SAP NetWeaver (AS) applications.

Note:Using the LicenseKey GUI (SLICENSE) instead of the

command line interface (saplicense) is strongly recommended as

it is easier to use, performs additional checks, and avoids most

handling errors. All saplicense commands are explained in the

Appendix.

Use the transaction SLICENSE to accomplish the following:

Display all installed license keysInstall a new permanent or temporary license keyDelete an installed license key

All screens shown in this document are based on SAP NetWeaver

2004s. The display and functions may vary with other releases.

SOFTWARE RUNNING ON SAP NetWeaver APPLICATION SERVER ABAP

10

Software Installation

When an SAP system is installed, a temporary license key is

created automatically. This key allows use of the system for a

period of four weeks giving time to arrange for the assignment

of a permanent license key. Once this period is up, the SAP system

can only be accessed with the username: SAP*.

Generating a Temporary License Key

As a temporary license key is automatically supplied during

software installation, it does not have to be created in most cases.

When changes are made to the hardware platform and a perma-

nent license becomes invalid, a temporary license key has to be

installed using the SLICENSE transaction. If this is the case, make

sure to keep any existing licenses so the system can determine if

a 4 week valid temporary license key is allowed.

Note:A temporary license key can only be installed if a perma-

nent license key in the system was used within the last 4 weeks.

To install a temporary license key, choose A. No additional

information is needed. Once the temporary license key is

installed, it is displayed in the list of licenses and is activated

immediately.

Figure 3: Temporary License Key

Use the transactionSLICENSE to accomplishthe following:Display all installed

license keysInstall a new permanent

or temporary license keyDelete an installed

license keyRequest a license key

Figure 2: License GUI


11/24

Generating Data for the License Key Request

Each system has a unique, encrypted hardware key to ensure it is

the only one used for a specific system. This hardware key needs

to be identif ied before requesting a license key from SAP and can

be located using the SLICENSE transaction. The hardware key

applies to the host on which the SAP message server is installed.

SLICENSE automatically detects the hardware key of the active

message server.

11

Figure 4: Generating data for the license key request


12/24

Installing the License Key

License keys may be installed using the SLICENSE transaction.

As of SAP NetWeaver 2004s, ABAP license keys will be digitally

signed. mySAP ERP 2005 is the f irst solution in mySAP Business

Suite running on SAP NetWeaver 2004s.

Note:A digitally signed license key should be installed when

upgrading to a software product that includes Web AS 7.0.

To install a digitally signed license key, do the following:

1. Choose New Licenses to enter the new license view:

SAP License Administration Digitally-Signed License Keys

2. Choose Install

3. Load the local file from the file system in the dialog box that

appears, enter the license key file and confirm

4. A message appears to confirm success5. The new license is displayed under Installed Licenses

6. Check ability to log on to the SAP System

The permanent license is installed, displayed in the list of

licenses, and activated immediately.

To install a license key (24-digits) that is not digitally signed,

do the following:

1. Enter SAP License Administration

2. Choose Install or choose Edit Install

3. Install License in the menu

4. Enter all relevant data

5. Choose Install New License

A system number is required as of SAP Web AS 6.10 (see Appendix).

Additional information is available at SAP Online Help: BC-Basis

ComponentsKernel Components BC SAP License.

12

Figure 5: SAP License administration

Figure 6: Installing the digitally signed license key


13/24

Note:The license process below is only valid as of J2EE Engine

6.30, but not valid for the Developer Edition or Sneak Preview

Edition. These have a temporary key for 90 days, but no perma-

nent key. Customers with SAP NetWeaver Application Server

ABAP and Java installed should use the license process described

in the SAP NetWeaver Application Server ABAP section.

User Interface

Customers can manage license keys and import license data

using the License Key Service. This service is accessed with the

Visual Administrator through the following path:

Services Licensing Adapter

It also reveals the following required data specific to a system:

Hardware key

System IDSoftware productsCurrent release

To have Visual Administrator display all the installed licenses of

an SAP system select: Services Licensing

Adapter Runtime Installed Licenses


During the standalone installation of an SAP NetWeaver,

Application Server Java or a J2EE Engine, a temporary license key

is installed in the system automatically. This key allows system

use for a period of four weeks after the installation (see Appendix).

Note:J2EE Engines installed with SAP NetWeaver do not need a

separate license key as they use the ABAP stack license key.

Generating a Temporary License Key

A temporary license key is generated by the system and is valid

for four weeks. When four weeks are up, it is not possible to

generate another one. The purpose of a temporary license key is

to give customers enough time to request a permanent license

key through the SAP Service Marketplace Website (see Appendix).

13

Figure 8: Generating a temporary license key

SAP NetWeaver APPLICATION SERVER JAVA OR J2EE ENGINE STANDALONE

Figure 7: Required system data


14/24


Each system has a unique, encrypted hardware key to ensure it is

the only one used for a specific system. This hardware key needs

to be identif ied before requesting a license key from SAP and

can be located using the Visual Administrator. To identify the

hardware key of the J2EE Engine, start its Visual Administrator

and follow this path: _ Services Licensing

Adapter. The hardware key is then found under the General tab.

Install additional license keys for a clustered environment with

the Visual Administrator. It shows only one license key per

hardware key and can install license keys for different hardware

keys without overwriting them. License keys can be displayed

with the Offline Configuration Editor (see SAP Note 731673).


1. Download the license key file supplied by SAP to a local disk

2. Start the Visual Administrator in the J2EE Engine and then

follow the path: Services Licensing Adapter

3. Use the Install License From File button to upload the file

4. Select the file with the downloaded license key

5. Choose Open to continue

6. Then a popup appears stating that the license has been

installed successfully

7. Restart the J2EE Engine

Check the license key under the Installed Licenses tab.

14

Figure 10: Installing the license key

Figure 9: General tab displays the hardware key


15/24

Note:As of SAP NetWeaver 04 (Support Package Stack 09) the

Enterprise Portal does not need a separate license key and is

either installed on Application Server ABAP or on Application

Server Java (including J2EE Engine standalone). If the license key

is installed on the ABAP stack, it should be requested using the

SAP NetWeaver Application Server ABAP instructions. If it is

installed on the J2EE Engine standalone, the key should be

requested using the SAP NetWeaver Application Server Java or

J2EE Engine 6.30 standalone section.

User Interface

SAP Enterprise Portal (EP) SAP NetWeaver

License keys and import license data should be managed using

the SAP NetWeaver Visual Administrator as the license UI of the

portal is read only. Use the following: System Administration

System Configuration Portal Licensing

SAP Enterprise Portal 6.0 SP2 and lower

(prior to SAP NetWeaver)

Note:The LicenseKey command line tool is no longer available

in EP 6.0.

License keys and import license data can be managed using the

License Key iView. Access the License Key iView under System

AdministrationSystem Configuration Portal Licensing. Three

users may log on to the portal simultaneously, but an additional

logon attempt automatically launches the License Key iView.

APPLICATIONS RUNNING SAP ENTERPRISE PORTAL(PRIOR TO SAP NetWeaver)


Install software in accordance with the attached instructions.

Generating A Temporary License Key

SAP Enterprise Portal SAP NetWeaver

Temporary license keys are automatically generated during the

SAP NetWeaver SAP Application Server and SAP Enterprise

Portal installations, respectively. These license keys are valid for

four weeks only. During this period of time, customers should

apply to SAP for permanent license keys as soon as possible.

Upon request, SAP issues a permanent license key, which must be

installed before the four-week temporary period is up. The portal

and Web AS license keys are independent of each other and are

installed separately. Temporary licenses can expire on different

dates according to when the products were installed.

Note:If a permanent license key is not installed for SAP Enterprise

Portal, only three users can log on simultaneously. If one is not

installed for SAP Web AS, the J2EE Engine stops after 30 minutes

(see Appendix).

Figure 11: License Key Iview

15


16/24


A temporary license key is automatically generated when launching

SAP Enterprise Portal 6.0 for the first time after installation. This

license key is valid for four weeks only. During this period of

time, customers should apply to SAP for permanent license keys

as soon as possible. The permanent license key must be installed

before the four-week trial period is up. If a valid license key is not

installed, only three users can log on to SAP Enterprise Portal

simultaneously. An additional logon attempt launches the

License Key iView.

See the Appendix for more information on licensing a clustered

portal environment.


Each system has a unique, encrypted hardware key to ensure itis the only one used per system. This hardware key needs to be

identified before requesting a license key from SAP.

16

Figure 12: Generating the hardware key


To identify the hardware key for SAP Enterprise Portal 6.0, use

the SAP Web AS Visual Administrator.

Alternatively: Log on to the portal with administrator creden-

tials and navigate to: System Administration System Configuration

Portal Licensingto view the hardware key.


To identify the hardware key for SAP Enterprise Portal 6.0, log on

to the portal as an administrator and select:

System Administration System Configuration Portal Licensing.



To install the permanent license key:1. Copy the license key file supplied by SAP to a directory

2. Start the Visual Administrator, then follow the path:

Services Licensing Adapter

3. Use the Install License From File button to upload the file

4. In the File Selection Popup browse to the location of the

license key file on client

5. Choose Open to continue

6. Restart the Portal Web server SAP Java Engine

SAP Enterprise Portal 6.0, SP 2

To install the permanent license key:

1. Copy the license key file supplied by SAP to a directory

2. Log on to the portal as an administrator and choose:

System Administration System Configuration Portal Licensing.

3. In the License File field browse to the location of the license

key file

4. Choose Install Permanent License

5. Restart the Portal Web server SAP Java Engine


17/24

SAP Enterprise Portal 5.0

Request license keys as described before. Use the graphical user

interface (GUI) or the command line interface to install the

license key as follows:

From Support Package (SP) 2 for SAP Enterprise Portal 5.0,

manage license keys and import license data using the license key

iView. Access this iView from System Configuration License.

If SAP Enterprise Portal is not licensed, this iView is displayed

automatically.

If SAP Enterprise Portal 5.0 without SP 2 is in operation, use the

command line interface.

DELETION OF SAP SYSTEMS

17

Figure 13: Installing the license key

For legal reasons related to the license agreement, all informa-

tion regarding deleted systems must be submitted online to SAP.

Systems may be deleted on the SAP Service Marketplace using

the Internet address service.sap.com/system-data . For more infor-

mation, see SAP Note 94998.

SAP Service Marketplace

Deleting an SAP System

Follow these steps to delete the system:

1. Enter the Internet address service.sap.com/system-data

2. Choose Start Application

3. Click on the installation number to expand the systems

4. Click on desired system ID

5. Choose Delete System

6. A window with system information appears

7. Choose Delete System

Deleting a Further License Key

Follow these steps to delete a further license key:

1. Enter the Internet address service.sap.com/system-data

2. Choose Start Application

3. Click on the installation number to expand the systems

4. Click on desired system ID

5. Choose the License Key tab page

6. Choose the Maintain License Key button on the right

7. Select the key to delete

8. Choose Delete Selected License Key


18/24

It may be necessary to move a system (See SAP Note 198140) to

a new installation number in the following cases:

The system was requested under the wrong installationnumber

The installation owner has changedA new installation number has been received from the contracts

department

System is to be reassigned to another installation numberwithin the same customer number

Note:With administration authorization for the new installa-

tion number, systems can be reassigned to another installation

number under a different customer number.

Self-service is available on the SAP Service Marketplace Website

for the reassignment process. Proceed as follows:1. Go to this Internet address:service.sap.com/system-data

2. Select Start Application

3. Select the old installation, and click on the requested system ID

4. Select Reassign System to the left of the Delete System button

5. Select an installation from the list, and click on Reassign

System

The list contains all the installations for which request license

key authorization is available. The e-mail address can also be

changed.

Note:Old license entries in the system must first be deleted so

that the new license key can be imported.

To obtain relevant authorization, open a customer message

under the XX-SER-SAPSMP-USR component. If the new

installation has not yet been created or requested, the contracts

department has to be contacted under XX-SER-GEN-CONTR.

18

Note:The hardware configuration and the software product of

the old and new installations must match. Otherwise only a

limited license key valid for two weeks will be received.

To reassign object and developer keys that have already been

registered, enter a message under the XX-SER-GEN-SSCR

component. In the message, include the system ID as well as the

old and new installation numbers.

To reassign a system to an installation number under another

customer number for which you dont have the request license

key authorization, enter a message under the XX-SER-LIKEY

component. The following information is required:

1. Old and new installation numbers

2. System ID

3. System number4. Hardware key

5. Contact person and e-mail address

6. State whether the reassignment of developer and object keys

is needed

Upon receipt of the message, the system is reassigned and

SAP generates a new license key. This is communicated to the

customer via e-mail. The license key can also be displayed on

the SAP Service Marketplace at:

service.sap.com/licensekeys mySAP Business Suite.

Note:In addition, SAP must reassign the developer and object

keys logged upon receipt of information stating whether they

are to be reassigned or not. If the customer number changed

when the installation number was changed, users and access to

customer messages must be adjusted as well (see Note 154743).

MOVING A SYSTEM TO A NEW INSTALLATION NUMBER


19/24

For more information, see SAP Service Marketplace at

service.sap.com/licensekeys and the SAP Notes assigned to the

XX-SER-LIKEY component. SAP Note 94998 provides a good

overview and lists most related notes.

For any further questions, create a message on the

SAP Service Marketplace XX-SER-LIKEY component.

19

ADDITIONAL INFORMATION SUPPORT


20/24

Further SAP Notes

94998 Requesting a License Key and Deleting an SAP System

538081 High Availability SAPLICENSE

870871 License Key Installation

432308 SAPLICENSE 6.10 New System Number Field

355536 Import an SAP License from a File

178409 Saplicense Problems with the Read From File

165306 64bit errors in saplicense

741886 Licensing Adapter not Displayed

853649 Message in EP6 SP2: Could not get the hardware key

848957 License Key: Unknown Return Code 11

836348 License Key for J2EE: This system number is

833434 License Key: Error Getting the Hardware Key

777681 License Key Enterprise Portal: Hardware Key not Readable

746402 Error when Installing the J2EE Engine License

607141 J2EE Engine License Key Request454473 SEM License Key

197623 Temporary License Key

131162 Installation Number is INITIAL

169293 System Data Maintenance

Validity of the License Key

License keys assigned to customers who buy or lease their SAP

systems are valid for an unlimited period of time. Those assigned

to SAP customers with demonstration or test systems are valid

for the period of time stated in their contracts.

The expiration date of a license is shown on the copyright screen

displayed when a customer logs on to an SAP system. It can also

be displayed on the System Status screen, by choosing System

Status SAP System Data(only valid for SAP Web Application

Server ABAP). If a limited license key was assigned, the license

key requested may have been granted for a limited period only.

There are several possible reasons for this, which can be checked

on the SAP Service Marketplace Website by displaying system

data. (see SAP Note 197623)

APPENDIX

20

Expiration of SAP Enterprise Portal SAP NetWeaver:

Permanent License Keys

If an SAP license key expires, a temporary license key can be

installed until a new permanent license key is requested and

installed. The temporary license key should be installed within

four weeks after the expiration of the permanent license. The

temporary key is valid for four weeks only and a permanent

license key must be applied for within that time period.

Maintaining the Permanent License Key in the J2EE Engine and

SAP Enterprise Portal If the license received from SAP is not time

limited, no maintenance is required. If a license with a predeter-

mined validity period has been applied for, its validity should be

followed up on and renewed when it expires. Its status can be

monitored as explained below.

To monitor and renew a license proceed as follows:

1. To monitor license validity status, go to the Visual

Administrator and select: Services

Monitoring.

2. From the Monitoring tree, in the main window, go to:

Root Kernel Licensing Manager License Validity Period

.

3. When the permanent license expires, a temporary license can

be installed until a new license arrives. The temporary license

can be used for four weeks.

4. Apply for a new license and install it, as instructed previously.

Unique System Number

Note:As of SAP Web AS 6.10, the license key features a unique

system number. Only one system number can now be assigned

to a system.

If a license key with a system number already exists, the newly

entered system number must be identical to it. Exceptions are for

old or new licenses with system number: INITIAL_SYSTEM_

IDX.


21/24

Old licenses that do not yet contain a system number can still be

installed. To do this, leave the field blank when entering the

system number (do not enter any blank characters). The system

number is then assigned the value: INITIAL_SYSTEM_IDX,

which means the old license is valid. All old licenses are upgraded

when the system is upgraded. At the same time, system numbers

are deleted and replaced with the value: INITIAL_SYSTEM_IDX.

To display a system number on the SAP Service Marketplace, go

to this Internet address: service.sap.com/licensekeys , and the initial

page for requesting license keys will be presented. To reach the

system overview, select Request license key to show the installa-

tion number and system number.

License Type

Note:To obtain a license key for SAP NetWeaver EP6 SP3 SP8,a license key with software product NetWeaver, license type

PORTAL, as well as a license key with license type J2EE should be

requested.

Choose one or more of the following license types to request a

license key:

Standard

For all systems installed on the SAP Web Application Server with

ABAP. Also aplies to SAP J2EE engine add-in installations.

If you have installed SAP NetWeaver Enterprise Portal SP9 or

higher on the ABAP stack

J2EE

For SAP J2EE engine standalone systems.As of EP6 SP9, if the Enterprise Portal has been installed on the

J2EE Engine standalone

Portal

For SAP Enterprise Portal 6.0 systems with Support Package 8or lower and Enterprise Portal 5.0.

21

High-Availability Clustered Environment

SAP NetWeaver (AS)

The license key in an SAP system is tied to the message server

computer. If the message server is moved to another computer,

a license key should also be imported to the new computer. If the

current message server breaks down in a high-availability environ-

ment, switching is carried out automatically. To that end, a license

key must be imported beforehand for the old computer to conduct

the switch seamlessly to the new one.

SAP NetWeaver Portal

In the SAP Web AS cluster, the server configured as message

server is the synchronizer of the rest of the cluster nodes. The

license key installed for the message server is valid for all machines

in the cluster. License validity is checked every 24 hours.

The cluster nodes can work up to one full day even if the machine

holding the license (the message server) is off. To ensure a valid

license presence at all times, it is recommended that an additional

license be requested and installed on more than one machine in

the cluster environment. The machines that take over in case of

message server failure are designated as failover message servers.

Therefore, a permanent license key for all message servers in a

system should be installed.


In a clustered environment, awareness of the following is needed:

One license on any of the machines is sufficient for the entirecluster.

Since the license is cached for one hour, it is possible to stopand restart the portal server on which the license was installed

for one hour only.

SAP recommends installing a license on several portal servers thus ensuring the availability of one licensed machine working

at all times.

The permanent key can be uploaded from any portal server.


22/24

Since the license key is valid for one machine only, make surethe machine(s) chosen to license are used in a productive

environment.

SAP does not recommend calling up the License Key iViewusing the Load Balancer it should be called up directly on the

machine where the key is to be installed, instead.

When installing a clustered environment, the temporarylicense should be installed on the first portal server only.

It is important to get permanent license keys as soon aspossible.

SAP Strategic Enterprise Management

SAP Strategic Enterprise Management (SAP SEM) is a business

warehouse system into which strategic enterprise management

functionality was installed as an add-on. Thus, the system provides

all BW functions as well as all SEM functions.

To use the SAPR/3-based consolidation component SEM-BCS,

SAP R/3 Release 4.6C or 4.7 is additionally required. For this pur-

pose, an already existing SAP R/3 system can be used or an

SAP R/3 system, which is contained in the SEM delivery, can be

installed. The SAP R/3-based consolidation component SEM-BCS

is a functional enhancement of the SAP R/3 consolidation compo-

nent EC-CS. The procedure for the release of the functional

enhancements is described in SAP Note 525335 (for an existing

SAP R/3 system) and SAP Note 458659 (for a separate SAP R/3

system).

Provided installation is followed as described in SAP Note 458659

and a separate SAP R/3 system is used exclusively for the SAP

R/3-based SEM-BCS consolidation component, it can be operated

productively under the SEM installation. Therefore, license keys

under the SEM installation need to be ordered for the SEM

system as well as for the SAP R/3 consolidation system. If the SAP

R/3-based SEM-BCS is to operate on an existing SAP R/3 system

according to SAP-Note 523335, the installation number of the

SAP R/3 system remains unchanged. No other R/3 System or BW

System should be used under the SEM installation, as these must

be operated under a different installation with the correct

software product. Request a new installation from your SAP

Contracts Department and order a license key for the new

installation.

System Types

Production System (Production)A system containing actual company business processes, and

where users enter their live production data

Development System (Develop)A system used for customer developments and customizing

settings

Test System (Test)The environment used by the project team to prototype and

test system settings and processes

Training System (Train)A system used to teach and practice system settings and

processes

International Demonstration and Education System(IDES)

An exclusive SAP system containing several sample companies

that typify relevant business processes

Demonstration System (DEMO)

A system used exclusively for giving demonstrations to

prospects and for training employees

Back-up System (BACKUP)An independent back-up system for a live system

22


23/24

Command Line Interfaces

Note:Using the saplicense or LicenseKey GUI instead of the

command line interface is strongly recommended as it is easier to

use, performs additional checks, and avoids most handling

errors.

SAP Web AS ABAP

The ABAP saplicense program supports the following para-

meters:

Test whether a valid SAP license exists testDelete an installed license deleteDisplay all installed licenses showCreate a temporary license tempOutput the customer key (hardware key) needed to request a

permanent license key get

Install licenses from a file install [ifile=]Display the tool version versionDisplay help text help

Note:The parameters are listed as they are used for UNIX and

NT. For iSeries, they have to be enclosed in quotation marks:

for example, -install instead of -install.

Log on as user adm (Unix and NT) or ofr (iSeries)

to the computer with the SAP system message server. This is

usually the PC on which the central SAP entity is running.

For detailed descriptions and more information, please read SAP

Online Help: BC-Basis Components Kernel Components BC

SAP License

As of Basis release 4.5A, license data can be entered manually

(saplicense install) or a file that contains all the data (saplicense

install ifile ) can be used. This file can be created

when the license key is displayed on the SAP Service Marketplace.

It is also attached to the e-mail notification that is sent if this

option is chosen when requesting a license key.

After Expiration of a J2EE Engine License Key

The procedure varies depending on the type of license key. After

expiration of a temporary license key, a permanent license key

has to be obtained from SAP.

When a permanent license key expires, however, a temporary

license key can be installed again. This is valid for 28 days giving

enough time to get a new permanent license key from SAP. To

install a temporary license key, go to the licensing service, choose

the General tab and click on Install Subsequent Temporary

License. After that, restart the SAP J2EE Engine.

23


24/24

www.sap.com/contactsap

LicenseKeys_SAPSystems.pdf

Documents

Transcript of LicenseKeys_SAPSystems.pdf