How to Verify the Installation of an SAP NetWeaver

 On the node where you installed the SAP NetWeaver instance as the root user, do the following: 1. Switch to the SAP NetWeaver administrative user. # su - sidadm 2. Stop the SAP NetWeaver instance. $ stopsap r3 instance name 3. Kill all remaining processes. $ pkill -f instance name 4. Start the instance. $ startsap r3 instance name 5. Check if the instance goes online. $ sapcontrol -nr instance number -function GetProcessList Repeat this step until all the processes show the GREEN status. 6. Stop the SAP NetWeaver instance. $ stopsap r3 instance name 7. Kill all remaining processes. $ pkill -f instance name

Supported Data Service Configurations

 HA for SAP NetWeaver supports configurations that conform to the requirements that are specified in the previous section. All configurations of HA for SAP NetWeaver have the following requirements: ■ The SAP central service is configured as a failover resource. ■ The SAP replicated enqueue server is configured as a failover resource. ■ The SAP application server instances which are primary application instances or additional application instances can be configured either as a failover resource or as a multiple master data service resource. ■ Each SAP instance resource must be dependent on a SAP sapstartsrv resource. ■ Do not configure central service resources and replicated enqueue resources in the same resource group. ■ The SAP replicated enqueue server resource is configured to depend on the SAP central service resource. This dependency ensures that the SAP replicated enqueue server does not attempt to start until the SAP central service is online. ■ The SAP central services resource group is configured to have weak positive affinity with the SAP replicated enqueue server resource group. This affinity ensures that, if a hardware or software failure occurs on the node or zone that is mastering the SAP central services resource group, the SAP central services resource group fails over to the node or zone where the SAP replicated enqueue server resource group is currently running. ■ You must configure the SAP replicated enqueue preempter resource in the SAP central services resource group. This is to ensure that if the SAP central services resource group fails over to the node running the SAP replicated enqueue server resource group is offloaded after the central services are online and the enqueue table is copied to the enqueue server process. This off-load happens once a node is available to host the replicated enqueue server resource group. The following example shows the following supported configurations of HA for SAP NetWeaver. ■ The SAP NetWeaver component is configured as a failover resource. ■ The SAP NetWeaver component is configured as a multiple master resource

Configuration Restrictions

 For restrictions that apply to all data services, see the release notes for your release of Oracle Solaris Cluster. The following configuration restriction applies only to HA for SAP NetWeaver. ■ Do not set Autostart=1 in an instance profile. This entry setting might cause failure of the data service to fail over. Only configure Autostart=0 in an instance profile. ■ The maximum length of the node names depends on the SAP release. Refer to the SAP installation guide for your release of SAP. This limitation is an SAP software restriction. ■ Configure the database resource to be in a different resource group from the SAP central services resource, if possible. However, if you are using Oracle as the database, and if you must configure Oracle in the same resource group as the SAP central services resource, you must ensure that the value of the restart_type extension property for HA for Oracle is set to RESOURCE_RESTART. This property setting means that if the response to a fault in the Oracle database is to restart the Oracle resource, only the Oracle database is restarted. If this property is set to RESOURCE_GROUP_RESTART, and if the response to a fault in the Oracle database is to restart the Oracle resource, all the resources in the resource group are restarted. However, if the SAP replicated enqueue server is configured and online on another node, the SAP central services must not be restarted locally. Therefore, the restart_type property must be set to RESOURCE_RESTART

Oracle® Solaris Cluster Data Service for SAP

 The SAP NetWeaver platform can be deployed as an ABAP, a JAVA, or a dual stack. In the dual stack, the primary application instance and the application server instance combine the ABAP and the JAVA processes in one instance. The central services and the replicated enqueue server implement either the ABAP or the JAVA deployment only. Caution - For a detailed description of the SAP NetWeaver platform in the High Availability environment, see the SAP documentation at http://service.sap.com/. In particular, read the section that provides an overview of the architecture of the SAP NetWeaver to be certain that you understand the basic concepts of your version of the SAP NetWeaver. To eliminate potential single points of failure in an SAP NetWeaver platform, HA for SAP NetWeaver provides fault monitoring, automatic restart, and automatic failover for the components of the SAP NetWeaver platform. The primary and additional application server instances can be configured as multiple master or failover deployments. All other instances must be failover deployments. Each component of the SAP NetWeaver platform has a data service that protects the component in an Oracle Solaris Cluster configuration, as described in the following table.

SAP HANA Administration Course Outline

 

Ø  SAP HANA Introduction (Completed on 26^th March)

Introduction to SAP HANA

SAP HANA Information Sources

Revision strategy of SAP HANA

 

Ø  Preparing Installation (Completed on 27^th March)

Sizing of SAP HANA

Requirements

 

Ø  Installation (Completed on 28^th March)

Installation with SAP HANA Lifecycle

Management

Tools

Performing a Distributed System Installation (Pending)

 

Ø  Post Installation

Post-Installation Steps

Updating SAP HANA

 

Ø  Migration to SAP HANA

Migration to SAP HANA using DMO

 

Ø  Architecture and Scenarios (Completed on 26^th March)

 

SAP HANA Memory Management & Data Persistence

Optional Transaction Management and Concurrency Control

Software Packaging

SAP HANA Roadmap and Scenarios

Deployment Options

 

 

Ø  Admin Tools for SAP HANA (Completed on 29^th March)

 

Administration Tool Overview

SAP HANA Studio

DBA Cockpit

HDBSQL Command Line Tool