06.01.2013 Views

Download PDF - IBM Redbooks

Download PDF - IBM Redbooks

Download PDF - IBM Redbooks

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

► Ensure that the Ethernet interface to the external network is virtualized by z/VM through<br />

an internal virtual LAN, called the z/VM VSWITCH.<br />

► Use Quagga and ospf daemons for VIPA support and dynamic routing<br />

– See the Quagga Routing Suite site at:<br />

http://www.quagga.net/<br />

– Use an NFS client for file sharing with AIX and z/OS UNIX System Services.<br />

– Use SAMBA for file sharing with Windows.<br />

Preparing for the SAP installation<br />

You can now install SAP NetWeaver and the applications. Everything you need is on the<br />

installation media that you download or receive from SAP.<br />

To begin, follow these steps:<br />

1. Start a PuTTY session or any other SSH terminal.<br />

2. Run the SAPINST utility on the application server platform.<br />

The SAPINST utility runs with root and administrator authority and uses a CLI or JDBC Driver –<br />

DB2 Connect Lite or Thin Client to communicate with DB2 on z/OS. Any media with<br />

NetWeaver 7 SR3 and later install the thin client.<br />

Performing the post-installation steps for SAP<br />

After the SAP code is installed and the database is created and loaded with the initial data,<br />

you must perform several steps to complete the installation process. Some software parts<br />

and agents, such as stored procedures, of the SAP system run in the z/OS environment<br />

directly, which the SAPINST tool cannot access from the application server it runs on.<br />

Perform the following post-installation steps:<br />

1. Install SAP Operating System Collector saposcol, which is the required agent to collect<br />

RMF and SMF data from the operating system.<br />

2. Install the CCMS agent SAPCCMSR, which is the SAP CCMS console interface.<br />

3. Install the SAP DB2 stored procedure SAPCL, which is the monitoring agent.<br />

4. Obtain and install the SAP license. The license key is in the SAP shared file system.<br />

5. Review the SAP profile parameters.<br />

6. Remove DB2 ZPARM OFFLOAD if it was modified. Also verify the other ZPARMs.<br />

7. Install the SAP support packages.<br />

8. Make a client copy.<br />

9. Back up the DB2 database by using the BACKUP SYSTEM DB2 command, which you can<br />

also run to test if your backup procedures are working.<br />

10.Back up the application server file systems.<br />

The backup procedures depend on the application server platforms. For Linux on System<br />

z, native, or under z/VM, you can use the DFSMShss utilities.<br />

11.Create zFS aggregates if the file systems are on z/OS.<br />

12.<strong>Download</strong> the latest build of DB2 Connect from the SAP Service Marketplace after installing<br />

SAP. The SAPINST tool installs a DB2 Connect version from the supplied media that was<br />

tested for the SAP installation. Newer versions are better suited for production work.<br />

Appendix B. Planning, preparing, and implementing the SAP landscape 189

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!