SAP NetWeaver on IBM Cloud Infrastructure Quick Reference Guide Red Hat Enterprise Linux. December 2017 V1.0

Transcription

1 SAP NetWeaver on IBM Cloud Infrastructure Quick Reference Guide Red Hat Enterprise Linux December 2017 V1.0

2 2 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

3 Contents Purpose of this guide... 4 Installing a 32 GB server single-node... 5 Order your 32 GB server... 5 Preparing your server for the SAP installation (32 GB) Partitioning and file systems Installing a 256 GB and a 32 GB server in a three-tier setup Order your servers for a three-tier installation Preparing your server for the SAP installation (256 GB) Partitioning and file systems Network and NFS considerations for three-tier setup Provisioning external storage to your server Installing your SAP landscape RPM package prerequisites Download your SAP software Preparation for SAP s Software Provisioning Manager (SWPM) graphical user interface (GUI) Installing SAP software Appendix A Copyright IBM Corp All rights reserved. 3 without the prior written permission of IBM.

4 Purpose of this guide The purpose of this guide is to provide an introduction for customers who are new to the IBM Cloud environment and would prefer a quick start format versus more detailed documentation. Two sample configurations help you through the ordering process to the start of the SAP installation. The first configuration sample is the smallest one possible a single node 32 GB RAM server. The second is an advanced configuration of two nodes, a 32 GB RAM server and a 256 GB RAM server with an external storage configuration. The disk layout might vary if you do not choose the same options in the examples. The sample layouts may not be your preferred layout; the purpose is to show you two possibilities if you are not experienced with the Linux operating system. Note that you can find an example of how to attach external storage to your provisioned server under Provisioning external storage to your server. IBM has unified their SoftLayer, IBM Bluemix, and IBM Cloud offering solutions, making the SoftLayer and Bluemix infrastructures synonymic for the IBM Cloud IaaS offering. See for more information. 4 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

5 Installing a 32 GB server single-node Order your 32 GB server 1. Open a browser window, enter and click the Log in with IBMid link. Figure 1. SoftLayer log in dialog box 2. Enter your IBMid or and click the Continue button. 3. Enter your Password and click the Sign in button. 4. Click the Devices icon on the Account Summary page. Figure 2. Device icon 5. Click the Monthly link under Bare Metal Servers on the Devices page. Figure 3. Bare metal servers monthly link The Server List dialog box will appear. Copyright IBM Corp All rights reserved. 5 without the prior written permission of IBM.

6 6. Click the hyperlink under STARTING PRICE PER MONTH to select server BI.S1.NW32. Figure 4. Hyperlink to Configure/Order page 7. Enter the number of servers you are ordering in the Quantity field. 6 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

7 Figure 5. Configure/Order page Server, RAM and Hard Drives will default based on your server selection and cannot be changed. 8. Select TOR01 for Data Center. The list of data centers depends on product availability within a particular data center. 9. Select Red Hat Enterprise Linux for SAP Business Application 6.X as your Operating System. 10. Under Hard Drives, select a second 2 TB SATA disk, create a RAID storage group of RAID1 from both disks, and choose Linux Basic as the Partition Template. Copyright IBM Corp All rights reserved. 7 without the prior written permission of IBM.

8 11. Select 500 GB for Public Bandwidth. 12. Select 1 Gbps Redundant Public & Private Network Uplinks for Uplink Port Speed. For this sample installation, leave the default values for all other fields. You can consult the SAP NetWeaver Implementation and Operations Guide ( for detailed descriptions of the options. 13. Click the Add to Order button at the end of the scroll. You will be redirected to the Checkout page once your order has been verified. Figure 6. Checkout page 8 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

9 14. Scroll down and enter the values in Table 1 under Advanced System Configuration. Field Backend VLAN Subnet Frontend VLAN Subnet Provision Scripts SSH Keys Hostname Domain Value Select from the drop-down list, for example, tor01.bcr01a.1241 Select from the drop-down list, for example, /26 Select from the drop-down list, for example, tor01.fcr01a.1199 Select from the drop-down list, for example, /27 Defaults to None Add For example, e2e1270 For example, saptest.com Table GB advanced configuration values Figure 7. Advanced System Configuration on the Checkout page 15. Confirm your selections on the Checkout page and click the Cloud Service terms checkbox on the right-hand side of the page. Copyright IBM Corp All rights reserved. 9 without the prior written permission of IBM.

10 Figure 8. Cloud Service terms checkbox 16. Click the Submit Order button on the right-hand side of the form. You will be redirected to a page with your order number. You can print the page because it is also your order receipt. In addition, you will receive a confirmation with the subject Your IBM Cloud Order ## has been approved with ## being your order number. 10 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

11 Once the order is submitted, the server will, depending on your order, be available for use within one to four hours. You can check the Device Details screen on the main Customer Portal page (Devices > Device List) for a status of the provisioning steps. Click your device s hostname to see its status (Figure 9). Figure 9. Device provisioning status See Preparing your server for the SAP installation (32 GB) once your server has been provisioned. Copyright IBM Corp All rights reserved. 11 without the prior written permission of IBM.

12 Preparing your server for the SAP installation (32 GB) A public IP is being used for remote access, which means you can connect to your server through an ssh client (for example, putty on Microsoft Windows). Use the public IP address displayed in the Device List for your device. The root password for your server is also displayed; be sure to click the Show Password checkbox to see it. Figure 10 Device List - find password Partitioning and file systems For the single-node example, a server with one logical disk (on RAID1) was ordered. There is one mirrored disk appearing in the operating system (OS) with one large root filesystem equal to the total size of disk (with some space used for /boot). The following is just one possible approach for a layout. For production use, you may want to follow the sizing information for your system as other layouts may better cater to your needs or SAP requirements. Below, the three directories required for the SAP installation; /usr/sap, /sapmnt and /db2 have been created: [root@e2e1270 ~]# mkdir /sapmnt [root@e2e1270 ~]# mkdir /usr/sap [root@e2e1270 ~]# mkdir /db2 In regard to storage, the server is now prepared for further installation steps. Refer to RPM package prerequisites to continue with your SAP installation. The information within it will help make graphical access to your server easier. 12 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

13 Installing a 256 GB and a 32 GB server in a three-tier setup Following is a more complex scenario using a 32 GB server as the SAP NetWeaver application server and a 256 GB server as the database server. External storage will also be provisioned as backup space for the database for both archived log files and online full backups. Order your servers for a three-tier installation Follow the steps in Order your 32 GB server to order the SAP NetWeaver application server. The following steps will guide you through ordering the database server. 1. Open a browser window, enter and click the Log in with IBMid link. Figure 11. Login dialog box 2. Enter your IBMid or and click the Continue button. 3. Enter your Password and click the Sign in button. 4. Click the Devices icon on the Account Summary page. Figure 12. Device icon Copyright IBM Corp All rights reserved. 13 without the prior written permission of IBM.

14 5. Click the Monthly link under Bare Metal Servers on the Devices page. Figure 13. Bare metal servers monthly link The Server List dialog box will appear. 6. Click the hyperlink under STARTING PRICE PER MONTH to select server BI.S1.NW256. Figure 14. Hyperlink to Configure/Order page 14 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

15 7. Enter the number of servers in the Quantity field. SAP NetWeaver on IBM Cloud infrastructure Figure 15. Configure/Order page Server, RAM and Hard Drives will default to predefined values based on your server selection and cannot be changed. 8. Select TOR01 for Data Center. 9. Select Red Hat Enterprise Linux for SAP Business Application 6.X as your Operating System. Copyright IBM Corp All rights reserved. 15 without the prior written permission of IBM.

16 10. Under Hard Drives, select a second 2 TB SATA disk, create an RAID storage group of RAID1 from both disks, and choose Linux Basic as the Partition Template. Continue with the network configuration. 11. Select 500 GB for Public Bandwidth. 12. Select 1 Gbps Redundant Public & Private Network Uplinks for Uplink Port Speed. For this sample installation, leave the default values for all other fields. You can consult the SAP NetWeaver Implementation and Operations Guide ( for detailed descriptions of the options. 13. Click the Add to Order button at the end of the scroll. You will be redirected to the Checkout page once your order has been verified. Figure 16. Checkout page 16 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

17 14. Scroll down and enter the values in Table 2 under Advanced System Configuration: Field Backend VLAN Subnet Frontend VLAN Subnet Provision Scripts SSH Keys Hostname Server1 Domain Server1 Value Select from the drop-down list, for example, tor01.bcr01a.1241 Select from the drop-down list, for example, /26 Select from the drop-down list, for example, tor01.fcr01a.1199 Select from the drop-down list, for example, /27 Defaults to None Defaults to None For example, e2e2690 For example, saptest.com Table 2. Advanced System Configuration values Figure 17. Advanced System Configuration on the Checkout page Copyright IBM Corp All rights reserved. 17 without the prior written permission of IBM.

18 15. Confirm your selections on the Checkout page and click the Cloud Service terms checkbox on the right-hand side of the page. Figure 18. Cloud Service terms checkbox 16. Click the Submit Order button. You will be redirected to a screen with your order number. You can print the screen because it s also your order receipt. Once the order is submitted, the server will, depending on your order, be available for use within one to four hours. You can check the Device Details screen on the main SoftLayer portal page (Devices > Device List) for a status of the provisioning steps. See Preparing your server for the SAP installation (256 GB) once your server(s) has been provisioned. 18 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

19 Preparing your server for the SAP installation (256 GB) A public IP is being used for remote access, which means you can connect to your servers through an ssh client (for example, putty on Windows). Use the public IP addresses that are displayed in the Device List for your device. The root passwords for your servers are also displayed; be sure to click the Show Password checkbox to see them. Figure 19. Device List - find password Partitioning and file systems For the three-tier example, a 256 GB server (database server) with one logical disk (on RAID10) was ordered, as well as a 32 GB server (application server) with one logical disk (on RAID 1). Both servers come with one large root filesystem equal to the total size of disk (with some space used for /boot). For the 32 GB server, follow the steps 1 to 10 in Preparing your server for the SAP installation (32 GB); then continue with steps 11 to 14, but replacing /db2 with /usr/sap /sapmnt and /usr/sap/trans will be created and the network file system (NFS) exported from the database server, which will also keep the Advanced Business Application Programming (ABAP) SAP Central Service (ASCS) instance. The following is just one possible approach for a layout. For production use, you may want to follow the sizing information for your system as other layouts may better cater to your needs or SAP requirements, or you might want to use quotas. The required directories for installing the SAP software will need to be created /sapmnt, /usr/sap and /db2 using the following commands: [root@ e2e2690 ~]# mkdir /sapmnt [root@ e2e2690 ~]# mkdir /usr/sap [root@ e2e2690 ~]# mkdir /db2 The server is now prepared for further installation steps in regard to storage. See Network and NFS considerations for three-tier setup for a description of the network layout and specific steps for the SAP installation. Copyright IBM Corp All rights reserved. 19 without the prior written permission of IBM.

20 Network and NFS considerations for three-tier setup If you are planning to install a three-tier setup, you need to prepare the network setup accordingly. For the sample setup, a 256 GB database server (named e2e2690) and a 32 GB application server (named e2e1270) were deployed. The database server will also host the ASCS instance. Adding the IPs on the private network to your /etc/hosts will help with upcoming steps and make sure that SAP internal network traffic will go through the right network. Figure 20. Sample of three-tier set up 1. Log in to the machines and find their private network configuration. [root@e2e2690 ~]# ifconfig bond0 bond0 Link encap:ethernet HWaddr 0C:C4:7A:66:2D:A8 inet addr: Bcast: Mask: inet6 addr: fe80::ec4:7aff:fe66:2da8/64 Scope:Link UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets: errors:0 dropped:0 overruns:0 frame:0 TX packets:25491 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes: (18.2 MiB) TX bytes: (3.2 MiB) [root@e2e2690 ~]# ifconfig bond1 bond1 Link encap:ethernet HWaddr 0C:C4:7A:66:2D:A9 inet addr: Bcast: Mask: inet6 addr: fe80::ec4:7aff:fe66:2da9/64 Scope:Link UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets: errors:0 dropped:0 overruns:0 frame:0 TX packets: errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes: (29.7 MiB) TX bytes: (17.7 MiB) 20 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

21 In this example, is the private IP of the database server; it is from one of the IP ranges from RFC You can determine the IP of the application server, too, and add both IPs to both servers /etc/hosts. ~]# cat /etc/hosts localhost.localdomain localhost e2e2690.saptest.com e2e e2e2690-priv e2e1270-priv On e2e1270 add the two last lines, too. 2. Install NFS software nfs-utils on both servers. ~]# yum install nfs-utils Make sure you start and register the rpcbind and NFS service on the database server. ~]# service rpcbind start ~]# chkconfig nfs on ~]# service nfs start 3. Use NFS to export /sapmnt and /usr/sap/trans from the database server to the application server by adding the required entry to /etc/exports of the database server. /sapmnt/c10 /usr/sap/trans (rw,no_root_squash,sync,no_subtree_check) (rw,no_root_squash,sync,no_subtree_check) The sample value C10 needs to be replaced with the SAP System ID for your SAP system. You must create the directory before you export it. Run the following from the command line of the database server: ~]# mkdir /sapmnt/c10 ~]# mkdir -p /usr/sap/trans ~]# exportfs -a 4. Mount the NFS share on the application server by adding the below entry to its /etc/fstab and mount it from the command-line. e2e2690-priv:/sapmnt/c10 /sapmnt/c10 nfs defaults 0 0 e2e2690-priv:/usr/sap/trans /usr/sap/trans nfs defaults Create the target directories on the application server and mount them: [root@e2e1270 ~]# mkdir -p /sapmnt/c10 [root@e2e1270 ~]# mkdir /usr/sap/trans [root@e2e1270 ~]# mount /sapmnt/c10 [root@e2e1270 ~]# mount /usr/sap/trans Your servers are now prepared to host the components of a distributed SAP installation. See Provisioning external storage to your server for information on how to provision external storage for backup purposes to the database server. Further installation preparation will be performed in Installing your SAP landscape. Copyright IBM Corp All rights reserved. 21 without the prior written permission of IBM.

22 Provisioning external storage to your server External storage can be added to your provisioned server(s) if you want to use it as a backup device or use a snapshot to quickly restore your database in a test environment. In the example, block storage will be used for both archiving log files of the database and online and offline backups for the database. The fastest block storage (4 IOPS per GB) was selected to help assure a minimum backup time. Slower block storage may be sufficient for your needs. External storage is ordered through the Customer Portal. 1. Open a browser window and log in to 2. Click the Log in with IBMid button. 3. Enter your IBMid or and click the Continue button. 4. Enter your Password and click the Sign in button. 5. Select Storage > Block Storage. Figure 21. Storage drop-down menu 6. Click the Order Block Storage link on the Block Storage page. Figure 22. Order Block Storage link 7. Select the specifics for your storage needs. Table 3 contains recommended values, including 4 IOPS/GB for a typical database workload. Field Select Storage Type Location Select Storage Package Value Endurance Data center where your device is located. 4 IOPS/GB 22 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

23 Select Storage Size Specify Snapshot Space Size Select OS Type Table 3. Recommended values for block storage Make your selection based on your workload needs. 0 GB Linux Figure 23. Ordering block storage (Endurance) page 8. Click the Continue button. 9. Click the I have read the Master Service Agreement checkbox and click the Place Order button. Copyright IBM Corp All rights reserved. 23 without the prior written permission of IBM.

24 Figure 24. Placing order for block storage 10. Click the Actions drop-down menu to the right of your LUN and select Authorize Host to access the provisioned storage. Figure 25. Block Storage page 11. Select Devices; the Device Type will default to Bare Metal Server. Click the Hardware drop-down menu and select the hostnames of your devices. 24 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

25 Figure 26. Authorizing your hosts for storage 12. Click the Submit button. 13. Check the status of your provisioned storage under Devices > (select your device) > Storage tab. 14. Note the Target Address and iscsi Qualified Name (IQN) for your server (iscsi initiator) as well as the username and password for authorization with the iscsi server. You will need that information in the following steps. Now you would follow the steps in Mounting Block Storage volumes on Linux under html#connecting-to-mpio-iscsi-luns-on-linux to make your storage accessible from your provisioned server. Copyright IBM Corp All rights reserved. 25 without the prior written permission of IBM.

26 In the sample deployment, the data retrieved from the Storage tab was Target IP: IQN: iqn com.softlayer:sl01su h User: SL01SU H Password: EtJ79F4RA33dXm2q 1. Enter the following based on the retrieved information: ~]# cat /etc/iscsi/initiatorname.iscsi InitiatorName=iqn com.softlayer:SL01SU H An existing entry might have to be replaced in /etc/iscsi/initiatorname.iscsi. 2. Add the following lines to the bottom of /etc/iscsi/iscsid.conf: ~]# tail /etc/iscsi/iscsid.conf # it continue to respond to R2Ts. To enable this, uncomment this line # node.session.iscsi.fastabort = No node.session.auth.authmethod = CHAP node.session.auth.username = SL01SU H node.session.auth.password = EtJ79F4RA33dXm2q discovery.sendtargets.auth.authmethod = CHAP discovery.sendtargets.auth.username = SL01SU H discovery.sendtargets.auth.password = EtJ79F4RA33dXm2q 3. Replace the username and password values (in italics) with those that you noted during the last step of the previous section 4. Discover the iscsi target by entering the following: [root@e2e2690 ~]# iscsiadm -m discovery -t sendtargets -p " " :3260,1031 iqn com.netapp:tor :3260,1032 iqn com.netapp:tor Set the host to automatically log into the iscsi array [root@e2e2690 ~]# iscsiadm -m node -L automatic 6. Install and start the multipath daemon. [root@e2e2690 ~]# yum install device-mapper-multipath [root@e2e2690 ~]# chkconfig multipathd on [root@e2e2690 ~]# service multipathd start 26 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

27 After completing all the commands in Mounting Block Storage volumes on Linux, another LUN will appear in the multipath output. ~]# multipath -ll 3600a f a42 dm-9 NETAPP,LUN C-Mode size=500g features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw -+- policy='round-robin 0' prio=50 status=active `- 10:0:0:169 sde 8:64 active ready running `-+- policy='round-robin 0' prio=10 status=enabled `- 9:0:0:169 sdf 8:80 active ready running You can now use the multipath device as you would use any disk device. A device path will appear under /dev/mapper/3600a f a42. Take the sample, /etc/multipath.conf from Appendix A and create it accordingly on your server. Be aware that special characters or DOS-like carriage returns and line-feed entries wrongly transferred from the document might lead to unexpected behaviour. Make sure you have an ASCII Unix file after copying the contents. Adapt the multipath block from /etc/multipath.conf to create an alias of the path to access the device under /dev/mapper/mpath1. multipaths { multipath { wwid 3600a f a42 alias mpath1 } } 5. Restart multipathd; you can now create the /backup filesystem and mount on the block device. [root@e2e2690 ~]# service multipathd restart [root@e2e2690 ~]# mkfs.ext4 /dev/mapper/mpath1 [root@e2e2690 ~]# mkdir /backup [root@e2e2690 ~]# mount /dev/mapper/mpath1 /backup 6. Check the file systems on both servers; you should see output like the following: [root@e2e1270 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 879G 1,5G 833G 1% / tmpfs 16G 0 16G 0% /dev/shm /dev/sda1 248M 63M 173M 27% /boot /dev/sdb2 849G 201M 805G 1% /usr/sap db2690-priv:/usr/sap/trans db2690-priv:/sapmnt/c10 165G 59M 157G 1% /usr/sap/trans 165G 59M 157G 1% /sapmnt/c10 Copyright IBM Corp All rights reserved. 27 without the prior written permission of IBM.

28 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 549G 2,3G 519G 1% / tmpfs 127G 0 127G 0% /dev/shm /dev/sda1 248M 63M 173M 27% /boot /dev/mapper/mpath1 493G 70M 468G 1% /backup /dev/mapper/datavg-datalv 1,2T 71M 1,1T 1% /db2 /dev/mapper/datavg-saplv 165G 60M 157G 1% /usr/sap /dev/mapper/datavg-sapmntlv 165G 60M 157G 1% /sapmnt If you install an SAP NetWeaver-based SAP application on DB2, you must create subdirectories under /backup owned by the database admin user (db2sid) for full backups and archived log files. For automatic archiving of the log files, you will want to set LOGMETH1 in your DB2 database. Refer to the DB2 documentation ( doc/doc/c html) for details: 28 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

29 Installing your SAP landscape RPM package prerequisites An SAP installation requires certain prerequisites with regards to the packages installed on the OS and the OS daemons running. Please refer to the latest installation guides and support notes from SAP for an up-to-date list of these prerequisites. As of the writing of this guide, two additional packages were required for an SAP NetWeaver installation: compat-sap-c++: Achieves compatibility of the C++ runtime with the compilers used by SAP uuidd: Maintains OS support for the creation of UUIDs 1. Check if uuid daemon (uuidd) is installed. If it s not, install and start it. [root@e2e2690 ~]# rpm -qa grep uuidd [root@e2e2690 ~]# yum install uuidd [root@e2e2690 ~]# chkconfig uuidd on [root@e2e2690 ~]# service uuidd start 2. Follow SAP note and install package compat-sap-c++ and create a specific soft-link, which is required by the SAP binaries. [root@e2e2690 ~]# yum install compat-sap-c++... [root@e2e2690 ~]# mkdir -p /usr/sap/lib [root@e2e2690 ~]# ln -s /opt/rh/sap/lib64/compat-sap-c++.so /usr/sap/lib/libstdc++.so.6 Download your SAP software Log in to the SAP Service Marketplace ( and download the required digital versatile discs (DVDs) to a local share drive and then transfer them to your provisioned server. Another option is to download the SAP Software Download Manager, install it on your target server and directly download the DVD images to the server. See for more information on the SAP Software Download Manager. Note that you will need an S-User ID and the Download Software authorization when downloading the DVDs from the SAP Service Marketplace. See if you need to request an S-User ID. Preparation for SAP s Software Provisioning Manager (SWPM) graphical user interface (GUI) Depending on your network bandwidth and latency, you may want to run the SAP SWPM GUI remotely in a virtual network computing (VNC session). Another option is to have the GUI running locally and connect to SWPM on the target machine. For the second option, please consult the SWPM documentation; the first option is demonstrated below. This option installs a VNC server, which might not be in line with hardening your operating system. You will want to make sure you are meeting your security measures. Please refer to the VNC documentation to get an overview on its functionality in case you are not familiar with it. Copyright IBM Corp All rights reserved. 29 without the prior written permission of IBM.

30 1. Use the following command to install a VNC server, an X11 window manager and a console tool to run SWPM s GUI in a remote session. [root@e2e2690 ~]# yum install tigervnc-server... The command in step 1 will install several dependent packages on your server. Next, you will need an X11 window manager the smallest, lightest and oldest of which is twm; it is included in every Linux distribution. 2. Use the following command to install the window manager. [root@e2e2690 ~]# yum install twm 3. Install a terminal emulator (e.g., xterm): [root@e2e2690 ~]# yum install xterm 4. Start the VNC server from the command-line: [root@e2e2690 ~]# vncserver You will now require a VNC client program; there are multiple implementations available for all operating systems at no cost. Typically, you will need port 590X (where X is the number of the servers running, starting at 1) to be accessible from your client. If you connect to your server s public IP, you will see a screen similar to Figure 27. You might have to start an xterm from the background menu of twm. You can now start SWPM (sapinst) from the xterm. Figure 27. Connecting to the server s IP 30 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

31 Installing SAP software After downloading the installation media, follow the standard SAP installation procedure documented in the SAP installation guide for your SAP version and components, and the corresponding SAP notes. You can start SAP SWPM from the xterm, and execute the installation steps. Figure 28 shows the SAP SWPM for a standard installation. Figure 28. SAP SWPM Figure 29 provides the steps for a three-tier setup. Begin by selecting Distributed System and execute the first two steps in the list shown in Figure 29 on the database server. The third step can be executed on the application server(s). Make sure that you use the private addresses for the ASCS and the database hostnames during installation of the application servers. This will assure that network traffic between the application server and ASCS, or database, will path through the private network and not through the public network. Copyright IBM Corp All rights reserved. 31 without the prior written permission of IBM.

32 Figure 29. SAP SWPM 32 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

33 Appendix A Following is a sample multipath.conf for Red Hat 6.X and NetApp-based iscsi LUNs. defaults { user_friendly_names no max_fds max flush_on_last_del yes queue_without_daemon no dev_loss_tmo infinity fast_io_fail_tmo 5 } # All data under blacklist must be specific to your system. blacklist { wwid "SAdaptec*" devnode "^hd[a-z]" devnode "^(ram raw loop fd md dm- sr scd st)[0-9]*" devnode "^cciss.*" } devices { device { vendor "NETAPP" product "LUN" path_grouping_policy group_by_prio features "3 queue_if_no_path pg_init_retries 50" prio "alua" path_checker tur failback immediate path_selector "round-robin 0" hardware_handler "1 alua" rr_weight uniform rr_min_io 128 } } # Sample multipath.conf multipaths extension for human readable device paths: multipaths { multipath { wwid XXXXYYYZZZ alias pathname } } Copyright IBM Corp All rights reserved. 33 without the prior written permission of IBM.

34 Trademarks IBM, the IBM logo, ibm.com, DB2 and Bluemix are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at SoftLayer is a registered trademark of SoftLayer, Inc., an IBM Company. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. This document is current as of the initial date of publication and may be changed by IBM at any time. Not all offerings are available in every country in which IBM operates. It is the user s responsibility to evaluate and verify the operation of any other products or programs with IBM products and programs. THE INFORMATION IN THIS DOCUMENT IS PROVIDED AS IS WITHOUT ANY WARRANTY, EXPRESS OR IMPLIED, INCLUDING WITHOUT ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT. IBM products are warranted according to the terms and conditions of the agreements under which they are provided. Actual available storage capacity may be reported for both uncompressed and compressed data and will vary and may be less than stated. Copyright International Business Machines Corporation All rights reserved. This document may not be reproduced in whole or in part without the prior written permission of IBM. Note to US Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. 34 Copyright IBM Corp All rights reserved. without prior written permission of IBM.

35 Copyright IBM Corp All rights reserved. 35 without the prior written permission of IBM.