Install Sap License From Os

Copyright © 2016 SUSE LLC and contributors. All rights reserved.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “ GNU Free Documentation License”. For SUSE trademarks, see Trademark and Service Mark list. Linux* is a registered trademark of Linus Torvalds. All other third party trademarks are the property of their respective owners. A trademark symbol (®, ™ etc.) denotes a SUSE trademark; an asterisk (*) denotes a third party trademark.

All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, the authors, nor the translators shall be held liable for possible errors or the consequences thereof. An overview of SUSE Linux Enterprise Server for SAP Applications. Information on hardware requirements, the installation workflow, partitioning, and other installation planning aspects. Installing the SUSE Linux Enterprise Server operating system that forms the basis of SUSE Linux Enterprise Server for SAP Applications.

May 11, 2012. Install the license through OS level. The database interface library is linked dynamically as of Release 4.5A. For saplicense to find this library, the following variables must be set in the environment of the user calling saplicense: dbms_type = (for example, ora, inf. You will now install the system in this Linux OS. Note: Since the course was released, it seems like the Sybase ASE Database license has expired. This is the installation script to start the installation of the SAP NetWeaver system.

Installing SAP applications on SUSE Linux Enterprise Server for SAP Applications, either directly after the installation of the operating system or in a running system. Setting up a server for all Installation Media used within your organization. Description of tools to configure SUSE Linux Enterprise Server for SAP Applications. Bugs and Enhancement Requests For services and support options available for your product, refer to. To report bugs for a product component, go to, log in, and select Submit New SR.

User Comments We want to hear your comments about and suggestions for this manual and the other documentation included with this product. Use the User Comments feature at the bottom of each page in the online documentation or go to and enter your comments there. Mail For feedback on the documentation of this product, you can also send a mail to doc-team@suse.de. Make sure to include the document title, the product version and the publication date of the documentation. To report errors or suggest enhancements, provide a concise description of the problem and refer to the respective section number and page (or URL). • /etc/passwd: directory names and file names • placeholder: replace placeholder with the actual value • PATH: the environment variable PATH • ls, --help: commands, options, and parameters • user: users or groups • Alt, Alt – F1: a key to press or a key combination; keys are shown in uppercase as on a keyboard • File, File › Save As: menu items, buttons • amd64, em64t, ipf This paragraph is only relevant for the architectures amd64, em64t, and ipf.

The arrows mark the beginning and the end of the text block. System z, ipseries This paragraph is only relevant for the architectures System z and ipseries. The arrows mark the beginning and the end of the text block.

• Dancing Penguins (Chapter Penguins, ↑Another Manual): This is a reference to a chapter in another manual. 1.1.3.1 SAPHana Resource Agent This resource agent from SUSE supports scale-up scenarios by checking the SAP HANA database instances for whether a takeover needs to happen. Unlike with the pure SAP solution, takeovers can be automated.

It is configured as a master/slave resource: The master assumes responsibility for the SAP HANA databases running in primary mode, whereas the slave is responsible for instances that are operated in synchronous (secondary) status. In case of a takeover, the secondary (slave resource instance) can automatically be promoted to become the new primary (master resource instance). This resource agent supports system replication for the following in scale-up scenarios. • Performance-Optimized Scenario. Two systems (A and B) in the same SUSE Linux Enterprise High Availability Extension cluster, one primary (A) and one secondary (B).

The primary system (A) is replicated synchronously to the secondary system (B). • Cost-Optimized Scenario. The basic setup of A and B is the same as in the Performance-Optimized Scenario.

However, the secondary system (B) is also used for non-productive purposes, such as for a development or QA database. The production database is only kept on permanent memory, such as a hard disk. If a takeover needs to occur, the non-productive system will is stopped before the takeover is processed. The system resources for the productive database are then increased as quickly as possible via an SAP hook call-out script. • Chain/Multi-Tier Scenario. Three systems (A, B, and C), of which two are located in the same SUSE Linux Enterprise High Availability Extension cluster (A and B). The third system (C) is located externally.

The primary system (A) is replicated synchronously to the secondary system (B). Ge Centricity Pacs Manual Treadmill. The secondary system (B) is replicated asynchronously to the external system (C). If a takeover from A to B occurs, the connection between B and C remains untouched. However, B is not allowed to be the source for two systems (A and C), as this would be a “ star” topology which is not supported with current SAP HANA versions (such as SPS11).

Using SAP HANA commands, you can then manually decide what to do. 1.1.6 Antivirus Protection with ClamSAP ClamSAP integrates the ClamAV antivirus toolkit into SAP NetWeaver and SAP Mobile Platform applications to enable cross-platform threat detection.

For example, you can use ClamSAP to allow an SAP application to scan for malicious uploads in HTTP uploads. ClamSAP can be installed from the package clamsap. To use virus scanning within SAP NetWeaver, you need to enable it there ( Transaction › VSCAN). ClamSAP is a shared library that links between ClamAV and the SAP NetWeaver Virus Scan Interface (NW-VSI) by SAP. The version of ClamSAP shipped with SUSE Linux Enterprise Server for SAP Applications 12 SP1 supports NW-VSI version 2.0. Important: Packages May Be Missing from Patterns The selection of packages of the software patterns are defined as a specific release (Service Pack or major version) of SUSE Linux Enterprise Server for SAP Applications is developed. This package selection is stable over the lifetime of this particular release.

When working with SAP applications that have been released more recently than your SUSE Linux Enterprise Server for SAP Applications version, dependencies may be missing from the patterns. For definitive information about the dependencies of your SAP application, consult the documentation provided to you by SAP. Extended Service Pack Overlap Support SUSE Linux Enterprise Server for SAP Applications includes Extended Service Pack Overlap Support which extends the overlap between the support periods of two consecutive service packs by one year. Within this period, you remain under full support and receive all relevant maintenance updates. As a standard offering, this is unique. Extended Service Pack Overlap Support allows you to perform service pack migrations within 18 months instead of only 6 months.

Migrations can be scheduled more easily and testing before a migration can be performed under lesser time constraints. Additional Update Channel. • Allows SAP-specific patches • Updates for SAP-specific packages SUSE Linux Enterprise Server Priority Support for SAP Applications Subscriptions for SUSE Linux Enterprise Server for SAP Applications include SUSE Linux Enterprise Server Priority Support for SAP Applications which offers technical support for SUSE Linux Enterprise Server for SAP Applications directly from SAP. The joint support infrastructure, used by support engineers from SUSE Technical Support and SAP, is based upon SAP Solution Manager and offers a seamless communication with both SAP and SUSE. This “ One Face to the Customer” support model reduces complexity and lowers the total cost of ownership.

• SAP NetWeaver. At least 80 GB of hard disk space are necessary. • SAP HANA. At least 60 GB of hard disk space are necessary.

Partitioning for the SAP system is controlled by the files from the directory /usr/share/YaST2/include/sap-installation-wizard/. Usually, base_partitioning.xml will be used. When installing SAP HANA on certified hardware, other files will be chosen, as defined in /etc/sap-installation-wizard.xml. Here, the content of the element partitioning is decisive.

If the installation is, for example, based on HA or a distributed database, no partitioning is needed. In this case, partitioning is set to NO, the file base_partitioning.xml is used. The files that control partitioning are AutoYaST control files that contain a partitioning section only. However, these files allow using several extensions to the AutoYaST format. • If the partitioning_defined tag is set to true, the partitioning will be performed without any user interaction. By default, this is only used when creating SAP HANA file systems on systems certified for SAP HANA (such as from Dell, Fujitsu, HP, IBM, or Lenovo). • For every partition, you can specify the size_min tag.

The size value can be given as a string in the format of RAM* N. This way you can specify how large the partition should minimally be ( N times the size of the available memory ( RAM)).

The steps below illustrates how to create a partitioning setup for TREX. However, creating a partitioning setup for other applications works analogously. • In /usr/share/YaST2/include/sap-installation-wizard/, create a new XML file.

Name it TREX_partitioning.xml, for example. • Copy the content of base_partitioning.xml to your new file and adapt the new file to your needs. • Finally, adapt /etc/sap-installation-wizard.xml to include your custom file. In the partitioning for TREX, insert the following line. 3.1 Using the Installation Workflow The installation workflow is a guided installation of the operating system with optimized settings for SAP applications.

During the installation workflow, you can choose whether you want to install an SAP application. If so, you will be asked to provide SAP installation media when the SUSE Linux Enterprise Server installation is finished. You can also choose whether to install third-party extensions. For more information, see.

This section will guide you through the installation of the SUSE Linux Enterprise Server for SAP Applications operating system. Figure 3.2: Language, Keyboard and License Agreement • Select a fitting keyboard layout Keyboard Layout. To test whether the selected layout matches your physical keyboard, use the text box Keyboard Test. • Read the license agreement.

If you agree, select I Agree to the License Terms. Proceed with Next. Otherwise, cancel the installation with Abort › Abort Installation.

• If automatic network configuration via DHCP fails, the screen Network Settings will open automatically. If instead the screen Registration appears, your network connection works.

To change network settings anyway, click Network Configuration. When you are finished configuring networking, proceed with Next. Important: Configure Networking as Recommended by SAP Make sure to configure the network connection as recommended in the documentation provided to you by SAP. For details regarding network configuration, see Administration Guide, Chapter 19 “ Basic Networking”, Section 19.4 “ Configuring a Network Connection with YaST” (). • On the screen Registration, enter your E-Mail Address and Registration Code. Successful registration is a prerequisite for receiving product updates and being entitled to technical support.

Proceed with Next. Note: Release Notes From this point on, the Release Notes can be viewed from any screen during the installation process by selecting Release Notes. • When asked whether to enable update repositories, choose Yes. • On the screen, Extension and Module Selection, you can optionally choose additional SLE extensions and modules. The list contains free modules, such as the SUSE Linux Enterprise SDK and extensions requiring a registration key that is liable for costs. Proceed with Next.

• The following screen allows you to choose the Product Installation Mode. You can now choose between. Edit Proposal Settings Allows you to change the options for the proposed settings, but not the suggested partition layout itself. Marshall Amp Serial Number Lookup. Create Partition Setup Select a disk to which to apply the proposal.

Expert Partitioner Open the Expert Partitioner described in Deployment Guide, Chapter 14 “ Advanced Disk Setup”, Section 14.1 “ Using the YaST Partitioner” (). For partitioning advice specific to SUSE Linux Enterprise Server for SAP Applications, see. To accept the proposed setup without changes, proceed with Next. Figure 3.5: Suggested Partitioning • Select the clock and time zone to use in your system. To manually adjust the time or to configure an NTP server for time synchronization, choose Other Settings. For detailed information, see Deployment Guide, Chapter 6 “ Installation with YaST”, Section 6.10 “ Clock and Time Zone” (). Proceed with Next.

• Type a password for the system administrator account (called root) and repeat the password under Confirm Password. You can use the text box Test Keyboard Layout to make sure that all special characters appear correctly. For more information, see Deployment Guide, Chapter 6 “ Installation with YaST”, Section 6.12 “ Password for the System Administrator root” (). Proceed with Next. Important: Do Not Forget the root Password The user root has the permission to carry out all administrative tasks. Without this password, you cannot log in to the system as root.

After you have entered the root password here, it cannot be retrieved again. • On the screen Installation Settings, you can review and, if necessary, change several proposed installation settings. Each setting is shown alongside its current configuration. To change parts of the configuration, click the headline or other underlined items. Tip: Pattern “ High Availability” Is Necessary for High-Availability Installations Only If you are not planning to install a highly available SAP product, you can deselect the pattern “ High Availability” from the installation.

This saves space on the hard disk and download bandwidth for updates. Note that this pattern is distinct from the product SUSE Linux Enterprise High Availability Extension which you should not try to remove. To remove the pattern, click Software and then deselect Primary Functions › High Availability. Return to the overview with OK. Tip: Remote Location Specification To install from an NFS source, enter the name of the server and the complete path to the media data. For more information about setting up a remote installation server, see.

If you have installed from an installation server before or set up your system to be an installation server, you can also directly choose that server as the provider of the Installation Master. To do so, use the drop-down box below Choose an installation master. • Under Advanced Options, choose from among the following options. Collect installation profiles but do not execute installation Use this option if you only want to set the installation parameters, but not perform the actual installation. If you choose this option, the installation will continue as it would without this option but the SAP Installer (SAPinst) will stop earlier.

However, the following steps fully apply. For more information, see. Link to the installation master without copying its content to local location (SAP NetWeaver only) Use this option to avoid copying an Installation Master from one local location to another. This option is only active when the drop-down box above is set to dir://. Serve all installation media (including master) to local network via NFS Set up this system as an installation server for other SUSE Linux Enterprise Server for SAP Applications systems. The media copied to this installation server will be offered through NFS and can be discovered via Service Location Protocol (SLP).

Proceed with Next. The SAP Installation Wizard will now copy the Installation Master to your local hard disk. Depending on the type of Installation Master you selected, the installation will continue differently. SAP Standard System Install an SAP application including its database onto this system. SAP Standalone Engines Engines that add functionality to a standard product. Distributed System An SAP application that is separated onto multiple servers.

SAP High-Availability System Installation of SAP NetWeaver in a high-availability setup. System Rename Allows changing the various system properties such as the SAP system ID, database ID, instance number or host name. This is useful, for example, when you want to install the same product in a very similar configuration on different systems. Copy a medium Provide a path to additional Installation Media. For more information on how to enter the path, see.

When providing a local path ( dir://), you can additionally choose to only link to the Installation Media. Skip copying of medium Do not copy additional Installation Media. Choose this option if you do not need additional Installation Media or if you want to install additional Installation Media directly from their source, for example CDs/DVDs or flash disks. When choosing this option despite your SAP product requiring additional Installation Media, you will later need to provide the SAP Installer (SAPinst) with the relevant paths. Proceed with Next. If you chose to copy Installation Media, the SAP Installation Wizard will then copy the relevant files to your local hard disk. Figure 4.4: SAP Installation Wizard: Additional Installation Media • After copying the Installation Media, you will be asked whether you want to copy ( “ prepare”) more Installation Media.

To do so, click Yes. After doing so, follow the instructions in. Otherwise, click No. • You will be asked whether you want to copy Supplementary Media or Third-Party Media. To do so, click Yes. After doing so, follow the instructions in.

Otherwise, click No. For information on creating Supplementary Media, see.

• On the screen Additional software repositories for your SAP installation, you can add further software repositories. This can be useful, for example, for installing add-ons that are packaged as RPM. To do so, click Add new software repositories. For more information on adding repositories, see Deployment Guide, Chapter 8 “ Installing and Removing Software”, Section 8.3.1 “ Adding Software Repositories” (). Proceed with Next.

Tip: Installation Log Files If the installation of the SAP application fails, it may help to look at installation log files ending in.err located in /var/adm/autoinstall. For more information on log files, see. • On the screen Tune your system for optimal performance, you can choose a tuning option for your system. Normally, the best option is preselected and you do not need to change the Profile name. Proceed with Next, then click OK. You can later change this configuration using sapconf. For more information, see.

• The final screen is Installation Completed. To create an AutoYaST file for this installation, activate Clone This System for AutoYaST. The AutoYaST file will be placed in /root/autoinst.xml and will overwrite AutoYaST files created earlier in the same location. Proceed with Finish. SAP_AUTO_INSTALL='yes' • In the case of an SAP HANA/SAP BusinessOne installation, the SAP Installation Wizard will later use the parameters documented in the AutoYaST files in /data/SAP_INST/ number. If you need to change any parameters, make sure to adapt the AutoYaST files at this point.

• Open the YaST control center and start SAP Product Installer. • You will be asked whether to continue the pending installation. Select Install. • All further interactions happen within the SAP Installer. Follow the steps of SAP Installer as described in the documentation provided to you by SAP. Important: Avoid Using Windows* Operating Systems for Copying Using Windows operating system for copying or copying from/to Windows file systems like NTFS may break permission settings and capitalization of files and directories. You can now install from the NFS server you set up.

In the SAP Installation Wizard, specify the path this way: server_name/srv/www/htdocs/sap_repo. For more information on how to specify the path, see. For information about installing SUSE Linux Enterprise Server from an NFS server, see Deployment Guide, Chapter 13 “ Remote Installation”, Section 13.2.2 “ Setting Up an NFS Repository Manually” (). Problem The kernel swaps out rarely accessed memory pages to use freed memory pages as cache to speed up file system operations, for example during backup operations.

SAP NetWeaver and SAP HANA use large amounts of memory for accelerated access to business data. Parts of this memory are rarely accessed. When a user request needs to access paged-out memory, the response time is poor. It is even worse when an SAP application running on Java incurs a Java garbage collection: The system starts heavy page-in (disc I/O) activity and has a poor response time for an extended period of time. Solution SUSE Linux Enterprise Server for SAP Applications includes a kernel tuning option that allows the system administrator to limit the amount of page cache that the kernel uses when there is competition between application memory and page-cache.

This option tells the kernel that when the page cache is filled to the configured limit, application memory is more important and should thus not be paged out. No pages will be paged out if the memory footprint of the workload plus the configured page-cache limit do not exceed the amount of physical RAM in the system.

I thought I saw some inconsistent behavior lately in slicense after system copies. Unfortunately, I don't remember all the details. I attributed it to either my user error, patch level, or that lately we have been using virtual servers for some downstream servers. In addition, for some reason our PRD ECC 6.0 system displayed no system number even though it had been working correctly for years and showed green license keys. It still worked without the system number.

I relicensed it to make that concern go away. We are at ECC 6.0 on PRD, with some downstream servers at EHP4.

We expect to be all EHP4 by year's end.