Download PDF - IBM Redbooks

More documents

Recommendations

Info

As a best practice, use the SAP as an HLQ in all infrastructure names and files or as a prefix to the HLQ. Table B-1 shows how the SID name is used in DB2 and networking. Example B-1 Naming elements based on an SAP SID of DE1 SAP SID = DE1 DB2 Subsystem Name = SSID = DE11 DB2 Address Spaces: DE11DBM1, DE11IRLM, DE111DIST, DE11MSTR DB2 Group Attach Name: DE1 ICF Catalog Name Examples: DE1DB2.SAPDB2.CATALOG: (alias) DE1 DE1USR.SAPDB2.CATALOG: (alias) DE1U DE1LOG.SAPDB2.CATALOG: (alias) DE11.LOGCOPY1 DE11.LOGCOPY2 DE111.DB2 DE11.ARCHLOG1 DE111.ARCHLOG2 DE1IC.SAPDB2.CATALOG: (alias) DE1IC DB2 Connect Userid for ABAP: DE1ADBC DB2 Connect Userid for Java: DE1JDBC DB2 Schema for ABAP: SAPR3 DB2 Schema for Java: SAPJAVA DB2 host network name: de1db21 Linux on System z Application Server: de1as0 In the next section, you apply the naming schema to the system design and the dependent resources. Applying naming and finishing the system design This section explains how to apply naming and sizing considerations to an example. The example scenario is close to a real implementation on an IBM zEnterprise 196 (z196). Scenario A mid-sized SAP landscape serving a few thousand users is required. The following SAP applications are selected by the LOB team: ► SAP Enterprise Resource Planning (ERP) Central Component (ECC either HCM or FI) ► SRM ► SAP Business Intelligence (BI) ► NetWeaver Portal ► Third-party software integration by using SAP NetWeaver PI The SAP Solution Manager and the SAProuter special server are also required. The client’s IT department wants to run as much of the SAP solution as possible on a zEnterprise System. Therefore, we selected Linux on System z as the application server platform. The LOB has basic requirements toward HA. The client requirement was a data loss of no more than 30 minutes. In a disaster situation, such as a complete site outage for more than one business day, a backup will be up and running within 48 hours. In this case, data loss will be no more than 8 business hours. Table B-3 shows the recovery time objectives. 158 Running SAP Solutions with IBM DB2 10 for z/OS on the IBM zEnterprise System
Table B-3 Recovery objective Type of outage Recovery time objective (downtime) Component failure (hardware, software, and network 2 business hours 30 minutes Total outage is more than 1 day 48 hours 8 hours Recovery period objective (data at risk) Solution By applying Quick Sizer results and the sizing estimate from IBM Techline, we determined that we need a z196-702 with two central processors (CPs), one zIIP for the database server load, and 11 IFLs for the SAP NetWeaver AS load. Additional information: You can find the IBM Sizing and Planning Questionnaire for SAP Solutions at: http://www.ibm.com/support/techdocs/atsmastr.nsf/PubAllNum/PRS261 For more information about using the SAP Quick Sizer, see “Questions for users of the SAP QuickSizer” at: http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS2294 To size the LPARs, give the production instances more memory than the minimum recommended by the Quick Sizer, because clients have experienced that memory proposed by Quick Sizer is conservative. However, development and QA instances can use the Quick Sizer recommendations. Because this system is new, we cannot estimate how much the processor is being used during production. Also the development systems might be more active during the SAP application customization and introduction phase. Therefore, we decided to share the processors between the production, development, and quality assurance instances for now. We might have to adjust the LPAR resources after the system workload settles, which is a good practice, because every client will have an individual SAP workload pattern. In particular, if SAP transactions or jobs were created or changed by LOB consultants, they often affect workload performance. For system recovery, we implement SCS in the z/OS LPAR to decouple it from the application server host. Also, this approach prepares the system if the client implements Parallel Sysplex data sharing and HA later. For data loss protection, use Metro Mirror to back up the DB2 log and data and to enable storage FlashCopy to use the DB2 BACKUP/RESTORE DATABASE utility, point-in-time recovery, and federated synchpointing of the applications. We designed four hosting LPARs: two for the database servers and two for the application servers. One pair of database servers and application servers is dedicated to production. The other pair hosts the development and QA instances. The database server partitions run each DB2 subsystem and one database instance per SAP application instance. Also one SCS instance is available per SAP database server instance in these LPARs. The application server LPARS are managed by z/VM as the host operating system. We have two application servers per production application, and one application per development and per QA application and instance. The exception is the Solution Manager, which has one application server central instance for production and one for QA and development, with no separate SCS servers and no separate QA or development instances. Also the SAProuter is available once per productions and QA or development. Appendix B. Planning, preparing, and implementing the SAP landscape 159
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 168 and 169: ► SAP on DB2 9 for z/OS: Implemen
Page 170 and 171: participate in the failover automat
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 222:
Running SAP Solutions with IBM DB2
show all

Download PDF - IBM Redbooks

Create successful ePaper yourself

Delete template?

Save as template?