Instalacao Cluster SAP Netweaver

New Installation Options for a HighAvailability SAP System Based on SAP NetWeaver 7.1 Including EHP1 (7.
11) in a Microsoft Cluster
Applies to:
SAP systems based on SAP NetWeaver 7.1 including EHP1 (7.11) and higher.
Summary
As of SAP NetWeaver 7.1 including EHP1 (7.11), and higher, SAP has adapted the installation procedure for a high-availability system on Windows Microsoft Failover Clustering to make it easier and less error-prone for customers. This document shows the new features and main advantages of the new cluster setup compared to the previous one. Authors: Goran Condric, Klaus-Georg Adams
Company: SAP AG, Created on: 9 January 2008
Authors Bio
Goran Condric joined SAP in 2000 and works in the Microsoft Platforms team. He is responsible for the deployment of SAP systems on Windows and the architecture of SAP high-availability solutions on Microsoft Failover Clustering. He also works on new virtualization concepts for SAP software on Microsoft platforms. Klaus-Georg Adams joined SAP in 2001. He works in the Software Logistics team and is responsible for the architecture of the SAP NetWeaver installation.
SAP COMMUNITY NETWORK 2009 SAP AG
SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 1
New Installation Options for a High-Availability SAP System Based on SAP NetWeaver 7.1
Table of Contents
New Installation Options for a High-Availability SAP System Based on SAP NetWeaver 7.1 Including EHP1 (7.11) in a Microsoft Cluster......................................................................................................3 Old Setup for an SAP High-Availability System Based on SAP NetWeaver 7.0 and 7.1 with Microsoft Custer ........................................................................................4 New Setup for an SAP High-Availability System with Microsoft Custer (SAP NetWeaver 7.11 and higher) .5
First Cluster Node ........................................................................................................................................................6 Additional Cluster Node ...............................................................................................................................................8
Installation of Primary and Additional Application Server Instances on Cluster Nodes..................................9 Uninstall Option.............................................................................................................................................10 Summary...........................................................................................................................................................12 Copyright...........................................................................................................................................................13
New Installation Options for a High-Availability SAP System Based on SAP NetWeaver 7.1 Including EHP1 (7.11) in a Microsoft Cluster
The SAP system landscape has become more complex over the years, with a central or standard system where all SAP instances run on the same host being the most simple system configuration. With the growing complexity of the SAP system landscape, the installation and configuration of an SAP system has also become more complex. The installation and configuration of a high-availability SAP system is the most complex installation type in an SAP system landscape, and is typically done by hardware partners. The only exception is the installation of a high-availability system on a Microsoft Windows Cluster, where SAP has been fully supporting the installation, configuration, and operation of SAP systems running on a SQL Server, Oracle, MaxDB, and DB6 database. For SAP systems based on SAP NetWeaver 7.1 including EHP1 (7.11) (and higher), SAP adapted the installation procedure for a high-availability system on Windows Microsoft cluster to make it easier and less error-prone for customers. This document shows the new setup of a high-availability system compared to the old one.
Old Setup for an SAP High-Availability System Based on SAP NetWeaver 7.0 and 7.1 with Microsoft Custer The following screenshot shows the installation options that were available for the installation of a highavailability system on Windows prior to SAP NetWeaver 7.11:
In a dual-stack (ABAP+Java) system, with the old cluster setup, you have to perform 11 separate steps to cluster your SAP system on Windows. The enqueue replication server (ERS) instance alone has to be installed 4 times in a ABAP+Java system on each node, once for ASCS and once for SCS. In addition, during the installation, you have to take care of the following: For the ASCS and SCS instances you have to choose a shared disk. For all other instances (ERS, host agent, diagnostic agent, central instance (as of SAP NetWeaver 7.1 called primary application server) and dialog instance (as of SAP NetWeaver 7.1 called additional application server instance) you have to choose a local disk. Often, customers have chosen the wrong disk (the local one instead of the shared one, and vice versa). When performing the installation options First MSCS Node, Additional MSCS Node, and Enqueue Replication Server, you have to re-enter the SAP system ID (<SAPSID>), instance numbers, domain, passwords, DVDs, and so on.
On Windows Server 2008, you have to start the installation of the ASCS and SCS installations from the command prompt with the command SAPINST_USE_HOSTNAME to run the installation with a virtual host name. On Windows Server 2008, unlike on Windows Server 2003, you also have to prepare the SAP cluster.
New Setup for an SAP High-Availability System with Microsoft Custer (SAP NetWeaver 7.11 and higher) The following screenshot shows the new installation options that are now available for the installation of a high-availability system:
The new setup has many new features and advantages, which are explained in detail below: In general, the installation functionality, the user interface, and the installation procedure are the same on Windows Server 2003 as on Windows Server 2008. Only four installation steps are required for all SAP systems regardless of whether you install an ABAP, Java, or ABAP+Java system. You can no longer mix up local or shared drives. Specifying cluster parameters have become more simple and less error prone Uninstall option is available for a high-availability system
First Cluster Node The First Cluster Node installation option now includes the previously separate options Central Services Instance for ABAP (ASCS), Central Services Instance (SCS), Enqueue Replication Server, and First MSCS Node, and performs the followings steps: It installs the central services instance for ABAP (ASCS) and central services instance (SCS), and prepares this host as the SAP global host. It installs the enqueue replication server instance (ERS) for the ASCS and SCS instances. It installs the host agent. It creates the SAP cluster group on the first cluster node and adds the ASCS and SCS instances to the SAP cluster group.
Another advantage is that for local instances, such as ERS, host agent, diagnostic agent, primary application server, or additional application server instance, you can only select local drives, whereas for the SCS or ASCS instance you can only select shared drives. The quorum disk is not available in the list of shared drives.
The following screenshot shows the first screen of the new cluster setup for the First Cluster Node.
Specifying cluster parameters has become less error-prone: You are prompted for the virtual host name for the (A)SCS instance(s). Therefore, you no longer have to start SAPinst with the SAPINST_USE_HOSTNAME option on Windows Server 2008. In addition, SAPinst checks whether the virtual host name is not in use and is resolvable For Windows Server 2008 you can also select whether you want to use DHCP-based IP addresses. The installation directly supports the multi-SID setup on Windows Server 2003.
The following screenshot shows the second screen of the new cluster setup for the First Cluster Node.
Additional Cluster Node The Additional Cluster Node installation option includes the previous options Enqueue Replication Server, and Additional MSCS Node, and performs the followings steps: It configures the additional cluster node to run the SAP cluster group. You just have to select one SAP cluster group and the installation then collects data about clustered instance(s), instance numbers, and so on. It installs the enqueue replication server instance (ERS) for the ASCS and SCS instance on a local drive. It installs the host agent on a local drive.
The following screenshot shows the first screen of the new cluster setup for the Additional Cluster Node.
Installation of Primary and Additional Application Server Instances on Cluster Nodes When you install the primary or additional application server instance(s) on cluster nodes, you can only select local drives to install them. It automatically installs the Diagnostic Agent (DAA instance)
Uninstall Option For the first time, SAPinst offers an uninstall option for clustered systems:
The uninstall option provides the following features: You have to run the option Uninstall SAP Systems or Single Instances on all cluster nodes. On the first cluster node the uninstall option removes: o All local instances of the first cluster node o The clustered A(SCS) instance(s) on both cluster nodes On the last cluster node, the uninstall option: o Removes all local instances o Offers to remove the SAP cluster group o Offers to move the shared disk to another cluster group
The following screenshot shows the uninstall dialog on the last cluster node:
When you uninstall an SAP system that was installed in a domain, you can now delete local users or groups only, as shown in the following screenshot:
Summary
The new cluster setup that is available as of SAP NetWeaver 7.11 provides many new features and advantages for customers to install an SAP system in a Microsoft Cluster. Customers now have to perform fewer installation steps and have to enter fewer parameters. The installation tool automatically collects and processes the input data. All this, together with improved data checks, means that the installation of a high-availability system has become much easier and less error-prone than before.
Copyright
2009 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. Any software coding and/or code lines/strings (Code) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

Instalacao Cluster SAP Netweaver

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Instalacao Cluster SAP Netweaver

Uploaded by

Copyright:

Available Formats

New Installation Options for a HighAvailability SAP System Based on SAP NetWeaver 7.1 Including EHP1 (7.

11) in a Microsoft Cluster

Company: SAP AG, Created on: 9 January 2008

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 1

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 2

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 3

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 4

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 5

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 6

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 7

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 8

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 9

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 10

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 11

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 12

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 13

You might also like