HP Serviceguard Extension for SAP (SGeSAP) SAP Preparation, SAP Pre-Installation Considerations

Page 35

SAP Preparation

This section covers the SAP specific preparation, installation and configuration before creating a high available SAP System landscape. This includes the following logical tasks:

•SAP Pre-Installation Considerations

•Replicated Enqueue Conversion

SAP Pre-Installation Considerations

This section gives additional information that help with the task of performing SAP installations in HP Serviceguard clusters. It is not intended to replace any SAP installation manual. SAP installation instructions provide complementary information and should be consulted in addition to this.

SAP Netweaver 2004s introduced High Availability installation options. In combination with SGeSAP they can also be activated to guide the clustering of SAP JAVA-only applications based on kernel 6.40. The SAP Enterprise Portal 6.0 belongs to this group of applications. All SAP components that are based on earlier SAP technology should to be installed in the standard way as described by the SAP Installation Guides. They can be clustered after the initial installation. In any case, it makes sense to already set up required file systems as documented in Chapter 2 'Planning the Storage Layout' to prevent avoidable conversion activities in a later stage.

The following paragraphs are divided into these installation options:

•SAP Netweaver High Availability

•Generic SAP Installation

SAP Netweaver High Availability

The SAP Netweaver High Availability options were officially introduced with Netweaver 2004s technology. They are based on the SAP Application Server 7.x. The SAPINST installer for SAP kernel 7.x offers the following installation options out of the box:

•Central System

•Distributed System

•High Availability System

The Central System and Distributed System installations build a traditional SAP landscape. They will install a database and a monolithic Central Instance. Exceptions are Java-only based installations.

NOTE: For Java-only based installations the only possible installation option is a High Availability System installation.

It is strongly recommended to use the "High Availability System" option for all new installations that are meant to be used with SGeSAP.

A SAP Application Server 7.0 may consist of any combination of the following components:

•Java System Central Services Instance (SCS) [Java Message and Enqueue Server]

•ABAP System Central Services Instance (ASCS) [ABAP Message and Enqueue Server]

•Dialog Instance(s) (D, JD, DVEBMGS) [ABAP and/or Java stack]

The potential SPOFs are the SCS, ASCS and DB instances. The Dialog instance can be installed redundantly on nodes inside or outside the cluster. The ABAP DVEBMGS instance for Netweaver 2004s (or higher) is similar to a simple Dialog Instance, except that it is preconfigured to contain the services Batch, Update, Spool and Gateway. For JAVA, a Central Instance runs the Java Software Deployment Manager (SDM). These services though can be also configured redundantly with other Dialog Instances.

The SAP Netweaver CDs/DVDs must be available either as physical copies or images on the local or shared file system for the duration of the installation.

As preparation, simple Serviceguard packages for the clustered instances have to be created. They provide the virtual IP addresses that are required during installation. The package(s) will later on be altered to utilize

SAP Preparation 35

Page 34 Page 36
Image 35
Page 34 Page 36
Contents Managing Serviceguard Extension for SAP Version B.05.00 Page Table of Contents SAP Master Data Management MDM 111 SGeSAP Cluster Administration 137SAP Supply Chain Management List of Figures Page List of Tables Page About this Manual Printing HistoryINSTNR, INR Related DocumentationGeneral Concepts of SGeSAP Designing SGeSAP Cluster ScenariosMutual Failover Scenarios Using the Two Package Concept Mutual Failover Scenarios Using the Two Package Concept Robust Failover Using the One Package Concept Follow-and-Push Clusters with Replicated Enqueue Applications/sap/enqor/SID ersINSTNR Replicated Enqueue Clustering for Abap and Java InstancesDedicated NFS Packages Handling of Redundant Dialog Instances Dedicated Failover Host Replicated Enqueue Clustering for Abap and Java Instances SAP Instance Storage Considerations Planning the Storage LayoutCommon Directories that are Kept Local Option 1 SGeSAP NFS ClusterDirectories that Reside on Shared Disks Option 2 SGeSAP NFS Idle Standby Cluster System and Environment Specific Volume GroupsOption 3 SGeSAP CFS Cluster Directories that Reside on CFS Database Instance Storage ConsiderationsOracle Single Instance Rdbms $ORACLEHOME/common/nls/admin/dataFile System Layout for NFS-based Oracle Clusters Oracle Real Application ClustersMaxdb Storage Considerations Globals IndepData=/sapdb/data IndepPrograms=/sapdb/programs Sapnfs Planning the Storage Layout Pgname = pkgtypeINSTNRSID Step-by-Step Cluster ConversionStep-by-Step Cluster Conversion SAP Netweaver High Availability SAP Pre-Installation ConsiderationsSAP Preparation Cmmakepkg -m sgesap/scs Cmmakepkg -m sgesap/ers Cmmakepkg -m sgesap/sapinstance -m ... /sap.configCmmakepkg -m sgesap/db -m sgesap/ci Cmmakepkg -m sgesap/db Cmmakepkg -m sgesap/ciPage Replicated Enqueue Conversion SAPINSTMASTERDVD/IMXOS/SAPINST/UNIX/OSSu sidadm Mkdir /usr/sap/SID/ASCSINSTNR Volume group needs to be created for the Ascs instanceSplitting an Abap Central Instance Create a new mountpointSapsystemname =SID If the used SAP kernel has a release older thanSAPLOCALHOST=DRELOC Instancename =ASCSINSTNRSAPSYSTEM=INSTNR2 Su sidadm Mkdir /usr/sap/SID/ERSINSTNR Volume group needs to be created for the ERS instanceCreation of Replication Instance Sapstartsrv Sapcontrol Servicehttp Mkdir -p exe/servicehttp/sapmcPF = $DIRPROFILE/SIDERSINSTNRAREPRELOC Scsid = INRHP-UX Configuration Ls -d /usr/sap/???/*INSTNR Directory Structure ConfigurationCluster Filesystem Configuration Installation Step IS049 Mkdir /usr/sap/SID.new Non-CFS Directory Structure ConversionMaxdb Database Step SD040 Filename localcopy checkexist Installation Step IS050Open the groupfile, /etc/group, on the primary side Open the password file, /etc/passwd, on the primary sideCluster Node Synchronization Copy the sidadm home directory to the backup nodes Look at the service file, /etc/services, on the primary sideSu sqddbsid Mkdir -p /sapdb/DBSID STARTPROFILE=STARTDVEBMGSINRprimarySTARTPROFILE=STARTDVEBMGSINRsecondary Su orasid Mkdir -p /oracle/SID ExitMkdir -p /usr/sap/tmp Cluster Node ConfigurationMkdir /dev/vgdbSIDmknod /dev/vgdbSID/group c 64 Ssh hostN date Ssh -l sidadm hostN date Swlist grep sshSsh-keygen -t dsa Iddsa Iddsa.pubSet -u External Application Server Host ConfigurationConfigure /etc/nsswitch.conf to avoid problems Hosts filesNOTFOUND=continue UNAVAIL=continue TRYAGAIN=nsDBRELOC=0.0.0.0 Modular Package ConfigurationDB=ORACLE Sapsystem C11 Modular Package Configuration Step-by-Step Cluster Conversion Example entries for the package configuration file Sapextinstance DVEBMGS10 Sapextsystem QAS Sbin/init.d/sapinit referenced by /sbin/rc3.d/S###sapinit Cmapplyconf -P ./sap.config Mkdir -p /etc/cmcluster/SID Legacy Package ConfigurationServiceguard Configuration Created configuration files need to be editedTouch /etc/cmcluster/SID/debug Servicename ciC11msServicefailfastenabled YES Servicehalttimeout Servicename ciC11dispApplications/sap/enqor/SIDersinstnr Resourcename /applications/sap/enqor/C11ascsENQORSCSPKGNAMEC11=foobar ENQORREPPKGNAMEC11=foorep Distribute the package setup to all failover nodes SGeSAP ConfigurationSpecification of the Packaged SAP Components NFSRELOC=0.0.0.0 DNAME1=D CINAME=DVEBMGS CINR=00AREPNAME=ERS AREPNR=01 AREPRELOC=0.0.0.0 DNAME0=DREPNAME=ERS REPNR=00 Configuration of Application Server HandlingJCINAME=SCS JCINR=01 JCIRELOC=0.0.0.0Page Restart Stop Start $STARTWITHPKG, $STOPWITHPKG, $RESTARTDURINGFAILOVERWAITOWNAS=1 ASTREAT0=$RESTARTDURINGFAILOVER ASPLATFORM0=SG-PACKAGEASPSTART=1 WAITOWNAS=0 Optional Parameters and Customizable FunctionsWAITOWNAS=2 RFCADAPTERCMD=runadapter.sh SAPROUTERSTART0=1 SAPROUTERPORT0=-S3299RFCADAPTERSTART=1 SAPSTARTSRVSTART=1 SAPSTARTSRVSTOP=1 Global DefaultsSAPCCMSRSTART=1 Legacy Package Configuration Packagename sapnfs HA NFS Toolkit ConfigurationEXEDIR= /usr/sap/SID/SYS/exe/runU JMSSERVBASE=3600Sapmnt/SID Usr/sap/trans Auto FS ConfigurationHANFSSCRIPTEXTENSION=pkgtype Export/sapmnt/SID Export/usr/sap/transNFSCLIENT=1 NFSSERVER=1 NUMNFSD=4 NUMNFSIOD=4 AUTOMASTER=/etc/automaster AUTOMOUNTOPTIONS=-f $AUTOMASTERAUTOMOUNTDOPTIONS= -L AUTOFS=1 AUTOMASTER=/etc/automaster AUTOOPTIONS=-f $AUTOMASTERDatabase Configuration Perform the following steps as orasid Additional Steps for OraclePerform the following step as sidadm Lsnrctl start LISTENERSID1/2 If you use more than one SAP system inside of your clusterAdditional steps for Oracle 10g Rdbms Additional Steps for MaxdbAdditional steps for Oracle 9i Rdbms SAP Application Server Configuration Sapmnt/SID/profile/SIDINSTNAMEINR SAP Abap Engine specific configuration stepsCdpro Rdisp/enqname = relocciSIDinstnrBatch jobs can be scheduled to run on a particular instance SaplocalhostsidinstnrSID/dbhost = relocdb Icm/hostnamefull=relocatibleip SAP J2EE Engine specific installation stepsRdisp/starticman=TRUE Jdbc/pool/SID/Url jdbcoraclethin@relocdb1527SID Admin/host/SID relocdbPage SAP Supply Chain Management More About Hot Standby Option 1 Simple Clusters with Separated Packages Planning the Volume Manager SetupOption 3 Full Flexibility Option 2 Non-MAXDB EnvironmentsOption 4 Hot Standby liveCache Maxdb Storage ConsiderationsLiveCache Installation Step LC010 Synchronize the /etc/group and /etc/passwd files HP-UX Setup for Options 1, 2Mkdir -p /sapdb/data Mkdir /sapdb/LCSID Do the following to continueCopy file /etc/opt/sdb to the second cluster node Mkdir /sapdbHORCCMRCF=1 HORCMINST=0 HP-UX Setup for OptionIf you use DNS Hosts filesNOTFOUND=continue UNAVAIL=continue \ TRYAGAIN=nsPackagename lcLCSID SGeSAP Modular Package ConfigurationCmmakepkg -m sgesap/livecache lcLCSID.config SGeSAP Modular Package Configuration Packagetype Failover SGeSAP Legacy Package ConfigurationCreate standard package control and configuration files Cp /opt/cmcluster/sap/*.functions /etc/cmclusterLCPRIMARYROLE=primarynode LCSECONDARYROLE=secondarynode Cold Admin Warm OnlineLCSTANDBYRESTART=1 Livecache Service MonitoringLCCOPYMECHANISM=BUSINESSCOPY AVOIDWWIDCHECK=1APO Setup Changes # dbmcli on hostname Lcsid quit Su lcsidadm Dbmcli -ux SAPLCSID,password -ulMv .XUSER.62 .XUSER.62.ORG Default key Sapdb/programsrelocsapnfss/export/sapdb/programs General Serviceguard Setup ChangesFor option Last step is to reconfigure the cluster with cmapplyconf1m Master Data Management User Interface Components Master Data Management OverviewSAP Netweaver XI components MDM Server ComponentsOracle/MDM Installation and Configuration ConsiderationsPrerequisites MDM SGeSAP File System LayoutOpt/MDM Single or Multiple MDM Serviceguard Package ConfigurationsSingle MDM Serviceguard Package ONE Multiple MDM Serviceguard packages FOUR+ONEMkdir -p /export/home/mdmuser Mkdir -p /home/mdmuser Run ioscan and insf to probe/install new disk devicesMkdir -p /oracle/MDM Mkdir -p /opt/MDM Installation and Configuration Considerations Runscript /etc/cmcluster/MDMNFS/mdmNFS.control.script Runscripttimeout NotimeoutHaltscripttimeout Notimeout NodenameSbin/init.d/nfs.client stop Sbin/init.d/nfs.client start Scp -rp /etc/cmcluster/MDMNFS clunode2/etc/cmcluster/MDMNFSScp -p /etc/auto.direct clunode2/etc/auto.direct Runscript /etc/cmcluster/MDM/mdbMDM.control.script Runscript /etc/cmcluster/MDM/mgroupMDM.control.scriptHaltscript /etc/cmcluster/MDM/mgroupMDM.control.script Haltscript /etc/cmcluster/MDM/mdsMDM.control.script Haltscript /etc/cmcluster/MDM/mdbMDM.control.scriptRunscript /etc/cmcluster/MDM/mdsMDM.control.script Haltscript /etc/cmcluster/MDM/mdssMDM.control.script Runscript /etc/cmcluster/MDM/mdisMDM.control.scriptHaltscript /etc/cmcluster/MDM/mdisMDM.control.script Runscript /etc/cmcluster/MDM/mdssMDM.control.scriptSsh -X clunode1 -l oramdm Runscript /etc/cmcluster/MDM/masterMDM.control.scriptHaltscript /etc/cmcluster/MDM/masterMDM.control.script KITS/ora9208/Disk1/runInstller Specify File Locations SidmdmSetup Step MDM218 SAP Master Data Management MDM MDM = Description = Addresslist = Sidlistlistener = Sidlist = Siddesc = Globaldbname = MDM Connectdata = Server = Dedicated Servicename = MDMListener = Descriptionlist = Description = Addresslist = Installation and Configuration Considerations Create a /home/mdmuser/mdss directory Global SAP Master Data Management MDM MDMUSER=mdmuser Single Serviceguard package configure sap.configMDMLISTENERNAME=LISTENER MDMMGROUPDEPEND=mdb mds mdis mdss MDMPASSWORD= MDMREPOSITORYSPEC=MDMMDSRELOC=172.16.11.96 MDMMONITORINTERVAL=60Cmrunpkg mgroupMDM Cmhaltpkg mgroupMDM Servicefailfastenabled no ServicehalttimeoutVi /etc/cmcluster/MDM/mdsMDM.config Servicename mdsMDMmon Cmapplyconf -P /etc/cmcluster/MDM/mdsMDM.configCmrunpkg masterMDM Cmhaltpkg masterMDM System Level Changes Change ManagementSGeSAP Cluster Administration SAP Software Changes Swlist -l bundle B7885BA T2803BA Upgrading SAP SoftwareMixed Clusters Swlist -l bundle T2357BA T2803BACd /sapmnt Ln -s /sapmnt/SID/exepa /sapmnt/SIDexelocal Cd /sapmnt/SID Mv exe exepaCd /sapmnt/SID Mkdir exeipf Cd /sapmnt/SID Ln -s /sapmnt/SIDexelocal exe
Related manuals
Manual 35 pages 22.06 Kb
Top Page Image Contents