Obtain a license key through the License Key application on Support Portal. Please find detailed step by step guides on the License key starting page ‘How to request license keys'.
To request an additional license key use the License Key application. Select the requested installation number and System ID, click Edit, click Continue, click the + icon. If you need to enter a new hardware key this can be found in the SLICENSE transaction in the system.
For SAP Business Suite products, you require a new key for each machine you install the product on because the license key is tied to your hardware key (new hardware requires a new license key). Please request a new license key using the License Key application.
For SAP Business Suite products the license key is tailored to your hardware configuration. If your hardware changes, you require a new license key. Please request a new license key using the License Key application.
You require a different key for each type of system. Please request a new license key using the License Key application. Additionally, if you wish to change a system type (e.g. from test to production), please do so via the System Data application. Instructions for editing your system can be found below, under the question ‘How do I edit details for a particular system'?
SAP Business Suite products can be used for 90 days without a license key. This allows you to start using the product as soon as you signed your contract. However, after 90 days you have to install a permanent license key.
Either click on the Install Temporary License button in Transaction SLICENSE, or enter saplicense -temp or saplikey -temp in your operating system command line. The license key will be valid for 2 or 4 weeks, depending on your release (as of release 6.40, the key is valid for 2 weeks). You can find more information in the Prerequisites section of SAP Note 870871 (creating a temporary license key). You can also request a permanent license key.
Whether your license key is valid or expired, you can always log into your system with the username SAP*. However, we strongly recommend that you request a permanent license key before your temporary key expires.
You need an SAP Solution Manager installation number. Please contact us if no SAP Solution Manager installation number is available.
Data stored in secure storage is encrypted with a key that includes the installation number and system ID. If one of these numbers changes, the data in secure storage must be migrated. For more information migrating secure storage data, see SAP Note 816861.
The maintenance certificate enables SAP's software logistics tools to identify your system and the scope of your corresponding SAP maintenance agreement.
To delete a license key and / or a maintenance certificate use the license key application on Support Portal. Select the requested installation number and System ID, click Edit, click Continue, select the requested entry and click the dustbin icon.
ABAP license keys can be installed entering the transaction SLICENSE in the GUI (Graphical User Interface). You should choose the SAP License Administration mode for your 24 digit key or click the New License button for installing your digital signed license key. Detailed information can be found in SAP Note 870871.
J2EE Engine stand alone or Enterprise Portal EP6 SP3 - SP8 license keys should be installed using the Visual Administrator/SAP NetWeaver Administrator. License keys with SWPRODUCTNAME NetWeaver in the license key file are not valid in the Visual Administrator/SAP NetWeaver Administrator.
Enterprise Portal 6.0 SP3 or smaller and EP 5.0 license keys can be installed using the Portal License Key iView.
You can create an installation number using the self-service. Use the option ‘Request Installation' under ‘Installation Data Maintenance'. It is required to have the authorization for managing installations. To receive this authorization contact the SAP user administrator in your company. If you have questions get in touch with your local contract department via online form. Each installation number also has an associated installation name, which you can edit. Typically, the default name of an installation corresponds to the name of the product you purchased.
A system represents the machine on which you install the software you purchased. A system consists of a System ID (SID), which is a 3 character alpha-numeric ID of your choice. A system also has other attributes that you fill in, such as the operating system you are running on, the name and version of the SAP product you install, the database that the SAP product on the system uses and whether it is a Production, Test or Development system. In the license key application you either pick an existing system if you want to add additional keys to that machine or you create a new system – by clicking the + icon.
Each installation number can have one or more systems (computers on which you install the product) associated to it. Each of those systems will likely require license keys for the SAP product you installed on it. Please note that some products do not require a license key. You can create a system for those products here.
We strongly recommend to keep your system data up-to-date (i.e. a true reflection of the machine on which you have installed the SAP product you purchased). This helps us faster resolve messages you open, because we know what OS, product and version you have installed.
Under System Data Administration pick your installation from the drop down boxes, click Search, click System ID (3 characters ID) for the system you wish to edit, click the Edit System button.
Upon installation a new HANA DB will automatically get a temporary license valid for 90 days. Permanent license keys can be installed using HANA Studio or HANA Cockpit as you want. You can also install license keys using command line with the hdbsql tool.
No, HANA Cockpit itself does not require a license key
Cockpit is always an optional component if you don’t want to use it. You can also install license keys using command line with the hdbsql tool.
Cockpit is independent of HANA DB and can be installed separately.
This is optional. Upon installation, the whole HANA DB (systemDB & all tenant DBs) can consume a temporary license key with 90 days validity. Permanent license keys are required after this period and can be installed on individual tenants for local utilization or on SystemDB for global utilization.
It depends on his licensing model and his multitenant database container (MDC) setup. Tenants can have different utilization, e.g. BW, Non-BW, and thus can have different licensing models/license keys.
For one HANA DB, all license keys must share the same data: SID, Hardware Key, Installation number, & System number. Only the memory amount can differ.
Yes, a license key is always needed. How it is installed is irrelevant (can be done via studio, cockpit, command line).
No. A new system will differ from the source system (SID, Hardware Key), thus the new tenant will find that the license from the source system (via the Backup) is not applicable as soon as it starts the first time after cloning. If the license in the backup is a permanent license and is still valid, the new tenant will get a temporary license key valid for 90 days and need a new permanent license key. If the license in the backup is a temporary license key or an expired license, this license will be deleted from the new tenant and it is immediately in lock down. Please see KBA 2832368.
Yes. There is some technical limitation though regarding the maximum number of tenants that can be created in our HANA DB (due to number of ports available).
Some reasons why you may be unable to request a license key:
Fix: Before you can request a license key for the specific product and version, make sure your order has been processed by the relevant order entry team. Also ensure you have an SAP BusinessObjects installation number which is provided by SAP when you sign your contract. To check the status of your contract, contact your local contract department or your Sales Account Manager. If you are not sure who your Sales Account Manager is, please contact the Customer Interaction Center who can verify this information for you. See SAP Note 1251889 for more details.
Fix: Check to see if someone in your company has already requested keys for this exact product and version. Click on tab Display License Key Requests > My License Key Requests or My Company's License Key Requests.
Tip: Clicking the SID will launch a comprehensive overview of the system, and you can find its license key under the License Key section.
Fix: Return to Step 3 and Step 4 of the License Key request process, and make sure you picked the correct product and version. Please note that the majority of SAP BusinessObjects license keys are platform independent. This means, that you can install them on any operating system.
Some reasons why you may be unable to install the license key on your system:
Fix: Check the product documentation for any pre-requisite requirements.
Fix: Make sure temporary keys are removed before you install any permanent keys. Permanent and temporary keys should never be mixed on the same system.
Obtain a license key through the License Key application. You will then need to pick the relevant installation (in step 1), and create a new system (in step 2). For an SAP BusinessObjects product, you can use a temporary key (valid for 90 days) while we set up permissions for you to request a permanent license key. The temporary key allows you to use your product right away. Once permissions have been set up, you can obtain a permanent license key.
In Step 2 of the license key application, select the system for which you want an additional key. Click on the Edit button. Click on the Continue button without changing the system details. In Step 3, click on the + icon to add a license key request. Select the product & version and type in the quantity. Click on Add and then Generate button.
Yes, for SAP BusinessObjects products you should request a new key for a new system (machine). Please request a new license key using the License Key application.
Please contact your account manager to check whether you need a new key for the new user. If you are not sure who your account manager is, please contact the Customer Interaction Center who can verify this information for you.
No, you require a different key for each type of system. Please request a new license key using the License Key application. Additionally, if you wish to change a system type, please do so via the System Data application.
SAP BusinessObjects products require a license key for activation. There are emergency temporary keys available which can be used to deploy the software until you obtain the license keys for your license contract with SAP. These emergency keys will expire on the date indicated in the file so the keys specific to your license contract should be requested and installed before that date.
An Installation number is a unique 10-digit number, created by your local SAP Order Management. An installation number can be requested by the Installation Request Form on the contracts department page. Each installation number also has an associated installation name which you can edit. Typically, the default name of an installation corresponds to the name of the product you purchased. In step 1 of the license key application, you must pick the installation that corresponds to the product you want a license key for.
A system represents the machine on which you install the software you purchased. A system consists of a System ID (SID), which is a 3 character alpha-numeric ID of your choice. A system also has other attributes that you fill in, such as the operating system you are running on it, the name and version of the SAP product you install on it and whether it is a Production, Test or Development system. In Step 2 of the license key application, you can create a new system by clicking the + icon. Or in Step 3 of the license key application , you can edit an existing system if you want to add additional keys.
Each installation number can have one or more systems (computers on which you install the product) associated to it. Each of those systems (computers) will likely require license keys for the SAP product you installed on it. Please note that some products do not require a license key. You can create a system for those products in the same way as products that do require a key. You will receive a message that a key is not required but you can continue to have a system created.
We strongly recommend you keep your system data up-to-date (i.e. a true reflection of the SAP product that you have installed). This helps us faster resolve messages you open, because we know what OS, product and version you have installed.
Under System Data Administration, pick your installation from the drop down boxes > click Search > click on the System ID (3 characters ID) for the system you wish to edit > click the Edit System button at the top-left of the page.
Under System Data Administration, pick your installation from the drop down boxes > click Search > click on the System ID (3 characters ID) for the system you wish to delete > click the Delete System button at the bottom-left of the page.
A bundle is a license in your contract that is made up of multiple products. A bundle may also be referred to as a "package", e.g., BI Package, or a "pack", e.g., Financial Perf. Mgmt. pack.
A component license material is a product found within a bundle.
A license material is the name assigned to a specific license. It could be the name of a "bundle" (see above) or an individual product.
Example: BA&T SAP BusinessObjects BI Suite is a bundle license. It contains several component license materials for which you can request a key:
Sybase Software Asset Management (SySAM) enables you to better track your software license assets from Sybase. SySAM enables you to see how many licenses for a given product you have purchased, how many licenses have been deployed and how many licenses are still available. Asset reporting utilities are included in your product distribution to provide you with further insight into your deployment and utilization of Sybase software.
Before you begin:
A license model refers to how you set up your license files to be accessed by your licensed program(s). License files can reside on a central, networked license server in a Served License model or can reside on the machine that is running the licensed program in an Un-served License model. Before you generate your license file, you should decide which model works best for you. Please refer to the SySAM2 Users Guide for more detail on license models.
Host IDs are unique identifiers for a particular machine or sub-capacity environment.
If you intend to run your Sybase product in a sub-capacity environment, you must use the sysamcap utility to derive the host ID for the virtual machine, partition, or resource-set. See the SySAM Users Guide for more information.
If you do not intend to run your Sybase product in a sub-capacity environment, you must enter your physical machine's Host ID. To find your host ID, you can run the lmhostid utility included in the lmutil administration tool or use the appropriate operating system command. lmutil is included in your product distribution, or can be downloaded from SAP Software Download page, Installation and Upgrades, A-Z Index, Click "S" and look for SYSAM.
To run lmhostid utility use the command:
> lmutil lmhostid.
The type of host ID returned by lmhostid utility will depend on the platform. The following table lists the host ID types used for each platform along with the native OS command that can be used to obtain the host ID value:
|Platform||Host ID Type||Native OS Command|
|Windows(*1)||Ethernet Address||ipconfig /all (use "Physical Address" value)|
|Linux||Ethernet Address||/sbin/ifconfig eth0 (use "HWaddr" value)|
|Mac OS X||Ethernet Address||/sbin/ifconfig eth0 (use "ether" value)|
|Tru-UNIX (Digital)||Ethernet Address||netstat -i|
|IBM AIX||32-bit Hostid||uname -m (returns 000276513100), then remove both the first and the last two digits, and use the remaining eight digits|
|SGI||32-bit Hostid||/etc/sysinfo -s (convert to hex, or prefix #)|
|HP-UX PA-RISC||32-bit Hostid||uname -i (convert to hex, or prepend with #)|
|HP-UX Itanium||Machine ID||getconf CS_PARTITION_IDENT (prefix with "ID_STRING=")|
(*1) For Windows platforms, if your machine does not have a network adapter, an alternate Hostid of type Disk Serial Number is supported. To get this host id, use the "lmutil lmhostid -vsn" command or get the disk's volume serial number by executing "DIR C:", remove "-" from the value and prefix "DISK_SERIAL_NUM=" to the serial number to get the host id.
Each host ID type has valid formats that will be checked when generating a license. Make sure the value entered matches these valid formats.
Ethernet addresses are 12 character hex values consisting of digits 0 thru 9 and characters A thru F. They may be entered in any of the following formats:
Host Ids are 8 character hex values consisting of digits 0 thru 9 and characters A thru F. They may be entered in the following formats:
Note: For some platforms, Host Ids can also be entered in decimal formats, in this case prefix the host id with a "#" sign. Example: #1039716963
Disk Serial Number is always entered with a "DISK_SERIAL_NUM=" prefix. For example: DISK_SERIAL_NUM=3e2e17fd
Machine ID string is always entered with an "ID_STRING=" prefix. For example: ID_STRING=9c766319-db72-d411-af62-0060b05e4c05
Sybase Sub-capacity allows you to license only the virtual machine, soft partition or resource set that your SySAM Sub-capacity enabled product is using. The SySAM Sub-capacity feature allows you to configure SySAM to recognize CPUs at the appropriate containment level using the sysamcap utility which is included with your SySAM Sub-capacity-enabled product. SySAM 2.2 is required for sub-capacity support. Refer to the SySAM Users Guide for more information.
Please see your Sybase product Configuration Guide and / or the SySAM Users Guide included in your product distribution for more information.
The SySAM Documentation explains the concepts, terminology, and capabilities available to you, including license file basics, license file model options, license administration options and tools, and more.
The number of licenses to be specified depends on how many licensed units are needed for the application running on this machine. For entitlements licensed under CPU license types, the quantity should correspond to the number of processors, i.e. cores, on the machine, partition or resource-set. For entitlements licensed under Seat / Connection models, the number should correspond to the expected seats / connections used by this machine. The license is generated for the quantity specified and the available license quantity is reduced accordingly.
The terms of a Secondary Copy Pool or Site License pricing arrangement may permit you to deploy Sybase Programs in excess of the quantity displayed on this SAP Support Portal website. The functions of SAP Support Portal are not intended to enforce limitations or restrictions on quantity or use and shall in no event modify or amend the terms and conditions of your License Agreement which constitutes the sole and complete agreement with respect to the licensing and use of Programs.
Please also note that the expiration date displayed may not match your actual Copy Pool or Site License expiration date. This is required to enable you to create license files that reflect your actual deployments of previous versions of your licensed Programs - even if your Copy Pool or Site License has actually expired. As per the preceding paragraph, this does not modify or amend the terms and conditions of your License Agreement. If the term of your Pool or Site has expired, you are restricted to the quantity of your existing Program deployments and are only entitled to Update those deployments in accordance with your current Support Plan.
Served Licenses are measured as the number of licenses used simultaneously. You should determine the quantity of licenses based on how many instances of the program will be in use during peak usage periods. For more information, please refer to your license agreement.
Some Sybase products allow users to install more instances of the product than the licensed (purchased) quantity specifies. These additional product licenses are known as Alternative Use Licenses.
Alternative Use Licenses are subject to usage limitations as defined in the Product Specific License Terms (PSLTs). The license terms for Alternative Use Licenses can vary from product to product. View the license terms for a specific product.
For your convenience, the License Check In / Re-host feature permits certain licenses to be returned to your License Pool for later redeployment to another Machine. If you elect to activate the Check In / Re-host feature, you must immediately discontinue Use of the Checked In license Program(s). Subsequent re-deployment may be subject to Transfer Fees and/or Upgrade Fees as set forth in your License Agreement. Use of this feature will not affect your existing obligations with respect to Support. To remain compliant with the terms of your License Agreement, at the time of Program re-deployment you must contact SAP, an SAP subsidiary or authorized reseller and pay all applicable Transfer, Upgrade and Support Fees.
Over time a License might need to be upgraded. This can be due to:
In order to upgrade your License, click the upgrade button and a new License will be generated. You will need to save this new License to a License File and install this on the machine that will run the newest version of the Product.
The License Server listens on 2 TCP/IP ports for incoming license requests, so firewall and VPN policies must be set up to accommodate both. For such use the ports will need to be fixed and must be specified as "License Server Port 1" and "License Server Port 2" when generating served licenses. If using a three-server-redundancy license server configuration "License Port 1" must be specified. If "License Server Port 2" is also specified then the value entered for the primary license server will be used for the secondary and tertiary license servers.
Note: Any unused port number between 0 and 64000 is valid. On UNIX, choose a port number greater than 1024 as most port numbers less than 1024 are privileged port numbers. Do not specify a number in the range 27000 to 27009 for "License Server Port 2", as ports in this range are used by the lmgrd** process when no port is specified for "License Server Port 1".
**The License Server consists of 2 processes: the license manager daemon (lmgrd) and the Vendor daemon (SYBASE). "License Server Port 1" is the TCP/IP port that will be used by the lmgrd process, and "License Server Port 2" is the TCP/IP port that will be used by the SYBASE process.
When you purchase production use licenses of some products, Development & Test and/or Standby licenses may be included. If these licenses are included, you may deploy any number of license keys, but each license key is limited to the quantity of your purchased production use license. You may deploy these licenses to meet your needs for development, testing or standby purposes only (subject to the terms and conditions of your software license agreement).
SAP Business Warehouse Accelerator:
SAP NetWeaver Identity management:
SAP Application Visualization by iRise:
SAP POS - Transaction GM:
SAP EH&S , Windows Wordprocessor Integration (WWI):
SAP Central Process Scheduling:
SAP Extended Diagnostics by CA Wily:
Enterprise Services Repository:
RWD Infopak / ANCILE Solutions: