Download PDF - IBM Redbooks
Download PDF - IBM Redbooks
Download PDF - IBM Redbooks
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
participate in the failover automation. If you run the database server in shared member<br />
mode on an <strong>IBM</strong> Parallel Sysplex, consider implementing the replicated instance of the<br />
SCS to the same LPAR where the shared failover member resides. You can find the<br />
Installation - SAP NetWeaver 7.3 Systems guide at:<br />
http://service.sap.com/~sapidb/011000358700001259432010E<br />
For a lightweight implementation, such as a test or development instance, or for SAP<br />
Solution Manager, choose the simple implementation. That is, stay with the old central<br />
instance approach, and keep the SCS on the primary application server.<br />
For more information, see 2.1.2 of the SAP Planning Guide for SAP NetWeaver for <strong>IBM</strong><br />
DB2 UDB for z/OS at:<br />
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/71a54946-0a01-0010-ceb8aca07c532bb1<br />
See also Business Continuity for SAP on <strong>IBM</strong> System z at:<br />
ftp://ftp.boulder.ibm.com/s390/software/sap/Business_Continuity_for_SAP.pdf<br />
4. Review the connectivity hardware required for your application server platform. See 2.3<br />
and 2.4 of the SAP Planning Guide for SAP NetWeaver for <strong>IBM</strong> DB2 UDB for z/OS (see<br />
step 3 on page 155 for the link).<br />
5. Determine the type of the file sharing technology for your application server platform:<br />
– SAP recommends using a shared hierarchical file system (HFS) to share file systems<br />
between z/OS systems. A shared HFS is a functional name and can be based on<br />
physical implementations, such as HFS, zSeries File System (zFS), NFS on the client,<br />
and a temporary file system (TFS). Consider using zFS as the fastest implementation,<br />
which also supports a Parallel Sysplex environment.<br />
– Use NFS to share files among z/OS and other UNIX or Linux systems. Also use NFS to<br />
access CD-ROMs mounted on a workstation or PC.<br />
– Use Server Message Block (SMB) to share files between z/OS and Windows.<br />
Review 3.2.4.3 “Selecting the Network File System Type” and all subchapters for file<br />
sharing and ASCII or EBDIC considerations in the SAP Planning Guide for SAP<br />
NetWeaver for <strong>IBM</strong> DB2 UDB for z/OS (see step 3 on page 155 for the link).<br />
6. Understand the file systems required for your application servers. See 3.2.4.2 “File<br />
System Setup” in the SAP Planning Guide for SAP NetWeaver for <strong>IBM</strong> DB2 UDB for z/OS<br />
(see step 3 on page 155 for the link).<br />
7. Review the Java requirements for application serving, where you get the code, and where<br />
it will be installed. See 3.2.4.7, “Java on z/OS,” in the SAP Planning Guide for SAP<br />
NetWeaver for <strong>IBM</strong> DB2 UDB for z/OS (see step 3 on page 155 for the link). See also SAP<br />
Note 1367498.<br />
8. Understand how you will synchronize heterogeneous servers in an SAP landscape. See<br />
3.2.4.8, “Setup of a Heterogeneous SAP System” in the SAP Planning Guide for SAP<br />
NetWeaver for <strong>IBM</strong> DB2 UDB for z/OS (see step 3 on page 155 for the link).<br />
With this information, you now can design your application server layout and prepare the<br />
platforms.<br />
Naming conventions for SAP landscapes<br />
An SAP application landscape contains more than one instance. Besides the ultimate<br />
production SAP system, each application has two or three more instances. At a minimum,<br />
SAP requires a test or development instance and a Quality Assurance (QA) staging instance.<br />
156 Running SAP Solutions with <strong>IBM</strong> DB2 10 for z/OS on the <strong>IBM</strong> zEnterprise System
Change language