Download PDF - IBM Redbooks

More documents

Recommendations

Info

2.1 SAP NetWeaver composition 2.1.1 SAP system 2.1.2 SAP instance SAP NetWeaver is an integrated stack of SAP technology products. Figure 2-1 illustrates a simplified version of the SAP technology stack. This technology stack is also known as the SAP computing platform or the SAP solution stack. It refers to the technology foundation (computing infrastructure) and the SAP technical installation on which all of the development activity and productive operations rely. Figure 2-1 SAP technology stack ©SAP AG, 2011 An SAP NetWeaver Application Server (SAP NetWeaver AS) is made up of specific entities called a system and an instance. The following sections provide a brief description of an SAP NetWeaver system and instance and introduce frequently used SAP terms. An SAP system is an installed software system that consists of several software components, physical and logical server instances, the network, and one or more databases. An SAP system is identified by a unique qualifier (SAPSID) and provides a set of functions as part of an SAP solution. The three-letter SAPSID can be used as a high-level qualifier for schemas of the SAP data model inside the database. An SAP system consists of SAP instances. An SAP instance defines a group of resources (such as memory and work processes) provided by a server. Different SAP instances are available as described in the following sections. Application server instances An application server instance is an administrative unit that puts together components of an SAP system running on one physical host. Application server instances provide the actual 10 Running SAP Solutions with <strong>IBM</strong> DB2 10 for z/OS on the <strong>IBM</strong> zEnterprise System
data processing functions of a system and offer the corresponding services. Instances are started, stopped, and monitored as one unit. Multiple instances (belonging to the same system or to different systems) can be on one host. An instance can be uniquely identified by the host name and a two-digit instance number. In this section, each SAP NetWeaver AS instance is described. Primary application server instance Each SAP system must have at least one application server instance (central instance) for either an Advanced Business Application Programming (ABAP) or a Java system. As shown in Figure 2-2, this requirement can be realized by one application server instance that contains central services (message and enqueue server) and the work processes that run the user sessions. This type of setup variant is the classic SAP central instance. For scalability and manageability reasons, especially in the context of high availability, a different mapping might be more attractive. For example, to establish a separate instance for messaging, an enqueue server (called a central services instance) and several dialog instances serving the user sessions can be helpful. The number of dialog instances can be adapted to the workload that will be processed. SAP Central Instance SAP Central Services Instance SAP Dialog Instance Message Server Message Server Figure 2-2 Setup variants of SAP system instances Enqueue Server Enqueue Server Work Work Work Work Process Process Process Work Work Work Work Process Process Process ©SAP AG, 2011 Central services instance SAP Central Services (SCS) instances contain components that are unique to the SAP system (see 2.1, “SAP NetWeaver composition” on page 10). Because they run on only one server at a time, these services must be independent and moveable, so that they can be taken over by another server if a server fails. This takeover is not apparent to the SAP applications and its users. The application resources are stored in the enqueue table, which is explained more in 2.6.2, “Enqueue replication server instance” on page 19. The traditional SAP central instance was redesigned into independent stand-alone components that are grouped together and operate as SCS. Even though the components can be started, stopped, and recovered independently, they share an instance directory and an instance profile. If a component fails, the recovery is more efficient within this setup. Chapter 2. Architectural overview of SAP NetWeaver with DB2 for z/OS 11
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 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:
Page 156 and 157:
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 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 214 and 215:
Page 216 and 217:
DSNACCOX usage 45 dual-log LG1 and
Page 218 and 219:
untime environment 13 software 162
Page 220 and 221:
Page 222:
Running SAP Solutions with IBM DB2
show all

Download PDF - IBM Redbooks

Create successful ePaper yourself

Delete template?

Save as template?