1

Linke SAP Ready AMIs on Amazon Web Services Marketplace

Before We Start This document introduces a product offering by Linke and will guide the reader through the process of setting up and deploying our product.

It is assumed that the reader has the proper technical knowledge on the technologies mentioned below including but not restricted to: AWS architecture, Linux, Microsoft Windows, SAP Basis technology, Hana Database and SQL Server Database.

Welcome Linke SAP Ready AMIs deliver fresh installations of SAP NetWeaver and SAP Business Suite products such as SAP ERP, SAP S/4HANA and SAP CRM. All AMIs have been installed by a team of experienced SAP Basis and AWS Consultants including all available best practices for deployment of SAP systems on AWS.

SAP Ready AMIs are suitable for deploying small to midsize SAP systems running on a single EC2 instance. All software is delivered in a single EC2 instance. Storage layout has been prioritized to reduce costs and not to maximize performance. For this reasons, SAP Ready AMIs are best suited for non-production SAP systems with no requirements for high performance. Production SAP systems are recommended to be deployed in High Availability and prioritize performance of storage subsystem.

For production use cases and high availability scenarios we recommend the usage of custom built systems that follow the best practices delivered by SAP and AWS and are available on: http://aws.amazon.com/es/sap/resources/

At Linke we can also offer custom deployment options for large-scale, highly available and replicated SAP systems on AWS. You can reach us at contact@linkeit.com

Licensing - Bring Your Own License (BYOL) SAP Ready AMIs do not include the corresponding SAP or database license. Operating systems license costs are charged as part of EC2 costs for you. You as a customer acknowledge that you already have the license required to use this software. Also, you will be responsible for operating your own AWS account.

Please obtain your SAP license through SAP or your preferred SAP partner. Then download your license file from SAP ONE Support Launchpad (https://launchpad.support.sap.com/)

2

Costs SAP Ready AMIs costs can be differentiated into two groups.

• AWS Costs: This includes all AWS related costs applied to your AWS account. Most relevant costs under this group are EC2 costs, EBS costs and Data Transfer costs.

• Software Costs: This is an extra charge on top of EC2 costs that covers the working hours and effort invested to setup and deliver the SAP Ready AMIs to you on the AWS Marketplace.

All costs are billed to you through your AWS account following AWS payment and billing procedures setup for your account.

Document version This document has been reviewed on February 28th, 2017 and reflects some changes implemented on the latest versions of our SAP Ready AMIs at that time.

AMI version This document covers all required actions that are required to launch a SAP Ready AMI into your AWS account, connect to it and get SAP started for you.

The following table details the SAP Ready AMI version covered in this document.

Name Operating System SAP Product Version Database Product Version

S41610 HANA Suse Suse Linux 12.1 SAP S4 1610 SP00 HANA 1.SP12

Our team of consultants is continuously working on updating available AMIs and adding new products. In case you miss something, please let us know by sending an e-mail to AWSDEVOPS@linkeit.com

SAP Installation data During the SAP software installation in this AMI some options had to be chosen to complete the installation. Chosen options are detailed below.

• Virtual Hostname: SAP software has been installed using the Virtual Hostname parameter so that you can adjust the physical hostname of your EC2 instance without affecting the installed SAP Software.

• SAP Instances: This AMI includes a database instance, an ABAP SAP Central Services (ASCS) and Primary Application Server (PAS) or Central Instance (CI).

The following table shows the relevant information about the SAP software installation included in the AMI. Information such as SAP SID, Master Password, Instance number and software location in the server are shown here.

3

SAP Instance ASCS

Hostname Saps4bhan Domain linkeit.local

Master Password Zaq12wsX

SAPSID LNK

Instance number 02

SAP Software Owner lnkadm

DB Instance HANA

Hostname Saps4bhan Domain linkeit.local

Master Password Amis@2016

SAPSID HAN

Instance number 00

SAP Software Owner hanadm

(*) We encourage you to change the SAP installation Master Password so that it remains private to you and meets your security requirements.

Important: SAP GUI and HANA Studio are not installed in the AMI. You will need to install SAP GUI software in order to be able to connect and login into your SAP Instance, and HANA Studio to administrate HANA Database.

SAP Instance PAS

Hostname Saps4bhan Domain linkeit.local

Master Password Zaq12wsX

SAPSID LNK

Instance number 01

SAP Software Owner lnkadm

4

How to create your own SAP Business Suite environment

Prerequisites

• An AWS account - if you don't have one yet, you can register here (click "Sign Up Now"). Have your credit card handy

• A key pair (what is a key pair?) to secure the access to your AWS instance. Find documentation on how to create a key pair here. Remember the provided key name and store the *.pem file on your local hard disk. You can also create the .pem during the instance creation.

• Amazon VPC (Virtual Private Cloud) or EC2-Classic.

• An SAP Service Marketplace valid S-User Account for requesting the SAP License Key.

5

Part 1 - Create your own SAP instance on AWS • Log on to Amazon Market Place: https://aws.amazon.com/marketplace and find SAP Preinstalled AMI

by Linke Click into it and launch an instance.

• Configure AWS instance size from the available choices. For HANA database we need 61Gb minimum memory: Instance CPU Memory

• For more detailed information about SAP Business Suite Sizing and appropriate EC2 instance types, please refer to SAP documentation, SAP sizing tool and OSS Notes (S-User required): (http://service.sap.com/instguides) (http://service.sap.com/quicksizer) (http://service.sap.com/sap/support/notes/1656099)

• Configure and define a network and subnet. If you need to connect directly by internet you need to enable

Auto-assign Public IP.

• You can choose the EBS volume type, you can leave as default or use SSD / IOPS for best performance. In this point you can increase the size of the volumes to expand the filesystems. It depends on the size of the database you are going to use.

• Next step is to tag the instance so you can identify it in the AWS Console.

• The next step is the security group. You should adapt these settings to meet your specific security policies:

6

• You must provide the name of an existing key pair, or you will not be able to create an ssh connection to your instance. If you have not checked the prerequisites and still need to create a key pair, you can do so in the AWS console.

• After a few minutes, you can access your instance with SSH and do the final configuration steps.

Part 2 - Important SAP and HANA ports You have to open the necessary ports in AWS security Group to allow the connection. This is the list of most important ports for SSH, SAP and HANA:

To open other specific ports this is the list of the most important.

SAP External Ports: https://wiki.scn.sap.com/wiki/display/TCPIP/Application+Server+ABAP

Hana External Ports: https://wiki.scn.sap.com/wiki/display/TCPIP/SAP+HANA+Platform

7

Part 3 – SSH connection to your SAP AWS instance • In the EC2 console, navigate to “INSTANCES à Instances”. This should show all your instances in

Amazon EC2. Make sure the SAP instance you want to connect to is in “running” state. If not, choose the instance, then click on “Instance Actions” menu, and click on “Start” in the pull down menu.

• Make a note of the IP address assigned to the instance. You will need it to connect to this SAP instance in AWS.

• SSH to the instance with “ec2-user” and the key pair chosen at launch time and reboot the system. (You can “sudo su –“ to be able to reboot the instance.)

>ssh –i <Key-pair.pem> ec2-user@<IP addres>

• The first time you start SAP may take longer since the disks in AWS are still not stable. The successive starts will be immediate.

We recommend you to run a prewarming first time you start the system to increase performance from the beginning. This can take a long time depending on the size of the disks and the status of the AWS network since the process will synchronize the data of the disks with AWS S3

This is the AWS document that explains these steps:

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-initialize.html

It will only be necessary to perform these actions once after the creation of the Instance

In our case the commands to be executed are as follows, please note, it can take up to 12 hours for all these commands to execute successfully depending on EBS size and types chosen for your instance.

sudo dd if=/dev/mapper/vg_sap-lv_usrsaphana of=/dev/null bs=1M

8

sudo dd if=/dev/mapper/vg_sap-Lv_sapmnt of=/dev/null bs=1M sudo dd if=/dev/mapper/vg_hanalog-lv_hana_log of=/dev/null bs=1M sudo dd if=/dev/mapper/vg_hanadata-lv_hana_data of=/dev/null bs=1M sudo dd if=/dev/mapper/vg_hanashared-lv_hana_shared of=/dev/null bs=1M

If you do not execute these actions, the first time you run SAP it will take a long time to boot.

9

Part 4 – Configure HANA Studio to HANA Database access To manage the HANA database, you need to install the Hana studio program on a PC/laptop, you can download it from the SAP website (https://launchpad.support.sap.com) with S-User credentials. To connect you have to enter the connection data of the instance created in AWS.

We need to configure SAP Hana Studio to install the new license. The first time you connect to Hana studio an error message will appear to inform that you need a proper license. To install it see the next part.

10

Part 5 – Licensing SAP Instance: HANA License: To install the HANA license, you need to connect to Hana studio as seen in Part5. SAP HANA Database is started automatically when you start the instance. So is not necessary to start HANA from operating system when you do this part.

When you try to connect to HANA Database firs time in Hana Studio, you get the error:

You have to open the Properties:

You need to save the Hardware Key to request for a new License.

And add a new License Key.

11

Go to https://support.sap.com/keys-systems-installations/keys.html and obtain a valid license key for your HANA system.

Here you have more information on how to add the license:

https://help.sap.com/saphelp_hanaplatform/helpdata/en/c1/2868abbb571014abb6a940e75f9c3e/content.htm

SAP License: • Get the instance’s hardware key to obtain the license from the SAP Service Marketplace issuing the

command “saplicense –get” as the lnkadm user:

• Go to https://support.sap.com/keys-systems-installations/keys.html and obtain a valid license key for your system (SID LNK and the hardware key obtained in the preceding step). Now you have a text file with the license.

• The installation license will have expired, so we can only enter with the SAP* user. To activate SAP* user we need to modify the default profile. You must edit the SAP file ( /sapmnt/LNK/profile/DEFAULT.PFL) and add the parameter “login/no_automatic_user_sapstar” with value 0 so you’ll be able to log into the SAP System once it’s started and install the license.

• Start the SAP instance or restart it and logon in SAPGUI with user SAP* and the Master Password “Zaq12wsX” (Case Sensitive) to install the SAP license and start working with the system.

• To add the SAP license, go to transaction “slicense” and insert the text file you get before.

• To stop SAP and the Database cleanly, you can use the command “/script/Stop_SAP.sh”

NOTE: we strongly recommend that you update the Master Password and apply a proper password management mechanism.

12

Part 6 - Start SAP S4 1610 on HANA AWS instance In order to be able to connect to your SAP instance for starting SAP software you need to connect by ssh software with correct “.pem” certificate created in part 1.

> ssh -i (pem file) ec2-user@(public IP)

To run the START/STOP scripts you have to switch to super user:

>sudo su –

In the /script/ folder you can find scripts to start and stop Hana DB instance and SAP instances.

To start SAP run:

> /script/Start_SAP.sh

(note: If you have not done the prewarming disks, the first time will take a long time to boot.)

• You can check if HANA has started in other terminal connection when you see all the HANA processes running with the command like “ps auxf”:

13

• And review that the SAP instance has started with the same command “ps auxf”. The output should look like this:

14

Part 7 – Configure SAP GUI to your SAP Instance You need the SAP GUI software installed in your PC/Laptop to access SAP Instance.

SAP GUI software can be downloaded from SAP Support Launchpad website (https://launchpad.support.sap.com). SAP Support S-User credentials are required.

Open SAP GUI on you PC/laptop and enter the connection data for your newly created SAP AMI.

To connect to the SAP Instance you need to install the SAP License And start the Instance from Operating System. You can see how to do this in the following parts

15

Part 8 - SAP SYSTEM DETAILS All Preinstalled SAP SYSTEMS have the same technical configuration:

Hostname saps4bhan

Domain Linkeit.local SAP Master Password Zaq12wsX

HANA Master Password Amis@2016

SAP SID LNK

HANA SID HAN

Message server port 3602

Hana Access Port 30015

SAP Instance numbers 01 (PAS), 02 (ASCS)

HANA Instance numbers 00 (HANA)

SAP Software Owner lnkadm

HANA Software Owner hanadm

16

Part 9 – Architecture Highlights • The SAP system is installed using the best practices and recommendations from Suse Linux and HANA DB

for SAP.

Control Costs You will be responsible for operating your AWS account and you will have to pay for the hosting costs. In order to control your costs, we suggest you stop your instance when you are not using it. Starting your instance just takes a few minutes, so you can fire it up when you need it. To stop your instance, find it in the AWS console, right click the instance and choose "Stop" from the context menu. To start it again, choose "Start" from the same context menu. Be aware that AWS also charges you very little money for stopped instances - if you want to stop using your SAP instance on AWS, and you don't want to pay any more monthly bills, make sure to terminate your instance. It will then be permanently deleted. To terminate your instance, choose "Terminate" from the context menu. AWS also provides tools to monitor your usage, so there are no surprises when you get your monthly bill - from your "My Account / Console" menu on the top right corner of the screen on http://aws.amazon.com, choose "Account Activity" and you will see your activity for the current month.

OS•SUSE12.1•LogicalVolumesforallthefilesystems.•SAPNoteswithrecommendationsforSuseapplied.

DATABASE•HANA1SP12BestPractices.

SAP•Readytouse.•S4HANA1610andBusinessSuiteProducts(ERP,CRM,SRM,SCM).•ABAP.