Download PDF - IBM Redbooks

More documents

Recommendations

Info

Typical roles and tasks for system administrators and operations Creating and managing an SAP infrastructure and application involves the teamwork of many specialists. On the business side are the business management and operations people, who focus on business processes, business applications, and services for users. The LOB organization defines the content and services provided by the SAP solutions and creates the implementation master plan. The skills of SAP business process management consultants, SAP application developers, and SAP application administrators are typically required. For a successful SAP implementation, and ultimately for the operation, the LOB must work hand-in-hand with IT management and the IT center. IT specialists set up and manage the server and network infrastructure, manage the data and storage, and maintain and keep the infrastructure up to date. Another role is the SAP Basis consultants or administrators who plan, install, and maintain the SAP software and system on an infrastructure that is provided. Basis consultants are the interface between the IT technicians and the business administration specialist. They understand the SAP plans and requirements of the LOB and work with the IT specialists on planning, preparing, and installing the systems. The following types of roles are within the IT staff: System programmers Manage the server and storage layout. They also plan and manage the operating systems and monitor their operation. Database administrators Manage the data and information. The database is the core component of an SAP system, where all application and business information are located. SAP is a multi-user, multi-server system that requires a balanced and fast network. IT networking staff (with the help of the SAP Basis consultant) Must understand the SAP networking requirements and how to create a reliable network. Security officer and administrator Ensures that important SAP systems are safe. The application has its own security management for application access. However, protection of the infrastructure is subject to the implementer and operations. Table B-1 lists the most common roles of IT staff in an SAP context. Depending on skills and organization, the roles described are not always distinct individuals. Your organization might want to split roles among several people or combine several roles into one role. Define and communicate who is responsible for which part of the plan. A clear responsibility structure helps the project team to assign tasks and coordinate the work. Table B-1 Roles and responsibilities of system administrators in an SAP project Administrator role Administrative and operations tasks Application server dependent AIX administrator Optional: SAP NetWeaver Application Server (SAP NetWeaver AS) environments on AIX DB2 DBA SAP databases, table spaces, and so on DB2 systems programmer Performs the DB2 installation, ZPARMS, basic configuration for SAP, backup, and disaster recovery 146 Running SAP Solutions with IBM DB2 10 for z/OS on the IBM zEnterprise System If AIX application server
Administrator role Administrative and operations tasks Application server dependent Linux x86 administrator Optional: Installs and maintains Linux servers for SAP NetWeaver AS Network administrator Manages the application to the database server, virtual IP address (VIPA), network security, firewalls, monitoring, and disaster recovery SAP Basis administrator Performs the NetWeaver and SAP installation, maintenance, SAP RFC, transport, SAP security, Computing Center Management System (CCMS) customization, and so on Security administrator Handles SAF/RACF, DB2 security, IBM Tivoli Directory Server Lightweight Directory Access Protocol (LDAP), and SAP security interactions Storage administrator Manages the storage layout, DASD mapping, IBM FICON®, FlashCopy, archiving, restore, and disaster recovery z/OS UNIX System Services administrator Manages the SAP Network File System (NFS) shared libraries and SCS Collecting and reviewing the project requirements If the application server is on x86 Linux Windows administrator Optional: Manages SAP NetWeaver AS environments on Windows If the AS is on Windows z/OS capacity planning and performance administrator z/OS systems programmer Linux on System z administrator Handles workload management, System Management Facility (SMF), and monitoring Sets up and maintains LPARS, coupling facility (CF) and sysplex, SMS, z/OS, z/VM, and high availability Optional: Installs and maintains Linux on System z partitions and libraries for SAP NetWeaver AS If the AS is on Linux on System z Your LOB team must be able to provide the general project plan and documentation. Collect as much technical information and as many requirements of the project as possible. Your LOB or SAP consulting team must provide the following information: ► The general project plan including the milestones ► The planned SAP system landscape ► The SAP application modules that are involved ► Detailed sizing information, including storage ► Growth projections or estimates ► Key plan dates for infrastructure provision and SAP system provisions (development, quality assurance (QA) or test, or production) ► Service-level requirements ► Business continuity requirements ► Security requirements ► Data management and archiving ► Disaster management Appendix B. Planning, preparing, and implementing the SAP landscape 147
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 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:
200 Running SAP Solutions with IBM
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

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

Delete template?

Save as template?