HP Storage Essentials Standard Edition SRM Software User Manual

HP Storage Essentials SRM Enterprise Edition 6.0 Microsoft Windows

Application Integration Software

for SAP ACC version A.02.00

User Guide

T4283-96335

Part number: T4283-96336 Third edition: May 2008

Legal and notice information

Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information is provided “as is” without warranty of any kind and is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Microsoft and Windows are registered trademarks of Microsoft Corporation. Oracle is a registered trademark of Oracle Corporation. Sun, Solaris, Sun StorEdge, and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. AIX and IBM are registered trademarks of International Business Machines Corporation in the United States, other countries or both. SGI and IRIX are registered trademarks of Silicon Graphics, Inc. Netscape is a registered trademark of Netscape Communications Corporation in the United States and other countries. HDS and HiCommand are registered trademarks of Hitachi Data Systems. HP, HP-UX, and OpenVMS, Tru64 UNIX are registered trademark of Hewlett-Packard Development Company. QLogic is a trademark of QLogic Corporation. Emulex is a registered trademark of Emulex Corporation. HBAnyware is a trademark of Emulex Corporation. SAP and SAP NetWeaver are registered trademarks of SAP AG in Germany and in several other countries. ABAP is a trademark of SAP AG in Germany and in several other countries.

Other product and company names mentioned herein may be the trademarks of their respective owners.

HP Storage Essentials SRM Enterprise Edition Microsoft Windows Application Integration Software for SAP ACC version A.02.00 User Guide

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

HP-authorized reseller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Helpful web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Contents

1SAP Adaptive Computing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

SAP ACC overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

The virtual SAP landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

SAP ACC components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Virtual IP address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Virtualized data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Application Integration Software for SAP ACC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

HP Storage Essentials SRM Enterprise Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Active host management interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Application Integration Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 Creating an Adaptive Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

SAP virtual landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Configure the SAP ACC landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Configure the SAP instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 Install HP Storage Essentials SRM and HP SIM . . . . . . . . . . . . . . . . . . . . . . . . . 17

User account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Storage system considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

SAN zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Host groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Reserved-Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4 Install the Application Integration Software for SAP ACC . . . . . . . . . . . . . . . . . . 19

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Installation Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Removing the Application Integration Software for SAP ACC . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

5 Interprocess Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Installing OpenSSH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Setup and Configuration on the Storage Essentials Server. . . . . . . . . . . . . . . . . . . . . . . . . . . 26

User Guide iii

Setup and Configuration on the ACC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Setup and Configuration on the Managed Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

6 Install the Integration Library on Managed Nodes . . . . . . . . . . . . . . . . . . . . . . . 29

Installing the storage specific integration library on SAP hosts . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Updating the storage specific integration library on SAP hosts . . . . . . . . . . . . . . . . . . . . . . . . . . 31

7 Record Storage Resources information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Adding a Storage Resource Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Viewing resource information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Removing a Storage Resource Identifier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

8 Application Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

9 Program Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Changing the user name and password used for communicating with HP Storage Essentials SRM . 49

Changing the reserve group assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

10Operational Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Operational information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Location of important log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Common issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Provisioning errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

An element in HP Storage Essentials SRM is reported as “(missing)”. . . . . . . . . . . . . . . . . . . . 58

HP Storage Essentials SRM is out of sync with managed host or storage array . . . . . . . . . . . . 58

Mount error in Microsoft Windows environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Some part of the SAP ACC Process fails, but SAP report instance “running” . . . . . . . . . . . . . . 59

11Application Scripts Description and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

SAP Central Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

SAP Database Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Starting and Stopping SAP instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Sample Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Script Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Preparing the SAP Central Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Sample Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Attaching the SAP Database Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Sample Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Detaching the SAP Database Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Sample Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Deleting the SAP Central Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Sample Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Configuring SAP to Run Customized Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Central Instance Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Database Instance Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

User Guide v

Figures

1 The components to create a virtualized application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 Virtual SAP instance on physical server HostA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3 SAP instance is moved from HostA to HostB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

4 Architecture for SAP Adaptive Computing Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

5 Overview of the SAP ACC library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

6 Relationship between physical storage devices on different operating systems . . . . . . . . . . . . . . 9

7 Configuring the Storage Integration in the SAP ACC Interface . . . . . . . . . . . . . . . . . . . . . . . . 15

8 Accepting the license agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

9 Choose a destination folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

10 Providing integration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

11 Installation is complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

12 Communication between systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

13 Login page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

14 Integration Library tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

15 Install/Upgrade Integration Library window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

16 Login page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

17 The Add Storage Resource page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

18 Associate physical storage to storage resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

19 A reserved group entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

20 Confirm details for new storage resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

21 Newly added storage resource is displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

22 Storage Resource Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

23 Removing a storage resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

24 Application Log page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

25 Application log detail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

26 Program Properties page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

27 Modify reserve group assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

29 Sample scripts for starting and stopping SAP instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

User Guide vii

viii

Tables

1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

User Guide ix

About this guide

This guide provides information about the implementation of the HP Storage Essentials Storage Resource Management (SRM) Enterprise Edition Windows Application Integration Software for SAP Adaptive Computing Controller. The Application Integration Software is available with HP Storage Essentials Storage Resource Management (SRM) to enable and integrate with the Adaptive Computing Controller for SAP when using SAN attached storage on HP StorageWorks arrays.

Intended audience

This guide is intended for:

• Storage Administrator

• System Administrator

• SAP Basis Administrator

• Network Administrator

Prerequisites

Prerequisites for using this product include:

• Networking

• Storage Area Networks (SANs)

• The Common Information Model (CIM)

• HP Storage Essentials Storage Resource Management

• HP Systems Insight Manager

Document conventions and symbols

Table 1 Document conventions

Convention Element

Medium blue text: Figure 1 Cross-reference links and e-mail addresses

Medium blue, underlined text (http://www.hp.com

Bold font • Key names

Italics font Text emphasis

Monospace font • File and directory names

Monospace, italic font • Code variables

Monospace, bold font Emphasis of file and directory names, system output, code, and

)

Web site addresses

• Text typed into a GUI element, such as into a box

• GUI elements that are clicked or selected, such as menu and

list items, buttons, and check boxes

• System output

• Code

• Text typed at the command-line

• Command-line variables

text typed at the command line

WARNING! Indicates that failure to follow directions could result in bodily harm or death.

xii

CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.

IMPORTANT: Provides clarifying information or specific instructions.

NOTE: Provides additional information.

TIP: Provides helpful hints and shortcuts.

HP technical support

Telephone numbers for worldwide technical support are listed on the HP support web site:

http://www.hp.com/support/

Collect the following information before calling:

• Technical support registration number (if applicable)

• Product serial numbers

• Product model names and numbers

• Applicable error messages

• Operating system type and revision level

• Detailed, specific questions

For continuous quality improvement, calls may be recorded or monitored.

HP strongly recommends that customers sign up online using the Subscriber's choice web site at

http://www.hp.com/go/e-updates

• Subscribing to this service provides you with e-mail updates on the latest product enhancements,

newest versions of drivers, and firmware documentation updates as well as instant access to numerous other product resources.

• After signing up, you can quickly locate your products by selecting Business support and then

Storage under Product Category.

HP-authorized reseller

For the name of your nearest HP-authorized reseller:

• In the United States, call 1-800-345-1518.

• Elsewhere, visit the HP web site: http://www.hp.com

and telephone numbers.

Helpful web sites

For third-party product information, see the following HP web sites:

• http://www.hp.com

• http://www.hp.com/go/storage

• http://www.hp.com/support/

. Then click Contact HP to find locations

User Guide xiii

xiv

1 SAP Adaptive Computing Overview

This chapter describes the following:

• SAP ACC overview, page 2

• Application Integration Software for SAP ACC, page 10

With the increasing complexity and inflexibility of the traditional SAP® environment, it has become necessary to rethink the way that a SAP environment is managed. With the SAP Adaptive Computing Controller (ACC), SAP has taken the first steps in improving the management of the SAP Landscape, and has provided a number of integration points for vendors to extend the Adaptive Computing Controller functionality.

This document describes the solution from Hewlett-Packard (HP) to extend an SAP Adaptive Computing environment to support Storage Area Network (SAN) attached storage from HP. The document provides background information about the adaptive computing concept and the specific integration points used by HP. This User Guide also describes the usage of the integrated solution with the SAP ACC in detail.

The basis of the SAP ACC is to virtualize the SAP application from the underlying computing environment, and arrange the software services together in a group of resources that can start, stop or be moved from any system, at any time, when needed, where needed. The process of abstracting the SAP software from the underlying hardware is known as Service Virtualization, and it requires that the SAP instance and all resources necessary for the virtual resource be independent of any physical system or system resource. This includes the IP address or host name for the software service as well as any storage used by the service.

The benefits of implementing an adaptive computing environment includes:

• Lower total cost of ownership (TCO)

• Better server utilization

• Better control of IT landscape

• Higher service levels at lower cost

• A standard approach to the four basic building blocks of you IT landscape: computing,

network, storage, and management

• Productivity

• Faster response time to business-driven needs

• Reduced operation complexity

• Flexibility

• Ability to assign and use hardware resources when needed

• Easy to add or modify hardware components in landscape

User Guide 1

SAP ACC overview

The following section provides some basic background on the structure and functionality of the SAP Adaptive Computing Controller (SAP ACC). For more detailed information, please refer to the documentation provided by SAP on this subject.

The following topics are covered in this section:

• The virtual SAP landscape, page 2

• SAP ACC components, page 4

• Virtual IP address, page 7

• Control, page 10

The virtual SAP landscape

To create an adaptive SAP landscape, it is necessary to have a virtual application setup. The application and all the resources belonging to the applications (network and storage) must be grouped together into one unit that can be moved from one system to another independent from anything else on the system.

The following figure describes the components to create a virtualized application.

Figure 1 The components to create a virtualized application

A SAP instance consists of network resources that includes a virtual host name and a virtual IP address. This virtual IP address is different from the dedicated server IP address assigned to the hardware. The virtual IP address of the application makes it possible to connect to the application, independent of the hardware, anywhere in the landscape.

The SAP instance also consists of physical storage, either Network Attached Storage (NAS) or Storage Area Network (SAN)-attached storage. The storage is made up of file systems located on logical devices (Ldev) from a storage system. The SAP ACC groups all the storage components of an instance under the Storage Resource Identifier (SRID) and lets you create a custom name for the storage component of the instance.

The HP Storage Essentials Storage Resource Management (SRM) Enterprise Edition Microsoft Windows Application Integration Software for SAP ACC provides a link between the SRID created in SAP and the physical storage resources that is associated with that instance. This allows HP Storage Essentials SRM to Present or Un-present this storage from any host in the SAN.

SAP Adaptive Computing Overview2

In the following figure, the virtual SAP instance is running on physical server HostA. The SAP Instance has two SAN-attached storage devices mapped from the storage array to the server.

Figure 2 Virtual SAP instance on physical server HostA

Let’s assume the SAP administrator decides that it is necessary to move this SAP instance from server HostA to server HostB due to business reasons or for maintenance. The SAP ACC initiates the service relocation action, and the Application Integration Software for SAP ACC ensures that the

User Guide 3

storage devices are removed from server HostA and are presented to server HostB. The following figure shows the status of the landscape after the service relocation is completed.

Figure 3 SAP instance is moved from HostA to HostB

The SAP ACC gives the SAP administrator the power and flexibility to stop, start or relocate any SAP instance to any system in the landscape when needed and on what is available.

SAP ACC components

SAP developed the ACC as a system management-like application based on the J2EE engine of the Web application server. The ACC software runs on a control node and interacts with other SAP components to create a full image of the entire SAP landscape. The SAP ACC also implements a component that runs on the managed node, enabling SAP to perform specific function on each node.

SAP Adaptive Computing Overview4

The following is a high level diagram of the SAP ACC Architecture.

Figure 4 Architecture for SAP Adaptive Computing Controller

The ACC station or Control node consists of the WebAS 6.40 J2EE Engine and the Adaptive Computing Controller software. The ACC software communicates with the System Landscape Directory (SLD) to derive a list of managed nodes installed in the SAP Landscape. Each managed node needs to register itself in the SLD Using remote function calls, and the SLD collect status information from the managed node using the saposcol agent installed on each managed node.

The ACC also requires the SAP instance-specific information from SAP® Solution Manager and obtains this information using remote function calls via the gateway process. The gateway process can be implemented either as a standalone or an integrated gateway system.

All Adaptive Computing operations are initiated and controlled from the SAP ACC control node using the GUI provided by SAP.

An SAP ACC agent is installed on each managed node in the system landscape that is under ACC control. This “sapacosprep” agent receives command operations from the central SAP ACC controller and executes the necessary integration modules to enable adaptive computing functions on the managed node.

Internally the “sapacosprep” agent comprises of a platform/partner independent module and an API that enables partners to integrate their platform and storage solutions by providing the

User Guide 5

necessary integration modules. The functions that the partner modules need to provide can be divided into two categories:

• Functions that are platform specific

• Activate an IP address

• Deactivate a virtual IP address

• Attach a network file system

• Detach a network file system

• Functions that are storage specific

• Attach a distributed file system

• Detach a distributed file system

• Attach a Storage Resource

• Detach a Storage Resource

Besides the two partner modules, SAP maintains and provides a common function module that provides:

• Setup and callback functions

• Return module version and information

SAP Adaptive Computing Overview6

The following figure provides an overview of the SAP ACC integration library, the functions implemented and the vendor integration point available.

Figure 5 Overview of the SAP ACC library

Keep in mind the following about Figure 5, “Overview of the SAP ACC library,” on page 7:

• The platform-specific modules are provided by each platform hardware/operating system

support team. For HP-UX these modules are provided by the HP SAP consulting and integration team for HP-UX. For Microsoft Windows and Linux platforms the modules are provided by the SAP support team.

• The storage-specific modules are provided by each storage vendor, but storage-specific modules

can also be platform-specific. The Application Integration Software for SAP ACC distributes this storage-specific module for HP StorageWorks arrays.

Virtual IP address

Adaptive Computing uses the concept of assigning a unique IP address and network name to the application, and by doing this, it separates the application from the physical host IP address. The process of using virtual IP addresses for applications is commonly used in all cluster systems, and all major operating system releases support the overloading of a network interface card with multiple IP addresses. The advantage here is you can always access the application through one unique name, no matter where the application is running.

User Guide 7

NOTE: To install or convert a SAP installation to a virtual landscape, the platform specific libraries

will be required to enable virtual IP addresses on the managed nodes.

Virtualized data

Adaptive Computing also implements the concept of virtualizing the application data into a single group of data devices (Storage Resources) that can be moved between physical managed nodes. The first requirement to accomplish data virtualization is to ensure that all the data required for the application is located on a dedicated set of storage devices. For the Application Integration Software for SAP ACC, it is required that all the storage devices for a specific SAP application are located on a central storage system with SAN access from all of the managed nodes. In the SAP ACC, the set of physical Storage Resources that are required for a specific SAP instance are identified by a Storage Resource Identifier (SRID). This identifier provides the link between the SAP ACC application and the Application Integration Software for SAP ACC.

The Application Integration Software for SAP ACC is specifically designed to support SAN-attached storage in an adaptive landscape.

SAP Adaptive Computing Overview8

The following diagram shows the relationships between physical storage devices and their usage on Windows systems.

Figure 6 Relationship between physical storage devices on different operating systems

Operating system disk management utilities lets you combine or subdivide the physical devices into custom-sized file systems, each with a specific mount point on the host.To successfully move physical resources between systems, without impacting other application, it is important to make sure that the physical drives and all associated objects belong only to the SAP instance identified by the SRID.

User Guide 9

Control

Controlling the adaptive landscape is performed from within the SAP application using the ACC software that is build on top of the SAP NetWeaver® application.

Application Integration Software for SAP ACC

To support a fully automated SAN storage movement between managed nodes, HP has developed the Application Integration Software for SAP ACC. The Application Integration Software for SAP ACC consists of the following parts:

• HP Storage Essentials SRM Enterprise Edition

• Active host management interface

• Application Integration Software for SAP ACC

HP Storage Essentials SRM Enterprise Edition

The HP Storage Essentials SRM Enterprise Edition product suite provides an integrated array management functionality for storage provisioning and managed node management. The Application Integration Software for SAP ACC is built on the HP Storage Essentials SRM API functions, and it utilizes the HP Storage Essentials SRM database for host objects and the storage management functions to present and un-present storage to/from any managed node in the landscape.

Active host management interface

The Application Integration Software for SAP ACC provides an active host management interface for HP SIM to perform active management on the managed nodes for storage management. For this to work, it is necessary to have all managed nodes discovered in HP SIM and HP Storage Essentials SRM and to configure a Secure Shell (OpenSSH) communication to each managed node.

Application Integration Software

The Application Integration Software has three main functions:

• Maintain relationship between Storage Resource Identifier (SRID) and the physical storage

devices - Since the SAP ACC does not maintain a list of physical devices associated to a SAP

instance, but rather only an identifier for the Storage Resources used by an SAP instance, it is necessary to maintain a link between the SRID used in the SAP ACC configuration and the list of physical devices used by the instance. The Application Integration Software for SAP ACC provides an interface that lets you easily associate the Storage Resource Identifier with a specific mount point and associated physical devices.

• Provide the interaction between SAP ACC and storage management - The Application

Integration Software for SAP ACC provides the vendor specific storage API (libsapacosprep_hp.dll) to integrate with the SAP “sapacosprep” agent on the managed node. The storage API forwards storage related requests to the Application Integration Software for SAP ACC.

• Implement the flow of operation necessary to “start”, “stop” or “relocate” Storage Resource

to/from a managed node - This includes the necessary actions on the managed node to

discover, configure and mount/unmount file systems on the individual computing systems and

SAP Adaptive Computing Overview10

storage array manipulation (to present and un-present storage to/from the managed node). The Application Integration Software for SAP ACC is also responsible to protect storage devices that are not currently accessed by any managed node.

User Guide 11

SAP Adaptive Computing Overview12

2 Creating an Adaptive Landscape

This chapter describes the following:

• SAP virtual landscape, page 13

• Configure the SAP ACC landscape, page 14

• Configure the SAP instance, page 15

How you create your adaptive landscape will depend on your environment:

• For new SAP installations, the landscape should be designed and implemented with

virtualization in mind, even if it is not planned to utilize virtualization at this stage. This step will eliminate the painful process of changing a landscape to support virtualization at a later stage, and it can also be used to support clustering solutions and operating system virtualization solutions.

• For the existing SAP landscapes that are not virtualized, it will be necessary to change the

hostname and IP addresses of most instances. This step can be a complex and time consuming task. Please consult with you SAP provider to plan the best way to modify the landscape.

NOTE: When creating a virtual landscape, use a DNS server and create roaming profiles for the

SAP admin users, and other users. This way all user and system data are centrally controlled and consistent on all nodes. It is also recommended to use a dedicate SAP Solution Manager server.

SAP virtual landscape

Installing a virtualized SAP system requires a dedicated network name (IP address and host name) for each SAP instance. This host name needs to be used when SAP is installed, instead of the fixed server name or IP address. For more details on installing a virtual SAP landscape, consult the SAP installation manuals and your SAP provider/integrator.

Keep the following in mind:

• The vendor-specific platform library is necessary to add the virtual IP address to the existing IP

address of the system. Access the following Web site to obtain the library for your operating system: http://service.sap.com/adaptive

This URL requires you to provide an SAP S-user ID. Once you login to the Web site, access the library as follows:

• Microsoft Windows and Linux - SAP provides the library for Microsoft Windows and Linux.

Follow the links for the library provided by SAP.

• HP-UX - The HP-UX SAP platform team provides the library, which is posted in the vendor

area of the Web site. Follow the vendor specific links for the library provided by the HP-UX SAP platform team.

User Guide 13

+ 63 hidden pages