SAP NW 7.50 Java ASE Suse

Preinstalled SAP NW 7.50 Java ASE on Suse (SAP License not included) #

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 product.support@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.

  • 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.

SAP Instance Values
Hostname sapnwjava
Domain linkeit.local
Master Password Zaq12wsXXX
SAPSID LNK
SYBSID LNK
Syb Admin User syblnk
SCS Instance Number 01
PAS Instance number 00
SAP Software Owner lnkadm
SAP NW Java Administrator User Administrator

PASSWORD CHANGE: It is mandatory to change the SAP and Database installation Master Password so that it remains private to you and meets all security requirements.
Important: SAP GUI is 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.

Getting Started #

Part 1 - Create your own SAP instance on AWS #

Start your new SAP server by following the next steps.

  1. Log on to Amazon Market Place: https://aws.amazon.com/marketplace/pp/B084GTTDQ7 and click on Continue to Subscribe

  2. Choose an Instance Type Select one of the AWS instance size from the available choices.

    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)

  3. 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.

  4. 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.

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

  6. Configure Security Group. You should adapt these settings to meet your specific security policies.

  7. Review Instance Launch. Review the configuration and click on Launch when accepted.

  8. 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.

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

Part 2 - Important SAP and Sybase 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 Syb:

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

Part 3 – SSH connection to your SAP AWS instance #

  1. 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.

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

  3. SSH to the instance with ec2-user and the key pair chosen at launch time. To access your instance: 1.Open an SSH client. (Recommended - find out how to connect using PuTTY) 2.Locate your private key file (.pem). 3.Connect to your instance using its IP:

    Example:

        ssh -i "<keypair_location>/<keypair>.pem" ec2-user@<IP Addr>
    

    ``

  4. The first time you start SAP may take longer (up to 1 hour) since the disks in AWS are still not stable. The successive starts will be immediate.

    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. 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. If you do not execute these actions, the first time you run SAP it will take a long time to boot.

Part 4 – Configure Sybase #

Sybase doesn’t need further configuration, as the database will start at boot.

Part 5 – Configure SAP #

Drawing
  1. 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
  1. 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.

  2. The SAP Instance is started at boot. Stop it to configure access to the SAP NW Administrator, executing the following command connected to a shell as lnkadm:

stopsap
  1. Configure SAP Netweaver Administrator.

  2. Start all processes to access SAP NW Administrator, executing the following command connected to a shell as lnkadm:

startsap
  1. Logon to the instance by web at port 22 and go to /sapmnt/LNK/global/security/data/ and editing the ``icm_filter_rules.txt``` file. You can configure access by setting rules or just comment the lines, like this:
# if %{REMOTE_ADDR} !stricmp 127.0.0.1 [AND]
# if %{REMOTE_ADDR} !stricmp ::1
# RegIRedirectUrl ^/webdynpro/resources/sap.com/tc~lm~itsam~ui~mainframe~wd/.*$ /nwa/remote_access_error [QSA]
Drawing
  1. Logon to SAP with web explorer to URL http://50000/nwa and Password Zaq12wsXXX (Case Sensitive).
PASSWORD CHANGE: Remember that it is mandatory to change the SAP and Database installation Master Password so that it remains private to you and meets all security requirements.
Drawing
  1. The system will force you to change the password.

  2. To install the SAP license, go to Configuration, Infrastructure, Licenses click on Install from file, and insert the text file you received from SAP.

Drawing
  1. A succesfull message should be received and the license should be installed

Ready to work #

Now you are ready to start working with your SAP instance!!

Additional Information #

Start/Stop processes #

Start ALL #

Stop the SAP instace by executing the following commands connected to a shell as lnkadm:

startsap

Start SAP NW752 ABAP on AWS instance #

In order to be able to connect to your Instance for starting SAP software you need to connect by ssh software as explained in previous Part.

Start DB #

Sybase instance should start automatically, but in case it fails it can be started connected to a shell with user lnkadm:

startdb
Start SAP #

Start the SAP instace by executing the following commands connected to a shell as lnkadm:

startsap
All-in-One with custom scripts #

Additionaly, Linke provider with a custom script located in the /etc/init.d folder that can help you to start all the services in one step at boot. Execute this script connected to a shell as root user:

/etc/init.d/startsap_syb start

Check that the instance is running by executing the following the command ps -fu lnkadm. The output should be similar to this:

sapnwjava:~ # ps -fu lnkadm
UID        PID  PPID  C STIME TTY          TIME CMD
lnkadm    2610     1  0 11:28 ?        00:00:01 /usr/sap/LNK/SCS01/exe/sapstartsrv pf=/usr/sap/LNK/SYS/profile/LNK_SCS01_sapnwjava -D -u lnkadm
lnkadm    2852     1  0 11:28 ?        00:00:01 /usr/sap/LNK/J00/exe/sapstartsrv pf=/usr/sap/LNK/SYS/profile/LNK_J00_sapnwjava -D -u lnkadm
lnkadm   27114     1  0 12:27 ?        00:00:00 sapstart pf=/usr/sap/LNK/SYS/profile/LNK_SCS01_sapnwjava
lnkadm   27127 27114  0 12:27 ?        00:00:00 ms.sapLNK_SCS01 pf=/usr/sap/LNK/SYS/profile/LNK_SCS01_sapnwjava
lnkadm   27128 27114  0 12:27 ?        00:00:00 en.sapLNK_SCS01 pf=/usr/sap/LNK/SYS/profile/LNK_SCS01_sapnwjava
lnkadm   27129 27114  0 12:27 ?        00:00:00 gw.sapLNK_SCS01 pf=/usr/sap/LNK/SYS/profile/LNK_SCS01_sapnwjava -no_abap
lnkadm   28528     1  0 12:27 ?        00:00:00 sapstart pf=/usr/sap/LNK/SYS/profile/LNK_J00_sapnwjava
lnkadm   28608 28528  0 12:27 ?        00:00:01 jc.sapLNK_J00 pf=/usr/sap/LNK/SYS/profile/LNK_J00_sapnwjava
lnkadm   28609 28528  0 12:27 ?        00:00:00 ig.sapLNK_J00 -mode=profile pf=/usr/sap/LNK/SYS/profile/LNK_J00_sapnwjava
lnkadm   28610 28609  0 12:27 ?        00:00:00 /usr/sap/LNK/J00/exe/igsmux_mt -mode=profile -restartcount=0 -wdpid=28609 pf=/usr/sap/LNK/SYS/profile/LNK_J00_sapnwjava
lnkadm   28611 28609  0 12:27 ?        00:00:00 /usr/sap/LNK/J00/exe/igspw_mt -mode=profile -no=0 -restartcount=0 -wdpid=28609 pf=/usr/sap/LNK/SYS/profile/LNK_J00_sapnwjava
lnkadm   28612 28609  0 12:27 ?        00:00:00 /usr/sap/LNK/J00/exe/igspw_mt -mode=profile -no=1 -restartcount=0 -wdpid=28609 pf=/usr/sap/LNK/SYS/profile/LNK_J00_sapnwjava
lnkadm   28738 28608  0 12:27 ?        00:00:00 /usr/sap/LNK/J00/exe/icman -appTrc pf=/usr/sap/LNK/SYS/profile/LNK_J00_sapnwjava -nodeId=1 -f /usr/sap/LNK/J00/work/dev_icm
lnkadm   28756 28608 13 12:27 ?        00:02:01 /usr/sap/LNK/J00/exe/jstart -appTrc -nodeId=2 pf=/usr/sap/LNK/SYS/profile/LNK_J00_sapnwjava -DSAPINFO=LNK_00_server0 -hostvm 

The script will start all the processes once the instance is launched or started.

Stop SAP NW750 Java on AWS instance #

Stop ALL #

Stop the SAP instace by executing the following commands connected to a shell as lnkadm:

stopsap
Stop only SAP #

Stop the SAP instace by executing the following commands connected to a shell as lnkadm:

sapcontrol -nr 10 -function Stop
sapcontrol -nr 01 -function Stop
Stop only Sybase #

To stop the Sybase server, execute the following command connected to a shell with user lnkadm:

stopdb
All-in-One with custom scripts #

Additionaly, Linke provider with a custom script located in the /etc/init.d folder that can help you to start all the services in one step. Execute this script connected to a shell as root user:

/etc/init.d/startsap_syb stop