HP Storage Essentials SRM Enterprise Edition 6.0 Microsoft Windows Application Integration Software for SAP ACC version A.02.
Legal and notice information © Copyright 2002-2007 Hewlett-Packard Development Company, L.P. 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.
Contents About this guide . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Central Instance Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Database Instance Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 The components to create a virtualized application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Virtual SAP instance on physical server HostA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 SAP instance is moved from HostA to HostB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Architecture for SAP Adaptive Computing Controller . . . . . . . . . . .
viii
Tables 1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x
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.
Document conventions and symbols Document conventions Table 1 Convention Element Medium blue text: Figure 1 Cross-reference links and e-mail addresses Medium blue, underlined text (http://www.hp.
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/.
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.
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.
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.
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.
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.
necessary integration modules.
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.
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 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.
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.
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.
12 SAP Adaptive Computing Overview
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.
NOTE: SAP ACC 1.0 is supported with NetWeaver 2004 only and not with 2004s. Always use the latest support pack recommended by SAP. Configure the SAP ACC landscape The following steps describe the high-level actions necessary to configure the SAP ACC landscape. For more detailed instructions, consult the SAP documentation for installing and configuring SAP adaptive computing. 1. Set up the SAP Solution Manager server. Apply the latest support packages and license. 2.
Configure the SAP instance In the SAP ACC software, it is necessary to define the appropriate Storage Vendor integration module to be used for each Adaptive enabled SAP instance. The following diagram is an example of how to configure the Storage integration in the SAP ACC interface: Figure 7 Configuring the Storage Integration in the SAP ACC Interface 1. Select the appropriate Sap Instance, and select Configuration. 2.
16 Creating an Adaptive Landscape
3 Install HP Storage Essentials SRM and HP SIM This chapter describes the following: • User account, page 17 • Storage system considerations, page 17 IMPORTANT: Refer to the release notes to determine which versions of HP Storage Essentials Storage Resource Management (SRM) and HP Systems Insight Manager (SIM) are supported. Prior to installing the Application Integration Software for SAP ACC, HP Storage Essentials SRM and HP SIM must be installed and configured.
• SAN zoning, page 18 • Host groups, page 18 • Reserved-Group, page 18 SAN zoning For a Managed Node to be able to access the physical storage device, it has to be physically connected to the storage array using a Storage Area Network (SAN). If any zone security is implemented in the SAN, the Managed Node must be added to the appropriate SAN zone for the Managed Node to have logical access to the storage array.
4 Install the Application Integration Software for SAP ACC This chapter describes the following: • Requirements, page 19 • Installation Steps, page 19 • Installation Checks, page 23 • Removing the Application Integration Software for SAP ACC, page 24 Requirements The Application Integration Software for SAP ACC is dependant on the prior successful installation of the following software components on the same server: • HP Storage Essentials SRM Enterprise Edition software • HP System Insight Manager • The
NOTE: If setup.exe is run from a shared drive, a warning message might appear asking for confirmation if the application is save to run. Click OK to start the install shield. The end user license agreement appears. Figure 8 Accepting the license agreement 2. Click Next to continue. 3. Enter the install location.
The installation program prompts for an installation location. Figure 9 Choose a destination folder Default location to install the Application Integration Software for SAP ACC is%SystemDrive%\Program File\HP\SE_SAP_ACC_Integration To change the default installation location, click the Browse button and select the alternative location. NOTE: It is recommended to use the default installation location. 4. Click the Next button to continue. 5. Enter the port number, domain, user names, and passwords.
b. Service Monitor Port: listens for the service to connect and monitor the status of HP Storage Essentials SRM SAP ACC Integration Core. c. Configuration port 1: listens for communications with the HP Storage Essentials SRM SAP ACC Integration Configuration Web interface. d. Configuration Port 2: a second port to listen for communications with the HP Storage Essentials SRM SAP ACC Integration Configuration Web interface.
6. Finish the installation by clicking Finish.
IMPORTANT: Verify that the AppStorManager service has started. The AppStorManager service runs HP Storage Essentials SRM. Although the Application Integration Software for SAP ACC depends on the AppStorManager service running, the AppStorManager service is not part of the Application Integration Software for SAP ACC.
5 Interprocess Communications This chapter describes ”Installing OpenSSH” on page 25. The Adaptive Computing Integration Software uses different communication methods to enable all the different components to communicate with each other. For successful implementation, it is necessary to understand the communication methods and the dependencies between products. The following diagram displays a summary of the inter-process communications in the adaptive landscape.
Setup and Configuration on the Storage Essentials Server 1. Install OpenSSH through the HP SIM GUI to the managed nodes using a common local administrator account. IMPORTANT: The local administrator account must be valid on all managed nodes for HP SIM to successfully install tools.
7. Configure c:\OpenSSH\etc\sshd_config. Set the parameters: RSAAuthentication yes PasswordAuthentication no 8. Create a file to map the domain users to ssh users. Open a command prompt and enter: Cd c:\OpenSSH\etc ..\bin\mkpasswd –d > passwd 9. Create a home directory for the SAP ACC Administrator or the SAPService username. For example: mkdir c:\OpenSSH\home\SAPServiceJ2E 10.Delete the file c:\OpenSSH\var\log\OpenSSH.log to avoid permission problems when restarting the service as the administrator.
28 Interprocess Communications
6 Install the Integration Library on Managed Nodes This chapter describes the following: • Installing the storage specific integration library on SAP hosts, page 29 • Updating the storage specific integration library on SAP hosts, page 31 The HP Storage Essentials SRM SAP ACC Integration Software contains a feature that installs/updates components onto the managed nodes.
NOTE: The can either be the local host domain or the global domain, depending on what you used to install HP SIM and HP Storage Essentials SRM. For a successful authentication, the username and password must match a username and password recognized by Storage Essentials. The match must be letter-by-letter and case sensitive. 4. Click the Integration Library tab.
NOTE: This version only supports one host installation at a time. Figure 15 Install/Upgrade Integration Library window The dialog confirms the version number of the Integration Library that is about to be installed on the selected host. This will always list the latest version of the library that is installed on the local server. 6. To start the installation of the library on the SAP host, click the Install/Upgrade button.
32 Install the Integration Library on Managed Nodes
7 Record Storage Resources information This chapter provides information about the following • Adding a Storage Resource Identifier, page 33 • Viewing resource information, page 40 • Removing a Storage Resource Identifier, page 41 Adding a Storage Resource Identifier The HP Storage Essentials SRM SAP ACC Integration Software saves the Storage Resource Identifiers (SRIDs) in the Integration Software’s database.
The following login page is displayed. Figure 16 Login page 3. Enter the user name and password to connect to the HP Storage Essentials SRM server. The format of the user name is \username. After successful authentication, the HP Storage Essentials SRM SAP ACC integration Main window is displayed. The list of Storage Resources is empty the first time you add a resource. 4. Click the Add button to add a Storage Resource. The Add Storage Resource page is displayed.
5. Enter the Storage Resource ID in the Storage Resource Name field. The Storage Resource ID you enter in this field must match the Storage Resource ID used in the SAP ACC interface when defining the storage for the specific SAP instance. Figure 17 The Add Storage Resource page 6. Add a Storage Resource group name, or select a name from the list of existing Storage Resource groups. This field is only used to sort the defined Storage Resources on the Main menu, and it has no other functional value.
A list of active file systems on the selected host are displayed. Detailed information for each file system is displayed in the table. Figure 18 Associate physical storage to storage resources 10.Select a file system that is part of the SAP instance. Multiple file systems can be selected. A file system can only belong to one Storage Resource at any time.
In the HP StorageWorks XP array, a storage device not presented to any host or host port is considered a free or available device, and will be available to be used whenever new storage is required.
Figure 20 Confirm details for new storage resource 13.Click the Finish button. The Storage Resource is added to the HP Storage Essentials SRM SAP ACC Integration Software configuration files. The physical devices are also added to the reserved group on the specific array. The reserved group is also created if this is the first Storage Resource for that array.
NOTE: This process can take some time, due to storage provisioning to the reserve pool. After successful completion of adding a Storage Resource the HP Storage Essentials SRM SAP ACC Integration Software returns to the main screen and the newly added Storage Resource is displayed in the table of configured Storage Resources. Figure 21 Newly added storage resource is displayed The Status column displays the current status of this storage.
NOTE: The HP SAP ACC Integration Software displays the last known status for the resource. Any status change done without the knowledge of the Integration Software, for example a manual change, can result in the status information being incorrect. NOTE: If mounting or dismounting a resource is interrupted prior to completion, the status may be displayed as Dismounting or Mounting.
The Storage Resource Properties window appears. Figure 22 Storage Resource Properties Removing a Storage Resource Identifier A storage resource can be removed by selecting the resource on the main screen and clicking Remove.
Figure 23 Removing a storage resource 42 Record Storage Resources information
A confirmation screen is displayed with two check boxes. A Storage Resource can be in one of two states at the time of deletion form the HP Storage Essentials SRM SAP ACC Application Integration Software. • Mounted: If the resource is mounted and therefore presented to a host, the delete operation only removes the configuration information from the local configuration files and removes the physical devices from the reserved group.
44 Record Storage Resources information
8 Application Logs The log files for all storage operations are located on the HP Storage Essentials SRM server under%SystemDrive%\Program File\HP\SE SAP ACC Integration\logs folder, and it can also be accessed by selecting the Application Log tab on the main screen.
The Application Log page lets you filter the log file for the following: • a time period • a host • SRID • type of event To view the application log entries, enter a start date and time in the mm/dd/yyyy hh:mm AM|PM format, for example 1/15/2007 1:30 AM. You can add any other filter options as necessary, then click the Refresh button. To see more details about an event, select the check box next to the event description and then click Properties.
The HP Storage Essentials SRM SAP ACC Integration Software creates a new log file monthly. Old log files remain in the log directory. You can remove the old log files manually from the%SystemDrive%\Program Files\HP\SE SAP ACC Integration\logs directory.
48 Application Logs
9 Program Properties This chapter describes the following: • Changing the user name and password used for communicating with HP Storage Essentials SRM, page 49 • Changing the reserve group assignment, page 50 Use the Program Properties tab to do one or more of the following: • Modify the user name and/or password used for communicating with HP Storage Essentials SRM. • Change the reserve group assignment.
4. Click Save Changes. Figure 26 Program Properties page Changing the reserve group assignment To change the reserve group assignment for a specific array: 1. Click the Program Properties tab from the Main Menu. 2. Select the array to be modified. 3. Click Properties.
The following page is displayed. Figure 27 Modify reserve group assignment 4. Change the port number or the name of the Reserve-Group on the array for the reserved group. The port number selected for the reserved group should be a Target or RCU Target port with security enabled. The HP Storage Essentials SRM SAP ACC integration software will create a host group with default name SAP ACC Reserved on this port and assign all the physical devices used in the Adaptive Computing environment to this group.
52 Program Properties
10 Operational Details This chapter describes the following: • Operational information, page 53 • Location of important log files, page 57 • Common issues, page 58 Operational information The movement of the application is initiated and controlled from the SAP ACC interface. The administrator has a choice from three operations: start, stop, or relocate a resource, where relocate is a combination of stopping on one Managed Node and starting on the next.
Figure 28: Flow diagram of operational details This flow diagram can also be used to trace any issues and to determine which log file to look at for failure events. 1. Lock Managed Node. This is an SAP ACC operation to lock any other ACC operations for the specific Managed Node, to ensure that only one operation will be performed on any node at any time. If some other node is already performing an operation, the new request will be on hold until the previous operation complete.
Check the OpenSSH installation, and manually test communications between SAP ACC server and the Managed Node. 3. SAP ACC verifies the “sapacosprep.exe” installation and version by running the “sapacosprep -diag” command. The following is the typical output for this command: SAPACOSPrep information: program version: 1.0.
This is an internal check from the Integration core service to ensure that the Managed node is accessible and configured in the Application Integration Software. If the Managed Node is not accessible, a potential problem can be that communication between OpenSSH from HP-SIM server to Managed Node is broken. Check the OpenSSH installation and run the specified communication checks (see “Installing OpenSSH” on page 32) to ensure communication from HP Storage Essentials SRM and HP SIM to Managed Node.
NOTE: If deactivating the IP address fails, SAP might incorrectly indicate that the instance is “running” on this managed node. In SAP ACC 1.0, SAP assumes that the instance is running if the virtual IP address of the instance is available, and it is not necessarily if the application is up and running. 12.Unlock Managed Node. The last step in the operation is for SAP ACC to unlock the managed node and allow for any other operations to be executed on this managed node.
Common issues HP Storage Essentials SRM SAP ACC Integration Library call fails. 1. If the SAP ACC process does not perform the “sapacosprep storage Library function AcDetachSr/AcAttachSr” operation, make sure that storage resource for this instance is configured as type “SR” and that Partner ID field is set to HP. 2. Ensure that the “sapacosprep -diag” call does recognize the HP Library “libsapacosprep_hp.dll”.
1. (Optional) Schedule a Run Discovery Data Collection operation to refresh all HP Storage Essentials SRM element data. This operation should be scheduled to run at an off-peak hours when SAP ACC Integration is not being used. 2. Perform a manual Run Discovery Data Collection operation after any manual changes on the storage array or managed nodes.
60 Operational Details
11 Application Scripts Description and Usage This chapter describes how to customize sample scripts that let you start and stop the SAP Central Instance (CI) and the SAP Database (DB) Instance. To use SAP application services in the Adaptive Computing Controller (ACC), it is required to have a CI and a DB Instance installed. To be able to start an SAP application service instance on a virtual hostname, it is necessary to use start and stop scripts.
• Database Instance • Dialog Instance Further information regarding instances is available in SAP's documentation1. Dialog instances are beyond the scope of this chapter. The following sections provide a high-level overview of SAP instance terminology. For further information, refer to related SAP documentation, such as the SAP DB documentation (http://www.sapdb.org/sap_db_documentation.htm) and SAP Adaptive Computing documentation (http://service.sap.com/adaptive).
running command scripts that implement these operations. The operations, and the scripts that implement them, must be executed in the following order: 1. Start the SAP Central Instance 2. Attach the SAP Database Instance 3. Detach the SAP Database Instance 4. Delete the SAP Central Instance NOTE: Each step must run successfully before the following step can be started.
You can use these sample scripts as a reference for developing scripts customized to perform those operations on your system. The sample scripts were designed for Microsoft Windows. The scripts provided are the following: • prepareCI.cmd.rename: sample script that includes commands to install and start the SAP Central Instance. • attachDB.cmd.rename: sample script that includes commands to attach the Database Instance. • detachDB.cmd.
• Implementation, page 65 Sample Input Parameters A script designed to start the SAP Central Instance services for a particular system must be provided with the following input parameters: • SID: System ID of the SAP system installed on the Managed Node • VHOST: Virtual hostname of the SAP CI • DBHOST: Virtual hostname of the server running the DB instance • SAPGLOB: Hostname of the SAP global host. This value is usually the hostname of the CI.
4. If the SAP Java instance is supported, it must be started before the Central Instance is started. In this case, use SAPSTARTSRV.EXE to register the Java start profile, the SAP service user ID, and the user environment. In the sample script, this is represented by the variables JAVA_START_PROFILE, %USERDOMAIN%\%SAPService%SID%, and %USERDOMAIN%\%SID%adm. Include a waiting time (around 10 seconds) for the Java instance to start. 5. Start the Central Instance using SAPSTARTSRV.EXE.
This section describes the following: • Sample Input Parameters, page 67 • Implementation, page 67 Sample Input Parameters A script designed to attach the SAP Database Instance for a particular system must be provided with the following input parameter: • SID: System ID of the SAP system installed on the Managed Node The command line interface for this script is the following: attachDB.cmd SID The header in the attachDB.cmd.
4. This script can be further improved by adding code that displays additional error messages if any of the preceding steps is not completed. This is also illustrated in the sample script provided. After customizing the script, verify that the script has successfully attached the Database Instance. This process may vary depending on the particular system. Consult the corresponding vendor documentation.
4. This script can be further improved by adding code that displays additional error messages if any of the preceding steps is not completed. This is also illustrated in the sample script provided. After customizing the script, verify that the script has successfully detached the Database Instance. This process may vary depending on the particular system. Consult the corresponding vendor documentation.
2. Stop the SAP Central Instance. This can be implemented by running the stopsap command, as shown in the sample script: %SYSTEMDRIVE%\usr\sap%SID%\%SID%\sys\exe\run\stopsap name=%SID% nr=%INR% SAPDIAHOST=%CI% 3. Stop the SAP SID service. This step is implemented in the sample script as follows: sc stop SAP%SID%_%INR% 4. Delete the SAP SID service. The sample script uses the following command: %SYSTEMDRIVE%\usr\sap%SID%\%SID%\sys\exe\run\SAPSTARTSRV.
Configuring SAP to Run Customized Scripts This section describes the procedure to run a customized script using the SAP GUI. It is assumed that the SAP administrator has developed a customized script compatible with the SAP landscape. It is also assumed that the SAP Administrator is familiar using SAP's Transaction SMSY. Otherwise, it is recommended to read the corresponding SAP documentation8 before reading this section.
This configuration allows the customized scripts to be launched by SAP when required. Troubleshooting This section provides troubleshooting procedures to use if there are problems executing the scripts as explained in the following sections: • Central Instance Scripts, page 72 • Database Instance Scripts, page 72 Central Instance Scripts If the scripts developed for a particular system fail to start or stop the SAP Central Instance, the following troubleshooting procedure can be followed: 1.
7. Manually stop and restart the SQL database service processes. Check that no other user is currently accessing the SQL database before performing this step. 8. Use the SQL server to verify that the SQL stored procedures developed for the installation system are running properly. Run those stored procedures again if necessary. Check the SQL server logs to further troubleshoot the issue. Verify that the stored procedures are producing the required output. 9.
74 Application Scripts Description and Usage
Index A adaptive landscape creating 13 adding Storage Resource Identifier 33 administrator account 17 Application Integration Software checking installation 23 installing 19 overview 1 removing 24 requirements 19 application logs 45 application scripts 61 troubleshooting 72 attachDB.cmd.
logging 45 M missing elements 58 modifying connection information for HP Storage Essentials SRM 49 reserved group assignments 50 mount error 59 mx.log 57 N Networking xi O OpenSSH 25 installing 25 operational infromation 53 out of sync information 58 overview 1 P password HP Storage Essentials SRM 49 password changes 49 prepareCI.cmd.
