Technology Consultants System Administrators

Transcription

1 PUBLIC Installation Guide SAP NetWeaver 7.0 SR3 Standalone Engine SAP livecache Technology: Windows Target Audience Technology Consultants System Administrators Document version: /28/2008

2 Document History Caution Before you start the implementation, make sure you have the latest version of this document, which you can find here: The following table provides an overview of the most important document changes. Version Date Description 1.0 3/28/2008 Initial Version 2/54 PUBLIC 03/28/2008

3 Table of Contents Chapter 1 Introduction New Features Before You Start SAP s for the Installation More Information on SAP Service Marketplace Naming Conventions Chapter 2 Planning Software Requirements Check Chapter 3 Preparation Choosing a livecache System Name Checking livecache File Systems Installing the Java Runtime Environment Preparing the Installation Media Preparing the Installation DVDs Downloading Installation DVDs from SAP Service Marketplace (Optional). 13 Chapter 4 Installation Installing livecache Using SAPinst Running SAPinst to Install livecache Using SAPinst GUI Interrupted Installation with SAPinst Performing a Remote Installation with SAPinst (Optional) Starting SAPinst GUI Separately (Optional) Chapter 5 Post-Installation Common Post-Installation Activities Setting Up the Connection to the livecache Instance Checking the livecache Instance Changing Password of Created Users Setting Up a livecache Super User Post-Installation Activities Specific to Workforce Deployment Server Installing the Administration Tools Secure Sockets Layer Protocol for Database Server Communication /28/2008 PUBLIC 3/54

4 5.4.1 Installing the SAP Cryptographic Library Generating the Personal Security Environment Chapter 6 Additional Information Operating Information for livecache Uninstalling livecache Troubleshooting with SAPinst Chapter 7 High Availability with Microsoft Cluster Service Planning Distribution of Components to Disks for MSCS Directories in an MSCS Configuration IP Addresses in an MSCS Configuration Obtaining IP Addresses for MSCS Preparation Checking Hardware and Software Requirements for MSCS Assigning Drive Letters for MSCS Mapping Host Names to IP Addresses for MSCS Checking the Mapping of Host Names for MSCS Installation Installing livecache on the First Node Configuring livecache on the Additional Node /54 PUBLIC 03/28/2008

5 1 Introduction 1 Introduction This documentation explains how to install the server for SAP livecache Technology. SAP livecache is used in SAP Supply Chain Management (SCM) and Workforce Deployment (WFD). livecache is SAP s memory-resident object management technology that enables higher levels of performance in business processing for SAP Supply Chain Management (SCM) and Workforce Deployment (WFD) Server. Caution Make sure you have the latest version of this document. See the version number on the front page. You can always find the latest version at: Installation Standalone Engines For more information about SAP SCM technology, see SAP SCM Technology For more information about Resource Planning, see either of the following: If required, you can install livecache with Microsoft Cluser Service (MSCS). For more information, see High Availability with Microsoft Cluster Service [page 35]. 1.1 New Features Area Description Database SAP MaxDB Release Operating systems SAP s Links in PDF files See the Product Availability Matrix (PAM) at: You can now access SAP s directly from your PDF. Place the cursor on the SAP <number> and double-click. A separate browser windows opens and the SAP is displayed. You can use the new links in the PDF files of the guides as follows: Click the section headings such as New Features to jump back to the table of contents at the beginning of the guide. Click an internet link such as to jump to the corresponding internet page. 03/28/2008 PUBLIC 5/54

6 1 Introduction 1.2 Before You Start 1.2 Before You Start Make sure that you read the following sections before you start the installation: SAP s for the Installation [page 6] Information Available on SAP Service Marketplace [page 6] Naming Conventions [page 6] SAP s for the Installation Read the following SAP s, which you can find at Number Title livecache 7.6 Installation Parameter values as of livecache version 7.6 and RFC destination for global working on the livecache More Information on SAP Service Marketplace You can find more information on SAP Service Marketplace as follows: Description livecache Installation Guide Product Availability Matrix (PAM) SAP s Address Installation Installation Standalone Engines Naming Conventions We use the following naming conventions in this documentation: Variable INST_DIR LC_HOST LC_NAME Description Installation directory Domain or server name where the livecache is installed Name of livecache instance consisting of three capital letters 6/54 PUBLIC 03/28/2008

7 1 Introduction 1.2 Before You Start Variable LC_HOME LC_USER Description Directory where the livecache software is installed Operating system user for the livecache instance 03/28/2008 PUBLIC 7/54

8 This page is intentionally left blank.

9 2 Planning 2 Planning To plan the installation you need to: Check the software requirements [page 9] Check the hardware requirements by using the Quick Sizer tool, which you can find at: Software Requirements Check For the most up-to-date information on the database and operating system of your product, check the SAP Product Availability Matrix (PAM) at: 03/28/2008 PUBLIC 9/54

10 This page is intentionally left blank.

11 3 Preparation 3 Preparation Prerequisites You have completed planning the installation [page 9]. Process Flow You have to complete the following preparations: 1. You choose a livecache system name [page 11]. 2. You check livecache file systems [page 11]. 3. You prepare the system for SAPinst [page 12]. 4. You prepare the installation media [page 13]. 3.1 Choosing a livecache System Name Choose a livecache name, <LC_NAME>, noting the following restrictions. The livecache system name must be unique throughout your organization and must consist of exactly three alphanumeric characters. Only uppercase letters are allowed. The first character must be a letter (not a digit). Since the following names are reserved for SAP systems, you cannot use them for your livecache system: ADD ALL AND ANY ASC B20 B30 BCO BIN COM DBA END EPS FOR GID IBM INT KEY LOG MON NOT OFF OMS P30 RAW ROW SAP SET SGA SHG SID SQL SYS TMP UID VAR Choose your livecache system name carefully. It is complex to rename and you have to reinstall livecache. 3.2 Checking livecache File Systems Make sure that you have enough space for the following on your disk: 03/28/2008 PUBLIC 11/54

12 3 Preparation 3.3 Installing the Java Runtime Environment Description livecache software and LCA objects Additional trace files for problem analysis Recommendation 300 MB 3 GB 3.3 Installing the Java Runtime Environment You need to prepare your system for SAPinst. This includes the installation of a Java Runtime Environment (JRE), which is required both for SAPinst and the SAPinst GUI. If required, you can perform a remote installation using a standalone SAPinst GUI on a separate Windows or UNIX host. This lets you perform the installation on a remote host, controlling it with the SAPinst GUI from a local host. If you want to perform a remote installation, see Performing a Remote Installation with SAPinst [page 20]. In this case, you need at least a JRE on the local host to start the SAPinst GUI there. Procedure 1. Check the JRE versions that are released for SAP systems in the Product Availability Matrix (PAM): a) Go to b) On the right-hand panel, choose SAP NetWeaver SAP NetWeaver 7.0. c) Choose tabstrip JSE Platforms. For more information about the recommended JDK version and about how to obtain it, see SAP Make sure a valid JRE version is installed, as follows: If JRE is not already installed Since JRE is not part of the SAP shipment, you need to download and install it. JRE is part of JDK (Java Development Kit). If JRE is already installed Check the installed version of JRE by entering: java -version SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environment. If SAPINST_JRE_HOME is not found, SAPinst also checks JAVA_HOME. 12/54 PUBLIC 03/28/2008

13 3 Preparation 3.4 Preparing the Installation Media 3.4 Preparing the Installation Media This section tells you how to prepare [page 13] and download [page 13] your installation media, such as CDs or DVDs Preparing the Installation DVDs You use this procedure to prepare the installation DVDs. You can also download installation DVDs from: Downloads Installations and Upgrades Entry by Application Group <your solution> <release of your solution>. If you download the installation DVDs, keep in mind that DVDs might be split into several downloadable files. In this case you have to manually put back together the files that are required for your installation after downloading them. Recommendation We recommend that you make all required DVDs available in parallel. Procedure 1. Identify the required DVDs: Installation Master DVD livecache 7.6 DVD 2. Use one of the following methods to make DVDs available in parallel: Before the installation: Have sufficient DVD drives Copy DVDs manually to local hard disks During the installation: Use the SAPinst DVD / CD Browser dialog. You can check the entered location and then copy the entire DVD to the path you entered in column Copy Package to Downloading Installation DVDs from SAP Service Marketplace (Optional) You normally obtain the installation DVDs as part of the installation package from SAP. However, you can also download installation DVDs from: 03/28/2008 PUBLIC 13/54

14 3 Preparation 3.4 Preparing the Installation Media Downloads Installations and Upgrades Entry by Application Group <your solution> <release of your solution> <your operating system> <your database>. If you download installation DVDs, note that DVDs might be split into several files. In this case, you have to reassemble the required files after the download. Prerequisites To extract the downloaded SAR files make sure that you use the latest SAPCAR version, which you can find on SAP Service Marketplace at You need at least SAPCAR 700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longer unpack current SAR files. For more information, see SAP Procedure 1. Create a download directory on the host on which you want to run SAPinst. 2. Identify all download objects that belong to one installation DVD according to one or both of the following: Material number All download objects that are part of an installation DVD have the same material number and an individual sequence number: <material_number>_<sequence_number> Example _ _2... Title All objects that are part of an installation DVD have the same title, such as <solution><dvd_name><os> or <database>rdbms<os> for RDBMS DVDs. 3. Download the objects to the download directory. 4. Extract the individual download objects using SAPCAR, starting with the lowest sequence number for example _1, then _2, and so on. During the download SAPCAR sets up the structure of the installation DVD. SAPCAR asks if you want to replace existing files, for example LABELIDX.ASC. Always accept with Yes. 14/54 PUBLIC 03/28/2008

15 4 Installation 4 Installation You install livecache using SAPinst [page 15]. 4.1 Installing livecache Using SAPinst To install livecache, you need to run SAPinst [page 15]. You might need to refer to the following information: Using SAPinst GUI [page 18] Interrupted Installation with SAPinst [page 18] Performing a Remote Installation with SAPinst (Optional) [page 20] Starting SAPinst GUI Separately (Optional) [page 21] Running SAPinst to Install livecache This procedure tells you how to install livecache with SAPinst. SAPinst includes a SAPinst GUI and a GUI server, which both use Java. This section describes an installation where SAPinst, SAPinst GUI, and the GUI server are running on the same host. If required, you can instead perform a remote installation with SAPinst [page 20], where SAPinst GUI is running on a separate host from SAPinst and the GUI server. the following about SAPinst: When you start SAPinst, SAPinst GUI and the GUI server also start. SAPinst GUI connects via a secure SSL connection to the GUI server and the GUI server connects to SAPinst. SAPinst normally creates the installation directory sapinst_instdir where it keeps its log files, and which is located directly below the Program Files directory. If SAPinst is not able to create sapinst_instdir directly below the Program Files directory, SAPinst tries to create sapinst_instdir in the directory defined by the environment variable TEMP. Recommendation We recommend that you keep all installation directories until the system is completely and correctly installed. 03/28/2008 PUBLIC 15/54

16 4 Installation 4.1 Installing livecache Using SAPinst SAPinst creates a subdirectory for each installation service, called <sapinst_instdir>\<installation_service>, which is located below %ProgramFiles%\sapinst_instdir. The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP, TMP, TMPDIR, or SystemRoot). These executables are deleted after SAPinst has stopped running. Directories with the name sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You can safely delete them. In the temporary directory, you can also find the SAPinst Self-Extractor log file dev_selfex.out, which might be useful if an error occurs. Caution If SAPinst cannot find a temporary directory, the installation terminates with the error FCO If you want to terminate SAPinst and the SAPinst Self-Extractor, do one of the following: Right-click the icon for the SAPinst output window located in the Windows tray and choose Exit. Click the icon for the SAPinst output window located in the Windows tray and choose File Exit. Prerequisites You are logged on as user with the required rights and privileges that authorize you to install the SAPinst tool and the SAP system. Each SAP instance requires a separate installation directory. You need at least 50 MB of free space in the installation directory for an installation. In addition, you need MB free space for the SAPinst executables. Procedure 1. Insert the SAP Installation Master DVD in your DVD drive or mount it locally. 2. Start SAPinst from the SAP Installation Master DVD by double-clicking sapinst.exe from the following path: <DVD drive>:\im_windows_<platform> SAPinst GUI starts automatically by displaying the Welcome screen. However, if there is only one component to install, SAPinst directly displays the first input dialog without presenting the Welcome screen. 16/54 PUBLIC 03/28/2008

17 4 Installation 4.1 Installing livecache Using SAPinst During the installation, the default ports and are used for communication between SAPinst, GUI server, and SAPinst GUI. SAPinst uses port to communicate with the GUI server. The GUI server uses port to communicate with SAPinst GUI. You get an error message if one of these ports is already in use by another service. In this case, open a command prompt and change to the required directory as follows: <DVD drive>:\im_windows_<platform>. Enter the following command in a single line: sapinst.exe SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server> GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui> For a list of all available SAPinst properties, enter the following command: sapinst p. 3. In the Welcome screen, install the livecache server or client: livecache server Choose SAP NetWeaver 7.0 Support Release 3 Standalone Engines livecache livecache Server Installation. SAPinst creates a subdirectory for the chosen installation service below the current working directory. livecache client If you intend to use livecache with a server other than SCM, you need to install the livecache client software for the host where the SAP central or dialog instance runs. Otherwise, this is not necessary. Choose SAP NetWeaver 7.0 Support Release 3 Standalone Engines livecache livecache Client Installation. 4. If SAPinst prompts you to log off from your system, log off and log on again. SAPinst restarts automatically. 5. Follow the instructions in the SAPinst dialogs and enter the required parameters. For more information about the input parameters, position the cursor in the field of the respective parameter and press F1. After you have entered all required input information, SAPinst starts the installation and displays the progress of the installation. If the installation was successful, the screen Finished installation successfully is displayed. 6. We recommend you to delete all files in the directory %userprofile%\.sdtgui\. More Information Troubleshooting with SAPinst [page 33]. 03/28/2008 PUBLIC 17/54

18 4 Installation 4.1 Installing livecache Using SAPinst Using SAPinst GUI The following table shows the most important functions that are available in SAPinst GUI: SAPinst GUI Functions Button / Function Key / Menu Entries F1 Exit Log off Description Displays detailed information about each input parameter. Cancels the installation with the following options: Stop Stops the installation without further changing the installation files. You can restart SAPinst to continue the installation later from this point. Continue Continues the installation. Stops the SAPinst GUI, but SAPinst and the GUI server continue running. If for some reason you need to log off during the installation from the host where you control the installation with SAPinst GUI, the installation continues while you are logged off. You can later reconnect to the same SAPinst installation from the same or another host. For more information, see Starting SAPinst GUI Separately [page 21]. Retry Stop Continue Performs the installation step again (if an error has occurred). Stops the installation without further changing the installation files. You can continue the installation later from this point. Continues with the option you have chosen before Interrupted Installation with SAPinst The SAP system installation might be interrupted for one of the following reasons: An error occurred during the dialog or processing phase: SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appears. The dialog box contains a short description about the choices listed in the table below as well as a path to a log file that contains detailed information about the error. You interrupted the installation by choosing Exit in the SAPinst menu. 18/54 PUBLIC 03/28/2008

19 4 Installation 4.1 Installing livecache Using SAPinst The following table describes the options in the dialog box: Option Retry Stop Continue Definition SAPinst retries the installation from the point of failure without repeating any of the previous steps. This is possible because SAPinst records the installation progress in the keydb.xml file. We recommend that you view the entries in the log files, try to solve the problem and then choose Retry. If the same or a different error occurs again, SAPinst displays the same dialog box again. SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and the GUI server. SAPinst records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps. See the procedure below. SAPinst continues the installation from the current point. Procedure This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to continue an interrupted installation after an error situation. 1. Log on to your remote host as a user who is a member of the local administrators group. 2. Insert the Installation Master DVD in your DVD drive. 3. Enter the following commands at the Windows command prompt: cd <DVD drive>:\im_windows<platform> sapinst.exe 4. From the tree structure in the Welcome screen, select the installation service that you want to continue and choose Next. If there is only one component to install, the Welcome screen does not appear. The What do you want to do? screen appears. 5. In the What do you want to do? screen, decide between the following alternatives and confirm with OK. 03/28/2008 PUBLIC 19/54

20 4 Installation 4.1 Installing livecache Using SAPinst Alternative Run a new Installation Continue old installation Behavior SAPinst does not continue the interrupted installation. Instead, it moves the content of the old installation directory and all installation-specific files to the backup directory. Afterwards, you can no longer continue the old installation. For the backup directory, the following naming convention is used: <log_day_month_year_hours_minutes_seconds> (for example, log_01_oct_2003_13_47_56). SAPinst continues the interrupted installation from the point of failure Performing a Remote Installation with SAPinst (Optional) You use this procedure to install your SAP system on a remote host. In this case, SAPinst and the GUI server run on the remote host, and SAPinst GUI runs on the local host. The local host is the host from which you control the installation with SAPinst GUI. Prerequisites The remote host meets the prerequisites before starting SAPinst as described in Running SAPinst to Install livecache [page 15]. Both computers are in the same network and can ping each other. To test this: Log on to your remote host and enter the command ping <local host>. Log on to the local host and enter the command ping <remote host>. Procedure 1. Log on to your remote host as a user who is a member of the local administrators group. 2. Insert the Installation Master DVD in the DVD drive on your remote host. 3. Enter the following commands: cd <DVD drive>:\im_windows_<platform> sapinst.exe -nogui For more information, see Running SAPinst to Install livecache [page 15]. SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the command prompt: guiengine: no GUI connected; waiting for a connection on host <host_name>, port <port_number> to continue with the installation 4. Start SAPinst GUI on your local host, as described in Starting SAPinst GUI Separately [page 21]. 20/54 PUBLIC 03/28/2008

21 4 Installation 4.1 Installing livecache Using SAPinst Starting SAPinst GUI Separately (Optional) You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUI separately in the following cases: You have logged off from SAPinst. If you logged off during the installation and you later want to reconnect to the installation while it is still running, you can start SAPinst GUI separately. You want to perform a remote installation [page 20]. If SAPinst GUI runs on a different host from SAPinst and the GUI server, you have to start SAPinst GUI separately. Prerequisites You have installed the Java Runtime Environment [page 12] on the host on which you want to start SAPinst without SAPinst GUI. Starting SAPinst GUI on a Windows Platform 1. Log on as a member of the local administrators group. 2. Insert the SAP Installation Master DVD into your DVD drive. 3. To change to the relevant directory enter the following command: cd <DVD drive>:\im_windows<platform> 4. Start SAPinst GUI in one of the following ways: If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following command: startinstgui.bat SAPinst GUI uses the local host as default. If SAPinst and the GUI server runs on a different host from SAPinst GUI (remote installation), enter the following command: startinstgui.bat -host <host_name> <host_name> is the host name of the installation host. If you enter the command without additional parameters, SAPinst GUI uses the local host as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. Since SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and the SAP Installation GUI Connection dialog appears. In this case, enter the name of the host on which SAPinst is running and choose Log on. The first dialog of the installation appears and you can perform the remote installation from your local host. For a list of options to start SAPinst GUI, change to the same directory as your SAPinst executable and enter the command startinstgui.bat -h. 03/28/2008 PUBLIC 21/54

22 4 Installation 4.1 Installing livecache Using SAPinst Starting SAPinst GUI on a UNIX Platform 1. Log on as user root. Caution Make sure that the root user has not set any environment variables for a different SAP system or database. 2. Mount your installation DVD. Mount the DVD locally. We do not recommend that you use Network File System (NFS). 3. To change to the mount directory enter the following command: cd <Installation_Master_DVD>/IM_<OS> 4. Start the SAPinst GUI in one of the following ways: If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following command without additional parameters:./startinstgui.sh SAPinst GUI uses as default the local host. If SAPinst and the GUI server run on a different host from SAPinst GUI (remote installation), enter the following command with additional parameters:./startinstgui.sh -host <host_name> <host_name> is the host name of the installation host. If you enter the command without additional parameters, SAPinst GUI uses the local host as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. Since SAPinst and GUI server are running on another host, SAPinst GUI cannot connect and the SAP Installation GUI Connection dialog appears. In this case, enter the name of host on which SAPinst is running and choose Log on. The first dialog of the installation appears and you can perform the remote installation from your local host. For a list of options to start SAPinst GUI, change to the same directory as your SAPinst executable and enter the command./startinstgui.sh -h. 22/54 PUBLIC 03/28/2008

23 5 Post-Installation 5 Post-Installation You perform the following post-installation steps: Caution If you are performing a new installation of livecache during an SCM 5.0 upgrade, to change from an unsupported operating system for livecache such as Windows 32-bit to a supported operating system, do not perform the steps listed below. The exception to this is the step Installing the Administration Tools [page 27], which you can still perform if required. The required livecache post-installation activities setup of the logical database connection with transaction LC10 and the loading of the master and transaction data occur in phase REQ_LCUPG of the SCM upgrade. For more information, see SAP Supply Chain Management 5.0 ABAP: <Your Operating System and Database, which you can find as follows: SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP SCM 5.0 Server Upgrade Documentation - SAP SCM You perform common post-installation activities [page 23]. 2. You perform post-installation activities specific to workforce deployment server [page 27]. 3. You install administration tools [page 27]. 4. If required, you install Secure Sockets Layer (SSL) protocol for database server communication [page 28]. 5.1 Common Post-Installation Activities You always need to perform the common post-installation activities listed below, regardless of the server with which you intend to use livecache Setting Up the Connection to the livecache Instance Before checking the connection, you must initialize the livecache instance using transaction LC10. Procedure 1. Start the SAP instances: Windows application server 03/28/2008 PUBLIC 23/54

24 5 Post-Installation 5.1 Common Post-Installation Activities a) Start service SAP<SID>_<instno>. b) Start the SAP central instance using Microsoft Management Console (if not already running). UNIX application server Restart all SAP central and dialog instances running on UNIX. 2. Log on to the SAP System as user DDIC (production client). 3. Execute the program SLCA_NON_LC_RELEVANT_CLIENT to maintain your relevant clients for livecache. 4. Apply SAP RFC destination for global working on the livecache for all livecache-relevant clients. 5. Switch livecache to state offline for the steps below by running the following command on the livecache server: dbmcli d <SID> -u <controluser>,<password> db_offline 6. Call transaction LC10. The livecache: Initial Screen appears. 7. In the Name of database connection field, enter LCA and choose Integration. 8. If not already entered, enter values for the following fields: The Name of database connection field is used for a NATIVE SQL connection to livecache. The livecache name field is the name of the livecache database. It can be different from the name of the database connection. The server name in the livecache server name is case-sensitive. It must be the same as the output from the command hostname in Windows or UNIX. During the installation, SAPinst prompted you to specify the DBM operator and the standard livecache user. The DBM operator is control. The standard livecache user is SAP<SID> by default but you can change this during the livecache installation if required. The standard livecache user is created by the lcinit script, which is automatically executed when the livecache is initialized. This makes sure that the SAP system connects to the correct livecache instance. 9. Choose the Administration Report tab. 10. If you have installed the Add-on LCAPPS_2005_700, enter /SAPAPO/DELETE_LC_ANCHORS in field Follow-up Procedures of section Initialize livecache and choose Enter, otherwise enter SLCA_INIT_FOLLOW_UP. 11. Enter the report SLCA_LCK_SYNCHOWNERS as a follow-up report of the livecache start on the Administration Report tab. 12. Save your entries. 13. Repeat steps 6 to 8 and 12 for the database connections LDA and LEA. As of livecache 7.6, you need the database connection LEA in addition to LCA and LDA. 24/54 PUBLIC 03/28/2008

25 5 Post-Installation 5.1 Common Post-Installation Activities 14. To initialize the livecache instance LCA: a) Choose Back (F3). The livecache: Initial Screen reappears. b) Enter LCA in the Name of database connection field. c) Choose livecache: Monitoring. Apply SAP if one of the following messages appears: Relative node for insert not found LastError node key... Cannot use node of type leaf as parent LastError node key The screen Properties appears with a tree structure <LC_NAME>(<host name-lc_name>) in the left frame. d) In the tree structure select <LC_NAME>(<host name-lc_name>) Administration and double-click Operating. The livecache Administration menu appears. e) From the menu, choose Administration Initialize livecache. Several dialog boxes appear. f) Confirm with Yes. After initializing livecache, initial application data is loaded as configured under Integration. 15. Create a backup. Caution For LDA and LEA you must not use an administration report. In addition, do not use alert monitoring for LDA and LEA Checking the livecache Instance Call transaction LCA03 in a livecache-relevant client. For more information, see Setting Up the Connection to the livecache Instance [page 23], step 3. This transaction performs a livecache check, consisting of a configuration check and a functional check. This also checks whether all required periodic jobs are scheduled. If there are open issues during the configuration check, the transaction guides you to fix them immediately. If you get errors during the functional check, open an OSS message for the component BC-DB-LCA. 03/28/2008 PUBLIC 25/54

26 5 Post-Installation 5.1 Common Post-Installation Activities Changing Password of Created Users You need to change the passwords of the users that SAPinst creates during the installation. The table below lists these users. You also need to remove the contents of the installation directory and store them securely because otherwise they might represent a security risk. Caution Make sure that you perform this procedure before the newly installed SAP system goes into production. Procedure 1. Change the passwords of these users. For more information, see: For more information about how to change the passwords for the following livecache users, see SAP SAPinst sets the initial passwords for the user CONTROL to CONTROL and for the user SUPERDBA to ADMIN. User Type User Comment livecache users SAP<SAPSID> CONTROL SUPERDBA livecache database owner (that is, the owner of the database tables) livecache database manager operator livecache administration user 2. Remove the contents of the installation directory and store them securely Setting Up a livecache Super User Process You need to create a livecache and livecache applications super user for livecache administration. Assign the roles SAP_APO_LC_ALL or SAP_LCA_ALL and SAP_BC_LVC_SUPERUSER to the user, as these roles already contain all required privileges. If you want to create users with limited privileges for transaction LC10 see SAP for more information about the authorization concept for transaction LC10. 26/54 PUBLIC 03/28/2008

27 5 Post-Installation 5.2 Post-Installation Activities Specific to Workforce Deployment Server 5.2 Post-Installation Activities Specific to Workforce Deployment Server If you are using SAP livecache with an SAP WFD Server (Software component WFMCORE 200) see SAP for more information. 5.3 Installing the Administration Tools This section describes how to install the following administration tools for SAP MaxDB and SAP livecache on Windows systems: Database Manager GUI and Web DBM You can use Database Manager GUI and Web DBM to administer databases, including remote ones. SQL Studio and Web SQL Studio You can use SQL Studio and Web SQL Studio to send SQL statements to the database and evaluate the results. The use of these tools for the SAP livecache is optional. If you do not want to use them, skip this section. For more information about these tools, see the following documentation: Database Manager GUI and Web DBM SQL Studio and Web SQL Studio You can find these at: Documentation MaxDB Online Library Tools Prerequisites You can install these administration tools on any Windows PC in your network, even if your database runs on UNIX. From the PC with the installed administration tool, you can then administer the database or send queries to it. Your PC must meet the following minimum operating system requirements: Operating System Version Windows NT 4.0 SP 4 Windows 2000 Windows Server 2003 Windows XP Any Any Any 03/28/2008 PUBLIC 27/54

28 5 Post-Installation 5.4 Secure Sockets Layer Protocol for Database Server Communication Your PC must meet the following minimum hardware requirements Pentium II 64 MB RAM 100 MB disk space You can get the required files from one of the following: The SAP livecache DVD By downloading from: Entry by Application Group Additional Components MaxDB MaxDB GUI COMPONENTS/TOOLS Caution If SAP MaxDB or SAP livecache is installed on the PC, you must not install the administration tools in the same directory. You can check the directories used by SAP MaxDB or SAP livecache as follows: dbmcli d <SID> -u <controluser>,<password> dbm_getpath IndepDataPath dbmcli d <SID> -u <controluser>,<password> dbm_getpath IndepProgPath Process 1. Start the installation as follows: If you are using the livecache DVD: DBMGUI <DVD>:\LC_WINDOWS_<Processor>\SETUPS\DBM76.EXE SQL Studio <DVD>:\LC_WINDOWS_<Processor>\SETUPS\SQLSTD76.EXE If you are using the files from SAP Service Marketplace, simply execute the downloaded.exe file. An installation shield guides you through the installation. If you already have an older version of the administration tools installed on the PC, the installation shield offers to upgrade it for you. 2. If you are prompted to restart the PC after the installation, bring down any databases that are running as follows: dbmcli d <SID> -u <controluser>,<password> db_offline 5.4 Secure Sockets Layer Protocol for Database Server Communication The SAP MaxDB database server supports the Secure Sockets Layer (SSL) protocol. You can use this protocol to communicate between the database server and its client, here the Application Server 28/54 PUBLIC 03/28/2008

29 5 Post-Installation 5.4 Secure Sockets Layer Protocol for Database Server Communication (AS). SSL guarantees encrypted data transfer between the SAP MaxDB database server and its client applications. In addition, the server authenticates itself to the client. Caution There is a performance cost for SSL since the data has to be encrypted, which requires time and processing power. To use SSL you need to: 1. Install the SAP cryptographic library [page 29] on the client host and on the server host machines 2. Generate the Personal Security Environment [page 30] (PSE) on the server (SSL Server PSE) and on the client (SSL Client PSE) Installing the SAP Cryptographic Library The cryptographic functions required to build a database server-client connection using Secure Sockets Layer (SSL) protocol are supplied by the SAP Cryptographic Library. Therefore, you need to install the SAP Cryptographic Library on the host machine of the SAP MaxDB database server and the SAP Application Server (AS). The installation package sapcrypto.car consists of the following: SAP Cryptographic Library: sapcrypto.dll License ticket: ticket Configuration tool: sapgenpse.exe You use the configuration tool to generate key pairs and PSEs. Caution The SAP Cryptographic Library is subject to German export regulations and might not be available to some customers. In addition, the library might be subject to the local regulations of your country. These regulations might further restrict import, use, and export or re-export of cryptographic software. For more information, contact your local SAP representative. Prerequisites Download the appropriate SAP Cryptographic Library installation package for your operating system from Procedure 1. Unpack the installation package for the SAP Cryptographic Library using sapcar.exe, which you can find for example on your Installation Master DVD, using the following command: 03/28/2008 PUBLIC 29/54

30 5 Post-Installation 5.4 Secure Sockets Layer Protocol for Database Server Communication car -xvf SAPCRYPTO.CAR The remainder of the procedure as described below does not apply to client applications such as SQL Studio, which do not recognize an independent directory. In this case, you must copy the SAPCRYPTO installation package to the installation directory of the application. In this directory you need to create a directory sec, into which you copy the ticket file. 2. Copy the sapcrypto library to the lib subdirectory of the independent program directory. You can find the value of the independent program directory by entering the following command: dbmcli dbm_getpath IndepProgPath Example The independent program directory might be called the following: <drive>:\sapdb\programs\lib 3. Copy the configuration tool sapgenpse.exe to the directory <independent program>\lib. 4. Create a subdirectory called sec under the independent data directory and copy the ticket file into it. Example The result might look like the following: <drive>:\sapdb\datal\sec\ticket 5. Make sure that only the local system account is allowed to possess access rights to the sec directory and the files it contains including the ticket file and the SSL Server PSE and that access is restricted to read&write. Only members of the administrator group can own the files. Result The SAP Cryptographic Library is copied to the application server and the environment is correctly configured so that the server can find the library at runtime Generating the Personal Security Environment The information required by the database server or client application to communicate using Secure Sockets Layer are stored in the Personal Security Environment (PSE). The required information differs according to whether SSL PSE is for the server or client: SSL Server PSE This PSE contains the security information from the database server, for example, the public-private cryptographic key pair and certificate chain. To install the SSL Server PSE, you 30/54 PUBLIC 03/28/2008

31 5 Post-Installation 5.4 Secure Sockets Layer Protocol for Database Server Communication need to generate the PSE. You can either do this for a single database server or system-wide. The SSL Server PSE is called SDBSSLS.exe. SSL Client PSE The client requires an anonymous certificate called SDBSSLA.exe, which contains the list of the public keys of trustworthy database servers. Procedure To generate the SSL Server PSE, proceed as follows: You need to know the naming convention for the distinguished name of the database server. The syntax of the distinguished name, which you enter in the procedure below, depends on the Certification Authority (CA) that you are using. 1. Change to the <independent programs>\lib directory. 2. Set up the following environment variable: SECUDIR=<independent data>\sec 3. Create a SSL Server PSE, SDBSSLS.pse, and generate a certificate request file, certreq, in the directory defined by SECUDIR (see previous step): sapgenpse gen_pse -v -r <SECUDIR>\certreq -p SDBSSLS.pse <your distinguished name> For each database server that uses a server-specific PSE, you must set up a unique certificate request. If you are using a valid system-wide SSL Server PSE, you only need to set up a single certificate request for all servers. 4. Send the certificate request to the CA for signing. You can either send it to the SAP CA or to another CA. You must make sure that the CA offers a certificate corresponding to the PKCS#7 certificate chain format. Thawte CA at offers a suitable certificate, either SSL Chained CA Cert or PKCS#7 certificate chain format. The CA validates the information contained in the certificate request, according to its own guidelines, and sends a reply containing the public key certificate. 5. After you have received the reply from the CA, make sure that the contents of the certificate request have not been destroyed during download. For example, if you requested the certificate on a UNIX system and stored it on a Windows front end, the formatting (that is, line indents and line breaks) is affected. To check the contents, open the certificate request with a text editor (such as pad) and repair the line indents and the line breaks. 03/28/2008 PUBLIC 31/54

32 5 Post-Installation 5.4 Secure Sockets Layer Protocol for Database Server Communication Example This is an example of a certificate request: -----BEGIN CERTIFICATE REQUEST-----MIIBPzCBqQIBADAAMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD/302IT+/Y wpignsw7u9fwneywz3wil0s18afcykro00wcpd8uwcac4dds4ugt6hl2wlj0/fotug+eqxonzbarrk9stalkn1mqx3yaue/geag -----END CERTIFICATE REQUEST Import the reply to the SSL Server PSE: a) Copy the text to a temporary file called srcert. b) Enter the following command: sapgenpse import_own_cert -c srcert -p SDBSSLS.pse You have generated the SSL Server PSE. You can now start the XServer as usual (if it is already running, you must stop and restart it). 7. To check whether the SSL functionality is working correctly, view the trace file niserver_<local computer name>.trace in the <independent data>\wrk directory. To generate the SSL Client PSE, proceed as follows: 1. Change to the <independent programs>\lib directory. 2. Set up the following environment variable: SECUDIR=<independent data>\sec 3. Create an anonymous client SSL Client PSE, SDBSSLA.pse in the directory defined by SECUDIR (see previous step): sapgenpse gen_pse -v -noreq -p SDBSSLA.pse You can leave the distinguished name empty. Before you can establish an SSL connection to a database server, the server certificate must be entered in the PK list of the anonymous client certificate. 4. To see the database server certificate, enter the following command: x_ping -n <servermode> -c[apture] You can check whether to trust the database server certificate. The client certificate is not affected by this. 5. Start the import with this command: x_ping -n <servermode> -i[import] 6. To administer the PSE, use the configuration tool sapgenpse. For more information, enter the following command: sapgenpse -h For applications such as SQL Studio replace the independent data or independent program in the above description with the installation directory. 32/54 PUBLIC 03/28/2008

33 6 Additional Information 6 Additional Information 6.1 Operating Information for livecache If you manually reinitialize livecache with transaction LC10, make sure that you first delete all administration reports, especially /SAPAPO/DELETE_LC_ANCHORS and SLCA_INIT_FOLLOW_UP, from the definition of the logical livecache LCA connection. 6.2 Uninstalling livecache Prerequisites Stop livecache with transaction LC10 in the SAP system. Procedure 1. Drop the database instance: dbmcli -d <LC_NAME> -u <dbm_user>,<password> db_drop 2. Delete integration entries on the SAP server: a) Log on to the SAP System as user DDIC. b) Call transaction LC10. The livecache: Initial Screen appears. c) In the Name of database connection field, enter LCA and choose Integration. d) Choose Display Change e) Choose Delete the logical link and confirm the deletion. f) Save your entries. g) Repeat steps b to f for database connections LDA and LEA. 3. Delete the livecache software (dependent package) using the SAP MaxDB SDBUNINST tool, as described in SAP You have now removed the livecache instance. 6.3 Troubleshooting with SAPinst This section tells you how to proceed when errors occur during the installation with SAPinst. If an error occurs, SAPinst: 03/28/2008 PUBLIC 33/54

34 6 Additional Information 6.3 Troubleshooting with SAPinst Stops the installation Displays a dialog informing you about the error Procedure 1. To view the log file, choose View Logs. 2. If an error occurs during the dialog or processing phase, do either of the following: Try to solve the problem Abort the installation with Exit For more information, see Interrupted Installation with SAPinst [page 18]. Continue the installation by choosing Retry. 3. Check the log and trace files of the GUI server and SAPinst GUI in the directory %userprofile%\.sdtgui\ for errors. 4. If SAPinst GUI does not start, check the file sdtstart.err in the current %userprofile% directory. 5. If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as described in Starting SAPinst GUI Separately. 34/54 PUBLIC 03/28/2008

35 7 High Availability with Microsoft Cluster Service Only valid for: HA (MSCS) 7 High Availability with Microsoft Cluster Service You can install a high-availability SAP system with Microsoft Cluster Service (MSCS). For this type of installation, you have to set up the system and configure it so that it can take advantage of the MSCS software. The MSCS software improves the availability of the system and safeguards it against failure and unplanned downtime, enabling 24-hour operation, 365 days a year. In the sections on MSCS we use SAP system to mean livecache. With high availability you enable critical system components, known as Single Points of Failure (SPOFs), to be automatically switched from one machine to the other, if hardware or software problems arise on one machine. With the help of this switchover or failover the system can continue functioning normally so that unplanned system downtime is avoided. Apart from enabling failover when hardware problems occur, you can also use MSCS to avoid downtime when you perform essential system maintenance. If you need to maintain one host (MSCS node), you can deliberately switch the cluster resources to the other host (MSCS node) and temporarily operate it there while maintenance is in progress. When maintenance work is finished you can easily move the resources back to their original node and continue operating them there. In this documentation the hosts in an MSCS cluster are referred to as first MSCS node and additional MSCS node(s). When you are setting up the SAP system with MSCS, you combine standard installation steps, described earlier in this documentation, with cluster-specific steps, described here. To install a new SAP system with MSCS, you have to perform a number of extra steps specially required for the cluster and configure the SAP system so that it can take advantage of the cluster functionality: Since the cluster hardware has at least two nodes that have access to all local and shared storage devices, you have to install some components on all nodes and observe special rules for distributing components to local or shared disks. 03/28/2008 PUBLIC 35/54

36 7 High Availability with Microsoft Cluster Service 7.1 Planning Since the correct configuration of network addresses is absolutely essential to enable the cluster to function properly, you have to perform a number of additional steps that are necessary to set up and check addressing. 7.1 Planning You have to complete the following planning activities for you SAP system using Microsoft Cluster Service (MSCS): 1. You decide how to distribute components to disks for MSCS [page 36]. 2. You read Directories in an MSCS Configuration [page 38] 3. You read IP Addresses in an MSCS Configuration [page 39] 4. You obtain IP addresses for MSCS [page 42] Distribution of Components to Disks for MSCS One of the central points to keep in mind when planning the MSCS installation is that the cluster hardware has two different sets of disks: Local disks that are connected directly to the MSCS node(s) Shared disks that can be accessed by all MSCS nodes via a shared interconnect Shared disk is a synonym for the MSCS resource of Resource type Physical disk. You need to install the SAP system components in both the following ways: Separately on all MSCS nodes to use the local storage on each node. On the shared storage that is used in common by all MSCS nodes. With Windows Server 2003, you can now choose between the following cluster models: Single Quorum Device Cluster In this cluster model, the quorum resource maintains the cluster configuration data on a single cluster storage device. The quorum resource is unique to a cluster installation and is always owned by one of the nodes. It has the following main functions in the cluster: It logs changes to the cluster configuration that are entered in the Registry. It arbitrates between competing nodes when the communication between nodes breaks down. This means that cluster resources are forced to fail over to the node that owns the quorum resource. Majority Node Set Cluster 36/54 PUBLIC 03/28/2008

37 7 High Availability with Microsoft Cluster Service 7.1 Planning In this new cluster model, each node maintains its own copy of the cluster configuration data. The Majority Node Set resource, acting as the Quorum Resource, ensures that the cluster configuration data is kept consistent across the different nodes. You can use majority node set for geographically dispersed cluster configuration. SAP supports Majority Node Set Cluster if it is part of a cluster solution offered by your Original Equipment Manufacturer (OEM), or Independent Hardware Vendor (IHV). The following figures show a livecache cluster configuration. They illustrate how to distribute the livecache data files, and the quorum resource (if used) to different disks. Only with this distribution of files to distinct disks is it possible to move livecache as a separate entity in a failover situation. Figure 1: The following software on the local disks must have the same drive letter and path on both nodes: Instance-independent program software Instance-dependent software Distribution of Database Files in a RAID Configuration Caution Microsoft does not support a Windows operating system-based RAID configuration (Dynamic Disks). 03/28/2008 PUBLIC 37/54

38 7 High Availability with Microsoft Cluster Service 7.1 Planning The following figure shows a secure method to distribute the livecache directories to different RAID volumes. Figure 2: More Information Directories in an MSCS Configuration [page 38] Directories in an MSCS Configuration The following tables show the directories where the main software components for the SAP cluster installation are stored: Directories on Local Disks on MSCS Nodes Component A supported operating system [page 45] MSCS software SAP cluster files livecache instance-independent programs livecache instance-dependent software Default Directory %windir% %windir%\cluster %windir%\sapcluster <drive>:\sapdb\program <drive>:\sapdb\<dbsid>\db 38/54 PUBLIC 03/28/2008

39 7 High Availability with Microsoft Cluster Service 7.1 Planning Directories on Shared Disks Component Cluster quorum resource livecache data volumes livecache database log volumes livecache mirrored database log volumes livecache instance-independent data Default Directory <drive>:\mscs <drive>:\sapdb\<sapsid>\sapdata\... <drive>:\sapdb\<sapsid>\saplog\... <drive>:\sapdb\<sapsid>\saplog\... <drive>:\sapdb\data IP Addresses in an MSCS Configuration A part of the installation process that is unique to MSCS is the configuration of host names and IP addresses in the network. This is a particularly important task because the addressing plays a key role in the switchover procedure. Addressing must be set up correctly so that the system can take advantage of the cluster functionality and switch between nodes when hardware problems arise. This section explains the different types of IP addresses and their function in the switchover mechanism of an MSCS cluster with two nodes. Types of IP Addresses In a correctly configured cluster with two nodes, there are six IP addresses and corresponding host names for your SAP system. You have two IP addresses for each MSCS node, one IP address for the cluster and one for the livecache cluster group. Some of the addresses are assigned to the network adapters (cards), others are virtual IP addresses that are assigned to the cluster groups. Physical IP Addresses Assigned to Network Adapters An MSCS configuration usually has two networks: A public network that is used for the communication between the central instance, application servers and the LAN. A private network that is used internally for communication between the nodes of the cluster. For more information about network configuration, see also the Microsoft Knowledge Base Article The following figure shows an MSCS cluster with two nodes and illustrates the adapters required for the public and private networks, and their corresponding physical IP addresses. A physical IP address, as opposed to a virtual one, is stationary and permanently mapped to the same adapter. 03/28/2008 PUBLIC 39/54

40 7 High Availability with Microsoft Cluster Service 7.1 Planning Figure 3: Adapters and IP Addresses Required for Public and Private Networks in an MSCS Cluster with Two Nodes Host Names Assigned to Network Adapters Each of the physical IP addresses of the network adapters must have a corresponding host name. For example, on the left-hand node in the figure above, you might assign the IP addresses of the public and private network adapters as follows: IP Addresses and Host Names Network Adapter IP Address Host Name Adapter 1 (private network) clusa_priv Adapter 3 ( public network) clusa Caution Make sure that you are aware of the following: The IP address and host name of the public network adapter is also the IP address and name of the machine. In our example, this means that the machine that is the MSCS node on the left in the figure has the name clus1. Do not confuse the host name with the computer name. Each node also has a computer name, which is often the same as the host name. The computer name is displayed in the node column of the Cluster Administrator. However, it is not required for the TCP/IP communication in the cluster. When you configure IP addresses 40/54 PUBLIC 03/28/2008

41 7 High Availability with Microsoft Cluster Service 7.1 Planning and corresponding names, keep in mind that it is the host names that are important for the cluster, not the computer names. Virtual IP Addresses Assigned to Cluster Groups When you have installed livecache and fully configured the cluster, the critical system resources are bound together in two different groups. Each of these groups requires a virtual IP address and host name that is permanently mapped to the group and not to a particular node. This has the advantage that, whenever a group is moved between nodes, its IP address and host name move together with it. A cluster configuration has the following groups: livecache cluster group Cluster group Each group consists of a set of related resources that work together to offer a service to the system. For example, the livecache cluster group comprises all the resources that enable the livecache server to fulfill the requests of a client. When the group is moved from one node to the other, due to node failure, the virtual IP address and host name move with it. Therefore, there is a failover not only of resources, but also of the virtual IP address and host name. As a result, all clients can still reach the livecache server with the same IP address as before. The following figure illustrates how the virtual IP addresses of the livecache group can move from one node to the other when failover occurs. Figure 4: 03/28/2008 PUBLIC 41/54