HP Serviceguard Extension for SAP (SGeSAP) manual HP-UX Configuration

Page 45

#-----------------------------------------------------------------------

_CPARG0 = list:$(DIR_EXECUTABLE)/ers.lst

Execute_00 = immediate $(DIR_EXECUTABLE)/sapcpe $(_CPARG0) pf=$(_PF)

#--------------------------------------------------------------------

# start enqueue replication server

#--------------------------------------------------------------------

_ER = er.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME) Execute_01 = immediate rm -f $(_ER)

Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/enrepserver $(_ER) Start_Program_00 = local $(_ER) pf=$(_PF) NR=$(SCSID)

The DIR_CT_RUN in these profiles should equal the value of DIR_CT_RUN(if specified) or DIR_EXECUTABLE from the [A]SCS instance profile. It is essential that the binaries from [A]SCS and ERS instances are from the same binary set.

Make sure that the [A]SCS instances are not configured for automatic restart in the SAP profile.

HP-UX Configuration

A correct HP-UX configuration ensures that all cluster nodes provide the environment and system configuration required to run SAP Application Server based business scenarios.

Several of the following steps must be repeated on each node. Record the steps completed for each node, as you complete them. This helps identify errors in the event of a malfunction later in the integration process. The HP-UX configuration task is split into the following sections:

Directory Structure Configuration - This section adds implementation practices to the architectural decisions made in the chapter "Storage Layout Considerations". It gives some guidance how to achieve the differences in directory structure layout for a clustered SAP system as compared to a standard installation.

NOTE: Most of these steps in this section are only performed once on the primary host.

The primary host is where the SAP Instance was installed. If your database is currently running on a machine different from this, the database vendor dependent steps will have to be done on the host on which the database was installed.

Cluster Node Synchronization - There are a couple of changes to the operating system configuration that were performed during SAP installation on the primary node. In order to allow the system to run on other nodes, these changes need to be made to other cluster nodes, too. This section also includes steps to distribute the changes of the directory structure configuration performed in the section above.

NOTE: Repeat the cluster node synchronization steps for each node of the cluster that is different than the primary.

Cluster Node Configuration - This section consists of steps performed on all the cluster nodes, regardless if the node is a primary node or a backup node.

NOTE: Repeat the cluster node configuration steps for each node of the cluster.

External Application Server Host Configuration - This section consists of steps performed on any host outside of the cluster that runs another ABAP instance of the SAP system.

NOTE: Repeat this section for each host that has an external application server installed

Performing some of the iterations in parallel is fine. Use caution in any complex setup situation.

Rather than using the cut and paste mechanism you can also fill out the tables provided by first analyzing the primary host(s). Afterwards you can use the tables to synchronize all nodes.

HP-UX Configuration 45

Image 45
Contents Managing Serviceguard Extension for SAP Version B.05.00 Page Table of Contents SGeSAP Cluster Administration 137 SAP Supply Chain ManagementSAP Master Data Management MDM 111 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 Pre-Installation Considerations SAP PreparationSAP Netweaver High Availability Cmmakepkg -m sgesap/db -m sgesap/ci Cmmakepkg -m sgesap/sapinstance -m ... /sap.configCmmakepkg -m sgesap/db Cmmakepkg -m sgesap/ci Cmmakepkg -m sgesap/scs Cmmakepkg -m sgesap/ersPage Replicated Enqueue Conversion SAPINSTMASTERDVD/IMXOS/SAPINST/UNIX/OSSplitting an Abap Central Instance Volume group needs to be created for the Ascs instanceCreate a new mountpoint Su sidadm Mkdir /usr/sap/SID/ASCSINSTNRSapsystemname =SID If the used SAP kernel has a release older thanInstancename =ASCSINSTNR SAPSYSTEM=INSTNR2SAPLOCALHOST=DRELOC Volume group needs to be created for the ERS instance Creation of Replication InstanceSu sidadm Mkdir /usr/sap/SID/ERSINSTNR Sapstartsrv Sapcontrol Servicehttp Mkdir -p exe/servicehttp/sapmcPF = $DIRPROFILE/SIDERSINSTNRAREPRELOC Scsid = INRHP-UX Configuration Directory Structure Configuration Cluster Filesystem ConfigurationLs -d /usr/sap/???/*INSTNR Installation Step IS049 Mkdir /usr/sap/SID.new Non-CFS Directory Structure ConversionMaxdb Database Step SD040 Filename localcopy checkexist Installation Step IS050Open the password file, /etc/passwd, on the primary side Cluster Node SynchronizationOpen the groupfile, /etc/group, on the primary side Copy the sidadm home directory to the backup nodes Look at the service file, /etc/services, on the primary sideSTARTPROFILE=STARTDVEBMGSINRsecondary STARTPROFILE=STARTDVEBMGSINRprimarySu orasid Mkdir -p /oracle/SID Exit Su sqddbsid Mkdir -p /sapdb/DBSIDCluster Node Configuration Mkdir /dev/vgdbSIDmknod /dev/vgdbSID/group c 64Mkdir -p /usr/sap/tmp Ssh-keygen -t dsa Swlist grep sshIddsa Iddsa.pub Ssh hostN date Ssh -l sidadm hostN dateConfigure /etc/nsswitch.conf to avoid problems External Application Server Host ConfigurationHosts filesNOTFOUND=continue UNAVAIL=continue TRYAGAIN=ns Set -uModular Package Configuration DB=ORACLEDBRELOC=0.0.0.0 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 Serviceguard Configuration Legacy Package ConfigurationCreated configuration files need to be edited Mkdir -p /etc/cmcluster/SIDServicefailfastenabled YES Servicehalttimeout Servicename ciC11msServicename ciC11disp Touch /etc/cmcluster/SID/debugApplications/sap/enqor/SIDersinstnr Resourcename /applications/sap/enqor/C11ascsENQORSCSPKGNAMEC11=foobar ENQORREPPKGNAMEC11=foorep SGeSAP Configuration Specification of the Packaged SAP ComponentsDistribute the package setup to all failover nodes NFSRELOC=0.0.0.0 AREPNAME=ERS AREPNR=01 AREPRELOC=0.0.0.0 CINAME=DVEBMGS CINR=00DNAME0=D DNAME1=DJCINAME=SCS JCINR=01 Configuration of Application Server HandlingJCIRELOC=0.0.0.0 REPNAME=ERS REPNR=00Page Restart Stop Start $STARTWITHPKG, $STOPWITHPKG, $RESTARTDURINGFAILOVERASTREAT0=$RESTARTDURINGFAILOVER ASPLATFORM0=SG-PACKAGE ASPSTART=1WAITOWNAS=1 Optional Parameters and Customizable Functions WAITOWNAS=2WAITOWNAS=0 SAPROUTERSTART0=1 SAPROUTERPORT0=-S3299 RFCADAPTERSTART=1RFCADAPTERCMD=runadapter.sh Global Defaults SAPCCMSRSTART=1SAPSTARTSRVSTART=1 SAPSTARTSRVSTOP=1 Legacy Package Configuration EXEDIR= /usr/sap/SID/SYS/exe/runU HA NFS Toolkit ConfigurationJMSSERVBASE=3600 Packagename sapnfsHANFSSCRIPTEXTENSION=pkgtype Auto FS ConfigurationExport/sapmnt/SID Export/usr/sap/trans Sapmnt/SID Usr/sap/transAUTOMOUNTDOPTIONS= -L AUTOFS=1 AUTOMASTER=/etc/automaster AUTOMOUNTOPTIONS=-f $AUTOMASTERAUTOMASTER=/etc/automaster AUTOOPTIONS=-f $AUTOMASTER NFSCLIENT=1 NFSSERVER=1 NUMNFSD=4 NUMNFSIOD=4Database Configuration Additional Steps for Oracle Perform the following step as sidadmPerform the following steps as orasid Lsnrctl start LISTENERSID1/2 If you use more than one SAP system inside of your clusterAdditional Steps for Maxdb Additional steps for Oracle 9i RdbmsAdditional steps for Oracle 10g Rdbms SAP Application Server Configuration Cdpro SAP Abap Engine specific configuration stepsRdisp/enqname = relocciSIDinstnr Sapmnt/SID/profile/SIDINSTNAMEINRSaplocalhostsidinstnr SID/dbhost = relocdbBatch jobs can be scheduled to run on a particular instance SAP J2EE Engine specific installation steps Rdisp/starticman=TRUEIcm/hostnamefull=relocatibleip 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, 2Copy file /etc/opt/sdb to the second cluster node Do the following to continueMkdir /sapdb Mkdir -p /sapdb/data Mkdir /sapdb/LCSIDIf you use DNS HP-UX Setup for OptionHosts filesNOTFOUND=continue UNAVAIL=continue \ TRYAGAIN=ns HORCCMRCF=1 HORCMINST=0SGeSAP Modular Package Configuration Cmmakepkg -m sgesap/livecache lcLCSID.configPackagename lcLCSID SGeSAP Modular Package Configuration Create standard package control and configuration files SGeSAP Legacy Package ConfigurationCp /opt/cmcluster/sap/*.functions /etc/cmcluster Packagetype FailoverLCPRIMARYROLE=primarynode LCSECONDARYROLE=secondarynode Cold Admin Warm OnlineLCCOPYMECHANISM=BUSINESSCOPY Livecache Service MonitoringAVOIDWWIDCHECK=1 LCSTANDBYRESTART=1APO Setup Changes Su lcsidadm Dbmcli -ux SAPLCSID,password -ul Mv .XUSER.62 .XUSER.62.ORG Default key# dbmcli on hostname Lcsid quit General Serviceguard Setup Changes For optionSapdb/programsrelocsapnfss/export/sapdb/programs Last step is to reconfigure the cluster with cmapplyconf1m Master Data Management User Interface Components Master Data Management OverviewSAP Netweaver XI components MDM Server ComponentsPrerequisites Installation and Configuration ConsiderationsMDM SGeSAP File System Layout Oracle/MDMSingle MDM Serviceguard Package ONE Single or Multiple MDM Serviceguard Package ConfigurationsMultiple MDM Serviceguard packages FOUR+ONE Opt/MDMRun ioscan and insf to probe/install new disk devices Mkdir -p /oracle/MDMMkdir -p /export/home/mdmuser Mkdir -p /home/mdmuser Mkdir -p /opt/MDM Installation and Configuration Considerations Haltscripttimeout Notimeout Runscripttimeout NotimeoutNodename Runscript /etc/cmcluster/MDMNFS/mdmNFS.control.scriptScp -rp /etc/cmcluster/MDMNFS clunode2/etc/cmcluster/MDMNFS Scp -p /etc/auto.direct clunode2/etc/auto.directSbin/init.d/nfs.client stop Sbin/init.d/nfs.client start Runscript /etc/cmcluster/MDM/mgroupMDM.control.script Haltscript /etc/cmcluster/MDM/mgroupMDM.control.scriptRunscript /etc/cmcluster/MDM/mdbMDM.control.script Haltscript /etc/cmcluster/MDM/mdbMDM.control.script Runscript /etc/cmcluster/MDM/mdsMDM.control.scriptHaltscript /etc/cmcluster/MDM/mdsMDM.control.script Haltscript /etc/cmcluster/MDM/mdisMDM.control.script Runscript /etc/cmcluster/MDM/mdisMDM.control.scriptRunscript /etc/cmcluster/MDM/mdssMDM.control.script Haltscript /etc/cmcluster/MDM/mdssMDM.control.scriptRunscript /etc/cmcluster/MDM/masterMDM.control.script Haltscript /etc/cmcluster/MDM/masterMDM.control.scriptSsh -X clunode1 -l oramdm KITS/ora9208/Disk1/runInstller Specify File Locations SidmdmSetup Step MDM218 SAP Master Data Management MDM MDM = Description = Addresslist = Connectdata = Server = Dedicated Servicename = MDM Listener = Descriptionlist = Description = Addresslist =Sidlistlistener = Sidlist = Siddesc = Globaldbname = MDM Installation and Configuration Considerations Create a /home/mdmuser/mdss directory Global SAP Master Data Management MDM Single Serviceguard package configure sap.config MDMLISTENERNAME=LISTENERMDMUSER=mdmuser MDMMDSRELOC=172.16.11.96 MDMPASSWORD= MDMREPOSITORYSPEC=MDMMONITORINTERVAL=60 MDMMGROUPDEPEND=mdb mds mdis mdssVi /etc/cmcluster/MDM/mdsMDM.config Servicename mdsMDMmon Servicefailfastenabled no ServicehalttimeoutCmapplyconf -P /etc/cmcluster/MDM/mdsMDM.config Cmrunpkg mgroupMDM Cmhaltpkg mgroupMDMCmrunpkg masterMDM Cmhaltpkg masterMDM System Level Changes Change ManagementSGeSAP Cluster Administration SAP Software Changes Mixed Clusters Upgrading SAP SoftwareSwlist -l bundle T2357BA T2803BA Swlist -l bundle B7885BA T2803BACd /sapmnt/SID Mkdir exeipf Cd /sapmnt/SID Mv exe exepaCd /sapmnt/SID Ln -s /sapmnt/SIDexelocal exe Cd /sapmnt Ln -s /sapmnt/SID/exepa /sapmnt/SIDexelocal
Related manuals
Manual 35 pages 22.06 Kb