TADM12_1_EN_Col72.pdf

Full text

(1)TADM12_1 SAP NetWeaver AS – Implementation & Operation II SAP NetWeaver. Date Training Center Instructors Education Website. Participant Handbook Course Version: 72 Course Duration: 10 Days Material Number: 50099805. An SAP course - use it to learn, reference it for work.

(2) Copyright Copyright © 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.. Trademarks •. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.. •. IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.. •. ORACLE® is a registered trademark of ORACLE Corporation.. •. INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.. •. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.. •. Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.. •. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.. •. JAVA® is a registered trademark of Sun Microsystems, Inc.. •. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.. •. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.. Disclaimer THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.. g201202334129.

(3) About This Handbook This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.. Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used. Type Style. Description. Example text. Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal and external.. 2012. Example text. Emphasized words or phrases in body text, titles of graphics, and tables. EXAMPLE TEXT. Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE.. Example text. Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.. Example text. Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation.. <Example text>. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.. © 2011 SAP AG. All rights reserved.. iii.

(4) About This Handbook. TADM12_1. Icons in Body Text The following icons are used in this handbook. Icon. Meaning For more information, tips, or background. Note or further explanation of previous point Exception or caution Procedures. Indicates that the item is displayed in the instructor's presentation.. iv. © 2011 SAP AG. All rights reserved.. 2012.

(5) Contents Course Overview ............................................................................. vii Course Goals.................................................................................vii Course Objectives ...........................................................................vii. Unit 1: Overview and Architecture of SAP Systems ...................................1 Overview of SAP Systems................................................................... 2 Technical Architecture of SAP Systems ................................................... 9. Unit 2: Preparing an Installation .......................................................... 25 Introducing SAPinst ........................................................................ 26 General Preparation for Installation ...................................................... 34 Additional Preparation for Installation on Windows .................................... 54 Additional Preparation for Installation on UNIX ......................................... 64. Unit 3: Installing SAP Solution Manager ................................................ 75 Installation of SAP Solution Manager .................................................... 76 Installation of a Secondary Application Server ......................................... 90. Unit 4: Planning an Installation ..........................................................103 Planning the Installation .................................................................. 104. Unit 5: Installation of SAP ECC (AS ABAP) ...........................................129 Installation of SAP ECC................................................................... 130. Unit 6: Installation of SAP XSS (AS Java) .............................................145 Installation of SAP XSS ................................................................... 146 Installation of Additional Usage Types .................................................. 160. Unit 7: Performing Post-Installation Activities .......................................171 Overview of Post-Installation Steps ..................................................... 173 Completing the Installation of SAP Enhancement Packages 5 for SAP ERP 6.0. 180 Patching SAP Systems ................................................................... 186 SAP License, Online Documentation, Remote Connection to SAP Support ...... 204 Initial Configuration for an AS ABAP based SAP System ............................ 218 Initial Configuration of an AS Java based SAP System .............................. 245. 2012. © 2011 SAP AG. All rights reserved.. v.

(6) Contents. TADM12_1. Appendix: Installation of Standalone SAP Gateway .................................. 254. Unit 8: Installation of SAP GUI ...........................................................269 Installation of SAP GUI for Windows and SAP GUI for Java ........................ 270 Installation and Usage of SAP GUI Installation Server ............................... 286. Unit 9: “SAP Patch Day” ...................................................................307 Patching SAP Systems ................................................................... 309 SAP Notes and Support Packages...................................................... 326 Preparation for Software Maintenance.................................................. 335 Support Package Manager (SPAM) ..................................................... 353 Importing Support Packages ............................................................. 362 Importing Corrections ..................................................................... 377 Other Tools in Software Lifecycle Management ....................................... 402 Enhancement Packages .................................................................. 410. Unit 10: Output Management .............................................................423 Configuring Printers in AS ABAP ........................................................ 424 Concept of Logical Spool Servers ....................................................... 450 Managing Spool Requests ............................................................... 461 Printing Assistant for Landscapes (PAL) ............................................... 470. Unit 11: Scheduling Background Tasks ................................................495 Fundamentals of Background Processing.............................................. 497 Time-Based Scheduling of Jobs ......................................................... 510 Event-Based Scheduling of Jobs ........................................................ 522 Background Processing: Further Topics................................................ 531 Job Scheduling with SAP Central Process Scheduling by Redwood ............... 547 Appendix: Job Management ............................................................. 563. Unit 12: SAPconnect and SMTP .........................................................575 Communication with SAPconnect ....................................................... 576 Communication Using SMTP ............................................................ 586. Glossary .......................................................................................621 Index ............................................................................................625. vi. © 2011 SAP AG. All rights reserved.. 2012.

(7) Course Overview TADM12 complements the knowledge and skills gained in TADM10. Courses TADM10 and TADM12 are largely independent of the type of operating system and database technology. Like the other TADM courses, TADM12 comprises several individual courses (or parts thereof), which are arranged here in a way that will enable you to gain the knowledge you require as an SAP Technology Consultant as efficiently as possible. Week 1 of course TADM12 is based on content taken from the following courses: 1. 2. 3. 4.. ADM110 ADM200 ADM100 ADM102. Week 2 of course TADM12 is based on content taken from the following courses: 1. 2.. ADM325 ADM102. Target Audience This course is intended for the following audiences: •. SAP Technology Consultants (Associate Level). Course Prerequisites Required Knowledge •. Knowledge of the content of TADM10. Course Goals This course will prepare you to: • • •. 2012. Work as an Associate Consultant (Junior Consultant) within the SAP technology environment Install, configure and maintain SAP systems based on SAP NetWeaver AS ABAP Install, configure and maintain SAP systems based on SAP NetWeaver AS Java. © 2011 SAP AG. All rights reserved.. vii.

(8) Course Overview. TADM12_1. Course Objectives After completing this course, you will be able to: •. viii. process basic tasks within the technology environment of SAP systems. © 2011 SAP AG. All rights reserved.. 2012.

(9) Guide for applying SP-Stack 28 to a freshly installed SAP Solution Manager 7.0 Enhancement Package 1 system (SP-Stack 18), based on MaxDB and Windows 2003, x64 (for use in TADM12_1, collection 72). Material Number: 50110983 Version 1.4, January 19th 2012© SAP AG 2012. © SAP AG 2012. TADM12_1. 1.

(10) 1.. Disclaimer: Don’t use this guide 1:1 on systems at home. It only describes “How to proceed…” in the context of TADM12_1, collection 72. This guide is not covering all possible situations you may encounter.. 2.. Usually, but not in the context of TADM12_1, you would prepare the patch activities by reading the corresponding SP-Stack Guide to be found at https://service.sap.com/maintenancenw70. 3.. Also, for updating SAP Solution Manager, you would read – at least – the following SAP Notes: https://service.sap.com/sap/support/notes/394616 https://service.sap.com/sap/support/notes/569116 https://service.sap.com/sap/support/notes/1161294 https://service.sap.com/sap/support/notes/1244225 https://service.sap.com/sap/support/notes/1595736. 4.. When patching AS Java-based systems, it is necessary to check: a.. b. 5.. if a new JRE/SDK is required, see /PAM and i.. SAP Note 1442124 for SAP JVM. ii.. SAP Note 716604 for SUN SDK (as an example). iii.. SAP Note 941595 for SUN SDK on x64 (as an example). SAP Note https://service.sap.com/sap/support/notes/394616. When patching AS ABAP-based SAP systems it is necessary to check for known problems within the patch procedure. For SAP NetWeaver 7.0-based SAP system, please read https://service.sap.com/sap/support/notes/822379 For the SAP Patch Day in TADM12_1 it is ESSENTIAL to observe this note and to apply some patches via SNOTE in advance! This will be considered later in this script. The patch procedure used in TADM12_1 is described in some detail on the following pages. This procedure is an almost naïve and unprepared approach to get a learning effect. Some of the following activities should be prepared before starting the unit “SAP Patch Day”. For each such activity it is noted when it should take place during TADM12.. © SAP AG 2012. TADM12_1. 2.

(11) Section 1: PREPARATION ACTIVITIES BEFORE SAP PATCH DAY Consisting of SUB-STEPS 1 to 12 Some steps relate to exercises in the course material, some are additional activities Install SAP Solution Manager (done before the Patch Day) 1.. Unit 2, exercise 1, task 2 Install Java JRE to G:\j2sdk (this destination is required later on!). Remark: This JRE version will be patched later during the Patch Day and finally will be replaced by SAP JVM. 2.. Install SAP Solution Manager 7.0 Enhancement Package 1 Follow the training material, Unit 3, exercise 3, except for the following changes: a.. Choose the SID “S00” this is the same SID for all participants! this is very important, otherwise you won’t be able to patch your system later on.. b.. Revise the size of the database data files: 7 x 15 GB (instead of using default values). c.. Number of sessions:100. d.. I/O Buffer Cache: 4096 MB. e.. 6 jobs for data load. f.. The installation of the secondary application server is optional.. © SAP AG 2012. TADM12_1. 3.

(12) 3.. Installation of the SAP ECC system (Unit 5) to be done using the user “install” – do not use the user “s00adm”. Follow the training material, Unit 5, exercise 5, except for the following changes/additional hints: a.. Choose the SID “E00” for your SAP ECC system.. b.. Observe the warning in exercise 5 about parallel MaxDB installations, otherwise the installation won’t work.. c.. In case you encounter a problem early during the installation relating to “msiexec.exe /norestart /L vcredist_x64.log …” proceed as follows: i.. Rename the file vcredist_x64.msi in directory G:\ADM110_col72\DVDs\EHP5_ERP_6.0\ EHP5_ERP_6.0_Installation_Master_13\ BS7i2010_Installation_Master\ IM_WINDOWS_X86_64\NTPATCH. to vcredist_x64.msi.old ii.. Copy vcredist_x64.msi from directory G:\ADM110_col72\DVDs\ Solution_Manager_7.0_EHP1\ Solution_Manager_7.0_EHP1_Installation_Master\ IM_WINDOWS_X86_64\NTPATCH. to directory G:\ADM110_col72\DVDs\EHP5_ERP_6.0\ EHP5_ERP_6.0_Installation_Master_13\ BS7i2010_Installation_Master\ IM_WINDOWS_X86_64\NTPATCH. iii.. In the window:. choose „No“. iv.. In this window:. choose „Retry“. It will work.. © SAP AG 2012. TADM12_1. 4.

(13) 4.. Unit 7, Exercise 8: Stop, Start and Logon Task 1: Do this on your system S00. Expand this exercise task by the following steps: Log off from the server (leaving the user “install”) Log on to the server using <sid>adm (“s00adm”) Log on to client 000 (using “SAP*”, for example) Create a named user (“TADM12-##”) in client 000 ## equals your group/seat number Assign the profile “SAP_ALL” in SU01 During the creation of this user in transaction SU01 you might need to create a new company address. The system will prompt you some fields to fill in. You can use, for example: Company address: Country: Time Zone:. SAP DE WDFT. You can use F4-help for other valid entries. Ignore warnings. Save. Log on to client 001 using SAP* Create another named user (“TADM12-##”) ## equals your group/seat number Assign the role: SAP_J2EE_ADMIN and the profile “SAP_ALL” in SU01 Log on with the new user to client 001 Change and note your new password. You will use this user later on (for example: for patching the content of the SLD). 5.. Unit 7, Exercise 9: Applying a Kernel Patch You can skip this exercise. You will do this and much more during Unit 8: SAP Patch Day.. © SAP AG 2012. TADM12_1. 5.

(14) 6.. Unit 7, Exercise 10: SAP License, SAProuter Task 1: Please go to step 9: “Apply a valid licence and Import Essential SAP Notes”, of Section 2: SAP Patch Day of THIS document. Apply the license as described there. Task 2: For the configuration of the RFC connection SAPOSS follow the instructions given below. Skip the exercise description of exercise 10, task 2. SM59: Configure the RFC connection SAPOSS according to SAP Note 182308: Incorrect logon data in R/3 destination SAPOSS (CHANGE/ADAPT the existing connection named) SAPOSS: Using “/H/tdcsaprouter/H/sapserv3/H/oss001/”:. pw: for the already entered user, is: ”cpic”:. This step is essential and needed later on. Test this connection and its connectivity in SM59.. © SAP AG 2012. TADM12_1. 6.

(15) 7.. Unit 7, Exercise 11: Initial Configuration of an AS ABAP based SAP System Before starting with Task 1, execute the following steps: a.. Install the MaxDB Database Studio (as provided at ..\TADM12_1_72_Patch_Day\00_Preparation\ MaxDB_Database_Studio_7_9\DBSTUDIO SDBSETUP.exe):. b.. Shutdown your SAP System using MMC:. c.. Shutdown the MaxDB using Database Studio (use the user “control”/<master password> set during installation). d.. Set DB Overwrite Mode using Database Studio:. © SAP AG 2012. TADM12_1. 7.

(16) e.. Restart MaxDB and the SAP System (It might be necessary, in case you rebooted your server, to enter the correct pw for the user SAPServices00 into 2 services if necessary, assuming your system uses instance number 00):. or change the account used for log on (this problem might occur in our training environment, it should not occur in YOUR companies environment):. © SAP AG 2012. TADM12_1. 8.

(17) Unit 7, Exercise 11, Task 1: This task is not optional. The steps described in the course material can be executed as described. Use your newly created named user for these activities. SE06: Execute “…after installation…” steps STMS: Configure TMS with default settings keeping the default values is – for TADM12_1 – absolutely necessary. Otherwise later steps in TADM12_1 won’t work.. set in SCC4 client 000: Automatic Recording of Changes Unit 7, Exercise 11, Task 2: This task is not optional. Adapt the instance profile as follows. Later on, continue working with transaction RZ10 as needed. Set some profile parameters, especially PHYS_MEMSIZE (for TADM12_1: use 2048 [MB], see below):. Don’t be scared about the many swaps.. © SAP AG 2012. TADM12_1. 9.

(18) You can adapt some parameters, using the file named Parameter_Changes.txt prepared for TADM12, week 1, at: ..\TADM12_1_72_Patch_Day\00_Preparation: login/system_client = 000 PHYS_MEMSIZE = 2048 rdisp/wp_no_dia = 14 rdisp/wp_no_btc = 8 stat/max_files = 96 rdisp/max_wprun_time = 3600 # https://service.sap.com/sap/support/notes/1166259 abap/shared_objects_size_MB = 100 # Nametab buffers #parameter created, Table definition buffer rsdb/ntab/entrycount = 100000 #parameter created, field description buffer rsdb/ntab/ftabsize = 150000 rsdb/ntab/entrycount = 80000 #parameter created, Short nametab rsdb/ntab/sntabsize = 15000 #parameter created, Initial record buffer rsdb/ntab/irbdsize = 36000 #parameter created, PXA buffer abap/buffersize = 500000 abap/buffer_fragments = 1 # ACCORDING TO SAP NOTE 746984 abap/pxa_cache = 1024 #parameter created, CUA buffer rsdb/cua/buffersize = 15000 #parameter created, Screen buffer zcsa/presentation_buffer_area = 44000000 sap/bufdir_entries = 20000 #parameter created, Generic Table buffer zcsa/table_buffer_area = 150000000 zcsa/db_max_buftab = 25000 #parameter created, Single record buffer rtbb/buffer_length = 100000 rtbb/max_tables = 5000 #parameter created, Export/import buffer rsdb/obj/buffersize = 80000 rsdb/obj/max_objects = 10000 # Roll area #parameter created rdisp/ROLL_MAXFS = 131072 #parameter created rdisp/ROLL_SHM = 65536. © SAP AG 2012. TADM12_1. 10.

(19) Append these parameters to the instance profile of your SolMan system. Restart your SolMan system. Tasks 3, 4, 5 and 6 can be done as described in the training material. Unit 7, Exercise 11, Task 7: This task is not optional. In contrast to the description of this exercise in the training material, plan SGEN as described: Schedule SGEN for the following SAP software components: SAP_BASIS, SAP_ABA, SAP_BW, ST, ST-A/PI This will take about 2h15min and creates about 15 GB of additional DB volume. Should be planned overnight (Monday/Tuesday) Later on, execute additional load creation for BSP Applications and Web Dynpros later as well:. You can plan these steps in parallel to other work, for example on Tuesday morning. After SGEN (see below) for some components, the DB will be filled like this:. © SAP AG 2012. TADM12_1. 11.

(20) The caches (sizes) will look like this:. 8.. Unit 8, Exercise 12, Task 1 Install SAP GUI as described in the training material.. Task 2 This task is optional, as you will patch SAP GUI in step 5 of Section 2 of this document. Task 3 – as in the training material. 9.. Unit 8, Exercise 13: optional, as described in the training material.. © SAP AG 2012. TADM12_1. 12.

(21) 10. Information/versions after installation: SAP MMC Version: Max DB Version: Kernel: ST: SAP_BASIS: ST-A/PI: ST-PI: JAVA –version: SAP GUI: SLD Content:. 7100.109.15.8983 7.7.04.28, DB: Used 36,5 GB / 107 GB 701/32 400/18 7.01.02 01L_CRM570/00 2008_1_700/0000 1.4.2_17 7.20 PL4 1.5.32 (SAP_CR 4.0 (produced 04/24/2008). 11. Stack 28 brings Kernel 150, AS ABAP/AS Java: SPS 10 (7.01.10) DB: used 51,5 GB (after SGEN, step 20) 12. DB13: Schedule Statistics Update & Backup Plan these activities to take place on Tuesday night just before the “Patch Day” in TADM12_1.. © SAP AG 2012. TADM12_1. 13.

(22) For creating the Backup, you need to define a backup device, see the following screenshot: (you are required to create the directory “G:\Backup”, the backup file will be named “S00” in this case as an example, the SID of the system). The Update all Optimizer Statistics ran for about 30 minutes:. The Check Database Structure run took about 2 hours:. The Complete Data Backup took about 30 minutes:. All this has been preparatory work for the actual “Patch Day” starting on Wednesday morning. © SAP AG 2012. TADM12_1. 14.

(23) Unit 1 Overview and Architecture of SAP Systems Unit Overview This unit explains the SAP Business Suite, the solutions inside (SAP ERP, SAP CRM, SAP SCM, SAP SRM) and the SAP systems within these solutions from a technical point of view.. Unit Objectives After completing this unit, you will be able to: • • • •. Describes the architecture of the SAP Business Suite, the SAP solutions and the SAP systems from a technical point of view List the technical processes of an AS ABAP based SAP system List the technical processes of an AS Java based SAP system Reflect the combination of SAP systems and Unicode. Unit Contents Lesson: Overview of SAP Systems ................................................. 2 Lesson: Technical Architecture of SAP Systems .................................. 9. 2012. © 2011 SAP AG. All rights reserved.. 1.

(24) Unit 1: Overview and Architecture of SAP Systems. TADM12_1. Lesson: Overview of SAP Systems Lesson Overview This lesson describes the architecture of the SAP Business Suite, the SAP solutions and the SAP systems from a technical point of view.. Lesson Objectives After completing this lesson, you will be able to: •. Describes the architecture of the SAP Business Suite, the SAP solutions and the SAP systems from a technical point of view. Business Example Describes the architecture of the SAP Business Suite, the SAP solutions and the SAP systems from a technical point of view.. SAP Business Suite, SAP Solutions, SAP Systems The SAP Business Suite consists of several SAP Solutions: SAP ERP: SAP Enterprise Resource Planning SAP CRM: SAP Customer Relationship Management SAP SCM: SAP Supply Chain Management SAP SRM: SAP Supplier Relationship Management SAP PLM: SAP Product Lifecycle Management The by far biggest solution is SAP ERP. Note: Another term for SAP Solution is SAP Application. This term is especially used for SAP ERP. The SAP Solutions consist of several installable units, the SAP systems. The by far biggest SAP system, containing the most business functions, is SAP ECC - formerly known as SAP R/3 Enterprise - formerly known as SAP R/3. Note: SAP ECC stands for SAP Enterprise Resource Planning Central Component - because it is the central component of SAP ERP. The more technical SAP systems from the different solutions are also called SAP NetWeaver systems.. 2. © 2011 SAP AG. All rights reserved.. 2012.

(25) TADM12_1. Lesson: Overview of SAP Systems. Caution: There are many more components inside SAP Business Suite than listed here.. Figure 1: SAP Business Suite. Because SAP ERP is the largest SAP Solution and SAP ECC is the largest Component we will look at these - as an example - in more detail. Besides many others, SAP ERP contains the following SAP systems: SAP ECC: SAP ERP Central Component SAP XSS: SAP Employee and Manager Self Services SAP BW: SAP NetWeaver Business Warehouse SAP Portal: SAP NetWeaver Portal SAP PI: SAP NetWeaver Process Integration SAP MDM: SAP NetWeaver Master Data Management Some of these SAP systems also belong to SAP NetWeaver: SAP BW, SAP Portal, SAP PI, SAP MDM.. 2012. © 2011 SAP AG. All rights reserved.. 3.

(26) Unit 1: Overview and Architecture of SAP Systems. TADM12_1. Figure 2: Example: SAP ERP. Several renamings took place in the past; here are a few of them: 1. 2.. 3. 4. 5. 6.. SAP R/3 was renamed to SAP R/3 Enterprise beginning with 4.7, and again was renamed to SAP ECC beginning with 6.0. The SAP Basis was renamed to SAP Web Application Server (SAP Web AS) beginning with 6.10, and again was renamed to SAP NetWeaver Application Server (SAP NetWeaver AS) beginning with 7.00. SAP Business Warehouse (SAP BW) was renamed to SAP Business Intelligence (SAP BI), and was renamed back to SAP BW. SAP Exchange Infrastructure (SAP XI) was renamed to SAP Process Integration (SAP PI). SAP Enterprise Portal (SAP EP) was renamed to SAP NetWeaver Portal. .... In addition, every SAP customer needs to run an additional SAP system: the SAP Solution Manager system. It is needed to control the SAP system landscape. SAP Solution Manager is mandatory for several administrative tasks: for example patching the SAP systems and upgrading them. For more information concerning SAP ERP consult the Installation Master Guide at SAP Service Marketplace, Quick Link instguides or SAP Service Marketplace, Quick Link erp.. 4. © 2011 SAP AG. All rights reserved.. 2012.

(27) TADM12_1. Lesson: Overview of SAP Systems. Releases The new release of the SAP Business Suite in June 2011 is SAP Business Suite 7i2010. The previous SAP Business Suite release was SAP Business Suite 7. In 2012 the next release will be shipped: SAP Business Suite 7i2011. Within SAP Business Suite 7i2010 the fours major Solutions have the following releases: SAP ERP 6.05 - actually: SAP Enhancement Package 5 for SAP ERP 6.0 SAP CRM 7.01 - actually: SAP Enhancement Package 1 for SAP CRM 7.0 SAP SCM 7.01 - actually: SAP Enhancement Package 1 for SAP SCM 7.0 SAP SRM 7.01 - actually: SAP Enhancement Package 1 for SAP SRM 7.0 The major component within SAP ERP is SAP ECC. These are the releases of SAP ECC, that are still in maintenance by SAP in 2011:. Figure 3: SAP ECC: Releases. No SAP R/3 release exists for SAP Basis/SAP Web AS/SAP NetWeaver AS 4.6D, 6.10 and 7.10. Concerning the ABAP part, SAP Web AS 6.30 is the same as SAP Web AS 6.20 (with more SAP Support Packages).. 2012. © 2011 SAP AG. All rights reserved.. 5.

(28) Unit 1: Overview and Architecture of SAP Systems. TADM12_1. Software Components Using the example of an up to date (June 2011) SAP ECC 6.05 system, we want to have a look at the software components.. Figure 4: Software Components. Note: These are only the major software components of an SAP ECC 6.05. There are many more. The kernel is no software component. It is the runtime environment to run the software components. The kernel is database and operating system depending. It is available for several operating systems and databases. For details see the Product Availability Matrix at SAP Service Marketplace, Quick Link pam. the kernel is also called SAP Application Server or SAP Instance or Dispatcher and Workprocesses. The software components SAP_BASIS and SAP_ABA and others form the basis. They contain the basis functionality, like user administration, performance tools, the Transport Management System (TMS), development tools and so on.. 6. © 2011 SAP AG. All rights reserved.. 2012.

(29) TADM12_1. Lesson: Overview of SAP Systems. The basis software components together with the kernel are also called SAP NetWeaver Application Server. In case of an ABAP based system (like SAP ECC) abbreviated with AS ABAP, in case of a Java based system (like SAP XSS) abbreviated with AS Java. The software components on top of the AS ABAP (or AS Java) are application specific software components. They are not to much of interest here. Examples for SAP system based on AS ABAP are: SAP ECC SAP BW SAP CRM Server SAP SCM Server SAP SRM Server Examples for SAP system based on AS Java are: SAP XSS SAP Portal In addition there are two SAP system based on AS ABAP and AS Java simultaneously, so called dual stack systems: SAP Solution Manager SAP PI. 2012. © 2011 SAP AG. All rights reserved.. 7.

(30) Unit 1: Overview and Architecture of SAP Systems. TADM12_1. Lesson Summary You should now be able to: • Describes the architecture of the SAP Business Suite, the SAP solutions and the SAP systems from a technical point of view. 8. © 2011 SAP AG. All rights reserved.. 2012.

(31) TADM12_1. Lesson: Technical Architecture of SAP Systems. Lesson: Technical Architecture of SAP Systems Lesson Overview In this lesson, you will learn about the structure and the processes of an SAP system, and how to use the terms system and instance correctly. Also you will learn about SAP systems and Unicode.. Lesson Objectives After completing this lesson, you will be able to: • • •. List the technical processes of an AS ABAP based SAP system List the technical processes of an AS Java based SAP system Reflect the combination of SAP systems and Unicode. Business Example You want to learn about the architecture of an SAP system.. AS ABAP and AS Java based SAP Systems For the installation procedure you have to understand the architecture of an SAP system. An SAP system consists of the components shown in the graphic: One database and one or more instances. The instance that, together with the database, forms a functional SAP system is also known as the central instance. There is not more than one central instance installed for every SAP system. A central system is an SAP system consisting out of only the central instance and the database, running on the same host. It is possible to install two instances of an SAP system or even of different SAP systems on one host. Before you install two SAP systems (and possibly their databases) on one host, you should examine the extent to which the chosen hardware is capable of handling the anticipated load. Other aspects to be considered are situations such as upgrades or restore scenarios - for example, one SAP system is to be recreated from a backup whilst the other SAP system should continue to be used without interference. Within a company, no SAP system IDs (SIDs) should be used more than once.. 2012. © 2011 SAP AG. All rights reserved.. 9.

(32) Unit 1: Overview and Architecture of SAP Systems. TADM12_1. An instance of an SAP system is an administrative unit in which components of an SAP system that provide one or more services are combined. The services within one instance are started or stopped together. There are three different types of SAP systems: AS ABAP based - for example SAP ECC or SAP BW AS Java based - for example SAP XSS or SAP Portal AS ABAP + Java based - only SAP Solution Manager and SAP PI The (ABAP) dispatcher is the central process of an ABAP instance. This process starts other processes that belong to the instance, such as the gateway (abbreviated as GW in the graphic), the Internet Communication Manager (ICM), and a configured number of work processes. You configure an ABAP instance using an instance profile. The ABAP instance has shared (main) memory areas and its own directory structure in the file system.. Figure 5: AS ABAP based SAP System. An (ABAP) instance consists of a dispatcher and several work processes. An instance requires a minimum of two dialog work processes. Otherwise it is not possible to start it. Several instances can be installed on the same host. The instances must then have different instance numbers. The instance number is a two-digit number, and is chosen at installation. It defines a range of standard communication ports. 10. © 2011 SAP AG. All rights reserved.. 2012.

(33) TADM12_1. Lesson: Technical Architecture of SAP Systems. for processes of the instance. The standard port of the dispatcher is 32$$ where $$ denotes the instance number. For example 3200 if the instance number 00 was chosen at installation. If several instances are installed on a shared host, these instances use their own, separate, (main) memory areas, and each instance has its own directory structure in the file system. Hint: You should not use the instance numbers 98 and 99, because they are reserved for the SAProuter. An SAP system can have several instances. One of them is the central instance. It includes an additional process – the ABAP Message Server – which only exists once across the system. Furthermore, the central instance is the only instance that offers one or more enqueue work processes. Hint: Note that this definition of the term central instance cannot be used in the sense described when the ABAP Central Services Instance (ASCS) is installed. You will find a description of the ASCS concept in the appendix to this lesson. An instance is also called an application server. The application server provides the runtime environment for the business applications of an SAP system. The (Java) dispatcher is the central process of a Java instance. This process distributes the incoming requests to the available server processes.. 2012. © 2011 SAP AG. All rights reserved.. 11.

(34) Unit 1: Overview and Architecture of SAP Systems. TADM12_1. Figure 6: AS Java based SAP System. A Java instance consists of a Java dispatcher and one or more server process. Several instances can be installed on the same host. A (Java-based) SAP system can have several instances. One of them is the (Java) central instance. It includes an additional process - the Software Deployment Manager (SDM) - which can only be configured once across the SAP system. There is also a Java Central Services (SCS or CS) instance. This CS instance offers the Java Message Server and the Java Enqueue Server. In the standard installation, the Java central instance and the CS instance are located on the same host. You can install additional Java instances on the same host together with the central instance or on other separate hosts. AS ABAP+Java-based instances (dual stack instances) offer ABAP and Java-based processes. This results in the following definition of a central instance: The central instance of an AS ABAP+Java-based SAP system offers all the processes of an ABAP central instance and a Java central instance.. 12. © 2011 SAP AG. All rights reserved.. 2012.

(35) TADM12_1. Lesson: Technical Architecture of SAP Systems. The Java Central Services instance does not belong to the AS ABAP+Java central instance. It is started and stopped separately. Note: The Java server processes are not the equivalent to the ABAP work processes: the Java server processes distribute the incoming work to underlying so called threads. So the Java server processes are kind of sub-dispatchers. Note: In future AS Java releases, starting from 7.10, there will be no Java dispatcher any longer. Instead the load balancing is been done by a Java ICM process.. Figure 7: AS ABAP+Java based SAP System. An AS ABAP+Java-based SAP system always provides one ABAP+Java-based central instance. Other instances are also AS ABAP+Java-based. Caution: Again: avoid installing AS ABAP+Java based (dual stack) systems! Exceptions: SAP PI and SAP Solution Manager.. 2012. © 2011 SAP AG. All rights reserved.. 13.

(36) Unit 1: Overview and Architecture of SAP Systems. TADM12_1. Since several releases it is almost not possible to install other dual stack systems any longer . This is because of several problems and high costs related to this architecture. Hint: In case you are still running a dual stack systems that was installed in former days, there is a possibility to split it up into an AS ABAP and a second AS Java based SAP system. This can be done using the installation tool SAPinst. In 2011 this should be available for splitting up all types of SAP systems.. Appendix: ABAP Central Services (ASCS) As of SAP NetWeaver 7.0, for high availability AS ABAP+Java-based SAP systems (such as SAP systems on Windows clusters), you have to set up a separate instance for central services instance for AS ABAP systems, the ABAP Central Services (ASCS). The ASCS instance enables you to separate the ABAP Message Server and the ABAP Enqueue Service (not implemented as a work process in this case) from the ABAP central instance. This cluster will then contain the ASCS instance and the database. Outside the cluster, you may have any number of ABAP instances of equal priority. This means that there is no longer any central instance in your SAP system. The same concept occurs in AS Java-based SAP systems of the installation standard: the (Java) Central Services instance with a Java message server and Java enqueue server. On the Java side, the concept is still referred to as a central instance because the Software Deployment Manager is installed here. Hint: You will find more information about the ASCS instance here: SAP Note 1010990 - Configuring a Standalone Gateway in an HA ASC instance SAP Note 1011190 - MSCS: Splitting the Central Instance After Upgrade to 7.0/7.1 You will also find further information on installing and configuring ASCS instances in the corresponding installation and upgrade guide for your SAP system at SAP Service Marketplace, Quick Link instguides.. Usage Types The solutions of SAP Business Suite 7i2010 are based on SAP NetWeaver 7.02 (SAP Enhancement Package 2 for SAP NetWeaver 7.0), which in turn consists of Usage Types.. 14. © 2011 SAP AG. All rights reserved.. 2012.

(37) TADM12_1. Lesson: Technical Architecture of SAP Systems. SAP NetWeaver systems are configured for a certain purpose, as indicated by Usage Types. • • • •. are structuring element for SAP software on a technical level. determine the intended purpose of an SAP system. are realized by installing and configuring a collection of software components. may require other Usage Types in the same SAP system to operate.. The following lists the usage types for SAP NetWeaver: • • • • • • • • •. Application Server ABAP (AS ABAP) Application Server Java (AS Java) Enterprise Portal Core (EPC) Enterprise Portal (EP) Business Intelligence (BI) Business Intelligence Java Components (BI Java) Development Infrastructure (DI) Mobile Infrastructure (MI) Process Integration (PI). AS ABAP is the basis of SAP ABAP systems. AS Java is the basis of SAP Java systems. EPC provides full portal capabilities. EP adds additional capabilities such as knowledge management and collaboration to EPC. Usage Type EPC is therefore a prerequisite for Usage Type EP. BI provides Business Warehouse (BW) capabilities, such as Enterprise Data Warehousing, Enterprise Reporting, Query, and Analysis, and Business Planning and Analytical Services. BI Java is used to provide the Java runtime for IT scenarios such as Enterprise Reporting, Query, and Analysis as well as Business Planning and Analytical Services. It enables variants such as Information Broadcasting and Ad-hoc Query & Analysis. It also enables Web Dynpro-based BI applications and third party data access via Universal Data Integration. BI Java requires Usage Types EP and EP Core in the same SAP system. BI Java is BEx Web (Business Explorer Web). DI provides the environment for all processes of Java-based development and Java-based software life-cycle management.. 2012. © 2011 SAP AG. All rights reserved.. 15.

(38) Unit 1: Overview and Architecture of SAP Systems. TADM12_1. MI is used to enable field personnel to participate in a business process in an occasionally connected mode. PI consists of core components that model, design, automate, and integrate processes in one or more application systems. For the integration of internal and cross-company processes, PI is used to incorporate several the functions. PI was formerly known as XI (Exchange Infrastructure).. Unicode Unlike other standard code pages, Unicode defines a character set that includes virtually all characters used worldwide and as a result provides consistent, global character encoding. Unicode is defined by the Unicode consortium (see http://www.unicode.org for more information), which consists of leading companies in the world-wide IT industry.. Figure 8: SAP Unicode and Non-Unicode Solution. Up to and including SAP ERP 2004, SAP has provided multiple language support using single code pages as well as multiple code pages in a single installation with MDMP (Multi-Display-Multi-processing), which permits the application server to dynamically switch code pages according to the logon language and language keys. 16. © 2011 SAP AG. All rights reserved.. 2012.

(39) TADM12_1. Lesson: Technical Architecture of SAP Systems. (see SAP Note 73606). However, even in an MDMP system, an individual user can use only the characters belonging to one code page at a time. To enhance language support for SAP Business Suite systems, SAP considers Unicode the appropriate development direction and strategy because Unicode offers a single, consistent, and standard character set encoding for virtually all languages in the world. A code page describes the assignment of one character to one hexadecimal (HEX) value. One (normal: 1 byte) code page represents 256 characters. • • • • •. SAP systems support around 40 different languages. Only languages belonging to the same code page are usable without restrictions. Up to and including SAP ECC 5.0, SAP supports multiple languages with Multi-Display-Multi-Processing (MDMP) systems. Since SAP ECC 6.0 MDMP is not supported any longer. SAP recommends to use Unicode as the standard technology to cover multilingual language requirements. Single code page systems (Non-MDMP) are still supported for existing SAP systems, but not any longer for new installations. Hint: SAP recommends to convert existing SAP systems to Unicode as soon as possible. New installations can only be performed as Unicode installations.. Since SAP ECC 6.0 MDMP is not supported any longer. SAP recommends to use Unicode. An upgrade from an existing SAP system older than SAP ECC 6.0 to SAP ECC 6.0 and above requires a system conversion to Unicode. You can find more information at SAP Service Marketplace, Quick Link unicode and SAP Note 79991, SAP Note 540911, SAP Note 745030 and SAP Note 73606. Generally single code page systems (Non-MDMP / Non-blended code pages) are still supported (with restrictions mentioned e.g. in SAP Note 858869 and SAP Note 838402). However SAP strongly recommends Unicode (for new installation see SAP Note 838402). New releases of SAP NetWeaver and SAP applications based on SAP NetWeaver, which are released in 2007 or later, will no longer support new installations of Non-Unicode systems. Also see SAP Note 379940. Unicode is the recommended system type for all SAP systems that deploy Unicode-enabled solutions and components.. 2012. © 2011 SAP AG. All rights reserved.. 17.

(40) Unit 1: Overview and Architecture of SAP Systems. TADM12_1. Unicode is the mandatory system type for: • • •. 18. SAP systems requiring a combination of languages that are based on more than one non-Unicode code page SAP systems that deploy Java applications (for example Java applications, WebDynpro applications) SAP AS ABAP systems that communicate with Java components. © 2011 SAP AG. All rights reserved.. 2012.

(41) TADM12_1. Lesson: Technical Architecture of SAP Systems. Lesson Summary You should now be able to: • List the technical processes of an AS ABAP based SAP system • List the technical processes of an AS Java based SAP system • Reflect the combination of SAP systems and Unicode. Related Information •. SAP NetWeaver - SAP Library at https://help.sap.com: Documentation → SAP NetWeaver → SAP NetWeaver 7.0 → English → SAP NetWeaver Library - SAP Developer Network at irj/sdn/netweaver. • • •. 2012. SAP ECC and SAP ERP: SAP Service Marketplace, Quick Link erp Unicode: SAP Service Marketplace, Quick Link unicode MCOD: SAP Service Marketplace, Quick Link mcod. © 2011 SAP AG. All rights reserved.. 19.

(42) Unit Summary. TADM12_1. Unit Summary You should now be able to: • Describes the architecture of the SAP Business Suite, the SAP solutions and the SAP systems from a technical point of view • List the technical processes of an AS ABAP based SAP system • List the technical processes of an AS Java based SAP system • Reflect the combination of SAP systems and Unicode. 20. © 2011 SAP AG. All rights reserved.. 2012.

(43) TADM12_1. Test Your Knowledge. Test Your Knowledge 1.. SAP ECC 6.05 and SAP R/3 4.6C are two completely different SAP systems, which are shipped by SAP. Determine whether this statement is true or false.. □ □ 2.. True False. SAP supports Unicode, Non-unicode and MDMP with SAP ECC 6.05 installations. Determine whether this statement is true or false.. □ □. 2012. True False. © 2011 SAP AG. All rights reserved.. 21.

(44) Test Your Knowledge. TADM12_1. Answers 1.. SAP ECC 6.05 and SAP R/3 4.6C are two completely different SAP systems, which are shipped by SAP. Answer: False Over years, SAP enhanced SAP R/3 4.6C with additional functionality to SAP ECC 6.05.. 2.. SAP supports Unicode, Non-unicode and MDMP with SAP ECC 6.05 installations. Answer: False With SAP ECC 6.0 and above MDMP is not supported any longer.. 22. © 2011 SAP AG. All rights reserved.. 2012.

(45)

(46)

(47) Unit Summary. 23. TADM12_1. © 2011 SAP AG. All rights reserved.. 2012.

(48) Unit Summary. 24. TADM12_1. © 2011 SAP AG. All rights reserved.. 2012.

(49) Unit 2 Preparing an Installation Unit Overview This unit explains how to prepare the installation of an SAP system.. Unit Objectives After completing this unit, you will be able to: • • • • •. Start and use SAPinst Name the log files used by SAPinst Perform the general preparation steps needed to install an SAP system Perform the necessary preparation steps to install an SAP system on Windows Perform the necessary preparation steps to install an SAP system on UNIX. Unit Contents Lesson: Introducing SAPinst ....................................................... 26 Lesson: General Preparation for Installation ..................................... 34 Exercise 1: Prepare the Installation Part 1/2................................. 49 Lesson: Additional Preparation for Installation on Windows ................... 54 Exercise 2: Prepare the Installation Part 2/2................................. 61 Lesson: Additional Preparation for Installation on UNIX........................ 64. 2012. © 2011 SAP AG. All rights reserved.. 25.

(50) Unit 2: Preparing an Installation. TADM12_1. Lesson: Introducing SAPinst Lesson Overview This lesson describes how to use SAPinst.. Lesson Objectives After completing this lesson, you will be able to: • •. Start and use SAPinst Name the log files used by SAPinst. Business Example As the system administrator, you would like to know some details on starting and using SAPinst.. Overview of SAPinst SAPinst includes a SAPinst GUI and a GUI server, which both use a Java Runtime Environment. In a standard installation SAPinst, SAPinst GUI, and the GUI server run on the same host. If required, you can instead perform a remote installation with SAPinst, whereby SAPinst GUI is running on a separate host from SAPinst and the GUI server. When you start SAPinst, SAPinst GUI and the GUI server also start. SAPinst GUI connects to the GUI server with a secure SSL connection, and the GUI server connects to SAPinst.. Starting SAPinst The following procedure starts SAPinst for Windows on a single host: 1. 2.. Log on to your host as a user who is a member of the local administration group. Start SAPinst from the installation master DVD. Double-click sapinst.exe from in the directory <DVD drive>:\IM_WINDOWS_<platform> Caution: Do not use user <sapsid>adm to do installations.. 26. © 2011 SAP AG. All rights reserved.. 2012.

(51) TADM12_1. Lesson: Introducing SAPinst. Figure 9: Start SAPinst on Windows. SAPinst normally creates the installation directory sapinst_instdir, where it keeps its log files, and which is located directly in the Program Files directory. If SAPinst is not able to create sapinst_instdir there, it tries to create sapinst_instdir in the directory defined by the environment variable TEMP. SAPinst creates a subdirectory for each installation service. Note: We recommend that you keep all installation directories until the system is completely and correctly installed. 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 called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You can safely delete them. The temporary directory also contains the SAPinst Self-Extractor log file dev_selfex.out, which might be useful if an error occurs. Hint: If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058.. 2012. © 2011 SAP AG. All rights reserved.. 27.

(52) Unit 2: Preparing an Installation. TADM12_1. If you want to terminate SAPinst and the SAPinst Self-Extractor, choose one of the following options: • •. 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.. On UNIX you start SAPinst in the following way: 1. 2.. Log on to your host as user root. Start SAPinst from the installation master DVD with the command ./sapinst. Caution: Make sure that the root user has not set any environment variables for a different SAP system or database.. SAPinst normally creates the installation directory sapinst_instdir directly below the temporary directory. SAPinst finds the temporary directory by checking the value of the environment variables TEMP, TMP, or TMPDIR. If no value is set for these variables, SAPinst uses /tmp as default installation directory. Make sure that the temporary directory has the permissions 777. The SAPinst self-extractor extracts the SAPinst executables to the temporary directory. These executables are deleted again after SAPinst has stopped running. If required, you can terminate SAPinst and the SAPinst Self-Extractor by pressing CTRL+C. The temporary directory also contains the SAPinst Self-Extractor log file dev_selfex.out, which might be useful if an error occurs. Caution: Make sure that your operating system does not delete the contents of the temporary directory /tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for example by using a crontab entry. Hint: If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058. During the installation, the default ports 21200 and 21212 and 4239 are used for communication between SAPinst, GUI server, SAPinst GUI, and HTTP server. SAPinst uses port 21200 to communicate with the GUI server. The GUI server uses port 21212 to communicate with SAPinst GUI. 4239 is the port of the HTTP server, which is part of the GUI server. You get an error message if one of these ports is already in use by another service. In this case start sapinst with the following command line parameters:. 28. © 2011 SAP AG. All rights reserved.. 2012.

(53) TADM12_1. Lesson: Introducing SAPinst. SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server> GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui> GUISERVER_HTTP_PORT=<free_port_number_http_server> To get a list of all available SAPinst properties, start SAPinst with the parameter -p: Windows: sapinst.exe -p UNIX: ./sapinst -p. Remote Installation with SAPinst SAPinst can also be used to perform a remote installation. This enables you to install an SAP system on another host (the remote host) while monitoring the installation with the SAPinst GUI on your local Windows or UNIX host (the local host).. Figure 10: Remote Installation with SAPinst. Prerequisites to perform a remote installation with SAPinst are: • •. 2012. Both hosts are on the same network and can ping each other. SAPinst Server uses the ports 21200 and 21212 to communicate with SAPinst GUI. If one of these ports is used by another service, SAPinst gives an error message.. © 2011 SAP AG. All rights reserved.. 29.

(54) Unit 2: Preparing an Installation. TADM12_1. Start SAPinst using the following procedure: 1.. Log on to your remote host. 2.. • Windows: as a user who is a member of the local administration group. • UNIX: as root. Start SAPinst form the installation master DVD using the following command:. 3.. • Windows: sapinst.exe -nogui • UNIX: ./sapinst -nogui On your local host start SAPinst GUI by executing the following command: • •. Windows: startinstgui.bat -host <remote hostname> UNIX: ./startInstGui.sh -host <remote hostname>. . For this you need to have access to the installation master DVD from your local host. Hint: 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 on Windows and ./startInstGui.sh -h on UNIX.. Troubleshooting with SAPinst If an error occurs, SAPinst stops the installation and displays a dialog informing you about the error. In this case, you can view the log file by choosing View Log. If you can solve the error manually, you can do during leaving SAPinst opened. After you fixed the problem choose Retry to continue the installation. Hint: There are some known error situations where you can choose Retry and SAPinst will continue without any error.. 30. © 2011 SAP AG. All rights reserved.. 2012.

(55) TADM12_1. Lesson: Introducing SAPinst. Figure 11: SAPinst Error Log: sapinst_dev.log. All the installation information is logged in several log files. The main SAPinst output files contain the following information: • •. sapinst.log - information on installation progress sapinst_dev.log - records all messages of every installation step in detail. The log files sapinst.log and sapinst_dev.log can be found in the current installation directory. Additional log files might be written during the installation process. The additional logs are referenced in sapinst.log and sapinst_dev.log. The logs of SAPinst GUI and the GUI Server are written to the folder %userprofile%\.stdgui (Windows) <user_home>/.stdgui (UNIX) If SAPinst GUI does not start, check the file sdtstart.err in the current %userprofile% (Windows) or <user_home> (UNIX) directory.. 2012. © 2011 SAP AG. All rights reserved.. 31.

(56) Unit 2: Preparing an Installation. TADM12_1. SAPinst - XML files SAPinst is controlled by XML files. The main XML files are: • •. dialog.xml - contains all dialogs used in the installation keydb.xml - SAPinst records the installation progress and user input in the keydb.xml file messages.xml - contains all messages used in the installation control.xml - contains the component definition used by SAPinst packages.xml - for software package administration. • • •. SAPinst GUI Handling When using the SAPinst GUI, the following functions are available on the different SAPinst GUI dialogs (input screens, installation progress screen, message boxes): Function. Description. F1. Displays detailed information about each input parameter.. Back. Displays the previous dialog for editing.. Next. Displays the next dialog for editing.. Cancel. 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.. 32. Log Off. Stops the SAPinst GUI, but SAPinst and the GUI server continue running. You can later reconnect to the same SAPinst installation from the same or another host by starting SAPinst GUI separately.. View Log. Displays the content of the sapinst.log file during the installation.. Retry. Performs the installation step again (if an error has occurred).. Stop. Stops the installation without further changing the installation files. You can continue the installation later from this point.. Continue. Continues with the option you have chosen before.. © 2011 SAP AG. All rights reserved.. 2012.

(57) TADM12_1. Lesson: Introducing SAPinst. Lesson Summary You should now be able to: • Start and use SAPinst • Name the log files used by SAPinst. 2012. © 2011 SAP AG. All rights reserved.. 33.

(58) Unit 2: Preparing an Installation. TADM12_1. Lesson: General Preparation for Installation Lesson Overview This lesson explains the general preparation steps needed to install an SAP system.. Lesson Objectives After completing this lesson, you will be able to: •. Perform the general preparation steps needed to install an SAP system. Business Example You want to perform the general preparation steps needed to install an SAP system.. Steps for Preparing a SAP System Installation The following steps need to be performed as preparation for the installation of an SAP system. General Installation Preparation Steps • • • • • • • • • •. 34. Download the installation DVDs. Read the required installation guides Read all required SAP Notes as listed in the installation guides. Install/update SAP front-end components like SAP GUI for Windows. Install Java Runtime Environment for SAPinst. Set environment variable for SAPinst. Install Java Development Kit for SAP NetWeaver AS Java (depending on usage types and operation system). Set environment variable for SAP NetWeaver AS Java. Download Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files for AS Java based SAP systems). Check if the necessary hardware and software requirements are fulfilled (Prerequisites Check).. © 2011 SAP AG. All rights reserved.. 2012.

(59) TADM12_1. Lesson: General Preparation for Installation. Figure 12: Download Installation DVDs. 2012. © 2011 SAP AG. All rights reserved.. 35.

(60) Unit 2: Preparing an Installation. TADM12_1. Read Installation Guides and SAP Notes. Figure 13: Read the Installation Guides. For each installation, you should read the corresponding installation guide for your specific combination of operating system and database system. It can be found at SAP Service Marketplace, Quick Link instguides. You should read it carefully before starting the installation process. Have the installation guide ready during the installation to follow each successive step of the installation procedure. Read relevant SAP Notes Read the current version of all the relevant SAP Notes. These SAP Notes contain additional information that is required when performing an installation. The SAP Notes can be found on the SAP Service Marketplace, Quick Link notes. Read only the SAP Notes relevant for your specific installation. To avoid known problems read them carefully before beginning an installation. Have all the relevant SAP Notes at hand during the installation so that you can quickly solve potential problems that might occur.. 36. © 2011 SAP AG. All rights reserved.. 2012.

(61) TADM12_1. Lesson: General Preparation for Installation. Install SAP Front-End Software. Figure 14: Install SAP Front-End Software. Ensure that the front-end software is installed on at least one host in your system environment. To simplify the administration of your SAP system, it is recommended that you do this on the central instance host. For more information on installing the front-end software, refer to the corresponding unit of this class and the separate documentation: • •. SAP Front-End Installation Guide (English version) SAP Frontend-Installationsleitfaden (German version). Make DVDs available The master guide lists the DVDs you need for the installation in the Media Information section. The installation guide lists the DVDs you need for the installation in the Preparation chapter. Download all required DVDs and make them assessable to the host, the SAP system should be installed on.. 2012. © 2011 SAP AG. All rights reserved.. 37.

(62) Unit 2: Preparing an Installation. TADM12_1. JRE/JDK Installation SAPinst is a Java based tool and thus needs a Java Runtime Environment (JRE) to be installed. If you will later on install Java based SAP software on the same host, make sure to install the right version, if possible. For example SAP NetWeaver AS Java 7.02 needs the full J2SE SDK (Java 2 Standard Edition Software Development Kit), also called JDK (Java Development Kit). In this JDK also the JRE is contained, which also works for SAPinst. Always check the Product Availability Matrix on SAP Service Marketplace, Quick Link pam for the supported version of the JDK. In addition following SAP Note 723909 - Java VM settings for J2EE 6.40/7.0 provides helpful information. The steps are described in detail in the following figures on the example of Windows 2003 Server x64 Edition. Note: For UNIX operating systems it is also mandatory to install the JRE and or JDK. The details on those installations are not included here. Note: If you are installing your SAP system on an Oracle database, be aware that the Oracle installer also installs an JRE on the database host. The location of this JRE is added automatically to the environment variable PATH.. 38. © 2011 SAP AG. All rights reserved.. 2012.

(63) TADM12_1. Lesson: General Preparation for Installation. Figure 15: Windows: JDK Installation. Hint: When you specify the Java installation directory, make sure that: • •. There are no spaces in the directory path The directory only contains the version number and NOT the build number or patch level. This is recommended because many SAP and non-SAP tools use the path to the Java installation directory in start scripts. If you upgrade from e.g. j2sdk1.4.2_15 to j2sdk1.4.2_17 and leave the default settings, the directory name changes, but the scripts don't get changed.. Because SAPinst is a Java-based tool, a Java Runtime Environment (JRE) must be installed for SAPinst. Normally the JRE coming with the JDK is sufficient for SAPinst. Refer to the relevant installation guide for details. A full JDK is only needed when you install AS Java based SAP systems. For AS ABAP based SAP system only an JRE for SAPinst is needed.. 2012. © 2011 SAP AG. All rights reserved.. 39.

(64) Unit 2: Preparing an Installation. TADM12_1. If you are not certain that the JDK/JRE is installed already, you can check under Start → Settings → Control Panel → Add/Remove Programs. The software is present if there is an entry for “Java ...”. Hint: Deactivate the automatic update feature of the Java installation. Otherwise you may upgrade your JDK unwillingly to a non-supported version. After installation of the JRE/JDK you have to set an environment variable so that SAPinst and SAP NetWeaver AS Java can locate the installed JRE/JDK. In case you need to install more than one JDK version, you can set different environment variables for SAPinst and SAP NetWeaver AS Java. 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. As SAP NetWeaver AS Java also needs the JAVA_HOME environment variable to be set, you can simply add the JAVA_HOME variable if SAPinst and SAP NetWeaver AS Java need the same JDK version. Setting the environment variable in Windows To set the JAVA_HOME environment variable in Windows, choose Start → Settings → Control Panel → System and switch to the Advanced tab. Select Environment Variables. Make sure the JAVA_HOME system variable is set to the Java home directory, which is the directory in which the JDK is installed. If it is not set, create a new variable. The procedure to create a new variable is: • • • • •. 40. Below section System variables choose New. Set Variable name to JAVA_HOME. Set Variable value to the Java home directory, for example G:\j2sdk Choose OK. The JAVA_HOME variable is now present in the system variables list.. © 2011 SAP AG. All rights reserved.. 2012.

(65) TADM12_1. Lesson: General Preparation for Installation. Figure 16: Windows: Environment Variable JAVA_HOME. If necessary repeat the steps above for the SAPINST_JRE_HOME variable to point to an alternative JRE. Note: The same environment variables need to be set for UNIX operating systems. Hint: If you need additional JRE or JDK installations, because additional software running on the same host require this, you can also set the environment variables to be user specific.. Download JCE Policy Files As of SAP NetWeaver 7.0 strong encryption is mandatory for SAP NetWeaver AS Java and for all usage types that are deployed on it. You need to obtain the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 1.4.2. beforehand so that they can be installed by SAPinst. Download the JCE policy files for the SUN JDK at http://java.sun.com/j2se/1.4.2/download.html. SAPinst installs the JCE policy files during the installation process.. 2012. © 2011 SAP AG. All rights reserved.. 41.

(66) Unit 2: Preparing an Installation. TADM12_1. Figure 17: JCE Policy Files (SUN). This file from SUN can also be used for HP-UX Java SDK/JDK. For the IBM JDK you get the JCE policy files from IBM at http://www6.software.ibm.com/dl/jcesdk/jcesdk-p.. Prerequisites Check You should check the hardware and software requirements for your operating system (OS) and the SAP instances using the Prerequisite Checker tool. The Prerequisite Checker provides information about the requirements that you need to meet before you start the installation. For example, it checks the requirements for the different installation services. Before using this tool consult SAP Note 855498 - Installation Prerequisite Checker to get the latest update for the prerequisite checker. Download the attachment fitting to your installation, here PREREQUISITE_CHECK_DATA_700.SAR, and save it on the host. Extract the SAR file using sapcar. When executing the check, reference the extracted XML file.. 42. © 2011 SAP AG. All rights reserved.. 2012.

(67) TADM12_1. Lesson: General Preparation for Installation. Figure 18: Prerequisites Check 1/5. On the welcome screen, choose: Enhancement Package 5 for SAP ERP 6.0 → Software Life-Cycle Options → Additional Preparation Options → Prerequisites Check.. 2012. © 2011 SAP AG. All rights reserved.. 43.

(68) Unit 2: Preparing an Installation. TADM12_1. Figure 19: Prerequisites Check 2/5. 44. © 2011 SAP AG. All rights reserved.. 2012.

(69) TADM12_1. Lesson: General Preparation for Installation. Figure 20: Prerequisites Check 3/5. 2012. © 2011 SAP AG. All rights reserved.. 45.

(70) Unit 2: Preparing an Installation. TADM12_1. Figure 21: Prerequisites Check 4/5. 46. © 2011 SAP AG. All rights reserved.. 2012.

(71) TADM12_1. Lesson: General Preparation for Installation. Figure 22: Prerequisites Check 5/5. In addition to using the Prerequisite Checker you also have to check the requirements checklists for the installed services mentioned in the installation guide.. 2012. © 2011 SAP AG. All rights reserved.. 47.

(72) Unit 2: Preparing an Installation. TADM12_1. Generate SAP Solution Manager Key. Figure 23: Generate SAP Solution Manager Key. When installing an SAP system - other than SAP Solution Manager itself - you will need a key generated by the SAP Solution Manager. Without this key a successful installation is not possible. SAP Note 811923 - Generating the SAP Solution Manager key describes how to generate the key. The funny thing is: instead of entering the System Number you have to enter the central instance number you plan to install. And instead of entering the Message Server you have to enter the name of the host, the message server should run on. ;-). 48. © 2011 SAP AG. All rights reserved.. 2012.

(73) TADM12_1. Lesson: General Preparation for Installation. Exercise 1: Prepare the Installation Part 1/2 Exercise Objectives After completing this exercise, you will be able to: • Install the JDK • Execute the Prerequisite Checker. Business Example You want to prepare the installation of an SAP system.. Task 1: Check DVDs Check if the installation DVDs are available. 1.. To log on to your host, use the host name, the user name, and the password given to you by your instructor. Note: Use a Terminal Service Client to connect to your host. You find the installation DVDs at G:\ADM110_col72.. Task 2: JDK Installation Prepare the installation by installing the JDK and setting the JAVA_HOME variable. 1.. Install the JDK (j2sdk-1_4_2_<patch level>-windows-amd64.exe) to G:\j2sdk. You should find the installation file in folder G:\ADM110_col72 of your host.. 2.. Set the JAVA_HOME environment variable to the just installed Java home directory G:\j2sdk.. Task 3: JCE Policy Files Check that the JCE Policy Files are on your host. 1.. Check that the JCE Policy Files are on your host. They should be available in folder G:\j2sdk.. Task 4: Prerequisites Check Use the Prerequisite Checker to check the hardware and software requirements. 1.. Start SAPinst. Continued on next page. 2012. © 2011 SAP AG. All rights reserved.. 49.

(74) Unit 2: Preparing an Installation. TADM12_1. Reference the PREREQUISITE_CHECK_DATA.XML file at G:\ADM110_col72\SAP_Note_0855498. 50. © 2011 SAP AG. All rights reserved.. 2012.

(75) TADM12_1. Lesson: General Preparation for Installation. Solution 1: Prepare the Installation Part 1/2 Task 1: Check DVDs Check if the installation DVDs are available. 1.. To log on to your host, use the host name, the user name, and the password given to you by your instructor. Note: Use a Terminal Service Client to connect to your host. You find the installation DVDs at G:\ADM110_col72. a). Follow the exercise description.. Task 2: JDK Installation Prepare the installation by installing the JDK and setting the JAVA_HOME variable. 1.. Install the JDK (j2sdk-1_4_2_<patch level>-windows-amd64.exe) to G:\j2sdk. You should find the installation file in folder G:\ADM110_col72 of your host. a). 2.. Double click the file j2sdk-1_4_2_<patch level>-windows-amd64.exe. Follow the figures Windows: JDK Installation from the course document and choose G:\j2sdk as the installation directory.. Set the JAVA_HOME environment variable to the just installed Java home directory G:\j2sdk. a). Choose Start → Settings → Control Panel → System and switch to the Advanced tab. Select Environment Variables. Follow the figures Windows: Environment Variable JAVA_HOME.. Task 3: JCE Policy Files Check that the JCE Policy Files are on your host. 1.. Check that the JCE Policy Files are on your host. They should be available in folder G:\j2sdk. a). Follow the step description.. Task 4: Prerequisites Check Use the Prerequisite Checker to check the hardware and software requirements. 1.. Start SAPinst. Continued on next page. 2012. © 2011 SAP AG. All rights reserved.. 51.

(76) Unit 2: Preparing an Installation. TADM12_1. Reference the PREREQUISITE_CHECK_DATA.XML file at G:\ADM110_col72\SAP_Note_0855498 a). 52. Follow the instruction from the course document, section Prerequisites Check.. © 2011 SAP AG. All rights reserved.. 2012.

(77) TADM12_1. Lesson: General Preparation for Installation. Lesson Summary You should now be able to: • Perform the general preparation steps needed to install an SAP system. 2012. © 2011 SAP AG. All rights reserved.. 53.

(78) Unit 2: Preparing an Installation. TADM12_1. Lesson: Additional Preparation for Installation on Windows Lesson Overview This lesson discusses the preparation steps that you need to perform in addition to the general preparation steps to install an SAP system on a Windows operating system.. Lesson Objectives After completing this lesson, you will be able to: •. Perform the necessary preparation steps to install an SAP system on Windows. Business Example You want to perform the necessary preparation steps to install an SAP system on Windows.. Preparing for Installation in Windows When installing an SAP system on a Windows operating system you have to do the following Windows specific preparations: • • •. 54. Check Windows file system Reduce size of file cache Prepare installation user. © 2011 SAP AG. All rights reserved.. 2012.

No results found