flexframe for sap 4 - fujitsu technology...

User Guide

FlexFrame™ for SAP® 4.2AInstallation ACC 7.1 SP06

English

FlexFrame™ for SAP® Version 4.2A

Installation ACC 7.1 SP06

Edition December 2008 Document Version 1.0

Fujitsu Siemens Computers GmbH

© Copyright Fujitsu Siemens Computers GmbH 2008 FlexFrame™, PRIMECLUSTER™. PRIMEPOWER™ and PRIMERGY™ are trademarks of Fujitsu Siemens Computers Windows®. Excel® and Word® are registered trademarks of Microsoft Corporation Intel® is a registered trademark of Intel Corporation in the United States and other countries Solaris™ is a trademark of Sun Microsystems, Inc. in the United States and other countries Linux® is a registered trademark of Linus Torvalds MaxDB® is a registered trademark of MySQL AB, Sweden MySQL® is a registered trademark of MySQL AB, Sweden SAP®, SAP™ and Netweaver™ are trademarks or registered trademarks of SAP AG in Germany and in several other countries 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 SPARC™ is a trademark of SPARC International, Inc. in the United States and other countries SuSE® is a registered trademark of SuSE Linux AG Ethernet® is a registered trademark of XEROX, Inc., Digital Equipment Corporation and Intel 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.

Installation ACC 7.1

Contents 1 Introduction ..................................................................................................... 1 1.1 Requirements .................................................................................................... 1 1.2 Notational Conventions ..................................................................................... 1 1.3 Document History.............................................................................................. 1

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

3 ACC Installation............................................................................................... 5 3.1 NW7.1 for PI (ACC) Installation......................................................................... 6 3.1.1 SCS Instance .................................................................................................... 6 3.1.2 DB Instance....................................................................................................... 8 3.1.3 Primary Application Server Instance ................................................................. 9 3.2 ACC Patch Installation .................................................................................... 10 3.3 Post Installation Activities................................................................................ 20 3.3.1 Performance Setup ......................................................................................... 20 3.3.2 NetWeaver Initial Setup................................................................................... 20 3.3.3 Configuring NWA for Java System and ACC Initial Setup............................... 25

4 Configuration of ACC.................................................................................... 35 4.1 User Administration for ACC Users ................................................................. 35 4.1.1 Creating Roles................................................................................................. 35 4.1.2 Creating Groups and Assigning Roles ............................................................ 38 4.1.3 Creating Users and Assigning Users to Groups.............................................. 41 4.2 SAPHOSTAGENT........................................................................................... 43 4.2.1 Installing SAPHOSTAGENT............................................................................ 43 4.2.2 Installing SAPACOSPREP Libraries ............................................................... 44 4.2.3 Registering Host with sldreg............................................................................ 44 4.2.4 Setting Up User Exit ........................................................................................ 45 4.2.5 Starting SAPHOSTAGENT ............................................................................. 51 4.2.6 Managing LiveCache Databases..................................................................... 53 4.3 Registering Managed Application Services ..................................................... 53 4.3.1 ABAP Stack..................................................................................................... 53 4.3.2 Java Stack....................................................................................................... 59 4.4 Configuring the Adaptive Computing Landscape ............................................ 71 4.4.1 Starting ACC ................................................................................................... 71 4.4.2 Configuring Pools & Networks......................................................................... 74 4.4.3 Configuring Resources.................................................................................... 76 4.4.4 Configuring Services ....................................................................................... 82

5 Troubleshooting ............................................................................................ 95

Contents

Installation ACC 7.1

5.1 J2EE Server is Restarting................................................................................ 95 5.2 J2EE Engine Start Problem............................................................................. 96 5.3 RZ70 Failed ..................................................................................................... 97 5.4 Resource Unlock ............................................................................................. 98 5.5 Resource configuration could not be saved..................................................... 99

6 Abbreviations............................................................................................... 101

7 Glossary ....................................................................................................... 105

8 Index ............................................................................................................. 111

Installation ACC 7.1 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 2008-12-10


2 General Preparations

2.1 Required Software for an ACC Environment ● NW 7.1 for PI (ACC integrated) with a released DB and OS version

● The latest SP’s from http://service.sap.com/swdc.

● The latest SAPHOSTAGENT from http://service.sap.com/swdc

● All systems that are to be managed need to be on a patchlevel that provides the correct data transfer to SLD. ( see SAP note: 1008828 )

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

● This guide (FSC)

● Installation Guide Adaptive Computing Controller 7.1

● Special Adaptive Computing Collection note: 1008828

The ACC 7.1 guides can be found here:

http://help.sap.com/saphelp_nwpi71/helpdata/de/46/0714a4e3f34f08e10000000a114a6b/frameset.htm

Before installing SAP NetWeaver 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:

ACC = SID for NW7.1 for PI (ACC) installation

bx600-1 = Host for ACC installation

com = Pool name

jcacc = Virtual host name of ACC system

cn1 = Control Node 1


http://service.sap.com/


3 ACC Installation Install a NW7.1 for PI and the latest Service Pack at the moment SP06 in a FlexFrame enviroment

Please make sure that the FA Application Agents are stopped on the hosts that you are installing SAP Software on. Please check FF Installation for SAP guide for additional hints installing NW7.1 in FlexFrame

Known issues and bugs:

1. Please create user sapadm as a member of group sapinst with the script ff_user_adm.pl.

2. Create the hostctrl directory manually (see section 4.2.1).

Change directory /usr/sap/adaptive to /usr/sap/hostctrl in LDAP.

3. When using ff_sid_adm.pl please select sapversion 7.0 at the moment.

4. Use new FFstart/stop scripts because of new pathes and profiles in NW7.1 or use sapdb <SID> start, startsap SCS<ID> scs<sid> and startsap J<ID> jc<sid>.

5. Workaround for NW7.1 start on Linux (server0 hang up): Change system parameter java.security.egd = file:/dev/./urandom with the Management Tool and don’t forget to restart the instance. The dot in the path is very important!

6. At the moment instance ASCS is not available to use in ACC. Special sapstartsrv (version 7.11) is needed and hotfix LMTOOLS06P_1-2000xxxx.SCA.

7. As a result of a bug please set in ACC configuration Solaris Instances for “Required Memory” to 0.

ACC Installation NW7.1 for PI (ACC) Installation

6 Installation ACC 7.1

3.1 NW7.1 for PI (ACC) Installation

3.1.1 SCS Instance ● Select Central Services Instance (SCS) and click on Next.

NW7.1 for PI (ACC) Installation ACC Installation


● Select Custom mode and click on Next. Follow the SAP Installation Guide.

● If the following message appears, use the FlexFrame script sapscs or startsap

SCS<ID> scs<sid> to start the instance.

ACC Installation NW7.1 for PI (ACC) Installation


3.1.2 DB Instance ● Enter the required parameters and click on Next.

NW7.1 for PI (ACC) Installation ACC Installation


● Enter the required parameters and click on Next.

3.1.3 Primary Application Server Instance ● When an error occurred in phase Start java engine please start it manually with

startsap J<ID> j(c)<sid> and click on Retry when the instance is up and running. It could take some minutes to start the instance.

● With jcmon pf=<instance_profile> -expert you are able to check if server0 is in state running.

● If not, please use workaround described below to get server0 running.

ACC Installation ACC Patch Installation


3.2 ACC Patch Installation After finishing the ACC installation successfully, proceed with the patch installation described in SAP ACC collective note 1008828, chapter 2.

cn1:~ # ssh -X accadm@bx600-1 Password: jcacc:accadm 4> cd /usr/sap/ACC/J04/j2ee/JSPM jcacc:accadm 5> ./go ...

ACC Patch Installation ACC Installation


● Enter the user name and the password and click on Log On.



● Make sure that all downloaded NW7.1 SP06 files were unpack to the Inbox directory and click on Next.

If your are not confirm with JSPM, please read the SP Stack Guide and the relevant SAP note.



● Click on Next.



● Check if every status is OK and click on Next.



● Enter user name and password and click on Next.



● Click on Exit and restart JSPM.



● Click on Next.



● In case of an error start instance manually. Login as <sid>adm and use startsap SCS<ID> scs<sid> and startsap J<ID> j(c)<sid>.

● Click on Resume.

Please take care of your DB logs while deployment is running.



● Check if every status is DEPLOYED and click on Exit.

ACC Installation Post Installation Activities


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

3.3.1 Performance Setup For getting a better performance and increasing the load for ACC please check and adjust the parameters SAP NW AS Java Engine in note 1008828, chapter 3.1. Don’t forget to set the additional VM Parameter –DAcCdpBypass to true as it is described in note 1008828, chapter 2.1.

3.3.2 NetWeaver Initial Setup Before you start with ACC configuration you have to finish the NetWeaver configuration.

● Logon to NWA, open the Configuration Wizard and start Netweaver initial setup.

Post Installation Activities ACC Installation


● Enter passwords and click on Continue.



● Click on Continue.




As of note 1008828, chapter 3.2: It’s recommended to have a local SLD for ACC. For selecting an ObjectServerName please use the Info button.



3.3.3 Configuring NWA for Java System and ACC Initial Setup

● Select Configure NWA for Java System and click on Start.



● Select Custom and click on Continue.



● Enter passwords and click on Continue.



● Type in a name and click on Continue.



● Enter the required parameters (see example below) and click on Next.

Find more details in the ACC Configuration Guide.


4 Configuration of ACC

4.1 User Administration for ACC Users Login to the user administration page: http://jcacc:50400/nwa/identity

4.1.1 Creating Roles ● Check if the roles are available with the relevant actions.

If not, create the roles for the various activities in ACC.

The relationship between roles and actions is shown in the following table.

Role Name Service / Application Action Name

ACC_Observing tc~lm~aci~engine~app Observing

http://jcacc:50400/nwa/identity

Configuration of ACC User Administration for ACC Users


Role Name Service / Application Action Name

ACC_Operation tc~lm~aci~engine~app Operation OperationExceptionHandling

ACC_Configuration tc~lm~aci~engine~app Configuration ServerEnable ServiceEnable Schedule CustomizeLink

ACC_Archiving tc~lm~aci~engine~app Archiving

Example for ACC_Observing

● Enter the role name under the General Information tab.

User Administration for ACC Users Configuration of ACC


● Navigate to the Assigned Actions tab and add the corresponding service.

● Click on Save and continue with creating roles.



4.1.2 Creating Groups and Assigning Roles ● Check if the groups are available with the relevant roles.

If not, execute the following steps.

1. Create the following groups for the defined actions in ACC:

AC_Observer AC_Operator AC_Administrator

2. Assign the roles to the created groups. The relationship between roles and groups is shown in the following table.



Group Roles

AC_Observer ACC_Observing

AC_Operator ACC_Observing, ACC_Operation

AC_Administrator ACC_Observing, ACC_Operation, ACC_Configuration, ACC_Archiving

Example for AC_Observer

● Enter the group name under the General Information tab.



● Navigate to the Assigned Roles tab and add the corresponding roles.

● Click on Save and continue with creating groups.



4.1.3 Creating Users and Assigning Users to Groups Assign individual users to the various created ACC groups.

Example for assigning the user AccAdmin to the AC_Administrator group

● Enter the required parameters (see below).



● Navigate to the Assigned Groups tab and add the AC_Administrator group to the AccAdmin user.

● Click on Save and go on with creating users if necessary.

For using AccAdmin as login user in SLD (see section 0) please add group administrators also.

After creating a user, don’t forget to login and to change the password! If you like to change the password for this account used in the sldreg configfile later on, do not forget to change it in every sldreg configfile (see section 4.2.3).

SAPHOSTAGENT Configuration of ACC


4.2 SAPHOSTAGENT

4.2.1 Installing SAPHOSTAGENT You can find the newest SAPHOSTAGENT.SAR in the SAP Software Distribution Center of the SAP Service Marketplace (http://service.sap.com/swdc). Log on with your SAP Service Marketplace ID. In the navigation bar, choose

Download -> Support Packages and Patches -> Entry by Application Group -> SAP NetWeaver -> SAP NETWEAVER -> SAP NETWEAVER 7.1 -> Entry by Component -> Application Server ABAP -> SAP KERNEL 7.10 32/64-BIT -> <operating_system> -> Database Independent

and download the archive.

For FlexFrame releases which do not have /usr/sap/hostctrl automount point the following steps have to be done:

Change the Ldap entry

ou=automount, ou=auto_usr_sap (ou=auto.usr_sap), cn=adaptive

to

ou=automount, ou=auto_usr_sap (ou=auto.usr_sap), cn=hostctrl

for every pool. Don’t forget to change adaptive to hostctrl in the path of attribute automountInformation.

For every pool on volFF:

cn1: cd /FlexFrame/volFF/pool-xxx/sap cn1: mv adaptive hostctrl

If /usr/sap/hostctrl is available go on with the following steps. (These steps have to be done for every pool and OS image Linux and/or Solaris.)

# mkdir /usr/sap/hostctrl/new # cd /usr/sap/hostctrl/new

Copy the OS relevant SAPHOSTAGENT file to /usr/sap/hostctrl/new:

# /sapmnt/ACC/exe/uc/linux86_64/SAPCAR -xvf SAPHOSTAGENT_19-10004201.SAR SAPCAR: processing archive SAPHOSTAGENT_19-10004201.SAR x hostagent.lst x hostagent.mf ... # ./saphostexec –upgrade

http://service.sap.com/swdc

Configuration of ACC SAPHOSTAGENT


The /etc/init.d/sapinit script will be changed during upgrade. Please take care that the relevant file system is readable for the upgrade phase.

4.2.2 Installing SAPACOSPREP Libraries You have to download the newest sapacosprep library for Solaris and for Linux 32/64 only in case of using SAN from:

https://partners.fujitsu-siemens.com/com > Product catalog > Dynamic Infrastructures > FlexFrame for SAP > Downloads (for certified FlexFrame installers only)

Customers please send an email to [email protected]

Copy the library for the relevant platform to /usr/sap/hostctrl/exe.

For Linux 32/64 :

# chown sapadm:sapsys libsapacosprep_FSC.so # chmod 755 libsapacosprep_FSC.so

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

# chown sapadm:sapsys libsapacosprep.so # chmod 755 libsapacosprep.so # ln –s libsapacosprep.so libsapacosprep_FSC.so

4.2.3 Registering Host with sldreg Create an sldreg connection file by running

# cd /usr/sap/hostctrl/exe # export LD_LIBRARY_PATH=/usr/sap/hostctrl/exe:$LD_LIBRARY_PATH # ./sldreg –configure slddest.cfg Use configuration file 'slddest.cfg' for output! Please specify the HTTP connect information: [User, Password, Host, Port, HTTP/HTTPS] User Name : AccAdmin # Must be a member of administrator group Password : ******** Verify Password : ******** Server Host : jcacc # ACC host with SLD Port [80,443,1024..65535]: 50400 Use HTTPS? (y/n): n =================== Entered Information ===================

https://partners.fujitsu-siemens.com/com

mailto:[email protected]



User: AccAdmin Passwd: (secret) Host: jcacc Port: 50400 HTTPS: n =================== Write this information to secure file 'slddest.cfg'? [y=yes/n=no/q=quit] y Fri Feb 22 10:15:45 2008 Renamed file 'slddest.cfg' to 'slddest.cfg.20080222101545' Fri Feb 22 10:15:45 2008 Writing data to encrypted file 'slddest.cfg' Fri Feb 22 10:15:45 2008 Data written to secured data file 'slddest.cfg' Fri Feb 22 10:15:45 2008 Using destination file 'slddest.cfg'. Fri Feb 22 10:15:45 2008 No key file 'slddest.cfg.key' used. Fri Feb 22 10:15:45 2008 Use encryted destination file 'slddest.cfg' as data source Fri Feb 22 10:15:45 2008 Configuration data successfully stored in file: slddest.cfg

Currently the host agent doesn’t register all computer system properties required by ACC. As a workaround execute the following command:

# ./saposcol –b |./sldreg –connectfile slddest.cfg hu Mar 27 11:05:57 2008 SLD Registration Program [2.0] (Mar 22 2008) [Non-Unic ode] Thu Mar 27 11:05:57 2008 No XML data input file set. Will read input data from s tandard input. Thu Mar 27 11:05:57 2008 Supplier Name: ComputerSystem / Supplier Version: 1.0 / Supplier Vendor: / CIM Model Version: 1.3.21 Thu Mar 27 11:05:57 2008 Group: ...

4.2.4 Setting Up User Exit ACC User Exit works as an interface to the FA Agents.

Add the following two lines to the host_profile file:

service/hook/sap_control = /usr/sap/hostctrl/exe/sap_control.sh %p %h %s %n service/hook/db_control = /usr/sap/hostctrl/exe/db_control.sh %p %h %s

Create the shell script sap_control.sh:

# !/bin/bash # User Exit Script for ACC (instances) echo "Running User Exit Script"



echo "/ ---- " $0 $* " ---- /" case $1 in "prestart") case $2 in "ci"*) /FlexFrame/scripts/sapci $3 prestart exit_code=$? ;; "jc"*) /FlexFrame/scripts/sapjc $3 prestart exit_code=$? ;; "ascs"*) /FlexFrame/scripts/sapascs $3 prestart exit_code=$? ;; "scs"*) /FlexFrame/scripts/sapscs $3 prestart exit_code=$? ;; "app"*) /FlexFrame/scripts/sapapp $4 $3 prestart exit_code=$? ;; "j"$4*) /FlexFrame/scripts/sapj $4 $3 prestart exit_code=$? ;; "ers"*) /FlexFrame/scripts/sapers $4 $3 prestart exit_code=$? ;; esac echo "/ PRESTART position executed /" if [ $exit_code -ge 1 -a $exit_code -le 4 ];then exit 4 else exit $exit_code fi ;; "poststart") case $2 in "ci"*)



/FlexFrame/scripts/sapci $3 poststart exit_code=$? ;; "jc"*) /FlexFrame/scripts/sapjc $3 poststart exit_code=$? ;; "ascs"*) /FlexFrame/scripts/sapascs $3 poststart exit_code=$? ;; "scs"*) /FlexFrame/scripts/sapscs $3 poststart exit_code=$? ;; "app"*) /FlexFrame/scripts/sapapp $4 $3 poststart exit_code=$? ;; "j"$4*) /FlexFrame/scripts/sapj $4 $3 poststart exit_code=$? ;; "ers"*) /FlexFrame/scripts/sapers $4 $3 poststart exit_code=$? ;; esac echo "/ POSTSTART position executed /" if [ $exit_code -ge 1 -a $exit_code -le 4 ]; then exit 4 else exit $exit_code fi ;; "prestop") case $2 in "ci"*) /FlexFrame/scripts/sapci $3 prestop exit_code=$? ;; "jc"*) /FlexFrame/scripts/sapjc $3 prestop exit_code=$?



;; "ascs"*) /FlexFrame/scripts/sapascs $3 prestop exit_code=$? ;; "scs"*) /FlexFrame/scripts/sapscs $3 prestop exit_code=$? ;; "app"*) /FlexFrame/scripts/sapapp $4 $3 prestop exit_code=$? ;; "j"$4*) /FlexFrame/scripts/sapj $4 $3 prestop exit_code=$? ;; "ers"*) /FlexFrame/scripts/sapers $4 $3 prestop exit_code=$? ;; esac echo "/ PRESTOP position executed /" if [ $exit_code -ge 1 -a $exit_code -le 4 ]; then exit 4 else exit $exit_code fi ;; "poststop") case $2 in "ci"*) /FlexFrame/scripts/sapci $3 poststop exit_code=$? ;; "jc"*) /FlexFrame/scripts/sapjc $3 poststop exit_code=$? ;; "ascs"*) /FlexFrame/scripts/sapascs $3 poststop exit_code=$? ;;



"scs"*) /FlexFrame/scripts/sapscs $3 poststop exit_code=$? ;; "app"*) /FlexFrame/scripts/sapapp $4 $3 poststop exit_code=$? ;; "j"$4*) /FlexFrame/scripts/sapj $4 $3 poststop exit_code=$? ;; "ers"*) /FlexFrame/scripts/sapers $4 $3 poststop exit_code=$? ;; esac echo "/ POSTSTOP position executed /" if [ $exit_code -ge 1 -a $exit_code -le 4 ]; then exit 4 else exit $exit_code fi ;; esac exit 0

Create the shell script db_control.sh:

# !/bin/bash # User Exit Script for ACC database echo "Running User Exit Script" echo "/ ---- " $0 $* " ---- /" case $1 in "prestart") case $2 in "lc"*) /FlexFrame/scripts/saplc $3 prestart exit $? ;; "db"*) /FlexFrame/scripts/sapdb $3 prestart exit $?



;; esac echo "/ PRESTART position executed /" exit 0 ;; "prestop") case $2 in "lc"*) /FlexFrame/scripts/saplc $3 prestop exit $? ;; "db"*) /FlexFrame/scripts/sapdb $3 prestop exit $? ;; esac echo "/ PRESTOP position executed /" exit 0 ;; "poststart") case $2 in "lc"*) /FlexFrame/scripts/saplc $3 poststart exit $? ;; "db"*) /FlexFrame/scripts/sapdb $3 poststart exit $? ;; esac echo "/ POSTSTART position executed /" exit 0 ;; "poststop") case $2 in "lc"*) /FlexFrame/scripts/saplc $3 poststop exit $? ;; "db"*) /FlexFrame/scripts/sapdb $3 poststop exit $?



;; esac echo "/ POSTSTOP position executed /" exit 0 ;; esac exit 0

Perform the following commands:

# chmod 750 sap_control.sh db_control.sh # chown root:root sap_control.sh db_control.sh

4.2.5 Starting SAPHOSTAGENT For Linux only:

As of Note 1008828: For Linux a PAM authentication policy is required.

Create a file named sapstartsrv in /etc/pam.d with the following content:

auth sufficient pam_unix2.so auth required pam_unix_auth.so account sufficient pam_unix2.so account required pam_unix_acct.so auth requisite pam_unix_auth.so nullok # for SLES 10 only

Perform the following commands on every Linux and/or Solaris host:

# ./saphostexec pf=/usr/sap/hostctrl/exe/host_profile -stop # ./saphostexec pf=/usr/sap/hostctrl/exe/host_profile

Check if the sapinit script is in rc3.d with the saphostexec commands for automatical startup after boot.

All steps for the SAPHOSTAGENT installation have to be done for every OS!



Check if the hosts (e.g. bx600-1) are registered in the SLD: http://jcacc:50400/sld.

● Select Technical Systems and choose the type Computer Systems:

If some information is missing ( e.g. Operating system) it is helpful to run the following commands on the hosts.

Manual registration of a host in SLD:

# cd /usr/sap/hostctrl/exe # export LD_LIBRARY_PATH=/usr/sap/hostctrl/exe:$LD_LIBRARY_PATH # ./saposcol -b | ./sldreg -connectfile slddest.cfg

http://jcacc:50400/sld

Registering Managed Application Services Configuration of ACC


4.2.6 Managing LiveCache Databases To allow the Host Agent control on LiveCache Databases. ...

1. Logon as user <SID>adm in the LiveCache database host.

2. Create an XUSER file with an entry for the control user with the user key c:

# su - <sid>adm # xuser -u control,<password> -U c -d <DB name> -n <hostname> -S INTERNAL set The xuser command is relevant to MaxDB version 7.4.3.

3. Verify the created XUSER file entry:

# dbmcli -U c db_state

4. Configure the standard LiveCache user:

# dbmcli -U c user_sap sap<DB name>,<password>

For more information about creating and authenticating XUSER entries, see SAP note 39439.

For more information about setting the default LiveCache user, see SAP note 616555.

4.3 Registering Managed Application Services In case of an ABAP +Java system (e.g. Solutionmanager 4.0) please register at first the Java stack of the system and afterwards the ABAP stack.

4.3.1 ABAP Stack It is important to check SAP note 1052457 before starting RZ70.

● Logon to the system and execute transaction RZ70. All relevant instances App’s must be up and running for every system to be managed.

● Enter the host and the service of the gateway (gateway running in the scs instance of ACC, e. g.: Host: scsacc, Service: sapgw05.

● If the area Data Collection Programs is empty, click on the Proposal button to enter the right programs (as below) with all programs marked as Active.

● Click on the Activate and Execute button.

Configuration of ACC Registering Managed Application Services


● Click on Yes.



● If the connection to SLD is not available, please check under SLD Administration -> Configuration -> datasupplier whether or not the right GatewayHost and GatewayService is selected.

● If not, correct it.



Check if the ABAP instance is visible now in the SLD:

● Start a browser and connect to the SLD.

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

● Navigate to Technical Systems and choose the type AS ABAP.

The registered application services should now appear in the list.



4.3.1.1 ASCS of ABAP Stack

For registering ASCS instance in SLD the sapstartsrv (7.11) for ASCS is used.

Therefore you have to use sldreg to create a SLD connectfile.

# su - lsmadm # cd /usr/sap/LSM/ASCS12/exe # ./sldreg –configure slddest.cfg Use configuration file 'slddest.cfg' for output! Please specify the HTTP connect information: [User, Password, Host, Port, HTTP/HTTPS] User Name : AccAdmin # Must be a member of administrator group Password : ******** Verify Password : ******** Server Host : jcacc # ACC host with SLD Port [80,443,1024..65535]: 50400 Use HTTPS? (y/n): n =================== Entered Information =================== User: AccAdmin Passwd: (secret) Host: jcacc Port: 50400 HTTPS: n =================== Write this information to secure file 'slddest.cfg'? [y=yes/n=no/q=quit] y Fri Feb 22 10:15:45 2008 Renamed file 'slddest.cfg' to 'slddest.cfg.20080222101545' Fri Feb 22 10:15:45 2008 Writing data to encrypted file 'slddest.cfg' Fri Feb 22 10:15:45 2008 Data written to secured data file 'slddest.cfg' Fri Feb 22 10:15:45 2008 Using destination file 'slddest.cfg'. Fri Feb 22 10:15:45 2008 No key file 'slddest.cfg.key' used. Fri Feb 22 10:15:45 2008 Use encryted destination file 'slddest.cfg' as data source Fri Feb 22 10:15:45 2008 Configuration data successfully stored in file: slddest.cfg # cp slddest.cfg /usr/sap/LSM/SYS/global Stop sapstartsrv process for ASCS12 # sapascs LSM restart



4.3.2 Java Stack

4.3.2.1 Java Stack <= NW2004s(7.0)

It is important to check SAP note 909797 before starting Visual Administrator.

Start Visual Administrator on the J2EE engine host that is to be managed. (This should be done for every JAVA system to be managed). All Services (J and SCS) 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 Connect.

● 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 shown above (1) and click on Save (2).

● Trigger a test connection to the SLD (3).

● Click on Yes.

● Click on OK.

2.

1.

3. Test connect to SLD



Check if the JAVA instance is visible now in the SLD:

● Start a browser and connect to the SLD.

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

● Navigate to Technical Systems and choose the type AS JAVA.

The registered application services should now appear in the list.



● Check SLD if SCS instance is available. If not, click on Add SCS Instance.



● Enter information about the central services instance and click on Save.



● Navigate to Home -> CIM Instances and select the class BC Central Service Instance.



● Select the new SCS instance and change under Properties the virtual host name in the Caption field and the SystemHome field, e.g. dbbw1-se to scsbw1.

● Click on Save.



Now the SCS instance should appear in the ACC Service Configuration.



4.3.2.2 Java Stack >= NW7.1

All services (J and SCS) must be up and running.

● Navigate to NWA: http://jcacc:50400/nwa

● Select Configuration Management -> Security -> Destinations.

● Select the right URL of ACC instance and check login data.

http://jcacc:50400/nwa



● Click on Save and click on Ping-Destination to check if the connection to SLD is working.



● Go back to Configuration Management -> Infrastructure -> SLD Data Supplier Configuration.

● Click on Collect and Send Data and check under Collect and Send Data completed successfully if it is successful.

Configuring the Adaptive Computing Landscape Configuration of ACC


4.4 Configuring the Adaptive Computing Landscape

This chapter describes how ACC make the landscape adaptive. See also the “Configuring the Adaptive Computing Landscape” on


4.4.1 Starting ACC Call the URL

http://<acc_host>:<port>/webdynpro/dispatcher/sap.com/tc~lm~itsam~ui~mainframe~wd/FloorPlanApp?applicationID=com.sap.itsam. ops.adaptive

or

http://<acc_host>:<port>/acc



Configuration of ACC Configuring the Adaptive Computing Landscape


● First, logon to ACC.



● Choose Configuration in the left pane.



4.4.2 Configuring Pools & Networks ● Navigate to Pool- & Network Configuration.

● Select the Pools tab.

● Click on Edit and then on Add and enter the required data.

● Click on Save.

Here you have to decide:

1. ACC pools like FlexFrame pools: You have to install FlexFrame in a “Common pool” with network routing to all other pools (Security restrictions!)

2. ACC pools like FlexFrame groups of hardware: You have to install ACC in every FlexFrame pool.



● Select the Network tab.

● Click on Edit and then on Add and enter the required data.

● Click on Save.



4.4.3 Configuring Resources Step 1

● Navigate back to Configuration -> Resource Configuration to see the servers that are already registered.

● Select the first server and switch to Edit mode.

● Activate Adaptive Management (chechbox AC Managed) and select the required pool.

● Test the connection to the server by clicking on Connection Test.

● Click on Next.



Step 2

● Activate Adaptive Enablement (checkboxes AC Enabled and AC Operational).

● For resource control you can select SAPS for your server, e.g. 500.

● To configure a network, add VLANs via the New Interface Id field. For each VLAN click on Add Interface Id and select the corresponding network.

The example below shows Linux VLANs. For Solaris please use ipmp-client and ipmp-server as Linux VLANs (vlan10 and vlan11).

● Click on Next.



Step 3

● Under step 3 you can select servers with equal conditions and you can configure them in one step by clicking on Save & Apply Mass Configuration.



● In the Server Options dialog box you can select different server options.

● Go on with Assume.



● If you have configured all servers you can check them by clicking on Show Resources.



If some information is missing, it is helpful to run the following commands on the hosts:

# cd /usr/sap/hostctrl/exe # export LD_LIBRARY_PATH=/usr/sap/hostctrl/exe:$LD_LIBRARY_PATH # ./saposcol -b | ./sldreg -connectfile slddest.cfg



4.4.4 Configuring Services ● Navigate back to Configuration -> Service Configuration to see the

servers that are already registered.

● If there is no service available, please switch to SLD and add your system to the relevant landscape (see the figure on the following page).



● Under Technical Systems select the system to be managed and add it to the relevant landscape.



● Expand the service you want to integrate in ACC and select a database (for example). Please do not configure the database with the physical hostname.



● Start configure database.

Step 1

● Select and fill in like the example below and press Next for step 2.



Step 2




Step 3

● In case of using NAS please activate the Automounter checkbox.



● In case of using SAN select Type=SR, Mountpoint=<SID>, FS/SRID-Typ=FFSRID, Partner-ID=FSC.



Step 4

● Click on Save.



● Select the next instance, e.g. scs.

Step 1




Step 2




Step 3

● Activate the Automounter checkbox and click on Next.



Step 4

● Click on Save.

● Go on to configure the relevant instances like the examples above.



Start/Stop/Relocate Application Services

● Select Services in the left pane. Here you are able to start/stop and relocate the configured instances.

There is more help available at http://help.sap.com

http://help.sap.com/


5 Troubleshooting

5.1 J2EE Server is Restarting A valid license key is missing.

● Use Visual Administrator or NWA >= NW7.1 to bring in a valid licence key file.

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)

Troubleshooting J2EE Engine Start Problem


5.2 J2EE Engine Start Problem If server0 in the jcmon tool is always in phase starting applications please change the value of the VM parameter java.security.egd.

# su – accadm # jcmon pf=/usr/sap/ACC/SYS/profile/ACC_J04_jcacc -expert

● Change the value file:/dev/urandom to file:/dev/./urandom.

● Click on set.

RZ70 Failed Troubleshooting


● Click on the diskette symbol to save the modification.

● Restart java instance (server0).

5.3 RZ70 Failed If RZ70 fails:

● Use transaction sldcheck.

● Use transaction sm59.

● Test connections to SLDUC or SLDNUC.

Troubleshooting Resource Unlock


5.4 Resource Unlock If an error messages like Resource could not be locked occurs or some resources are not available,

● navigate to NWA -> Problem Management -> Locks and release the locks.

Resource configuration could not be saved Troubleshooting


5.5 Resource configuration could not be saved If an error messages like Resource configuration could not be saved occurs,

● navigate to NWA -> Operation Management -> Java EE Application and

● click on Refresh for routing service or

● start and stop the application.


6 Abbreviations ABAP Advanced Business Application Programming

ACC Adaptive Computing Controller

ACI Adaptive Computing Infrastructure

ACPI Advanced Configuration and Power Interface

APM Advanced Power Management

APO Advanced Planner & Optimizer

CIFS Common Internet File System

DHCP Dynamic Host Configuration Protocol

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

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

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

Abbreviations


OSS Open Source Software

POST Power-On Self Test

PCL PRIMECLUSTER

PW PRIMEPOWER

PXE Preboot Execution Environment

PY PRIMERGY

RAID Redundant Array of Independent (or Inexpensive) Disks

RARB 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

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

Abbreviations


WAFL Write Anywhere File Layout

XSCF Extended System Control Facility


7 Glossary Adaptive Computing Controller (ACC)

SAP system for monitoring and controlling SAP environments.

Advanced Business Application Programming (ABAP) Proprietary programming language of SAP.

Advanced Power Management (APM) A standard for power saving and management in computers.

Application Agent A software program for monitoring and managing applications.

Application Node (AN) 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.

BOOTPARAM Boot time parameters of the Solaris kernel.

BRBACKUP SAP backup and restore tools.

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

Common Internet File System (CIFS) 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.

Glossary


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

Control Station An Application Node running SAP ACC.

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

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

Enterprise Resource Planning (ERP) 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 Fibre Channel is a serial computer bus intended for connecting high-speed storage devices to computers.

Filer Network attached storage for file systems.

FlexFrame™ for mySAP™ Business Suite FlexFrame™ for mySAP™ Business Suite is a radically new architecture for mySAP environments. It exploits the latest business-critical computing technology to deliver major cost savings for SAP customers.

Gigabit Ethernet A Local Area Network which supports data transfer rates of 1 Gigabit (1,024 Megabits) per second.

Host name Name of a physical server as seen from outside the network. One physical server may have multiple host names.

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

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

Glossary


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

Local Area Network (LAN) 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 (LUN) An address for a single (SCSI) disk drive.

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

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

mySAP Business Suite The main ERP software produced of SAP AG.

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 mySAP Business Suite solutions.

Network Appliance Filer See “Filer”.

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

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

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

Node A physical computer system controlled by an OS.

Glossary


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 (NVRAM) 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.

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

Oracle RAC A cluster database by Oracle Corporation.

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

Power-On Self Test (POST) 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 Computers’ high-availability and clustering software.

PRIMEPOWER

Fujitsu Siemens Computers’ SPARC-based server product line.

PRIMERGY

Fujitsu Siemens Computers’ i386-based server product line.

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

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

SAP Service In FlexFrame: SAP Service and DB Services.

Glossary


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.

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 the Filer.

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

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.

Glossary


Virtual host Before an application starts, the virtual host name is assigned to the physical host where the application is to run. From the application's perspective, it always runs on the same virtual host, even if the application is moved to another physical host.

The following rule forms the host names of virtual services: <service_type>[<ID>]<SID>[<-LAN type]

where <service_type> can be one of:

ci - central instance (ABAP) db - database instance app - application instance (ABAP) ascs - ABAP SAP central services instance scs - JAVA SAP central services instance jc - JAVA central instance j - JAVA application instance

<ID> is a number from 00 to 96 (except: 2, 25, 43, 72, 89) for the service types app and j only. It is empty for other service types.

<SID> is the system ID of an SAP system.

<LAN type> -se Server LAN empty string Client LAN

This host name formation rule for virtual services is mandatory in version 3.2 of the FlexFrame solution. Some components rely on this rule.

Within a FlexFrame environment, each node name must be unique. However, each node may have multiple host names that are derived from the node name by a defined naming rule.

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. (See SAP Note No. 611361)

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.


8 Index A

ABAP stack 53

abbreviations 101

adaptive computing landscape

configuring 71

configuring networks 74

configuring pools 74

configuring resources 76

configuring services 82

starting ACC 71

C

configuration 35

user administration 35

D

document history 1

documentation 3

G

general preparations 3

glossary 105

I

installation 5

NW7.1 for PI 6

DB instance 8

primary application server instance 9

SCS instance 6

J

J2EE engine start problem 96

J2EE server is restarting 95

Java stack 59

M

managed application services

ABAP stack 53

Java stack 59

registering 53

N

notational conventions 1

P

patch installation 10

post installation 20

ACC inital setup 25

NetWeaver initial setup 20

NWA for Java system 25

performance setup 20

R

required software 3

resource configuration not saved 99

resource unlock 98

RZ70 failed 97

S

SAPHOSTAGENT 43

installing 43

installing SAPACOSPREP libraries 44

managing LiveCache databases 53

registering host with sldreg 44

Index


setting up user exit 45

starting 51

T

troubleshooting 95

U

user administration

assigning roles 38

assigning users to groups 41

creating groups 38

creating roles 35

creating users 41

V

valid license key missing 95

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

flexframe for sap 4 - fujitsu technology...

Documents