Rocket Steam Preinstalled SAP Systems on Amazon Web Services

Before We Start This document introduces a product offering by Rocket Steam 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, Red Hat Linux, SAP Basis technology and Oracle Database

Welcome Rocket Steam Preinstalled SAP systems AMIs include a SAP Business Suite system already installed. Installation has been done by a team of experienced SAP Basis and AWS Consultants including all available best practices for deployment of SAP systems on AWS. Preinstalled SAP systems are complete SAP Business Suite product installations in a single EC2 instance, including SAP Database and SAP Netweaver Application Server (ABAP). These systems are ideal for small and medium deployments of non-productive systems where a single instance can handle all workload and no high availability is required. 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 available on: http://aws.amazon.com/es/sap/resources/ At Rocket Steam we can also offer custom deployment options for large-scale, highly available and replicated SAP systems on AWS. You can reach us at contact@rocket-steam.com The Preinstalled SAP systems AMIs do not include the corresponding SAP product license. 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.

Document version This document has been reviewed on September 4th, 2015 and reflects some changes implemented on the latest versions of our Linux/Oracle AMIs at that time.

These are the current AMIs we made available for you: Platform SAP Product Version Database Product Version

Red Hat Enterprise Linux 6.7 64-bit SAP Netweaver 7.4 SR1 Oracle 11.2.0.4 on ASM

Red Hat Enterprise Linux 6.7 64-bit SAP ERP 6 Ehp7 SR1 Oracle 11.2.0.4 on ASM

Red Hat Enterprise Linux 6.7 64-bit SAP CRM 7.0 Ehp3 SR1 Oracle 11.2.0.4 on ASM

Red Hat Enterprise Linux 6.7 64-bit SAP SCM 7.0 Ehp3 SR1 Oracle 11.2.0.4 on ASM

Red Hat Enterprise Linux 6.7 64-bit SAP SRM 7.0 Ehp3 SR1 Oracle 11.2.0.4 on ASM

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 contact@rocket-steam.com

Licensing This is offered as a BYOL (Bring Your Own License) model. Please obtain your SAP license through SAP or your preferred SAP partner.

Then download your license file from SAP Service Marketplace (http://service.sap.com/licensekeys).

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.

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

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

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 Rocket-Steam Click into it and  launch an instance.

• Review the options and click continue:

• Configure AWS instance size from the available choices. For small SAP systems, up to 10 concurrent users,

we recommend that you use an EC2 instance with at least 7.5 Gb or memory (ex. m3.large). For medium sized systems, up to 50 concurrent users, we recommend that an EC2 instance with at least 15 Gb of memory (ex. r3.large). 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)

• You can launch the SAP System on EC2-CLASSIC or VPC:

• Next you can choose the EBS volume type, you can leave as default or use SSD / IOPS for best performance:

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

• The next step is the security group. Default proposed values allow access from anywhere. You should adapt this settings to meet your specific security policies:

• You can review your options here:

• 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 - Connect 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 again to the instance and wait for Oracle ASM instance to start (It might several minutes based). You can check it has started when you see all the ASM processes running with the command like “ps auxf”:

• Once the ASM instance has started, execute “sudo su –“ to become root user, and then “su – rckadm” to launch the next commands as the SAP Software administrator user.

• Now you must edit the SAP default profile (file /sapmnt/RCK/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.

• You can then start the SAP system and the database with the command “/usr/local/bin/startall”. Review that the SAP instance has started issuing a “ps auxf” command. The output should look like this:

• Get the instance’s hardware key to obtain the license from the SAP Service Marketplace issuing the command “saplicense –get” as the rckadm user:

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

• Now you can logon to the SAP System with SAPGUI with user SAP* and the Master Password “Zaq12wsX” (Case Sensitive) to install the SAP license and start working with the system.

• To stop SAP and the Database cleanly, you can use the command “/usr/local/bin/stopall”

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

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

Hostname genlocalhost

Domain gendomain.com

Master Password Zaq12wsX

ASM SID ASM

Oracle Grid Home /oracle/GRID/11204

Oracle SID RCK

Oracle Home /oracle/RCK/11204

Oracle Listener Port 1521

Oracle Software Owner oracle

SAPSID RCK

Instance numbers 01 (ASCS), 00 (DVEBMGS00)

SAP Software Owner rckadm

Part 4 – Architecture Highlights • The SAP system is installed using the best practices and recommendations from RedHat, Oracle and SAP.

OS  • Logical  Volumes  for  all  the  filesystems.  •   16GiB  Swap  • SAP  Notes  with  recommendaGons  for  RHEL  applied.  

DATABASE  • Oracle  Best  PracGces  and  SAP  Notes  for  Oracle.  • AutomaGc  Storage  Management.  • Latest  SBP  Installed.  

SAP  • Ready  to  use.  • Netweaver  7.41    and  Business  Suite  Products  (ERP,  CRM,  SRM,  SCM).  • ABAP.  

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.