FlexFrame for SAP 4 - Fujitsumanuals.ts.fujitsu.com/file/6791/ff4s-acc_install.pdf · SAP® and NetWeaver™ are trademarks or registered trademarks of SAP AG in Germany and ... ORACLE

User Guide

FlexFrame™ for SAP® 4.0Installation ACC 1.0 SP13

English

FlexFrame™ for SAP® Version 4.0

Installation ACC 1.0 SP13

Edition March 2007 Document Version 1.0

Fujitsu Siemens Computers GmbH

© Copyright Fujitsu Siemens Computers GmbH 2007 FlexFrame™, PRIMECLUSTER™. PRIMEPOWER™ and PRIMERGY™ are trademarks of Fujitsu Siemens Computers SPARC64® is a registered trademark of Fujitsu Ltd. SAP® and NetWeaver™ are trademarks or registered trademarks of SAP AG in Germany and in several other countries Linux® is a registered trademark of Linus Torvalds SUSE® Linux is a registered trademark of Novell, Inc., in the United States and other countries Java™ and Solaris™ are trademarks of Sun Microsystems, Inc. in the United States and other countries Intel® and PXE® are registered trademarks of Intel Corporation in the United States and other countries MaxDB® is a registered trademark of MySQL AB, Sweden MySQL® is a registered trademark of MySQL AB, Sweden NetApp®, Network Appliance®, Open Network Technology for Appliance Products™, Write Anywhere File Layout™ and WAFL™ are trademarks or registered trademarks of Network Appilance, Inc. in the United States and other countries Oracle® is a registered trademark of ORACLE Corporation EMC®, CLARiiON®, Symmetrix®, PowerPath®, Celerra™ and SnapSure™ are trademarks or registered trademarks of EMC Corporation in the United States and other countries SPARC™ is a trademark of SPARC International, Inc. in the United States and other countries Ethernet® is a registered trademark of XEROX, Inc., Digital Equipment Corporation and Intel Corporation Windows®, Excel® and Word® are registered trademarks of Microsoft Corporation All other hardware and software names used are trademarks of their respective companies. All rights, including rights of translation, reproduction by printing, copying or similar methods, in part or in whole, are reserved. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Delivery subject to availability. Right of technical modification reserved.


Contents 1 Introduction ..................................................................................................... 1 1.1 Requirements .................................................................................................... 1 1.2 Notational Conventions ..................................................................................... 1 1.3 Document History.............................................................................................. 1 1.4 Related Documents........................................................................................... 2

2 General Preparations ...................................................................................... 3 2.1 Required Software for an ACC Environment ..................................................... 3 2.2 Documentation .................................................................................................. 3

3 Installation of Solution Manager 3.2 SR1 ...................................................... 5 3.1 Applying SAP Support Patches......................................................................... 5

4 Installation of WebAS 6.40 with NetWeaver 04 SR1 ..................................... 7 4.1 Applying SAP Support Patches......................................................................... 7 4.2 Installation of WebAS 6.40 SP18 ...................................................................... 7 4.3 Changing Startup Mode for SSL........................................................................ 8 4.3.1 Procedure.......................................................................................................... 8 4.3.2 Result ................................................................................................................ 8

5 ACC Installation............................................................................................... 9 5.1 ACC Patch Installation .................................................................................... 12 5.2 Post Installation Activities................................................................................ 21

6 Configuration of ACC.................................................................................... 27 6.1 User Administration for ACC Users ................................................................. 27 6.1.1 Creating Users ................................................................................................ 27 6.1.2 Checking and Creating Roles.......................................................................... 30 6.1.3 Checking and Creating Groups ....................................................................... 36 6.1.4 Assigning Roles to Groups.............................................................................. 40 6.1.5 Assigning Users to Groups.............................................................................. 44 6.2 Configuration of the SLD ................................................................................. 50 6.2.1 Configuration of the SLD Connection to the J2EE Engine .............................. 55 6.3 Registering Managed Application Services into SLD ...................................... 60 6.3.1 ABAP System.................................................................................................. 60 6.3.2 Java System.................................................................................................... 64 6.4 ACC Agents..................................................................................................... 68 6.4.1 Installing ACC Agents ..................................................................................... 68 6.4.2 Setting up sapacoscol and sapacosprep......................................................... 69 6.4.3 Setting up sldreg ............................................................................................. 70 6.4.4 Setting up sapacusrexit ................................................................................... 71 6.4.5 Starting ACC Agents ....................................................................................... 75

Introduction Requirements


6.5 Configuring SSH.............................................................................................. 79 6.6 Configuration of Connections between SolMan and ACC ............................... 81 6.6.1 Creating SAP Services User SAPJSF ............................................................. 81 6.6.2 Connection Configuration in the ACC with Visual Administrator...................... 94 6.6.3 Configuration of Connections in the Solution Manager.................................... 97 6.7 Data Transfers from SLD to Solution Manager.............................................. 106 6.7.1 Configuration ................................................................................................. 106 6.7.2 Activate and Check Transfer from SLD to Solution Manager ........................ 109 6.8 Making the Landscape Adaptive.................................................................... 113 6.8.1 Start of ACC .................................................................................................. 113 6.8.2 Configuring Network ...................................................................................... 115 6.8.3 Configuring ACC-Pools ................................................................................. 116 6.8.4 Adaptive Enabled Computing Nodes............................................................. 117 6.8.5 Adaptive Enabled Application Services Using Solution Manager .................. 121 6.9 Integration of SAP Services........................................................................... 122 6.9.1 Integration of an ABAP and ABAP+JAVA Central Instance........................... 122 6.9.2 Integration of an ABAP Application Service................................................... 126 6.9.3 Integration of a Database Service ................................................................. 128 6.9.4 Integration of a Java Central Instance ........................................................... 132 6.9.5 Integration of a Java Application Instance ..................................................... 135 6.9.6 Final Configuration for the Application Services ............................................ 137 6.9.7 Repeat the procedure with the next service.Start/Stop/Relocate

Application Services ...................................................................................... 143 6.9.8 Multiple Services on one Server .................................................................... 144

7 Troubleshooting .......................................................................................... 145 7.1 J2EE Server is Restarting.............................................................................. 145 7.2 Error by SMSY_Setup ................................................................................... 146 7.3 RZ70 Failed ................................................................................................... 146 7.4 SDM Error ACC SP07 ................................................................................... 146 7.5 SDM Password Change ................................................................................ 147 7.6 ACC Installation Failed .................................................................................. 147

8 Abbreviations............................................................................................... 149

9 Glossary ....................................................................................................... 153

10 Index ............................................................................................................. 159

Installation ACC 1.0 SP13 1

1 Introduction

1.1 Requirements This document addresses administrators on FlexFrame environments. We assume that the reader of this document has technical background knowledge in the areas of operating systems (Linux®, Solaris™), IP networking and SAP® basis.

1.2 Notational Conventions The following conventions are used in this manual:

Additional information that should be observed.

Warning that must be observed.

fixed font Names of paths, files, commands, and system output.

<fixed font> Names of variables.

fixed font User inputs in command examples (if applicable using <> with variables).

1.3 Document History Document Version Changes Date

1.0 First Edition 2007-03-08

Introduction Related Documents

2 Installation ACC 1.0 SP13

1.4 Related Documents FlexFrame™ for SAP® – Planning Tool

FlexFrame™ for SAP® – Installation of a FlexFrame Environment

FlexFrame™ for SAP® – Installation Guide for SAP Solutions

FlexFrame™ for SAP® – Administration and Operation

FlexFrame™ for SAP® – Network Design and Configuration Guide

FlexFrame™ for SAP® – FA Agents - Installation and Administration

FlexFrame™ for SAP® – myAMC.FA_LogAgent - Concept and Usage

FlexFrame™ for SAP® – Upgrading FlexFrame 3.1 or 3.2 to 4.0

FlexFrame™ for SAP® – White Paper

PRIMECLUSTER Documentation

ServerView Documentation

SUSE Linux Enterprise Server Documentation

Solaris Documentation


2 General Preparations

2.1 Required Software for an ACC Environment ● Solution Manager 3.2 with the most current available ST320 patchlevel (at least

Patch 0012) with a released DB version.

● WebAS 6.40 J2EE only installation with the most current available SP (at least SP18) with a released DB version. (For ACC only: ORACLE for Solaris_64 and ORACLE or MAXDB for Linux).

● Java version 1.4.2_12 necessary for WebAS 6.40 J2EE SP18

● ACC 1.0 with the most current available SP (at least SP13):

– CD No. 51031424 SP8 and CD 51031591 SP8 for LinuxX86_64

– The latest SP from http://service.sap.com/adaptive

● ACC 1.0 Agents (at least 1.0.13.0) from http://service.sap.com/adaptive

● All ABAP systems that are to be managed need to be on a patchlevel that provides the RZ70 transaction.

2.2 Documentation The following documents provide detailed information on SAP ACC:

● This guide (FSC) ● Installation Guide for SAP Solutions (FSC) ● ACCReadMe.pdf ● ACCRelease.pdf ● ACCImplementation.pdf ● ACCInstallation.pdf ● ACCSecurity.pdf ● ACCCustomizing.pdf ● Installation Guide for SAP Solution Manager 3.2 PART I+II ● Installation Guide for the relevant database ● Installation Guide for WebAS 6.40 ● Ongoing SAP notes for all the above software installations ● Special Adaptive Computing Collection note: 725397 ● Support Package 13 for ACC note 943632

General Preparations Documentation


Before installing SAP Enterprise on FlexFrame, please refer to the original SAP installation guide. Get the latest SAP Notes from the SAPNET:

http://service.sap.com

Please make sure that the FA Application Agents are stopped on the hosts that you are installing SAP Software on.

Sample System for this Document:

This document refers to the following examples:

OAC = SID for WEBAS 6.40 J2EE (ACC) installation

OSM = SID for Solution Manager 3.2

baby_3 = Host for OSM installation

baby_4 = Host for OAC installation

karl = Pool name

jcoac = Virtual host name of ACC system

ciosm = Virtual host name of SolMan system

control1 = Control Node 1


3 Installation of Solution Manager 3.2 SR1

The installation process is the same as for WebAS 6.20. Please refer to the “Installation Guide for SAP® Solutions“, chapter “Installing WebAS 6.20”.

3.1 Applying SAP Support Patches For using ACC, it s necessary to have Solution Manager up to the latest patch level.

Please be careful when applying support patches, it is recommended to refer to the SAP note 782140.

Therefore, at the time of writing this document you have to apply the following patches:

● Kernel update to newest version ● SPAM update to newest version (>= 620/19) ● BASIS Support Package: SAPKB62053-SAPKB62058 ● ABA Support Package: SAPKA62053-SAPKA62058 ● SAP Solution Manager Tool Patch: SAPKITL319-SAPKITL322


4 Installation of WebAS 6.40 with NetWeaver 04 SR1

Please refer to the “Installation Guide for SAP® Solutions“, chapter “Installing WebAS 6.40 with NetWeaver 04 SR1”.

4.1 Applying SAP Support Patches For using ACC, it is necessary to have WebAS 6.40 up to the latest patch level.

Therefore, at the time of writing this document you have to apply Support Package 18.

For further information, please refer to the “Installation Guide for SAP® Solutions”, chapter “Web AS 6.40 Deployment SP”.

4.2 Installation of WebAS 6.40 SP18 Before starting sapinst, do the following steps:

Start the Config Tool with configtool.sh.

Installation of WebAS 6.40 with NetWeaver 04 SR1 Changing Startup Mode for SSL


Set the key bindHost to the IP-Address of jc<sid>.

Press save and 2 times ok and run sapjc <SID> restart.

Start the standard SP18 installation procedure with SAPINST_USE_HOSTNAME=jc<sid>

4.3 Changing Startup Mode for SSL If you need secure connections, you have to have the SAP Cryptographic Software installed, during installation of WebAS 6.40The following sections describe the activation.

4.3.1 Procedure Use the Configuration Adapter in the Visual Administrator to change the startup mode for the SSL Provider. Adjust the mode for both, the dispatcher and each server.

Do the following in the Visual Administrator: ...

1. Choose Server → Services → Configuration Adapter.

2. Expand Configurations → cluster_data → <dispatcher/server> → cfg → services.

3. Switch to edit mode (Choose .) Confirm with Yes.

4. Select Propertysheet ssl-runtime and choose the symbol for Show the details of the selected node ( ).

5. In the Change Configuration dialog, select start-up mode. The Change property entry dialog appears.

6. In the Custom field, enter the value always and choose Apply custom.

7. You are taken to the Change Configuration dialog.

8. Choose OK.

Specify the option for both the J2EE dispatcher and the server(s).

4.3.2 Result The next time the J2EE dispatcher or server is started, the SSL Provider service will be automatically started as well.


5 ACC Installation The following chapter describes how to …

● Install ACC 1.0 with integrated SP 08 from CD ● Install ACC Patch SP 13

The WebAS 6.40 should be up and running and a valid license should be installed (via Visual Admin tool).

Create the SAP ACC installation directory:

baby_4:~ # cd /usr/sap/OAC/install baby_4:~ # mkdir OACACC baby_4:~ # chmod 777 OACACC baby_4:~ # cd OACACC baby_4:~ # JAVA_HOME=/usr/java/j2sdk1.4.2_12 baby_4:~ # export JAVA_HOME baby_4:~ # SAPINST_JRE_HOME=/usr/java/j2sdk1.4.2_12 baby_4:~ # export SAPINST_JRE_HOME

Start the SAP ACC installation (using CD51031424 or CD51031591 for LinuxX86_64 ACC1.0 SP8 Installation CD):

baby_4:/usr/sap/OAC/install/OACACC # ....../SAPINST/UNIX/SUNOS_64/sapinst -extract . . . iamodrfc.so: ok iamodsdm.so: ok iamodwas.so: ok iarfclib642.so: ok Done # ....../SAPINST/UNIX/SUNOS_64/sapinst SAPINST_USE_HOSTNAME=jcoac ....../SAPINST/UNIX/SUNOS_64/product.catalog guiengine: no GUI connected; waiting for a connection on host baby_4, port 21212 to continue with the installation guiengine: login in process.

ACC Installation Changing Startup Mode for SSL


Installation is running.

Changing Startup Mode for SSL ACC Installation


Installation of ACC has finished, click on OK.

ACC Installation ACC Patch Installation


5.1 ACC Patch Installation After finishing the ACC installation successfully, proceed with the patch installation:

# cd /usr/sap/OAC/install # mkdir OACACCPATCH # chmod 777 OACACCPATCH # cd OACACCPATCH

After downloading the latest patch set (at the moment Patch 13) from SAP Service Marketplace, do:

# ls # ACCONL13_0-10002986.SCA ACC13_0-10002986.SCA # /usr/sap/OAC/JC04/SDM/program/RemoteGui.sh

Click the connect button, enter the password of SDM and click on Login.

ACC Patch Installation ACC Installation


Choose the Deployment card and click the “+” button.

Navigate to the install directory and select ACCONL13... first. Then click on the Choose button.



Click the Next button.



Click the Next button.



Click the Start Deployment button.



Click the Confirm button when the deployment has finished successfully.



Click the “+” Button.

Select ACC13… file and press the Choose button

In the next two windows, click the Next button.



Click the Start Deployment button.

Click the Yes button.



Click the Confirm button if all deployments were successful.

Post Installation Activities ACC Installation


Leave the SDM RemoteGUI by choosing Exit from the menu.

5.2 Post Installation Activities After the installation, please follow the steps below.

See also the ACC Implementation Guide (Setting the Properties Values).

control1:~ # ssh -X oacadm@baby_4 oacadm@baby_4's password: baby_4:oacadm 38> JAVA_HOME=/usr/java/j2sdk1.4.2_12 baby_4:oacadm 39> export JAVA_HOME baby_4:oacadm 40> cd /usr/sap/OAC/JC04/j2ee/configtool/ baby_4:oacadm 41> ./configtool.sh

ACC Installation Post Installation Activities


Click the Yes button.



Navigate to com.sap.aci.DAL.



Type in your specific values for each line and click on the Set button.

In the example, the following URL is used: http://jcoac:50400/webdynpro/dispatcher/sap.com/ca~ac~acc~accadministrationtools/AdministrationTools

You may as well specify a https: URL:

https://jcoac:50401/.....

If the SSL Provider is activated see section “Changing Startup Mode for SSL” on page 8.

For password, enter the password for user sapjsf.

The user sapjsf will be created later, so make sure to remember the password.

After changing the parameters, click on the Floppy disk symbol to save your data.

For using multiple services on one host, you have to fill in (ACC.Control.MultiService) the key form SAP (refer to section “Multiple Services on one Server“on page 144).



Press OK.

Stop the Config Tool by choosing File -> Exit.



baby_4:~ # su - oacadm baby_4:~ # stopsap JC04 jcoac Checking OAC Database ------------------------------ ABAP Database is not available via R3trans Checking OAC Database ------------------------------ J2EE Database is running See logfile JdbcCon.log Stopping the SAP instance JC04 ---------------------------------- Shutdown-Log is written to /home_sap/oacadm/stopsap_JC04.log Instance on host baby_4 stopped Waiting for cleanup of resources........ . baby_4:~ # stopsap SCS03 scsoac ... baby_4:~ # stopj2eedb … ...

Restart the ACC system with the FlexFrame start/stop scripts.

baby_4:~ # sapdb OAC start baby_4:~ # sapscs OAC start baby_4:~ # sapjc OAC start


6 Configuration of ACC

6.1 User Administration for ACC Users The Adaptive Computing Controller 1.0 Security Guide can be found here:

http://service.sap.com/securityguide

6.1.1 Creating Users Login to the user administration page:

http://jcoac:50400/useradmin

Insert user administrator and password and click on Log on.

Configuration of ACC User Administration for ACC Users


Select Create User, fill in general Information and click on create. You can create users e.g. accuser, Observer, Operator, …

Don’t forget to login after creating a user to change your password!

User Administration for ACC Users Configuration of ACC


Login and change your password.



6.1.2 Checking and Creating Roles

Click on Roles.



Click on the binocular symbol to check if the roles are there.



Click on Create New.



Insert Role Name ACC_Observing:

1. Fill in Role Name: ACC_Observing

2. Select Available Actions. ca~ac~acc~accadministrationtools.Observing

3. Add to Selected Actions.

4. Click on Save.

1.

3.

2.

4.



Repeat the above steps for the following role names and actions:

Role Name Action

ACC_Observing Ca~ac~acc~accadministrationtools.Observing

ACC_Operation Ca~ac~acc~accadministrationtools.Operation

ACC_Configuration Ca~ac~acc~accadministrationtools.Configuration

Ca~ac~acc~accadministrationtools.ServerEnable

Ca~ac~acc~accadministrationtools.Schedule

Ca~ac~acc~accadministrationtools.CustomizeLink

ACC_Archiving Ca~ac~acc~accadministrationtools.Archiving





6.1.3 Checking and Creating Groups

1. Click on Groups

2. Click on the binocular symbol to check if the groups above are there.

3. Click on create groups.

1.

3.

2.



Fill in the group name AC_Observer and save.



Repeat the steps for the following groups: AC_Operator and AC_Administrator.





6.1.4 Assigning Roles to Groups

Select Roles and select the first role. Click on Assign groups to.



Click on “+” to open the Search/Select Groups window.

Click on the binocular symbol for searching.



Select AC_Administrator and press Select button.



To assign all groups to roles correctly, press Continue and repeat the steps for the following schemas:

Roles Groups

ACC_Archiving AC_Administrator

ACC_Observing AC_Observer, AC_Operator, AC_Administrator

ACC_Operation AC_Operator, AC_Administrator

ACC_Configuration AC_Administrator



6.1.5 Assigning Users to Groups

Select Groups and choose the first group AC_Administrator. Click on Assign Users to …



Click on + sign to open the Search/Select Groups window.

Click on Search.



Select Administrator and accuser. Click on Select.



Click on Continue to assign more users e.g. accuser to the Administrators group.





Configuration of ACC Configuration of the SLD


6.2 Configuration of the SLD The SLD is running on the WebAS 6.40 together with ACC on the same J2EE engine.

To configure the SLD, login via the following link:

http://<ACChostname>:5<SAP_System_No>00/sld/

Login with user administrator and password.

Navigate to Administration

Configuration of the SLD Configuration of ACC


Navigate to Server Settings



Fill in Object Server jcoac, click the button and navigate Back to Administration.

3.

2.

1.



Navigate to Data Supplier Bridge:

Click on Start Bridge.

1.

2.

4.

3.



Click Back to Administration.

Start the Server. Status changes to running.



6.2.1 Configuration of the SLD Connection to the J2EE Engine

Start of Visual Administrator:

control1:~ # ssh -X oacadm@baby_4 oacadm@baby_4's password: Last login: Fri Dec 10 17:48:51 2006 from jcoac Directory: /home_sap/oacadm jcoac:oacadm 58> cd /usr/sap/OAC/JC04/j2ee/admin jcoac:oacadm 60> ./go

Enter Password and click on the Connect button.



Navigate to Server 0_XX Services



Navigate to SLD Data Supplier. Select HTTP Settings sheet. Fill in the fields marked above and click the Save button.

Check if the user e.g. accuser is able to logon to the SLD system!!

Test the connection to SLD. Trigger a test connect to SLD.

Click on Yes.

2.

1.

3. Test connect to SLD



Click on OK.

Select the CIM Client Generation Settings sheet. Fill in the fields marked above and press Save.

Test the connection to the CIM Client.

Click on OK.

1.

2. 3.



Exit.

Click on Yes.

Configuration of ACC Registering Managed Application Services into SLD


6.3 Registering Managed Application Services into SLD

6.3.1 ABAP System Logon to the system and execute transaction RZ70. Application Services (App) must be up and running.(for every ABAP system to be managed).

If the field with the Data Collector Programs is empty, click on the Proposal button to fill in the right programs (as above).

Fill in the hostname and service of the gateway. Click on the activate and execute button.

1.

2. 3.

!.

Registering Managed Application Services into SLD Configuration of ACC


Click on Yes.

Check if the ABAP instance OL4 is visible in the SLD.

Start a browser and connect to the SLD.




Navigate to Technical Landscape.



The registered application services should now appear in the list.



6.3.2 Java System Start Visual Administrator on the J2EE engine host that is to be managed. (This should be done for every JAVA system to be managed). Application Services (J) must be up and running.

control1:~ # ssh -X mepadm@baby_4 mepadm@baby_4's password: Last login: Fri Dec 10 17:48:51 2004 from jcmep Directory: /home_sap/mepadm jcmep:mepadm 58> cd /usr/sap/MEP/JC10/j2ee/admin jcmep:mepadm 60> ./go

Select Default and click on the Connect button

Enter the Password and click on Connect.



Navigate to Server 0_XX Services.



Navigate to SLD Data Supplier and select the HTTP Settings sheet. Fill in the fields marked above and save.

Trigger a test connection to the SLD.

Click Yes.

Click OK.

2.

1.

3. Test connect to SLD



Check if the JAVA instance MEP is visible in the SLD. Start a browser and connect to the SLD.


Navigate to Technical Landscape

Configuration of ACC ACC Agents


Select Technical System Type: Web AS Java. The registered application services should now appear in the list.

6.4 ACC Agents

6.4.1 Installing ACC Agents Download the SAP ACC Agents from the SAP Service Marketplace: http://service.sap.com/adaptive

Unzip the downloaded file and unpack AccAgents_v1.0.13.0.sar (use an <sid>adm)

# su - oleadm baby_4:oleadm 1% cd /tmp baby_4:oleadm 7% cp ACCAGENTSV10130.SAR /tmp baby_4:oleadm 9% SAPCAR -xvf ACCAGENTSV10130.SAR SAPCAR: processing archive AccAgents_v1.0.13.0.sar x AccAgents_v1.0.13.0 x AccAgents_v1.0.13.0/unix ...

ACC Agents Configuration of ACC


The following steps have to be done for every platform (SunOS, Linux.i686, Linux.SLES-9.i686, Linux.SLES-9.x86_64, Linux.SLES-10.x86_64)

Go to the platform-specific directory e.g sun_64

baby_4:oleadm 46% su root Password: # cd /tmp/AccAgents_v1.0.13.0/unix/sun_64 # cp * /usr/sap/adaptive # cd /usr/sap/adaptive # chown -R root:sapsys /usr/sap/adaptive # chmod -R 750 /usr/sap/adaptive # chown oacadm:sapsys /usr/sap/tmp # chmod 770 /usr/sap/tmp # chown oacadm:sapsys sapacoscol saposcol sldreg

6.4.2 Setting up sapacoscol and sapacosprep Proceed as follows:

# vi /usr/sap/adaptive/sapacoscol.ini "/usr/sap/adaptive/sapacoscol.ini" [New file] # sapacoscol.ini HOSTNAME jcoac # hostname of ACC J2EE host PORT 50400 # Port of ACC J2EE engine PATH /saposcol/CCMSProxy # chmod 640 sapacoscol.ini # chown oacadm:sapsys sapacoscol.ini

Download the newest sapacosprep libraries for Solaris and Linux 32/64 from:

http://extranet.fujitsu-siemens.com/sap -> Solutions -> FlexFrame -> Downloads (Don’t forget to login before)

# chown root:sapsys sapacosprep libsapacosprep.so libsapacosprep_FSC.so # chmod 4750 sapacosprep libsapacosprep.so libsapacosprep_FSC.so

There is only one library for Solaris please install the following link:

# ln –s libsapacosprep.so libsapacosprep_FSC.so



6.4.3 Setting up sldreg Create an sldreg connection file by running

# ./sldreg –configure sldreg.cf stderr initialized Fri Apr 08 17:05:05 2005 SLD Registration Program [1.0] (Oct 25 2004) [Unicode] Use configuration file ‘sldreg.cf’ for output! Please specify the HTTP connect information: [User, Password, Host, Port] HTTP User Name : accuser # Don’t use “Administrator” as user User’s Password : # Don’t use “password” as password Server Host : 10.1.7.104 # IP-Address for jcoac Port [1024..65535] : 50400 Entered Information User: accuser Passwd: (secret) Host: 10.1.7.104 Port: 50400 Write this information to secure file ‘sldreg.cf’? [y=yes/n=no/q=quit] y Fri Apr 08 17:06:15 2005 Writing data to encrypted file ‘sldreg.cf’ Fri Apr 08 17:06:15 2005 Data written to secured data file ‘sldreg.cf’ Fri Apr 08 17:06:15 2005 Using connect file ‘sldreg.cf’. Fri Apr 08 17:06:15 2005 No key file ‘sldreg.cf.key’ used. Fri Apr 08 17:06:15 2005 Configuration data successfully stored in file: sldreg.cf # chmod 640 sldreg.cf # chown oacadm:sapsys sldreg.cf



6.4.4 Setting up sapacusrexit Sapacusrexit works as an interface to the FA-Agents.

Example:

# cd /usr/sap/adaptive # vi sapacusrexit #!/bin/bash echo "Running User Exit Script" echo "/ ---- " $0 $* " ---- /" case $1 in "prestart") case $2 in # MEP example for JAVA standalone "MEP (DB)") sudo /FlexFrame/scripts/sapdb MEP prestart exit $? ;; "MEP (DISP 01)") sudo /FlexFrame/scripts/sapscs MEP prestart sudo /FlexFrame/scripts/sapjc MEP prestart exit $? ;; "MEP (DISP 02)") sudo /FlexFrame/scripts/sapj 12 MEP prestart exit $? ;; # MXI example for ABAP+JAVA "MXI (DB)") sudo /FlexFrame/scripts/sapdb MXI prestart exit $? ;; "MXI (CI)") sudo /FlexFrame/scripts/sapscs MXI prestart sudo /FlexFrame/scripts/sapci MXI prestart exit $? ;; "MXI (APP 01)") sudo /FlexFrame/scripts/sapapp 19 MXI prestart exit $? ;; # O46 example for ABAP only



"O46 (DB)") sudo /FlexFrame/scripts/sapdb O46 prestart exit $? ;; "O46 (CI)") sudo /FlexFrame/scripts/sapci O46 prestart exit $? ;; "O46 (APP 01)") sudo /FlexFrame/scripts/sapapp 20 O46 prestart exit $? ;; esac echo "/ PRESTART position executed /" exit 0 ;; "poststart") case $2 in "MEP (DB)") sudo /FlexFrame/scripts/sapdb MEP poststart exit $? ;; "MEP (DISP 01)") sudo /FlexFrame/scripts/sapscs MEP poststart sudo /FlexFrame/scripts/sapjc MEP poststart exit $? ;; "MEP (DISP 02)") sudo /FlexFrame/scripts/sapj 12 MEP poststart exit $? ;; # MXI example for ABAP+JAVA "MXI (DB)") sudo /FlexFrame/scripts/sapdb MXI poststart exit $? ;; "MXI (CI)") sudo /FlexFrame/scripts/sapscs MXI poststart sudo /FlexFrame/scripts/sapci MXI poststart exit $? ;; "MXI (APP 01)") sudo /FlexFrame/scripts/sapapp 19 MXI poststart exit $?



;; # O46 example for ABAP only "O46 (DB)") sudo /FlexFrame/scripts/sapdb O46 poststart exit $? ;; "O46 (CI)") sudo /FlexFrame/scripts/sapci O46 poststart exit $? ;; "O46 (APP 01)") sudo /FlexFrame/scripts/sapapp 20 O46 poststart exit $? ;; esac echo "/ POSTSTART position executed /" exit 0 ;; "prestop") case $2 in "MEP (DB)") sudo /FlexFrame/scripts/sapdb MEP prestop exit $? ;; "MEP (DISP 01)") sudo /FlexFrame/scripts/sapjc MEP prestop sudo /FlexFrame/scripts/sapscs MEP prestop exit $? ;; "MEP (DISP 02)") sudo /FlexFrame/scripts/sapj 12 MEP prestop exit $? ;; "MXI (DB)") sudo /FlexFrame/scripts/sapdb MXI prestop exit $? ;; "MXI (CI)") sudo /FlexFrame/scripts/sapci MXI prestop sudo /FlexFrame/scripts/sapscs MXI prestop exit $? ;; "MXI (APP 01)") sudo /FlexFrame/scripts/sapapp 19 MXI prestop



exit $? ;; "O46 (DB)") sudo /FlexFrame/scripts/sapdb O46 prestop exit $? ;; "O46 (CI)") sudo /FlexFrame/scripts/sapci O46 prestop exit $? ;; "O46 (APP 01)") sudo /FlexFrame/scripts/sapapp 20 O46 prestop exit $? ;; esac echo "/ PRESTOP position executed /" exit 0 ;; "poststop") case $2 in "MEP (DB)") sudo /FlexFrame/scripts/sapdb MEP poststop exit $? ;; "MEP (DISP 01)") sudo /FlexFrame/scripts/sapjc MEP poststop sudo /FlexFrame/scripts/sapscs MEP poststop exit $? ;; "MEP (DISP 02)") sudo /FlexFrame/scripts/sapj 12 MEP poststop exit $? ;; "MXI (DB)") sudo /FlexFrame/scripts/sapdb MXI poststop exit $? ;; "MXI (CI)") sudo /FlexFrame/scripts/sapci MXI poststop sudo /FlexFrame/scripts/sapscs MXI poststop exit $? ;; "MXI (APP 01)") sudo /FlexFrame/scripts/sapapp 19 MXI poststop



exit $? ;; "O46 (DB)") sudo /FlexFrame/scripts/sapdb O46 poststop exit $? ;; "O46 (CI)") sudo /FlexFrame/scripts/sapci O46 poststop exit $? ;; "O46 (APP 01)") sudo /FlexFrame/scripts/sapapp 20 O46 poststop exit $? ;; esac echo "/ POSTSTOP position executed /" exit 0 ;; *) echo "/ unknown error /" exit 1 ;; esac exit 0 # chmod 750 sapacusrexit # chown oacadm:sapsys sapacusrexit

6.4.5 Starting ACC Agents Create an rc script for starting the ACC agents

# cd /usr/sap/adaptive # vi ACCagents “ACCagents” 60 lines, 1224 characters #!/bin/bash # # ACCagents script to start saposcol,sapacoscol and sldreg # # Global variables # ACHOME=/usr/sap/adaptive



ACSLDCF=$ACHOME/sldreg.cf # path to sldreg connection file ACTMP=/usr/sap/tmp ACLOG=/tmp/`basename $0`.log SLDHOST=10.1.7.104 # IP-Address of jcoac # only for Solaris case $1 in start) # sld registration if [ -x $ACHOME/saposcol –a –x $ACHOME/sldreg ] ; then echo “Registering System in SLD” #we first need to start saposcol to fill the shm segment $ACHOME/saposcol –l 1>/dev/null 2>&1 if (ping $SLDHOST 1 1 >/dev/null 2>&1); then # only for Solaris $ACHOME/saposcol –b | \ $ACHOME/sldreg –file /dev/stdin –connectfile $ACHOME/sldreg.cf \ 1>$ACLOG 2>&1 fi # only for Solaris if [ $? -ne 0 ] ; then echo "Error while registering" fi fi if [ -x $ACHOME/sapacoscol ]; then echo "Starting sapacoscol" $ACHOME/sapacoscol -start -f $ACHOME/sapacoscol.ini </dev/null if [ $? -ne 0 ]; then echo "Error while starting sapacoscol" fi fi ;; stop) ;; esac # chmod 750 ACCagents # chown root:sapsys ACCagents # ls –la total 22321 drwxr-x--- 3 root sapsys 4096 Apr 3 13:26 . dr-xr-xr-x 6 root root 6 Apr 3 13:28 .. -rwxr-x--- 1 root sapsys 1133 Feb 8 17:26 ACCagents -rwsr-x--- 1 root sapsys 43456 Apr 3 13:17 libsapacosprep.so -rwxr-x--- 1 oacadm sapsys 2020104 Apr 3 13:17 sapacoscol -rw-r----- 1 oacadm sapsys 55 Apr 3 13:22 sapacoscol.ini -rwsr-x--- 1 root sapsys 761432 Apr 3 13:17 sapacosprep -rwxr-x--- 1 oacadm sapsys 7028 Apr 3 13:16 sapacusrexit



-rwxr-x--- 1 oacadm sapsys 1548952 Apr 3 13:17 saposcol -rwxr-x--- 1 oacadm sapsys 6987760 Apr 3 13:17 sldreg -rw-r----- 1 oacadm sapsys 74 Apr 3 13:26 sldreg.cf # ./ACCagents start Registering System in SLD Starting sapacoscol INFO: sapacoscol working directory is /usr/sap/tmp/sapacoscol INFO: found option –start

Runnig rc scripts for Linux, e.g.:

control1:~ # cd /FlexFrame/volFF/os/Linux/FSC_4.xxx/root_img/etc/init.d/rc3.d control1:/FlexFrame/volFF/os/Linux/FSC_4.xxx/root_img/etc/init.d/rc3.d # ln –s ../ACCagents S23ACCagents control1:/FlexFrame/volFF/os/Linux/FSC_4.xxx/root_img/etc/init.d/rc3.d # cd .. control1:/FlexFrame/volFF/os/Linux/FSC_4.xxx/root_img/etc/init.d # cp –p /FlexFrame/volFF/pool-xxx/sap/adaptive/LINUX.xxx/ACCagents ACCagents

The last step has to be repeated for every Linux image.

klinge5:.# cd /etc/init.d/rc3.d klinge5:/etc/init.d/rc3.d # ./S23ACCagents start Registering System in SLD Starting sapacoscol INFO: sapacoscol working directory is /usr/sap/tmp/sapacoscol INFO: found option -start klinge5:/etc/init.d/rc3.d #

The last step must be repeated for every Linux host to be managed in the pool.

Run the rc scripts for Solaris, e.g.:

# cd /etc/rc3.d # ln –s /etc/init.d/ACCagents S98ACCagents # cd /etc/init.d # ln –s /usr/sap/adaptive/ACCagents ACCagents # cd /etc/rc3.d # ./S98ACCagents start Registering System in SLD Starting sapacoscol INFO: sapacoscol working directory is /usr/sap/tmp/sapacoscol INFO: found option -start



This step must be repeated for every Solaris host to be managed in the pool.

Check if the host (e.g. baby_3) is registered in the SLD.

Select Content Maintenance -> Landscape Description with Class: Computer System.

Configuring SSH Configuration of ACC


6.5 Configuring SSH Proceed as follows:

# su - oacadm baby_4:oacadm 11%vi .cshrc setenv PATH ${PATH}:/usr/sap/adaptive alias hostname "echo `~/hostname`" # necessary to get hostname without domain (AIX, OS/390 and NOT sun) switch (`uname`) case AIX*: alias hostname 'hostname -s' breaksw case OS/390*: setenv _BPXK_AUTOCVT ON setenv _TAG_REDIR_IN TXT set _TAG_REDIR_IN=TXT setenv _TAG_REDIR_OUT TXT set _TAG_REDIR_OUT=TXT setenv _TAG_REDIR_ERR TXT set _TAG_REDIR_ERR=TXT alias hostname 'hostname -s' breaksw endsw baby_4:oacadm 12% exit # su - oacadm baby_4:oacadm 1% mkdir .ssh baby_4:oacadm 2% cd .ssh

Check if the above user has the correct owner and permissions for his home directory.

The procedure how to configure ssh in an ACC environment is as follows:

baby_4:oacadm 3% ssh-keygen -t rsa Generating public/private rsa key pair. Enter file in which to save the key (/home_sap/oacadm/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /home_sap/oacadm/.ssh/id_rsa. Your public key has been saved in /home_sap/oacadm/.ssh/id_rsa.pub. The key fingerprint is: 34:17:0e:62:cb:6b:60:e5:90:37:40:b0:da:0a:1e:72 oacadm@baby_4 baby_4:oacadm 4%cp -p id_rsa.pub authorized_keys baby_4:oacadm 5%exit

Configuration of ACC Configuring SSH


For every host to be managed, the user oacadm and for all to be managed systems the adminstration user <sid>adm,e.g. SID=O46 must able to connect baby_4# cd /home_sap baby_4# mkdir -p o46adm/.ssh baby_4# cp -p oacadm/.ssh/authorized_keys o46adm/.ssh baby_4# cd o46adm/.ssh baby_4# ls –la total 16 drwxr-xr-x 2 root root 4096 Apr 4 13:01 . drwxr-xr-x 4 o46adm sapsys 8192 Apr 4 13:00 .. -rw-r--r-- 1 oacadm sapsys 223 Feb 8 17:57 authorized_keys baby_4# chown o46adm:sapsys . * baby_4# chmod 700 . baby_4# ls –la # check authorizations total 16 drwx------ 2 o46adm sapsys 4096 Apr 4 13:01 . drwxr-xr-x 4 o46adm sapsys 8192 Apr 4 13:00 .. -rw-r--r-- 1 o46adm sapsys 223 Feb 8 17:57 authorized_keys

The last step has to be done from ACC Application Node to each other Application Node. That means, depending on which platform ACC was installed, the ssh connection has to be done once from the Application Node running ACC to all other Application Nodes in the pool for each <sid>adm.

baby_4# su - oacadm baby_4:oacadm 20% ssh –l <sid>adm baby_3 The authenticity of host 'baby_3 (10.1.7.7)' can't be established. RSA key fingerprint is f8:10:f9:23:4b:e3:1c:7f:e7:38:3d:1b:64:7f:f3:6a. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'baby_3,10.1.7.7' (RSA) to the list of known hosts. baby_3:oacadm 11%exit baby_4:oacadm 21%

Configuration of Connections between SolMan and ACC Configuration of ACC


6.6 Configuration of Connections between SolMan and ACC

6.6.1 Creating SAP Services User SAPJSF Logon to the Solution Manager System and maintain your company address if it is not yet done: “SU01” Menue Environment -> Maintain company address.

Next step: Call the transaction “SE37”:

Type in Function module: PRGN_J2EE_CREATE_SERVICE_USER.

Choose Single Test (F8).

Configuration of ACC Configuration of Connections between SolMan and ACC


Specify IF_PASSWORD and choose Execute(F8). Exit.

Use the password which you have configured in the Config Tool (see section “Post Installation Activities” on page 21).

1.

2.



Call the transaction su01.



Fill in user sapjsf and choose Change.



Fill in Role: SAP_SMSY_ACC_RFC and save.



Activate the profiles with transaction pfcg.

Fill in SAP_SMSY_ACC_RFC and click on the pencil icon.



Select Authorizations and click on the pencil icon.



Generate the profile.

Click OK.



If profiles are created, switch back one step.



Select User and click on User comparison.

Click on Complete comparison.



Go back to transaction su01.



Go to Profiles and check whether the profile for SAP_SMSY_ACC_RFC was generated.



Go to Roles and check if both roles above are present and show a green light.



6.6.2 Connection Configuration in the ACC with Visual Administrator

Proceed as follows:

control1:ssh –X oacadm@baby_4 baby_4:oacadm 12% cd /usr/sap/OAC/JC04/j2ee/admin baby_4:oacadm 13% ./go

Select Default and click on the Connect button.

Insert the password and click Connect.

Navigate to Server 0_XXX -> Services -> JCo RFC Provider



First connection: ACI_READ_SLD_DATA

Fill in the above fields

Program ID has to be unique and the same as in the next chapter. Gateway host and Gateway service values are from the Solution Manager system. Click Set to activate (the gateway should be running).

1

2



Second connection: sapsldapi_osm.

Fill in the above fields.

Program ID has to be unique and the same as in the next chapter. Gateway host and Gateway service values are from the Solution Manger system. Click Set to activate (the gateway should be running).

Choose Menu: Connect -> Logout

1

2



6.6.3 Configuration of Connections in the Solution Manager First connection: ACC

Logon to the Solution Manager system.

Choose Transaction SM59.

Select TCP/IP connections and press Create.



Fill in the above fields and save.

1.

2.




1.

2.



Click Test connection.

If the Test connection works fine, the following screen appears. If not , restart jc<sid>.



Go back to transaction SM59.



Second connection: ACC


1.

2.




1.

2.



Click Test connection.



If the Test connection works fine, the following screen appears.

Configuration of ACC Data Transfers from SLD to Solution Manager


6.7 Data Transfers from SLD to Solution Manager

6.7.1 Configuration Logon to Solution Manager and call the transaction sldapicust.

Fill in the fields and activate the password settings (click on the field under Password).

Insert password, execute and save.

5.6.

1.

3.

2.

4.

7.

Data Transfers from SLD to Solution Manager Configuration of ACC


Execute the transaction SMSY_SETUP.

Select System and Landscape Directory.

Navigate to Menu: Edit -> Expert Settings.



Set up field Write Data Back to SLD and execute.



6.7.2 Activate and Check Transfer from SLD to Solution Manager

Navigate back to transaction SMSY_SETUP.

Press the Schedule Data Transfer button.

Click Y.

2.

1.



Click Immediate and save.

1.

2.



Insert lp01 and execute.

Check with transaction SM37.

1.

2.



The Job LANDSCAPE FETCH status should be Complete after a while.

Making the Landscape Adaptive Configuration of ACC


6.8 Making the Landscape Adaptive This chapter describes how ACC and Solution Manger work to make the landscapes adaptive.

6.8.1 Start of ACC Call the following URL:

http://jcoac:50400/webdynpro/dispatcher/sap.com/ca~ac~acc~accadministrationtools/AdministrationTools

or

http://jcoac:50400/acc/Administration

First, logon to ACC:

Configuration of ACC Making the Landscape Adaptive




6.8.2 Configuring Network

Navigate to Technical Settings -> Server Enabling -> Network. Then switch to Edit Mode, click on Add and enter the required data (network name, netmask, broadcast address) and click on Save.



6.8.3 Configuring ACC-Pools

Navigate to Technical Settings -> Server enabling -> Pool. Then switch to Edit Mode, click on Add and enter the required data. Click on Save.

ACC exists once in each FF Pool, so you can define e.g. groups of hardware for the ACC Pool



6.8.4 Adaptive Enabled Computing Nodes

Navigate to Technical Settings -> Server Enabling -> Servers and to see the servers that are already registered. Only the physical server names will be adaptive enabled.



6.8.4.1 Server Enabling with the Single Operation Procedure

Switch to Edit Mode, click on the right computing node and select the Pool and enter the SAPS figures in Server Details.

After this step, press Add in the Network List and enter the interface name (ipmp-client/ipmp-server for Solaris and for e.g vlan10/vlan11 for Linux) and the associated network.

Finally click Save to save the entered data.



6.8.4.2 Server Enabling with the Mass Operation Procedure

After you have “adaptive enabled” at least one of the servers in the landscape, you may use the mass operation procedure to enable the other computing nodes in a more efficient manner, if they require the same settings. Switch to Edit Mode, click on the group of computing nodes (with the Shift or the Ctrl key) which you want to apply the configuration of the computing node to. Then choose the Reference Server, press Map Settings and Save to save the configuration.

If all servers are adaptive enabled, they should be visible in Detailed Navigation -> Physical Landscape.





6.8.5 Adaptive Enabled Application Services Using Solution Manager

Logon to the Solution Manager and execute the transaction SMSY.

If the above screen does not appear with an Adaptive Computing button, do the following steps:

1. Restart the J2EE engine while the Solution Manager is running

2. Go to the ACC -> Technical Settings -> Server Enabling -> Pool

3. Press Edit and then Save button

4. Repeat step 3. for Network

5. Go back to Solution Manager

6. Repeat transaction smsy

7. When clicking the Adaptive Computing button, Networks and the List of Computer Pools should be filled

Configuration of ACC Integration of SAP Services


6.9 Integration of SAP Services Take care that the newest start/stopsap and start/stopdb scripts are available in the exe directory, especially for older SAP Systems e.g. 4.6C.

You can find them on the SAP Service MARKETPLACE or in the directory ../AccAgents_v1.0.13.0/unix/common/.. where you have unpacked the actual ACCAGENTSV10130.SAR file (see section “Installing ACC Agents” on page 68).

6.9.1 Integration of an ABAP and ABAP+JAVA Central Instance

Select Systems -> SAP WebAS, click the Change button and then the Activate button for Adaptive-enabled.

Integration of SAP Services Configuration of ACC


Select Computer Pool and click OK.

Click on Save button before going on, otherwise the pencil icon on the instances sheet is not available.

Select the Instances sheet.

Select the CI instance and click on the pencil icon to change.



1. Fill in mandatory fields e.g. Start/stop command (depending on the instance e.g.

ABAP+JAVA) with user <sidadm>. An ABAP-only instance needs no start/stop for SCS<ID> .

2. Fill in the appropriated Host Name and Network.

3. After the fields are complete, press Save.

1.

2.

3.



Example for an ABAP+JAVA instance with separated ASCS and SCS (≥ WebAS 7.0).



6.9.2 Integration of an ABAP Application Service A central instance must be integrated before.

Select an Application Instance and click on the pencil icon.

These steps must be repeated for each application instance listed.



1. Fill in mandatory fields: Start/stop command (depending on the instance e.g. ABAP)

with user <sid>adm.

2. Fill in the app<id><sid>-se and Network Server Lan.

3. After the fields are complete, press Save.

1.

2.

3.



6.9.3 Integration of a Database Service Navigate to Database.

Select Managed by Adaptive Computing and save.

Navigate to the Technical Data sheet.



Click on the pencil icon.



Example for SAPDB/MaxDB:

1. Fill in the above fields. Mandatory fields are: Start/stop command with user <sid>adm. For JAVA DB use startj2eedb/stopj2eedb.

2. Fill in the db<sid>-se and Network Server Lan.

3. After the fields are complete, press save.

1.

2.

3.



Example for DB Oracle with lsnrctl start/stop.

Before you can start the listener as <sid>adm, you have to do:

baby_4:~ # cd /oracle/OSS/920_64/network/log baby_4:~ # ls –la total 584 drwxr-xr-x 2 oraoss dba 4096 Apr 5 11:36 . drwxr-xr-x 14 oraoss dba 4096 Jan 10 17:26 .. -rw-rw-r-- 1 oraoss dba 213260 Apr 5 15:16 listener.log -rw-r--r-- 1 oraoss dba 64110 Apr 6 16:13 listener_oss.log baby_4:~ # chmod 664 listener_oss.log baby_4:~ # chmod 664 .



6.9.4 Integration of a Java Central Instance

Select System Components -> Java-System -> <sid>, click the Change button and then the Activate button for Adaptive-enabled.

Select Computer Pool and press OK.



Select the Instances sheet

Select DISP 01 (JC) and click on the pencil icon to change.



1. Fill in mandatory fields e.g. Start/stop command (depending on the instance e.g. JAVA) with user <sid>adm.

2. Fill in the appropriated Host Name and Network .


1.

2.

3.



6.9.5 Integration of a Java Application Instance

Select Instances sheet

Select DISP 02 (J) and click on the pencil icon to change.



1. Fill in mandatory fields, e.g. Start/stop command (depending on the instance e.g.

JAVA) with user <sid>adm.

2. Fill in the j<id><sid>-se and Network Server Lan.


1.

2.

3.



6.9.6 Final Configuration for the Application Services Move to ACC -> Logical Landscape.

The following steps have to be done for each application service which is new in ACC.

Also if you changed an existing service in the SolMan and save it to the SLD, you have to repeat the following steps.

Click on an application service to be configured.

Click on Edit.



Set Auto Mount to On.



Only for Service DB with SAN you have to configure the DB Storage List:

Choose Storage Type SR, type SRID=SID, FFSRID and Partner ID FSC.

Click Next.



Select the OS and press the Next button. In case of using an instance in e.g Sol9 +10 please select No Check.



Click on Save.



Click on Yes.



6.9.7 Repeat the procedure with the next service.Start/Stop/Relocate Application Services

Using ACC is described in the “FlexFrame™ for SAP® - Administration and Operation” guide in chapter “SAP ACC”.

You may also use the Help button in the ACC WebGUI.



6.9.8 Multiple Services on one Server SAP note 864855

Multiple Services on one Server - this function enables you to run multiple services on one server at the same time. This feature is only available as project-specific release. If you're interested in using this feature, please open an OSS message on component "CA-AC" with the subject "request: multiple service". Then the product management of Adaptive Computing will get in contact with you.

The key you will receive should be inserted (see section “Post Installation Activities”on page 21) as Custom value for the key “ACC.Control.MultiService”

Don’t forget to reboot the JC instance.


7 Troubleshooting Troubleshooting information can also be found in the “FlexFrame™ for SAP® -Administration and Operation” guide in section “SAP ACC Troubleshooting”.

7.1 J2EE Server is Restarting License key problem server0 restarts.

jcoac:oacadm 52> cd /usr/sap/OAC/JC04/j2ee/admin/logviewer-standalone jcoac:oacadm 57> ./logviewer.sh java version "1.4.2_05" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04) Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)

A valid license key is missing. Use Visual Administrator to bring in a valid licence key file.

Troubleshooting Error by SMSY_Setup


7.2 Error by SMSY_Setup Look in the ouput of sm37 if a job is cancelled. Analyze the job log.

Check sm59 with ACC und sapsldapi connections test.

If the error Programm not registered occurs, restart Server0 with the jcmon tool:

jcoac:oacadm 52> jcmon pf=/sapmnt/OAC/profile/<InstanceProfileJC>

7.3 RZ70 Failed If RZ70 fails:

● Use transaction sldcheck. ● Use transaction sm59. ● Test connections to SLDUC or SLDNUC.

7.4 SDM Error ACC SP07 In case starting of SDM fails, check if the log file contain an error message similar to the following:

Starting Deployment of ca/ac/acc/accadministrationtools Aborted: development component 'ca/ac/acc/accadministrationtools'/'sap.com'/'SAP AG'/'1.0007.00.20050812161209.0000':Caught exception during application deployment from SAP J2EE Engine's deploy API:com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file . Reason: java.io.FileNotFoundException: /usr/sap/MAC/JC92/SDM/program/./temp/temp_dm/temp_ca_ac_acc_accadministrationtools.ear (Permission denied) (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC) Deployment of ca/ac/acc/accadministrationtools finished with Error (Duration 7631 ms)

Solution

Execute the following command:

# /usr/sap/MAC/JC92/SDM/program # chown -R macadm:sapsys temp

SDM Password Change Troubleshooting


7.5 SDM Password Change Go to /usr/sap/<SID>/JC<ID>/SDM/program

1. ./sdm.sh jstartup “mode=standalone” ”sdmhome=/usr/sap/<SID>/JC<ID>/SDM/program”

2. ./sdm.sh changepassword ”sdmhome=/usr/sap/<SID>/JC<ID>/SDM/program”

3. ./sdm.sh jstartup “mode=integrated” ”sdmhome=/usr/sap/<SID>/JC<ID>/SDM/program”

7.6 ACC Installation Failed Message: ….. no appropriated instance found ..... Start RemoteGui: blade5:/usr/sap/MAC/JC83/SDM/program # ./RemoteGui.sh

Deploy ACC SP12 by hand: First offline package and then online package


8 Abbreviations ABAP Advanced Business Application Programming

ACC Adaptive Computing Controller

ACI Adaptive Computing Infrastructure

ACPI Advanced Configuration and Power Interface

APM Advanced Power Management

APOLC Advanced Planner & Optimizer Life Cache

CCU Console Connection Unit

CIFS Common Internet File System

DART Data Access in Real Time

DHCP Dynamic Host Configuration Protocol

DIT Domain Information Tree

ERP Enterprise Resource Planning

ESF Enhanced System Facility

EULA End User License Agreement

FAA FlexFrame Autonomous Agent

FC Fiber Channel

FTP File Transfer Protocol

IP Internet Protocol

IPMP IP Multipathing

LAN Local Area Network

LDAP Lightweight Directory Access Protocol

LUN Logical Unit Number

MAC Media Access Control

MINRA Minimal Read Ahead

NAS Network Attached Storage

NDMP Network Data Management Protocol

NFS Network File System

Abbreviations


NIC Network Interface Card

NVRAM Non-Volatile Random Access Memory

OBP Open Boot Prom

OLTP On-Line Transaction Processing

ONTAP Open Network Technology for Appliance Products

OSS Open Source Software

POST Power-On Self Test

PCL PRIMECLUSTER

PFS Production File System (on Celerra)

PW PRIMEPOWER

PXE Preboot Execution Environment

PY PRIMERGY

QA Quality Assurance

QS Quality of Service

RAID Redundant Array of Independent (or Inexpensive) Disks

RARP Reverse Address Resolution Protocol

RDBMS Relational Database Management System

RHEL Red Hat Enterprise Linux

RSB Remote Service Board

SCS System Console Software

SAP BW SAP Business Warehouse

SAPGUI SAP Graphical User Interface

SAPOSS SAP Online System Service

SID System Identifier

SLD System Landscape Directory

SLES SUSE Linux Enterprise Server

SMB Server Message Block

SMC System Management Console

SNMP Simple Network Management Protocol

Abbreviations


SPOC Single Point Of Control

TELNET Telecommunications Network

TFTP Trivial File Transfer Protocol

UDP User Datagram Protocol

UPS Uninterruptible Power Supply

VLAN Virtual Local Area Network

VTOC Virtual Table Of Contents

WAN Wide Area Network

WAS Web Application Server

WAFL Write Anywhere File Layout

XSCF Extended System Control Facility


9 Glossary Adaptive Computing Controller

SAP system for monitoring and controlling SAP environments.

Advanced Business Application Programming Proprietary programming language of SAP.

Advanced Power Management Advanced Power Management defines a layer between the hardware and the operating system that effectively shields the programmer from hardware details.

Application Agent A software program for monitoring and managing applications.

Application Node A host for applications (e.g. SAP instances db, ci, agate, wgate, app etc.). This definition includes Application Servers as well as Database Servers.

Automounter The automounter is an NFS utility that automatically mounts directories on an NFS client as they are needed, and unmounts them when they are no longer needed.

Autonomous Agent Central system management and high availability software component of FlexFrame.

Blade A special form factor for computer nodes.

BladeRunner The working title for the solution part of SAP for FlexFrame.

BOOTPARAM Boot time parameters of the kernel.

BRBACKUP SAP backup and restore tools.

Celerra NAS system of EMC.

Checkpoint Restore On EMC Celerra a SnapSure feature that restores a PFS to a point in time using checkpoint information. As a precaution, SnapSure automatically creates a new checkpoint of the PFS before it performs the restore operation.

Client LAN Virtual network segment within FlexFrame, used for client-server traffic.

Glossary


Common Internet File System A protocol for the sharing of file systems (same as SMB).

Computing Node From the SAP ACI perspective: A host that is used for applications.

Control Agent A software program for monitoring and managing nodes within FlexFrame.

Control LAN Virtual network segment within FlexFrame, used for system management traffic.

Control Node A physical computer system, controlling and monitoring the entire FlexFrame landscape and running shared services in the rack (dhcp, tftp, ldap etc.).

Control Station A Control Node in an SAP ACI environment.

DART Operating system of Celerra data movers (Data Access in Real Time).

Dynamic Host Configuration Protocol DHCP is a protocol for assigning dynamic IP addresses to devices on a network.

Dynamic Host Configuration Protocol server A DHCP server provides configuration parameters specific to the DHCP client host, required by the host to participate on the Internet.

EMC NAS Network attached storage for file systems of EMC.

Enterprise Resource Planning Enterprise Resource Planning systems are management information systems that integrate and automate many of the business practices associated with the operations or production aspects of a company.

Ethernet

A Local Area Network which supports data transfer rates of 10 megabits per second.

Fiber Channel Fiber Channel is a serial computer bus intended for connecting high-speed storage devices to computers.

Filer Network attached storage for file systems of NetApp.

FlexFrame A joint project in which the main partners are SAP, Network Appliance, Intel and Fujitsu Siemens Computers.

Glossary


FlexFrameTM for SAP® FlexFrameTM for SAP® is a radically new architecture for SAP environments. It exploits the latest business-critical computing technology to deliver major cost savings for SAP customers.

FlexFrame internal LAN Switch Cisco network switches which are integral part of the FlexFrame for SAP hardware configuration and which are automatically configured by the FlexFrame for SAP software.

Gigabit Ethernet A Local Area Network which supports data transfer rates of 1 gigabit (1,000 megabits) per second.

Host name The name of a node (assigned to an interface) that is resolved to a unique IP address. One node can have multiple host names (cf. node name). In SAP environments host names are currently limited to 13 alphanumeric characters including the hyphen (“ - “). The first character must be a letter. In the SAP environment host names are case-sensitive.

Image In the FlexFrame documentation, “Image” is used as a synonym for “Hard Disk Image”.

Internet Protocol Address A unique number used by computers to refer to each other when sending information through networks using the Internet Protocol.

Lightweight Directory Access Protocol Protocol for accessing on-line directory services.

Local Area Network A computer network that spans a relatively small area. Most LANs are confined to a single building or group of buildings. However, one LAN can be connected to other LANs over any distance via telephone lines and radio waves. A system of LANs connected in this way is called a Wide Area Network (WAN).

Local host name The name of the node (physical computer); it can be displayed and set using the command /bin/hostname.

Logical Unit Number An address for a single (SCSI) disk drive.

MAC address Device identifier number of a Network Interface Card. In full: "media access control address".

Glossary


MaxDB A relational database system from mySQL (formerly ADABAS and SAPDB).

Media Access Control address An identifier for network devices, usually unique. The MAC address is stored physically on the device.

NAS system Network Attached Storage of any vendor (in our context: EMC NAS or NetApp Filer).

NDMPcopy NDMPcopy transfers data between Filers using the Network Data Management Protocol (NDMP).

Netboot A boot procedure for computers where the operating system is provided via a network instead of local disks.

Netweaver

SAP NetWeaver is the technical foundation of SAP solutions.

Network Appliance Filer See “Filer”.

Network Attached Storage A data storage device that is connected via a network to one or multiple computers.

Network File System A network protocol for network-based storage access.

Network Interface Card A hardware device that allows computer communication via networks.

Node A physical computer system controlled by an OS.

Node name The name of a physical node as returned by the command uname -n. Each node name within a FlexFrame environment must be unique.

Non-Volatile Random Access Memory A type of memory that retains its contents when the power is turned off.

On-Line Transaction Processing Transaction processing via computer networks.

OpenLDAP An Open Source LDAP Service Implementation.

Open Network Technology for Appliance Products The operating system of Network Appliance Filers.

Glossary


Open Source Software Software that is distributed free of charge under an open source license, such as the GNU Public License.

Oracle RAC A cluster database by Oracle Corporation.

Physical host Name of a physical computer system (node).

Power-On Self Test Part of a computer's boot process; automatic testing of diverse hardware components.

Preboot Execution Environment An environment that allows a computer to boot from a network resource without having a local operating system installed.

PRIMECLUSTER Fujitsu Siemens Computer’s high-availability and clustering software.

PRIMEPOWER

Fujitsu Siemens Computer's SPARC-based server product line.

PRIMERGY

Fujitsu Siemens Computer's i386-based server product line.

Red Hat Enterprise Linux Linux distribution by Red Hat, Inc., targeting business customers.

Reverse Address Resolution Protocol A protocol allowing resolution of an IP address corresponding to a MAC address.

SAP Service In FlexFrame: SAP Service and DB Services.

SAP service script An administration script for starting and stopping an SAP application on a virtual host.

SAP Solution Manager Service portal for the implementation, operation and optimization of an SAP solution.

SAPLogon Front-end software for SAPGUI.

SAPRouter Router for SAP services like SAPGUI or SAPTELNET.

SavVol A Celerra volume to which SnapSure copies original point-in-time data blocks from the PFS before the blocks are altered by a PFS transaction.

Glossary


Server A physical host (hardware), same as node.

Service A software program providing functions to clients.

Service type The type of an application or service (db, ci, app, agate, wgate etc.).

Single Point of Control In FlexFrame: One user interface to control a whole FlexFrame environment.

Storage LAN A virtual LAN segment within a FlexFrame environment, carrying the traffic to NAS systems.

SUSE Linux Enterprise Server A Linux distribution by Novell, specializing in server installations.

Telecommunications Network A terminal emulation program for TCP/IP networks such as the Internet.

Trivial File Transfer Protocol A simple form of the File Transfer Protocol (FTP). TFTP uses the User Datagram Protocol (UDP) and provides no security features. It is often used by servers to boot diskless workstations, X-terminals, and routers.

TFTP server A simple FTP implementation.

Virtual host The name of the virtual host on which an application runs; it is assigned to a physical node when an application is started.

Virtual Local Area Network A VLAN is a logically segmented network mapped over physical hardware according to the IEEE 802.1q standard.

Virtualization Virtualization means the separation of hardware and processes. In a virtualized environment (FlexFrame), a process can be moved between hardware nodes while staying transparent to the user and application.


10 Index A

abbreviations 149

ACC

agents 68

configuration 27

installation 9

ACC patch

installation 12

ACC users

user administration 27

C

connections between SolMan and ACC

configuration 81

D

data transfer

from SLD to the Solution Manager 106

document history 1

documentation 3

G

general preparations 3

glossary 153

L

landscape

making adaptive 113

N

notational conventions 1

P

post installation activities 21

R

related documents 2

required software 3

S

SAP services

integration 122

SAP support patches

applying 5, 7

SLD

configuration 50

registering managed application services 60

Solution Manager 3.2 SR1

installation 5

SSH

configuration 79

startup mode for the SSL provider

changing 8

T

troubleshooting 145

W

WebAS 6.40 SP15

installation 7

WebAS 6.40 with NetWeaver 04 SR1

installation 7

Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Compu-ters. This new subsidiary of Fujitsu has been renamed Fujitsu Technology So-lutions.

This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed.

Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions.

Contact and support addresses will now be offered by Fujitsu Technology So-lutions and have the format …@ts.fujitsu.com.

The Internet pages of Fujitsu Technology Solutions are available at http://ts.fujitsu.com/... and the user documentation at http://manuals.ts.fujitsu.com.

Copyright Fujitsu Technology Solutions, 2009

Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seit-dem den Namen Fujitsu Technology Solutions.

Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion.

Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind.

Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Form …@ts.fujitsu.com.

Die Internetseiten von Fujitsu Technology Solutions finden Sie unter http://de.ts.fujitsu.com/..., und unter http://manuals.ts.fujitsu.com finden Sie die Benutzerdokumentation.

Copyright Fujitsu Technology Solutions, 2009