Provisioning SAP S/4HANA and SAP HANA

Prerequisites

The SAP HANA and SAP S/4HANA software installation packages have been uploaded to the OBS bucket. For details about how to upload packages, see Uploading the Software Packages.

Procedure

1. Log in to the management console. In the upper right corner, choose Enterprise > Project Management.

   The Enterprise Project Management page is displayed.

2. In the navigation pane, choose Application Management > Applications.

   The application list is displayed in the lower part of the page.

3. Click Create Application in the upper left of the application list.

   The Create Application page is displayed.

4. Configure basic application information. Set the parameters based on Table 1.

   Table 1 Configuration information

   Parameter	Description	Example Value
   Enterprise Project Name	Select an existing enterprise project from the drop-down list box.	SAP
   Region	Select a region to create the application. A maximum of 100 applications can be created in each region.	CN-Hong-Kong
   Application Name	Specifies the name of the provisioned application.	S4HANA-1709
   Application Description	Optional. The description can contain a maximum of 256 characters.	-
   Source Type	Select Example Templates or My Templates as required.	Example Templates
   Template Type	Set it to SAP or Common as required.	SAP
   Select Template	Select the template from the list. If there are many templates, you can enter the template name in the search box to search for the template.	S4HANA-Standard-With-DB

5. Click Next.
6. On the displayed page, configure parameters. For details, see Table 2.

   Table 2 Configuration information

   Parameter	Description	Example Value
   Network and Basic Configuration
   VPC Name	Name of the VPC where the HANA ECS is located If no VPC is available, click Create VPC on the management console to create one. For details, see Creating a VPC.	vpc-sap-hana
   Subnet	Subnet used by the HANA ECS If no subnet is available, click Create Subnet on the management console to create one. For details, see Creating a Subnet and Configuring a Security Group.	subnet-fd25-sap-hana
   AZ	Name of the AZ where the SAP S/4HANA ECS is located.	AZ1
   Security Group	Security group to which the SAP S/4HANA ECS belongs If no security group is available, click Create Security Group on the management console to create one. For details, see Creating a Subnet and Configuring a Security Group.	c28cef02-d150-4a62-8d98-ff5b2a663289
   Key Pair	Key pair for logging in to the S/4HANA ECS If no key pair is available, click Create Key Pair on the management console to create one. For details, see Creating a Key Pair.	KeyPair-sap-hana
   IAM Agency	IAM agency name. After the IAM agency is configured, the ECS has the permission to access OBS and Cloud Eye. For details about the agency name, see Configuring an Agency.	DataProviderAccess
   HANA Database Configuration
   HANA Hostname	SAP HANA hostname. The name must be 1 to 13 characters long and must contain only letters, digits, periods (.), hyphens (-), and underscores (_).	hana-1709
   HANA Specifications	Specifications of a HANA ECS. Set this parameter as required.	e3.7xlarge.12 | 28vCPUs | 348GB
   Image	Image of a HANA ECS Select an image based on Requirements on OSs and Disks.	Private image: SUSE Linux Enterprise Server for SAP Applications 15
   HANA System ID	SAP HANA system ID. The ID is composed of one uppercase letter and two digits.	S00
   System Disk Type	Type of the system disk	Ultra-high I/O
   System Disk (GB)	Size of the system disk (GB)	50
   Usrsap Disk Type	Type of the usrsap disk	Ultra-high I/O
   Usrsap Disk (GB)	Size of the usrsap disk (GB)	50
   Swap Disk Type	Type of the swap disk	Ultra-high I/O
   Swap Disk (GB)	Size of the swap disk (GB)	10
   Shared Disk Type	Type of the shared disk	Ultra-high I/O
   Shared Disk (GB)	Size of the shared disk (GB)	418
   Log Disk Type	Type of the log disk	Ultra-high I/O
   Log Disk (GB)	Size of the log disk (GB)	200
   Data Disk Type	Type of the data disk	Ultra-high I/O
   Single Data Disk (GB)	Size of an EVS disk (GB) If the LVM is not configured, the value is the size of a single EVS disk. If the LVM is configured, the value is the size of the EVS disks that from the logical volume.	250
   Data Disk Quantity	Number of data disks. Set this parameter based on the actual situation. If the LVM is not configured, the data disk is an EVS disk. Choose 1 from the drop-down list. If the LVM is configured, the data disk is a logical volume formed by multiple EVS disks. Choose the number of the EVS disks form the drop-down list.	1
   Backup SFS AZ	Name of the AZ where the SFS ECS is located	AZ1
   Backup SFS Size (GB)	Size of the created SFS file system for backing up the HANA database	1044
   HANA Instance Number	Instance number of the SAP HANA database	00
   HANA Password	Password of user SYSTEM to log in to the SAP HANA database. The password must comply with the SAP password setting rules.	-
   SAP Configuration
   S/4HANA Hostname	SAP S/4HANA hostname. The name must be 1 to 13 characters long and must contain only letters, digits, periods (.), hyphens (-), and underscores (_).	s4hana-1709
   S/4HANA ECS Specifications	SAP S/4HANA ECS specifications. Set this parameter based on the site requirements.	m3.large.8 | 2vCPUs | 16GB
   Image	Image of the SAP S/4HANA ECS Select an image based on Requirements on OSs and Disks.	Private image: SUSE Linux Enterprise Server for SAP Applications 15
   SAP System ID	SAP system ID. The ID is composed of one uppercase letter and two digits.	S01
   System Disk Type	Type of the system disk	High I/O
   System Disk (GB)	Size of the system disk (GB)	100
   Usrsap Disk Type	Type of the usrsap disk	High I/O
   Usrsap Disk (GB)	Size of the usrsap disk (GB)	50
   Sapmnt Disk Type	Type of the sapmnt disk	High I/O
   Sapmnt Disk (GB)	Size of the sapmnt disk (GB)	110
   Swap Disk Type	Type of the swap disk	High I/O
   Swap Disk (GB)	Size of the swap disk (GB)	64
   ASCS Instance Number	ASCS instance number	01
   PAS Instance Number	PAS instance number	02
   S/4HANA Password	Password of the SAP S/4HANA system. Confirm the password. The password must comply with the SAP password setting rules.	-
   OBS Backup Directory	Directory of the SAP S/4HANA installation package on OBS. For details, see Uploading the Software Packages. NOTE: The OBS bucket directory is in the format of obs://Bucket name/Directory.	obs://obs-sap/s4hana/s4hana1709
   Extended Configuration
   OS Version	OS version	SUSE 12
   S/4HANA Usage Type	Specifies the usage type of the SAP S/4HANA.	DEV
   Application Type	S/4HANA application type	S/4HANA
   S/4HANA Version	SAP S/4HANA version. Select a version from the drop-down list box.	S/4HANA 1709
   SAP Kernel Version	SAP kernel version	773
   Install SAP Software	Decide whether to install SAP software based on the site requirements.	Yes

7. Click Next.

   On the Confirm Specifications page, confirm the basic information and template parameters.

8. Click Submit and Pay.

   After the application is created, you can view it in the application management list.

Configuring Mutual Trust Between ECSs and Their Password

To enable the NAT server to communicate with SAP HANA and SAP S/4HANA ECSs using SSH, you need to configure mutual trust among them. The password for user root to log in to the created SAP S/4HANA ECS is the default image password. You need to use the key pair to log in to the NAT server to configure mutual trust between the NAT server and the SAP S/4HANA and SAP HANA ECSs and change the password of user root to log in to the SAP S/4HANA and SAP HANA ECSs.

1. For details about how to create a NAT server, see the SAP HANA User Guide (Single Node).
2. Use PuTTY to log in to the NAT server. Ensure that user root and the private key file (.ppk file) are used for authentication. Send the private key file and the authorized_keys file on the NAT server to the SAP S/4HANA and SAP HANA ECSs through the IP addresses. The commands are in the following format:

   scp /root/.ssh/id_rsa Peer IP address:/root/.ssh/id_rsa

   scp /root/.ssh/authorized_keys Peer IP address:/root/.ssh/

   For example, if the peer IP addresses are 10.0.3.102 and 10.0.3.2, run the following commands:

   scp /root/.ssh/id_rsa 10.0.3.102:/root/.ssh/id_rsa

   scp /root/.ssh/authorized_keys 10.0.3.102:/root/.ssh/

   scp /root/.ssh/id_rsa 10.0.3.2:/root/.ssh/id_rsa

   scp /root/.ssh/authorized_keys 10.0.3.2:/root/.ssh/

3. Verify the switching.

   Switch from the NAT server to the SAP S/4HANA and SAP HANA ECSs using SSH. Assume that the IP address of the SAP S/4HANA ECS is 10.0.3.102.

   ssh 10.0.3.102

   NOTE:

   During the first switching, the system displays the fingerprint as well as the message "Are you sure you want to continue connecting (yes/no)?". In such a case, enter yes and continue the switching.

4. After switching to the SAP S/4HANA and SAP HANA ECSs, run the following command to change the password of user root:

   passwd

   Enter the new password as prompted and confirm it.

   NOTE:

   Securely keep the root password. In addition, ensure that the passwords of user root for logging in to all ECSs are the same.

Modifying the Configuration File

Modify the configuration file on the server where the SAP application is deployed. For details, see What Should I Do If a SAP Application on an ECS Cannot Be Started?.

Checking SAP HANA Deployment Status

1. Use PuTTY to log in to the NAT server with an EIP bound. Ensure that the root user and the key file (.ppk file) are used for authentication. Then, use SSH to switch to the SAP HANA node.
2. Verify the SAP HANA installation.
   1. Run the following command to switch to the /hana/shared/$SID/HDB00/ directory:

      For example, run the following command to switch to the target directory:

      cd /hana/shared/S00/HDB00

   2. Switch to the database system administrator.

      Account s00adm is displayed on the page during the installation. Run the following command:

      su - s00adm

   3. Run the following command to query the database version:

      If the version can be queried, the database software is installed.

      HDB -version

      After the database is installed, the system returns the version information.

      HDB version info:
        version:             2.00.020.00.1500920972
        branch:              fa/hana2sp02
        git hash:            7f63b0aa11dca2ea54d450aa302319302c2eeaca
        git merge time:      2017-07-24 20:29:32
        weekstone:           0000.00.0
        compile date:        2017-07-24 20:35:12
        compile host:        ld4551
        compile type:        rel

3. Check whether the database process is running properly.
   1. Run the following command to check the process, taking the SAP HANA instance with ID 00 as an example:

      00 is the SAP HANA instance ID.

      sapcontrol -nr 00 -function GetProcessList

      In the terminal display, if the dispstatus value is GREEN, the process is running properly.

      13.04.2017 16:04:15
      GetProcessList
      OK
      name, description, dispstatus, textstatus, starttime, elapsedtime, pid
      hdbdaemon, HDB Daemon, GREEN, Running, 2017 04 13 11:18:33, 4:45:42, 3013
      hdbcompileserver, HDB Compileserver, GREEN, Running, 2017 04 13 11:18:42, 4:45:33, 3154
      hdbindexserver, HDB Indexserver, GREEN, Running, 2017 04 13 11:18:47, 4:45:28, 3180
      hdbnameserver, HDB Nameserver, GREEN, Running, 2017 04 13 11:18:34, 4:45:41, 3027
      hdbpreprocessor, HDB Preprocessor, GREEN, Running, 2017 04 13 11:18:42, 4:45:33, 3156
      hdbwebdispatcher, HDB Web Dispatcher, GREEN, Running, 2017 04 13 11:19:09, 4:45:06, 3513
      hdbxsengine, HDB XSEngine, GREEN, Running, 2017 04 13 11:18:47, 4:45:28, 3182
   2. Run the following command to return to user root:

      exit

Checking SAP S/4HANA Deployment Status

After the ECS is created, deploy SAP S/4HANA on the ECS. You can log in to the SAP S/4HANA ECS to view the deployment status.

1. Use PuTTY to log in to the NAT server with an EIP bound. Ensure that the root user and the key file (.ppk file) are used for authentication. Then, use SSH to switch to the SAP S/4HANA node.
2. Run the following command on the CLI to view the installation logs:

   tailf /var/log/huawei/auto-install/s4-intall.log

   If Install S/4HANA Successful is displayed in the installation log, the software deployment is complete. The following is an example of the log content indicating that the installation is successful:

   INFO      2018-12-26 17:50:26.325 (root/sapinst) (startInstallation) [syuxcpath.cpp:441]id=syslib.filesystem.creatingFile CSyPath::createFile()Creating file/tmp/sapinst_instdir/S4HANA1809/CORE/HDB/INSTALL/STD/ABAP/instslana.xml.
   INFO      2018-12-26 17:50:29.746 (root/sapinst)(startInstallation) [syuxcdir.cpp:147] id=syslib.filesystem.removedDirectoryCSyDirectoryImpl::sap_remove(ISyFSErrorHandler * pErrorHandler)Removed directory /root/.sapinst/s41809/4576.
   [2018-12-26 17:50:29] [INFO ] [s4-install.sh 319] Install S/4HANA successful
   [2018-12-26 17:50:29] [INFO ] [s4-install.sh 540] ******************End to install S/4HANA 1709********************
   [2018-12-26 17:50:29] [INFO ] [s4-install.sh 543] ******************clean password in the INIT files********************

   NOTE:

   The software deployment duration varies according to the software version and resource configuration.