SAP Solution Manager 7.2 SR2 ASE on Suse (SAP License not included)

In this section you will find the required information to start using your SAP Netweaver 7.52 ABAP ASE on Suse instance in just minutes.

Topics

What does the instance include

EC2 instance comes with the following products:

SAP Solution Manager 7.2 SR2
SAP ASE 16.0
SuSE Enterprise Server 15.1

EC2 & SAP information

The following table shows the relevant information about the SAP software installation included in the AMI:

SAP Instance	Values
Hostname	sapsolman
Domain	linkeit.local
Master Password	Zaq12wsXXX
SAP ABAP SID	LNK
SYB ABAP SID	LNK
Syb ABAP Admin User	syblnk
ASCS ABAP Instance Number	01
PAS ABAP Instance number	10
SAP ABAP Software Owner	lnkadm
SAP ABAP SID	LNJ
SYB ABAP SID	LNJ
Syb ABAP Admin User	syblnj
ASCS ABAP Instance Number	02
PAS ABAP Instance number	20
SAP ABAP Software Owner	lnjadm

Password Change

It is mandatory to change the Database installation Master Password so that it remains private to you and meets all security requirements.

Deploy your instance

Follow the next steps to deploy your new SAP instance:

Log on to Amazon MarketPlace https://aws.amazon.com/marketplaceopen in new window
Search for "Preinstalled SAP SolMan 7.2SR2 ASE (SAP License not included)" and access the product
Click on Continue to Subscribe.
Choose an Instance Type. Select one of the AWS instance size from the available choices.
Configure Instance Details Configure and define a network and subnet. If you need to connect directly by internet you need to enable Auto-assign Public IP.
Add Storage. 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.
Add Tags. Next step is to tag the instance so you can identify it in the AWS Console.

Configure Security Group. You have to open the necessary ports in AWS security Group to allow the connection.

Minimal ports needed to access the instance are:

Header	Protocol	Port Range	Description
SSH	TCP	22	Connect to the EC2 instance remotely
SAP Dispatcher	TCP	3200-3299	Used by SAP Gui for Windows and Java
SAP Gateway	TCP	3300-3399	Used for CPIC and RFC communication
SAP JAVA	TCP	50000 - 59999	Default Por Range for Java servers
ICM HTTP	TCP	8000-8099	Default port range. Can be set up for any different port
ICM HTTPS	TCP	44300 - 44399	Defaultport range. Can be set up for any different port

TCP/IP Ports of All SAP Products

Find additional information in https://help.sap.com/docs/Security/575a9f0e56f34c6e8138439eefc32b16/616a3c0b1cc748238de9c0341b15c63c.html?locale=en-USopen in new window

Review Instance Launch. Review the configuration and click on Launch when accepted.
The process will ask you to provide an existing Key Pair or to create a new one. If you choose to create a new one, do not forget to download the Key Pair file as this will be mandatory to access the EC2 instance through SSH.
After a few minutes, you can access your instance with SSH and do the final configuration steps.

Post-deployment Steps

The following is the list of tasks to be done before you can start working with your SAP environment:

Connect to your EC2 instance

For some actions you will need to access your EC2 instance via SSH. To do so, follow the next steps:

In the EC2 console, navigate to instances. This will list 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. To access your instance:
1. Open an SSH client. (If you are running Windows, check how to connect using Puttyopen in new window
2. Locate your private key file (<keypair>.pem).
3. Connect to your instance using its IP:
```
ssh -i "<keypair_path>/<keypair>.pem" ec2-user@<IP Addr>
```

EBS Pre-warming

We recommend you run some pre-warming commands the first time you start the system to increase performance from the beginning. First time you launch an instance from an AMI, the process synchronizes the snapshots that compose this AMI with the EBS volumes of your instance. This can take a long time depending on the size of the disks and the instance type you have chosen. Depending on the instance, it can run out of storage credits and perform at its baseline (3 iops x gb), this situation becomes a bottleneck. The process can take up to 12 hours with a m4.4xlarge instance.

To pre-warm your disks follow the guidelines in the AWS Documentation Guide http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-initialize.htmlopen in new window

Start SAP instance

Follow these steps to start your SAP instance:

Connect via SSH to your EC2 instance as describe in the previous section.
From the ec2-user shell, jump into the lnkadm user to start the SAP ABAP instance:
```
sudo su - lnkadm
```
Execute startsap command to start all required services.
```
startsap
```
If the instance is correctly started, you will see a message like the one below:
```
Instance on host sapsolman started
```
Execute exit to jump back to the ec2-user shell:
```
startsap
```
From the ec2-user shell, jump into the lnjadm user to start the SAP Java instance:
```
sudo su - lnjadm
```
Execute startsap command to start all required services.
```
startsap
```
If the instance is correctly started, you will see a message like the one below:
```
Instance on host sapsolman started
```

License your SAP Server

Follow these steps to obtain and install a new license for the deployed SAP instance:

Get the instance’s hardware key to obtain the license from the SAP Service Marketplace issuing the following command as the lnkadm user:
```
saplicense -get
```
Go to https://support.sap.com/keys-systems-installations/keys.htmlopen in new window 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.
Configure SAPGUI to access the SAP Server. Change the IP for the one obtained during instance launch.
Log in to SAP with SAPGUI to Client 000, with user SAP* and Password Zaq12wsX (Case Sensitive).
Call transaction SLICENSE
Click on New Licenses if needed, click Install and insert the text file you received from SAP.

Ready to work

If all the previous steps are done, you are ready to start working with your new SAP Instance!

Check [Maintenance] section for more details in how to manage the daily basis.

# SAP Solution Manager 7.2 SR2 ASE on Suse (SAP License not included)

# What does the instance include

# EC2 & SAP information

# Deploy your instance

# Post-deployment Steps

# Connect to your EC2 instance

# EBS Pre-warming

# Start SAP instance

# License your SAP Server

# Ready to work