Download PDF - IBM Redbooks

More documents

Recommendations

Info

OvercommitRatio Virtual Memory versus Real Memory ratio; as a rule of thumb, see the following initial values: – Productive application server: Less than 1.5:1 (1.4:1 is a good start) – Non-productive application server: Approximately 1.5:1 – Sandbox systems: 2.5:1 VirtualMemory@zLinuxGuest 4 - 8 GB for initial virtual memory per Linux guest. Note the following minimum memory: – 4 GB for each nonproduction guest – 6 GB for each production guest, except BW – 8 GB for each production BW guest See your sizing documents for the estimated memory requirements of each application server instance. For more information, consult your experienced SAP Basis person. See also Installation Guides - SAP NetWeaver 7.3 and the Planning Guide SAP on IBM DB2 for z/OS, version 2.50 - 2011-10-01. ► Disk storage In addition to the storage that z/VM must run, the z/VM host also handles all the disk space for the Linux on System z guests and SAP NetWeaver AS application. The exception is the zFS/HFS/NFS shared directories, which are shared across LPARS. If you plan to run the SCS instance in the z/OS LPAR, the shared directories must be in the z/OS LPAR and NFS, mounted to the application servers. See 3.2.4.2.2 about SAP Directory Structure in the Planning Guide SAP on IBM DB2 for z/OS, version 2.50 - 2011-10-01. The z/VM 6.1 host requires five 3390-9 volumes: – 1 RES volume – 1 SPOOL volume – 3 PAGE volumes z/VM also manages the Linux on System z DASD per application server, which is the disk space for the libraries, and system and application work files of the server. For installation of SAP ECC 6.0, use the following sizes: – 1.2 GB of temporary installation disk space – 4.3 GB of temporary installation disk space for every DVD to be copied locally for the installation – 20 GB or ~2 x Guest Virtual Memory Size: Linux swap space – 7 - 9 GB of local SAP file systems (For SAP recommended sizes, see the Installation Guides - SAP NetWeaver 7.3.) – 6-GB Linux kernel + boot image + logs Confirm the sizes with your Linux on System z provider. Although these sizes are the Linux guest sizes for an SAP ECC installation, other SAP applications have other disk requirements. Monitor the servers as they become more used, and adapt the requirements according to the Installation Guides - SAP NetWeaver 7.3, the experience of your SAP Basis consultant, and your observations. ► Network resources SAP NetWeaver ASs use TCP/IP connections to the SAP database server and database, to the SCS, and to the user network. For Linux on System z, the hosting LPAR has the following requirements: 184 Running SAP Solutions with IBM DB2 10 for z/OS on the IBM zEnterprise System
– HiperSockets local and virtual LAN connections to the database server and SCS instances on z/OS These connections use at least two CHPIDs (HiperSockets LANs) to separate production from nonproduction (up to 16 are allowed) communication. An alternative to HiperSockets is classic LAN connections using OSA or OSD, but you can lose the performance advantages of HiperSockets and place significant load onto the OSA hardware. – OSA communication hardware to connect to the company network Use OSA-2 at a minimum. OSA-3 and OSA-4 promise faster communication. The speed is less critical for SAP user connections, but bandwidth and number of users play a role. If you use OSA or OSD to connect to the SAP database server, a low latency, high-bandwidth hardware is beneficial. – For securing your external communication to the enterprise network, additional hardware for firewalls and encryption (SAP recommended) Preparing the z/VM host SAP supports z/VM 6.1 and 6.2 as a managing host for Linux on System z application servers. Try to use the latest SAP supported z/VM release when you plan a new installation or platform renewal. Similar to DB2 for z/OS, which incorporated many optimizations specific to SAP over the years, z/VM is increasing the role of Linux on System z hosting, which increases the values for SAP NetWeaver ASs. Consider the following best practices from the field: ► Create the LPAR, define the hardware resources, and install the z/VM software according to the z/VM product documentation. ► Calculate and activate z/VM virtual memory, and allocate the paging space according to the z/VM: CP Planning and Administration Manual, SC24-6803: – Minimize paging and swapping. Define the Linux guests as small as possible without having Linux swapping occur on a regular basis. – Do not let Linux on System z perform paging. z/VM is more efficient than Linux on System z if memory is overcommitted. – Monitor Linux on System z paging, and let z/VM page as necessary. – Configure some expanded storage for use by z/VM as a high-speed paging device. (Memory of 2 GB does the job well.) – Calculate DASD page space so that it does not exceed 50% utilization. Use the following formula to calculate the page space: Sum of all virtual guest sizes - (real memory + expanded memory) x 2 – Use multiple swap volumes to avoid I/O bottlenecks. VM paging works best with large and continuous space on volumes of the same type. Consider the 3390-A EAV DASD format, and consider dedicating them to the paging job. Paging DASD must also use parallel FICON channels and the PAV storage access feature to avoid bottlenecks. Striping is advised on a storage level. ► Turn off minidisk caching for swap minidisks on read-only minidisks. The read ratio is not balanced by write path length. Appendix B. Planning, preparing, and implementing the SAP landscape 185
Page 1:
ibm.com/redbooks Front cover Runnin
Page 4 and 5:
Note: Before using this information
Page 6 and 7:
2.10.2 IBM zEnterprise BladeCenter
Page 8 and 9:
System software planning. . . . . .
Page 10 and 11:
Trademarks IBM, the IBM logo, and i
Page 12 and 13:
Maxim Kukarev is a Client Technical
Page 14 and 15:
xii Running SAP Solutions with IBM
Page 16 and 17:
1.1 IBM DB2 on System z and SAP The
Page 18 and 19:
technologies, it provides advanced
Page 20 and 21:
1.2.3 SAP Industry Solutions SAP In
Page 22 and 23:
8 Running SAP Solutions with IBM DB
Page 24 and 25:
2.1 SAP NetWeaver composition 2.1.1
Page 26 and 27:
Consequently, the central instances
Page 28 and 29:
► Data layer. The database instan
Page 30 and 31:
Integration ESB / Connectors Figure
Page 32 and 33:
2.4 Rolling maintenance Within one
Page 34 and 35:
2.7 Database server Another compone
Page 36 and 37:
Metro Mirror Figure 2-7 Metro and M
Page 38 and 39:
2.10.4 zEnterprise Ensemble System
Page 40 and 41:
System p or System x AIX, Linux on
Page 42 and 43:
SAP mixed 3-tier structure The data
Page 44 and 45:
3.1 Features implicitly used by SAP
Page 46 and 47:
3.1.4 Scalability improvements for
Page 48 and 49:
Insert time per row in msec. 500,00
Page 50 and 51:
New tables are automatically create
Page 52 and 53:
3.3 SAP modifications to optimize t
Page 54 and 55:
The solution is the Hybrid DBSL, wh
Page 56 and 57:
Figure 3-5 New DBM1 display Enhance
Page 58 and 59:
- Accumulated wait time for global
Page 60 and 61:
The view shown in Figure 3-8 for th
Page 62 and 63:
3.4.1 IN-list in-memory tables DB2
Page 64 and 65:
With DB2 10, the new access type NR
Page 66 and 67:
2. Ensure that the user who is crea
Page 68 and 69:
4.1 Installing Linux on System z, S
Page 70 and 71:
Installing the server from DVD We i
Page 72 and 73:
Verifying the installation In the I
Page 74 and 75:
Registration: To access the SAP Ser
Page 76 and 77:
Figure 4-4 Support Package list Fig
Page 78 and 79:
lnxsu11:t73adm 64> telnet wtsc59oe
Page 80 and 81:
2. Configure the JCL head. From the
Page 82 and 83:
4.2.2 Considerations for migration
Page 84 and 85:
Figure 4-8 DB2_V10_CHECK report Imp
Page 86 and 87:
4.2.4 Considerations for data shari
Page 88 and 89:
You must make the following changes
Page 90 and 91:
lnxsu11 Figure 4-12 SAP system land
Page 92 and 93:
Product Vendor Type Version SAP Net
Page 94 and 95:
5.1 Functions of Unified Resource M
Page 96 and 97:
5.2 Simplifying management tasks in
Page 98 and 99:
Figure 5-6 DBA Cockpit initial pane
Page 100 and 101:
Figure 5-8 Global Times panel Tip:
Page 102 and 103:
Figure 5-10 Buffer Pools The Buffer
Page 104 and 105:
Table 5-1 highlights the tasks or a
Page 106 and 107:
Tip: To enable the capture of syspl
Page 108 and 109:
Figure 5-14 AIX monitoring data Fig
Page 110 and 111:
► DB2 Network Stats ABAP report (
Page 112 and 113:
3. Enter the perfkit command to sta
Page 114 and 115:
You can also access monitoring data
Page 116 and 117:
Example 5-3 Linux memory utilizatio
Page 118 and 119:
In addition to user resource utiliz
Page 120 and 121:
In a high availability system, ever
Page 122 and 123:
7.1 Classifications of virtualizati
Page 124 and 125:
7.2 Resources to the virtual machin
Page 126 and 127:
112 Running SAP Solutions with IBM
Page 128 and 129:
8.1 Separation of duties for databa
Page 130 and 131:
authority is granted to an entire D
Page 132 and 133:
malicious or careless unauthorized
Page 134 and 135:
After starting each audit policy, D
Page 136 and 137:
8.3 Writing SQL to audit SAP tables
Page 138 and 139:
Example 8-13 shows the audit record
Page 140 and 141:
The client and server perform the f
Page 142 and 143:
Digital certificates: Digital certi
Page 144 and 145:
The following rule conditions are a
Page 146 and 147:
Example 8-24 shows the assigned val
Page 148 and 149: 8.5.3 Reasons for establishing trus
Page 150 and 151: Example 8-31 shows the results of a
Page 152 and 153: From the central log of the SAP sys
Page 154 and 155: 140 Running SAP Solutions with IBM
Page 158 and 159: The SAP implementation process from
Page 160 and 161: Typical roles and tasks for system
Page 162 and 163: Key documentation From the IT and C
Page 164 and 165: Then you see a list of SAP Notes th
Page 166 and 167: SAP Notes The SAP Note system is us
Page 168 and 169: ► SAP on DB2 9 for z/OS: Implemen
Page 170 and 171: participate in the failover automat
Page 172 and 173: As a best practice, use the SAP as
Page 174 and 175: ��
Page 176 and 177: System software planning SAP on the
Page 178 and 179: Software product Part number Commen
Page 180 and 181: Capability Software product Part nu
Page 182 and 183: � Decide which installation optio
Page 184 and 185: c. Disable the IEFUSI exit in membe
Page 186 and 187: 3. Optional: Make the directories a
Page 188 and 189: Additional information: For more in
Page 190 and 191: 11.After finishing the DB2 subsyste
Page 192 and 193: ARC The archive log data sets. CI T
Page 194 and 195: DB2 members of the same data sharin
Page 196 and 197: Figure B-4 illustrates how SAP uses
Page 200 and 201: ► Set the following z/VM SRM para
Page 202 and 203: ► Separate the SAP private networ
Page 204 and 205: DB2 10 ZPARMS for SAP Important: Yo
Page 206 and 207: - SMS constructs and ACS routines -
Page 208 and 209: Downloading and extracting the web
Page 210 and 211: PI Process Integration PIT point-in
Page 212 and 213: SAP Notes Registration required: To
Page 216 and 217: DSNACCOX usage 45 dual-log LG1 and
Page 218 and 219: untime environment 13 software 162
Page 222: Running SAP Solutions with IBM DB2
show all

Download PDF - IBM Redbooks

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?