Download PDF - IBM Redbooks

More documents

Recommendations

Info

Figure B-4 illustrates how SAP uses stored procedures in DB2. SAP Application Server EXEC SQL CALL PROCX DB2 address space DBM1 Propagate stored procedure to corresponding WLM application environment for execution WLM work queue WLM Figure B-4 WLM enabled stored procedures flow for SAP WLM established DB2 stored procedure address space Preparing SAP NetWeaver Application Server platforms The SAP NetWeaver AS runs on various hardware and operating systems. A selection of those platforms is certified and supported by SAP to be combined with a database server on DB2 10 for z/OS. This section describes the preparations for Linux on System z, running SUSE SLES 11 or Red Hat 6. Preparing for SAP NetWeaver AS on Linux on System z SAP NetWeaver ASs can run on Linux on System z in dedicated LPARs or as operating system guests under a hosting z/VM. Because the creation of an LPAR dedicates system resources to the hardware region, it is similar to installing a physical server. Unified Resource Manager simplifies the task, but the result is still a bit inflexible. Most clients prefer the advantages and flexibility of a virtualized environment. For simplification reasons, the following sections focus on that setup, assuming that z/VM is the host for the application servers on Linux on System z and managing a dedicated LPAR. For more information, see the following SAP Notes (see “SAP Notes” on page 198 for links to each one): ► SAP Note 81737 - z/OS, DB2, and APAR List ► SAP Note 1452070 - SAP on Linux for IBM System z and z/VM ► SAP Note 746299 - Recommended settings for Linux on System z JVM ► SAP Note 563060 - DB2/390: Kernel Parameter for Linux on zSeries ► SAP Note 941735 - SAP Memory Management for 64-bit Linux ► SAP Note 892818 - Application Servers on Linux for zSeries: Settings ► SAP Note 1263782 - Recommended Settings for HiperSockets ► SAP Note 1495160 - SAP JVM as replacement for Partner JDKs ► SAP Note 1367498 - SAP JVM installation prerequisites: SAP JVM 1.4.2, ► SAP Note 1310037 - SUSE Linux Enterprise Server 11: Installation Notes ► SAP Note 1496410 - Red Hat Enterprise Linux 6.x: Installation and Upgrade ► SAP Note 1465174 - DB2-z/OS: Overview of Linux on System z JVM for NetWeaver 6.40 and 7.0 182 Running SAP Solutions with IBM DB2 10 for z/OS on the IBM zEnterprise System PROCLIB PROCX
Preparing System z hardware for application servers on Linux on System z SAP NetWeaver ASs that run on Linux on System z require a separate LPAR setup to host them. Linux application servers on System z are best run in a virtualized environment where the virtualization layer is implemented by z/VM. z/VM can also host a z/OS guest and a DB2 for z/OS guest environment for the SAP database server. However, it is not supported (nor tested) by SAP, at least not for production systems. For z/VM as the Linux on System z host, the following design criteria apply: ► Separate the z/VM LPARS for production and nonproduction. z/VM is a stable and reliable host environment, so that you can host all your application servers in one LPAR. For improved availability and performance management, separate the production and nonproduction environments. In this case, you need at least two z/VM LPARs in your landscape. ► For extended HA, implement two parallel LPARs. Consider that you have the correct SAP and operating system software release and version staging process in place, and your SLAs do not require rolling maintenance. In this case, you can have one hosting LPAR for a group of production application servers. You might have extended requirements for HA, which might justify a Parallel Sysplex for your database server. In this case, consider implementing more than one production z/VM LPAR with parallel application server instances distributed across them, which also permits rolling maintenance of the application server platforms and software. The zEnterprise LPAR that hosts the z/VM must provide sufficient resources to all of the application server workloads that will run in the LPAR. The following resources are required: ► Processor power Techline sizing or your zEnterprise might have calculated the number of IFL processors for your system that are required to run the anticipated SAP workload. Assign these IFLs to the LPARs you are going to populate. If your test, development, and QA staging instances are on the same zEnterprise central electronics complex (CEC), you can share the IFLs across the LPARs. IFL sharing accommodates some load balancing between the environments. Later in the system lifecycle, you can reconsider sharing and assign fixed pools to the groups of servers. ► Processing memory, also called real storage Your LPAR needs enough processing memory to host all servers. This memory is the sum of all server images hosted. z/VM manages memory allocation for its guests and ensures that each guest has a private, fully isolated virtual memory region. z/VM can manage more virtual memory for its clients than real memory. Use care with memory overcommitment because it might imply swapping to disk by z/VM and can degrade performance. Use the following formula to calculate LPAR memory: 0 � allGuests VirtualMemory@zLinuxGuest zVM + FastPaging + ------------------------------------------------------------------------------------------------------------ = LPAR OvercommitRatio Where: z/VM Memory to run the z/VM host; start with 4 GB. FastPaging A minimum of 2 GB z/VM expanded memory to run as a high-speed paging device. Appendix B. Planning, preparing, and implementing the SAP landscape 183
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 198 and 199: OvercommitRatio Virtual Memory vers
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?