Download PDF - IBM Redbooks

More documents

Recommendations

Info

► SAP on DB2 9 for z/OS: Implementing Application Servers on Linux for System z, SG24-6847 See the following chapters: – Chapter 2, “Planning for SAP on Linux on System z” – Chapter 3, “Preparing the System z environment” SAP database server planning for DB2 and the zEnterprise System With the SAP landscape designed, review the system design and the capacity layout: 1. Review the sizing document from IBM Techline or the documentation from the team that suggested the System z hardware configuration. 2. Determine the following resource requirements: – Number of General Purpose Engines – Number of System z Integrated Information Processor (zIIP) Engines – Number of Integrated Facility for Linux (IFL) Engines, if SAP parts will run on Linux on System z – Internal Coupling Facility (ICF) Engines, if sysplex is in the plan – Central Storage (memory) per SAP server and per LPAR Collaborate with the people who made the initial sizing and system layout. If their input is close to the actual environment, only minor changes are required. 3. Review the hard disk drive (storage) requirements for NetWeaver 7: – Minimum of 135 GB is required for the initial installation or copy of an SAP NetWeaver AS instance using Unicode. – Disk storage for the SAP database varies by solution. Contact your SAP Basis administrator about the requirements for the installation. See also “System z storage planning” on page 160. 4. Optional: If possible, optimize the ISV Sizing estimates based on the following criteria: – Sizing SAP installations – Customer experiences – Unicode – DB2 Hardware Compression – Copies from FlashCopy – Cloning – Growth Factor – Storage Capacity Utilization Then recheck steps 2 and 3. As a good practice, do this sizing recheck a couple of months after going into production. Use the IBM SAP Insight Report to analyze SAP workload behavior. Find more information about IBM Insight, see the “IBM Insight for SAP - Utility for anyone running SAP” page at: http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS381 SAP NetWeaver Application Server planning SAP NetWeaver ASs are the workhorses of an SAP infrastructure. An SAP workload shared between SAP database server and application server instances can have a distribution ratio from 1:1 (SAP Business Warehouse applications) up to 1:5 (SAP Sales and Distribution type 154 Running SAP Solutions with IBM DB2 10 for z/OS on the IBM zEnterprise System
applications). SAP NetWeaver AS runs all the SAP application logic and processes, including the following examples: ► SAP work dispatchers ► SAP ABAP work processes ► SAP Java server processes ► SAP Central Services SAP NetWeaver AS also runs other SAP application logic and processes that have less impact on the planning process. Depending on the SAP application, your application server might run either ABAP processes, Java processes, or both. With SAP NetWeaver 7.0, the enqueue server and the enqueue replication, message, and gateway servers are broken out and run on a new stand-alone Central Services instance. This concept resolves the single-point-of-failure problem of the former SAP enqueue server, which then was part of the first or primary instance. For SAP installations, consider placing this central service on the z/OS platform and including it in the sysplex failover plan. The SAP project team, specifically, the SAP Basis administrator, provides basic layout and sizing documentation. The team has this information based on previous sizings to allocate budgets and procure the hardware. At this point, the hardware and operating system platform for application serving has been determined. To design your application server layout and prepare the platforms for the SAP installation: 1. Review the sizing document from IBM Techline or the documentation from the team that suggested the System z hardware configuration. 2. Determine the following resource requirements: – Application server processor power per application and application server The sizing output determines the processing power needed. You can distribute it across several application servers according to design and platform capacity. In most cases, the application server instance needs two processors (or cores) to permit parallelism of threads. Increasing the number of cores is not always beneficial and depends on the SAP application. The processors do not need to be physical. You can define virtual processors and thus share the physical ones with several SAP NetWeaver AS instances. – The number of application servers required per application The number depends on the selected hardware, virtualization capabilities of the platform to host several AS, and availability requirements. For production, SAP encourages the use of two application server instances per application at a minimum. – Memory (random access memory (RAM)) requirements per application server instance You can get this information from the Quick Sizer or Techline output. Allow for a generous amount of memory. – Disk storage requirements per application server The minimum storage for the application file systems is 17 GB for the primary server instance, plus 2 x RAM, or a 20-GB minimum for the swap files, plus 4.4 GB per installation media DVD. Allow sufficient space because the systems have a trend for dynamic growth. 3. Determine the location of the SCS instance In the Installation - SAP NetWeaver 7.3 Systems guide (login required), SAP recommends that you run the SCS in the z/OS UNIX System Services environment of the database server hosting LPAR. You must run the SCS in an HA setup that permits SCS to Appendix B. Planning, preparing, and implementing the SAP landscape 155
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 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 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 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 220 and 221:
206 Running SAP Solutions with IBM
Page 222:
Running SAP Solutions with IBM DB2
show all

Download PDF - IBM Redbooks

Create successful ePaper yourself

Delete template?

Save as template?