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
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
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.
Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
© 2011 SAP AG. All rights reserved.
iii
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
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
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
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
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
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
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
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
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
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 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
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
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”/ set during installation)
d.
Set DB Overwrite Mode using Database Studio:
© SAP AG 2012
TADM12_1
7
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Unit Summary
23
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
24
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
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
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 :\IM_WINDOWS_ Caution: Do not use user adm to do installations.
26
© 2011 SAP AG. All rights reserved.
2012
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
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
TADM12_1
Lesson: Introducing SAPinst
SAPINST_DIALOG_PORT= GUISERVER_DIALOG_PORT= GUISERVER_HTTP_PORT= 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
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 UNIX: ./startInstGui.sh -host
. 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
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) /.stdgui (UNIX) If SAPinst GUI does not start, check the file sdtstart.err in the current %userprofile% (Windows) or (UNIX) directory.
2012
© 2011 SAP AG. All rights reserved.
31
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
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
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
TADM12_1
Lesson: General Preparation for Installation
Figure 12: Download Installation DVDs
2012
© 2011 SAP AG. All rights reserved.
35
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
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
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
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
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
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
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
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
Unit 2: Preparing an Installation
TADM12_1
Figure 19: Prerequisites Check 2/5
44
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: General Preparation for Installation
Figure 20: Prerequisites Check 3/5
2012
© 2011 SAP AG. All rights reserved.
45
Unit 2: Preparing an Installation
TADM12_1
Figure 21: Prerequisites Check 4/5
46
© 2011 SAP AG. All rights reserved.
2012
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
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
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_-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
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
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_-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_-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
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
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
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
TADM12_1
Lesson: Additional Preparation for Installation on Windows
Check Windows File System
Figure 24: Windows File System: NTFS
You must install an SAP system on an NTFS file system. Check the partition on which you plan to install the SAP system for the correct file system type: open the Windows Explorer, select G:, choose Properties and switch to the General tab to see the type of file system. Domain or local installation You can decide, if you want to install your system on the hosts locally or using a Windows domain. SAP recommends to perform a domain installation. For a domain installation SAP recommends that all SAP system and database hosts are members of a single Windows domain. This is valid for all SAP system setups, whether standalone central systems or distributed systems. In the single domain model, the SAP system and the user accounts are included in a single domain. Caution: You cannot create local users and groups on the host that is used as domain controller. Therefore, SAP does not support running an SAP instance (including the database instance) on the host where the DNS service is installed.
2012
© 2011 SAP AG. All rights reserved.
55
Unit 2: Preparing an Installation
TADM12_1
For performance and security reasons, make sure that you do not run an SAP instance (including the database instance) on the host where the domain controller is running. SAP does not support an SAP system installation on a domain controller. If you want to use the Change and Transport System (CTS) to transport objects between different SAP systems, ensure that all the SAP systems are either members of a single domain or members of different domains with a trust relationship established between them. Only SAP application and SAP database servers (no other software) should be members of the domains.
Installation User For a local installation, your installation user needs local administration rights; for a domain installation, your installation user needs domain administration rights.
Figure 25: Windows: User needs Administration Rights
For a local installation, you need an installation user who is member of the local Administrators group. To check if your user is a member of the group, choose Start → Settings → Control Panel → Administrative Tools → Computer Management and select the Local Users and Groups → Users folder. Choose your user and switch to the Member Of tab.
56
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Additional Preparation for Installation on Windows
Normally when doing a domain installation you need to be a domain administrator. Anyhow it is possible to do a domain installation with local administration rights. In this case the domain administrator has to prepare some additional things. See the installation guide for a detailed description. Caution: Do not use the user adm for the installation of the SAP system.
Reduce Size of File Cache
Figure 26: Windows: Reducing the Size of the File Cache
When the Maximize data throughput for network applications option is selected, the Windows file cache is reduced in size so that application server software, such as an SAP system, has more resources available. This also decreases the time needed for the installation, especially for the database import. To check the setting go to Start → Settings → Network Connections, right click on the active connection and choose Properties from the context menu.
2012
© 2011 SAP AG. All rights reserved.
57
Unit 2: Preparing an Installation
TADM12_1
Prepare the Transport Host The transport host has a directory structure that is used by the SAP transport system to store transport data and meta data. The transport system stores the change information, such as ABAP programs, data dictionary data, customizing data as well as SAP Support Packages from SAP Service Marketplace in files that are located in this directory structure. If you do not intend to use the directory structure of the system you are going to install, you need to prepare it on the transport host. You need to prepare one host in for the role of a transport host. This host has the function of controlling the import or export of files between the current SAP system and other SAP systems, such as a test or production system. The global transport directory \usr\sap\trans is used by the Change and Transport System (CTS). The CTS helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP systems in your SAP system landscape. •
• •
If you install the first SAP system of the system landscape, for example the development system you can use the installed file system structure on the host of the central instance of this SAP system. If the directory structure already exists, you must set up its security to allow the new SAP system to write into it. If it does not yet exist, you must create the core directory structure and a share to export it for other hosts as well as setting the security on it.
If your transport host is not the central instance host, you have to create the transport directory as follows: 1. 2. 3.
58
On the transport host, create the directory \usr\sap\trans. Grant Everyone the permission Full Control for the directory. Share the usr\sap directory on the transport host as sapmnt. This enables SAPinst to address the transport directory in the standard way as \\SAPTRANSHOST\SAPMNT\trans. Note: These permissions are only necessary during the SAPinst installation. You must remove them after you have finished the installation. After the installation, you only have to grant Full Control on this directory to the SAP__GlobalAdmin groups of all the systems that are part of your transport infrastructure. SAPinst assigns the appropriate rights with the help of an additional SAP__LocalAdmin group.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Additional Preparation for Installation on Windows
Changes to File System Structure As of release SAP NetWeaver 7.0 the structure of the Windows file system for the SAP system's kernel undergoes some minor changes. See SAP Note 919046 for details. These changes don't apply for systems running on UNIX operating systems. Note: For systems based on SAP NetWeaver AS 7.10 and higher the kernel file system structure for UNIX was adjusted, so that it is the same as for Windows.
Preparation Checklist for Installation on Windows Preparation Checklist for Installation on Windows
Figure 27: Preparation Checklist for Windows
2012
© 2011 SAP AG. All rights reserved.
59
Unit 2: Preparing an Installation
60
© 2011 SAP AG. All rights reserved.
TADM12_1
2012
TADM12_1
Lesson: Additional Preparation for Installation on Windows
Exercise 2: Prepare the Installation Part 2/2 Exercise Objectives After completing this exercise, you will be able to: • Check the Windows file system • Reduce the size of the file cache • Check the installation user
Business Example You want to prepare the installation of an SAP system.
Task 1: Check the Windows File System Check if the file system is NTFS. 1.
Check if the file system of the installation partition (G:) is NTFS.
Task 2: Installation User Check if your user has administration rights. 1.
Check if your user has administration rights.
Task 3: Reduce Size of File Cache Reduce the size of the Windows file cache. 1.
2012
Reduce the size of the Windows file cache by editing the properties of the local area connection.
© 2011 SAP AG. All rights reserved.
61
Unit 2: Preparing an Installation
TADM12_1
Solution 2: Prepare the Installation Part 2/2 Task 1: Check the Windows File System Check if the file system is NTFS. 1.
Check if the file system of the installation partition (G:) is NTFS. a)
Check if the file system of the installation partition (G:) is NTFS. Follow the directions given in the section Check Windows File System.
Task 2: Installation User Check if your user has administration rights. 1.
Check if your user has administration rights. a)
Check if your user has administration rights. Follow the directions given in section Installation User.
Task 3: Reduce Size of File Cache Reduce the size of the Windows file cache. 1.
Reduce the size of the Windows file cache by editing the properties of the local area connection. a)
Reduce the size of the Windows file cache by editing the properties of the local area connection. Follow the directions given in section Reduce Size of File Cache.
62
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Additional Preparation for Installation on Windows
Lesson Summary You should now be able to: • Perform the necessary preparation steps to install an SAP system on Windows
2012
© 2011 SAP AG. All rights reserved.
63
Unit 2: Preparing an Installation
TADM12_1
Lesson: Additional Preparation for Installation on UNIX 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 an UNIX operating system.
Lesson Objectives After completing this lesson, you will be able to: •
Perform the necessary preparation steps to install an SAP system on UNIX
Business Example You want to perform the necessary preparation steps to install an SAP system on UNIX.
Adapting Kernel Parameters For many UNIX operation system and database system combinations, you have to modify the UNIX kernel parameters. The details are given in the installation guide corresponding to your operating system.
Creating Operating System Users If you do not want SAPinst to create operating systems users, groups and services, you can optionally create them before the installation. If you want to use global accounts that are configured on a separate host, you can do this in one of the following ways:
64
•
You start SAPinst and choose Software Life-Cycle Tasks → Additional Preparation Tasks → Operating System Users and Groups.
•
You create operating system users and groups manually.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Additional Preparation for Installation on UNIX
For details which users have to be created and how, see the installation guide. Hint: If you install a distributed system and you do not use central user management (for example, NIS), and you use local operating system user accounts instead, then adm and the database operating system user must have the same password on all hosts.
NIS If you use Network Information Service (NIS), you need to distribute users over the network. SAPinst checks all required users, groups, and services on the local machine. If you manage users, groups or services network-wide in your company, we recommend that you create the user and group NIS entries before running SAPinst. SAPinst checks if the required services are available on the host and creates them if necessary. See the log messages about the service entries and adapt the network-wide (NIS) entries accordingly. SAPinst checks the NIS users, groups and services using NIS commands. However, SAPinst does not change NIS configurations.
2012
© 2011 SAP AG. All rights reserved.
65
Unit 2: Preparing an Installation
TADM12_1
Setting Up File Systems
Figure 28: UNIX: Setting Up File Systems
You have to set up the file systems and/or raw devices for the SAP system and the database. You have to manually set up the file systems selected in the figure; SAPinst will do the rest during the installation process. If you do not set up any file system on your installation host, SAPinst creates all directories in the root directory /. SAPinst prompts you only for the directory during the installation. The file system starting from SCS is from the Central Services instance of an AS Java or AS ABAP+Java system. The file system ASCS only is relevant for a high availability (HA) installation of an AS ABAP or AS ABAP+Java system. For the space required by different file systems, refer to your installation guide.
66
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Additional Preparation for Installation on UNIX
The processes of creating and mounting file systems and creating raw devices for an SAP system and for different databases are described in the installation guide. Note: Depending on the database you choose, you have to set up additional file systems for the database. Note: For systems based on SAP NetWeaver AS 7.10 and higher the kernel file system structure for UNIX was adjusted, so that it is the same as for Windows. This means, that the folder .../SYS/exe/run was replaced by .../SYS/exe//. stands for nuc or uc depending if it is an non-Unicode or Unicode kernel. specifies the operating system platform, for example linuxx86_64.
Exporting and Mounting the Global Transport Directory In your SAP system landscape, a global transport directory for all SAP systems is required. •
•
If this global transport directory already exists, make sure that it is exported on the global transport directory host and mount it on the SAP system installation host. If this global transport directory does not exist, proceed as follows: – – –
2012
Create the transport directory (either on the central instance host or on a file server). Export it on the global transport directory host. If you did not create the transport directory on your SAP instance installation host, mount it there.
© 2011 SAP AG. All rights reserved.
67
Unit 2: Preparing an Installation
TADM12_1
Preparation Checklist for Installation on UNIX
Figure 29: Preparation Checklist for Installation on UNIX
68
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Additional Preparation for Installation on UNIX
Lesson Summary You should now be able to: • Perform the necessary preparation steps to install an SAP system on UNIX
2012
© 2011 SAP AG. All rights reserved.
69
Unit Summary
TADM12_1
Unit Summary You should now 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
70
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Test Your Knowledge
Test Your Knowledge 1.
Before installing an SAP system, you should ensure that the front-end software is installed on in your system environment. Fill in the blanks to complete the sentence.
2.
What are the necessary preparation steps to do a SAP ECC 6.0 installation? Choose the correct answer(s).
□ □ □ □ 3.
2012
A B C D
Do a Prerequistes Check? Install the right JDK? Install and configure SAPinst? Rename the host to SAP?
Name at least one SAP file system that you need to set up manually for installations on UNIX operating systems.
© 2011 SAP AG. All rights reserved.
71
Test Your Knowledge
TADM12_1
Answers 1.
Before installing an SAP system, you should ensure that the front-end software is installed on at least one host computer in your system environment. Answer: at least one host computer
2.
What are the necessary preparation steps to do a SAP ECC 6.0 installation? Answer: A, B SAPinst installs itself on execution. The host does not need to be renamed.
3.
Name at least one SAP file system that you need to set up manually for installations on UNIX operating systems. Answer: At least these file systems need to be set up manually: /usr/sap, /.
72
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
73
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
74
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit 3 Installing SAP Solution Manager Unit Overview In this unit you install an SAP Solution Manager system with a primary application server and a secondary application server.
Unit Objectives After completing this unit, you will be able to: • •
Install an SAP Solution Manager system Install a secondary application server
Unit Contents Lesson: Installation of SAP Solution Manager ................................... 76 Exercise 3: Install an SAP Solution Manager 7.01 System ................ 87 Lesson: Installation of a Secondary Application Server ........................ 90 Exercise 4: Installation of a Secondary Application Server ................ 95
2012
© 2011 SAP AG. All rights reserved.
75
Unit 3: Installing SAP Solution Manager
TADM12_1
Lesson: Installation of SAP Solution Manager Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •
Install an SAP Solution Manager system
Business Example You want to install an SAP Solution Manager system.
SAP Solution Manager Installation The following figures show the installation steps for SAP Solution Manager 7.01 on an Windows operating system and with a MaxDB database. Start the installation by double clicking on sapinst.exe on the Solution Manager Master DVD at G:\ADM110_col72\DVDs\Solution_Manager_7.0_EHP1\Solution_Manager_7.0_EHP1_Installation_Master\IM_WINDOWS_X86_64.
76
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP Solution Manager
Figure 30: SAP Solution Manager Installation 1/9
Start the installation of the SAP Solution Manager system as a central system.
2012
© 2011 SAP AG. All rights reserved.
77
Unit 3: Installing SAP Solution Manager
TADM12_1
Figure 31: SAP Solution Manager Installation 2/9
Choose Parameter Mode Typical to reduce the number of questions asked by SAPinst. You can still change the defaults afterwards, shortly before starting the actual installation. Provide the requested DVD and the JCE Policy Files. All needed DVDs and files can be found on files system level of the installation host at G:\ADM110_col72.
78
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP Solution Manager
Figure 32: SAP Solution Manager Installation 3/9
Choose S## as SAP system ID, G: as installation drive, Master## as master password and S## as database ID - whereby ## stands for your two digit group number.
2012
© 2011 SAP AG. All rights reserved.
79
Unit 3: Installing SAP Solution Manager
TADM12_1
Figure 33: SAP Solution Manager Installation 4/9
Provide the requested DVDs. All needed DVDs and files can be found on files system level of the installation host at G:\ADM110_col72.
80
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP Solution Manager
Figure 34: SAP Solution Manager Installation 5/9
Provide the requested DVDs. All needed DVDs and files can be found on files system level of the installation host at G:\ADM110_col72.
2012
© 2011 SAP AG. All rights reserved.
81
Unit 3: Installing SAP Solution Manager
TADM12_1
Figure 35: SAP Solution Manager Installation 6/9
Configure a local SLD, choose mynamespace as object server name and Master## as passwords. Whereby you don't have to enter Master## because it is taken by default from the master password selected before.
82
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP Solution Manager
Figure 36: SAP Solution Manager Installation 7/9
Change the values as shown on the slide. Hint: Double click into the field and change the drive letter directly. That's faster than browsing. Caution: For productive installations data files and log files should be installed on separate drives! Start the installation of your SAP Solution Manager system.
2012
© 2011 SAP AG. All rights reserved.
83
Unit 3: Installing SAP Solution Manager
TADM12_1
Figure 37: SAP Solution Manager Installation 8/9
Congratulations! You have installed your SAP Solution Manager system. But...:
84
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP Solution Manager
Figure 38: SAP Solution Manager Installation 9/9
Caution: Due to a wrong set default you have to change the profile parameter PHYS_MEMSIZE. Change it immediately after the installation in the instance profile of the central instance of the SAP Solution manager system. Reduce the value of the parameter as shown on the slide. The instance profile can be found at G:\usr\sap\\SYS\profile. The instance profile is named _DVEBMGS_, for example S00_DVEBMGS00_twdf0000. Afterwards you have to restart the central instance of your SAP Solution Manager system, of course. In addition to the SAP Solution Manager system a Solution Manager Diagnostic (SMD) agent with SAP SID SMD is installed. In the context of this course we don't need it and ignore it. Hint: For more details about SAP Solution Manager see SAP Service Marketplace, Quick Link solutionmanager and SAP Service Marketplace, Quick Link solman-mopz.
2012
© 2011 SAP AG. All rights reserved.
85
Unit 3: Installing SAP Solution Manager
86
© 2011 SAP AG. All rights reserved.
TADM12_1
2012
TADM12_1
Lesson: Installation of SAP Solution Manager
Exercise 3: Install an SAP Solution Manager 7.01 System Exercise Objectives After completing this exercise, you will be able to: • install an SAP Solution Manager 7.01 system
Business Example You want to install an SAP Solution Manager 7.01 system.
Task: Install an SAP Solution Manager 7.01 System Install an SAP Solution Manager 7.01 system on the platform combination Microsoft Windows and MaxDB. 1.
2012
Install an SAP Solution Manager 7.01 system.
© 2011 SAP AG. All rights reserved.
87
Unit 3: Installing SAP Solution Manager
TADM12_1
Solution 3: Install an SAP Solution Manager 7.01 System Task: Install an SAP Solution Manager 7.01 System Install an SAP Solution Manager 7.01 system on the platform combination Microsoft Windows and MaxDB. 1.
Install an SAP Solution Manager 7.01 system. a)
Perform the installation as described in the lesson Installation of SAP Solution Manager. Hint: Don't forget to reduce the value of the profile parameter PHYS_MEMSIZE!
88
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP Solution Manager
Lesson Summary You should now be able to: • Install an SAP Solution Manager system
2012
© 2011 SAP AG. All rights reserved.
89
Unit 3: Installing SAP Solution Manager
TADM12_1
Lesson: Installation of a Secondary Application Server Lesson Overview This lesson describes how to install a secondary application server (AS ABAP, AS Java or AS ABAP+Java).
Lesson Objectives After completing this lesson, you will be able to: •
Install a secondary application server
Business Example You want to install a secondary application server
Installing a Dialog Instance You have already installed an SAP system with a central instance, also called primary application server. For performance reasons you now want to install an additional dialog instance, also called secondary application server. Hint: In case of an AS ABAP based SAP system, all dialog instances will be installed as AS ABAP instances, in case of an AS Java based SAP system as AS Java instances, in case of an AS ABAP+Java based SAP system as AS ABAP+Java instances. The installation procedure is almost the same in all three cases. It only differs in the amount of phases and the time needed for the installation: an AS ABAP based dialog instance can be installed in a few minutes, the other types take seceral times as long. Note: After installing the SAP Solution Manager system as a central system, we want to install an additional dialog instance for the SAP Solution Manager system. Start the installation program SAPinst from the SAP Solution Manager Installation Master DVD.
90
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of a Secondary Application Server
Figure 39: Dialog Instance Installation 1/4
Navigate to SAP Solution Manager 7.0 EHP1 → Software Life-Cycle Options → Application Server → MaxDB → Dialog Instance. Choose the Parameter Mode Typical.
2012
© 2011 SAP AG. All rights reserved.
91
Unit 3: Installing SAP Solution Manager
TADM12_1
Figure 40: Dialog Instance Installation 2/4
Select the profile directory of the SAP Solution Manager system, you installed. Provide the master password you have chosen for the SAP Solution Manager system. It should be Master##, whereby ## is your two digit group number. Provide the requested DVDs.
92
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of a Secondary Application Server
Figure 41: Dialog Instance Installation 3/4
Change the instance number as shown on the slide and start the installation process. Congratulations! You have just installed a dialog instance.
2012
© 2011 SAP AG. All rights reserved.
93
Unit 3: Installing SAP Solution Manager
TADM12_1
Figure 42: Dialog Instance Installation 4/4
Caution: Due to a wrong set default you have to change the profile parameter PHYS_MEMSIZE. Change it immediately after the installation in the instance profile of the installed instance. Reduce the value of the parameter as shown on the slide. The instance profile can be found at G:\usr\sap\\SYS\profile. The instance profile is named _D_, for example S00_D01_twdf0000. Afterwards you have to restart the instance, of course. For more information on installing additional dialog instances, see the installation guides on the SAP Service Marketplace, Quick Link instguides.
94
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of a Secondary Application Server
Exercise 4: Installation of a Secondary Application Server Exercise Objectives After completing this exercise, you will be able to: • install a secondary application server
Business Example You want to install a secondary application server.
Task: Install a Secondary Application Server Install a secondary application server for your previously installed SAP Solution Manager system. 1.
2012
Install a secondary application server for your previously installed SAP Solution Manager system.
© 2011 SAP AG. All rights reserved.
95
Unit 3: Installing SAP Solution Manager
TADM12_1
Solution 4: Installation of a Secondary Application Server Task: Install a Secondary Application Server Install a secondary application server for your previously installed SAP Solution Manager system. 1.
Install a secondary application server for your previously installed SAP Solution Manager system. a)
Perform the installation as described in the lesson Installation of a Secondary Application Server. Hint: Don't forget to reduce the value of the profile parameter PHYS_MEMSIZE!
96
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of a Secondary Application Server
Lesson Summary You should now be able to: • Install a secondary application server
2012
© 2011 SAP AG. All rights reserved.
97
Unit Summary
TADM12_1
Unit Summary You should now be able to: • Install an SAP Solution Manager system • Install a secondary application server
98
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Test Your Knowledge
Test Your Knowledge 1.
Which types of dialog instances can be installed to an SAP system, depending on the SAP system type? Choose the correct answer(s).
□ □ □
2012
A B C
AS ABAP dialog instance Central services dialog instance AS Java dialog instance
© 2011 SAP AG. All rights reserved.
99
Test Your Knowledge
TADM12_1
Answers 1.
Which types of dialog instances can be installed to an SAP system, depending on the SAP system type? Answer: A, C There is no central services dialog instance.
100
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
101
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
102
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit 4 Planning an Installation Unit Overview This unit explains how to plan the installation of an SAP system.
Unit Objectives After completing this unit, you will be able to: • •
List some planning topics for the installation of an SAP system List some technical requirements for an SAP system
Unit Contents Lesson: Planning the Installation ................................................. 104
2012
© 2011 SAP AG. All rights reserved.
103
Unit 4: Planning an Installation
TADM12_1
Lesson: Planning the Installation Lesson Overview This lesson explains the installation planning, such as hardware sizing and technical requirements, for an SAP system. Before starting the installation of an SAP system, you need to answer several questions. Typically this phase starts several weeks (sometimes even months) before the actual installation work takes place.
Lesson Objectives After completing this lesson, you will be able to: • •
List some planning topics for the installation of an SAP system List some technical requirements for an SAP system
Business Example You want to plan the installation of an SAP system.
Planning Overview SAP supports you through the whole software life cycle. From planning and implementation to operations and maintenance. The SAP Service Marketplace (http://service.sap.com) provides access to various tools and services throughout the software life cycle.
104
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Planning the Installation
Figure 43: SAP Service Marketplace - Quick Links
2012
© 2011 SAP AG. All rights reserved.
105
Unit 4: Planning an Installation
TADM12_1
Hardware Sizing
Figure 44: Sizing Your System
Consider the following potential issues: •
• •
Hardware that is sized too small creates additional costs by causing bad performance of the SAP system. High response times lead to inefficient productive operation. Adequate hardware prevents performance losses and avoids unnecessary hardware costs. Hardware sized too large means you invested too much money to reach your goal of good performance. Hint: When sizing your hardware, consider the future development of load on the SAP system!
106
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Planning the Installation
Figure 45: Sizing is an Ongoing Process
Sizing plays a role very early in the planning of your SAP system landscape. It determines the hardware resources needed for your SAP system. The resources needed are influenced by several factors, such as: • • • • • • • • • •
2012
Number of concurrent users in the system and the activity levels of users Your company's goals for the average dialog answer time are 1.5 seconds OK or less than 0.5 second required? The amount of high availability (HA) needed; full-blown HA solutions may cost a fortune Type of system (SAP ECC, SAP BW, SAP CRM Server, and so on) Functions used in the SAP system, such as SAP ECC: lean (HR and FI) or complex (PP) Release of system (SAP R/3 4.6C, SAP R/3 4.7, SAP ECC 6.0, SAP ECC 6.05, and so on) Type of operating system (Linux, HP-UX, Solaris, AIX, Windows, and so on) Type of database used (MaxDB, DB2 UDB, Microsoft SQL Server, Oracle, and so on) Type of access to the system (LAN, WAN, SAP GUI type, and so on) Preferred backup concept (for example, online backup parallel to productive use requires more hardware)
© 2011 SAP AG. All rights reserved.
107
Unit 4: Planning an Installation
TADM12_1
If one or more of the these factors are subject to change, a new sizing or hardware improvement might become necessary. If you perform a upgrade from 4.6C to SAP ECC 6.05 you should read the delta hardware requirements. In general, you can say that a new release will have additional hardware requirements. Always check the documentation and look at the SAP Service Marketplace, Quick Link sizing. From there, choose Sizing Guidelines → Solutions & Platform). Unicode influences the following factors: •
Load of applications on hardware (CPU & RAM)
•
– See SAP Service Marketplace, Quick Link unicode – See SAP Service Marketplace, Quick Link performance – Result: up to +35% CPU, around +50% RAM Size of database – –
•
See SAP Service Marketplace, Quick Link unicode The result depends on the usage of Unicode representation - UTF-8 (+10%) or UTF-16 (+30% to +60%). Performance of the database
–
Ask the database vendor for the performance results of databases using Unicode.
Unicode systems use between 1 and 4 bytes of space to store single characters, based on the character and its Unicode representation. As a result, in a simple estimate, the resources of the system could be doubled to be prepared for worst-case scenario. In reality, the load on the CPU caused by the applications, in this case, the SAP software, increases by around 35%. The load on the RAM, again caused by application software and not database software, increases by about 50%. The size of the database of Unicode systems, compared to non-Unicode systems, depends largely on the type of Unicode representation chosen. UTF-16 (+30% to 60%) requires more space than UTF-8 (+10%). The performance of the database system is also affected. For performance data on the database systems under Unicode, contact your database manufacturer.
108
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Planning the Installation
Distribution Among Hardware
Figure 46: Distribution among hardware
You can distribute SAP software in several ways on the available hardware. The result of the sizing may also influence this decision because the distribution of the software can affect system performance. Some examples and considerations follow: Central system: The database and the only application server (the central instance) are installed on the same host. This setup is useful for smaller SAP systems where one host is able to offer all the hardware resources needed for the SAP system. Distributed System: In this scenario, additional application servers (dialog instances) are installed on additional hosts. There are many different options possible: • • • •
database and central instance on one host, all additional instances on separate hosts database, central instance, dialog instances on different hosts database on separate host, central instance and one dialog instance on separate host, all additional dialog instances on separate hosts ...
If you decide to install the database on a separate host interferences from the SAP instance on database performance are excluded.
2012
© 2011 SAP AG. All rights reserved.
109
Unit 4: Planning an Installation
TADM12_1
If you decide to install a central system and a need arises for additional SAP system users, an additional dialog instance is a possible solution. A dialog instance may host as many users as their corresponding hardware allows - as long as there are not more than 100 dialog work processes necessary. If you need more than 100 dialog work processes, you can install more than one dialog instances on the same host. SAP systems may have many dialog instances. Productive systems with more than 20 dialog instances exist. Gateway instance (not shown): Optionally, a gateway instance can be set up to offer powerful communication performance for SAP systems that exchange data with external systems with a high load. Note: As a very rough rule of thumb, you can estimate for an SAP ECC system: one dialog work process can handle 10 high load parallel users, one dispatcher can handle 100 dialog work processes -> 1000 high load parallel users per instance, this equals maybe several 1000 normal parallel users per instance, and as many named users as you like per instance.
Usage Type Dependencies, Restrictions and Configuration Activities Usage types for SAP NetWeaver 7.02 can be used standalone or sometimes have to be combined. Nevertheless there are some restrictions in SAP systems with multiple usage types.
Usage type dependencies Usage type AS ABAP and AS Java should not be combined in one SAP system (exceptions: SAP PI and SAP Solution Manager). Usage type EP requires usage type AS Java as a prerequisite. Optionally, usage type EP can be combined with other usage types in one system. Usage type EPC is a prerequisite for usage type EP and BI Java. Usage type BI requires usage type AS ABAP as a prerequisite in the same system. Usage type BI Java requires usage type AS Java and EPC as prerequisites in the same system. Usage type DI requires AS Java as a prerequisite in the same system. Usage type MI requires usage type AS Java as a prerequisite in the same system.
110
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Planning the Installation
Usage type PI requires usage types AS ABAP and AS Java as prerequisites in the same system. Hint: SAP recommends that you have a dedicated SAP PI system. For SAP PI, it should be that no other SAP system in your system landscape has a higher release than the SAP PI system.
Configuration of SAP Systems with Usage Types The information about the required configuration activities for SAP systems with usage types are described in the corresponding installation guide. Additionally for certain AS Java based usage types, configuration tasks exist that can be applied by the Configuration Wizard (formerly known as Central Technical Configuration – Template Installer (CTC)) after the installation.
Network Requirements Technical Requirements A well-designed technical infrastructure ensures the lowest cost of ownership and improves the system's: • • • • •
Performance Functionality Availability Scalability Security
Find more information at SAP Service Marketplace, Quick Link instguides. The technical infrastructure describes the technical setup of an AS ABAP based SAP system. The technical setup includes the network layout, the server layout, the disk layout of the database, the type of computer interface used and many more details. The technical infrastructure influences the listed technical areas.
2012
© 2011 SAP AG. All rights reserved.
111
Unit 4: Planning an Installation
TADM12_1
Figure 47: Network: External Ports Used by AS ABAP based SAP Systems
As shown in the figure, AS ABAP based SAP systems use several different ports for external communication. All these ports should be secured by some means, such as firewalls, routers, and SAProuter, to ensure the SAP system's security. In addition, SAP systems use several internal connections to communicate with the database. The number of connections and the ports used depend on the type of database employed. The figure shows only the AS ABAP based SAP system ports. For AS Java based SAP systems, the ports 50000 and higher are used. For more information about used ports in SAP environment, go to SAP Service Marketplace, Quick Link security, Security in Detail → Infrastructure Security → TCP/IP Ports Used by SAP Applications. For more information about Infrastructure Security, go to SAP Service Marketplace, Quick Link security, Security in Detail → Infrastructure Security .
112
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Planning the Installation
Figure 48: Network: Load Caused by SAP System Communication
The bandwidth needed depends on the following parameters: • • • • •
Type of GUI used (BEx for SAP BW, SAP GUI for HTML, SAP GUI for Windows, and so on) Type of application (within SAP ECC: FI, HR, SD, and so on) Type of SAP system used (SAP ECC, SAP CRM, and so on) Low-speed connection flag used (SAP Note 161053) Other applications on the front end (office products) using the same connection
For more information, go to SAP Service Marketplace, Quick Link sizing. From there, choose Sizing Guidelines → Solutions & Platform. From there, you can download the document, Frontend Network Requirements for SAP Solutions. The load between the application layer and the database layer is considerable. As a result, SAP recommends offering a bandwidth of at least 100 megabits per second for this communication. It is usually not possible to separate the database by more than the LAN width from the application layer. For more information on network layout for SAP servers, read SAP Note 21151 and read the document, Network Integration of SAP Servers.
2012
© 2011 SAP AG. All rights reserved.
113
Unit 4: Planning an Installation
TADM12_1
Database Requirements Databases of SAP systems hold different types of data: • •
Business data (master data, transaction data, and so on) and corresponding index data Logging data for the database (needed for recovery)
Databases of SAP systems are usually stored on disks combined with some RAID level (usually 1 or 5). Databases used for SAP systems can hold up to several terabytes of business data. Because practically you are unable to restore a large database, you have to ensure that data loss is avoided under almost all circumstances. The disk layout for databases used for SAP systems affects not only SAP system performance, but also reliability and availability. To ensure the maximum availability of your SAP system, you have to take several scenario into account: • • • • • •
Disk failure RAID controller failure Network card failure Network failure Power supply failure Massive environmental damages (fire, flood, earthquake, and so on)
For more information on the these issues, go to SAP Developer Network, at irj/sdn/ha.
114
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Planning the Installation
Figure 49: Recommendations about the Database Disk Layout
Using the configuration shown in the figure, you achieve an optimum of the factors hardware costs, availability, and performance. If costs are not a factor, higher-performing configurations are possible. For these options, see SAP Developer Network, at irj/sdn/ha and contact your hardware, operating system, and/or database vendor. You should not store the historical log files of your database on any of the arrays listed in the figure; instead, you should save the historical log files to tape or any other suitable location twice before deleting them. Historical log files are referred to as Offline Redo Log Files by Oracle.
2012
© 2011 SAP AG. All rights reserved.
115
Unit 4: Planning an Installation
TADM12_1
Rules concerning the SAP system ID (): • •
The SAP system ID ( or ) and database system ID () must be unique. The SAP system ID must consist of three alphanumeric characters. Only uppercase letters are allowed. The first character must be a letter, subsequent characters may be digits. Hint: If you use Oracle as a database management system, you should be aware that you can choose the ID of the database schema as well. Please refer to SAP Note 355771 - Oracle: Explanation of the new tablespace layout and SAP Note 617444 - Separate SCHEMA ID for database schema and tablespace name.
Database management systems can host multiple databases (exception: when MCOD is used). Note: The set of reserved names may differ between different database and operating system combinations. Database Users for SAP Systems; more than one might be needed Database
Schema User
Other users
SAP MaxDB
sap
control, superdba
Oracle
SAPSYSTEM, SYS
MS SQL Server
SAP
sa, adm, SAPService
DB2 UDB
sap
db2
DB2 zOS
sap
also see installation guide
DB2 i (Series)
sap
OFR and see installation guide
Hint: The schema user for AS Java based installations is sapdb. Caution: Read the installation guide and related SAP Notes carefully. There are critical differences in naming conventions. For example, for Microsoft SQL Server, the user adm must be named using lower-case characters , such as tstadm, while the user SAPService must be named using upper-case characters , such as SAPServiceTST.
116
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Planning the Installation
When higher security settings are used on iSeries computers, password entries become case sensitive. SAP Note 495433 explains that the default password, using higher security settings, must be entered as SAPOFR.
SAP Solution Manager The SAP Solution Manager supports you throughout the entire life cycle of your SAP solutions, from the business blueprint to the configuration to production processing. It provides central access to tools, methods and preconfigured contents which you can use during evaluation, implementation and operational processing of your SAP systems.
Figure 50: SAP Solution Manager
The SAP Solution Manager provides central access to all tools, methods, documents and other data required in the implementation environment. You can use implementation contents, delivered with the SAP Solution Manager and regularly updated, and adjust it to your requirements. Make sure you have access to a SAP Solution Manager system, so that you can generate a key for the installation of a new SAP system.
2012
© 2011 SAP AG. All rights reserved.
117
Unit 4: Planning an Installation
TADM12_1
Production Client Considerations A client is a self-contained business unit in an SAP system with separate master records. In AS ABAP based SAP systems SAPinst creates three clients during installation, client 000, client 001, and client 066. As of SAP NetWeaver 7.0 you can install an SAP PI and SAP Solution Manager system (AS ABAP+Java based) in one installation run. The AS Java is configured by default against AS ABAP client 001. You can choose one of the following methods to set up your new production client: Client 000 is for special administrative purposes (setting up TMS, language import, applying SAP Support Packages, performing SAP system upgrades) and client 000 holds the default SAP customizing. You should not change client 000. Client 001 is meant to be your productive client. If you don't want to use client 001 as your productive client, you can delete client 001. Client 066 is the early watch client. It is used for access to the SAP system, for example, if a performance analysis should be performed. Client 066 has the advantage, that it does not contain any kind of business data. So - for security reasons - you can provide access without the risk of somebody reading your data.
System Landscape Directory (SLD) The System Landscape Directory (SLD) of SAP NetWeaver serves as a central information repository for your SAP system landscape. An SAP system landscape consists of a number of hardware and software components that depend on each other with regard to installation, software updates, and demands on interfaces. The SLD stores information about all installable and installed components of an SAP system landscape. SAP provides information about installable SAP software, dependencies and recommended scenarios and regularly publishes updates on SAP Service Marketplace. SAP software components that are installed on technical systems are registered automatically and on a regular basis in the SLD. Thus the SLD always contains up-to-date information about the installed SAP system landscape.
118
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Planning the Installation
Figure 51: System Landscape Directory
During installation you have three possibilities concerning SLD usage: • • •
Register in existing central SLD (default) Configure a local SLD No SLD destination
The recommendation is to choose Register in existing central SLD (default). The usual cases is to configure one SLD for the complete SAP system landscape.
2012
© 2011 SAP AG. All rights reserved.
119
Unit 4: Planning an Installation
TADM12_1
Figure 52: How many SLD do you need?
For the System Landscape Directory, different topology options are available (depending on your requirements), all with different pros and cons. There is no general recommendation that fits all use cases. The most straightforward scenario is the use of a single SLD. However, depending on organizational, operational, or security reasons, it is also possible to have more than one SLD distributed over the SAP system landscape. Automatic message forwarding, as well as sophisticated data export and import functions, are provided to support the operation of multiple SLDs. The easiest scenario is the central SLD. All data is collected and maintained in a single SLD. All requests are routed to this single SLD, which contains information about the whole SAP system landscape. All clients must be enabled to access the central SLD. The illustration in the lower-left section shows a hosting scenario with several separate customer SAP system landscapes. Each customer SAP system landscape incorporates its own SLD containing this customer’s SAP system landscape only. Global or widely distributed IT landscapes may require more than a central SLD. It is then expected that an SLD is locally available but that it provides more than a local view. This can be achieved by coupling multiple distributed SLDs. The following kinds of coupling between SLDs are possible: “Automatic forwarding of landscape data” or “Export and import of landscape data”.
120
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Planning the Installation
For more information, see the Planning Guide – SLD (available on SAP Developer Network SAP Developer Network, at irj/sdn/nw-sld).
2012
© 2011 SAP AG. All rights reserved.
121
Unit 4: Planning an Installation
TADM12_1
Lesson Summary You should now be able to: • List some planning topics for the installation of an SAP system • List some technical requirements for an SAP system
Related Information •
SAP Service Marketplace http://service.sap.com: Quick Links: /sizing, /performance, /unicode, /platforms, /pam, /instguides, /osdbmigration, /security
•
SAP Developer Network http://www.sdn.sap.com/irj/sdn Quick Links: /nw-sld, /ha
•
122
SAP Notes as listed in this unit
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Unit Summary
Unit Summary You should now be able to: • List some planning topics for the installation of an SAP system • List some technical requirements for an SAP system
2012
© 2011 SAP AG. All rights reserved.
123
Unit Summary
124
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Test Your Knowledge
Test Your Knowledge 1.
An SAP ECC 6.05 system does not require more hardware resources than an SAP R/3 4.6C system. Determine whether this statement is true or false.
□ □
2012
True False
© 2011 SAP AG. All rights reserved.
125
Test Your Knowledge
TADM12_1
Answers 1.
An SAP ECC 6.05 system does not require more hardware resources than an SAP R/3 4.6C system. Answer: False Apart from the additional resources required for Unicode, an SAP ECC 6.05 system in general does require more hardware resources than an SAP R/3 4.6C system.
126
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
127
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
128
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit 5 Installation of SAP ECC (AS ABAP) Unit Overview In this unit you install an SAP ECC system with a primary application server.
Unit Objectives After completing this unit, you will be able to: •
Install an SAP ECC 6.05 system
Unit Contents Lesson: Installation of SAP ECC ................................................. 130 Exercise 5: Install an SAP ECC 6.05 System .............................. 139
2012
© 2011 SAP AG. All rights reserved.
129
Unit 5: Installation of SAP ECC (AS ABAP)
TADM12_1
Lesson: Installation of SAP ECC Lesson Overview This lesson shows how to install an SAP ECC 6.05 system.
Lesson Objectives After completing this lesson, you will be able to: •
Install an SAP ECC 6.05 system
Business Example You want to install an SAP ECC 6.05 system
Install an SAP ECC 6.05 system Caution: You can not really install an SAP ECC 6.05 system. You will only be able to install an SAP ECC 6.0 system with one single technical usage of SAP Enhancement Package 5: Central Applications. All other needed technical usages have to be installed afterwards using SAPehpi. For more details see the corresponding lesson of this course. The initial installation of an SAP ECC 6.05 system takes less than one day. The installation of the other usage types takes around three days and is much more complicated. In the past, when trying to install an SAP ECC 6.04 system, NO technical usage of SAP Enhancement Package 4 for SAP ERP 6.0 was installed! This was called an EHP 4 ready system. All technical usages had to be installed afterwards using SAPehpi. For the initial installation of the SAP ECC 6.05 system: After you did all necessary planning and preparation steps, start SAPinst from the SAP Enhancement Package 5 for SAP ERP 6.0 installation master DVD and choose to install an SAP ECC system.
130
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP ECC
Figure 53: Installation of SAP ECC 6.05 - 1/7
Navigate to Enhancement Package 5 for SAP ERP 6.0 → SAP Application Server ABAP → MaxDB → Central System → Central System. Choose Parameter Mode Typical.
2012
© 2011 SAP AG. All rights reserved.
131
Unit 5: Installation of SAP ECC (AS ABAP)
TADM12_1
Figure 54: Installation of SAP ECC 6.05 - 2/7
Choose E## as SAP system ID, G: as installation drive, Master## as master password and E## as database ID. Whereby ## is your two digit group number.
132
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP ECC
Figure 55: Installation of SAP ECC 6.05 - 3/7
Provide the DVDs and the path to the SAP Cryptographic Library. They all can be found at G:\ADM110_col72.
2012
© 2011 SAP AG. All rights reserved.
133
Unit 5: Installation of SAP ECC (AS ABAP)
TADM12_1
Figure 56: Installation of SAP ECC 6.05 - 4/7
Change the default values as shown on the slide and start the installation process.
134
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP ECC
Figure 57: Installation of SAP ECC 6.05 - 5/7
Generate the SAP Solution Manager key within your SAP Solution Manager system, transaction SMSY: Log on to your previously installed SAP Solution Manager system, client 001 with user SAP*. SAP* should have the master password you selected when installing your SAP Solution Manager system. It should be Master##, whereby ## is your two digit group number. Right click Systems and choose Create New System to create an entry for your new SAP ECC system. After you have created an entry for your system choose Other Object... and press the button Generate Installation/Upgrade Key. But, just for confusion: 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. ;-) Hint: Just for generating the SAP Solution Manager key it is not important how you create the SMSY entry in detail. Creating SAP system entries in SMSY is not part of this course.
2012
© 2011 SAP AG. All rights reserved.
135
Unit 5: Installation of SAP ECC (AS ABAP)
TADM12_1
Figure 58: Installation of SAP ECC 6.05 - 6/7
Congratulations! You have installed your SAP ECC system.
136
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP ECC
Figure 59: Installation of SAP ECC 6.05 - 7/7
Caution: Due to a wrong set default you have to change the profile parameter PHYS_MEMSIZE. Change it immediately after the installation in the instance profile of the central instance of the SAP ECC system. Reduce the value of the parameter as shown on the slide. The instance profile can be found at G:\usr\sap\\SYS\profile. The instance profile is named _DVEBMGS_, for example E00_DVEBMGS10_twdf0000. Afterwards you have to restart the central instance of your SAP ECC system, of course.
2012
© 2011 SAP AG. All rights reserved.
137
Unit 5: Installation of SAP ECC (AS ABAP)
138
© 2011 SAP AG. All rights reserved.
TADM12_1
2012
TADM12_1
Lesson: Installation of SAP ECC
Exercise 5: Install an SAP ECC 6.05 System Exercise Objectives After completing this exercise, you will be able to: • install an SAP ECC 6.05 system
Business Example You want to install an SAP ECC 6.05 system.
Task: Install an SAP ECC 6.05 System Install an SAP ECC 6.05 system on the platform combination Microsoft Windows and MaxDB. Caution: Before this installation of the SAP ECC system you have installed the SAP Solution Manager system on the same host. Because of the different versions of the MaxDB of SAP ECC 6.05 and SAP Solution Manager 7.01 the installation of the SAP ECC system will break down right after selecting the MaxDB DVD. The error message will be: The global PATH variable contains information about the paths to existing MaxDB installations. ... as described in Oss-note 1357452 ... Solution: shutdown the SAP Solution Manager system, move the MaxDB parts from the global PATH variable to the local PATH variable of user S##adm. For setting the local PATH variable you have to log on as user S##adm, of course. Whereby ## stands for your two digit group number. 1.
2012
Install an SAP ECC 6.05 system.
© 2011 SAP AG. All rights reserved.
139
Unit 5: Installation of SAP ECC (AS ABAP)
TADM12_1
Solution 5: Install an SAP ECC 6.05 System Task: Install an SAP ECC 6.05 System Install an SAP ECC 6.05 system on the platform combination Microsoft Windows and MaxDB. Caution: Before this installation of the SAP ECC system you have installed the SAP Solution Manager system on the same host. Because of the different versions of the MaxDB of SAP ECC 6.05 and SAP Solution Manager 7.01 the installation of the SAP ECC system will break down right after selecting the MaxDB DVD. The error message will be: The global PATH variable contains information about the paths to existing MaxDB installations. ... as described in Oss-note 1357452 ... Solution: shutdown the SAP Solution Manager system, move the MaxDB parts from the global PATH variable to the local PATH variable of user S##adm. For setting the local PATH variable you have to log on as user S##adm, of course. Whereby ## stands for your two digit group number. 1.
Install an SAP ECC 6.05 system. a)
Perform the installation as described in the lesson Installation of SAP ECC. Hint: Don't forget to reduce the value of the profile parameter PHYS_MEMSIZE!
140
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP ECC
Lesson Summary You should now be able to: • Install an SAP ECC 6.05 system
2012
© 2011 SAP AG. All rights reserved.
141
Unit Summary
TADM12_1
Unit Summary You should now be able to: • Install an SAP ECC 6.05 system
142
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
143
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
144
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit 6 Installation of SAP XSS (AS Java) Unit Overview In this unit you install an SAP XSS system, which also includes the installation of an SAP NetWeaver Portal Core system in the same SAP system. Also you learn how to install additional Usage Types.
Unit Objectives After completing this unit, you will be able to: • •
Install an SAP XSS system Install an additional usage type in an existing AS Java based SAP system
Unit Contents Lesson: Installation of SAP XSS.................................................. 146 Exercise 6: Install an SAP XSS System..................................... 157 Lesson: Installation of Additional Usage Types ................................. 160 Exercise 7: Optional: Installation of an additional Usage Type .......... 165
2012
© 2011 SAP AG. All rights reserved.
145
Unit 6: Installation of SAP XSS (AS Java)
TADM12_1
Lesson: Installation of SAP XSS Lesson Overview This lesson explains how to install an SAP XSS system.
Lesson Objectives After completing this lesson, you will be able to: •
Install an SAP XSS system
Business Example After the successful installation of SAP ECC 6.05 system you decide to use some self service scenarios. Therefor you need to install an SAP XSS system.
Install an SAP XSS System An SAP XSS system is an AS Java based system. SAP XSS is a component of SAP ERP. SAP XSS needs an SAP Portal Core system installed in the same system. So you need to install the XSS software components together with the Portal Core software components. After you did all the necessary planning and preparation steps, start SAPinst from the SAP Enhancement Package 5 for SAP ERP 6.0 installation master DVD and choose the installation service to install an SAP NetWeaver system.
146
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP XSS
Figure 60: Installation of SAP XSS - 1/9
To install software units based on AS Java, select Enhancement Package 5 for SAP ERP 6.0 → SAP Application Server Java → MaxDB → Central System → Central System Select Parameter Mode Typical.
2012
© 2011 SAP AG. All rights reserved.
147
Unit 6: Installation of SAP XSS (AS Java)
TADM12_1
Figure 61: Installation of SAP XSS - 2/9
Select the software units needed. For more information see the Installation Master Guide. You want to install the software unit XSS. This software unit depends on the software units AS Java, EP Core, BP-XSS and BP-Common. Select these software units. Provide the requested DVD. All needed DVDs can be found on the installation host at G:\ADM110_col72.
148
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP XSS
Figure 62: Installation of SAP XSS - 3/9
Select X## as SAP system ID, G: as installation drive, Master## as master password and X## as database ID. Whereby ## stands for your two digit group number.
2012
© 2011 SAP AG. All rights reserved.
149
Unit 6: Installation of SAP XSS (AS Java)
TADM12_1
Figure 63: Installation of SAP XSS - 4/9
Provide the requested DVDs. All needed DVDs can be found on the installation host at G:\ADM110_col72.
150
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP XSS
Figure 64: Installation of SAP XSS - 5/9
Check if the SLD on the SAP Solution Manager system is available by using the URL http://:/sld. Log on with the user j2ee_admin and the master password you gave during the installation of the SAP Solution Manager system should be Master##, whereby ## stands for your two digit group number. If you see no error message or warnings the SLD should work. It should be installed and configured during the installation of the SAP Solution Manager system. See lesson SAP Solution Manager Installation. In SLD go to Technical Systems and choose All from the drop down. You should see two entries for your own SAP Solution Manager system (ABAP and Java). After the installation is finished you can check in SLD again, if the new SAP XSS system appears. Register the new SAP XSS system at the central SLD of your SAP Solution Manager system. Therefor you need to provide: the SLD HTTP Host - should be ., for example twdf0000.wdf.sap.corp the SLD HTTP Port - should be 500, should be 50000 the SLD Data Supplier User - leave the default
2012
© 2011 SAP AG. All rights reserved.
151
Unit 6: Installation of SAP XSS (AS Java)
TADM12_1
the Password for SLD Data Supplier User - should be the master password of your SAP Solution Manager system, should be Master##, whereby ## stands for your two digit group number
Figure 65: Installation of SAP XSS - 6/9
Change the values as described on the slide.
152
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP XSS
Figure 66: Installation of SAP XSS - 7/9
Choose to install an own database for the SAP XSS system (of course!) and start the installation process.
2012
© 2011 SAP AG. All rights reserved.
153
Unit 6: Installation of SAP XSS (AS Java)
TADM12_1
Figure 67: Installation of SAP XSS - 8/9
Generate the SAP Solution Manager key within your SAP Solution Manager system, transaction SMSY: Log on to your previously installed SAP Solution Manager system, client 001 with user SAP*. SAP* should have the master password you selected when installing your SAP Solution Manager system. It should be Master##, whereby ## is your two digit group number. Right click Systems and choose Create New System to create an entry for your new SAP XSS system. After you have created an entry for your system choose Other Object... and press the button Generate Installation/Upgrade Key. But: 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. ;-) Hint: Just for generating the SAP Solution Manager key it is not important how you create the SMSY entry in detail. Creating SAP system entries in SMSY is not part of this course.
154
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP XSS
Figure 68: Installation of SAP XSS - 9/9
Congratulations! You have installed your SAP XSS system.
2012
© 2011 SAP AG. All rights reserved.
155
Unit 6: Installation of SAP XSS (AS Java)
156
© 2011 SAP AG. All rights reserved.
TADM12_1
2012
TADM12_1
Lesson: Installation of SAP XSS
Exercise 6: Install an SAP XSS System Exercise Objectives After completing this exercise, you will be able to: • install an SAP XSS system
Business Example You want to install an SAP XSS system.
Task: Install an SAP XSS system Install an SAP XSS system. 1.
2012
Install an SAP XSS system.
© 2011 SAP AG. All rights reserved.
157
Unit 6: Installation of SAP XSS (AS Java)
TADM12_1
Solution 6: Install an SAP XSS System Task: Install an SAP XSS system Install an SAP XSS system. 1.
Install an SAP XSS system. a)
158
Perform the installation as described in the lesson Installation of SAP XSS.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP XSS
Lesson Summary You should now be able to: • Install an SAP XSS system
2012
© 2011 SAP AG. All rights reserved.
159
Unit 6: Installation of SAP XSS (AS Java)
TADM12_1
Lesson: Installation of Additional Usage Types Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •
Install an additional usage type in an existing AS Java based SAP system
Business Example You want to install an additional usage type to an existing AS Java based SAP system.
Installing an Additional Usage Type with JSPM To install additional usage types to existing AS Java based SAP systems, not SAPinst is used, but the tool JSPM. JSPM is also used, for example, to install SAP Java Support Packages in AS Java based SAP systems. Hint: In older releases it was possible to install AS Java based usage types to AS ABAP based systems. This resulted in a AS ABAP + Java (dual stack) system. Because SAP recommends to do not install and use dual stack systems any longer, this possibility is deactivated since several releases. This installation was done in the past with SAPinst. Since 7.0 SPS 12 the Java Support Package Manager JSPM can be used to install an AS Java based usage type to an existing AS Java based SAP system. In this lesson the usage type BI Java is installed to the previously installed SAP XSS system. Usage type BI Java needs usage types EP Core and AS Java as prerequisites. These are fulfilled in the existing SAP XSS system.
160
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of Additional Usage Types
In this lesson you will take the necessary software components for usage type BI Java from one of the installation DVDs. This is ok, because you have just installed the SAP XSS system without patching it by now. Hint: In real live your installed system was patched already. Then you should rather collect the necessary software components for usage type BI Java including necessary SAP Support Packages via a maintenance transaction via Maintenance Optimizer (MOpz) via SAP Solution Manager. Using the Maintenance Optimizer is not part of this course. Caution: At the end of this lesson, you will have installed XSS and BI Java in the same SAP system. If this is a good idea has to be evaluated for the individual case. Of course now XSS and BI Java conflict in terms of performance, availability, maintenance, upgrade and so on.
Figure 69: Installation of Additional Usage Type with JSPM 1/4
2012
© 2011 SAP AG. All rights reserved.
161
Unit 6: Installation of SAP XSS (AS Java)
TADM12_1
The necessary software components for BI Java are located at G:\ADM110_col72\UT_BI-Java. They come from the Java Software Components DVD, as Part of the SAP Enhancement Package 5 for SAP ERP 6.0 DVDs at G:\ADM110_col72\DVDs\EHP5_ERP_6.0\EHP2_NETWEAVER_7.0_Java_SCs\DATA_UNITS\JAVA_J2E DEP_UT. Copy the six SCA files for BI Java to the electronic parcel service (EPS) inbox, should be G:\usr\sap\trans\EPS\in. Start JSPM by double clicking go.bat. go.bat is located at G:\usr\sap\\JC\j2ee\JSPM, should be G:\usr\sap\X00\JC20\j2ee\JSPM.
Figure 70: Installation of Additional Usage Type with JSPM 2/4
Provide the SDM password, which should be the master password of the SAP XSS system, should be Master##, whereby ## stands for your two digit group number.
162
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of Additional Usage Types
Choose New Software Components. If you would have manually supplied the necessary software components including a stack XML file, you would choose Additional Usage Type Installation. Hint: If you would have supplied the necessary software components including SAP Support Packages via a maintenance transaction, you would choose Support and Enhancement Package Stack.
Figure 71: Installation of Additional Usage Type with JSPM 3/4
JSPM scans the EPS inbox and validates the selected software components. Because Portal components are involved, JSPM has to restart the SAP XSS system after deployment of BI Java. Start the deployment.
2012
© 2011 SAP AG. All rights reserved.
163
Unit 6: Installation of SAP XSS (AS Java)
TADM12_1
Figure 72: Installation of Additional Usage Type with JSPM 4/4
The deployment takes around 15 minutes. After the deployment has finished, JSPM informs you, that essential manual configuration actions still have to be performed. The manual configuration of BI Java is not part of this lesson.
164
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of Additional Usage Types
Exercise 7: Optional: Installation of an additional Usage Type Exercise Objectives After completing this exercise, you will be able to: • install an additional usage type
Business Example You want to install an additional usage type for your SAP XSS system.
Task: Install the additional usage type BI Java for your SAP XSS system. Install the additional usage type BI Java for your SAP XSS system using JSPM. 1.
2012
Install the additional usage type BI Java.
© 2011 SAP AG. All rights reserved.
165
Unit 6: Installation of SAP XSS (AS Java)
TADM12_1
Solution 7: Optional: Installation of an additional Usage Type Task: Install the additional usage type BI Java for your SAP XSS system. Install the additional usage type BI Java for your SAP XSS system using JSPM. 1.
Install the additional usage type BI Java. a)
166
Perform the installation as described in the lesson Installation of Additional Usage Types.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of Additional Usage Types
Lesson Summary You should now be able to: • Install an additional usage type in an existing AS Java based SAP system
Related Information •
2012
For more information about installing additional usage types see the AS Java installation guide on SAP Service Marketplace, Quick Link instguides.
© 2011 SAP AG. All rights reserved.
167
Unit Summary
TADM12_1
Unit Summary You should now be able to: • Install an SAP XSS system • Install an additional usage type in an existing AS Java based SAP system
168
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
169
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
170
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit 7 Performing Post-Installation Activities Unit Overview This unit provides information about post-installation steps. In case of an SAP ECC 6.05 system you should first of all complete the installation of SAP Enhancement Package 5 for SAP ERP 6.0. Afterwards apply the latest Kernel patch and SAP Support Packages. You will learn about the initial technical configuration of AS ABAP and AS Java based SAP systems.
Unit Objectives After completing this unit, you will be able to: • • • • • • • • • • • • • • • •
2012
List relevant post installation steps Explain how to complete the installation of SAP Enhancement Package 5 for SAP ERP 6.0 Explain how to apply a kernel patch Explain how to apply a SAP Support Package for AS ABAP based SAP systems Explain how to apply a SAP Support Package for AS Java based SAP systems Explain what an SAP Support Package Stack is Describe the steps to install an SAP license Describe the steps to install the SAP online documentation Describe the steps to install and configure the SAProuter Describe the steps needed to configure the Transport Management System (TMS) Describe the steps needed to configure profile parameters Describe the steps to configure operation modes Perform final installation checks Describe how to activate SAP ECC Extensions Start and schedule the SAP Load Generator (SGEN) Run the Configuration Wizard
© 2011 SAP AG. All rights reserved.
171
Unit 7: Performing Post-Installation Activities
• •
TADM12_1
Describe the steps to verify the AS Java configuration Install a standalone SAP Gateway instance
Unit Contents Lesson: Overview of Post-Installation Steps .................................... 173 Exercise 8: Stop, Start and Logon ........................................... 177 Lesson: Completing the Installation of SAP Enhancement Packages 5 for SAP ERP 6.0 .............................................................................. 180 Lesson: Patching SAP Systems .................................................. 186 Exercise 9: Applying a Kernel Patch......................................... 201 Lesson: SAP License, Online Documentation, Remote Connection to SAP Support ............................................................................... 204 Exercise 10: SAP License, SAProuter....................................... 215 Lesson: Initial Configuration for an AS ABAP based SAP System........... 218 Exercise 11: Initial Configuration of an AS ABAP based SAP System .. 239 Lesson: Initial Configuration of an AS Java based SAP System ............. 245 Lesson: Appendix: Installation of Standalone SAP Gateway ................. 254
172
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Overview of Post-Installation Steps
Lesson: Overview of Post-Installation Steps Lesson Overview This lesson gives a short overview of necessary steps after the installation of an SAP system.
Lesson Objectives After completing this lesson, you will be able to: •
List relevant post installation steps
Business Example You want to list relevant post installation steps.
Overview of Post-Installation Steps After you installed an SAP system you need to perform the following steps. The suggested order may vary slightly depending on your installation variant and database: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10.
11. 12. 13. 14.
2012
Start and stop the SAP system Log on to the SAP system Install a permanent license Install and configure the online documentation Configure remote connection to SAP support Perform initial configuration for AS ABAP based SAP systems, for example Transport Management System (TMS), logon groups, profile parameters, printers Apply the latest SAP Support Packages and patches Create the production client (if you don't want to use 001) Perform a full backup of the whole installation Perform various settings depending on what components you installed or want to use, for example settings for Adobe Document Service (ADS) or Composite Application Framework. Or implement and configure Add-on components Ensure user security Run the Configuration Wizard for AS Java based SAP systems Check Java documentation for Java relevant settings Configure IT scenarios with the help of documentation found in the SAP Solution Manager
© 2011 SAP AG. All rights reserved.
173
Unit 7: Performing Post-Installation Activities
TADM12_1
Procedure to Start and Stop the SAP System •
Stop the SAP system by executing command stopsap on the host of the SAP system using the SAP Management Console (http://:5$$13, whereby $$ is the instance number) – using the SAP Microsoft Management Console on the host of the SAP system (Windows only) Check the settings for Java Virtual Machine parameters as described in SAP Note 723909. Start the SAP system by
– –
• •
executing command startsap on the host of the SAP system using the SAP Management Console (http://:5$$13, whereby $$ is the instance number) – using the SAP Microsoft Management Console on the host of the SAP system (Windows only) Log on to the AS ABAP based SAP system with standard user SAP* or DDIC and the master password you have chosen during the installation Log on the AS Java based SAP system with standard user Administrator (AS Java based SAP systems only) or j2ee_admin (AS ABAP + Java based SAP systems only) – –
• •
You can use this procedure to see if you can start and stop the SAP system after the installation. To log on, install a client software such as the SAP GUI. Two of the standard users in AS ABAP based SAP systems after the installation are: • •
SAP* in client 000, 001, 066 DDIC in client 000, 001 Hint: The first thing after you have logged on to the SAP system is to create an own SAP user account. Many post processing activities can NOT be performed with SAP* or DDIC - not because they do not have enough authorizations, but just because they are SAP* or DDIC..
174
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Overview of Post-Installation Steps
Check some basic SAP system services to solve the initial problems that might occur when trying to log on to or run the SAP system for the first time. •
•
•
Check the following file system files in directory \usr\sap\\\work\ – dev_ms – dev_disp – dev_dispatcher – dev_rd – dev_w* – dev_server0 Check transactions – SM51 (all available instances) – SM50 (all available work processes for the instance you are logged on to) – SM21 (system log) For AS Java based SAP systems check the Java system information (http://:5$$00/sap/monitoring/SystemInfo, where $$ is the instance number)
Performing a Full Installation Backup Windows operating system: save the Registry: • •
Choose Start → Programs → Accessories → System → Tools → Backup → Emergency Repair Disk. Select Also Backup the Registry to the Repair directory. When you confirm your entry, the Registry is written to the disk.
Save system state data: • •
2012
Choose Start → Programs → Accessories → System → Tools → Backup → Backup Wizard. Select Only back up system state data and specify the Backup media type and the destination of the backup.
© 2011 SAP AG. All rights reserved.
175
Unit 7: Performing Post-Installation Activities
TADM12_1
Back up all SAP specific and database related directories: • • •
•
Choose Start → Programs → Accessories → System → Tools → Backup → Backup Wizard. Select Backup selected files, drives or network data. Select the Windows directory and all SAP and database related directories, including \usr\sap; \usr\sap\trans; of adm; \%WINDIR%. On the Where to Store the Backup screen, specify the media type and the destination of the backup.
You need to back up the following directories and files: • • •
All database specific directories Registry All SAP specific directories: – – – –
• •
\usr\sap\ \usr\sap\trans home directory of user adm \%WINDIR%
All database specific directories All SAP specific directories: – – – – –
/usr/sap/ /usr/sap/trans / home directory of user adm root file system
This saves the structure of the SAP system and all configuration files, for example, file system size, logical volume manager configuration, and database configuration data. This procedure works on all hardware platforms. See your system administration guide for details and for operating system specific backup procedures.
176
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Overview of Post-Installation Steps
Exercise 8: Stop, Start and Logon Exercise Objectives After completing this exercise, you will be able to: • Stop and start an SAP system • Log on to an SAP system
Business Example You want to stop and start your newly installed SAP system and log on to it.
Task 1: Stop, start and log on to your SAP ECC system Restart the SAP ECC system and perform some basic checks. 1.
Stop and start the SAP ECC system using the Microsoft Management Console.
2.
Check developer traces on file system level. Log on to the SAP system and check the work processes, installed instances and the SAP system log for error messages.
Task 2: Check your SAP XSS system Check Java System Information of your SAP XSS system. 1.
2012
Call Java System Information of your SAP XSS system and check whether all AS Java processes are up and running.
© 2011 SAP AG. All rights reserved.
177
Unit 7: Performing Post-Installation Activities
TADM12_1
Solution 8: Stop, Start and Logon Task 1: Stop, start and log on to your SAP ECC system Restart the SAP ECC system and perform some basic checks. 1.
2.
Stop and start the SAP ECC system using the Microsoft Management Console. a)
Log on to the operating system as user adm.
b)
Start the Microsoft Management Console by choosing the appropriate icon. Select the desired instance(s), right-click and choose Stop from the context menu. Depending on whether you choose an individual instance or the entire SAP system, either an individual instance or the entire SAP system stops.
c)
Choose the node for the central instance in the Microsoft Management Console tree. Select the desired instance, right-click and choose Start.
Check developer traces on file system level. Log on to the SAP system and check the work processes, installed instances and the SAP system log for error messages. a)
On file system level, open dev_ms, dev_disp, dev_rd, and dev_w0, located in the instance directory G:\usr\sap\\DVEBMGS10\work using Windows Explorer. Check the files for errors.
b)
Log on to your SAP system. Choose transaction SM51 to display the active SAP instances. The work process overview in transaction SM50 displays the list of work processes of the instance to which you are logged on.
c)
Check the system log in transaction SM21 for errors.
Task 2: Check your SAP XSS system Check Java System Information of your SAP XSS system. 1.
178
Call Java System Information of your SAP XSS system and check whether all AS Java processes are up and running. a)
Open a Browser and call http://:52000/sap/monitoring/SystemInfo.
b)
log on with the standard administrator user Administrator and the corresponding password, should be the master password, should be Master##, whereby ## is your two digit group number.
c)
Check whether all Java processes have the status running.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Overview of Post-Installation Steps
Lesson Summary You should now be able to: • List relevant post installation steps
2012
© 2011 SAP AG. All rights reserved.
179
Unit 7: Performing Post-Installation Activities
TADM12_1
Lesson: Completing the Installation of SAP Enhancement Packages 5 for SAP ERP 6.0 Lesson Overview This lesson explains the steps to complete the installation of SAP Enhancement Package 5 for SAP ERP 6.0.
Lesson Objectives After completing this lesson, you will be able to: •
Explain how to complete the installation of SAP Enhancement Package 5 for SAP ERP 6.0
Business Example You want to explain how to complete the installation of SAP Enhancement Package 5 for SAP ERP 6.0.
Completing the Installation In a previous unit you installed an SAP ECC 6.05 system. To be precise, it only contains one Technical Usage of SAP Enhancement Package 5 for SAP ERP 6.0: Central Applications. In most cases you need additional Technical Usages of SAP Enhancement Package 5 for SAP ERP 6.0. To complete the installation, you must install the required Technical Usages of SAP Enhancement Package 5 for SAP ERP 6.0. Hint: Technical Usages are groups of software components. For example the Technical Usage Central Applications contains the software components SAP_APPL and EA-APPL. You will not be able to really install the missing Technical Usages in this course, because the installation would run for three ore more days (if you know, what you are doing). You should just roughly understand the concept of SAP enhancement packages for SAP ERP 6.0.
180
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Completing the Installation of SAP Enhancement Packages 5 for SAP ERP 6.0
SAP Enhancement Packages for SAP ERP 6.0 In the past SAP delivered new functions for existing releases with SAP Support Packages, which means not only legal changes and corrections but also several new functions were delivered by SAP Support Packages. The new big functions are normally delivered with a new release, so that an SAP system upgrade was necessary. An SAP system upgrade is a big project running over a long time. To reduce time and expenses for an SAP system upgrade, SAP introduces SAP enhancement packages for SAP ERP 6.0. Caution: Don't get mixed up: SAP enhancement packages for SAP ERP 6.0 (or SAP CRM 7.0 or SAP SCM 7.0 or SAP SRM 7.0) are technically totally different from SAP enhancement packages for SAP NetWeaver. This lesson only refers to SAP enhancement packages for SAP ERP 6.0. Hint: Compared with an upgrade project, a project to implement SAP enhancement packages for SAP ERP 6.0 runs only about half as long and only produces only about half the costs.
Figure 73: What are SAP Enhancement Packages for SAP ERP 6.0?
2012
© 2011 SAP AG. All rights reserved.
181
Unit 7: Performing Post-Installation Activities
TADM12_1
SAP enhancement packages for SAP ERP 6.0 represent a new software delivery strategy that allows you to get innovations on top of SAP ECC 6.0 without the need for fully upgrading your current SAP ECC 6.0. With SAP enhancement packages for SAP ERP 6.0, the methodology for implementing new functionality has significantly changed. Caution: Beware of the essential difference between SAP ERP and SAP ECC! With the SAP enhancement package for SAP ERP 6.0 delivery technology, SAP provides you with new developments and enhancements of applications for your existing SAP ERP 6.0 systems. This means that you can use new developments offered for your business processes when you want to and according to your own requirements. The new developments and enhancements only become active after you decide to use these new features, have installed the relevant technical components, and have activated the corresponding business functions in your AS ABAP based SAP ECC system. The existing business processes for which you do not activate a business function remain unchanged. Caution: There is not the possibility to activate business functions in other SAP ERP systems than SAP ECC! So in most SAP ERP systems there are no switches, only in an SAP ECC system. SAP enhancement packages for SAP ERP 6.0 are based on SAP ERP 6.0. In SAP ECC 6.0, a new Switch Framework was introduced to activate SAP industry solutions which are delivered with SAP ECC 6.0. With the SAP ECC parts of the SAP enhancement packages for SAP ERP 6.0, this Switch Framework has been enhanced to activate deliveries of SAP enhancement packages for SAP ERP 6.0 in the customer's system. From the technical point of view this means, the Switch Framework can change repository objects without being immediately active in the SAP ECC system. Without activating the deliveries for SAP enhancement package for SAP ERP 6.0, neither the functionality delivered nor the corresponding user interface enhancements can be used. SAP enhancement packages for SAP ERP 6.0 provide organizations, that have implemented SAP ERP 6.0, with additional high-value applications and enable them to install new applications quickly. SAP plans to deliver at least 6 SAP enhancement packages for SAP ERP 6.0. A newer SAP enhancement package for SAP ERP 6.0 includes the deliveries of the predecessor versions.
182
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Completing the Installation of SAP Enhancement Packages 5 for SAP ERP 6.0
Figure 74: Installation and Activation
SAP enhancement packages for SAP ERP 6.0 are shipped as a delta shipment to SAP ERP 6.0. They are full patches for software components of an SAP ERP 6.0 system. As SAP enhancement packages for SAP ERP 6.0 are cumulative, you don't have to care about the implementation sequence. SAP recommends to implement always the newest available SAP enhancement package for SAP ERP 6.0.
2012
© 2011 SAP AG. All rights reserved.
183
Unit 7: Performing Post-Installation Activities
TADM12_1
Installation of SAP Enhancement Package for SAP ERP 6.0 Implementation Procedure at a Glance: 1.
2. 3.
Collect the information on which business functions should be used - provided by a business expert. You can find the complete list of business functions as well as the mapping to processes and scenarios in the SAP Service Marketplace, Quick Link erp-ehp. Check which prerequisites must be met. Map the business function(s) to the corresponding Technical Usage(s). Hint: For SAP Enhancement Package 4 for SAP ERP 6.0 see SAP Note 1165438 for details. For SAP Enhancement Package 5 for SAP ERP 6.0 see SAP Note 1324838 for details.
4.
Use the Maintenance Optimizer (in SAP Solution Manager) to select the correct Technical Usages and SAP Support Packages - this is mandatory! Hint: Use at least SAP Solution Manager 7.01!
5.
Install the required software components and SAP Support Packages of the SAP enhancement package for SAP ERP 6.0 parts. Hint: The installation is been done with the SAP Enhancement Package Installer SAPehpi.
6.
Activate the business function – depending on your planning, either directly, or separately, after the installation procedure. Hint: SAP recommends to activate the business functions separately, some time after the installation procedure. Hint: The installation is been done with SAPehpi - this is almost identically with upgrading an SAP system with SAPup.
184
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Completing the Installation of SAP Enhancement Packages 5 for SAP ERP 6.0
Lesson Summary You should now be able to: • Explain how to complete the installation of SAP Enhancement Package 5 for SAP ERP 6.0
Related Information •
2012
Additional information about SAP enhancement packages for SAP ERP 6.0 is available at SAP Service Marketplace, Quick Link erp-ehp
© 2011 SAP AG. All rights reserved.
185
Unit 7: Performing Post-Installation Activities
TADM12_1
Lesson: Patching SAP Systems Lesson Overview This lesson explains how to apply patches, such as kernel patches, SAP Notes and SAP Support Packages for AS ABAP and AS Java based SAP systems.
Lesson Objectives After completing this lesson, you will be able to: • • • •
Explain how to apply a kernel patch Explain how to apply a SAP Support Package for AS ABAP based SAP systems Explain how to apply a SAP Support Package for AS Java based SAP systems Explain what an SAP Support Package Stack is
Business Example You want to apply patches to your SAP system.
SAP Support Package Stacks SAP recommends that you keep your SAP systems up to date by regularly applying SAP Notes, SAP Support Packages and SAP Kernel Patches. This patching is becoming more and more a challenge by the complexity of the SAP system landscapes. Types of patches for an AS ABAP based SAP system: • •
• •
186
SAP Note: contains the correction or enhancement of a single repository object, for example some coding lines for a program SAP Support Package: contains a bundle of objects and customizing for one single software component to be exchanged - for correction or for legal reasons, sometimes to deliver new functionality Kernel patch: contains a bundle of kernel elements, such as executables or libraries SAP Support Package stack: bundle of SAP Support Packages and a kernel patch that have been tested by SAP for side effects
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
Types of patches for an AS Java based SAP system: • • • •
Patch: contains a bundle of corrections SAP Support Package: contains a complete software component Kernel patch: contains a bundle of kernel elements, such as executables or libraries SAP Support Package stack: bundle of SAP Support Packages and a kernel patch that have been tested by SAP for side effects Note: An AS ABAP Support Package is not the equivalent to an AS Java Support Package! An AS ABAP Support Package is a subset of a software component, an AS Java Support Package is the full delivery of a software component.
Because SAP systems have more and more software components and because SAP system landscapes consist of more and more SAP systems, Hint: SAP recommends to apply complete SAP Support Package stacks rather than an individual combination of SAP Support Packages. An SAP Support Package stack also contains a installation guide for the SAP Support Package stack. You should read this guide and the corresponding SAP Notes before applying the SAP Support Package stack.
2012
© 2011 SAP AG. All rights reserved.
187
Unit 7: Performing Post-Installation Activities
TADM12_1
Figure 75: SAP Note, Patch, SAP Support Package, SAP Support Package Stack
In older SAP releases you could download SAP Support Package stacks from SAP Service Marketplace, Quick Link sp-stacks. This is not possible any longer, since SAP is shipping new software components via SAP enhancement packages. For these newer releases it is mandatory to use the SAP Solution Manager Maintenance Optimizer. The Maintenance Optimizer calculates an individual SAP Support Package stack for your SAP system, lays the necessary patches in your download basket and approves your download basket. You can than download your download basket with the Download Manager to the SAP system's host. Now you can apply the patches.
188
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
Figure 76: Calculating SAP Support Package Stacks with Maintenance Optimizer
2012
© 2011 SAP AG. All rights reserved.
189
Unit 7: Performing Post-Installation Activities
TADM12_1
Steps to Apply AS ABAP SAP Support Packages Using Transaction SPAM
Figure 77: Apply AS ABAP SAP Support Packages Using Transaction SPAM
The usage of transaction SPAM is explained in great detail in the courses ADM100 – Administration AS ABAP I and ADM325 - Software Logistic for AS ABAP. The screen shots remind you how to apply AS ABAP SAP Support Packages.
Steps to Apply AS Java SAP Support Packages Using JSPM You can use the Java Support Package Manager (JSPM) to apply AS Java SAP Support Packages. With JSPM you can also deploy SAP and third-party software components to your AS Java based SAP system. You can also deploy new business packages of the SAP Business Suite. You can also upgrade and update business packages of SAP Business Suite that are deployed on the AS Java based SAP system to a higher release. In addition, JSPM detects SAP software components that have been modified and allows you to apply SAP Support Packages to them.
190
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
JSPM has the following features: • • •
Overview of deployed components Update of kernel binaries, Software Deployment Manager (SDM), Internet Graphics Server (IGS), and JSPM Deployment of: – – – – – –
AS Java SAP Support Package stack single AS Java SAP Support Packages SAP and third-party software components deploy and upgrade business packages of SAP Business Suite detects modified software components and transports them for deployment to SAP NetWeaver Development Infrastructure (NWDI) informs you if restarting of the AS Java is necessary during the deployment process Hint: Only operating system user adm can use JSPM.
Make sure that all SAP Support Packages to be applied are copied into the JSPM inbox. The JSPM inbox is a file system directory and resides at DIR_EPS_ROOT/in. DIR_EPS_ROOT/in is a profile parameter and can be defined in the central instance profile. The SAP Support Packages for the kernel and other OS level binaries are delivered as SAR files. Make sure that your current SAPCAR tool is able to extract these files.
2012
© 2011 SAP AG. All rights reserved.
191
Unit 7: Performing Post-Installation Activities
TADM12_1
Figure 78: JSPM: AS Java SAP Support Package 1/2
192
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
Figure 79: JSPM: AS Java SAP Support Package 2/2
The use of tool JSPM is explained in great detail in the course ADM200 – Administration AS Java. The screen shots remind you how to apply AS Java SAP Support Packages.
Steps to Apply a Kernel Patch Depending on your installed SAP system you can use the Java tool JSPM (Java Support Package Manager) or the manual procedure to do an update of the kernel. • •
2012
manual update: For all SAP system based on AS ABAP (only), for example, SAP ECC, SAP BW, SAP CRM server update with JSPM: For all system based on AS Java (including AS ABAP + AS Java system), for example, SAP Portal, SAP XSS, SAP Solution Manager
© 2011 SAP AG. All rights reserved.
193
Unit 7: Performing Post-Installation Activities
TADM12_1
Manual Update When you apply a kernel patch manually, make sure that the following prerequisites are met: • •
SAP system is stopped On Windows, the SAP services, including SAPOsCol, are stopped.
When applying a kernel patch with JSPM, the SAP system has to stopped also, of course. But you don't have to stop it manually, JSPM does the stopping and starting.
Figure 80: AS ABAP: Show Patch Levels Kernel, SAP Support Packages, and Database Release
The screenshots show the content of the System → Status of an AS ABAP based SAP system. To update the kernel, follow the instructions given in the SAP Support Package stack guide. This guide can be found at SAP Service Marketplace, Quick Link instguides under, for example, SAP NetWeaver → SAP NetWeaver 7.0 → Maintenance. Note: Usually applying a kernel patch manually is just stopping the SAP system, copy and paste the kernel patch, restart the SAP system.
194
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
As of SAP NetWeaver 7.0 and related SAP systems, SAP introduces a new directory structure to improve the support of mixed platform configurations. The new directory structure is only created during new installations. SAP Note 919046 Upgrade to the New Instance-Specific Directory Structure describes how to configure upgraded SAP systems to the new directory structure. Hint: The new kernel structure applies only for SAP systems installed on Windows operating system with SAP NetWeaver 7.0 and related SAP systems. For SAP systems installed on other operating systems, the new kernel structure comes with SAP NetWeaver 7.10 and related SAP systems. The new directory structure consists of the following major changes: •
• •
•
2012
The directory \\sapglobalhost\sapmnt\SAPSID\sys\exe\run on the central instance is replaced with \\sapglobalhost\sapmnt\\sys\exe\\ whereby is UC for Unicode Systems, or NUC for non-Unicode systems, and is NTI386 (for 32 Bit Windows), NTAMD64 (for Windows X86_64), or NTIA64 (for Windows IA64 executables). The directory \\sapglobalhost\sapmnt\\sys\exe\runU used by the AS Java Add-in instances is replaced by \\sapglobalhost\sapmnt\\sys\exe\UC\ The central instance uses an instance-specific executable directory (\\sapglobalhost\saploc\\DVEBMGS##\exe, whereby ## is the instance number). An instance should not directly use \\sapglobalhost\sapmnt\\SYS\exe\run
© 2011 SAP AG. All rights reserved.
195
Unit 7: Performing Post-Installation Activities
TADM12_1
Figure 81: Applying a Kernel Patch Manually (1/2)
196
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
Figure 82: Applying a Kernel Patch Manually (2/2)
In the screenshots, you see that you will replace kernel files in the directory \usr\sap\\SYS\exe\uc\NTADM64. The success of the kernel patch can be seen at System → Status.
Apply Kernel Update using JSPM Starting with SAP NetWeaver 7.0, the Java Support Package Manager (JSPM) is used for applying SAP Support Packages and kernel patches to AS Java based SAP systems. Additionally JSPM can update JSPM itself and all installed AS Java based usage types in the AS Java based SAP system.
2012
© 2011 SAP AG. All rights reserved.
197
Unit 7: Performing Post-Installation Activities
TADM12_1
Figure 83: Apply a Kernel Patch using JSPM
Steps to Apply a Database Patch • • • • •
Download the latest database patch from SAP Service Marketplace, Quick Link patches to your SAP host. Follow SAP Note 735598 - Importing MaxDB software as of 7.5.00 to install patches for MaxDB. Follow, for example, SAP Note 1363170 - DB6: Installing fix packs for DB2 9.7 (Windows) for DB2 UDB; Follow SAP Note 62988 - Service Packs for Microsoft SQL Server and related SAP Notes to install Service Packs for Microsoft SQL Server. Follow, for example, SAP Note 839182 - Installing patches using OPatch to install patches for Oracle 10.2 and 11.2.
Because different database releases might have different patch strategies, please check SAP Service Marketplace, Quick Link instguides and go to Other Documentation → Database Upgrades.
198
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
There are different procedures to apply patches to the different databases supported by SAP systems. When applying patches, you will notice that databases from the same vendor can differ significantly between releases. As a result, ensure that you are using the patch description that fits your database release. In addition, check the SAP Notes in the figure before applying a database patch. The content of the SAP Notes might have been revised. For DB2 on iSeries, go to http://www.4soi.de/IBM-Infoapars.php. For DB2 on zSeries, follow the instructions on how to fix the operating system. SAP Note 81737 lists the operating system fixes that should be applied in an SAP environment.
2012
© 2011 SAP AG. All rights reserved.
199
Unit 7: Performing Post-Installation Activities
200
© 2011 SAP AG. All rights reserved.
TADM12_1
2012
TADM12_1
Lesson: Patching SAP Systems
Exercise 9: Applying a Kernel Patch Exercise Objectives After completing this exercise, you will be able to: • manually apply a kernel patch • apply a kernel patch with JSPM
Business Example You want to apply a kernel patch.
Task 1: AS ABAP: Apply a Kernel Patch Manually Manually apply a kernel patch to your SAP ECC system. 1.
Check the current kernel patch level of your SAP ECC system and apply the kernel patch, provided at G:\ADM110_col72\Kernel_Patch_720_AS_ABAP_unpacked. Afterwards check the result. Caution: Copy the old kernel to a backup folder before you patch it.
Task 2: OPTIONAL: AS Java: Apply a Kernel Patch with JSPM Apply a Kernel patch using JSPM to your SAP XSS system. 1.
2012
Copy the kernel patch from G:\ADM110_col72\Kernel_Patch_720_AS_Java to your EPS inbox G:\usr\sap\trans\EPS\in and apply the kernel patch using JSPM with option Single Support Packages.
© 2011 SAP AG. All rights reserved.
201
Unit 7: Performing Post-Installation Activities
TADM12_1
Solution 9: Applying a Kernel Patch Task 1: AS ABAP: Apply a Kernel Patch Manually Manually apply a kernel patch to your SAP ECC system. 1.
Check the current kernel patch level of your SAP ECC system and apply the kernel patch, provided at G:\ADM110_col72\Kernel_Patch_720_AS_ABAP_unpacked. Afterwards check the result. Caution: Copy the old kernel to a backup folder before you patch it. a)
Follow the steps described on the slides of this lesson.
Task 2: OPTIONAL: AS Java: Apply a Kernel Patch with JSPM Apply a Kernel patch using JSPM to your SAP XSS system. 1.
Copy the kernel patch from G:\ADM110_col72\Kernel_Patch_720_AS_Java to your EPS inbox G:\usr\sap\trans\EPS\in and apply the kernel patch using JSPM with option Single Support Packages. a)
202
Follow the steps described on the slide of this lesson.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
Lesson Summary You should now be able to: • Explain how to apply a kernel patch • Explain how to apply a SAP Support Package for AS ABAP based SAP systems • Explain how to apply a SAP Support Package for AS Java based SAP systems • Explain what an SAP Support Package Stack is
2012
© 2011 SAP AG. All rights reserved.
203
Unit 7: Performing Post-Installation Activities
TADM12_1
Lesson: SAP License, Online Documentation, Remote Connection to SAP Support Lesson Overview The lesson describes how to install an SAP License, the SAP online documentation, and a remote connection to the SAP Support.
Lesson Objectives After completing this lesson, you will be able to: • • •
Describe the steps to install an SAP license Describe the steps to install the SAP online documentation Describe the steps to install and configure the SAProuter
Business Example You want to install an SAP license, install the SAP online documentation and configure the SAProuter.
Steps to Install an SAP Licenses You have to install a new permanent SAP license after you do the following: • • • • •
Perform a new SAP system installation Rename your SAP system ID Change the message server host Change an existing hardware configuration that results in a change of hardware key Change of database type
To work with an SAP system, you require an SAP license. After the installation of the central instance, a temporary license is active only for four weeks. During this period, you must install a permanent license. If the temporary license expires, only the user SAP* can log on to the SAP system. With this temporary license, you cannot create new repository objects or modify SAP repository objects. You can install several licenses. When you change the installation number, all dependent information, such as SSCR (SAP software change registration) keys, is lost.
204
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: SAP License, Online Documentation, Remote Connection to SAP Support
You can find information about applying for an SAP license key in the SAP Service Marketplace, Quick Link licensekey, and in the SAP Note 767123 and the SAP Note 765620. Note: As of SAP NetWeaver 7.0 basis, in addition to the old type of license key, there is also a new type of license key, which is based on a digital signature. Both types of license keys are installed and administered with transaction SLICENSE, as previously, and are available as temporary and permanent license keys. The functions for the new license keys can be accessed by choosing the New Licenses button in transaction SLICENSE. To allow a seamless transition, both types of license keys initially function in parallel after an SAP system upgrade. If license keys of the old type were already installed, you can continue to use these. However, we recommend that you also import license keys of the new type, since the license keys of the old type will be deactivated in future. For this reason, only keys of the new type are assigned for new installations.
Figure 84: Installing new SAP License in an AS ABAP based SAP System
In an AS ABAP based SAP system you can use transaction SLICENSE to determine the hardware key on all hosts of the SAP system.
2012
© 2011 SAP AG. All rights reserved.
205
Unit 7: Performing Post-Installation Activities
TADM12_1
On the initial screen of the transaction SLICENSE, choose New Licenses. The hardware key of the local host is shown directly on the screen. Use this hardware key to request a license at SAP. You can install a new SAP License on your SAP system using the SLICENSE transaction. In the New Licenses screen choose Edit → Install License and upload the license file you received from SAP by mail. After the license is installed, the license key is active immediately.
AS Java License In case you have an SAP system based on AS Java (without ABAP), for example an SAP Portal system, you have to install the SAP license with the SAP Visual Administrator.
Figure 85: Installing License in AS Java based System
Log on to the Visual Administrator. You may need to create a new connection entry first. For this you need to know either the HTTP port of the Java Message Server (default 81) or the P4 port of a Java Dispatcher (default 504).
206
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: SAP License, Online Documentation, Remote Connection to SAP Support
In the Visual Administrator go to the server node of the central instance and select the Licensing Adapter Service. Copy the Hardware Key to request the license from SAP. Afterwards choose Install license from file to install the license.
Steps to Install SAP Online Documentation
Figure 86: Installing SAP Online Documentation
There is one SAP Online Documentation DVD containing both formats, standard HTML and compiled HTML. With help type PlainHtmlHttp (installation of help files on a Web server), you also need to maintain Web server settings. For more information about installing SAP online documentation, refer to Installing the Online Documentation in the root directory of the SAP Library - Online Documentation DVD or go toSAP Service Marketplace, Quick Link instguides, Other Documentation → SAP Library. You can also refer to the documentation given on the SAP Library DVD itself.
2012
© 2011 SAP AG. All rights reserved.
207
Unit 7: Performing Post-Installation Activities
TADM12_1
General information on how to install the help files: • •
Use separate directories for different language versions of the documentation. Use a two-character language key, such as EN for English, DE for German or FR for French, for directory names.
When accessing the documentation online, the help processor expects directories that are named with their respective two-character language keys, such as EN for English, DE for German or FR for French.
Installation of Help Type HtmHelpFile The compiled HTML files for help type HtmlHelpFile can be installed with SAPinst from the installation master DVD to a local file server. Start SAPinst from G:\ADM110_col72\DVDs\EHP5_ERP_6.0\EHP5_ERP_6.0_Installation_Master_13\BS7i2010_Installation_Master\IM_WINDOWS_X86_64.
Figure 87: Installation of Help Type HtmHelpFile
Approximately 1 GB of disk space is needed for the English and German language versions.
208
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: SAP License, Online Documentation, Remote Connection to SAP Support
You can, for example, install the SAP NetWeaver online help from G:\ADM110_col72\DVDs\EHP5_ERP_6.0\EHP2_NETWEAVER_7.0\HTMLHELP\DE.
Installation of PlainHtmlHttp, PlainHtmlFile The Standard HTML files for help types PlainHtmlHttp and PlainHtmlFile are stored in a packed format in the archive Plainhtm.sar on the DVD. They cannot be viewed directly from the DVD but must first be unpacked on a file server. To unpack the help files you must use SAPinst from the installation master DVD. The complete installation comprises nearly 400,000 files in nearly 200,000 directories for one language version. Depending on the file system and the configuration of the hard disk they require about 3 GB of disk space. You cannot install online help on a Microsoft FAT32 file system because it cannot handle the large number of files and directories. If your web server runs on Microsoft Windows, do not install the help documentation on the system partition; choose another partition instead.
Setup Variants and Browsers for Online Help
Figure 88: Setup Variants and Browsers for Online Help
2012
© 2011 SAP AG. All rights reserved.
209
Unit 7: Performing Post-Installation Activities
TADM12_1
For a given front-end platform, a setup variant specifies a help type, the location of help files (server and/or path), and the language version of help files. The language version specified in the currently active setup variant determines which language version of the online help displays, regardless of the user’s logon language. As of release SAP R/3 4.6C, maintaining the old profile parameters for online help has no effect any longer. The HTML-based online documentation can display with a Web browser on all front-end platforms supported by SAP. However, certain requirements and restrictions must be observed, based on the platform. For more information refer to SAP Service Marketplace, Quick Link instguides, Other Documentation → SAP Library. For more information on setup variants for Online Help, see course ADM100 Administration AS ABAP I.
Remote Connection to SAP Support SAProuter is an SAP program that acts as an intermediate station (proxy) in a network connection between SAP systems, or between SAP systems and external networks. SAProuter controls the access to your network (application level gateway), and, as such, is a useful enhancement to an existing firewall system (port filter). • •
•
Control and log the connections to your SAP system, for instance from an SAP service center Set up an indirect connection when programs involved in the connection can not communicate with each other due to the network configuration (address conflicts when using non-registered IP addresses or restrictions arising from firewall systems Improve network security by means of the following: –
•
A password, which helps to protect your connection and data from unauthorized external access – Allowing access from particular SAProuters only – Only allowing encrypted connections from a known partner (using the SNC layer) Increase performance and stability by reducing the SAP system workload within a local area network (LAN) when communicating with a wide area network (WAN)
SAP offers its customers access to support and a number of remote services such as the EarlyWatch Service or the GoingLive Service. Therefore, you have to set up a remote network connection to SAP.
210
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: SAP License, Online Documentation, Remote Connection to SAP Support
For detailed information refer to SAP Service Marketplace, Quick Link remoteconnection . Also follow SAP Note 35010 - Service connections: Composite note (overview) You require SAProuter if you are using any of the following: • • •
Remote Services: e.g. EarlyWatch Remote Consulting SAP Support Portal
Figure 89: SAProuter and SAP Support Portal
SAProuter increases network security and simplifies network configuration. SAProuter allows you to make indirect network connections. SAProuter software is included in the standard SAP kernel. An additional installation is not required. The SAP Support Portal is the SAP based service system, which provides the technical link between SAP customers and SAP. SAProuter controls connections from SAP to your SAP system. SAProuter is started as a demon under UNIX and as a service under Windows.
2012
© 2011 SAP AG. All rights reserved.
211
Unit 7: Performing Post-Installation Activities
TADM12_1
Figure 90: Configuring SAProuter and SAP Support Portal in OSS1
For information about installing SAProuter on the AS400 platform, read SAP Note 86329. For more information on using SAProuter, see course ADM960 - SAP System Security. Also see SAP Notes: • • • •
212
Remote connection: SAP Note 14716 Log on to Online Service System: SAP Note 17285 SAProuter: SAP Note 30289 Security aspects for remote access: SAP Note 46902
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: SAP License, Online Documentation, Remote Connection to SAP Support
Figure 91: Configuring SAProuter in OSS1
Select the suitable SAProuter at SAP.
2012
© 2011 SAP AG. All rights reserved.
213
Unit 7: Performing Post-Installation Activities
214
© 2011 SAP AG. All rights reserved.
TADM12_1
2012
TADM12_1
Lesson: SAP License, Online Documentation, Remote Connection to SAP Support
Exercise 10: SAP License, SAProuter Exercise Objectives After completing this exercise, you will be able to: • Check the installed SAP license • Install SAProuter for SAPNet-R/3 Frontend access
Business Example You want to check the installed SAP license and install SAProuter.
Task 1: SAP License Check the installed SAP license. 1.
Check whether a temporary SAP license is installed.
Task 2: SAProuter Install, start, and configure SAProuter for SAP R/3 front-end access. The attachment of SAP Note 30289 is stored on your installation server, at G:\ADM110_col72\SAP_Note_0030289 . 1.
Install SAProuter and create the saprouttab permission file. Proceed as described in attachment of SAP Note 30289, section Installation on Windows. Use the saprouter.exe and niping.exe executables from the directory G:\usr\sap\\SYS\exe\uc\NTADM64.
2.
Create the saprouttab route permission table. Create the saprouttab file in the directory G:\usr\sap\saprouter and create the entry P * * *.
3.
Start SAProuter. Proceed as described in attachment of SAP Note 30289, section Starting SAProuter.
4.
2012
Check the technical settings in transaction OSS1.
© 2011 SAP AG. All rights reserved.
215
Unit 7: Performing Post-Installation Activities
TADM12_1
Solution 10: SAP License, SAProuter Task 1: SAP License Check the installed SAP license. 1.
Check whether a temporary SAP license is installed. a)
Start transaction SLICENSE and look at the Installed Licenses table to see the installed temporary license for your .
Task 2: SAProuter Install, start, and configure SAProuter for SAP R/3 front-end access. The attachment of SAP Note 30289 is stored on your installation server, at G:\ADM110_col72\SAP_Note_0030289 . 1.
Install SAProuter and create the saprouttab permission file. Proceed as described in attachment of SAP Note 30289, section Installation on Windows. Use the saprouter.exe and niping.exe executables from the directory G:\usr\sap\\SYS\exe\uc\NTADM64. a)
2.
Read the attachment of the SAP Note and follow its instructions in section Installation on Windows.
Create the saprouttab route permission table. Create the saprouttab file in the directory G:\usr\sap\saprouter and create the entry P * * *. a)
3.
(see task description)
Start SAProuter. Proceed as described in attachment of SAP Note 30289, section Starting SAProuter. a)
4.
Check the technical settings in transaction OSS1. a)
216
(see task description)
Proceed as described in the lesson.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: SAP License, Online Documentation, Remote Connection to SAP Support
Lesson Summary You should now be able to: • Describe the steps to install an SAP license • Describe the steps to install the SAP online documentation • Describe the steps to install and configure the SAProuter
2012
© 2011 SAP AG. All rights reserved.
217
Unit 7: Performing Post-Installation Activities
TADM12_1
Lesson: Initial Configuration for an AS ABAP based SAP System Lesson Overview This lesson explains post installation activities for an AS ABAP based SAP system. • • • • • • •
Configuration of the Transport Management System (TMS) Configuration of profile parameters Configuration of operation modes Perform final installation checks Activate SAP ECC Extensions Install additional languages Start and schedule the SAP Load Generator (SGEN)
Lesson Objectives After completing this lesson, you will be able to: • • • • • •
Describe the steps needed to configure the Transport Management System (TMS) Describe the steps needed to configure profile parameters Describe the steps to configure operation modes Perform final installation checks Describe how to activate SAP ECC Extensions Start and schedule the SAP Load Generator (SGEN)
Business Example You want to perform some post installation activities for your AS ABAP based SAP system.
Create Your own User Directly after the installation only a few standard dialog users exist in the SAP system: for example SAP* and DDIC. Although these users have many authorizations (authorization profile SAP_ALL), they are not allowed to do many things. For
218
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration for an AS ABAP based SAP System
example, they are not allowed to do any customizing or development related tasks. So already for performing the post installation steps you need to create a normal dialog user account.
Figure 92: Create own User Account in all Clients
In transaction SU01 copy SAP* or DDIC to a normal dialog user. This is necessary to perform some of the post installation steps. Hint: When creating the first dialog user, SU01 informs you, that no default company address exists. Create and maintain the default company address.
2012
© 2011 SAP AG. All rights reserved.
219
Unit 7: Performing Post-Installation Activities
TADM12_1
Post-Installation Activities for Transport Organizer
Figure 93: Post-Installation Activities for Transport Organizer
If you have installed your SAP system from the installation DVDs, you don't have to initialized the Change and Transport System (CTS) after installation, because it was already initialized by SAPinst. Basic settings for the CTS are generated during this initialization of the Transport Management System (TMS). If you have installed your SAP system as a copy of an existing SAP system, you must initialize the CTS after installation. If you set up an SAP system that originated from a database copy using Standard installation, problems could arise when you transport objects or upgrade the SAP system. Select Database Copy or Database Migration if the SAP system was created based on a copy. SAPinst provides utilities to copy and migrate databases of SAP systems. Once for the entire SAP system you have to set the system change options. These control the changeability of repository objects.
220
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration for an AS ABAP based SAP System
Once per client you have to maintain the client change options. Besides others, they control the changeability of repository objects and customizing from within the specific client. Note: For details see course ADM325 - Software Logistic AS ABAP.
Transport Management System (TMS) Configuration
Figure 94: TMS Configuration: Transport Domain
After installing the first SAP system, you can already set up the Transport Management System (TMS). The TMS describes the role of the SAP systems within a transport landscape. This could be for example: development system, quality assurance system, productive system. Hint: It is not necessary that all SAP systems from the transport landscape exist right from the start. Those SAP systems, that will be installed later, can be represented as virtual systems until they exist physically. After defining the role of the SAP systems, the transport sequence is defined by creating transport routs.
2012
© 2011 SAP AG. All rights reserved.
221
Unit 7: Performing Post-Installation Activities
TADM12_1
Optionally you should define the Quality Assurance (QA) procedure to prevent untested objects and customizing settings to be imported into the productive SAP system. Hint: The basic configuration of TMS must be done in transaction STMS in client 000.
Figure 95: TMS Configuration: Transport Routes
The initialization of TMS is done, when calling transaction STMS the first time. This includes the setup of the transport domain controller. To create virtual SAP systems or to approve SAP systems in transaction STMS navigate to Overview → Systems. To create transport routes in transaction STMS, drag the appropriate SAP systems from the node area to the display area. To create a transport route between these SAP systems, navigate to Overview → Transport Routes and choose Configuration → Standard Configuration. Select Single System or Development and Production System or Three Systems in group. Note: For details see course ADM325 - Software Logistic AS ABAP.
222
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration for an AS ABAP based SAP System
Performing Basic Operations
Figure 96: Import of Profiles
The technical configuration of an SAP system is controlled by profile parameters. There are more than 1,000 profile parameters. Most of them have a default, compiled in the kernel. They are not set explicitly. Only a very few profile parameter normally around 100 - are explicitly set in profiles. There is one single default profile, containing profile parameters that configure all instances. In addition each instance has its own instance profile to individually configure the corresponding instance. To configure what should be started when starting an SAP instance, each SAP instance has its own start profile. For example, when starting the central instance, the message server should be started also. After the installation, the profile parameters are only present at file level in these profiles. To use the profile administration inside the SAP system (transaction RZ10), the profiles must be imported into the database. During this import, the system performs a consistency check. Changes to profile parameters can then be performed in the SAP system. The profile parameters are then stored in the database and are written back to file system level. The changes only take effect when they are read by the SAP system at SAP system start. So after changing profile parameters the affected instances of the SAP system have to be restarted.
2012
© 2011 SAP AG. All rights reserved.
223
Unit 7: Performing Post-Installation Activities
TADM12_1
Perform the administration and maintenance of profiles in transaction RZ10. In the first step, you import the profiles into the database by choosing Utilities → Import Profiles→ Of active servers. After selecting the profile to edit, you can change and add individual profile parameters. SAPinst installs the SAP systems with a very small number of work processes. You have to increase the amount of work processes to the needs of the SAP system. • • • • • •
dialog work processes: 2 per instance update work processes: 1 per SAP system, usually on the central instance update2 work processes: 0 per SAP system, usually on the central instance batch work processes: 2 per SAP system enqueue work processes: 1 per SAP system, only on the central instance spool work processes: 1 per SAP system
SAP recommends that you adapt SAP profiles using transaction RZ10. Nevertheless, it is possible to change SAP parameters in the corresponding files on file system level, for example, if the SAP system can not be started any more because of a wrong configuration. Note: For details see course ADM100 - Administration AS ABAP I.
Set up Operation Mode Using operation modes you can control the amount of the different work process types during a day via a time table. The total amount of all work processes stays constantly. The total amount of all work processes can only be changed by changing the corresponding profile parameters and restarting the instances. Hint: Starting with AS ABAP 7.02 it is possible to dynamically change the total amount of work processes. This is controlled by new profile parameters.
224
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration for an AS ABAP based SAP System
Figure 97: Set up Operation Modes
Operation modes are set up in four steps: •
First, the operation modes are created as empty containers in transaction RZ04. Hint: A prerequisite for this is, that the profiles are loaded into the database with transaction RZ10.
•
•
•
Next, all active instances of the SAP system are recorded and the work processes defined in the instance profile(s) are assigned to the operation modes as default values. Next, distribute the individual operation modes in the total amount of work processes taken from the instance profile(s). The distribution should be primarily made between the dialog and background work processes. In the timetable (transaction SM63), you specify the periods for which operation modes are valid and when the switch between operation modes should occur. Note: For details see course ADM100 - Administration AS ABAP I.
2012
© 2011 SAP AG. All rights reserved.
225
Unit 7: Performing Post-Installation Activities
TADM12_1
Schedule Standard Background Jobs During the time several statistical and technical data cumulates in as SAP system: performance data, job logs, ABAP short dumps, spool data and so on. This data has to be reorganized regularly. For this purpose, standard reorganization jobs are offered in the SAP system. These standard jobs should be run regularly in an SAP System. The Job Definition, transaction SM36, provides a list of important standard jobs, which you should schedule.
Figure 98: Schedule Background Jobs
In transaction SM36 select Standard jobs. In the field SAP Component select BC. If you want to schedule all the standard jobs with one click, choose Default scheduling. The system schedules all standard jobs along with their specified variants and intervals. You can also schedule the different jobs individually. See SAP Note 16083 for more information on the standard jobs. Note: For details see course ADM100 - Administration AS ABAP I.
226
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration for an AS ABAP based SAP System
Basic Configuration: Additional Tasks • • •
Set up logon groups with transaction SMLG. Install printers with transaction SPAD. Configure system log with transaction SM21.
Load distribution allows you to dynamically distribute the SAP users across the application servers of the SAP system. Logon load balancing increases efficiency with respect to performance and the use of system resources for variously defined workgroups by distributing users across available application servers based on requirements for workgroup service and utilization. Set up logon groups with transaction SMLG. The platform-independent SAP spool system is responsible for the output of forms and documents. All devices, servers, and so on that are involved in printing are defined and managed in spool administration, transaction SPAD. For more information refer to SAP Printing Guide in online documentation. The SAP system logs all system errors, warnings, and interesting information in the system log. Use transaction SM21 to access the system log output screen. Note: For details see course ADM100 - Administration AS ABAP I.
Client Copy SAPinst creates three ABAP clients during the installation, client 000, client 001, and client 066. Client 000 is the SAP reference client. Client 000 is the SAP reference client. It contains the SAP standard customizing settings. Client 000 can be used as a source for copying new clients. In addition client 000 is needed for certain administrative topics like applying SAP Support Packages, configuring TMS and so on. Client 001 can be used as the productive client. Client 001 is a copy of client 000. If you do not want to use client 001 as your productive client, you can delete it. Client 066 is the Early Watch client. It contains no application data and customizing. Client 066 can be used for logging on external users to the SAP system, for example to perform a performance analysis, without risking them seeing any of your data. In the seldom case of an AS ABAP + Java SAP system (should only be SAP PI and SAP Solution Manager), client 001 is configured as the partner client for the AS Java during the installation.
2012
© 2011 SAP AG. All rights reserved.
227
Unit 7: Performing Post-Installation Activities
TADM12_1
How is a new productive client created and filled with initial customizing data? 1. 2.
Log on to any client and maintain the new client within transaction SCC4 Activate kernel user SAP* •
3. 4.
Set the profile parameter login/no_automatic_user_sapstar to 0
• Restart the application server Log on to the new client with kernel user SAP* and password pass Copy reference client 000 to your new client with transaction SCCL, using copy profile SAP_UCUS Hint: Your initial productive client must be a copy of the SAP reference client 000.
5. 6.
7.
Check the log files with transaction SCC3 Create the required users. These users must have at least the authorizations required for user administration and system administration. Create a user SAP* with all required authorizations. If you want to have other users for system administration, you can also create user SAP* without authorizations. Deactivate kernel user SAP* • •
Reset profile parameter login/no_automatic_user_sapstar to 1, which is the installation default Restart the application server Note: For details see course ADM325 - Software Logistic AS ABAP.
Need for Installation Checks The installation check via transaction SICK checks the consistency of the newly installed SAP system. The following checks are performed: • • • • •
228
Completeness of installation Version compatibility between the SAP release and the operating system Accessibility of the message server Availability of all work process types Information about the enqueue server and the update service
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration for an AS ABAP based SAP System
Figure 99: Installation Checks
The consistency check determines inconsistencies in your SAP system. This function is also called automatically when you start your SAP system or start an application server. The installation check checks whether the following are true: • • •
The release number in the SAP kernel matches the release number stored in the database system. The character set specified in the SAP kernel matches the character set specified in the database system. The critical structure definitions defined in both the data dictionary and the SAP kernel are identical. The structures that are checked include structures SYST, T100, TSTC, TDCT, TFDIR, and others.
Install Additional Languages Depending on the release status, the SAP system supports up to 40 different languages. The language with which a user works is specified during logon by an entry on the logon screen, by a system default, or by a default setting in the user master record. Before users can log on with the desired language, this language must first be imported into the SAP system. After a new installation of an SAP system, only German (DE) and English (EN) are initially installed. You can use transaction SMLT to import additional languages, if desired. If you select a language (other than German, English, or Japanese), you should note that this language is not fully translated. The texts that are not translated in this language must be provided using a supplemental language. This supplemental
2012
© 2011 SAP AG. All rights reserved.
229
Unit 7: Performing Post-Installation Activities
TADM12_1
language must be a completely translated language. This can also be recursively configured so that you use a number of supplemental language, each of which supplements texts that are not translated in the previously configured languages. The extent to which individual languages need to be imported into the SAP system and the extent to which these are completely translated depends not only on economic, but also political and cultural criteria. User acceptance is an important aspect in these considerations.
Figure 100: Installing Additional Languages (1/3)
Language and translation: Only English •
In this case, the SAP system supports only English as a logon language and when printing. All reporting is done in English. All communication is performed in English. The problem of language-dependent objects does not arise and no costs are accrued for translations. The question here is not only whether the users have any problems with the English language, but also whether English language reporting, such as annual financial statements, are legally acceptable. This is therefore a solution for a relatively small number of countries that use English as an official language.
Language and translation: Mainly English •
230
In this case, it is assumed that the users have a command of English. They log on in English, and the menus and so on are also in English. However, reporting is done in the national language. If desired, language-dependent objects are translated. This requires a certain translation cost and a small amount of Customizing (for example, for units of measurement). The master data is available in the national language. Communication is also performed in the local national language.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration for an AS ABAP based SAP System
Language and translation: Some English •
This solution can be regarded as “Best Business Practice.” The master language of the system is English. However, users do not require significant knowledge of English. They log on in their local language, and can therefore use language-dependent objects, such as menus, input screens, and so on. Communication and all legally-relevant evaluations are also performed in the national language. Texts that are not translated are displayed using the supplemental language English. Depending on the level of translation of the language in question, there may be no translations in some areas. Additional texts can be translated, if desired. However, this is not necessary in many internal areas. There are periodic language supplements for newly generated texts. The standard tools are used for these. Manual translations remain manageable.
Language and translation: No English •
In this case, users have no knowledge of English or English is unacceptable due to political or cultural considerations. In this case, not only must the corresponding national language be imported, but all other required texts that have not been delivered translated must be translated manually. It is not possible to use English as a supplemental language. This means continual translation activity in a multilingual system. This is necessary even if the system is only operated in one language, as new language-dependent texts are imported into the SAP system with every SAP Support Package and every upgrade, and it may be necessary to translate these.
You can use transaction SMLT to import additional languages into an SAP system. The following figure shows an overview of the steps that are required for a language import. The following section describes the individual steps in more detail.
2012
© 2011 SAP AG. All rights reserved.
231
Unit 7: Performing Post-Installation Activities
TADM12_1
Figure 101: Installing Additional Languages (2/3)
Before you start the language import, you must configure the required languages using report RSCPINST. To do so, start report RSCPINST using transaction SA38 or I18N (area: I18N Menu → I18N Customizing → I18N System Configuration). In the left screen area, choose Add to select the country code for each language required and choose Simulation. If no further preparation is required, choose Activate. Hint: For more information about report RSCPINST, see SAP Note 42305 – RSCPINST (I18N configuration tool).
232
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration for an AS ABAP based SAP System
Figure 102: Installing Additional Languages (3/3)
SAP delivers SAP Support Packages to correct errors that occur in SAP transactions. SAP Support Packages can contain language-dependent data such as message texts, ABAP text pool entries, or screen texts. After importing an SAP Support Package with transaction SPAM, the translated texts for these objects have the newest status for all languages that exist in the system. Problems can occur if an additional language is to be imported from the language CD into a system in which SAP Support Packages have already been installed. Since the language CD is created before the first SAP Support Package is shipped, and the objects in the SAP Support Packages are only provided with translations for the languages that have already been imported, importing a language subsequently places the objects contained in the SAP Support Packages in an undefined status with regard to translation. Texts can be both obsolete, and therefore incorrect, or completely missing (see also SAP Note 352941). Since SAP Basis 4.6C, you can subsequently import the language data contained in the SAP Support Packages to achieve a consistent language status.
2012
© 2011 SAP AG. All rights reserved.
233
Unit 7: Performing Post-Installation Activities
TADM12_1
You must classify each language to make it known in the system. Only then is it possible to import a language package or supplement the language. 1. 2. 3.
In transaction SMLT, choose Language → Classify. In the dialog box that then appears, choose the language to be imported and the associated supplementation language. Note that you must define the languages imported (using transaction SMLT or by upgrading) in the instance profiles to be able to log on in the relevant languages. The parameter is zcsa/installed_languages.
You can display the current settings for a language at any time by choosing Information on the initial screen of transaction SMLT. If no supplementation language was specified when classifying a language, it is possible to do this at any time. You can use transaction SMLT to import an additional language package. English and German are always completely available in newly installed systems. You therefore do not need to import these into installed systems. After importing the languages, you must also import the language data in Support Packages. To do so, select the affected language in transaction SMLT and choose Language → Special Actions → Import Support Packages. To fill translation gaps that exist in a language, you should always start the language supplementation after the language import. The supplementation actions are client-dependent. The language supplementation is performed in the client in which you are logged on. If you use multiple clients, you must perform the language supplementation explicitly in each production client. You can access the texts stored in cross-client database tables simultaneously from all clients. The default setting is set in such a way that cross-client tables are supplemented if you are logged on in client 000. The following rules apply for defining supplementation logic: •
• •
234
Languages with a degree of translation of one cannot be supplemented. If, however, these languages need to be supplemented, see SAP Note 111750 – Supplementing German with English (Customizing) . You should define a supplementation language for every language in the system (except languages with a degree of translation of one). You can only supplement texts from a language with a degree of translation of one or from a language that has already been supplemented with a language with a degree of translation of one.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration for an AS ABAP based SAP System
Ensure that you take the following SAP Notes into account: • • • • • • • •
SAP Note 830722 – Current note for language transports in Release 7.0 SAP Note 73606 – Supported Languages and Code Pages SAP Note 15023 – Initializing table TCPDB (RSCP0004) (EBCDIC) SAP Note 18601 – Frequently asked questions on language import SAP Note 43853– Consulting: Language-dependent and client-specific Customizing SAP Note 195442 – Language import and Support Packages SAP Note 352941 – Consultation: Languages and Support Packages SAP Note 703795– Transaction UMB_CUST: Menu bar displays only ?????
See course ADM102 - Administration AS ABAP II for more information on importing languages.
Activation of Business Functions
Figure 103: Activation of Business Functions
2012
© 2011 SAP AG. All rights reserved.
235
Unit 7: Performing Post-Installation Activities
TADM12_1
Business Functions can be Enterprise Extensions, Industry Solutions or Enterprise Business Functions. Client-independent activation switches allow you to activate these functions. You activate the functions by selecting the relevant activation switch in the Switch Framework, transaction SFW5. Transaction SFW5 provides additional information about the business functions. After activating business functions, a batch job is started, that switches all objects belonging to the selected business function. Hint: Business functions are activated manually only in the development system. They are transported to the subsequent SAP systems, where they are imported. The import automatically starts the batch job for activating the individual object switches. Generally, you cannot deactivate an activated switch because after activation data is maintained in a different way than it would be if the switch was inactive. This depends on the component and the actions performed in the system after activation. Because you generally can not deactivate the switches, SAP recommends to activate and test the switches in a sandbox system before activating them in the development system.
SAP Load Generator After the installation of an SAP system, all ABAP programs and other objects are available as source code. When calling a transactions for the first time, all corresponding programs will be generated (compiled) automatically - their loads are being generated. But this can take several seconds of time. When calling the transaction the second time, these loads already exist and the transaction call is fast. To avoid the generating when calling a transaction for the first time, you can pre-generate programs and other objects. This can be done with the SAP Load Generator, transaction SGEN.
236
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration for an AS ABAP based SAP System
Figure 104: SAP Load Generator (SGEN)
You can use transaction SGEN to generate the ABAP loads of a number of programs, function groups, classes, and so on. You can choose wether you want to generate all objects from selected software components, or objects from the last run and so on. Before the generation starts, consecutive screens give you options about the: • • •
Task of the generation Selection of generation set (= number of objects to be generated) Use of parallel generation
The progress of the generation can be monitored on the SAP Load Generator Job Monitor screen. In addition, this screen gives you information about current generation jobs or jobs that may have already run, such as predictions about the duration of the generation.
2012
© 2011 SAP AG. All rights reserved.
237
Unit 7: Performing Post-Installation Activities
238
© 2011 SAP AG. All rights reserved.
TADM12_1
2012
TADM12_1
Lesson: Initial Configuration for an AS ABAP based SAP System
Exercise 11: Initial Configuration of an AS ABAP based SAP System Exercise Objectives After completing this exercise, you will be able to: • Perform initial post-installation activities for an AS ABAP based SAP system
Business Example You want to perform initial post-installation activities for an AS ABAP based SAP system.
Task 1: OPTIONAL: TMS Perform initial post-installation activities for an AS ABAP based SAP system. 1.
Perform post-installation actions in transaction SE06.
2.
Configure TMS.
Task 2: OPTIONAL: Profiles Import and change SAP profiles. 1.
Import all profiles into the SAP system.
2.
Change the values of the parameters related to the number of work processes (rdisp/wp_no_*). For example, enter twice the amount for dialog and batch work processes.
Task 3: OPTIONAL: Operation Modes Configure operation modes. 1.
Set up operation modes.
2.
Maintain a timetable for operation modes.
Task 4: OPTIONAL: Standard Jobs Check standard background jobs. 1.
Schedule the standard background jobs. Continued on next page
2012
© 2011 SAP AG. All rights reserved.
239
Unit 7: Performing Post-Installation Activities
TADM12_1
Task 5: SICK Installation check. 1.
Perform the installation check.
Task 6: OPTIONAL: Client Copy Perform a client copy. 1.
Create a new client in your SAP system.
Task 7: SGEN SAP Load Generator 1.
240
Start the SAP Load Generator and schedule it for tomorrow 8 PM.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration for an AS ABAP based SAP System
Solution 11: Initial Configuration of an AS ABAP based SAP System Task 1: OPTIONAL: TMS Perform initial post-installation activities for an AS ABAP based SAP system. 1.
Perform post-installation actions in transaction SE06. a)
2.
Proceed as described in the training material in section Post-Installation Activities for Transport Organizer. Use the setting Standard Installation. Do not select Database Copy or Database Migration.
Configure TMS. a)
Proceed as described in the training material in section Transport Management System (TMS) Configuration.
Task 2: OPTIONAL: Profiles Import and change SAP profiles. 1.
Import all profiles into the SAP system. a)
2.
Call the profile maintenance using transaction RZ10. You can import all profile files together by choosing Utilities → Import Profiles → Of active servers. A check log displays the result of the import.
Change the values of the parameters related to the number of work processes (rdisp/wp_no_*). For example, enter twice the amount for dialog and batch work processes. a)
To change the values of individual parameters, select the instance profile and change the profile parameters in extended maintenance.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
241
Unit 7: Performing Post-Installation Activities
TADM12_1
Task 3: OPTIONAL: Operation Modes Configure operation modes. 1.
2.
Set up operation modes. a)
Create operation modes in transaction RZ04.
b)
Choose Create and enter the name. Choose Save. Repeat this step one or more times with different names.
c)
Switch to the Instances/Operation Modes view by choosing Instances/Operation Modes.
d)
Define work process distribution for all instances of your system by choosing Settings → Based on current status → New instances → Create.
e)
To change the distribution of work processes for the operation modes of instances, double-click the operation modes entries. Change and then save the distribution of work processes in the Maintain Work Process Distribution window by choosing “+” and “-”. After you have changed the distribution for all operation modes and instances, choose Save.
Maintain a timetable for operation modes. a)
Schedule operation modes using the operation mode calendar using transaction SM63.
b)
Choose Normal Operation and Change. Select the start and end of the period of the operation mode by double-clicking the appropriate lines.
c)
Choose Assign and then select Operation mode. After you have assigned the entire 24 hour period to your operation modes, choose Save.
Task 4: OPTIONAL: Standard Jobs Check standard background jobs. 1.
Schedule the standard background jobs. a)
Choose transaction SM36 and choose Goto → Standard jobs. To schedule standard jobs, choose Default scheduling for SAP Component BC.
Continued on next page
242
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration for an AS ABAP based SAP System
Task 5: SICK Installation check. 1.
Perform the installation check. a)
Proceed as described in the training material in section Need for Installation Checks.
Task 6: OPTIONAL: Client Copy Perform a client copy. 1.
Create a new client in your SAP system. a)
Create a new client named 100. Proceed as described in the training material in section Client Copy.
Task 7: SGEN SAP Load Generator 1.
Start the SAP Load Generator and schedule it for tomorrow 8 PM. a)
2012
Proceed as described in the training material in section SAP Load Generator.
© 2011 SAP AG. All rights reserved.
243
Unit 7: Performing Post-Installation Activities
TADM12_1
Lesson Summary You should now be able to: • Describe the steps needed to configure the Transport Management System (TMS) • Describe the steps needed to configure profile parameters • Describe the steps to configure operation modes • Perform final installation checks • Describe how to activate SAP ECC Extensions • Start and schedule the SAP Load Generator (SGEN)
244
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration of an AS Java based SAP System
Lesson: Initial Configuration of an AS Java based SAP System Lesson Overview This lesson describes how to perform the initial configuration of an AS Java based SAP system. • •
Run the Configuration Wizard Verify the AS Java settings
Lesson Objectives After completing this lesson, you will be able to: • •
Run the Configuration Wizard Describe the steps to verify the AS Java configuration
Business Example You want to perform the initial configuration of an AS Java based SAP system.
Run the Configuration Wizard When you have installed an AS Java based SAP system, the Configuration Wizard makes technical settings which are required for the technical processing of a SAP system or a technical scenario, e.g. connectivity, service users, usage type initialization. You have to make the technical settings with the Configuration Wizard, immediately after installing an AS Java based SAP system. The configuration wizard is part of the SAP NetWeaver administrator. The SAP NetWeaver installation guide contains detailed information about which configuration tasks to choose. The Configuration Wizard makes the technical settings (technical configuration) using scenario-based templates, e.g. for the AS Java based part of an SAP Process Integration (PI) system, pure AS Java system, etc. Automated configuration tasks allow you to enter the same data centrally, once only, e.g. connectivity, service users, etc. The system distributes this data automatically to the AS Java based SAP system. You cannot use the configuration wizard after an SAP system upgrade, an Add-In installation and the installation of an additional usage type.
2012
© 2011 SAP AG. All rights reserved.
245
Unit 7: Performing Post-Installation Activities
TADM12_1
Caution: You can run the Configuration Wizard only once and only directly after you installed and patched the AS Java based SAP system.
Figure 105: Configuration Wizard
1. 2. 3.
Before you run the Configuration Wizard, make sure you have applied the latest kernel patch and SAP Support Packages to your system. Call http://:/nwa in a browser, and logon with a Java administrator user. Navigate to Deploy & Change tab and choose Configuration Wizard. Note: The SAP system displays the scenarios and their configuration tasks, according to your selection during the installation.
4. 5. 6. 7.
246
Select a task from the list and choose Start. Enter the required data and choose Next. Follow the screens. The Configuration Wizard makes the necessary settings. The Configuration Wizard reports any configuration errors.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration of an AS Java based SAP System
There are different configuration views available: •
All Configuration Tasks This view is displayed when you first enter the Configuration Wizard. It lists all configuration tasks available for your AS Java based SAP system.
•
NetWeaver Initial Configuration This view includes the configuration steps for all usage types you installed.
•
Interrupted Configuration Tasks If you cancelled a configuration and want to resume it later, choose the configuration task and then Resume
•
History of Executed Configuration Tasks This view lists all configuration tasks that have been executed previously.
For more information on the Configuration Wizard and its limitations, see SAP Note 923359.
Verifying the AS Java Configuration There are some recommended configuration procedures after you set up an AS Java based system. • • •
Create a second administrator user Check and configure the necessary communication ports Check additional configuration settings:
•
– parameters depending on the size of the AS Java based SAP system – parameters depending on the expected workload Configure security settings
To prevent locking the administrator in case you do change its password and forget to update the entry secure storage, we also recommend you create a second administrator user after installing an AS Java based SAP system. When you install an AS Java instance or create an additional server process, the AS Java assigns default values to the communication ports. In case some of these ports are being used by another program, you will have to manually assign a different value
2012
© 2011 SAP AG. All rights reserved.
247
Unit 7: Performing Post-Installation Activities
TADM12_1
to the corresponding port. If necessary, you can change the assigned join port of a server process, on which the server process listens for connections (for example, when the port assigned to the cluster element is already in use by another program). 1. 2. 3.
4.
Start the J2EE Engine Visual Administrator. Choose Server/Dispatcher → Kernel → Cluster Manager → Properties tab. Use element joinPort to specify the port on which the server process listens for connections. The port value must not be: greater than 65535, less than 1024, or a “well known” port. This property is available only on server processes. Choose Save to save your changes and restart the cluster node.
Additional Configuration The additional cluster configuration that you can perform can be divided into two types of configuration: •
Required configuration: This includes the configuration of some additional parameters depending on the size of the AS Java based SAP system, the expected workload, and so on. Although referred to as “required configuration”, we recommend that you maintain these settings only after careful consideration and testing. –
•
Connections manipulation – configure the maximum number of user connections that the dispatcher can handle simultaneously and a time-out for establishing these connections. – Setting service load timeout – configure the maximum time for which the services on a cluster node have to be started. Optional configuration: Perform the optional configuration only in case there are some problems within the AS Java based SAP system operation. Otherwise, we recommend that you do not reconfigure the default settings. –
– – –
248
Thread system configuration – to optimize the reallocation of SAP system resources, we recommend that you closely monitor and if necessary, reconfigure the AS Java based SAP system thread system. Startup and Shutdown – configure the manner in which the cluster elements will be started up and shut down. Configuring the cluster communication mechanisms - configuring the Message Server, Session and Lazy Communication Configuring the services stop and event time-outs
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration of an AS Java based SAP System
The management of client connections in the cluster is represented in AS Java based SAP systems by the connections manipulator manager. This connections Manipulator manager has an indirect connection with all services running on the dispatcher that receive or send data outside the cluster using a socket. Here you can configure the maximum number of user connections that a dispatcher will be able to process at a certain moment, a time-out for these connections, and the connections checks. Go to the service manager to change the maximum time for which all services on a cluster node have to be started. If there are still services that have not started after this timeout elapses, the service manager assumes that all services are started and the SAP system continues with the other startup processes. The timed-out services will continue their startup process in the background. A notification for each timed-out service is logged in the log files. The AS Java thread system is responsible for handling SAP system and client threads. It comprises two managers – thread manager and application thread manager. All threads in which AS Java based SAP system operations are executed (core, services, and so on) use system threads supplied by the thread manager. The application thread manager supplies the threads in which the client application’s code is executed. Use the cluster manager to configure the cluster to work in the manner of a full parallelism, or to set its startup/shutdown to be serialized. For your configuration purposes, use the properties provided by the AS Java cluster manager. By default, the cluster elements start up and shut down in full parallelism mode, that is, simultaneously, without waiting for each other. Message server communication is established through the message server that is used as a dispatcher when sending messages. The advantage of this way of communication is that it provides a fail-over function that avoids the loss of information. The cluster manager provides properties to configure the default settings of the message server communication. Session communication is used to exchange information between the dispatcher and a server in one cluster group. The cluster manager provides properties to modify the default settings of the session communication The lazy communication mechanism is used automatically by the cluster manager to quickly exchange large amounts of information between two server processes without using the message server as an intermediary. By default, lazy communication
2012
© 2011 SAP AG. All rights reserved.
249
Unit 7: Performing Post-Installation Activities
TADM12_1
is enabled only for a predefined list of services. You can enable a mechanism by which lazy communication is activated when a previously defined amount of objects is transferred between two parties for a defined time interval. Hint: We recommend that you do not modify the default message server communication, the default session communication and the default lazy communication settings unless you are officially advised to do so by SAP support. The service stop time-out in the service manager is responsible for the maximum time which the service manager waits for each service to stop when the cluster node is shutting down. If this time-out has elapsed and the service has not managed to stop, the service manager continues with the cluster node shutdown. A notification for each timed-out service is logged in the log files. The event time-out in the service manager specifies the time that the service manager waits for the event to be processed before undertaking another action. If you want to stop a service, a beforeServiceStopped event is thrown first. Then it waits for all components to process the event. That is, the components are notified that the service will be stopped and they should undertake the appropriate actions, such as unregistration, and so on. After the specified time-out, the service is stopped. The default value of the event time-out is 20 seconds. If after 20 seconds there are still components that have not processed the event, the system will not wait for them and the service will be stopped. We recommend modifying this value only if you have problems stopping the service. Otherwise, we recommend that you do not reconfigure the default time-out.
Configuring Security Configuring security – you may also need to configure some additional aspects of the server’s security environment. Providing security for the applications that run on the AS Java based SAP system is also an important aspect in the overall architecture of the AS Java based SAP system. You need to be able to identify the users that access the server and you need to protect access to individual resources. In addition, confidentiality is also important when dealing with sensitive information. To configure the server’s security environment, use the following services in the Visual Administrator: •
Security Provider Service The security provider service is the primary service needed for maintaining the server’s security environment. Use this service to: –
250
Choose cryptographic providers
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration of an AS Java based SAP System
•
– Select the data source – Maintain users and groups – Assign security roles – Restrict access to resources – Set up your login modules to use – Maintain protection domains – Monitor user sessions User Storage Service The security provider service uses the user storage service to determine and access the chosen data source, either the DBMS user store or the UME. There are no administration tasks directly associated with this service, however you can change the properties that apply.
•
Key Storage Service Use the key storage service to maintain the server’s personal security information where cryptography is supported, for example, when using the SSL protocol. You can create the server’s key pairs, generate the corresponding certificate signing requests, and maintain the list of trusted Certification Authorities (CAs) associated with the key pair.
•
SSL Provider Service Use this service to select the key pair that the server is to use for SSL. If you are using client certificates for user authentication, then you also maintain the list of CAs who you trust as issuers of client certificates.
•
Certificate Revocation Check Service With the AS Java based system, you can use certificate revocation lists (CRLs) to make sure that a given certificate has not been revoked by the issuing Certificate Authority (CA).
•
SAML Authentication Service This service handles the user authentication for applications that use the Security Assertion Markup Language (SAML). It requests the SAML assertions from the corresponding SAML source site for a user and processes them.
•
Secure Storage Service Use this service to maintain the AS Java based system’s secure storage area, which is a storage area on the server that applications or services can use to store security-critical information such as passwords. Data stored in this area is encrypted and can only be accessed and decrypted by the corresponding application.
2012
© 2011 SAP AG. All rights reserved.
251
Unit 7: Performing Post-Installation Activities
•
TADM12_1
Destination Service Applications or services can establish connections to other services. When using such connections, you need to specify the remote service’s address and the user authentication information to use for the connection. Many applications use the Destination service for this purpose.
252
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Initial Configuration of an AS Java based SAP System
Lesson Summary You should now be able to: • Run the Configuration Wizard • Describe the steps to verify the AS Java configuration
2012
© 2011 SAP AG. All rights reserved.
253
Unit 7: Performing Post-Installation Activities
TADM12_1
Lesson: Appendix: Installation of Standalone SAP Gateway Lesson Overview This appendix describes the installation of a standalone SAP Gateway.
Lesson Objectives After completing this lesson, you will be able to: •
Install a standalone SAP Gateway instance
Business Example You want to install a standalone SAP Gateway instance.
Appendix: SAP Gateway Instance Installation In some cases it is useful to install a standalone SAP Gateway instance. For example when using standard cross system SAP processes from, for example, an SAP ECC system. These cross system standard scenarios often are implemented via Remote Function Call (RFC). For example, for HR reasons (time registration) you are using a third party software to read the access cards of the employees when entering and leaving the company . This information has to be transferred to your SAP ECC (HR) system to be processed. Assuming that the time registration software is not RFC enabled, you can install a standalone SAP Gateway instance on the host of this software. Now the time registration software can communicate with the SAP Gateway instance, for example, via TCP/IP. And within your SAP ECC system you can use the standard RFC based scenarios to communicate via the standalone SAP Gateway with the time registration software.
254
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Appendix: Installation of Standalone SAP Gateway
Figure 106: Installation of SAP Gateway Instance 1/4
To install a standalone SAP Gateway, start SAPinst from the SAP Enhancement Package 5 for SAP ERP 6.0 Installation Master DVD and navigate to SAP NetWeaver 7.0 including Enhancement Package 2 → Standalone Engines → Gateway → Gateway Installation.
2012
© 2011 SAP AG. All rights reserved.
255
Unit 7: Performing Post-Installation Activities
TADM12_1
Figure 107: Installation of SAP Gateway Instance 2/4
Choose G## as SAP system ID, G: as installation drive and Master## as the master password. Whereby ## stands for your two digit group number. Provide the requested DVD, which is available at G:\ADM110_col72 on your installation host.
256
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Appendix: Installation of Standalone SAP Gateway
Figure 108: Installation of SAP Gateway Instance 3/4
Change the instance number as described on the slide and start the installation process. Hint: The installation of the standalone SAP Gateway instance takes only a few minutes.
2012
© 2011 SAP AG. All rights reserved.
257
Unit 7: Performing Post-Installation Activities
TADM12_1
Figure 109: Installation of SAP Gateway Instance 4/4
Congratulations! You have successfully installed an SAP Gateway instance.
258
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Appendix: Installation of Standalone SAP Gateway
Lesson Summary You should now be able to: • Install a standalone SAP Gateway instance
Related Information •
2012
For more details see the installation guide for SAP Gateway installation at SAP Service Marketplace, Quick Link instguides.
© 2011 SAP AG. All rights reserved.
259
Unit Summary
TADM12_1
Unit Summary You should now be able to: • List relevant post installation steps • Explain how to complete the installation of SAP Enhancement Package 5 for SAP ERP 6.0 • Explain how to apply a kernel patch • Explain how to apply a SAP Support Package for AS ABAP based SAP systems • Explain how to apply a SAP Support Package for AS Java based SAP systems • Explain what an SAP Support Package Stack is • Describe the steps to install an SAP license • Describe the steps to install the SAP online documentation • Describe the steps to install and configure the SAProuter • Describe the steps needed to configure the Transport Management System (TMS) • Describe the steps needed to configure profile parameters • Describe the steps to configure operation modes • Perform final installation checks • Describe how to activate SAP ECC Extensions • Start and schedule the SAP Load Generator (SGEN) • Run the Configuration Wizard • Describe the steps to verify the AS Java configuration • Install a standalone SAP Gateway instance
260
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Test Your Knowledge
Test Your Knowledge 1.
What is the procedure to perform a full backup for Windows?
2.
SAP Enhancement Package 5 for SAP ERP 6.0 is installed using transaction SAINT. Determine whether this statement is true or false.
□ □
2012
True False
3.
What are the steps to manually apply a kernel patch?
4.
Name the two major steps to install SAP online documentation.
5.
What is the need for SAProuter?
© 2011 SAP AG. All rights reserved.
261
Test Your Knowledge
6.
TADM12_1
After the installation of the central instance, no user can log on to the SAP system until a permanent license is installed. Determine whether this statement is true or false.
□ □ 7.
True False
SAProuter can be started as a demon under UNIX and as a service under Windows. Determine whether this statement is true or false.
□ □ 8.
True False
Identify the activity that is not performed by Installation Check. Choose the correct answer(s).
□ □ □ □ 9.
A B C D
Completeness of installation Version compatibility Accessibility of the message server Network security
What are the steps needed to install additional languages?
10. What are the steps needed to perform a client copy?
11. Immediately after a new installation all ABAP programs are available as source code including their load. Determine whether this statement is true or false.
□ □
262
True False
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Test Your Knowledge
12. The installation check checks, among others, whether the release number in the SAP kernel matches the one stored in the database system. Determine whether this statement is true or false.
□ □
True False
13. You have installed an AS Java based SAP system. Which tool makes technical settings which are required for the technical processing of a system or a technical scenario? Choose the correct answer(s).
□ □ □ □
2012
A B C D
Template Wizard Configuration Wizard Postinstaller Configuration Template Installer
© 2011 SAP AG. All rights reserved.
263
Test Your Knowledge
TADM12_1
Answers 1.
What is the procedure to perform a full backup for Windows? Answer: 1. 2. 3.
2.
Save the Registry. Save system state data. Back up all SAP specific and database related directories.
SAP Enhancement Package 5 for SAP ERP 6.0 is installed using transaction SAINT. Answer: False SAP Enhancement Package 5 for SAP ERP 6.0 is implemented using the SAP Enhancement Package Installer (SAPehpi).
3.
What are the steps to manually apply a kernel patch? Answer: 1. 2. 3.
4.
Stop the SAP system (Windows OS: including Windows services). Copy and paste the kernel patch to the central kernel directory. Start the SAP system (Windows OS: first start the Windows services).
Name the two major steps to install SAP online documentation. Answer: Install the help files and customize setup variants for online help.
5.
What is the need for SAProuter? Answer: SAProuter increases network security, simplifies network configuration, and allows you to make indirect network connections. SAProuter is required for remote support connections.
264
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Test Your Knowledge
6.
After the installation of the central instance, no user can log on to the SAP system until a permanent license is installed. Answer: False After the installation of the central instance, a temporary license is active for four weeks. During this time, users can log on to the SAP system.
7.
SAProuter can be started as a demon under UNIX and as a service under Windows. Answer: True SAProuter is started as a demon under UNIX and as a service under Windows. This allows to start SAProuter automatically after a restart of your server.
8.
Identify the activity that is not performed by Installation Check. Answer: D The SAProuter software, from the standard SAP kernel, can increase network security.
9.
What are the steps needed to install additional languages? Answer: 1. 2. 3.
Classifying the language. Scheduling of language transport/import. Scheduling of language supplementation.
10. What are the steps needed to perform a client copy? Answer: 1. 2. 3.
2012
Maintain the client in transaction SCC4. Copy the client. Check the log files.
© 2011 SAP AG. All rights reserved.
265
Test Your Knowledge
TADM12_1
11. Immediately after a new installation all ABAP programs are available as source code including their load. Answer: False Immediately after a new installation all ABAP programs are available as source code only. You can use transaction SGEN to generate the ABAP loads of a number of programs, function groups, and classes after installation. 12. The installation check checks, among others, whether the release number in the SAP kernel matches the one stored in the database system. Answer: True The installation check determines inconsistencies in the SAP system. 13. You have installed an AS Java based SAP system. Which tool makes technical settings which are required for the technical processing of a system or a technical scenario? Answer: B The Configuration Wizard is responsible for technical settings after the installation of an AS Java based SAP system which are required for the technical processing of a system or a technical scenario, e.g. connectivity, service users, usage type initialization.
266
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
267
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
268
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit 8 Installation of SAP GUI Unit Overview In this unit you will learn how to install an SAP GUI manually and via SAP GUI Installation Server.
Unit Objectives After completing this unit, you will be able to: • • • • • • •
Describe the different types of SAP GUIs Perform a local SAP GUI for Windows installation Patch a local SAP GUI for Windows Install a local SAP GUI for Java Perform an SAP GUI Installation Server installation Create an SAP GUI installation package Perform an unattended SAP GUI installation using the SAP GUI Installation Server
Unit Contents Lesson: Installation of SAP GUI for Windows and SAP GUI for Java ....... 270 Exercise 12: Installing SAP GUI for Windows and SAP GUI for Java... 281 Lesson: Installation and Usage of SAP GUI Installation Server .............. 286 Exercise 13: OPTIONAL: Installing SAP GUI for Windows from an SAP GUI Installation Server ......................................................... 299
2012
© 2011 SAP AG. All rights reserved.
269
Unit 8: Installation of SAP GUI
TADM12_1
Lesson: Installation of SAP GUI for Windows and SAP GUI for Java Lesson Overview This lesson explains how to install and patch an SAP GUI for Windows. Additionally you will find information about the installation of an SAP GUI for Java. A local SAP GUI is installed during this lesson. The lesson also explains how to patch an SAP GUI for Windows.
Lesson Objectives After completing this lesson, you will be able to: • • • •
Describe the different types of SAP GUIs Perform a local SAP GUI for Windows installation Patch a local SAP GUI for Windows Install a local SAP GUI for Java
Business Example You want to install and patch a local SAP GUI.
Variants of the SAP GUI The use of SAP GUI is supported on many different operating systems. The operating systems support is provided by the different variants of the SAP GUI. The different types of SAP GUI are listed in the following figure:
270
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP GUI for Windows and SAP GUI for Java
Figure 110: Variants of the SAP GUI
There are three classical SAP GUI variants to access AS ABAP based SAP systems: • • •
The SAP GUI for Windows The SAP GUI for HTML The SAP GUI for Java Hint: There is no special SAP GUI to access AS Java based SAP systems. Caution: Don't get mixed up: the SAP GUI for Java has nothing to do with AS Java based SAP systems! With the SAP GUI for Java you access AS ABAP based SAP systems!
Certain other options to access SAP systems are not covered here: SAP Portal interfaces, such as iViews, Business Explorer (BEx) to access SAP BW systems, and many more. The SAP GUI for HTML requires either the Internet Transaction Server (ITS, available up to basis release 6.40) or the integrated Internet Transaction Server (part of the ICM, available since basis release 6.40) to provide access to an SAP system. The activation and publishing of the SAP GUI for HTML is not part of this course.
2012
© 2011 SAP AG. All rights reserved.
271
Unit 8: Installation of SAP GUI
TADM12_1
One common aspect of the SAP GUI for Windows and the SAP GUI for Java is that both GUIs use the DIAG and RFC protocol to communicate with AS ABAP based SAP systems. These protocols requires a very small bandwidth, reducing network load. You will find more SAP GUI-related information on the SAP Developer Network SAP Developer Network, at irj/sdn/sap-gui.
Manual Installation of an SAP GUI for Windows Installation files for SAP GUI for Windows are located on one of the presentation DVDs. Navigate to G:\ADM110_col72\DVDs\EHP5_ERP_6.0\NETWEAVER_7.0_Presentation_4\NW_7.0_Presentation\PRES1\GUI\WINDOWS\WIN32 and start the installation by choosing SetupAll.exe.
Figure 111: Manual Installation of SAP GUI for Windows (1/2)
Select some SAP GUI components as shown on the slide.
272
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP GUI for Windows and SAP GUI for Java
Figure 112: Manual Installation of SAP GUI for Windows (2/2)
Select an installation directory on drive G: for the local installation of the SAP GUI. After you choose Next the installation starts. On the last screen choose Finish. Hint: As of SAP GUI for Windows 7.10 patch 11 the new Signature design is delivered. To activate it, choose Start → Programs → SAP Frontend → SAP GUI Configuration and select the option Use Signature Design.
2012
© 2011 SAP AG. All rights reserved.
273
Unit 8: Installation of SAP GUI
TADM12_1
Manually Patching SAP GUI for Windows
Figure 113: Patching SAP GUI for Windows (1/4)
You can determine the versions for SAPLogon.exe, SAPGUI.exe, and Front.exe as described on the slide.
274
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP GUI for Windows and SAP GUI for Java
Figure 114: Patching SAP GUI for Windows (2/4)
Start the GUI patch by executing gui720_-.EXE found in the directory G:\ADM110_col72\SAPgui_Patches, if available.
2012
© 2011 SAP AG. All rights reserved.
275
Unit 8: Installation of SAP GUI
TADM12_1
Figure 115: Patching SAP GUI for Windows (3/4)
After applying the patch, you sometimes have to restart your front end computer because some essential DLLs were exchanged.
276
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP GUI for Windows and SAP GUI for Java
Figure 116: Patching SAP GUI for Windows (4/4)
After the patch is applied, control the new patch level of the components.
Steps to Install SAP GUI for Java The SAP GUI for Java requires that a Java Runtime Environment (JRE) is installed. For more information on the Java JRE version, please read the documentation shipped with the SAP GUI for Java.
2012
© 2011 SAP AG. All rights reserved.
277
Unit 8: Installation of SAP GUI
TADM12_1
Figure 117: Installing SAP GUI for Java
Installation files for SAP GUI for Java are located on one of the presentation DVDs. Navigate to G:\ADM110_col72\DVDs\EHP5_ERP_6.0\NETWEAVER_7.0_Presentation_5\NW_7.0_Presentation\PRES2\GUI\JAVA and start the installation by choosing the appropriate PlatinGUI_.JAR file (e.g. for Windows PlatinGUI720Windows_4.JAR).
278
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP GUI for Windows and SAP GUI for Java
Figure 118: Configuration of SAP GUI for Java
You can find the configuration details of the SAP GUI for Java in the documentation. The documentation is available on the presentation DVD and also installed together with the SAP GUI for Java. To access the documentation choose Help → SAPGUI Help in the SAP GUI for Java window. To obtain information about the version of the SAP GUI for Java in use, choose Help → About SAPGUI. In addition to the manual installation, SAP GUI for Java 7.20 also supports silent installation. For more information see section Installation from the documentation of SAP GUI for Java.
2012
© 2011 SAP AG. All rights reserved.
279
Unit 8: Installation of SAP GUI
280
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP GUI for Windows and SAP GUI for Java
Exercise 12: Installing SAP GUI for Windows and SAP GUI for Java Exercise Objectives After completing this exercise, you will be able to: • Manually install SAP GUI for Windows • Manually patch SAP GUI for Windows • Manually install SAP GUI for Java
Business Example You want to manually install and patch an SAP GUI for ABAP and install an SAP GUI for Java.
Task 1: Installing SAP GUI for Windows Manually install an SAP GUI for Windows on your installation host. 1.
Start SetupALL.exe from folder G:\ADM110_col72\DVDs\EHP5_ERP_6.0\NETWEAVER_7.0_Presentation_4\NW_7.0_Presentation\PRES1\GUI\WINDOWS\WIN32. Install the SAP GUI on drive G:. Choose some SAP GUI components of your choice to be installed. The components should contain at least SAP GUI with SAP Logon.
Task 2: Patching SAP GUI for Windows Raise the patch level of your freshly installed SAP GUI for Windows. Note: There may be no higher patch level available yet. In this case you can skip this exercise. 1.
Check the current patch level of your SAP GUI components.
2.
Patch the SAP GUI for Windows you installed in task 1 of this exercise. You find the patch to be applied in folder G:\ADM110_col72\SAPgui_Patches.
3.
Check the new patch level of your SAP GUI components.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
281
Unit 8: Installation of SAP GUI
TADM12_1
Task 3: OPTIONAL: Installing SAP GUI for Java Install an SAP GUI for Windows on your installation host. 1.
Install SAP GUI for the Java environment. You find the installation files in folder G:\ADM110_col72\DVDs\EHP5_ERP_6.0\NETWEAVER_7.0_Presentation_5\NW_7.0_Presentation\PRES2\GUI\JAVA. Proceed as described in the training material.
282
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP GUI for Windows and SAP GUI for Java
Solution 12: Installing SAP GUI for Windows and SAP GUI for Java Task 1: Installing SAP GUI for Windows Manually install an SAP GUI for Windows on your installation host. 1.
Start SetupALL.exe from folder G:\ADM110_col72\DVDs\EHP5_ERP_6.0\NETWEAVER_7.0_Presentation_4\NW_7.0_Presentation\PRES1\GUI\WINDOWS\WIN32. Install the SAP GUI on drive G:. Choose some SAP GUI components of your choice to be installed. The components should contain at least SAP GUI with SAP Logon. a)
Follow the steps as described in this lesson Installation of SAP GUI for Windows and SAP GUI for Java for details.
Task 2: Patching SAP GUI for Windows Raise the patch level of your freshly installed SAP GUI for Windows. Note: There may be no higher patch level available yet. In this case you can skip this exercise. 1.
Check the current patch level of your SAP GUI components. a)
2.
Patch the SAP GUI for Windows you installed in task 1 of this exercise. You find the patch to be applied in folder G:\ADM110_col72\SAPgui_Patches. a)
3.
Follow the steps as described in this lesson Installation of SAP GUI for Windows and SAP GUI for Java for details.
Follow the steps as described in this lesson Installation of SAP GUI for Windows and Java for details.
Check the new patch level of your SAP GUI components. a)
Follow the steps as described in this lesson Installation of SAP GUI for Windows and SAP GUI for Java for details.
Task 3: OPTIONAL: Installing SAP GUI for Java Install an SAP GUI for Windows on your installation host. 1.
Install SAP GUI for the Java environment. You find the installation files in folder G:\ADM110_col72\DVDs\EHP5_ERP_6.0\NETWEAVER_7.0_Presentation_5\NW_7.0_Presentation\PRES2\GUI\JAVA. Continued on next page
2012
© 2011 SAP AG. All rights reserved.
283
Unit 8: Installation of SAP GUI
TADM12_1
Proceed as described in the training material. a)
284
Follow the steps as described in this lesson Installation of SAP GUI for Windows and SAP GUI for Java for details.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation of SAP GUI for Windows and SAP GUI for Java
Lesson Summary You should now be able to: • Describe the different types of SAP GUIs • Perform a local SAP GUI for Windows installation • Patch a local SAP GUI for Windows • Install a local SAP GUI for Java
2012
© 2011 SAP AG. All rights reserved.
285
Unit 8: Installation of SAP GUI
TADM12_1
Lesson: Installation and Usage of SAP GUI Installation Server Lesson Overview This lesson explains how to install and use the SAP GUI Installation Server (for Windows). The SAP GUI Installation Server will be installed during this lesson.
Lesson Objectives After completing this lesson, you will be able to: • • •
Perform an SAP GUI Installation Server installation Create an SAP GUI installation package Perform an unattended SAP GUI installation using the SAP GUI Installation Server
Business Example You want to install an SAP GUI Installation Server.
Installing the SAP GUI Installation Server When installing SAP GUI for Windows on several workstations, it is recommended to use a SAP GUI Installation Server. The server-based installation is flexible and makes maintenance easier, for example, when patches have to be applied.
286
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation and Usage of SAP GUI Installation Server
Figure 119: SAP GUI Server Installation and Configuration
The manual installation and update of SAP GUI for Windows on every front-end is very time consuming. Using the SAP GUI installation server you can save time during the installation and update procedure. SAP delivers all necessary installation and configuration files. They can be found on one of the Presentation DVDs. The following screen shots explain how to setup a SAP GUI Installation Server. It is recommended that you read the instructions in the SAP front-end installation guide, which can be found on one of the Presentation DVDs G:\ADM110_col72\DVDs\EHP5_ERP_6.0\NETWEAVER_7.0_Presentation_4\NW_7.0_Presentation\PRES1\DOCU\SAP_Front_End_Installation_Guide.pdf, before starting the installation. Follow these steps to install the SAP GUI Installation Server. On the Presentation DVD, start NwCreateInstServer.exe in G:\ADM110_col72\DVDs\EHP5_ERP_6.0\NETWEAVER_7.0_Presentation_4\NW_7.0_Presentation\PRES1\GUI\WINDOWS\WIN32\setup directory.
2012
© 2011 SAP AG. All rights reserved.
287
Unit 8: Installation of SAP GUI
TADM12_1
Figure 120: Installing an SAP GUI Installation Server (1/4)
Note that a prerequisite for using the SAP GUI Installation Server is the installation of Microsoft .NET Framework Runtime v2.0. Any other version of .NET framework is not supported. See also SAP Note 1057666 - NW SAPSetup - List of Bugfixes. Browse to a folder to which you want to install the SAP GUI Installation Server. You can create a new folder during this process.
288
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation and Usage of SAP GUI Installation Server
Figure 121: Installing an SAP GUI Installation Server (2/4)
Share the installation folder and verify it before executing the next step.
2012
© 2011 SAP AG. All rights reserved.
289
Unit 8: Installation of SAP GUI
TADM12_1
Figure 122: Installing an SAP GUI Installation Server (3/4)
Now all files will be put into the shared folder. After the installation finished, you can work from the share. The Presentation DVD is not needed any longer.
290
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation and Usage of SAP GUI Installation Server
Figure 123: Installing an SAP GUI Installation Server (4/4)
Directly after the installation the administration tool (NwSapSetupAdmin.exe) opens up and you can begin your work.
Patching the SAP GUI Installation Server After the SAP GUI Installation Server has been installed, it should be patched using the standard SAP GUI patches found on the SAP Service Marketplace, Quick Link patches). The following figures will explain the patching of the SAP GUI Installation Server. Start program NwSapSetupAdmin.exe located in the setup directory of your SAP GUI Installation Server folder.
2012
© 2011 SAP AG. All rights reserved.
291
Unit 8: Installation of SAP GUI
TADM12_1
Figure 124: Patching the SAP GUI Installation Server (1/2)
Choose Patch Server and browse to the patch file.
292
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation and Usage of SAP GUI Installation Server
Figure 125: Patching the SAP GUI Installation Server (2/2)
Confirm all screens and wait until the patching is done. Afterwards the administration tool will open up and you can control the patch level. When you now install a SAP GUI Installation Package on a front-end PC where SAP GUI is already installed, it will only install the patched files.
Creating a SAP GUI Installation Package After installation and patching of the SAP GUI Installation Server, you can start to define new SAP GUI installation packages. Afterwards these SAP GUI installation packages can be distributed to the front-end PCs. Use NwSAPSetupAdmin.exe to create new SAP GUI installation packages for the SAP GUI for Windows.
2012
© 2011 SAP AG. All rights reserved.
293
Unit 8: Installation of SAP GUI
TADM12_1
Figure 126: Creating an SAP GUI Installation Package (1/3)
Choose New Package and select the GUI components you would like to install with this SAP GUI installation package.
294
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation and Usage of SAP GUI Installation Server
Figure 127: Creating an SAP GUI Installation Package (2/3)
Choose a name for your SAP GUI installation package.
2012
© 2011 SAP AG. All rights reserved.
295
Unit 8: Installation of SAP GUI
TADM12_1
Figure 128: Creating an SAP GUI Installation Package (3/3)
You can now install the SAP GUI installation package on the front-end PCs by executing a script, for example when the user logs on to his front-end PC. The content of the SAP GUI installation package can be changed later on.
Installing an SAP GUI Installation Package The just created SAP GUI installation package can now be used to perform an unattended installation.
296
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation and Usage of SAP GUI Installation Server
Figure 129: Installing an SAP GUI Installation Package
You can start the unattended installation of an SAP GUI installation package by running the following command: \\\\Setup\NwSAPSetup.exe /Silent /Package=“” for example, \\twdf0000\GUIServer\Setup\NwSAPSetup.exe /Silent /Package=“SAP GUI only” You can carry out unattended installations and automatic patch deployment on the front-end PC. To do this, place the appropriate NwSAPSetup.exe command line in the logon script of the front-end PC. The logon script is a program that is executed when you log on to your front-end PC. See the Help of the SAP GUI Installation Server to get detail information on the possible command lines. There is also the possibility to provide an Distribution Service which makes it possible to do front-end installations without having administrative rights. See Configuring Local Security Handling in the documentation of the SAP GUI Installation Server for more information.
2012
© 2011 SAP AG. All rights reserved.
297
Unit 8: Installation of SAP GUI
298
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation and Usage of SAP GUI Installation Server
Exercise 13: OPTIONAL: Installing SAP GUI for Windows from an SAP GUI Installation Server Exercise Objectives After completing this exercise, you will be able to: • Install an SAP GUI for Windows from an SAP GUI Installation Server
Business Example You want to install an SAP GUI for Windows from an SAP GUI Installation Server.
Task: Installing SAP GUI for Windows from the SAP GUI Installation Server Install an SAP GUI for Windows from the SAP GUI Installation Server. Don't start a manual installation. Use the SAP GUI installation package defined by your trainer and start the SAP GUI installation on your installation host. Start the SAP Logon on your installation host.
2012
1.
Start the installation of SAP GUI for Windows from the SAP GUI Installation Server of your trainer and use the installation package defined by your trainer. The installation should be performed on your installation host.
2.
Start SAP Logon on your installation host.
© 2011 SAP AG. All rights reserved.
299
Unit 8: Installation of SAP GUI
TADM12_1
Solution 13: OPTIONAL: Installing SAP GUI for Windows from an SAP GUI Installation Server Task: Installing SAP GUI for Windows from the SAP GUI Installation Server Install an SAP GUI for Windows from the SAP GUI Installation Server. Don't start a manual installation. Use the SAP GUI installation package defined by your trainer and start the SAP GUI installation on your installation host. Start the SAP Logon on your installation host. 1.
Start the installation of SAP GUI for Windows from the SAP GUI Installation Server of your trainer and use the installation package defined by your trainer. The installation should be performed on your installation host. a)
Logon to operating system of your installation host. Navigate to Start → Run and enter \\\\Setup\NwSAPSetup.exe /package=. Your instructor will provide you with the appropriate information.
2.
Start SAP Logon on your installation host. a)
300
Use the SAP Logon icon on your desktop to start SAP Logon.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Installation and Usage of SAP GUI Installation Server
Lesson Summary You should now be able to: • Perform an SAP GUI Installation Server installation • Create an SAP GUI installation package • Perform an unattended SAP GUI installation using the SAP GUI Installation Server
2012
© 2011 SAP AG. All rights reserved.
301
Unit Summary
TADM12_1
Unit Summary You should now be able to: • Describe the different types of SAP GUIs • Perform a local SAP GUI for Windows installation • Patch a local SAP GUI for Windows • Install a local SAP GUI for Java • Perform an SAP GUI Installation Server installation • Create an SAP GUI installation package • Perform an unattended SAP GUI installation using the SAP GUI Installation Server
302
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Test Your Knowledge
Test Your Knowledge 1.
Which of the following is not a classical GUI variant to access an SAP ECC system? Choose the correct answer(s).
□ □ □ □ 2.
A B C D
Business Explorer SAP GUI for Windows SAP GUI for HTML SAP GUI for Java
The SAP GUI Installation Server can be used to install all types of SAP GUIs (SAP GUI for Windows, SAP GUI for Java, SAP GUI for HTML). Determine whether this statement is true or false.
□ □
2012
True False
© 2011 SAP AG. All rights reserved.
303
Test Your Knowledge
TADM12_1
Answers 1.
Which of the following is not a classical GUI variant to access an SAP ECC system? Answer: A You can use the Business Explorer (BEx) to access SAP NetWeaver BW systems.
2.
The SAP GUI Installation Server can be used to install all types of SAP GUIs (SAP GUI for Windows, SAP GUI for Java, SAP GUI for HTML). Answer: False The SAP GUI Installation Server can only trigger the installation and update of SAP GUI for Windows.
304
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
305
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
306
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
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
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
Section 2: The Application of SP-Stack 28 to your newly installed SAP Solution Manager 7.0 Enhancement Package 1 system (and more): SAP Patch Day: Consisting of SUB-STEPS 1 to 13 In case you installed a secondary instance to your SAP Solution Manager system S00, please shut down this additional instance now. More reading for preparation: The SP-Stack Guide: http://service.sap.com/~form/sapnet?_SHORTKEY=011000358700006599 46&_OBJECT=011000358700001041312011E
recommends the following approach:
© SAP AG 2012
TADM12_1
15
We will consider this recommendation in the following. At least, as far as possible (especially step 3.). For optimum performance, we will also consider: SAP Note 1309506 - SPAM/SAINT with parallel R3trans https://service.sap.com/sap/support/notes/1309506
SAP Note 569116 Release strategy for Solution Manager Service Tools (ST-SER) recommends to implement: ST-SER 701_2010_1 for SAP Solution Manager 7.0 Enhancement Package 1 Delivery: 30-April-2010 ST Release: ST 400 Support Package 23 ST-PI Release: ST-PI 2008_1_700 Support Package 02 ST-SER Release: ST-SER 701_2008_2 Procedure: Add-on upgrade using SAINT Notes: 608277, 892412 as well.
© SAP AG 2012
TADM12_1
16
Therefore, we will use transaction SAINT to apply the SAP Support Packages and the Add-On in one step.
What components will we patch? In the order of the following list: (It’s an OVERVIEW, don’t do anything based on the following list, observe the detailed notes given later in this document): 1.
Patch the database, in our case: MaxDB. This might improve performance for further patch activities; therefore we execute this step rather early.
2.
Patch the SAP Snap-In of the Microsoft Management Console. This could be done later, but takes only seconds, so why not.
3.
Apply latest SPAM/SAINT update
4.
Set parallel r3trans option. This will improve the performance of the patch activity.
5.
Patch SAP GUI. This could be done later, but takes only seconds, so why not.
6.
Include “patches into stack” (JSPM option). This will shorten the duration of the patch activity.
7.
Patch the Java SDK: SAP Note 716604: Access to Oracle J2SE and recommended J2SE options tells us (on December 7th, 2011):
It tells us as well:
8.
Here follow the recommendation of the SP-Stack Guide (above) Patch JSPM (JSPM) Patch the Kernel (JSPM)
© SAP AG 2012
TADM12_1
17
9.
Apply a valid licence and Import Essential SAP Notes PREPARE the patch process by: applying a valid license applying some essential SAP Notes
10. Start the Patch AS Java (JSPM)
this Patch will finish first
Patch AS ABAP (SAINT, because of ST-SER and others). in parallel. 11. Additional Kernel Patch (optional) 12. Switch to SAP JVM (optional) 13. Update the Content of the SLD (optional)
© SAP AG 2012
TADM12_1
18
1.
Patch the database (MaxDB) Shutdown the SAP System Shutdown SAP MaxDB Start: ...\TADM12_1_72_Patch_Day\01_MaxDB__7_7_07_39\maxdb-serverwin-64bit-x86_64-7_7_07_39 SDBUPD.exe in a DOS-box.
Including the shutdown activities (SAP System, Database) the patch activity for MaxDB takes about
10 minutes.
2.
Patch the SAP Snap-In of the Microsoft Management Console using ...\TADM12_1_72_Patch_Day\02_SAP_MMC_720_12 sapmmc_12-20005871.msi old:
New:
The patch activity for SAP MMC takes about
5 minutes
© SAP AG 2012
TADM12_1
19
3.
Apply latest SPAM/SAINT update Before Patch:
Use ...\TADM12_1_72_Patch_Day\03_SPAM_SAINT\EPS\in CSN0120061532_0054780.PAT You will encounter an error. Simply start SPAM again and continue applying the update. This is no unusual error. After Patch:
The patch activity for SPAM/SAINT takes about
10 minutes 4.
Set in SPAM:
5.
Patch SAP GUI Use ...\TADM12_1_72_Patch_Day\04_SAP_GUI_Patch_720_09 gui720_9-10007878.exe old:
new:
The patch activity for SAP GUI takes about
5 minutes
© SAP AG 2012
TADM12_1
20
6.
Set /jspm/includePatchesInStack = true in \usr\sap\S00\DVEBMGS00\j2ee\JSPM\deploy\param\ jspm_config.txt
as described in Task 5 of Exercise 19 of TADM12_1. This activity takes about
5 minutes 7.
Patch the Java SDK Stop the SAP system Stop the database (you will need to reboot the server!) Update the existing Java SDK using the installation file provided at: ..\TADM12_1_72_Patch_Day\05_1_4_2_34_x64 j2sdkfb-1_4_2_34-windows-amd64.exe old:
Execute the file named above.
© SAP AG 2012
TADM12_1
21
An error might occur:
Retry: It runs Change the installation path:
to:
This is your original Java SDK-directory. Result:
Reboot your server. new:
Within the training environment it might be necessary to provide the password to the SAP services, using the user SAPService. This is unusual behavior and should not occur. See step 11 from the preparatory steps. Including the reboot and service user password adaptation and DB and system restart, this (optional) activity takes about
25 minutes
© SAP AG 2012
TADM12_1
22
8.
Follow the recommendation of the SP-Stack Guide (above) Copy the files from: ..\TADM12_1_72_Patch_Day\06_SP_Stack_28\EPS\in to G:\usr\sap\trans\EPS\in It’s about 18GB, so it is a good idea to have a break. Patch the Kernel (JSPM)
Set all components to “skip”,
except for the Kernel and JSPM itself:
Proceed
© SAP AG 2012
TADM12_1
23
Proceed by exit and restarting JSPM. Deploy the new kernel version.
Including the copy activity and the several steps in JSPM (incl. restarting JSPM), this activity takes about
50 minutes. 9.
This step has already been done earlier during TADM12_1. Apply a valid licence and Import Essential SAP Notes Go to SPAM You will encounter this error:
We need to apply a license. The very special license used for this training allows the application of SAP Support Packages. How to apply the license? Switch to transaction “SLICENSE”
Choose “New Licenses”.
© SAP AG 2012
TADM12_1
24
Choose “Install” Select the file named to you by your instructor. Likely: …\TADM12_1_72_Patch_Day S00_multiple.txt Result:
Got to transaction SPAM again, no warning occurs now. If you try to define a queue, only consisting of SAP_BASIS SPs (according to the SP Stack Guide), the following information will be shown:
This means: the application of SAP_BASIS Support Packages (alone) is not possible. We need to use transaction SAINT.
© SAP AG 2012
TADM12_1
25
Read on, don’t proceed in SAINT until completing the following steps. VERY IMPORTANT! Before proceeding with the SP-Stack application, we need to consider the following SAP Note 822379: Known problems with Support Packages in SAP NW 7.0x AS ABAP Go to transaction SNOTE. Download the following SAP Notes:
Apply the notes, start with the one on top then work to bottom. The following procedure might vary during the actual course, because SAP Notes could have been updated since the writing of this guide. In this course, always confirm with “yes”:
Always confirm:
© SAP AG 2012
TADM12_1
26
Create your own, new Workbench request:
Confirm:
Confirm:
© SAP AG 2012
TADM12_1
27
Confirm:
Repeat this step with the other SAP Notes. For the second note in the list, you will encounter this pop up:
Because this include is being used in the context of both main programs, it is not important which one you choose for the “activation step” in SNOTE. You can choose “SAPLSDMA” (or the other). For the third note in this list, you will encounter the pop up:
It is important to download and implement this note as well. Please confirm. Next, you can confirm this queue:
Choose:
(Install)
© SAP AG 2012
TADM12_1
28
Confirm the next steps until this pop up:
The same as above applies. You can choose “RADMASG0”. Proceed as usual with the next SAP Note. When encountering:
choose the first program from the list. For the next SAP Note, when encountering:
Choose the first program of the list. For the last note, no special activities need to be observed ☺ Release your workbench request via SE09.
© SAP AG 2012
TADM12_1
29
10.
Now go to transaction SAINT Start JSPM right after the step named below – “The import will start (hours since start import: 00:00)” Choose “Start”:
Choose “Load” and confirm the next windows:
Until you reach this one:
Choose “Stack XML file” and select the Stack XML file (stack.xml)
© SAP AG 2012
TADM12_1
30
provided here: …\TADM12_1_72_Patch_Day\06_SP_Stack_28
Choose “Continue” on this window:
© SAP AG 2012
TADM12_1
31
Choose “Continue” on this window:
Choose “No”:
© SAP AG 2012
TADM12_1
32
Enter the four passwords given below in their sequence into the entry fields:
8058D78A99 565C531308 52A2843078 52A2843171 Confirm your entries. Choose “Import” on this screen:
© SAP AG 2012
TADM12_1
33
The import will start (hours since start import: 00:00):
Release your transport request (from SNOTE) via SE09, otherwise you will encounter (hours since start import: 00:30):
RUNNING (Now jump to the patch activities involving JSPM, see below) At time (hours since start import: 04:00) the following error might occur:
© SAP AG 2012
TADM12_1
34
The log:
Further error messages (SM21, ST22) imply that something like a timeout happened. “Continue” in SAINT. Errors like this happen. At (hours since start import: 08:00):
© SAP AG 2012
TADM12_1
35
© SAP AG 2012
TADM12_1
36
In parallel to SAINT, start JSPM (after doing all interactive SAINT work): Not “Stack” but “Single” – only for this course! Usually, SAP recommends applying “Support Package Stacks”.
Take care that the kernel patch is not applied now (should have been done earlier) otherwise a system restart will occur bad for SAINT. The JSPM update will require another restart of JSPM, therefore has also been done earlier.
© SAP AG 2012
TADM12_1
37
After about 15 minutes:
After about 30 Minutes:
DONE with JSPM, continue observing SAINT (see above)
© SAP AG 2012
TADM12_1
38
After finishing SAINT and JSPM: After another “regeneration of existing loads” via SGEN (strongly optional), the database would grow (to about 65 GB):
One more patch to go: Start SPAM, Define queue, Select “all components”, Select the following SP:
Choose “Calculate Queue”, Confirm
Select “No” “Import queue” About 3 minutes later:
DONE!
© SAP AG 2012
TADM12_1
39
Now you could proceed with working on the following topics: Use SGEN again: Execute additional load creation for BSP Applications and Web Dynpros later as well:
You can plan these steps in parallel to other work. Doing a backup Report “RTCCTOOL” Report “RSECNOTE” Report “RSUSR003” Transaktion “SOLMAN_SETUP” Apply SAP Note 1635809: SAP Solution Manager - Basic function SP 28 or higher You should do the SGEN step, especially for Web Dynpro and BSP applications, the other steps won’t be executed in TADM12_1.
© SAP AG 2012
TADM12_1
40
In TADM12_1 we proceed with some smaller topics. 11. If you like you can execute another, manual, kernel patch (optional). Before Patch:
Stop your SAP system. Copy the content from G:\usr\sap\S00\SYS\exe\uc\NTAMD64 to another “Copy (2) of NTAMD64” (now you could delete the old “Copy” that you created earlier):
After the SAP system has stopped: Copy the content of …\TADM12_1_72_Patch_Day\07_Patches_after_Stack\ Kernel_not_included_in_06_SP_Stack_28\uncompressed to: G:\usr\sap\S00\SYS\exe\uc\NTAMD64 Confirm “yes to all” twice. Start your system again.
© SAP AG 2012
TADM12_1
41
12. Switch from Oracle’s Java SDK to SAP JVM! (optional) Open the PDF (sapjvm_switch_win.pdf) located at: …\TADM12_1_72_Patch_Day\09_SAP_JVM_Switch_Tool_optional
It says:
The switch tool is already extracted: …\TADM12_1_72_Patch_Day\08_SAP_JVM_Switch_Tool_optional\ SAPJVMSWITCH00 Please take note:
Next:
Time 00:00h Wait for some activities to finish.
© SAP AG 2012
TADM12_1
42
Confirm path to profile directory:
Choose “Next”. Enter the password, choose “Next”:
Select the correct file, choose “Next”: Located at: …\TADM12_1_72_Patch_Day\08_SAP_JVM_Switch_Tool_optional SAPJVM4_13-10009724.SAR
Provide the path to the JCE … archive, choose “Next”:
© SAP AG 2012
TADM12_1
43
You can confirm the transferred parameters, choose “Next”:
Confirm the next parameters as well:
and again:
Choose “Next”. Maybe several times. Don’t worry. Leave as default:
Choose “Next”. Confirm the parameter summary:
© SAP AG 2012
TADM12_1
44
Switch in progress:
After about 00:15h:
Check via http://twdfxxxx.wdf.sap.corp:50000/monitoring/SystemInfo:
© SAP AG 2012
TADM12_1
45
13. Now update the SLD content (optional): http://twdfxxxx.wdf.sap.corp:50000/webdynpro/dispatcher/sap.com/tc~sld~wd~main/Main
Import cimsap61610_0-20006535.zip from …\TADM12_1_72_Patch_Day\09_SLD_Patches_optional
Also import cimsap71606_0-20008269.zip:
Import CRDelta41514_0-10006428.ZIP:
© SAP AG 2012
TADM12_1
46
09:45h – 10:34h:
Import CRDelta51509_1-20005942.ZIP: 10:35h – 11:10h
Import CRDelta61610_0-20006535.ZIP Fix the following error:
According to SAP Note 1326081: SLD import error: "Posted content length exceeds limit” 1. Click the "Administration" link. 2. Choose "Profile". 3. Choose the section "WebUI". 4. Add the parameter "MaxUploadSizeMB" as required with the value (default value: "20" for 20 MB). Set to 40 (MB)!
5. Choose "Save" to save your changes.
© SAP AG 2012
TADM12_1
47
It will look like this:
Continue the import
Import CRDelta71606_0-20008269.ZIP: etc. The updates will take a long time. My recommendation is: don’t do this during TADM12_1. Done
© SAP AG 2012
TADM12_1
48
Unit 9 “SAP Patch Day” Unit Overview This unit deals with maintaining SAP software using Kernel Patches, SAP Notes, Support Packages and Support Package Stacks.
Unit Objectives After completing this unit, you will be able to: • • • • • • • • • • • • •
Explain how to apply a kernel patch Explain how to apply a SAP Support Package for AS ABAP based SAP systems Explain how to apply a SAP Support Package for AS Java based SAP systems Explain what an SAP Support Package Stack is Describe the concept of SAP Notes and Support Packages Explain the concept of maintenance certificates Describe a maintenance transaction Explain the use of the Support Package Manager and import a SPAM/SAINT update. Import Support Packages with transaction SPAM Provide a general explanation of the import process for Support Packages Install Support Packages for SAP NetWeaver Application Server Java-based systems List other tools involved in the software lifecycle management environment Understand the idea of SAP enhancement packages
Unit Contents Lesson: Patching SAP Systems .................................................. 309 Exercise 14: Applying a Kernel Patch ....................................... 323 Lesson: SAP Notes and Support Packages..................................... 326 Exercise 15: Implementing an SAP Note with the Note Assistant ....... 331
2012
© 2011 SAP AG. All rights reserved.
307
Unit 9: “SAP Patch Day”
TADM12_1
Lesson: Preparation for Software Maintenance ................................ 335 Exercise 16: Execute a Maintenance Transaction ......................... 347 Lesson: Support Package Manager (SPAM).................................... 353 Exercise 17: Support Package Manager (SPAM) .......................... 357 Lesson: Importing Support Packages ............................................ 362 Exercise 18: Import Support Packages...................................... 371 Lesson: Importing Corrections .................................................... 377 Exercise 19: Applying Corrections ........................................... 391 Lesson: Other Tools in Software Lifecycle Management ...................... 402 Lesson: Enhancement Packages................................................. 410
308
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
Lesson: Patching SAP Systems Lesson Overview This lesson explains how to apply patches, such as kernel patches, SAP Notes and SAP Support Packages for AS ABAP and AS Java based SAP systems.
Lesson Objectives After completing this lesson, you will be able to: • • • •
Explain how to apply a kernel patch Explain how to apply a SAP Support Package for AS ABAP based SAP systems Explain how to apply a SAP Support Package for AS Java based SAP systems Explain what an SAP Support Package Stack is
Business Example You want to apply patches to your SAP system.
SAP Support Package Stacks SAP recommends that you keep your SAP systems up to date by regularly applying SAP Notes, SAP Support Packages and SAP Kernel Patches. This patching is becoming more and more a challenge by the complexity of the SAP system landscapes. Types of patches for an AS ABAP based SAP system: • •
• •
2012
SAP Note: contains the correction or enhancement of a single repository object, for example some coding lines for a program SAP Support Package: contains a bundle of objects and customizing for one single software component to be exchanged - for correction or for legal reasons, sometimes to deliver new functionality Kernel patch: contains a bundle of kernel elements, such as executables or libraries SAP Support Package stack: bundle of SAP Support Packages and a kernel patch that have been tested by SAP for side effects
© 2011 SAP AG. All rights reserved.
309
Unit 9: “SAP Patch Day”
TADM12_1
Types of patches for an AS Java based SAP system: • • • •
Patch: contains a bundle of corrections SAP Support Package: contains a complete software component Kernel patch: contains a bundle of kernel elements, such as executables or libraries SAP Support Package stack: bundle of SAP Support Packages and a kernel patch that have been tested by SAP for side effects Note: An AS ABAP Support Package is not the equivalent to an AS Java Support Package! An AS ABAP Support Package is a subset of a software component, an AS Java Support Package is the full delivery of a software component.
Because SAP systems have more and more software components and because SAP system landscapes consist of more and more SAP systems, Hint: SAP recommends to apply complete SAP Support Package stacks rather than an individual combination of SAP Support Packages. An SAP Support Package stack also contains a installation guide for the SAP Support Package stack. You should read this guide and the corresponding SAP Notes before applying the SAP Support Package stack.
310
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
Figure 130: SAP Note, Patch, SAP Support Package, SAP Support Package Stack
In older SAP releases you could download SAP Support Package stacks from SAP Service Marketplace, Quick Link sp-stacks. This is not possible any longer, since SAP is shipping new software components via SAP enhancement packages. For these newer releases it is mandatory to use the SAP Solution Manager Maintenance Optimizer. The Maintenance Optimizer calculates an individual SAP Support Package stack for your SAP system, lays the necessary patches in your download basket and approves your download basket. You can than download your download basket with the Download Manager to the SAP system's host. Now you can apply the patches.
2012
© 2011 SAP AG. All rights reserved.
311
Unit 9: “SAP Patch Day”
TADM12_1
Figure 131: Calculating SAP Support Package Stacks with Maintenance Optimizer
312
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
Steps to Apply AS ABAP SAP Support Packages Using Transaction SPAM
Figure 132: Apply AS ABAP SAP Support Packages Using Transaction SPAM
The usage of transaction SPAM is explained in great detail in the courses ADM100 – Administration AS ABAP I and ADM325 - Software Logistic for AS ABAP. The screen shots remind you how to apply AS ABAP SAP Support Packages.
Steps to Apply AS Java SAP Support Packages Using JSPM You can use the Java Support Package Manager (JSPM) to apply AS Java SAP Support Packages. With JSPM you can also deploy SAP and third-party software components to your AS Java based SAP system. You can also deploy new business packages of the SAP Business Suite. You can also upgrade and update business packages of SAP Business Suite that are deployed on the AS Java based SAP system to a higher release. In addition, JSPM detects SAP software components that have been modified and allows you to apply SAP Support Packages to them.
2012
© 2011 SAP AG. All rights reserved.
313
Unit 9: “SAP Patch Day”
TADM12_1
JSPM has the following features: • • •
Overview of deployed components Update of kernel binaries, Software Deployment Manager (SDM), Internet Graphics Server (IGS), and JSPM Deployment of: – – – – – –
AS Java SAP Support Package stack single AS Java SAP Support Packages SAP and third-party software components deploy and upgrade business packages of SAP Business Suite detects modified software components and transports them for deployment to SAP NetWeaver Development Infrastructure (NWDI) informs you if restarting of the AS Java is necessary during the deployment process Hint: Only operating system user adm can use JSPM.
Make sure that all SAP Support Packages to be applied are copied into the JSPM inbox. The JSPM inbox is a file system directory and resides at DIR_EPS_ROOT/in. DIR_EPS_ROOT/in is a profile parameter and can be defined in the central instance profile. The SAP Support Packages for the kernel and other OS level binaries are delivered as SAR files. Make sure that your current SAPCAR tool is able to extract these files.
314
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
Figure 133: JSPM: AS Java SAP Support Package 1/2
2012
© 2011 SAP AG. All rights reserved.
315
Unit 9: “SAP Patch Day”
TADM12_1
Figure 134: JSPM: AS Java SAP Support Package 2/2
The use of tool JSPM is explained in great detail in the course ADM200 – Administration AS Java. The screen shots remind you how to apply AS Java SAP Support Packages.
Steps to Apply a Kernel Patch Depending on your installed SAP system you can use the Java tool JSPM (Java Support Package Manager) or the manual procedure to do an update of the kernel. • •
316
manual update: For all SAP system based on AS ABAP (only), for example, SAP ECC, SAP BW, SAP CRM server update with JSPM: For all system based on AS Java (including AS ABAP + AS Java system), for example, SAP Portal, SAP XSS, SAP Solution Manager
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
Manual Update When you apply a kernel patch manually, make sure that the following prerequisites are met: • •
SAP system is stopped On Windows, the SAP services, including SAPOsCol, are stopped.
When applying a kernel patch with JSPM, the SAP system has to stopped also, of course. But you don't have to stop it manually, JSPM does the stopping and starting.
Figure 135: AS ABAP: Show Patch Levels Kernel, SAP Support Packages, and Database Release
The screenshots show the content of the System → Status of an AS ABAP based SAP system. To update the kernel, follow the instructions given in the SAP Support Package stack guide. This guide can be found at SAP Service Marketplace, Quick Link instguides under, for example, SAP NetWeaver → SAP NetWeaver 7.0 → Maintenance. Note: Usually applying a kernel patch manually is just stopping the SAP system, copy and paste the kernel patch, restart the SAP system.
2012
© 2011 SAP AG. All rights reserved.
317
Unit 9: “SAP Patch Day”
TADM12_1
As of SAP NetWeaver 7.0 and related SAP systems, SAP introduces a new directory structure to improve the support of mixed platform configurations. The new directory structure is only created during new installations. SAP Note 919046 Upgrade to the New Instance-Specific Directory Structure describes how to configure upgraded SAP systems to the new directory structure. Hint: The new kernel structure applies only for SAP systems installed on Windows operating system with SAP NetWeaver 7.0 and related SAP systems. For SAP systems installed on other operating systems, the new kernel structure comes with SAP NetWeaver 7.10 and related SAP systems. The new directory structure consists of the following major changes: •
• •
•
318
The directory \\sapglobalhost\sapmnt\SAPSID\sys\exe\run on the central instance is replaced with \\sapglobalhost\sapmnt\\sys\exe\\ whereby is UC for Unicode Systems, or NUC for non-Unicode systems, and is NTI386 (for 32 Bit Windows), NTAMD64 (for Windows X86_64), or NTIA64 (for Windows IA64 executables). The directory \\sapglobalhost\sapmnt\\sys\exe\runU used by the AS Java Add-in instances is replaced by \\sapglobalhost\sapmnt\\sys\exe\UC\ The central instance uses an instance-specific executable directory (\\sapglobalhost\saploc\\DVEBMGS##\exe, whereby ## is the instance number). An instance should not directly use \\sapglobalhost\sapmnt\\SYS\exe\run
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
Figure 136: Applying a Kernel Patch Manually (1/2)
2012
© 2011 SAP AG. All rights reserved.
319
Unit 9: “SAP Patch Day”
TADM12_1
Figure 137: Applying a Kernel Patch Manually (2/2)
In the screenshots, you see that you will replace kernel files in the directory \usr\sap\\SYS\exe\uc\NTADM64. The success of the kernel patch can be seen at System → Status.
Apply Kernel Update using JSPM Starting with SAP NetWeaver 7.0, the Java Support Package Manager (JSPM) is used for applying SAP Support Packages and kernel patches to AS Java based SAP systems. Additionally JSPM can update JSPM itself and all installed AS Java based usage types in the AS Java based SAP system.
320
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
Figure 138: Apply a Kernel Patch using JSPM
Steps to Apply a Database Patch • • • • •
Download the latest database patch from SAP Service Marketplace, Quick Link patches to your SAP host. Follow SAP Note 735598 - Importing MaxDB software as of 7.5.00 to install patches for MaxDB. Follow, for example, SAP Note 1363170 - DB6: Installing fix packs for DB2 9.7 (Windows) for DB2 UDB; Follow SAP Note 62988 - Service Packs for Microsoft SQL Server and related SAP Notes to install Service Packs for Microsoft SQL Server. Follow, for example, SAP Note 839182 - Installing patches using OPatch to install patches for Oracle 10.2 and 11.2.
Because different database releases might have different patch strategies, please check SAP Service Marketplace, Quick Link instguides and go to Other Documentation → Database Upgrades.
2012
© 2011 SAP AG. All rights reserved.
321
Unit 9: “SAP Patch Day”
TADM12_1
There are different procedures to apply patches to the different databases supported by SAP systems. When applying patches, you will notice that databases from the same vendor can differ significantly between releases. As a result, ensure that you are using the patch description that fits your database release. In addition, check the SAP Notes in the figure before applying a database patch. The content of the SAP Notes might have been revised. For DB2 on iSeries, go to http://www.4soi.de/IBM-Infoapars.php. For DB2 on zSeries, follow the instructions on how to fix the operating system. SAP Note 81737 lists the operating system fixes that should be applied in an SAP environment.
322
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
Exercise 14: Applying a Kernel Patch Exercise Objectives After completing this exercise, you will be able to: • manually apply a kernel patch • apply a kernel patch with JSPM
Business Example You want to apply a kernel patch.
Task 1: AS ABAP: Apply a Kernel Patch Manually Manually apply a kernel patch to your SAP ECC system. 1.
Check the current kernel patch level of your SAP ECC system and apply the kernel patch, provided at G:\ADM110_col72\Kernel_Patch_720_AS_ABAP_unpacked. Afterwards check the result. Caution: Copy the old kernel to a backup folder before you patch it.
Task 2: OPTIONAL: AS Java: Apply a Kernel Patch with JSPM Apply a Kernel patch using JSPM to your SAP XSS system. 1.
2012
Copy the kernel patch from G:\ADM110_col72\Kernel_Patch_720_AS_Java to your EPS inbox G:\usr\sap\trans\EPS\in and apply the kernel patch using JSPM with option Single Support Packages.
© 2011 SAP AG. All rights reserved.
323
Unit 9: “SAP Patch Day”
TADM12_1
Solution 14: Applying a Kernel Patch Task 1: AS ABAP: Apply a Kernel Patch Manually Manually apply a kernel patch to your SAP ECC system. 1.
Check the current kernel patch level of your SAP ECC system and apply the kernel patch, provided at G:\ADM110_col72\Kernel_Patch_720_AS_ABAP_unpacked. Afterwards check the result. Caution: Copy the old kernel to a backup folder before you patch it. a)
Follow the steps described on the slides of this lesson.
Task 2: OPTIONAL: AS Java: Apply a Kernel Patch with JSPM Apply a Kernel patch using JSPM to your SAP XSS system. 1.
Copy the kernel patch from G:\ADM110_col72\Kernel_Patch_720_AS_Java to your EPS inbox G:\usr\sap\trans\EPS\in and apply the kernel patch using JSPM with option Single Support Packages. a)
324
Follow the steps described on the slide of this lesson.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Patching SAP Systems
Lesson Summary You should now be able to: • Explain how to apply a kernel patch • Explain how to apply a SAP Support Package for AS ABAP based SAP systems • Explain how to apply a SAP Support Package for AS Java based SAP systems • Explain what an SAP Support Package Stack is
2012
© 2011 SAP AG. All rights reserved.
325
Unit 9: “SAP Patch Day”
TADM12_1
Lesson: SAP Notes and Support Packages Lesson Overview This lesson provides an introduction to the subject of SAP Notes and Support Packages.
Lesson Objectives After completing this lesson, you will be able to: •
Describe the concept of SAP Notes and Support Packages
Business Example You want to import adjustments (made in response to changes in legal requirements) into your SAP system. You also want to correct bugs that may be in the SAP software. SAP provides SAP Notes and Support Packages for this purpose.
SAP Notes and Support Packages An SAP system comprises various software components. These software components receive regular updates through SAP Notes and Support Packages. SAP Notes and Support Packages are used to import adjustments based on changes in legal requirements. They are also used to correct errors in the standard SAP software and to enhance existing functions or make minor new functions available. The SAP system should always have the most recent Support Package level, to comply with legal requirements and to eliminate errors.
326
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: SAP Notes and Support Packages
Figure 139: SAP Notes and Support Packages
SAP Notes can contain general information, hints and tips, or recommendations from SAP. They can also describe a problem and the solution to errors in standard functions of the SAP software. This type of SAP Note contains the solution to an individual problem, which is often the solution to a programming error, in the form of corrected lines of source code. Support Packages are bundles of repository objects and Customizing. In principle, each software component and each release level has its own Support Packages. In the case of software components that intersect (with modified add-ons, for example), there is an additional type of Support Package, the Conflict Resolution Transport (CRT). Technically speaking, Support Packages are a kind of transport request that cannot be imported as a normal transport request, however. A Support Package contains all known, relevant SAP Notes that have been created since the last Support Package for the corresponding software component. It can also contain new Customizing and Customizing that has been corrected since the last Support Package. Support Packages are not cumulative, but are based on their predecessors. In principle, importing Support Packages for one particular software component is independent of the level of Support Packages of other software components. The individual components are in general independent of one another. However, there can be cases where the importing of individual Support Packages leads to side-effects.
2012
© 2011 SAP AG. All rights reserved.
327
Unit 9: “SAP Patch Day”
TADM12_1
Importing an SAP_HR Support Package can require the previous import of a SAP_BASIS Support Package, or an SAP_APPL Support Package, for example. As soon as they have been identified, these side-effects are documented in a composite SAP Note that is referenced when importing Support Packages. Hint: If a maintenance transaction in SAP Solution Manager - Maintenance Optimizer is used to determine the Support Packages, known dependencies are also highlighted there. To enable patches to be implemented consistently in different software components, SAP recommends you import Support Packages using Support Package Stacks. Support Package Stacks are recommended combinations of Support Packages of different software components. Support Package Stacks are not alternative, special patches, but recommended combinations of normal Support Packages. Support Package Stacks are available for the various SAP systems. In addition to Support Packages, they mostly contain recommendations for patching other components, such as kernel patches for patching the ABAP runtime environment. The problem of how to patch a complex landscape frequently arises, as well as the question of how to actually use the Support Package Stack for orderly, documented patching. What is the current patch status of my system landscape? Where can I find the necessary Support Packages and the Support Package Stack information? The Maintenance Optimizer (MOpz) as part of SAP Solution Manager provides the solution to these questions. With the Maintenance Optimizer, you can request the Support Package Stacks required for the systems of your landscapes defined in SAP Solution Manager in a controlled and manageable way. Note: The Maintenance Optimizer is mandatory for some Support Packages, such as the Support Packages for SAP ECC 6.0 and above, which have been available since April 2007.
Note Assistant Support Packages are imported with the Support Package Manager (transaction SPAM). SAP Notes are implemented with the Note Assistant (transaction SNOTE).
328
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: SAP Notes and Support Packages
Figure 140: Note Assistant
The Note Assistant is called with the transaction SNOTE. It has been part of the standard system since Basis release 6.10. In earlier releases, you can make it available by importing it as an additional software component, as an add-on. The current version of the Note Assistant can implement various types of SAP Notes: Changes to SAP programs, the creation of new SAP programs, changes to SAP function modules and several other types of repository objects can be handled. It cannot, however, change Dictionary objects, for example. Furthermore, the Note Assistant can only change repository objects, not Customizing, for example.
2012
© 2011 SAP AG. All rights reserved.
329
Unit 9: “SAP Patch Day”
TADM12_1
The Note Assistant implements SAP Notes as follows: 1.
2. 3.
4. 5. 6. 7.
330
You have to localize the required SAP Notes on the SAP Service Marketplace, for example, by searching for keywords or selecting the unique SAP Note number, if you know it. You can then load these SAP Notes to the development system with the Note Assistant (transaction SNOTE). The SAP Notes are checked by the Note Assistant here. It checks whether the release named in the SAP Note and the Support Package level are correct, whether the SAP Note requires other SAP Notes as predecessors, whether it can be implemented due to other modifications that may exist for the affected repository object, and so on. The SAP Note is implemented by choosing the Implement SAP Note button. This creates a transport request. The result of implementing the SAP Note is roughly tested in the development system. If this test is successful, the resulting transport request is imported into the quality assurance system. The quality assurance test is performed here. If this is also successful, the transport request is imported into the production system.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: SAP Notes and Support Packages
Exercise 15: Implementing an SAP Note with the Note Assistant Exercise Objectives After completing this exercise, you will be able to: • Implement an SAP Note with the Note Assistant
Business Example To correct the coding of an SAP object, you want to implement an SAP Note. Caution: The SAP Note is implemented into the DEV system with the Note Assistant. Later on it could be imported into the QAS system with the Transport Management System (TMS). So the QAS groups work together with their partner DEV groups in the corresponding DEV system.
Task 1: Download and check an SAP Note Download the SAP Note given by the instructor with the Note Assistant from SAP Service Marketplace. Afterwards check, if the SAP Note can be implemented. 1.
Download the SAP Note.
2.
Check the downloaded SAP Note.
Task 2: Implement the downloaded SAP Note Implement the downloaded SAP Note with the Note Assistant.
2012
1.
Implement the SAP Note.
2.
Complete the SAP Note implementation.
© 2011 SAP AG. All rights reserved.
331
Unit 9: “SAP Patch Day”
TADM12_1
Solution 15: Implementing an SAP Note with the Note Assistant Task 1: Download and check an SAP Note Download the SAP Note given by the instructor with the Note Assistant from SAP Service Marketplace. Afterwards check, if the SAP Note can be implemented. 1.
2.
Download the SAP Note. a)
Log on to your DEV system, client 100 and start transaction SNOTE.
b)
Download the SAP Note by choosing Goto -> Download SAP Note. Enter the SAP Note number and choose Execute.
Check the downloaded SAP Note. a)
Select the SAP Note and choose the Check SAP Note button. You can find the SAP Note in the New folder. Confirm the popup with Continue.
Task 2: Implement the downloaded SAP Note Implement the downloaded SAP Note with the Note Assistant. 1.
Implement the SAP Note. a)
Select the SAP Note and use the Set Processing Status button to set the processing status to In Processing.
b)
Select the SAP Note and choose the Implement SAP Note button. You can find the SAP Note in the In Processing folder. Confirm that you have read the SAP Note with Yes.
c)
Confirm the popup about the repairs with Continue. Press the Create Request button in the Prompt for transportable Workbench request popup. Enter a short description for the transport request and create the transport request by choosing the Save button. Press Continue to confirm the Prompt for transportable Workbench request popup.
d)
Confirm the Confirm Changes popup with Continue. Activate any inactive items by confirming the Inactive Objects for ... popup with Continue.
Continued on next page
332
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: SAP Notes and Support Packages
2.
2012
Complete the SAP Note implementation. a)
The SAP Note is implemented now. If you are satisfied with the result in the DEV system, select the SAP Note and use the Set Processing Status button to set the processing status to Completed.
b)
The next steps would be to release the corresponding transport request via transaction SE09 in the DEV system and to import the transport request into the QAS system. Here it would be tested. After a positive test result the transport request can be imported into the PRD system. Imports are done via transaction STMS. But transporting and testing is not part of this exercise.
© 2011 SAP AG. All rights reserved.
333
Unit 9: “SAP Patch Day”
TADM12_1
Lesson Summary You should now be able to: • Describe the concept of SAP Notes and Support Packages
334
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Preparation for Software Maintenance
Lesson: Preparation for Software Maintenance Lesson Overview This lesson discusses the use of the SAP Solution Manager - Maintenance Optimizer (MOpz) to request Support Packages within a maintenance transaction.
Lesson Objectives After completing this lesson, you will be able to: • •
Explain the concept of maintenance certificates Describe a maintenance transaction
Business Example You want to import Support Packages into your SAP system. You want to request these with the help of your Solution Manager
Maintenance Certificates A maintenance certificate enables the SAP software logistics tools (for example, SPAM, SAINT, and JSPM) to identify the system to be maintained and to determine the extent of maintenance required. It is also used to ensure that only customers with a valid maintenance contract can perform the relevant maintenance transactions. Hint: As of January 2009, the software logistics tools can only maintain a system if a valid maintenance certificate is available. As of SPAM/SAINT Version 7.00/0034, a valid maintenance certificate is a prerequisite for importing Support Packages. Hint: All SAP products based on SAP NetWeaver AS ABAP 7.0 and higher require a maintenance certificate.
2012
© 2011 SAP AG. All rights reserved.
335
Unit 9: “SAP Patch Day”
TADM12_1
Maintenance certificates are valid for a period of three months, after which time they must be renewed. To keep costs to a minimum, a SAP Solution Manager system can be used to automate the process of generating maintenance certificates. For this purpose, a SAP Solution Manager system must have release 7.0 and Support Package Stack level 16 or higher (recommended: 18). Hint: The SAP Solution Manager system requires a connection to SAP Service Marketplace and to the SAP system to be patched. If these connections are not possible (for example, for security reasons), the maintenance certificates can also be requested manually from SAP Service Marketplace. When performing a release upgrade or importing SAP enhancement packages, Support Packages are incorporated into the update process. A maintenance certificate is not required here. You can use transaction SLICENSE to check whether your system has a valid maintenance certificate. Choose New Licenses (to switch to the Digitally-Signed License Keys view). You can now check the following: • • •
Software Product: Maintenance in the Sware Prod column Valid From: Date on which the maintenance certificate was requested Valid To: Date on which the maintenance certificate was requested + approximately three months Hint: See also SAP Note 1280664 - Distribution of maintenance certificates: Troubleshooting
336
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Preparation for Software Maintenance
Figure 141: Maintenance Certificate
1. 2. 3. 4.
2012
The SAP Solution Manager system requests a maintenance certificate for all managed systems, where the maintenance certificate is expiring. The maintenance certificates are generated in the SAP Global Support Backbone. The SAP Solution Manager system contains the maintenance certificates the next time a connection is established (every 24 hours). The managed systems receive the maintenance certificates from the SAP Solution Manager system.
© 2011 SAP AG. All rights reserved.
337
Unit 9: “SAP Patch Day”
TADM12_1
The following is a more detailed description of the process: 1.
2. 3.
If automatic distribution is active for maintenance certificates, SAP Solution Manager passes the system numbers of all satellite systems to the SAP Global Support Backbone. The SAP Global Support Backbone automatically checks each system for a valid maintenance contract. If there is no valid maintenance contract, the process in the SAP Global Support Backbone automatically ends, and the customer's SAP Solution Manager system is informed. If there is a valid maintenance contract, the SAP Global Support Backbone automatically checks whether there is a maintenance certificate, and returns it to SAP Solution Manager.
4.
5. 6.
7. 8.
If there is no maintenance certificate, the SAP Global Support Backbone automatically generates one for this system. The next time it runs (every 24 hours), SAP Solution Manager can get this maintenance certificate from the SAP Global Support Backbone. The maintenance certificates are automatically given to SAP Solution Manager, where they are saved and made available. The Maintenance Package task, which runs daily in the satellite systems (in the Service Data Control Center, transaction SDCCN), uses an RFC connection to request the relevant maintenance certificate from SAP Solution Manager. If a maintenance certificate is successfully retrieved, it is automatically saved locally in SAP License Management (transaction SLICENSE). If the tools SPAM or SAINT are used to import Support Packages, an automatic check is performed to check whether there is a valid maintenance certificate for the system.
SAP Note 1280664 - Distribution of maintenance certificates: Troubleshooting provides detailed information about troubleshooting.
Maintenance Transaction All SAP systems that are part of the customer's system landscape are registered in SAP Solution Manager. The Maintenance Optimizer (MOpz), as part of SAP Solution Manager, can then work with this information. To import Support Packages, among other things, SAP recommends that you create a maintenance transaction with the Maintenance Optimizer. On the one hand, this maintenance transaction is used to calculate a consistent combination of Support
338
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Preparation for Software Maintenance
Packages for a systems in the system landscape. On the other hand, the Support Packages to be imported must be approved before they can be downloaded. The approval is performed as part of the maintenance transaction. Hint: All Support Packages for systems based on SAP NetWeaver 7.0 (and higher) require the Maintenance Optimizer for approval.
Figure 142: Maintenance Transaction
2012
© 2011 SAP AG. All rights reserved.
339
Unit 9: “SAP Patch Day”
TADM12_1
The following steps are necessary to perform a maintenance transaction and using it to select Support Packages: 1. 2. 3. 4. 5.
6. 7.
8.
In the SAP Solution Manager system, the basic configuration needs to have been performed with transaction SOLMAN_SETUP. The SAP systems to be maintained need to have been registered in SAP Solution Manager with transaction SMSY. As part of this registration process, the systems are assigned to a logical component. The logical component needs to be assigned to a solution in the SAP Solution Manager Administration work center. In the Change Management work center you can create a maintenance transaction using the Maintenance Optimizer (MOpz) by choosing Common Tasks → New Maintenance Transaction. The required Support Packages can be selected within this maintenance transaction. The selected Support Packages can be placed in the download basket. They are then approved within the maintenance transaction so the Download Manager can be used to download them from the SAP Service Marketplace. (Alternatively, the Software Lifecycle Manager functions (SLM) can be used for the download.) The downloaded Support Packages can now be imported using the Support Package Manager (transaction SPAM in the AS ABAP based system to be maintained). In AS Java based systems Support Packages are imported with the tool JSPM. Hint: With SAP Solution Manager 7.1 transaction codes SOLUTION_MANAGER, DSWP, and DSMOP will be deactivated. Transaction SOLMAN_WORKCENTER replaces the transaction SOLUTION_MANAGER. For more information see SAP Note 1480419.
A maintenance transaction consists of five major steps that need to be performed. Start the transaction SOLMAN_WORKCENTER to open SAP Solution Manager: Work Centers
340
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Preparation for Software Maintenance
Figure 143: Starting the Maintenance Optimizer and entering the Basic Data
Select the tab (1) Change Management. In Overview select (2) Maintenance Optimizer to start a new maintenance transaction. As a shortcut you could select (3) New Maintenance Transaction in the Common Tasks. The screen New Maintenance Optimizer transaction will open. Here you need to select the (4) Solution and (5) Product Version. In the box Product System you need to select the systems that you want to patch in this maintenance transaction. When you have entered the correct basic data you can press (6) Continue.
2012
© 2011 SAP AG. All rights reserved.
341
Unit 9: “SAP Patch Day”
TADM12_1
Figure 144: Selecting the files and target patch level
The figure above shows how to choose (1) the automatic or manual file selection and (2) Continue to the update options. Depending on your start release the system will present you (3) with the possible update option. Press (4) Continue to the Select Target screen. In this screen you can select the target support package stack that you want to implement. Choose (6) Continue to the screens Confirm Major Target, Select Add-on Products and Select OS/DB-Dependent Files.
342
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Preparation for Software Maintenance
Figure 145: Confirm target and select add-on and OSDB files 1/2
The choices above depend on the product that you are applying the patches to. In the example shown in the figure above we only select the correct OS/DB files. No add-on was selected.
2012
© 2011 SAP AG. All rights reserved.
343
Unit 9: “SAP Patch Day”
TADM12_1
Figure 146: Confirm target and select add-on and OSDB files 2/2
In the steps shown above you can choose to include a SPAM Update (step 2.5). In step 2.6 you can change the selected Stack-Dependant Files. Changing the selection here is not recommended. The step 2.7 will put the files into your Download Basket.
344
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Preparation for Software Maintenance
Figure 147: Download, implement and complete the maintenance transaction
In download the selected files using the Download Manager in step 3. When this is done continue to step 4 and maintain the status of the implementation of the support package stack. This step can only continue when all the systems in this Maintenance Transaction have the status Completed. In step 5 you can close the Maintenance Transaction by choosing Complete Transaction. After completion no changes are possible.
2012
© 2011 SAP AG. All rights reserved.
345
Unit 9: “SAP Patch Day”
346
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Preparation for Software Maintenance
Exercise 16: Execute a Maintenance Transaction Exercise Objectives After completing this exercise, you will be able to: • Create and execute a maintenance transaction for Support Packages in the SAP Solution Manager system.
Business Example You want to update the SAP systems in your company to the latest Support Package level. You want to use a maintenance transaction in the SAP Solution Manager system to determine the Support Packages. Caution: The DEV groups log on to the partner QAS system and define a maintenance transaction for their own DEV system. The QAS groups log on to the partner DEV system and define a maintenance transaction for their own QAS system. The partner system is assumed to be the Solution Manager system, the own system is assumed to be the system to be updated. Caution: The maintenance transaction exercise requires certain system configurations to be made. The systems for this course are prepared accordingly. However, you may still need to create a solution and assign logical components. The first task is used for this.
Task 1: Create a Solution Create a solution your partner SAP Solution Manager system that has a logical component assigned to it with your own system included. 1.
Create a solution and assign your logical component to it. Use the SAP Solution Manager Administration work center.
Task 2: Execute a Maintenance Transaction Use your partner SAP Solution Manager system to execute a maintenance transaction for your own system for importing a Support Package Stack into your system. 1.
Create a maintenance transaction for importing a Support Package Stack. Continued on next page
2012
© 2011 SAP AG. All rights reserved.
347
Unit 9: “SAP Patch Day”
348
TADM12_1
2.
Select the Support Package Stack you require for your maintenance transaction.
3.
Complete the maintenance transaction.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Preparation for Software Maintenance
Solution 16: Execute a Maintenance Transaction Task 1: Create a Solution Create a solution your partner SAP Solution Manager system that has a logical component assigned to it with your own system included. 1.
Create a solution and assign your logical component to it. Use the SAP Solution Manager Administration work center. a)
Log on to your SAP Solution Manager system.
b)
Call the SAP Solution Manager Administration work center using the SOLMAN_WORKCENTER transaction, for example.
c)
Choose Solutions and select the New button.
d)
Enter user and password and log on. You are now in the screen to create a new Solution.
e)
In the field Solution, enter the name of your solution, for example Solution ## and choose a language.
f)
Switch to the System Group tab.
g)
Choose Development System as the Leading Role of the Solution and then Save Solution.
h)
Press the F4 key in the first cell of column Logical Components to add the correct logical component.
i)
In the popup expand SAP SOLUTION MANAGER → Solution Manager ABAP Stack and select SAP Solution Manager. Confirm this selection.
j)
Save your changes.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
349
Unit 9: “SAP Patch Day”
TADM12_1
Task 2: Execute a Maintenance Transaction Use your partner SAP Solution Manager system to execute a maintenance transaction for your own system for importing a Support Package Stack into your system. 1.
Create a maintenance transaction for importing a Support Package Stack. a)
Log on to your partner SAP Solution Manager system.
b)
Call the Change Management work center using the SOLMAN_WORKCENTER transaction, for example.
c)
Choose Common Tasks → New Maintenance Transaction.
d)
Choose a Priority and enter a Description. Choose the Solution you created in the previous task.
e)
Choose SAP SOLUTION MANAGER 7.1 as the Product Version and select the row with your own SAP system.
f)
Choose Continue.
Continued on next page
350
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Preparation for Software Maintenance
2.
3.
2012
Select the Support Package Stack you require for your maintenance transaction. a)
Select Calculate Files Automatically - Recommended and choose Continue.
b)
Maintenance is already selected in your maintenance transaction. Choose Continue.
c)
Accept the Target stack currently proposed, for example, 03 (09/2011) and choose Continue. (This may take several minutes.)
d)
Check the technical system and choose Continue.
e)
Do not select any Add-on and choose Continue.
f)
You now see a selection of operation system- and database-dependent files. For the operating system Windows Server on x64 64bit, select the #Database independent and MaxDB files. Choose Continue.
g)
You now see a selection of stack-independent files. Leave the selection unchanged and choose Continue.
h)
You now see the files that belong to your stack. Leave the selection unchanged and choose Continue.
i)
As the download tool choose Download Basket. The files will be added to the download basket. Choose Continue.
j)
The files are automatically confirmed in your S-user's download basket. You could now start the Download Manager by choosing Download Files from Download Basket. In the context of this course this step is not necessary, because the relevant files are already downloaded to your server.
k)
Choose Continue. The Status of Implementation is New. You may want to set it to In Process.
l)
At this point, you would use the Download Manager to download the files and, for example, use transaction SPAM to import the Support Packages into your own AS ABAP based system. For an AS Java based system, the tool JSPM is used. However, this is not part of this exercise. Imagine that you have already successfully imported all of the files contained in your maintenance transaction.
Complete the maintenance transaction. a)
Set the Status of Implementation to Completed and Save.
b)
Choose Complete Transaction and Continue.
© 2011 SAP AG. All rights reserved.
351
Unit 9: “SAP Patch Day”
TADM12_1
Lesson Summary You should now be able to: • Explain the concept of maintenance certificates • Describe a maintenance transaction
352
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Support Package Manager (SPAM)
Lesson: Support Package Manager (SPAM) Lesson Overview In this lesson you will be introduced to the Support Package Manager. You will learn what a SPAM/SAINT update is and how to import it. A SPAM/SAINT update may be required before you can import new Support Packages.
Lesson Objectives After completing this lesson, you will be able to: •
Explain the use of the Support Package Manager and import a SPAM/SAINT update.
Business Example Functional enhancements to a system can affect not only the applications, but also the actual tools that you use to import the Support Packages.
SPAM/SAINT Update Most standard software components of an SAP system are installed during the initial installation process. Additional software components can be imported afterwards, if required. These are referred to as add-ons. Examples of add-ons are plug-ins or industry-specific components (industry solutions) that are not part of the standard installation. These add-ons are imported with the help of the Add-On Installation Tool (transaction SAINT). The Add-On Installation Tool and add-ons themselves will not be dealt with in detail in this lesson. The tool for importing Support Packages is the Support Package Manager. You can call it using the transaction SPAM.
2012
© 2011 SAP AG. All rights reserved.
353
Unit 9: “SAP Patch Day”
TADM12_1
Figure 148: Support Package Manager: SPAM/SAINT Update
The Support Package Manager offers the following functions: You can use the Support Package Manager (transaction SPAM) to import individual Support Packages for individual components. You can also import several consecutive Support Packages for a software component. Furthermore, you can import several Support Packages for various software components (a vector). If you want to import such a vector of Support Packages, you can either switch to All Components in the selection dialog box for the queue or you can choose Extras → Settings → Define Queue to switch to the vector selection view. When the Support Package Manager imports a Support Package into the system, it follows a fixed sequence of steps. If the process of implementing the Support Package terminates, processing can be restarted at the break-off point. The process restarts at the point at which it was terminated. A special import procedure keeps downtime to a minimum. (Extras → Settings → Import Queue → Import Mode: Downtime-minimized) The individual phases of the Support Package Manager are grouped into four modules. You can determine the start times of the modules individually. The individual modules can also be scheduled for background processing.
354
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Support Package Manager (SPAM)
The Support Package Manager can recognize dependencies between Support Packages and take account of these (but not the side-effects, however). To remain up-to-date and to be able to use the new functions of the Support Package Manager too, you should update the Support Package Manager itself before you import Support Packages. Since transactions SPAM and SAINT are closely related from a technical point of view, a shared patch, the SPAM/SAINT update, is supplied at unregular intervals to upgrade the tools. You can find out the version from the short description of transaction SPAM (for example, SPAM/SAINT update - Version 7.01/0040). Hint: The update for the Support Package Manager (SPAM/SAINT update) is only delivered in German and English. You are therefore recommended to log on in English or German when working with the Support Package Manager. The SPAM/SAINT update is imported using the transaction SPAM. You can only import a SPAM/SAINT update if there are no aborted Support Packages in the system. If there are aborted Support Packages, a dialog box informs you of this. You then have two options: • •
2012
You first import the complete queue of Support Packages and then the SPAM/SAINT update. You reset the status of the queue, import the SPAM/SAINT update first and then the Support Package queue. You can reset the status of the queue by choosing Extras → Reset status → Queue.
© 2011 SAP AG. All rights reserved.
355
Unit 9: “SAP Patch Day”
TADM12_1
Procedure for importing a SPAM/SAINT update: 1.
2.
3. 4. 5.
6.
Check whether the SPAM/SAINT update currently offered on SAP Service Marketplace is newer than the one imported into the SAP system (the SPAM/SAINT version of the SAP system is displayed in the title bar of the Support Package Manager). Download the latest SPAM/SAINT update from SAP Service Marketplace. As part of a maintenance transaction, the Maintenance Optimizer can be used for this purpose. Extract the downloaded file to the transport directory of the relevant SAP system, subdirectory EPS, subdirectory in. Log on to client 000 in the SAP system and call transaction SPAM. Communicate the patch (the SPAM/SAINT update) to the Support Package Manager: Support Package → Load packages → From Application Server. This is simply a notification for the Support Package Manager and does not import the SPAM/SAINT update. No packages are loaded. And they are not searched for on the application server, but rather on the host, the application server run on. To import the SPAM/SAINT update, choose Support Package → Import SPAM/SAINT Update.
In a multi-system landscape you have to carry out this import procedure in each system. In a three system landscape, the most practical sequence is development system, quality assurance system, and then production system. Since the SPAM/SAINT update is a full delivery of transactions SPAM and SAINT, you can import the latest available SPAM/SAINT update immediately. For example, for an existing version 0035, you can directly import version 0040.
356
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Support Package Manager (SPAM)
Exercise 17: Support Package Manager (SPAM) Exercise Objectives After completing this exercise, you will be able to: • Import a SPAM/SAINT update
Business Example To import Support Packages, you often need to first update the tool that you are using for the import. This may be necessary in order to read current attributes from the new Support Package, for example.
Task: Importing a SPAM/SAINT Update Import a SPAM/SAINT update. Caution: This exercise must be performed by the DEV group first and then by the QAS group. In the first step, a SPAM/SAINT update is imported into the SAP system DEV. After it has been imported successfully, the SPAM/SAINT update is imported into the SAP system QAS. Your instructor will show you the downloaded file you require for the SPAM/SAINT update. 1.
Check the current SPAM version in your system.
2.
Extract the file that contains the SPAM/SAINT update at operating system level. Hint: Remember that this step only needs to be performed once for each transport directory.
2012
3.
Log on to the correct client.
4.
Load the SPAM/SAINT update using transaction SPAM; that is, declare the file to the SAP system.
5.
Import the SPAM/SAINT update into your SAP system. Note any possible errors.
6.
Check the import process log for errors.
© 2011 SAP AG. All rights reserved.
357
Unit 9: “SAP Patch Day”
TADM12_1
Solution 17: Support Package Manager (SPAM) Task: Importing a SPAM/SAINT Update Import a SPAM/SAINT update. Caution: This exercise must be performed by the DEV group first and then by the QAS group. In the first step, a SPAM/SAINT update is imported into the SAP system DEV. After it has been imported successfully, the SPAM/SAINT update is imported into the SAP system QAS. Your instructor will show you the downloaded file you require for the SPAM/SAINT update. 1.
Check the current SPAM version in your system. a)
Call transaction SPAM. The SPAM version is displayed in the title bar (for example, “Support Package Manager - Version 7.01/0039).” To see whether SPAM/SAINT updates have already been imported, select the Imported Support Packages radio button and choose Display. The system displays an overview of the previously imported SPAM/SAINT updates, called SAP_OCS (SAP Online Correction System) here. Note: You can also skip individual SPAM/SAINT updates, which means that you can switch directly from version 7.01/0039 to the newest version corresponding to SAP_BASIS release 7.01.
Continued on next page
358
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Support Package Manager (SPAM)
2.
Extract the file that contains the SPAM/SAINT update at operating system level. Hint: Remember that this step only needs to be performed once for each transport directory. a)
Go to operating system level. Copy the file KD701.CAR to the transport directory (for example, G:\usr\sap\trans). stands for the (latest) version of the SPAM/SAINT update. At operating system level, open a command prompt in the transport directory and use the command sapcar -xvf KD701.CAR to extract the file you have just copied. This extracts the file to the directory \EPS\in. It should now be in G:\usr\sap\trans\EPS\in, for example.
3.
Log on to the correct client. a)
4.
Log on to client 000. You can only import a SPAM/SAINT update from client 000.
Load the SPAM/SAINT update using transaction SPAM; that is, declare the file to the SAP system. a)
Transaction SPAM: Support Package → Load packages → From Application Server. Confirm the dialog box for the “upload”. See that the SPAM/SAINT update was recognized. Go back to the initial screen of SPAM Hint: Remember that - although the menu path may suggest it no package is uploaded or imported here, and it is not searched for on the application server, but rather on the host, the application server is running on.
5.
Import the SPAM/SAINT update into your SAP system. Note any possible errors. a)
In transaction SPAM, choose Support Package → Import SPAM/SAINT Update. Confirm the dialog box to import. In case the import process terminates due to an error, just restart it with transaction SPAM. A termination is not unusual, because you are patching the tool with itself.
b)
Then call transaction SPAM again. This takes some time, since the system must regenerate the underlying programs and so on, due to the SPAM/SAINT update. Continued on next page
2012
© 2011 SAP AG. All rights reserved.
359
Unit 9: “SAP Patch Day”
6.
Check the import process log for errors. a)
360
TADM12_1
Call transaction SPAM and choose Goto → Import Logs → SPAM/SAINT Update. No errors should be displayed.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Support Package Manager (SPAM)
Lesson Summary You should now be able to: • Explain the use of the Support Package Manager and import a SPAM/SAINT update.
2012
© 2011 SAP AG. All rights reserved.
361
Unit 9: “SAP Patch Day”
TADM12_1
Lesson: Importing Support Packages Lesson Overview In this lesson you will learn how Support Packages are imported into your systems.
Lesson Objectives After completing this lesson, you will be able to: • •
Import Support Packages with transaction SPAM Provide a general explanation of the import process for Support Packages
Business Example Importing Support Packages is a task for the SAP system administrator. The new versions of SAP objects in the Support Packages stabilize and extend the functional scope of the SAP system. They are also needed in regard of legal changes.
Importing Support Packages The Support Package Stacks represent combinations of Support Packages recommended by SAP for the respective product version, and you are advised to import these regularly. When importing Support Packages you should observe the instructions for the Support Package Stack and import all the Support Packages in the Support Package Stack, if possible. A kernel patch often is part of the Support Package Stack, too. This should be implemented before you import the Support Packages (not covered in this lesson). If you have installed an enhancement package in your SAP system, you must use the Maintenance Optimizer, as part of SAP Solution Manager, to calculate a Support Package Stack. In any case you should use the Maintenance Optimizer.
362
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Support Packages
Figure 149: Importing Support Packages
The procedure for importing Support Packages should be as follows: 1.
2. 3. 4. 5.
2012
Create a maintenance transaction in the Maintenance Optimizer. The Maintenance Optimizer calculates the necessary combination of Support Packages (Support Package Stack) for the system you want to patch. You should also make sure you have the latest SPAM/SAINT update. The Maintenance Optimizer approves the selected Support Packages for the download, and place them in the download basket for the Download Manager. You can download the required Support Packages from SAP Service Marketplace using the Download Manager. The downloaded files need to be unpacked to the transport directory of the relevant SAP system, subdirectory \EPS\in. Log on to client 000 in the SAP system and call transaction SPAM. The new Support Packages are announced to the Support Package Manager: Support Package → Load Packages → From Application Server. This is simply a notification for the Support Package Manager and does not import the Support Packages. If the compressed files are on the front-end servers host and are smaller than around 10 MB, you can also transfer these files to the application
© 2011 SAP AG. All rights reserved.
363
Unit 9: “SAP Patch Day”
6. 7.
8. 9. 10. 11. 12.
13.
TADM12_1
servers host and decompress them directly from the Support Package Manager. With files that are larger than approximately 10 MB in size, this method is inefficient, since it is too slow. Make settings for the import procedure (see below). You define the queue for the Support Packages to be imported. This can choose Support Packages for one single software component as well as Support Packages for several components. The Support Package Manager checks the consistency of the queue. The Support Package Manager ensures that only Support Packages that match the system are displayed in the queue. Support Packages that are intended for a different release or a software component that is not installed, or whose predecessor relationships are not fulfilled, do not appear in the queue, even if these have been specified in the SAP system. To import the Support Package queue, choose Support Package → Import Queue. Choose the start conditions for the four import modules (see below). Start the import process. One or two modification adjustments may arise during the import (see below). These must be executed at the specified point. Once the Support Packages have been imported successfully, check the logs: Goto → Import Logs → Queue After the Support Packages have been imported to the development system, the developers can check the objects. After the Support Packages have been imported to the quality assurance system, an acceptance test should be carried out by subject matter specialists. You can then import the Support Packages to the production system. If the import has been completed successfully, the imported queue has to be confirmed in the relevant system: Support Package → Confirm
There are a number of possible settings for the import procedure (Extras → Settings). Under Import Queue → Scenario, you can define the actions to be carried out during the import: •
•
Standard: The standard scenario is used to import Support Packages completely; all steps are performed. The import mode Downtime-minimized can be used here (see below). Test: You can use the test scenario to observe whether a modification adjustment is required before you import the Support Package, or to check whether conflicts occur that must be resolved before the import. No data or objects are imported to the SAP system during the test scenario. There is no test scenario for SPAM/SAINT updates. The selection you make here is ignored when importing a SPAM/SAINT update.
364
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Support Packages
There are many steps (phases) to the import procedure. These are subdivided into four modules. • • •
The modules can be executed individually in the correct sequence. The modules can be started in a background process. The start time of the module can be controlled flexibly.
The four modules execute the following steps: 1.
2.
3.
4.
2012
Preparation module: All the preparatory steps and check steps (such as the test import, add-on conflict check) are performed in this module. The module can run during production operation. Once the preparation module has been completed, you still have the option of resetting or deleting the queue. If you continue with the Import 1 module, data is changed on the database and the queue can no longer be reset or deleted. Import 1 module: In this module, the objects of the Support Packages are imported. If the import procedure is carried out in Downtime-minimized mode, programs are inactively imported. The runtime system cannot “see” these changes yet. Dictionary objects are inactive when imported, independent of the import mode. The manual modification adjustment of the Dictionary objects is performed at the end of this module, if required (SPDD modification adjustment). Now the dictionary objects are activated. If you can guarantee that no manual changes are required for the SAP system and no transports are imported into the SAP system during this time, up to here this module can run with the Downtime-minimized import mode during production operation. These conditions are normally given in the production system. Nevertheless, in this case this module runs longer. Import 2 module: The remaining import steps are carried out in this module. If you use the Downtime-minimized import mode, inactive programs are activated in this module as well. During this module production operation is not permitted to avoid inconsistencies and data loss. As a result, this module always means system downtime. Clean Up module: In this module, all the clean-up steps are processed. The modification adjustment of the non-Dictionary repository objects is performed in this module (SPAU modification adjustment). When all modifications have been adjusted, production operation can continue.
© 2011 SAP AG. All rights reserved.
365
Unit 9: “SAP Patch Day”
TADM12_1
Figure 150: Import Mode Downtime-minimized
Caution: The SAP system administrator must manage the downtime manually! This means, that the administrator is responsible for locking the system, logging out the users, stopping batch processing, invalidating RFC connections and so on. With the Downtime-minimized import mode, the ABAP programs in the Import 1 module are inactive when imported. Advantages of the Downtime-minimized import mode: Since you can stop the import of Support Packages after each module, you can run the Preparation and Import 1 modules up to the first modification adjustment during production operation. After the scheduled switch to non-production operation, you can run the Import 2 module and the modification adjustments, if required. After that, production operation can resume. Note: You can considerably reduce system downtime by selecting Downtime-minimized. However, this makes the overall import procedure longer because you still need to activate the ABAP programs in module Import 2. Additionally, module Import 1 will take longer to run because the imported objects must be kept in addition to the previous versions of the objects using the version administration tools.
366
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Support Packages
The setting for the Downtime-minimized import mode also influences the default setting for the start conditions of the four import modules. If you selected the conventional import procedure (Downtime-minimized import mode not activated), the following settings appear by default: 1. 2. 3. 4.
Preparation: Start in dialog immediately Import 1: Continue in dialog immediately Import 2: Continue in dialog immediately Clean Up: Continue in dialog immediately
If you selected the Downtime-minimized import mode, the following settings appear by default: 1. 2. 3. 4.
Preparation: Start in dialog immediately Import 1: Continue in dialog immediately Import 2: Continue manually Clean Up: Continue manually
Figure 151: Modification adjustment when importing Support Packages
2012
© 2011 SAP AG. All rights reserved.
367
Unit 9: “SAP Patch Day”
TADM12_1
If SAP objects were modified by the customer and then imported with a Support Package, the objects have to be adjusted when they are imported. If these objects are not adjusted, the customer's modifications that have been made to the SAP objects are reset to the SAP delivery status. Use transaction SPDD to adjust Dictionary repository objects, and transaction SPAU to adjust non-Dictionary repository objects. The modification adjustment for Dictionary repository objects is performed using transaction SPDD. This modification adjustment must be carried out completely before you can continue with the import. Otherwise, the modifications to the Dictionary repository objects are lost. This can then lead to data loss. Caution: The SPDD adjustment should be performed manually in each system in the landscape and not be replaced by importing a transport request. Importing a transport request can lead to inconsistencies and is not recommended. Note: As of SPAM/SAINT Version 7.00/0024, you can bind transport requests that contain the modification adjustments from the development system into the Support Package queue for the subsequent SAP systems. This means that the modification adjustments only need to be carried out once in the development system, and are then implemented automatically in the quality assurance and production systems by the modification adjustment transports. This is a similar procedure as in a release upgrade. The modification adjustment for non-Dictionary repository objects is performed using transaction SPAU. You can perform the SPAU adjustment in each system of a multi-system landscape manually. Or this modification adjustment can be performed once in the development system and imported to the following systems using the resulting transport request (which is not possible in transaction SPDD). To do this, however, you should compare the modification status of the individual systems in the landscape beforehand. You can check these at any time with the Modification Browser (transaction SE95). Note: As of SPAM/SAINT Version 7.00/0024, you can bind transport requests that contain the modification adjustments from the development system into the Support Package queue for the subsequent SAP systems.
368
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Support Packages
To perform an SPDD or an SPAU modification adjustment, proceed as follows: 1.
2.
3.
4. 5.
To enable developers to perform the modification adjustment, create a transport request in the Transport Organizer, and under the transport requests, create tasks for the developers. You are advised to create only one transport request for the adjustment of Dictionary repository objects (SPDD) and one second transport request for the adjustment of non-Dictionary repository objects (SPAU). The developers can now perform the modification adjustment. They can use transactions SPDD and SPAU to do this. After the adjustment is complete, the developers must release the tasks and transport requests. If you are using a SPAM/SAINT version 7.00/0024 or above, you can flag the adjustment transport requests (select Select for Transport in the transactions SPDD and SPAU). This is possible as of Basis Release 7.00. This enables you to perform the modification adjustments manually in the development system only. When you import the Support Packages to the subsequent SAP systems of the landscape, these adjustment transports can be included in the Support Package queue. This means manual modification adjustments are no longer required in the subsequent SAP systems. Now choose Confirm Adjustment and confirm the prompt. To continue the import process, choose Support Package → Import Queue.
The Support Package Manager continues the processing and displays the status.
2012
© 2011 SAP AG. All rights reserved.
369
Unit 9: “SAP Patch Day”
TADM12_1
Figure 152: Additional Hints
Hint: It is also possible to import Support Packages with the current version of the SAP enhancement package installer (SAPehpi) (without importing an SAP enhancement package). Importing Support Packages with SAPehpi is by far more difficult and complex for the SAP system administrator, but leads to a shorter downtime! This method of importing Support Packages is not covered in this lesson. Hint: For some SAP systems, for example SAP CRM, an advanced version of SPAM is used: The in Transaction SPAM choose Environment →Support Package Manager for EBP/CRM. It is more interactively and - besides others - helps the administrator to control the downtime.
370
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Support Packages
Exercise 18: Import Support Packages Exercise Objectives After completing this exercise, you will be able to: • Import Support Packages with transaction SPAM
Business Example You need to import the most recent Support Packages to update the SAP system.
Task: Import one Support Package Caution: This exercise must be performed first by the DEV group and then by the QAS group. It must not be performed by both groups at the same time. Note: Information only applicable for the current training environment: The import of the single Support Package takes about 6 minutes. Of this time, most is spent with some preliminary checks (about 5 minutes). Import the Support Package named by your instructor. In the first step, the available Support Package is imported into the SAP system DEV. After this import is successfully completed, the Support Package is imported into the SAP system QAS. The file required for the Support Package has already been requested. The instructor will show you where to find them. 1.
Check which Support Packages have already been imported into your system. Have these been confirmed?
2.
Extract the files that contain the new Support Package at operating system level. Note that this step only needs to be performed once for each transport directory.
2012
3.
Log on to the correct client.
4.
Load the Support Package, that is, inform the SAP system about the files.
5.
Check the settings for the import of the Support Packages in transaction SPAM.
6.
Define the queue for importing the Support Package in transaction SPAM.
7.
Import the Support Package queue to your system. Note any possible errors. Continued on next page
© 2011 SAP AG. All rights reserved.
371
Unit 9: “SAP Patch Day”
372
TADM12_1
8.
Check the log for the import process for errors.
9.
Confirm the imported Support Package after successful import.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Support Packages
Solution 18: Import Support Packages Task: Import one Support Package Caution: This exercise must be performed first by the DEV group and then by the QAS group. It must not be performed by both groups at the same time. Note: Information only applicable for the current training environment: The import of the single Support Package takes about 6 minutes. Of this time, most is spent with some preliminary checks (about 5 minutes). Import the Support Package named by your instructor. In the first step, the available Support Package is imported into the SAP system DEV. After this import is successfully completed, the Support Package is imported into the SAP system QAS. The file required for the Support Package has already been requested. The instructor will show you where to find them. 1.
Check which Support Packages have already been imported into your system. Have these been confirmed? a)
Transaction SPAM: Select the Imported Support Packages radio button and choose Display. Result: Support Packages have already been imported. They have also already been confirmed. You can tell this, for example, from the green traffic light on the initial screen of transaction SPAM.
2.
Extract the files that contain the new Support Package at operating system level. Note that this step only needs to be performed once for each transport directory. a)
Go to file system level. Copy the relevant file to the transport directory (for example D:\usr\sap\trans). At operating system level, open a Command Prompt in the transport directory (for example D:\usr\sap\trans). Extract the file you have just copied there using the command sapcar -xvf . This extracts the file to the relative directory \EPS\in (for example D:\usr\sap\trans\EPS\in). Continued on next page
2012
© 2011 SAP AG. All rights reserved.
373
Unit 9: “SAP Patch Day”
3.
TADM12_1
Log on to the correct client. a)
Log on to client 000. It is only possible to import Support Packages from client 000.
4.
Load the Support Package, that is, inform the SAP system about the files. a)
Transaction SPAM: Support Package → Load packages → From Application Server. Smile about the misleading named menu path and confirm the dialog box to “upload”. See that the new Support Package was recognized. Go back to the initial screen of SPAM.
5.
Check the settings for the import of the Support Packages in transaction SPAM. a)
Transaction SPAM: Extras → Settings Leave the settings at their default values.
6.
Define the queue for importing the Support Package in transaction SPAM. a)
Transaction SPAM: Choose the Display/define button. Choose the required software component (TRAINING) and the required Support Package. You can confirm the queue with Enter. There are no adjustment transports that could be included: You should therefore confirm the system prompt Do you want to add Modification Adjustment Transports to the queue now? with No
Continued on next page
374
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Support Packages
7.
Import the Support Package queue to your system. Note any possible errors. a)
In transaction SPAM, import the queue by choosing Support Package → Import Queue. Retain the default values for the start conditions of the four modules. Confirm the dialog box to start the import. Follow the individual steps of the import process, as far as possible, in the status line. If errors occur, check these by opening the error log. In this case, repeat the import the Support Packages. The import process can be repeated beginning with the step it failed. Confirm the dialog box informing you that the import was successful.
8.
Check the log for the import process for errors. a)
Check the import logs in transaction SPAM by choosing Goto → Import Logs → Queue. No return code values of 8 or higher should be displayed.
9.
Confirm the imported Support Package after successful import. a)
2012
Finally, confirm the queue in transaction SPAM by choosing Support Package → Confirm
© 2011 SAP AG. All rights reserved.
375
Unit 9: “SAP Patch Day”
TADM12_1
Lesson Summary You should now be able to: • Import Support Packages with transaction SPAM • Provide a general explanation of the import process for Support Packages
376
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Corrections
Lesson: Importing Corrections Lesson Overview This lesson presents the updating of SAP NetWeaver Application Server Java-based systems by installing a current Support Package.
Lesson Objectives After completing this lesson, you will be able to: •
Install Support Packages for SAP NetWeaver Application Server Java-based systems
Business Example SAP NetWeaver Application Server with Usage Type AS Java is used as the runtime environment for applications that conform to the J2EE standard. You can use Support Packages to correct errors and implement new functions for SAP NetWeaver Application Server with Usage Type AS Java.
Support Packages Support Packages are corrections and new functions that SAP supplies to customers. The component module used by SAP in the context of Java development is used both in delivery (installation) and in the context of maintenance (import of Support Packages).
2012
© 2011 SAP AG. All rights reserved.
377
Unit 9: “SAP Patch Day”
TADM12_1
Figure 153: Component Model in Delivery and Maintenance
Software maintenance is organized into three tiers: •
•
•
378
A product consists of one or more software components that represent related business processes. Products are installed or undergo an upgrade to a new release. A release is a full delivery of software components that provide new functions (and possibly user interfaces) or improvements. Software components contain a set of development components. Support Packages are delivered in the context of software maintenance. An Support Package (SP) is (unlike ABAP) a full delivery of one (or more) software component(s) and contains a number of patches. If sources are delivered with Support Packages, the SPs must be transported using the NWDI's Change Management Service (CMS). The usual file format of an SP is the SCA format. Patches are full deliveries of a development component that allow a quick error correction, before the complete SP is available. The usual file format is the SDA format. If patches include sources, they should also be imported using the resources of the CMS.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Corrections
Introduction: Java Support Package Manager As of SAP NetWeaver 7.0, the Java Support Package Manager (JSPM) is used to import Support Packages for SAP NetWeaver Application Server Java (AS Java) and all the Java-based software components running on it. JSPM is the only supported tool for the import of Support Packages and Support Package Stacks. JSPM can update all the integral components of Java systems listed below. •
Updating: –
• •
Kernel, Internet Graphic Server (IGS) and other native AS Java operating system binaries – JSPM itself, the system's deployment service (SDM) – all installed Java Usage Types in the system – modified software components (integration with NWDI) Deployment of SAP and third-party software components Deployment, update and upgrade of Business Packages in the SAP Business Suite
JSPM can import either individual Support Packages or a complete Support Package Stack. SAP recommends that you always implement the complete Support Package Stack in a Java system. This is the only way to ensure the consistency of the system and the application. Java Support Package files (SCAs) contain all the software objects and the associated software components (Full Patch). As a result, it is sufficient to update the Java system with the required Support Package Stack. It is not necessary to import all the Support Package Stacks from the start Support Package Stack level through to the Support Package Stack level one after the other. JSPM provides a simple, intuitive graphical user interface (GUI). JSPM only displays those components for which an update is possible. You can also see the current Support Package level in JSPM. JSPM simplifies the Support Package management process for Java applications by recognizing and taking account of dependencies and reducing manual activities. JSPM works together with the SAP NetWeaver Development Infrastructure (NWDI), thus making it possible to identify modified components. JSPM does not deploy the standard Support Packages but instead the NWDI's adapted Software Component Archives (SCAs). To deploy Support Packages and software components, JSPM connects to the SDM server (central instance).
2012
© 2011 SAP AG. All rights reserved.
379
Unit 9: “SAP Patch Day”
TADM12_1
Figure 154: JSPM-to-SDM Connection
Before deployment, the SDM server performs additional checks of the Support Packages and software components. AS Java and the SDM server must be started before you can start JSPM. It is also important that no applications (e.g. SDM GUI) are connected to the SDM server since only one connection can be opened to the SDM server. Hint: Only the user adm may start the JSPM. You start JSPM using a central instance file system script from the directory /usr/sap///j2ee/JSPM. The script is named go.bat (Windows) or go (Unix). You must now enter the SDM password. If you enter the password incorrectly three times, the SDM server is stopped. You must then restart it and log onto JSPM again. JSPM writes all its log files to the directory /usr/sap///j2ee/JSPM/log. Before you use the Java Support Package Manager, read SAP Note 891983. If you use SAP systems on iSeries then you can find additional information in SAP Notes 885063 and 1066038.
380
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Corrections
JSPM: Preparatory Steps You should note the following steps before using JSPM: 1. 2.
Before the update: Check the entire functional capability of the system Download the Support Package Stack (for all employed Usage Types) and the corresponding Support Package Stack definition file (stack.xml). Note: In the JSPM Gui, you can find the activated Usage Types in the Deployed Components tab. Hint: Only the definition file (stack.xml) corresponding to the Support Package Stack should be present in the file system as otherwise problems may occur.
3.
Storage location of the files (Support Packages and Support Package definition file): JSPM Inbox (Default: /usr/sap/trans/EPS/in) Note: The storage location of the JSPM Inbox is defined via the parameter DIR_EPS_ROOT.
4.
Check the free space in the file system for the SDM file transfer directory /usr/sap///SDM/program/temp Note: Temporarily available disk space: 1.5 times the size of the Support Package files Hint: You can use the following commands to modify the transfer directory of the SDM: a)
Windows: cd StopServer.bat sdm.bat jstartup “mode=standalone” sdm.bat filetransferdir “dir=new_dir” sdm.bat jstartup “mode=integrated” StartServer.bat
b)
UNIX : cd StopServer.sh
2012
© 2011 SAP AG. All rights reserved.
381
Unit 9: “SAP Patch Day”
TADM12_1
sdm.sh jstartup mode=standalone sdm.sh filetransferdir dir=new_dir sdm.sh jstartup mode=integrated StartServer.sh 5. 6.
Check and, if necessary, update the JDK version and Java VM settings of the Java runtime environment (SAP Note 723909) Check: The password of the default Java administration user in the secure store must be up-to-date! Note: For information on modifying the default Java administration user, see SAP Note: 870445
If JSPM is to recognize the Support Package Stack correctly, both the Support Package files and the corresponding Support Package Stack definition file (stack.xml) must be downloaded and available in the JSPM Inbox.
JSPM: Importing Corrections You perform the following steps to import corrections using JSPM. 1.
Log on as user adm to the central instance host. Note: Close the SAP Management Console and the SDM Remote Gui Client.
2.
Start the JSPM and log on with the SDM password. Hint: Start JSPM from /usr/sap///j2ee/JSPM using the script go or go.bat.
3.
Update the JSPM Hint: The JSPM update can be imported at runtime.
4.
Stop the dialog instances Hint: Before applying the support packages stop all dialog instances (not the central services). After applying the support packages, you can start the dialog instances again.
382
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Corrections
5. 6.
Call JSPM again and enter the SDM password. On the Deployment tab page, select the option Support and Enhancement Package Stack and then choose Next. Hint: If the system to be updated is embedded in an NWDI landscape, the corresponding role of the system is specified automatically. In this step, JSPM performs a number of status checks and displays the result for each individual software component in the following screen. The following status can be reported:. OK: SP can be imported. WARNING: The software contains customer modifications in a system monitored by NWDI. Deployment can be performed. • REVISE: Indicates inconsistencies with the corresponding software component. A deployment cannot be performed until all the problems have been eliminated. Select Next if the SP Stack has the appropriate status. This starts the updating of the software component and the status of the JSPM changes to SCHEDULED. • •
7.
Figure 155: Import Support Package Stacks
2012
© 2011 SAP AG. All rights reserved.
383
Unit 9: “SAP Patch Day”
TADM12_1
There are different ways to import Support Package Stacks. A significant difference is whether or not patches are applied. In particular, you apply patches if patches have already been applied on the current system. If the patch that has already been applied is of a younger date than the delivery date of the Support Package for the software components, the correction of the patch may not be contained in the Support Package for the software components. If you decide to apply patches, you can do this in one or two steps. The option to apply patches with the Support Package of the SPS in one step has been available as of SPS 14. Before you decide on this option, read SAP Note 1080821 carefully. Procedure: You start JSPM from the file system and log on with the SDM password.
Figure 156: Starting JSPM
The step Specify Queue displays the (highest) Support Package Stack level available in the JSPM Inbox. Then, in the Check Queue step, JSPM checks the deployment queue and every software component in the stack is assigned a status.
384
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Corrections
Figure 157: Support Package Stack: Specify Queue, Check Queue
In the Deploy Queue step, JSPM starts the deployment of the software components in the selected stack. At this time, the status is set to SCHEDULED. The Completed step displays the status of the software components after deployment.
2012
© 2011 SAP AG. All rights reserved.
385
Unit 9: “SAP Patch Day”
TADM12_1
Figure 158: Support Package Stack: Deploy Queue, Completed
After import, the Support Packages can have the following status: • • • •
DEPLOYED DEPLOYED WITH WARNING: The Support Packages have been deployed but might possibly not function correctly with other deployed components. ERROR: An error occurred during deployment and must be eliminated before continuing with the import of the Support Package. NOT DEPLOYED: For certain reasons, JSPM has not attempted to deploy the software components. Eliminate the problems and restart the import.
If the Support Package Stack contains a Kernel Update, JSPM starts with the Kernel Update. JSPM updates the kernel binaries of all the instances (dialog instances and CS instance).
386
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Corrections
In the case of a Kernel Update, the following steps are performed: 1. 2. 3. 4.
JSPM automatically stops the central instance and requests you to stop the dialog instances and CS instance After all the instances have been stopped, choose Next to start the Kernel Update. Once the kernel has been updated, a dialog box asks you to restart the CS instance. Choose Next so that JSPM can import the remaining Support Packages.
In general, corrections can be imported individually or in the stack. SAP urgently recommends you to use Support Package Stacks in order to ensure the consistency of the system and the applications. After starting, JSPM offers you the following options: • • • •
Support Package stack Single Support Package (advanced use) New Software Components Business Packages (advanced use)
If you only want to update individual software components and not all the components of the SP Stack, choose the option Single Support Package (advanced use). Caution: Before starting the import of Support Packages at a given level, you must make sure that the JSPM Update has at least the same level.
2012
© 2011 SAP AG. All rights reserved.
387
Unit 9: “SAP Patch Day”
TADM12_1
Figure 159: Single Support Package: Select Package Type, Specify Queue
In the next step, you specify the queue by choosing the required SP level or skip (do not import) for each software component. In the case of modified software components and systems monitored by NWDI, there is also the setting , Modified by NWDI. JSPM now checks the validity of the deployment queue and outputs the status OK, WARNING or REVISE accordingly.
388
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Corrections
Figure 160: Single Support Package: Check Queue
In the fourth step, deployment is started and the status of all the components changes to SCHEDULED or IN PROGRESS. In the last step, the final status is displayed (DEPLOYED, DEPLOYED WITH WARNINGS, NOT DEPLOYED, ERROR)
2012
© 2011 SAP AG. All rights reserved.
389
Unit 9: “SAP Patch Day”
TADM12_1
Figure 161: Single Support Package: Deploy Queue, Completed
390
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Corrections
Exercise 19: Applying Corrections Exercise Objectives After completing this exercise, you will be able to: • Import corrections for AS Java
Business Example SAP NetWeaver Application Server Java is used as the runtime environment for applications that conform to the J2EE standard. You can use Support Packages to correct errors and implement new functions for SAP NetWeaver AS Java.
Task 1: Preparations for applying Support Package Stacks Provide the required Support Packages, the corresponding file stack.xml, and the patches for the Support Package Stack in the directory EPS/in. The DEV and QAS systems that are installed on a host using the same EPS/in directory and the following steps need to be carried out only once on each host. Therefore, the following steps are to be carried out as group work of the DEV and QAS group. Prepare to import the Support Package Stack from the adm70\ADM200_72\Support_Packages share for the Java part of your Solution Manager 7.0 system. 1.
For the software component JSPM, determine which Support Package number belongs to the Support Package Stack to be imported.
2.
Copy the Support Packages of the Support Package Stack and the file stack.xml from the directory SPS to the directory EPS/in.
3.
Copy the patches for the Support Packages of the Support Package Stack from the directory Patches to the directory EPS/in.
Task 2: Applying a JSPM Update Apply the patch that you copied in the previous task in your system. 1.
Use JSPM to check the current JSPM level. To do this, start JSPM.
2.
Carry out the JSPM update.
3.
Use JSPM to check the current JSPM level. To do this, start JSPM.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
391
Unit 9: “SAP Patch Day”
TADM12_1
Result You have successfully applyed a JSPM Update for SAP NetWeaver AS Java.
Task 3: Advanced: Applying a Support Package Stack You can either carry out this task or the task of “applying a Support Package Stack with patches”. Use JSPM to apply a Support Package Stack. Caution: Close the SAP MMC and the Services if they are started on the host of your SAP system. Caution: Stop the complete dialog instance (ABAP+Java) of your SAP system. Close the SAP MMC and the Services if they are started on the host of your SAP system. 1.
Use the System Information to check the current Support Package level.
2.
Appy the Support Package Stack.
Task 4: Advanced: Applying Patches You can carry out this task only if you have successfully completed the task of “applying a Support Package Stack”. Use the JSPM to apply the patches for your Support Package Stack. You made these patches available in the first task in the directory EPS/in. Caution: Stop the complete dialog instance (ABAP+Java) of your SAP system. Close the SAP MMC and the Services if they are started on the host of your SAP system. 1.
Use the JSPM to apply the patches for your Support Package Stack.
Continued on next page
392
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Corrections
Task 5: Advanced: Applying a Support Package Stack with Patches You can either carry out this task or the task of “applying a Support Package Stack”. Hint: Before you apply patches with the Support Package Stack option, read SAP Note 1080821. Use the JSPM to apply a Support Package Stack with the relevant patches. Caution: Stop the complete dialog instance (ABAP+Java) of your SAP system. Close the SAP MMC and the Services if they are started on the host of your SAP system.
2012
1.
Use the System Information to check the current Support Package level.
2.
Set the parameter /jspm/includePatchesInStack in the file jspm_config.txt to the value true. You can find the file jspm_config.txt in the directory param.
3.
Apply the Support Package Stack with patches in one step.
© 2011 SAP AG. All rights reserved.
393
Unit 9: “SAP Patch Day”
TADM12_1
Solution 19: Applying Corrections Task 1: Preparations for applying Support Package Stacks Provide the required Support Packages, the corresponding file stack.xml, and the patches for the Support Package Stack in the directory EPS/in. The DEV and QAS systems that are installed on a host using the same EPS/in directory and the following steps need to be carried out only once on each host. Therefore, the following steps are to be carried out as group work of the DEV and QAS group. Prepare to import the Support Package Stack from the adm70\ADM200_72\Support_Packages share for the Java part of your Solution Manager 7.0 system. 1.
For the software component JSPM, determine which Support Package number belongs to the Support Package Stack to be imported. a)
Search for the file JSPM_0-... in the subdirectory SPS, which you can find on the training share adm70\ADM200_72\Support_Packages. is the number of the Support Package of the software component JSPM searched for.
b)
You can find the JSPM patches in the directory Patches (which you can find on the training share).
c)
The files have the following form: JSPMP_-.... specifies the number of the Support Package and specifies the number of the patch. Copy the file where corresponds to the number from the previous exercise step. If there are several of these files, copy the one that has the highest .
2.
Copy the Support Packages of the Support Package Stack and the file stack.xml from the directory SPS to the directory EPS/in. a)
You can copy the complete contents of the directory SPS to EPS/in. If the system issues a prompt asking you whether you want to overwrite a file, confirm this by choosing Do this for the nexst xx conflicts and choose Copy and Replace.
Continued on next page
394
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Corrections
3.
Copy the patches for the Support Packages of the Support Package Stack from the directory Patches to the directory EPS/in. a)
You can copy the complete contents of the directory Patches to EPS/in. If the system issues a prompt asking you whether you want to overwrite one of more files, confirm this by choosing Do this for the nexst xx conflicts and choose Copy and Replace.
Task 2: Applying a JSPM Update Apply the patch that you copied in the previous task in your system. 1.
2.
Use JSPM to check the current JSPM level. To do this, start JSPM. a)
Log on as user adm to your central instance's host.
b)
Start JSPM (/usr/sap///j2ee/JSPM/ go.bat) and log on with the SDM password given to you by the instructor.
c)
In the menu, choose Help → About. You can find the version of the JSPM, for example, 7.02...0, where specifies the Support Package and specifies the patch.
Carry out the JSPM update. a)
If you have not yet already done so, start the JSPM (see 1.)
b)
In the step Select Package Type, choose the option Java Support Package Manager (JSPM) followed by Next.
c)
In the step Specify Queue, check whether the correct Support Package and patch was selected. If this is not the case, choose the correct Support Package and patch (see task 1). Confirm with Next.
d)
In the step Check Queue, start the import of the JSPM update.
e)
In the step Deploy Queue, the component is assigned the status SCHEDULED and is then displayed with the achieved status DEPLOYED after deployment. End the JSPM by choosing Exit.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
395
Unit 9: “SAP Patch Day”
3.
TADM12_1
Use JSPM to check the current JSPM level. To do this, start JSPM. a)
Start JSPM (/usr/sap///j2ee/JSPM/ go.bat) and log on with the SDM password given to you by the instructor.
b)
In the menu, choose Help → About. Here, you can find the version of the JSPM, for example, 7.02...0, where specifies the Support Package and specifies the patch.
Result You have successfully applyed a JSPM Update for SAP NetWeaver AS Java.
Task 3: Advanced: Applying a Support Package Stack You can either carry out this task or the task of “applying a Support Package Stack with patches”. Use JSPM to apply a Support Package Stack. Caution: Close the SAP MMC and the Services if they are started on the host of your SAP system. Caution: Stop the complete dialog instance (ABAP+Java) of your SAP system. Close the SAP MMC and the Services if they are started on the host of your SAP system. 1.
Use the System Information to check the current Support Package level. a)
Call the System Information via its URL. The URL is http://twdfxxxx.wdf.sap.corp:5$$00/monitoring/SystemInfo. Replace twdfxxxx with the name of the training host and replace $$ with the instance number of your system. Then log on to your system. Navigate to the area Software Components Version. Here you will find the Support Package level for the components sap.com/SAP-JEECOR and sap.com/SAP-JEE. Navigate to all components ... where you will find all the imported Support Packages and their levels.
Continued on next page
396
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Corrections
2.
Appy the Support Package Stack. a)
Log on as user adm to your central instance's host. Start JSPM (/usr/sap///j2ee/JSPM/ go.bat) and log on with the SDM password given to you by the instructor. In the step Select Package Type, choose the option Support and Enhancement Package Stack and confirm by choosing Next. The stack that is available according to D:\usr\sap\trans\EPS\in\SPStab.xml and which may be possible to apply is now displayed.
b)
In the Specify Queue step, choose the highest available Support Package Stack level. Hint: The selected SP Stack level must be higher than that of the stack that is already imported! Choose Show Details to see which Support Package levels of the individual components. Now confirm with Next.
c)
In the step Check Queue, the status OK or WARNING should be displayed for all components. Choose Start to start the deployment.
d)
In the step Deploy Queue, the components are assigned the status SCHEDULED or IN PROGRESS, and, after the deployment, they are displayed with the status DEPLOYED or DEPLOYED WITH WARNING.
e)
In the Completed step, select Exit.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
397
Unit 9: “SAP Patch Day”
TADM12_1
Task 4: Advanced: Applying Patches You can carry out this task only if you have successfully completed the task of “applying a Support Package Stack”. Use the JSPM to apply the patches for your Support Package Stack. You made these patches available in the first task in the directory EPS/in. Caution: Stop the complete dialog instance (ABAP+Java) of your SAP system. Close the SAP MMC and the Services if they are started on the host of your SAP system. 1.
Use the JSPM to apply the patches for your Support Package Stack. a)
Start JSPM (/usr/sap///j2ee/JSPM/ go.bat) and log on with the SDM password given to you by the instructor. In the step Select Package Type, choose the option Single Support Packages (advanced use) followed by Next.
b)
In the step Specify Queue, check the proposed Support Package and patch level. These have the format: 7.02.., where specifies the Support Package level and specifies the patch level. If, for a software component, the Support Package level is different from the current Support Package level, choose a patch that corresponds to the current Support Package level or deactivate the deployment of this patch by choosing skip. You do not need to concern yourself here with software components for which no patches or Support Packages were found. Now confirm with Next.
c)
In the step Check Queue, the status OK or WARNING should be displayed for all components. Choose Start to start the import.
d)
In the step Deploy Queue, the components are assigned the status SCHEDULED or IN PROGRESS, and, after the deployment, they are displayed with the achieved status DEPLOYED or DEPLOYED WITH WARNING.
e)
In the Completed step, select Exit.
Continued on next page
398
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Corrections
Task 5: Advanced: Applying a Support Package Stack with Patches You can either carry out this task or the task of “applying a Support Package Stack”. Hint: Before you apply patches with the Support Package Stack option, read SAP Note 1080821. Use the JSPM to apply a Support Package Stack with the relevant patches. Caution: Stop the complete dialog instance (ABAP+Java) of your SAP system. Close the SAP MMC and the Services if they are started on the host of your SAP system. 1.
Use the System Information to check the current Support Package level. a)
Call the System Information via its URL. The URL is http://twdfxxxx.wdf.sap.corp:5$$00/monitoring/SystemInfo. Replace twdfxxxx with the name of the training host and replace $$ with the instance number of your system. Then log on to your system. Navigate to the area Software Components Version. Here you will find the Support Package level for the components sap.com/SAP-JEECOR and sap.com/SAP-JEE. Navigate to all components ... where you will find all the imported Support Packages and their levels.
2.
Set the parameter /jspm/includePatchesInStack in the file jspm_config.txt to the value true. You can find the file jspm_config.txt in the directory param. a)
Log on as user adm to your central instance's host. In the file /usr/sap///j2ee/JSPM/ param/jspm_config.txt, search for the parameter /jspm/includePatchesInStack and replace the value false with true. Save your entry.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
399
Unit 9: “SAP Patch Day”
3.
TADM12_1
Apply the Support Package Stack with patches in one step. a)
Start JSPM (/usr/sap///j2ee/JSPM/ go.bat) and log on with the SDM password given to you by the instructor. In the step Select Package Type, choose the option Support and Enhancement Package Stack and confirm by choosing Next. The stack that is available according to D:\usr\sap\trans\EPS\in\stack.xml and which it may be possible to import is now displayed.
b)
In the Specify Queue step, choose the highest available Support Package Stack level. Hint: The selected SP Stack level must be higher than that of the stack that is already applyed! Choose Show Details to see the Support Package levels of the individual components. Now confirm with Next.
c)
In the step Specify Queue Patches, check the proposed Support Package and patch level. These have the format: 7.02.., where specifies the Support Package level and specifies the patch level. If, for a software component, the Support Package level is different from the current Support Package level, choose a patch that corresponds to the current Support Package level or deactivate the deployment of this patch by choosing 7.02..0. Now confirm with Next.
400
d)
In the step Check Queue, the status OK or WARNING should be displayed for all components. Choose Start to start the deployment.
e)
In the step Deploy Queue, the components are assigned the status SCHEDULED or IN PROGRESS, and, after the deployment, they are displayed with the achieved status DEPLOYED or DEPLOYED WITH WARNING.
f)
In the Completed step, select Exit.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Importing Corrections
Lesson Summary You should now be able to: • Install Support Packages for SAP NetWeaver Application Server Java-based systems
Related Information • • •
2012
SAP NetWeaver Support Package Stack Guide SAP Note 891983, JSPM: Composite-SAP Note SAP NetWeaver 2004s AS Java SAP Service Marketplace: Quick Link /jspm
© 2011 SAP AG. All rights reserved.
401
Unit 9: “SAP Patch Day”
TADM12_1
Lesson: Other Tools in Software Lifecycle Management Lesson Overview This lesson provides you with an overview of other tools involved in software lifecycle management..
Lesson Objectives After completing this lesson, you will be able to: •
List other tools involved in the software lifecycle management environment
Business Example Alongside tools for the installation and import of patches, other tools are involved in software lifecycle management such as Software Deployment Manager (SDM), jload, SAPjup.
The Software Deployment Manager (SDM) The Software Deployment Manager (SDM) is used by a large number of tools in the AS Java environment. It is responsible for deploying software in AS Java and is therefore used in close conjunction with NWDI, JSPM, etc. SDM is also the tool with which you can manage and “deploy” the special software packages that you receive from SAP and other providers. Deployment is the last step in the delivery process of software; that is, the transfer of the supplied software packages – SDAs, SCAs or other J2EE archives – into the runtime environment of the SAP systems. Hint: The Software Deployment Archive (SDA) is the delivery format for SAP AS Java-based applications. It is a ZIP-compatible archive format. The SDA contains the manifest information; that is, package-related data for the archives contained in it (such as jar, war) and an SAP manifest that contains the additional information required for software logistics. An SDA is the smallest unit that can be supplied for deployment. The SDA also represents the smallest unit for which patches can be created and delivered. A Software Component Archive (SCA) is the physical representation of a status of a software component. It contains a specific number of SDAs, the set of which describes a precisely-defined version status. An update of an SCA always results in a newer version status of the software component.
402
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Other Tools in Software Lifecycle Management
Figure 162: SDM Gui-to-SDM Server Connection
The SDM is a client/server application. On the AS Java side there runs the SDM server that is started by the central instance of the AS Java automatically. The client provides a graphical user interface which you can start using the script RemoteGui.bat or RemoteGui.sh via the file system /usr/sap///sdm/program.
2012
© 2011 SAP AG. All rights reserved.
403
Unit 9: “SAP Patch Day”
TADM12_1
Figure 163: SDM Gui: Logon
The deployment of SDAs/SCAs using the Software Deployment Manager stores the data in the SDM repository, with which the SDM controls the management of the installed archives. The SDM also identifies dependencies between archives and therefore offers support for the software lifecycle tools during installation and maintenance. You can reset the SDM password in the SDM Gui after logging on. If you can no longer log on at the SAP Gui because you do not know the password, it is necessary to set the SDM password at operating system level by means of SDM commands.
404
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Other Tools in Software Lifecycle Management
Figure 164: Changing the SDM Password
Hint: If you change the password of the SDM, this can also have consequences for the automatic access to the SDM for other tools, such as the SAP NetWeaver Developer Studio.
Copying and Migrating Systems In various situations during your Solution Lifecycle, it may be useful to copy or migrate a system. SAP recommends that you make a system copy if you want to set up a test, demonstration or training system. You must also perform a system copy if you want to change your operating system or database.
2012
© 2011 SAP AG. All rights reserved.
405
Unit 9: “SAP Patch Day”
TADM12_1
You can find additional information about copying systems in the SAP Service Marketplace under http://service.sap.com/systemcopy. Note: • •
•
In NetWeaver 04 and below (SAP Web Application Server 6.40), it was only possible to perform system copies of ABAP systems. With NetWeaver 04 SR1 (SAP Web Application Server 6.40 SR1), you can also perform system copies for a Java add-in in an ABAP system as well as for Java standalone systems. In NetWeaver 2004s, you can include not only an ABAP or Java standalone system but also a system consisting of an ABAP and Java stack in this operation.
You create the following types of system copy: •
•
You perform a homogeneous system copy when your target system runs on the same operating system and the same database system as your source system.. The contents of the database are copied from the source to the target system. You perform a heterogeneous system copy when you want to change the operating system or database system. The term migration is a synonym for heterogeneous system copy.
You can use the following procedures/methods for the two types of system copy: • •
406
Database-specific method: homogeneous system copies only Database-independent method: homogeneous and heterogeneous system copies
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Other Tools in Software Lifecycle Management
Figure 165: System Copy
Database-specific methods are not available for all database systems. For more information, see the corresponding guidelines on copying systems under http://service.sap.com/systemcopy. You can use the SAP installation tool SAPinst to create exports and imports of the contents of your Java database, the file system and the configuration in database-independent format. SAPinst uses the tool Jload. Jload generates a database export of all the SAP objects which are defined in the Java Dictionary and archives the configuration and file system components. A Java-based system consists of data which is stored in the database and in the file system. The Software Deployment Manager (SDM) is stored in the file system. Every SAP instance possesses a unique ID which is stored in the database. Note: SAP Note 970518 lists the Java components based on SAP NetWeaver 7.0 SR2 which are released for system copies.
SAP Release Upgrade SAP supplies high-performance tools (SAPup and SAPJup) and sophisticated procedures for upgrading an SAP system. SAP constantly enhances these tools and procedures in order to ensure seamless upgrade operations.
2012
© 2011 SAP AG. All rights reserved.
407
Unit 9: “SAP Patch Day”
TADM12_1
The SAPup tool is used to upgrade AS-ABAP-based SAP NetWeaver systems. In contrast, SAPJup is the right tool for upgrading AS Java-based SAP NetWeaver systems.
Figure 166: SAPJup
408
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Other Tools in Software Lifecycle Management
Lesson Summary You should now be able to: • List other tools involved in the software lifecycle management environment
2012
© 2011 SAP AG. All rights reserved.
409
Unit 9: “SAP Patch Day”
TADM12_1
Lesson: Enhancement Packages Lesson Overview In this lesson you will learn what SAP enhancement packages are.
Lesson Objectives After completing this lesson, you will be able to: •
Understand the idea of SAP enhancement packages
Business Example New functions are required for an existing SAP system. There are no plans for a complete system upgrade. New functions are delivered in SAP enhancement packages.
SAP Enhancement Package In the past, new functions for an existing release were “hidden” in Support Packages. This meant that Support Packages did not just consist of legal changes and error corrections, but also imported new functions. However, not all new functions were delivered by Support Package. The really “large” new functions were only available with a new release. Therefore, a system upgrade was necessary every few years. A system upgrade (for example, from SAP R/3 4.6C to SAP ECC 6.0) is a complete delivery of all software components in the new release. After the upgrade, the system behaves like the new release. Before it can be used in production operation you therefore need to make numerous adjustments. These include modification adjustments, delta Customizing, delta developments for customer developments, and enhancements. The functional acceptance test is also very time-consuming. You normally need to allow a period of several months for an upgrade project of a system landscape. A system upgrade is thus relatively expensive. To reduce the cost and effort involved, SAP is delivering SAP enhancement packages for all applications. This began with SAP ERP 6.0 in 2007. The current SAP ERP Enhancement Package in 2010 is Enhancement Package 4 for SAP ERP 6.0. SAP enhancement packages are complete deliveries of several software components of one ore more SAP systems. In other words, they are a partial upgrade of several SAP systems.
410
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Enhancement Packages
The Switch Framework is used to deliver the new functions in a “hidden” way. The Switch Framework allows changes to be made to repository objects without these changes becoming effective immediately. If you need to use the new functions, you have to activate these changes first. It is even possible to make various changes to a single repository object and activate the one individual changes required. Hint: The switch framework is only available in some AS ABAP-based systems, AS ABAP 7.00 and higher, not in AS Java-based systems. In some AS ABAP-based systems, it is therefore possible to import parts of an SAP enhancement package without any immediate functional change. This means no further actions are necessary after the import, unlike a complete system upgrade. In a second step you can activate the needed functions by activating Business Function sets (BC sets). As a result, the time needed for implementation and testing is kept to a minimum. Caution: In real live you always have to bind Support Packages to the SAP enhancement package installation process. Support Packages are not switchable. So you need to perform a complete regression test even if you do not activate any Business Function sets! Just as if you would import Support Packages only. Hint: Therefor SAP recommends to import about once a year the newest SAP enhancement package together with its corresponding Support Packages instead of applying Support Packages only.
2012
© 2011 SAP AG. All rights reserved.
411
Unit 9: “SAP Patch Day”
TADM12_1
Figure 167: SAP Enhancement Packages and Software Components
SAP enhancement packages are therefore an upgrade of individual software components with the advantage that the new functions can be activated when required. Note: Selective activation of business functions of an SAP enhancement package is only possible in certain AS ABAP-based SAP systems! The advantages of SAP enhancement packages are: • • • •
Simple adaptation to legal requirements Easier to maintain and plan Fewer complete system upgrades necessary The new function can be activated as and when required (only possible in some AS ABAP-based systems) Note: An SAP enhancement package not only delivers software components of an SAP system, but also different SAP systems of an application, for example SAP ERP.
412
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Enhancement Packages
As such, an SAP ERP 6.0 enhancement package might contain some software components of an SAP ECC 6.0 system, and additional software components or content of an SAP NetWeaver Portal 7.0 system, and components of an SAP XSS 600 system. An SAP enhancement package can therefore include elements for various components in an application (in this example: SAP ERP 6.0). Since SAP enhancement packages are complete deliveries of the software components they contain, they are cumulative. This means that Enhancement Package 4 for SAP ERP 6.0, for example, contains Enhancement Package 3 for SAP ERP 6.0. SAP enhancement packages therefore do not need to be imported in a specific sequence (as is the case with Support Packages). You can implement the latest SAP enhancement package directly (as is the case with a system upgrade). The selected elements of an SAP enhancement package are imported with the SAP Enhancement Package Installer (SAPehpi). Note: Importing elements of an SAP enhancement package causes a technical downtime comparable to the downtime of a complete system upgrade. The project length and project costs are much lower, however, due to less testing effort. Hint: Support Packages should always be selected corresponding to the release level of their software component. For example, if SAP_APPL is of release 604, and SAP_HR is of release 600, then you need to import release 604 SAP_APPL Support Packages and release 600 SAP_HR Support Packages. Hint: With the current release the SAP Enhancement Package Installer (SAPehpi) can also be used to import Support Packages only! The effort and complexity is higher compared to importing Support Packages with transaction SPAM. But the downtime is much shorter!
2012
© 2011 SAP AG. All rights reserved.
413
Unit 9: “SAP Patch Day”
TADM12_1
Lesson Summary You should now be able to: • Understand the idea of SAP enhancement packages
Related Information SAP course ADM327 - Importing Enhancement Packages
414
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Unit Summary
Unit Summary You should now be able to: • Explain how to apply a kernel patch • Explain how to apply a SAP Support Package for AS ABAP based SAP systems • Explain how to apply a SAP Support Package for AS Java based SAP systems • Explain what an SAP Support Package Stack is • Describe the concept of SAP Notes and Support Packages • Explain the concept of maintenance certificates • Describe a maintenance transaction • Explain the use of the Support Package Manager and import a SPAM/SAINT update. • Import Support Packages with transaction SPAM • Provide a general explanation of the import process for Support Packages • Install Support Packages for SAP NetWeaver Application Server Java-based systems • List other tools involved in the software lifecycle management environment • Understand the idea of SAP enhancement packages
2012
© 2011 SAP AG. All rights reserved.
415
Unit Summary
416
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Test Your Knowledge
Test Your Knowledge 1.
What are the steps to manually apply a kernel patch?
2.
For what are Support Packages used? Choose the correct answer(s).
3.
□ □
A B
□
C
□ □
D E
To enter user data. To import SAP objects to keep the system at the current maintenance level. To implement adjustments in the system due to changes in legal requirements. To transport programs developed by the customer. To import all the transport requests that SAP makes available on the SAP Service Marketplace.
What can be done with a maintenance transaction? Choose the correct answer(s).
□ □ □ □ □ 4.
A B C D E
Import Support Packages. Calculate Support Package Stacks for your SAP systems. Approve objects in your download basket. Import SAP Notes. Import SAP enhancement packages
You always have to import all available SPAM/SAINT updates in order, since they build on one another. Determine whether this statement is true or false.
□ □ 5.
True False
The queue for importing the SPAM update must be confirmed manually. Determine whether this statement is true or false.
□ □
2012
True False
© 2011 SAP AG. All rights reserved.
417
Test Your Knowledge
6.
TADM12_1
A prerequisite for importing a SPAM/SAINT update is that the system must not have any terminated import procedures for Support Packages. Determine whether this statement is true or false.
□ □ 7.
True False
Support Packages can be imported in any order. Determine whether this statement is true or false.
□ □
True False
8.
With which program do you install a Support Package for SAP NW Application Server Java?
9.
What tools are used in AS Java software lifecycle management? Choose the correct answer(s).
□ □ □ □
A B C D
SAPup SAPJload SDM SAPJup
10. SAP enhancement packages are imported in order to implement new functions. For these new functions to be effective in an AS ABAP-based system, they must be . Fill in the blanks to complete the sentence.
418
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Test Your Knowledge
Answers 1.
What are the steps to manually apply a kernel patch? Answer: 1. 2. 3.
2.
Stop the SAP system (Windows OS: including Windows services). Copy and paste the kernel patch to the central kernel directory. Start the SAP system (Windows OS: first start the Windows services).
For what are Support Packages used? Answer: B, C Support Packages are not used to enter user data. Customer developments are transported to other systems using transport requests. Transport requests from SAP are imported with the Transport Management System (TMS).
3.
What can be done with a maintenance transaction? Answer: B, C A maintenance transaction can not import SAP Notes, Support Packages and SAP enhancement packages. SAP Notes are imported via the Note Assistant, Support Packages for AS ABAP based systems via transaction SPAM, Support Packages for AS Java based systems via tool JSPM, SAP enhancement packages via the tool SAPehpi.
4.
You always have to import all available SPAM/SAINT updates in order, since they build on one another. Answer: False All repository objects that belong to the tools are always upgraded during the SPAM/SAINT update. It is therefore not necessary to follow any particular order.
5.
The queue for importing the SPAM update must be confirmed manually. Answer: False It is neither necessary to define a special queue, nor to confirm this non-existent queue.
2012
© 2011 SAP AG. All rights reserved.
419
Test Your Knowledge
6.
TADM12_1
A prerequisite for importing a SPAM/SAINT update is that the system must not have any terminated import procedures for Support Packages. Answer: True This is true, the system must not have any terminated import procedures for Support Packages.
7.
Support Packages can be imported in any order. Answer: False Support Packages must be imported in ascending order, without any gaps.
8.
With which program do you install a Support Package for SAP NW Application Server Java? Answer: With the JSPM program.
9.
What tools are used in AS Java software lifecycle management? Answer: C, D SDM, SAPJup, JLoad, JSPAM, ... are tools used for AS Java software lifecycle management.
10. SAP enhancement packages are imported in order to implement new functions. For these new functions to be effective in an AS ABAP-based system, they must be activated. Answer: activated Importing elements of an SAP enhancement package in AS ABAP-based systems does not change the existing function until activation.
420
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
421
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
422
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit 10 Output Management Unit Overview In this unit, you learn about the output processing architecture in the SAP system. You learn how to define printers and spool servers in the system and how to manage spool and output requests. You also learn how to set up central printer administration.
Unit Objectives After completing this unit, you will be able to: • • • • • • • • • •
Describe the architecture and data flow of output processing in ABAP-based SAP systems Create printers and spool servers in the SAP system List important access methods Manage spool requests Describe the concept of logical spool servers Set up logical spool servers Manage spool and output requests Name the prerequisites for using the Printing Assistant for Landscapes (PAL) Explain the terms in the PAL environment Set up and use a PAL landscape
Unit Contents Lesson: Configuring Printers in AS ABAP ....................................... 424 Exercise 20: Configure Printers .............................................. 439 Lesson: Concept of Logical Spool Servers ...................................... 450 Exercise 21: Logical Spool Servers .......................................... 457 Lesson: Managing Spool Requests .............................................. 461 Exercise 22: Managing Spool Requests .................................... 467 Lesson: Printing Assistant for Landscapes (PAL) .............................. 470 Exercise 23: Central Administration of Output Devices (PAL)............ 477
2012
© 2011 SAP AG. All rights reserved.
423
Unit 10: Output Management
TADM12_1
Lesson: Configuring Printers in AS ABAP Lesson Overview In this lesson, you will learn about the output processing architecture. You will learn how to set up printers in the SAP system.
Lesson Objectives After completing this lesson, you will be able to: • • • •
Describe the architecture and data flow of output processing in ABAP-based SAP systems Create printers and spool servers in the SAP system List important access methods Manage spool requests
Business Example The administrator sets up printers in the SAP system and monitors the output of spool requests.
Printing from SAP Systems There are various document classes in the SAP system (such as report lists, SAPscript or SAP Smart Forms documents). Although the way in which documents are created may be completely different, the output on paper is always performed using the same mechanism in two steps: First a spool request is created. The spool request contains device-independent print data and includes administrative information (such as author, date, number of copies) and the actual print data. Only when the spool request is to be output on a particular device is an output request created. The device-independent print data from the spool request is converted to the printer language that the selected output device understands.
424
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Configuring Printers in AS ABAP
Figure 168: Data Flow During Printing
This procedure allows the user to display a spool request before output. There can also be several output requests for one spool request. This can avoid the user having to recreate (possibly with a great deal of effort) a spool request, if, for example, the toner in a printer is exhausted, or the wrong paper was in the tray. The user can of course create a spool request and an output request at the same time (immediate print) by choosing the Print out immediately option. The actual document content of a spool request is stored in TemSe (for temporary sequential objects), for which you define the storage location with the profile parameter rspo/store_location. • •
Value db (the default value): Spool requests are stored in database table TST03 (advantage: backup as part of the database). Value G: Storage at operating system level in the (global) directory /usr/sap//sys/global (advantage: performance).
SAP Note 20176 contains additional possible values for rspo/store_location. Note: You can also specify the storage location individually for each output device in transaction SPAD (list or details of output device, then menu path Edit → Data Storage).
2012
© 2011 SAP AG. All rights reserved.
425
Unit 10: Output Management
TADM12_1
Creating an output request prompts the SAP spool system to send a (usually) printer-dependent, completely formatted data stream to a printer through an operating system spooler (OS spool). This means that the addressed printer model must be known to the SAP system. Definitions of this type are described as device types. If a printer cannot be controlled at operating system level, it cannot be used from the SAP system, either. There are several ways in which a spool work process can reach an operating system spooler. The most important of these connections, described as access methods, are introduced in the following sections.
Local Printing
Figure 169: Local Printing
In local printing, the spool work process and operating system spool run on the same host. It is irrelevant whether the printer is directly connected to this host, or is reached over a network (and possibly another print server). The spool work process passes on its data locally, that is on the same host. •
•
426
On UNIX systems, the print data with access method L is output using operating system methods (for example, with the commands lp or lpr). The specific syntax is stored in profile parameters. Under Microsoft Windows, the data with access method C is passed directly to the operating system print API.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Configuring Printers in AS ABAP
Local printing is the fastest and most reliable connection from the SAP system to the operating system. As soon as the spool work process has transferred its data, it can deal with new output requests, even if the operating system spooler is still occupied. You can configure multiple spool work processes for an SAP instance. Regardless of the access method, this affects the output sequence. Different spool requests for the same printer may be printed in a different order to that in which they were created. If you require output in sequence, you can specify this for individual printers. However, a setting of this type reduces the ability to process printouts in parallel. For more information about this topic, see SAP Note 108799.
Remote Printing With remote printing, the spool work process and operating system spooler run on different hosts. In exactly the same way as with local printing, it is irrelevant from the SAP system's point of view whether the printer is directly connected to the remote host, or is reached using another network connection.
Figure 170: Remote Printing
2012
© 2011 SAP AG. All rights reserved.
427
Unit 10: Output Management
TADM12_1
Typical scenarios for remote printing are: •
•
•
Network printers provide their own operating system spoolers, and are directly connected to a computer network. Printers of this type are directly addressed from the SAP system using their names (access method U). Access method U is also used if the remote host is a UNIX system. SAP Note 39405 describes how access method U can be used for the various UNIX versions. SAP provides the SAPSprint program for all hosts running on Microsoft Windows operating systems. SAPSprint is a Windows service capable of multi-threading. Each output request is processed in a separate, isolated thread. The output requests that SAPSprint receives from the SAP system can thus be transferred to a particular printer individually. If the printer is not working, this does not disturb the printing of other output requests on the other printers. Access method S is usually used here (SAP protocol), but access method U (UNIX Berkeley protocol) is also supported.
For performance reasons, you should only use remote printing in a LAN environment (not WAN), and ensure that the operating system spoolers are available.
Front-end Printing SAP users can output documents on their local printers using front-end printing. These local printers do not need to be individually defined in the SAP system. Rather the system administrator only needs to create a representative output device for each operating system platform.
428
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Configuring Printers in AS ABAP
Figure 171: Front-end Printing with Control Technology (Access Method G)
As of SAP Basis Release 4.6C, a new procedure is available for front-end printing: front-end printing using control technology with access method G. Controls are DLLs that run in the process context of the SAP GUI. The new print control receives the print data and transfers it to the printing system for the operating system. In contrast to previous front-end printing with access method F, front-end printing with control technology and access method G offers the advantage that front-end printing using SAP GUI for Java can be set up irrespective of the platform. Printing using the Windows Terminal Server is also made easier with front-end printing using control technology. SAP Note 821519 contains useful information about front-end printing using control technology including the exact system requirements. The processing of front-end printing is also performed, as with the other output methods, using a spool work process. There can, therefore, be conflicts between regular and front-end print requests. The profile parameter rdisp/wp_no_spo_Fro_max allows you to define the maximum number of spool work process for front-end printing for each SAP instance (the standard value is 1). Front-end printing is suitable for output on local printers; however, it is not for production or mass printing.
2012
© 2011 SAP AG. All rights reserved.
429
Unit 10: Output Management
TADM12_1
Front-end printing requires a connection to the front-end PC. However, this method cannot be used for background processing. For more information, see SAP Composite Note 128105. SAP Note 771683 describes front-end printing with the integrated ITS (for SAP systems as of AS ABAP 6.40) when using the SAP GUI for HTML. SAP Note 150533 contains information about front-end printing when using Windows Terminal Server. If you are using the SAP GUI for HTML and want to print on your front end, this is also possible through access method G. The print data is sent to the browser and displayed using this print method. You can then print the document on your front end. SAP recommends that you configure at least one spool work process on each application server that (end) users log onto. If no work process is running on the application server that a user wants to use for front-end printing, the system selects one of the available spool servers with the least load to process the print request. You can define a spool server specifically for front-end printing by setting the profile parameter rspo/local_print/server to the required server name.
Creating Output Devices The configuration of the spool system is a system administration task. The central tool for this is transaction SPAD (menu path Tools → CCMS → Print → Spool Administration). Creating Output Devices Local
Device Attributes
Device Type Spool Server
Host Spool Access Method Access
Remote
Front end (Microsoft Windows)
Select the appropriate type in each case
SWIN
L (Unix) C (Windows)
G
S or U
–
Host Printer
OS Printer Name
Host
fix
–
–
Destination Host
–
specify
–
_ _DEFAULT
With front-end printing with control technology (access method G), the printer is given a generic name in the SAP system, and is assigned to the physical device _ _DEFAULT (for Microsoft Windows front ends). Since the models used as front-end
430
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Configuring Printers in AS ABAP
printers can vary considerably, the device type SWIN is often assigned for Microsoft Windows front ends. When printing with SAP GUI for Java on other operating systems, you have to use a corresponding device type, such as PostScript or PDF1. If you are using SAP GUI for HTML for front-end printing, the device type PDF1 is suitable. The print data is then transferred to the front-end browser as a PDF document, and can be printed locally. Output Devices for Front-end Printing SAP GUI for Windows
SAP GUI for Java SAP GUI for HTML
Device Type
SWIN
Select the appropriate type in each case
PDF1
Access Method
G
G
G
Host Printer
_ _DEFAULT
specify
Any
To create an output device, call transaction SPAD and choose Output Devices on the Devices / Servers tab page. If there are a large number of devices in your system already, you can restrict the output list in the field next to the button (for example “PR*”). Important information for an output device: Output device Name, maximum of 30 characters long (case-sensitive). Short name For internal system purposes (can be automatically generated). Device type Printer model/family (more information about this below). The device type SWIN transfers the spool data from the SAP system to the Microsoft Windows printer driver. This is useful, for example, if various printers are used for front-end printing in a Microsoft Windows environment. Spool server SAP application server with spool work processes or logical server. Location For example, building and room number (so that users can find their output). Message Used to temporarily override the location (such as “Is currently in maintenance”).
2012
© 2011 SAP AG. All rights reserved.
431
Unit 10: Output Management
TADM12_1
Lock printer in SAP system Output requests for printers for which this indicator is selected are created but not transferred to the printer. The user receives the message ...no immediate printing. Host spool access method How does a spool work process contact the operating system spooler? Host printer Name of the printer at operating system level. Note that this name is case-sensitive. Under Microsoft Windows, there must not be a space in the printer name, and network printers are addressed using their UNC names (in the format \\R12345\P42). The entry _ _DEFAULT controls the Windows default printer (for front-end printing using SAP GUI for Windows). Host name Only for local printing, is calculated automatically from the spool server. Destination host Only for remote printing. Name of the host on which the operating system spooler is running.
Device Types The SAP system uses a device type to format the output device-specific print output. Hint: When reference is made to an output device in the SAP environment, it does not necessarily mean a printer. An output device can also be, for example, an Output Management System or an archiving system. When the spool work process generates an output request, it uses the specifications of the device type. That is, the device type describes how print data should be formatted for a particular output device. The following figure illustrates how a device type is created.
432
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Configuring Printers in AS ABAP
Figure 172: What Is a Device Type?
The following list explains the terms from the above graphic: Page format A page format describes the format of a printable page in the SAP system. A large number of standard page formats are predefined in the system. If a device is to support additional format that are not delivered, you can define new formats. Consider when doing so that your output device must, of course, be able to use the new format. Format type A format type describes how output should appear on paper. It primarily contains the formatting of the page format. Format A format is a device-specific implementation of a format type. That is, the SAP system can use the description in a format to control a device correctly to, for example, perform an output on a page with the Letter format. A format type is therefore not device-specific; the format, on the other hand, is a device-specific implementation of a format type.
2012
© 2011 SAP AG. All rights reserved.
433
Unit 10: Output Management
TADM12_1
Character set A character set contains the characters that can be output by a particular output device. That is, to be able to use a particular character set for a selected printer model in the SAP environment, the device type assigned to this printer model must contain this character set. Print control Print controls allow the control of particular display options of output devices, such as boldface, changing the font size, changing the font, and so on. Print controls use device-specific control character sequences. That is, to create a new device type, the display options offered in the SAP system must be stored with the control character sequences that the selected printer model supports. The control character sequences to be used can be found in the device vendor's documentation. You can see that using devices for which no suitable device type exists in the SAP system may mean a significant effort.
Figure 173: Selecting an Appropriate Device Type
434
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Configuring Printers in AS ABAP
How do you assign the correct device type to your printer? •
•
•
•
•
In the ideal situation, there is already a device type in your SAP system. Note that a separate device type is not required for every printer model of a vendor, but just for each model family. Several printer manufacturers participate in the SAP Printer Vendor Program. It is easy to import the corresponding device types for the supported printer models using the Wizard (available in transaction SPAD for output devices). For many printers, you can use a generic format (such as PostScript) for which device types exist. It is also possible that your printer can be addressed in the same way as another model that is supported by SAP (compatibility mode). There are drivers for the Microsoft Windows operating systems for practically all printers on the market. You can use these printers as output devices with device type SWIN. The conversion to a print data stream is performed by the Microsoft Windows driver in this case. The SAP system contains all of the tools required to create your own device types or to adjust copies of existing device types. Detailed knowledge of the SAP spool system and the printer control are required to do this. You should weigh up the expense against the purchase of supported printers.
Device Type Wizard The following figure shows a roadmap with the major steps if you want to create an output device in your SAP system for output devices which are supported by the SAP Printer Vendor Program:
2012
© 2011 SAP AG. All rights reserved.
435
Unit 10: Output Management
TADM12_1
Figure 174: Roadmap: Using the Device Type Wizard
To start the Device Type Wizard, launch transaction SPAD and navigate to the list of Output Devices. Double-click an existing ouput device, or create a new one. On the tab Device Attributes you will find a button Device Type Selection (icon with magic wand). The major steps are: 1. 2. 3. 4. 5. 6. 7.
436
Within the Device Type Wizard, check if your printer shows up in the list of known printers. If necessary, download the attachment tspopi-.zip from SAP Note 1036961. Unzip that file and import the XML file tspopi-.xml into the Device Type Wizard. Find and double-click the printer in question in the Device Type Wizard. In case of status “device type not exist on the system”, open the SAP Note for that device. Using the Device Type Wizard, download the SAP Note for the printer in question. Within the Device Type Wizard, import the proper SAP Note for your printer.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Configuring Printers in AS ABAP
Now you can either create new ouput devices (or change exising ones) which make use of the new device type.
2012
© 2011 SAP AG. All rights reserved.
437
Unit 10: Output Management
438
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Configuring Printers in AS ABAP
Exercise 20: Configure Printers Exercise Objectives After completing this exercise, you will be able to: • Create printers and spool servers in the SAP system
Business Example The administrator sets up printers in the SAP system.
Task 1: Check the Print Environment First check the print environment of your SAP system. 1.
How many spool work processes are set up for the application server to which you are currently logged on?
2.
How many spool work processes are configured in your entire SAP system?
3.
How many spool servers are available in your SAP system?
4.
As the default setting for your SAP user, change the settings so that an output request is not created immediately for a spool request.
5.
Which printers are defined at operating system level of your server? Where do they print?
6.
(If possible) Which printers are defined at operating system level of your front-end PC in the training room? Where do they print to?
Task 2: Local Printing Create an output device with a local host spool access method. 1.
In your SAP system, create a local printer Local## with the short name LO## (where ## denotes your group number) that controls one of the previously defined printers.
2.
Output any list (Suggestion: All profile parameters that begin with “rspo”) without immediate printing on the printer Local##.
3.
Check your output.
4.
Optional: Display the generated print data. Instead of checking at operating system level, you can view the file from the SAP system using transaction AL11 (SAP directory DIR_C_TEMP). Continued on next page
2012
© 2011 SAP AG. All rights reserved.
439
Unit 10: Output Management
TADM12_1
Task 3: Remote Printing Install SAPSprint, and create an output device with a remote host spool access method. 1.
Install and start SAPSprint on your server. Caution: This exercise section should only be performed once for each host: Decide whether the DEV group or OAS group should perform this exercise.
2.
In the SAP system, create a remote printer Remote## with the short name RE## that controls a printer on a remote server. Note: These exercise sections should be performed by both groups again.
3.
As the default setting for your SAP user, change the settings so that an output request is created immediately for a spool request.
4.
Output any list with immediate printing on the printer Remote##.
5.
Check your output.
Task 4: Front-End Printing Create an output device for front-end printing with the SAP GUI for Windows. 1.
In the SAP system, create a front-end printer Frontend## with the short name FR## that controls the default printer of a Microsoft Windows front-end PC.
2.
Send any list for immediate printing on the front end## printer, and check the output.
Task 5: Optional: Web Printing Create an output device for front-end printing with the SAP GUI for HTML.
440
1.
Create a copy of the output device front end## you created and name this device Web Print## with the short name WP##. Change the device type to PDF1.
2.
Log on to the SAP GUI for HTML with your course user -##.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Configuring Printers in AS ABAP
Solution 20: Configure Printers Task 1: Check the Print Environment First check the print environment of your SAP system. 1.
How many spool work processes are set up for the application server to which you are currently logged on? a)
2.
Call transaction SM50, and count the number of work processes of type SPO.
How many spool work processes are configured in your entire SAP system? a)
This information is provided by transaction SM66. If you do not see any work processes at first, check the status wait under Select process. Hint: The number of spool work processes cannot be changed by operation mode switches.
3.
How many spool servers are available in your SAP system? a)
4.
A (real) spool server is an SAP application server with at least one spool work process. You can display this information with transaction SM51 more easily than with transaction SM66: All application servers that provide the service Spool are spool servers.
As the default setting for your SAP user, change the settings so that an output request is not created immediately for a spool request. a)
To do this, choose System → User Profile → Own Data (transaction SU3) and the Defaults tab there. Ensure that Output Immediately is not checked and save your changes, if necessary. Hint: This default setting can be overridden with the direct setting when printing at any time.
5.
Which printers are defined at operating system level of your server? Where do they print? a)
Choose Start → Devices and Printers at the operating system level of your server. There should be printers (such as Printer1 for the group working on the DEV system, and Printer2 for the group working on the QAS system) that each print to a file. Continued on next page
2012
© 2011 SAP AG. All rights reserved.
441
Unit 10: Output Management
6.
TADM12_1
(If possible) Which printers are defined at operating system level of your front-end PC in the training room? Where do they print to? a)
If possible, choose Start → Devices and Printers on your front-end PC.
Task 2: Local Printing Create an output device with a local host spool access method. 1.
In your SAP system, create a local printer Local## with the short name LO## (where ## denotes your group number) that controls one of the previously defined printers. a)
In the SAP system, choose SAP menu → Tools → CCMS → Print → Spool Administration (transaction SPAD).
b)
On the Devices/servers tab, choose the Display pushbutton besides Output Devices (leave the field to the left empty).
c)
If you cannot see a Create pushbutton, choose Change to switch to change mode. Now create the printer Local## with the following specifications: • • •
Output Device: Local## Short name: LO## Device Attributes tab: Device Type: Should match the previously determined printer (HPLJ4) – Spool Server: Any spool server from your system (use F4 help) – Location: Any text Access Method tab: –
•
– –
Host Spool Access Method: C for Windows Host Printer: Name of the previously determined printer (Printer1 or Printer2)
Accept the default values for the other values and save.
Continued on next page
442
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Configuring Printers in AS ABAP
2.
Output any list (Suggestion: All profile parameters that begin with “rspo”) without immediate printing on the printer Local##. a)
To create the proposed list, call transaction RSPFPAR. Enter the parameter rspo* and choose Execute again. Select the pushbutton to print. Choose Local## as the output device (select it using the F4 help). Choose Continue without making any additional entries.
3.
Check your output. a)
4.
Call transaction SP01. Choose Execute, and view your spool requests.
Optional: Display the generated print data. Instead of checking at operating system level, you can view the file from the SAP system using transaction AL11 (SAP directory DIR_C_TEMP). a)
Both solutions are described here: •
•
At operating system level, you can use Notepad for example (Start → Run and then enter notepad) to view the file C:\temp\Print1.txt/C:\temp\Print2.txt. Note that Notepad cannot display all printer-specific control characters. In the SAP system, call transaction AL11 and double-click the entry DIR_C_TEMP at the end of the list. Double click the file name (Print1.txt or Print2.txt) displays the file contents.
Task 3: Remote Printing Install SAPSprint, and create an output device with a remote host spool access method. 1.
Install and start SAPSprint on your server.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
443
Unit 10: Output Management
TADM12_1
Caution: This exercise section should only be performed once for each host: Decide whether the DEV group or OAS group should perform this exercise. a)
On your server, navigate to the directory S:\ADM100_72\SAPSprint.
b)
Start the most recent installation program listed (naming convention xSPrint_.exe).
c)
Run through the installation (and be sure to check SAP Print Service for installation). Retain the default values for all other prompts.
d)
Optional: You can use the Windows Service Manager to verify that a SAPSprint has been created and started as a Windows service.
Continued on next page
444
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Configuring Printers in AS ABAP
2.
In the SAP system, create a remote printer Remote## with the short name RE## that controls a printer on a remote server. Note: These exercise sections should be performed by both groups again. a)
In the SAP system, choose Tools → CCMS → Print → Spool Administration (transaction SPAD).
b)
On the Devices/servers tab, choose the Display pushbutton besides Output Devices (leave the field to the left empty).
c)
If you cannot see a Create pushbutton, choose Change to switch to change mode. Now create the printer Remote## with the following specifications: • • •
Output Device: Remote## Short name: RE## Device Attributes tab:
•
Device Type: Should match the previously determined printer (HPLJ4) – Spool Server: Any spool server from your system (use F4 help) – Location: Any text Host Spool Access Method tab: –
– – –
Access Method: S for the SAP printing protocol Host Printer: Name of the previously determined printer (Printer1 or Printer2) Destination Host: twdf****.wdf.sap.corp (where twdf**** should be replaced with the host on which SAPSprint was installed)
Accept the default values for the other values and save. 3.
As the default setting for your SAP user, change the settings so that an output request is created immediately for a spool request. a)
To do this, choose System → User Profile → Own Data (transaction SU3), and choose the tab Defaults. Ensure that output immediately is checked and save your changes. Hint: This default setting can be overridden with the direct setting when printing at any time. Continued on next page
2012
© 2011 SAP AG. All rights reserved.
445
Unit 10: Output Management
4.
Output any list with immediate printing on the printer Remote##. a)
5.
TADM12_1
Follow the same procedure as for local printing. For a list, you could output the list of work processes in transaction SM50, for example.
Check your output. a)
With the settings in Step 3, the print time Output Immediately is now the default value. The user can make this (and other) settings in the print dialog box by choosing Properties. Hint: By choosing Show selected print parameters on initial screen in the Properties window, you can maintain some parameters directly on the print dialog box in future.
b)
Call transaction SP01. Choose Execute, and view the spool requests and the corresponding output requests.
Continued on next page
446
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Configuring Printers in AS ABAP
Task 4: Front-End Printing Create an output device for front-end printing with the SAP GUI for Windows. 1.
In the SAP system, create a front-end printer Frontend## with the short name FR## that controls the default printer of a Microsoft Windows front-end PC. a)
In the SAP system, choose Tools → CCMS → Print → Spool Administration (transaction SPAD).
b)
On the Devices/servers tab, choose the Display pushbutton besides Output Devices (leave the field to the left empty).
c)
If you cannot find the Create pushbutton, choose Change to switch to change mode. Now create the printer Frontend## with the following specifications: • • •
Output Device: Frontend## Short name: FR## Device Attributes tab:
•
– Device Type: SWIN – Location: here Host Spool Access Method tab: – –
Access Method: G Host Printer: _ _DEFAULT (without spaces between the two underscores)
Accept the default values for the other values and save. 2.
Send any list for immediate printing on the front end## printer, and check the output. a)
The procedure is the same as for the previous task.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
447
Unit 10: Output Management
TADM12_1
Task 5: Optional: Web Printing Create an output device for front-end printing with the SAP GUI for HTML. 1.
2.
Create a copy of the output device front end## you created and name this device Web Print## with the short name WP##. Change the device type to PDF1. a)
In the SAP system, choose Tools → CCMS → Print → Spool Administration (transaction SPAD).
b)
On the Devices/servers tab, choose the Display pushbutton besides Output Devices (leave the field to the left empty).
c)
If you cannot find the Create pushbutton, choose Change to switch to change mode.
d)
Select the line for the output device front end##, and choose the pushbutton Create with Template.
e)
Enter Web Print## as the name of the new output device. Change the short name to WP##. In the Device Attributes tab, change the field Device Type to PDF1. Save the output device without further changes.
Log on to the SAP GUI for HTML with your course user -##. a)
Either start the transaction SICF (in SAP GUI for Windows). Enter the value webgui in the search field under Service Name, and choose Execute (F8). Select the service /sap/bc/gui/sap/its/webgui with the right mouse button, and choose Test service. Or enter the following URL in your web browser: http://twdfSSSS.wdf.sap.corp:/sap/bc/gui/sap/its/webgui. You can determine the ICM HTTP port (of the ICM of the instance to which you are currently connected) in transaction SMICM – the standard value is 80$$, where $$ denotes the instance number.
b)
Log on to the SAP GUI for HTML with your course user -##.
c)
Send any list to the output device Web Print## for immediate printing. Hint: You can view the print dialog box in Menu → System → List → Print. Wait a few seconds until the generated PDF document is displayed in a new browser window.
448
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Configuring Printers in AS ABAP
Lesson Summary You should now be able to: • Describe the architecture and data flow of output processing in ABAP-based SAP systems • Create printers and spool servers in the SAP system • List important access methods • Manage spool requests
Related Information •
•
SAP NetWeaver 7.02 online documentation, path SAP NetWeaver → SAP NetWeaver by Key Capability → Solution Life Cycle Management by Key Capability → System Management → SAP Printing Guide (BC-CCM-PRN) SAP Notes 118057: Flexible Configuration of the Spool Service 19706:Tuning the Spooler 128105:Frontend printing (collective note) 150533:Printing in Windows Terminal Server (WTS) 1130927: SAP Printer Vendor Program 1100779: Participants in the SAP Printer Vendor Program 1097990: List of Printer Vendor Wizard Notes
•
2012
1036961: Device type selection wizard in transaction SPAD SAP Developer Network, Quick Link /irj/sdn/printing
© 2011 SAP AG. All rights reserved.
449
Unit 10: Output Management
TADM12_1
Lesson: Concept of Logical Spool Servers Lesson Overview In this lesson, you will learn about the concept of logical spool servers, and how to set them up.
Lesson Objectives After completing this lesson, you will be able to: • •
Describe the concept of logical spool servers Set up logical spool servers
Business Example Concept of Logical Spool Servers The printing concept introduced up to now envisages a fixed assignment of an output device to a spool server. A spool server, on the other hand, can be assigned multiple output devices, which raises the risk of this server becoming overloaded. It would therefore be desirable to have a mechanisms for load balancing across multiple servers. It is also advisable to set up groups of spool servers to ensure reliability. Both aspects are considered in this introduction to logical spool servers. Include logical spool servers from the outset when planning your printer landscape. When scaling your SAP system later (additional instances with spool work processes), logical spool servers make it easier to adapt the printer landscape.
450
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Concept of Logical Spool Servers
Figure 175: Spool Server
A (real) spool server is an SAP application server with at least one spool work process. Every output request is processed on a “real” spool server of this type. An output device created in the SAP system can be assigned a spool server directly. However, there are many advantages associated with an additional logical layer between the output device and the spool server. You can use logical (spool) servers for this purpose. These stand for a hierarchy of other logical servers and/or “real” spool servers. You can classify output devices and spool servers, for example, for test printing or production printing. The SAP system checks the classifications when saving, and displays a warning message if there are deviations. For example, the system warns you if you attempt to assign a high volume printer to a production print server.
Creating a Logical Spool Server You can maintain the spool server in transaction SPAD by choosing Spool Servers on the Devices / Servers tab page. Important information for a spool server: Server Name Name of the spool server, maximum of 20 characters (case-sensitive). The field below is intended for a short description.
2012
© 2011 SAP AG. All rights reserved.
451
Unit 10: Output Management
TADM12_1
Server Class Classify the spool server here (for example, for mass printing). Logical Server Select this field when you create a logical server. Mapping Name of a real or logical server to which this logical server refers. Additional information is presented below.
Figure 176: Creating a Logical Server
If you expect a significant workload due to front-end printing, you should configure at least one additional spool work process for each front-end printing spool server for other tasks. As already mentioned, you can classify output devices and spool servers. To classify an output device, select it (in transaction SPAD under Output Devices) and choose the menu path Edit → Classification.
452
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Concept of Logical Spool Servers
Advantages of Logical Spool Servers Safeguarding Against Failure When creating a spool server (either a logical server or a spool server), you can specify an alternative server. If the normal server is not available, the SAP system attempts to use this alternative.
Figure 177: Specifying Alternatives
You must ensure that all printers that may be used by a different spool server can be controlled in the same way by every spool server. For example, if the output device Test 1 in the above example points at operating system level to a printer P42 that is controlled locally, an operating system printer P42 must be available on servers twdf5000 and twdf5001. You cannot define more than two spool servers for a logical server. Since a logical server can itself reference logical servers, extensive spool server hierarchies are also possible.
2012
© 2011 SAP AG. All rights reserved.
453
Unit 10: Output Management
TADM12_1
Load Balancing You can allow load balancing for every spool server with an alternative server (to do this, select the field Allow Load Balancing). The load of a spool server is calculated from the number of spool work processes, output requests, and printed pages.
Figure 178: Load Balancing
For an output request for a spool server with load balancing (the setting can be made for logical servers and spool servers), the system determines the server with the smallest load. The algorithm is recursive: The same selection criteria are used on the mapping and the alternative server (both could be logical servers themselves). Sequential request processing (property of an output device) has priority over the load balancing shown here (property of a spool server). This means that output requests for an output device with sequential request processing would not be distributed in accordance with the current load, although assigned to a spool server with load balancing.
Transporting the Print Landscape The concept of logical servers supports you when defining a consistent, transportable print landscape. Unlike real spool servers, logical servers can have the same name in various SAP systems. In this way, you can define a consistent SAP print architecture
454
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Concept of Logical Spool Servers
in the development system and then transport it to other systems. After the transport, all you need to do is adjust the mapping of the logical servers to the spool servers of the new system.
Figure 179: Transporting the Print Landscape
There are functions for the manual transport of output devices and spool servers in transaction SPAD.
2012
© 2011 SAP AG. All rights reserved.
455
Unit 10: Output Management
456
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Concept of Logical Spool Servers
Exercise 21: Logical Spool Servers Exercise Objectives After completing this exercise, you will be able to: • Set up logical spool servers and assign output devices.
Business Example You want to set up logical spool servers in your ABAP-based SAP system to ensure load balancing and reliability.
Task: Create a Logical Spool Server
2012
1.
Create a logical server Logical##. If possible, enter two different spool servers as mapping and alternative servers and activate load balancing. Classify Logical## as a test server.
2.
Change the output device Local## so that the logical server Logical## is used as the spool server in future. Classify Local## as a test printer.
3.
Send any list to the printer Local## for immediate printing (suggestion: all profile parameters that begin with rspo).
4.
Check your output. Which real spool server was used?
© 2011 SAP AG. All rights reserved.
457
Unit 10: Output Management
TADM12_1
Solution 21: Logical Spool Servers Task: Create a Logical Spool Server 1.
Create a logical server Logical##. If possible, enter two different spool servers as mapping and alternative servers and activate load balancing. Classify Logical## as a test server. a)
In the SAP system, choose Tools → CCMS → Print → Spool Administration (transaction SPAD).
b)
On the Devices/servers tab page, choose Spool Servers (leave the field to the left empty).
c)
If you cannot see a Create pushbutton, choose Change to switch to change mode. Now create a logical server Logical##. Choose Logical server and enter at least one spool server under Mapping (use the F4 help). Enter the other details as described in the exercise and choose save.
2.
Change the output device Local## so that the logical server Logical## is used as the spool server in future. Classify Local## as a test printer. a)
From transaction SPAD, choose the Output Devices pushbutton on the Devices / Servers tab page. By double-clicking Local##, you can edit your printer (switch to change mode if necessary). On the Device Attributes tab page, enter the logical spool server Logical## as the spool server. To classify the output device, choose Edit → Classification → Test Print. Save your entries.
Continued on next page
458
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Concept of Logical Spool Servers
3.
Send any list to the printer Local## for immediate printing (suggestion: all profile parameters that begin with rspo). a)
Settings from previous exercises may mean that Output Immediately is proposed as the time of printing. The user can make this (and other) settings in the print dialog box by choosing Properties. Hint: By choosing Show selected print parameters on initial screen on the Properties window, you can maintain some parameters directly on the print dialog box in future. To create the proposed list, call transaction RSPFPAR. Enter the parameter rspo* and choose Execute again. To print, choose the appropriate pushbutton. Alternatively, you can choose System → List → Print. Choose Local## as the output device (select it using the F4 help). Choose Continue without making any additional entries.
4.
Check your output. Which real spool server was used? a)
2012
This time, an output request is created immediately. Transaction SP01 displays its status. For the spool server, select your output request (not the spool request) and choose Choose Detail. The server name is at the bottom of the list.
© 2011 SAP AG. All rights reserved.
459
Unit 10: Output Management
TADM12_1
Lesson Summary You should now be able to: • Describe the concept of logical spool servers • Set up logical spool servers
Related Information •
•
460
SAP NetWeaver 7.02 online documentation, path SAP NetWeaver → SAP NetWeaver by Key Capability → Solution Life Cycle Management by Key Capability → System Management → SAP Printing Guide (BC-CCM-PRN) → Spool Server SAP Note 118057: Flexible Configuration of the Spool Service
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Managing Spool Requests
Lesson: Managing Spool Requests Lesson Overview In this lesson, you will learn about managing spool and output requests.
Lesson Objectives After completing this lesson, you will be able to: •
Manage spool and output requests
Business Example As a spool administrator, you maintain the spool and output requests in your SAP system.
Managing Spool and Output Requests To maintain spool and output requests, call the Output Controller (transaction SP01 or choose System → Services → Output Controller). If you only want to check the status of your own spool requests, choose System → Own Spool Requests (transaction SP02). Transaction SP01 provides many selection criteria for selecting particular spool or output requests. The Further selection criteria... function is simple to use and allows each user to define their own selection criteria.
2012
© 2011 SAP AG. All rights reserved.
461
Unit 10: Output Management
TADM12_1
Figure 180: Selecting Spool or Output Requests
It is even possible to monitor spool and output requests on other SAP systems. To do this, enter a valid RFC connection in the System Name field. If this field remains empty, all systems are addressed that were selected for remote monitoring using transaction RZ20 (table ALCONSEG).
462
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Managing Spool Requests
Figure 181: Monitoring Spool and Output Requests
The displayed list shows all spool or output requests that match your selection criteria. The list is created using the SAP List Viewer (ALV). This allows you to change the appearance of the list as you desire. This means that you can show and hide columns, sort columns, or create variants. The following indicators specify the status of a spool request: Not yet sent to the operating system (no output request exists). + Spool request is still being created (stored in spool system). Waiting The output request has not yet been processed by the spool system. Proc. A spool work process is formatting the output request for printing. Print. The output request is printed by the operating system spooler. If the query at the host spooler is not activated, this status is shown for around a minute.
2012
© 2011 SAP AG. All rights reserved.
463
Unit 10: Output Management
TADM12_1
Compl. The output request has been printed. If the query at the host spooler is not activated, the status changes to Compl. as soon as the output request is transferred to the host spooler. There are (at least two) output requests with various statuses. Problem Indicates an error not of a serious nature (such as incomplete character set). This request was still printed. Error Indicates a serious error (such as a network error). Time A particular time was specified for the output of the request by the request creator. If you double click the status of a spool request, the system displays the associated output requests. To view the output requests of multiple spool requests, select these and choose Output Requests (or choose F5). For every unsuccessful output request, a log is written that you can use for error analysis.
Figure 182: Maintaining the Spool Database
464
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Managing Spool Requests
The system administrator is responsible for regularly deleting old spool requests and monitoring the consistency of the spool database. To delete old spool requests, schedule the ABAP program RSPO1041 with an appropriate variant as a periodic job. For more information about the RSPO1041 program, see SAP Note 130978. To check the consistency of the spool database, schedule the ABAP program RSPO1043 with an appropriate variant as a daily job. For more information about the RSPO1043 program, see SAP Note 98065. You can also start spool administration tools (in the dialog) in transaction SPAD in the Admin. tab page. However, the functions provided in transaction SPAD for deleting spool requests and running consistency checks are limited compared to the other programs available. For information about the reorganization of TemSe and spool, see also SAP Note 48400.
Appendix: Other Print Scenarios Here is an overview of other print scenarios:
Figure 183: Appendix: Other Print Scenarios
2012
© 2011 SAP AG. All rights reserved.
465
Unit 10: Output Management
TADM12_1
External Output Management Systems (OMS) can be addressed from the SAP system using a defined interface (BC-XOM) (access method E). This method is of particular interest if you have a very large volume, or the output of multiple systems (SAP systems and others) is to be centrally controlled and monitored. As of SAP Basis Release 4.0B (with a specific kernel and Support Package status), you can send print output by e-mail to a user (access method M). The e-mail is sent using SAPconnect. For more information, see SAP Notes 311037 and 513352. A user can also be connected to an SAP system from a web browser using SAP GUI for HTML. This type of connection can be set up in the SAP system with the integrated ITS as of AS ABAP 6.40. What options does this user have for print output? One option is the previously described output by e-mail. Web printing on the other hand does not require an e-mail client. You can use web printing as of SAP Basis Release 4.6B. To do this, the system administrator must set up a printer with device type PDF1 and the access method G. If the user selects this printer, a PDF document appears in a new browser window. The user can then print this PDF document locally. SAP Note 351230 describes the exact prerequisites and contains additional information about Web printing.
466
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Managing Spool Requests
Exercise 22: Managing Spool Requests Exercise Objectives After completing this exercise, you will be able to: • Manage spool and output requests
Business Example You want to delete unwanted spool requests from TemSe.
Task: Deleting spool requests Evaluate and delete spool requests.
2012
1.
Display all the spool requests you have created today.
2.
Run the report RSPO1041 (in the dialog) to delete all of your spool requests with successful output requests.
© 2011 SAP AG. All rights reserved.
467
Unit 10: Output Management
TADM12_1
Solution 22: Managing Spool Requests Task: Deleting spool requests Evaluate and delete spool requests. 1.
Display all the spool requests you have created today. a)
Choose System → Services → Output Control (transaction SP01).
b)
Restrict the output to your spool requests from today (this is the default selection (restricted to the current client)).
c)
Choose Execute (F8). Hint: To view the output requests for a spool request: • •
2.
Double click the Status field, or Select a spool request, and press F5.
Run the report RSPO1041 (in the dialog) to delete all of your spool requests with successful output requests. a)
Call transaction SA38.
b)
In the Program field, enter RSPO1041, and choose Execute (F8).
c)
Uncheck the fields Without output request, In processing, and Incorrect. In the Completed section, only check the Completed field, and in the older than ... days field, enter 0. Further down, in the Creator field, enter your course user -##, and choose Execute (F8).
d)
You can see which spool requests were deleted in the log. Note: In practice, you will schedule the RSPO1041 report as a periodic background job with an appropriate variant.
468
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Managing Spool Requests
Lesson Summary You should now be able to: • Manage spool and output requests
Related Information •
•
SAP NetWeaver 7.02 online documentation, path SAP NetWeaver → SAP NetWeaver by Key Capability → Solution Life Cycle Management by Key Capability → System Management → SAP Printing Guide (BC-CCM-PRN) → Maintaining the Spool Database SAP Notes: 130978: RSPO1041 - Deleting old spool requests 98065: Spool Consistency Check with RSPO1043 as of 4.0A 48400: Reorganization of TemSe and Spool 48284:System can no longer create spool requests 311037:Printing via e-mail 771683:Front-end printing for SAP GUI for HTML (as of Release 6.40)
2012
© 2011 SAP AG. All rights reserved.
469
Unit 10: Output Management
TADM12_1
Lesson: Printing Assistant for Landscapes (PAL) Lesson Overview In this lesson, you will learn about the Printing Assistant for Landscapes (PAL). After learning the concepts and terms, you will learn about administrative tasks in transaction PAL.
Lesson Objectives After completing this lesson, you will be able to: • • •
Name the prerequisites for using the Printing Assistant for Landscapes (PAL) Explain the terms in the PAL environment Set up and use a PAL landscape
Business Example Your company uses several ABAP-based SAP systems, each with several output devices. To keep administration tasks to a minimum in the event of changes, you want to use the Printing Assistant for Landscapes.
Prerequisites for Using PAL You can use the Printing Assistant for Landscapes to simplify the administration of output devices in ABAP-based SAP systems. To do this, output devices are maintained in one system (normally the central system), and their definition is then distributed across any number of additional systems (target systems) over RFC. SAP recommends using PAL if at least one of the following criteria applies: • • •
You manage several output devices in a few SAP systems. You manage a few output devices in several SAP systems. You manage several output devices in several SAP systems.
The following diagram is based on a small PAL landscape, and shows the release requirements of the systems involved:
470
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Printing Assistant for Landscapes (PAL)
Figure 184: PAL Landscape
The central system must be based on an AS ABAP 7.00 (or higher) with an up-to-date patch level. Since SAP Solution Manager also allows you to manage other functions centrally, SAP Solution Manager 7.0 suggests itself as the central system for PAL. The target systems must have a minimum release level of AS ABAP 6.20 with certain Support Package levels. Hint: See SAP Note 964501 for the precise system requirements. PAL currently supports the following access methods: • • • • •
L and C: Local printing U and S: Remote printing F and G: Front-end printing M: E-mail based printing E: External output management systems
Restrictions exist for some of these access methods: See the SAP online documentation for SAP NetWeaver 7.0 Enhancement Package 2 (or higher) for details.
Setting Up and Using PAL Before introducing the configuration steps, some terms need to be explained first:
2012
© 2011 SAP AG. All rights reserved.
471
Unit 10: Output Management
TADM12_1
Figure 185: PAL Terminology
(PAL) Printer The first step in the Printing Assistant for Landscapes is to create an output device (using transaction SPAD). This output device must then be designated as a PAL printer (often simply referred to as a “printer” below). Printer Group A printer group normally comprises several printers that are jointly distributed later. Target System A target system in a PAL environment refers to an RFC connection (maintained in the central system). This RFC connection contains connection and log on data for a suitable ABAP-based SAP system in the PAL landscape. Target System Group Printer groups are always distributed in a target system group, which usually consists of several target systems. The following diagram shows the steps for defining and using a PAL printer landscape:
472
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Printing Assistant for Landscapes (PAL)
Figure 186: Roadmap for PAL
The following sections explain the individual steps in more detail.
Maintaining a PAL System Landscape Printer definitions are distributed from the central system to the target systems across RFC. You therefore need an RFC connection in your central system to each target system. SAP recommends setting up a dedicated system user for spool administration in every target system. This user has authorization to the following authorization objects
2012
Authorization Object
Values
S_TCODE
SPAD, PAL
S_ADMI_FCD
SP01, SPOR, SPAA, SPAB, SPAC, SPAD
© 2011 SAP AG. All rights reserved.
473
Unit 10: Output Management
TADM12_1
To ensure a target system is recognized by PAL, it must be created with transaction PAL (to start it in the central system). Printers are then always distributed using target system groups that define a logical collection of target systems. A target system group could consist of all production systems for example. Note: A target system cannot belong to multiple target system groups. Key steps of the initial set up: 1. 2. 3. 4.
Create an RFC connection in the central system for each target system. Call transaction PAL in the central system. Under Show, choose the option Target System, and choose Create. Select a PAL target system name and the corresponding RFC destination. Under Show, choose the option Target System Group, and choose Create. Select a PAL target system group name. You can define the target systems you want to include now or later.
Create and Distribute PAL Printers PAL allows you to manage and distribute Printers (“PAL printers”) that you defined in the central system or a target system as a output device earlier (in transaction SPAD). You can then subsume these PAL printers in printer groups. A printer group could incorporate all test printers for example. You can then distribute printer groups across target system groups. Note: A PAL printer cannot belong to multiple printer groups. Key steps during set up: 1. 2.
3. 4. 5.
Call transaction PAL in the central system. Under Show, choose the option Printers, and choose Create. The Wizard will ask you whether you want to specify output devices from the central system or a target system as a printer. Under Show, choose the option Printer Group, and choose Create. Select a PAL printer group name. You can define the printers you want to include now or later. In the view Printer Group, select a printer group, and choose Distribute. Select one (or several) target system group(s). After you have distributed the printer group, check the Distribution Status.
PAL printers in the target system can only be displayed in transaction SPAD, not changed.
474
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Printing Assistant for Landscapes (PAL)
When a printer is distributed to a target system for the first time, an arbitrary (physical) spool server is assigned to the output device. Using the report SPCPC_SPOO_SERV_MASS_CHANGE in the target system, you can assign a (logical or physical) spool server to some or all PAL printers. The only mandatory input field is New Spool Server. The checkbox Confirm before change is selected as a default. If you use the default setting, a list of affected PAL Printers will be displayed. You can check first if the new spool servers are correct before you execute the report. It is also possible to schedule the distribution as a background job (via report SPCPC_DIST_PRG_TO_TSG). See SAP Note 1476793 for the (minimum system requirements).
Deleting PAL Objects You can also delete objects from the PAL landscape. There are some points to consider. To delete an (existing) printer, proceed as follows: 1. 2. 3.
4. 5.
Call transaction PAL in the central system. Delete the relevant printer from the printer group. Call the distribution status: changes that have not yet been distributed are displayed. Distribute the relevant printer group across the listed target system group(s). The deleted printer no longer appears in transaction SPAD for the target systems. Delete the (PAL) printer. If required, delete the output device using transaction SPAD in the central system.
To delete a target system, proceed as follows: 1. 2. 3.
4. 5. 6.
2012
Call transaction PAL in the central system. Delete the required target system from the target system group. Call the distribution status: changes that have not yet been distributed are displayed. Distribute the relevant printer group across the listed target system group(s). Delete the target system. If required, delete the RFC destination using transaction SM59 in the central system. If required, delete the relevant system user using transaction SU01 in the target system.
© 2011 SAP AG. All rights reserved.
475
Unit 10: Output Management
476
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Printing Assistant for Landscapes (PAL)
Exercise 23: Central Administration of Output Devices (PAL) Exercise Objectives After completing this exercise, you will be able to: • Set up a PAL system landscape • Distribute the definition of output devices
Business Example Your company uses several ABAP-based SAP systems, each with several output devices. To keep administration tasks to a minimum in the event of changes, you want to use the Printing Assistant for Landscapes (PAL). Caution: The DEV and QAS groups must work together on this exercise. The DEV system will assume the role of the central system, and the QAS system (on the same server) will assume the role of a target system. The following steps should therefore be completed together. The aim of the exercise is to distribute the output devices created in the DEV system to the QAS system so that they can be used there.
Task 1: PAL System Landscape Checking the prerequisites and defining the PAL landscape. 1.
Verify that in the central system (the DEV system) there is an RFC connection of the type __ defined to the target system (the QAS system), for example QAS_100_RFC. This RFC connection should provide the logon credentials of a (dialog or system) user with spool administration rights. Hint: If you have not yet created an RFC connection of the type __, you can use the prepared RFC connection PARTNER instead.
2.
In the DEV system, configure the QAS system as a PAL target system.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
477
Unit 10: Output Management
3.
TADM12_1
In the DEV system, create a target system group TestSystems, and add the QAS system to this group.
Result You have created a target system group TestSystems, and assigned the QAS system to it. In practice, you would manage multiple target system groups and/or define more systems for each target system group.
Task 2: Distribute Local Printer Defining a local printer as the PAL printer, and distributing it. Note: This section assumes that a local printer Local## has been created in the DEV system. 1.
Define the local printer Local## as a PAL printer in the DEV system.
2.
In the DEV system, create a printer group TestPrinters, and add the printer Local##. Then distribute the printer group TestPrinters to the system group TestSystems.
3.
In the target system, check whether the output device Local## is recognized.
Result You have successfully distributed a local printer using PAL.
Task 3: Distribute Remote Printer Defining a remote printer as the PAL printer, and distributing it. Note: This section assumes that a remote printer Remote## has been created in the DEV system. 1.
Define the remote printer Remote## as a PAL printer in the DEV system.
2.
Add the PAL printer Remote## to the printer group TestPrinters that you created earlier. Then distribute the printer group TestPrinters to the system group TestSystems.
3.
In the target system, check whether the output device Remote## is recognized.
Result You have successfully distributed a remote printer using PAL. Continued on next page
478
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Printing Assistant for Landscapes (PAL)
Task 4: Distribution via Report Performing a change and distribution via report 1.
Perform a change to the output device Local## (e.g. the Location on tab Device Attributes.
2.
Using report SPCPC_DIST_PRG_TO_TSG, perform a distribution of printer group TestPrinters to system group TestSystems.
3.
In the target system, check whether the change of output device Local## is recognized.
Result You have performed a distribution of a printer group to a system group via a report. Note that you could schedule SPCPC_DIST_PRG_TO_TSG as a periodical background job.
Task 5: Optional: Mass Change of Spool Server(s) Changing the spool servers of all distributed PAL printers. Note: This section assumes that a logical spool server Logical## has been created in the QAS system. 1.
Using report SPCPC_SPOO_SERV_MASS_CHANGE, assing the logical spool server Logical## to all PAL printers in the target system QAS.
2.
Check the spool server of all PAL printers in the target system QAS.
Result You have adjusted the spool server of the distributed PAL printers.
2012
© 2011 SAP AG. All rights reserved.
479
Unit 10: Output Management
TADM12_1
Solution 23: Central Administration of Output Devices (PAL) Task 1: PAL System Landscape Checking the prerequisites and defining the PAL landscape. 1.
Verify that in the central system (the DEV system) there is an RFC connection of the type __ defined to the target system (the QAS system), for example QAS_100_RFC. This RFC connection should provide the logon credentials of a (dialog or system) user with spool administration rights. Hint: If you have not yet created an RFC connection of the type __, you can use the prepared RFC connection PARTNER instead.
2.
a)
In the DEV system, start transaction SM59.
b)
Under ABAP Connections (Type 3), you should see the RFC connection of the type __ (or PARTNER) that corresponds to the QAS system, and which contains a user with the profile SAP_ALL in the target system.
In the DEV system, configure the QAS system as a PAL target system. a)
In the DEV system, start transaction PAL.
b)
Under Show, choose the option Target System, and press Create.
c)
Populate the Create Target System window as follows: Field
Input
Target System Name
QAS
Description
Any
RFC destination
use F4 help to select __ (for example QAS_100_RFC) or PARTNER
Then use the Check pushbutton to verify that the target system can be accessed. Then press OK. Continued on next page
480
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Printing Assistant for Landscapes (PAL)
3.
In the DEV system, create a target system group TestSystems, and add the QAS system to this group. a)
You have opened transaction PAL in the DEV system.
b)
Under Show, choose the option Target System Group, and press Create.
c)
Populate the Create Target System Group window as follows: Field
Input
Target System Group Name
TestSystems
Description
Any
Select the line for the target system QAS, and press OK.
Result You have created a target system group TestSystems, and assigned the QAS system to it. In practice, you would manage multiple target system groups and/or define more systems for each target system group.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
481
Unit 10: Output Management
TADM12_1
Task 2: Distribute Local Printer Defining a local printer as the PAL printer, and distributing it. Note: This section assumes that a local printer Local## has been created in the DEV system. 1.
Define the local printer Local## as a PAL printer in the DEV system. a)
You have opened transaction PAL in the DEV system.
b)
Under Show, choose the option Printer, and press Create.
c)
In the window Select - Source of Output Devices, select the option Central System, and choose Next.
d)
In the window Select - Output Devices in Central System, select the device Local##, and choose Next.
e)
Confirm the prompt (with information about the access method) asking you if you want to continue with Yes. Note: An error message “Lock failed. Foreign lock.” indicates that the selected output device is currently processed in change mode. To release the lock, leave transaction SPAD (or switch to the Display mode).
f)
The printer assistant issues a log detailing the (hopefully successful) creation of the PAL printer, which you can Close.
Continued on next page
482
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Printing Assistant for Landscapes (PAL)
2.
In the DEV system, create a printer group TestPrinters, and add the printer Local##. Then distribute the printer group TestPrinters to the system group TestSystems. a)
You have opened transaction PAL in the DEV system.
b)
Under Show, choose the option Printer Group, and press Create.
c)
Populate the Create Printer Group window as follows: Field
Input
Printer Group Name
TestPrinters
Description
Any
Select the line for the PAL printer Local##, and press OK.
3.
d)
In transaction PAL, select the printer group TestPrinters, and choose Distribute.
e)
If the system displays a prompt on the access method of the selected printer(s), confirm it by pressing OK.
f)
In the window Select - PAL Target System Group, select the target system group TestSystems you just created, and choose Next.
g)
View the result of the Device Type Check in Target System – if this was successful, choose Next.
h)
The printer assistant issues a log about the distribution, which you can Close now.
In the target system, check whether the output device Local## is recognized. a)
In the QAS system, start transaction SPAD.
b)
Make sure that the definition of the output device Local## is correctly recognized in the QAS system. Note • • •
that you can not change the definition in the target system. the description “Centrally-Administered Device”. the spool server of the device.
Result You have successfully distributed a local printer using PAL. Continued on next page
2012
© 2011 SAP AG. All rights reserved.
483
Unit 10: Output Management
TADM12_1
Task 3: Distribute Remote Printer Defining a remote printer as the PAL printer, and distributing it. Note: This section assumes that a remote printer Remote## has been created in the DEV system. 1.
Define the remote printer Remote## as a PAL printer in the DEV system. a)
You have opened transaction PAL in the DEV system.
b)
Under Show, choose the option Printer, and press Create.
c)
In the window Select - Source of Output Devices, select the option Central System, and choose Next.
d)
In the window Select - Output Devices in Central System, select the device Remote##, and choose Next.
e)
Confirm the prompt asking you if you want to proceed with Yes.
f)
The printer assistant issues a log detailing the creation of the PAL printer, which you can Close now.
Continued on next page
484
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Printing Assistant for Landscapes (PAL)
2.
3.
Add the PAL printer Remote## to the printer group TestPrinters that you created earlier. Then distribute the printer group TestPrinters to the system group TestSystems. a)
You have opened transaction PAL in the DEV system.
b)
Under Show, choose the option Printer Group, and select the line TestPrinters.
c)
In the section shown below, switch to the Members tab. Choose the Add pushbutton. Select the line for the printer Remote##, and choose OK.
d)
In transaction PAL, select the printer group TestPrinters, and choose Distribute.
e)
If the system displays a prompt on the access method of the selected printer(s), confirm it by pressing OK.
f)
In the window Select - PAL Target System Group, select the target system group TestSystems, and choose Next.
g)
View the result of the Device Type Check in Target System – if this was successful, choose Next.
h)
Confirm the system message about the distribution of the printer group(s) with Yes.
i)
The printer assistant issues a log about the distribution, which you can Close now.
In the target system, check whether the output device Remote## is recognized. a)
In the QAS system, start transaction SPAD.
b)
Make sure that the definition of the output device Remote## is correctly recognized in the QAS system. Note • • •
that you can not change the definition in the target system. the description “Centrally-Administered Device”. the spool server of the device.
Result You have successfully distributed a remote printer using PAL.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
485
Unit 10: Output Management
TADM12_1
Task 4: Distribution via Report Performing a change and distribution via report 1.
2.
3.
Perform a change to the output device Local## (e.g. the Location on tab Device Attributes. a)
In the central system (DEV), start transaction SPAD.
b)
On the Devices/servers tab, choose the Display pushbutton besides Output Devices (leave the field to the left empty).
c)
Double click the entry Local##.
d)
If you cannot see a Change pushbutton, choose Change to switch to change mode.
e)
On the Device Attributes tab, enter or change the Location.
f)
Press save (and note the popup).
g)
Ensure that you do not hold any locks anymore, e.g. by leaving transaction SPAD.
Using report SPCPC_DIST_PRG_TO_TSG, perform a distribution of printer group TestPrinters to system group TestSystems. a)
In the central system (DEV), start transaction SA38.
b)
As Program, enter SPCPC_DIST_PRG_TO_TSG and press Execute (or the F8 key).
c)
As Printer Group, select TestPrinters. As Target System Groups, select TestSystems. When done, press Execute (or the F8 key).
In the target system, check whether the change of output device Local## is recognized. a)
In the QAS system, start transaction SPAD.
b)
Verify that the output device Local## comes with the changed property.
Result You have performed a distribution of a printer group to a system group via a report. Note that you could schedule SPCPC_DIST_PRG_TO_TSG as a periodical background job.
Continued on next page
486
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Printing Assistant for Landscapes (PAL)
Task 5: Optional: Mass Change of Spool Server(s) Changing the spool servers of all distributed PAL printers. Note: This section assumes that a logical spool server Logical## has been created in the QAS system. 1.
2.
Using report SPCPC_SPOO_SERV_MASS_CHANGE, assing the logical spool server Logical## to all PAL printers in the target system QAS. a)
You are logged on to the QAS system.
b)
Start transaction SA38.
c)
Enter Program SPCPC_SPOO_SERV_MASS_CHANGE (you may enter spcpc* and use the F4 help), and press Execute (F8).
d)
For New Spool Server, choose Logical## (you may use the F4 help).
e)
Keep all other fields with their default value, and press Execute (F8).
f)
Check the window Confirm Spool Server Change, and press Change Spool Server. A log with detailed information regarding the spool server change is displayed.
Check the spool server of all PAL printers in the target system QAS. a)
You are logged on to the QAS system.
b)
Start transaction SPAD.
c)
On the tab Devices / severs, press Display besides Output Devices (without any search pattern).
d)
In the overview of output devices, note the column Spool servers. For the output devices created by PAL, you should see the value Logical##.
Result You have adjusted the spool server of the distributed PAL printers.
2012
© 2011 SAP AG. All rights reserved.
487
Unit 10: Output Management
TADM12_1
Lesson Summary You should now be able to: • Name the prerequisites for using the Printing Assistant for Landscapes (PAL) • Explain the terms in the PAL environment • Set up and use a PAL landscape
Related Information •
• • • •
488
SAP NetWeaver 7.02 online documentation, path SAP NetWeaver → SAP NetWeaver by Key Capability → Solution Life Cycle Management by Key Capability → System Management → SAP Printing Guide (BC-CCM-PRN) → Printing Assistant for Landscapes (PAL) SAP Developer Network, Quick Link /irj/sdn/printing. SAP Note 964501: Printing Assistant for Landscape (PAL) SAP Note 1240633: PAL: Transferring the spool server SAP Note 1476793: PAL Printer Distribution in Background
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Unit Summary
Unit Summary You should now be able to: • Describe the architecture and data flow of output processing in ABAP-based SAP systems • Create printers and spool servers in the SAP system • List important access methods • Manage spool requests • Describe the concept of logical spool servers • Set up logical spool servers • Manage spool and output requests • Name the prerequisites for using the Printing Assistant for Landscapes (PAL) • Explain the terms in the PAL environment • Set up and use a PAL landscape
2012
© 2011 SAP AG. All rights reserved.
489
Unit Summary
490
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Test Your Knowledge
Test Your Knowledge 1.
Which of the following access methods exist in the SAP system? Choose the correct answer(s).
□ □ □ □ 2.
A B C D
Remote printing Front-end printing Instance printing Local printing
Which of the listed states can a spool request have? Choose the correct answer(s).
□ □ □ □ □ □
2012
A B C D E F
Compl. Canceled Error Waiting Active Print.
© 2011 SAP AG. All rights reserved.
491
Test Your Knowledge
TADM12_1
Answers 1.
Which of the following access methods exist in the SAP system? Answer: A, B, D Instance printing does not exist.
2.
Which of the listed states can a spool request have? Answer: A, C, D, F The incorrect options canceled and active are possible status messages from job monitoring. Other possible statuses of a spool request are -, +, Proc., , Problem, and Time.
492
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
493
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
494
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit 11 Scheduling Background Tasks Unit Overview This unit deals with the basics of background processing, and the scheduling and monitoring of jobs. You also learn about special functions and extension options of background processing.
Unit Objectives After completing this unit, you will be able to: • • • • • • • • • •
Describe the uses of background processing Schedule and monitor jobs Schedule time-dependent jobs Schedule standard jobs Schedule event-dependent jobs Define and trigger events Use additional, special functions of background processing Explain how to use SAP Central Process Scheduling by Redwood Name the most important features of SAP CPS Use the Work Center Job Management to schedule and monitor background jobs
Unit Contents Lesson: Fundamentals of Background Processing ............................ 497 Exercise 24: Fundamentals of Background Processing................... 507 Lesson: Time-Based Scheduling of Jobs ........................................ 510 Exercise 25: Time-Based Jobs ............................................... 515 Lesson: Event-Based Scheduling of Jobs ....................................... 522 Exercise 26: Event-Dependent Jobs......................................... 527 Lesson: Background Processing: Further Topics .............................. 531 Exercise 27: (Optional) Other Topics in the Area of Background Processing....................................................................... 541
2012
© 2011 SAP AG. All rights reserved.
495
Unit 11: Scheduling Background Tasks
TADM12_1
Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood ............................................................................. 547 Exercise 28: Job Scheduling with SAP CPS................................ 557 Lesson: Appendix: Job Management ............................................ 563
496
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Fundamentals of Background Processing
Lesson: Fundamentals of Background Processing Lesson Overview In this lesson, you will learn about the basics of background processing.
Lesson Objectives After completing this lesson, you will be able to: • •
Describe the uses of background processing Schedule and monitor jobs
Business Example Reports that are to run on a regular basis and long-running programs are scheduled as jobs in the SAP system. The administrator schedules jobs and monitors the system's background processing to ensure that it is running correctly.
Basics The following questions are answered in the course of this lesson: • • • • • •
Why do you need background processing? What is a job? What can be performed in the background? What start criteria are there? How are jobs scheduled and monitored? What status can a job have?
Dialog work processes should be able to respond to end users' requests quickly. Dialog resources should therefore not be burdened with long-running programs. This can lead to bottlenecks in the dialog response time. The system profile parameter rdisp/max_wprun_time exists for this reason. It limits the maximum runtime of a dialog step within a dialog work process. This should ensure that dialog work processes are not blocked by long-running programs, interfering with online operation. After the maximum runtime has elapsed, the program is terminated. Note: The way in which the parameter rdisp/max_wprun_time works is described in detail in SAP Note 25528.
2012
© 2011 SAP AG. All rights reserved.
497
Unit 11: Scheduling Background Tasks
TADM12_1
Figure 187: Why Background Processing?
You can use the background work processes for long-running tasks. These are sometimes also called batch work processes. Normally, background processing is used not only for long-running, but also for recurrent tasks. Examples of this type of task are the daily database backup or the month-end work for financial accounting.
498
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Fundamentals of Background Processing
Figure 188: What Is a Job?
A job comprises one or more steps (known as job steps). A step can be: • • •
An ABAP program An external command An external program
Every job is processed without interruption by one single background work process. Background jobs can be scheduled with different priorities: • • •
2012
Class A (highest priority) Class B (medium priority) Class C (normal priority)
© 2011 SAP AG. All rights reserved.
499
Unit 11: Scheduling Background Tasks
TADM12_1
If a job should be executed on a particular server or server group, it is handled preferentially compared to other jobs with the same class. This preference only applies if multiple jobs of various priorities request background processing at the same time, for example, because they are scheduled for the same time. Hint: You should ensure that a large share of all background tasks are normally scheduled as class C without target server specification. This share can include 90% (or more) of all tasks. System background tasks are also executed in this way, such as the tasks that you schedule with transaction DB13.
Figure 189: What Can Be Performed in the Background?
500
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Fundamentals of Background Processing
A step within a job can call one of three actions: •
•
•
Every ABAP program can be scheduled as a step of a job. If the ABAP program has one or more selection screens, you must create the input required there in advance in the form of a variant. A variant makes it possible to run an ABAP program in the background although the program requires input. The values stored in the variant are then used during the execution of the program. If an ABAP program has a screen output as its result, this is directed to a spool list. You can specify an (e-mail) recipient for this spool list when defining the job. This recipient then receives the job output by e-mail after the job has been executed. You must also specify a printer for the creation of spool lists even though, as a result of background processing, there is not necessarily any direct output to a printer (this depends on the printer's access method). This may have to be explicitly started later. An external command is a call of a predefined script, a command, or a program at operating system level. With external commands, you can mask operating system calls and store them in the SAP system under a name. You can also use the SAP authorization concept to protect the execution of an external command. This enables you to determine which users are allowed to execute which external commands (on which target hosts and/or operating systems). An external program is any operating system command. The SAP authorization concept only specifies whether a user can call external programs or not. A more detailed authorization assignment, for example at the level of program names, is not provided; use external commands for this.
Figure 190: Start Criteria for a Job
2012
© 2011 SAP AG. All rights reserved.
501
Unit 11: Scheduling Background Tasks
TADM12_1
A job can be triggered: •
•
By scheduling it on a particular date at a particular time (this includes the start time “immediately”, if there are no free background work processes available when the job is scheduled). By the occurrence of a particular event defined in the SAP system (this includes jobs that are to start after other jobs or at operation mode changes, or jobs with immediate start if there are free background work processes available when the job is scheduled).
Scheduling and Monitoring Use transaction SM36 to define new jobs. You can also call the Job Wizard (transaction SM36WIZ) from transaction SM36.
Figure 191: Job Scheduling
Required specifications when defining a job are: • • •
General specifications such as job name, job priority (Default: C) and (optionally) target server (group) Definition of one or more job steps Definition of start conditions (time-dependent or event-dependent)
The Job Wizard supports you when defining jobs, by guiding you easily through the creation process.
502
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Fundamentals of Background Processing
The way in which a job is created (“classic” or using the Job Wizard) has no bearing on the result. Some functions (specifying an SAP user for each step, swapping steps) are not available with the Job Wizard, however. Use transaction SM37 to monitor jobs. You can select jobs using a diverse range of criteria on the initial screen of this transaction. In this way, you can display all jobs that contain a particular job step, that have a particular status, or that react to a defined event (for this, you must select a particular event or “*”).
Figure 192: Job Monitoring
2012
© 2011 SAP AG. All rights reserved.
503
Unit 11: Scheduling Background Tasks
TADM12_1
After you have chosen Execute, a job overview appears that is realized by the SAP List Viewer (ALV). By choosing Settings from the menu you can determine the columns that are displayed and the sort order, amongst other things. You can set this layout as the standard layout (for the current user or for all users). Hint: The transaction SM37 offers the following two ALV-based display types: • •
LIST: offers a quick list structure (standard setting) GRID: enables you to change the layout easily (required for accessibility)
Using the program BTC_SWITCH_LIST_GRID, a batch administrator can determine the display type for individual users or all users. You can navigate to other job-specific views from the job overview shown above: • • •
The spool list contains the output lists for ABAP programs (if they exist). The job details contain, among other information, the job definition, duration of the processing of the job, and the start time of the job. All messages output by a background program are stored in the job log. You can display this log to obtain information about a program that terminated with errors or to perform a detailed investigation about a background processing run.
Figure 193: Status of a Job
504
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Fundamentals of Background Processing
A job can have the following statuses: Scheduled The steps that make up the job have already been defined, however the start condition still needs defining. Released The job has been completely defined, including its start condition. A job cannot be released without a start condition. Only an administrator or a user with the relevant authorizations for background processing can release a job. This ensures that unauthorized users cannot execute jobs without approval. Ready The start condition of a released job has been fulfilled. A job scheduler has placed the job in the wait queue for a free background work process. Active The job is currently being executed and cannot be deleted or changed. If an active job does not seem to be running correctly (for example, it is running for an unusually long time), you can terminate it in a background work process in debugging mode, analyze it, and then either release it again or terminate it completely. To do this, call transaction SM37 and choose Job → Capture: active job. Hint: To capture a job, you must be logged on to the instance on which the job is running. Finished All steps of this job were successfully completed. Canceled The job aborted. This can happen in two ways: • •
An administrator deliberately terminates the job in transaction SM37 by choosing Job → Cancel active job. A job step is terminated with an error.
You can still change a job as long as the job still has the status Scheduled or Released. If the execution of the job has already begun, you can monitor the processing in the job log. If the job contains ABAP programs that create output lists, these are stored in spool lists. You can create a new job by copying an existing job. From the menu, choose Job → Copy.
2012
© 2011 SAP AG. All rights reserved.
505
Unit 11: Scheduling Background Tasks
506
© 2011 SAP AG. All rights reserved.
TADM12_1
2012
TADM12_1
Lesson: Fundamentals of Background Processing
Exercise 24: Fundamentals of Background Processing Exercise Objectives After completing this exercise, you will be able to: • Determine the configuration of your SAP system with regard to background processing.
Business Example Reports that are to run on a regular basis and long-running programs are scheduled as jobs in the SAP system. The administrator schedules jobs and monitors the system's background processing to ensure that it is running correctly.
Task: Checking the Configuration Check the way that background processing is configured in your SAP system. The following steps will make you familiar with the SAP system settings that are relevant for background processing.
2012
1.
How many background processes are currently configured in your SAP system?
2.
What determines the number of available background work processes?
3.
How many jobs can be processed simultaneously?
4.
Assume that all background work processes in your system are currently processing and there are, therefore, no free resources for other jobs. Can you set up additional background work processes without restarting the SAP system?
© 2011 SAP AG. All rights reserved.
507
Unit 11: Scheduling Background Tasks
TADM12_1
Solution 24: Fundamentals of Background Processing Task: Checking the Configuration Check the way that background processing is configured in your SAP system. The following steps will make you familiar with the SAP system settings that are relevant for background processing. 1.
How many background processes are currently configured in your SAP system? a)
Start transaction SM66.
b)
Choose the Select Process pushbutton to make the following selections: • •
Type: Background only Status: choose Wait in addition
Choose Continue and count the number of work processes displayed. 2.
What determines the number of available background work processes? a)
The parameter rdisp/wp_no_btc initially specifies the number of available background work processes on the current instance. You can check the value of the parameter with transaction RZ11 or the report RSPFPAR. If you have defined operation modes (transaction RZ04), this value can be overwritten. In this case, use the CCMS Control Panel (transaction RZ03) to specify the current operation mode.
3.
How many jobs can be processed simultaneously? a)
4.
Assume that all background work processes in your system are currently processing and there are, therefore, no free resources for other jobs. Can you set up additional background work processes without restarting the SAP system? a)
508
The SAP system process as many jobs concurrently as there are background work processes available.
Using the concept of operation modes, you can define an operation mode with additional background work processes in transaction RZ04. You can then perform a manual operation mode switch using transaction RZ03. You do not need to restart your system when doing this.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Fundamentals of Background Processing
Lesson Summary You should now be able to: • Describe the uses of background processing • Schedule and monitor jobs
Related Information SAP Notes: 25528 - Parameter rdisp/max_wprun_time 519059 - FAQ: Background Processing System
2012
© 2011 SAP AG. All rights reserved.
509
Unit 11: Scheduling Background Tasks
TADM12_1
Lesson: Time-Based Scheduling of Jobs Lesson Overview In this lesson, you will learn about time-based scheduling of jobs.
Lesson Objectives After completing this lesson, you will be able to: • •
Schedule time-dependent jobs Schedule standard jobs
Business Example The administrator schedules jobs and monitors the system's background processing to ensure that it is running correctly.
Time-Based Scheduling
Figure 194: Time-Dependent Start of a Job
510
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Time-Based Scheduling of Jobs
A job can be started in a time- or event-dependent manner. In the case of a time-dependent start of a job, you can choose between the following options: • • •
The job should be executed immediately The job should be executed at a particular date/time The job should be executed on a particular work day
You can choose to make all time-based start conditions for jobs recurrent. This means that the job is executed again after a defined period of time has elapsed. You can specify exceptions (such as postponement to the following work day in the case of holidays in the factory calendar). The job is started at the specified date and time, in accordance with the job priority and availability of background work processes. You can also specify a time period during which the job should be executed. To do this, you specify a time after which the job should no longer be executed. With this function, you prevent periodic jobs being executed at an undesirable time, among other things. For example, a reorganization job that should only be executed at night is delayed. With a start time window, you can avoid this job being executed during the day, when the dialog users are active and there are fewer system resources available.
Load Balancing The profile parameter rdisp/bctime specifies the time period in which the time-dependent job scheduler is active (see the next figure). Executing jobs with the start condition immediate usually avoids the time-dependent scheduler. In this case, the dialog work process of the scheduling user performs the job scheduling. Only if no free resources are found, is the job concerned scheduled in a time-based way. The scheduled start time then corresponds to the time point at which it should have started.
2012
© 2011 SAP AG. All rights reserved.
511
Unit 11: Scheduling Background Tasks
TADM12_1
Figure 195: Scheduling Jobs and Load Balancing
Background work processes can be configured on every instance of the SAP system using the profile parameter rdisp/wp_no_btc. The number of background work processes required in the SAP system depends on the number of tasks to be performed in the background. If the transport system is used, there must be at least two background work processes in the system. The combination of job ID and job name define the job uniquely in the system. On every SAP instance on which background work processes are defined, the time-dependent job scheduler runs every rdisp/btctime seconds (default value: 60 seconds). This is an ABAP program (SAPMSSY2 - an auto ABAP) that runs automatically in a dialog work process. Hint: Since SAP NetWeaver 7.0, the job scheduler also starts after a job has finished. This increases the throughput for background processing considerably (depending on how many jobs there are). SAP Note 923228 describes how you can activate this for SAP systems with Basis release 4.6C and above.
512
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Time-Based Scheduling of Jobs
The time-dependent job scheduler checks the job scheduling table in the database for jobs that are waiting for processing. These jobs are transferred to free background work processes in the SAP instance, in accordance with their priority and execution target. •
•
Jobs that are not assigned any particular execution target can be executed with any free background work process. This means that the workload is automatically distributed between the SAP instances. If a job is explicitly assigned an execution target (such as a selected instance or a group of instances), the special properties of the execution target can be used (for example, you can ensure that a job is performed on a particular operating system, or that the job is executed by a background work process that is running on the same host as the database). This means, however, that you do not have the advantages of automatic load balancing.
Standard Jobs Standard jobs are background jobs that should run regularly in a production SAP system. These jobs mainly perform certain clean up tasks in the system, such as the deletion of obsolete spool requests.
Figure 196: Scheduling Standard Jobs
2012
© 2011 SAP AG. All rights reserved.
513
Unit 11: Scheduling Background Tasks
TADM12_1
In the job definition transaction (SM36), you can access a selection of important standard jobs that you can schedule, monitor, and edit by choosing Standard Jobs (see figure). •
• •
If you want to schedule all standard jobs, choose Default Scheduling. All standard jobs that are defined in table REORGJOBS are scheduled with the specified variant and period. If other jobs exist that execute one of the programs of the standard jobs, the system informs you of this. To schedule individual jobs, choose the selected job with the input help and specify an execution period. To define an additional standard job that is not yet available in the selection (table REORGJOBS), choose Predefine new job. Note: For information about standard jobs, see also SAP Note 16083:Standard jobs, reorganization jobs , SAP Note 1034532: Changes for standard jobs, SAP Note 1610282: Problems when scheduling standard jobs and SAP Note 1411877: New standard jobs.
514
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Time-Based Scheduling of Jobs
Exercise 25: Time-Based Jobs Exercise Objectives After completing this exercise, you will be able to: • Schedule and monitor time-dependent jobs
Business Example The administrator schedules jobs and monitors the system's background processing to ensure that it is running correctly.
Task 1: Check Profile Parameter Check the setting for the time-dependent Job Scheduler. 1.
What is the time interval for the time-dependent Job Scheduler in your system?
Result You now know every how many seconds the time-dependent Job Scheduler is started.
Task 2: Optional: Variants Create a variant for an ABAP program. 1.
Create a variant DISP_## for the program RSPFPAR (## stands for your group number) which only issues parameters for the ABAP dispatcher.
Result You have created a variant for an ABAP program.
Task 3: Schedule Jobs Use various tools to create jobs. 1.
(Optional) Use transaction SA38 to run the report RSPFPAR in the background (start time: Execute immediately). For the Variant, select the name DISPATCHER or (if you have carried out the previous task) DISP_##.
2.
(Optional) Use transaction SM36WIZ to create a job with the following properties: Continued on next page
2012
© 2011 SAP AG. All rights reserved.
515
Unit 11: Scheduling Background Tasks
3.
TADM12_1
Job Name
TIME-WIZ-##, ## = group number.
Job Class
C
Target Server
Leave empty
1. step
Program RSUSR000
Start Condition
Immediate
Period
Hourly
Use the transaction SM36 (without the wizard) to create a job with the following characteristics: Job Name
TIME-##, ## = group number.
Job Class
C
Target Server
Leave empty
1. step
Program RSPFPAR with variant DISPATCHER or DISP_##
Start Condition
Period
Daily
Hint: Bear in mind that the system time (System → Status) is the determining factor for jobs.
Result You can schedule time-dependent jobs with different tools.
Task 4: Monitor Jobs Use the job overview to monitor jobs.
516
1.
Display all your jobs for today.
2.
Find out details for the job RSPFPAR such as the priority, client, job ID, user who scheduled and released the job, and the work process that executed the job.
3.
Take a look at the spool list for the job TIME-WIZ-##.
4.
Determine whether the job TIME-## was delayed, and if so, the length of the delay.
5.
In SM37, why do you see the next job TIME-WIZ-##, but not the next job TIME-##?
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Time-Based Scheduling of Jobs
Solution 25: Time-Based Jobs Task 1: Check Profile Parameter Check the setting for the time-dependent Job Scheduler. 1.
What is the time interval for the time-dependent Job Scheduler in your system? a)
Determine the value of the profile parameter rdisp/btctime (with either the transaction RZ11 or the report RSPFPAR).
Result You now know every how many seconds the time-dependent Job Scheduler is started.
Task 2: Optional: Variants Create a variant for an ABAP program. 1.
Create a variant DISP_## for the program RSPFPAR (## stands for your group number) which only issues parameters for the ABAP dispatcher. a)
Start the transaction SA38 and enter RSPFPAR as the Program. Choose Execute.
b)
Under Profile Parameters, enter rdisp/* and choose Save as Variant ( ).
c)
Under Variant Name enter DISP_##, and under Meaning enter any text.
d)
Leave the other fields unchanged and Save the new variant.
Result You have created a variant for an ABAP program.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
517
Unit 11: Scheduling Background Tasks
TADM12_1
Task 3: Schedule Jobs Use various tools to create jobs. 1.
2.
3.
(Optional) Use transaction SA38 to run the report RSPFPAR in the background (start time: Execute immediately). For the Variant, select the name DISPATCHER or (if you have carried out the previous task) DISP_##. a)
Start the transaction SA38 and enter RSPFPAR as the Program.
b)
Choose Background.
c)
Select the variant DISPATCHER or DISP_## (using the F4 help).
d)
Choose Execute Immed. Use the Job Overview pushbutton to go to the transaction SM37, where you can display the results of your job (Execute pushbutton).
(Optional) Use transaction SM36WIZ to create a job with the following properties: Job Name
TIME-WIZ-##, ## = group number.
Job Class
C
Target Server
Leave empty
1. step
Program RSUSR000
Start Condition
Immediate
Period
Hourly
a)
Start the transaction SM36WIZ and choose Continue.
b)
Fill the screens as specified in the task. Use the F4 Help wherever possible. Where no values have been specified, use the default values.
c)
To finish, choose Complete.
Use the transaction SM36 (without the wizard) to create a job with the following characteristics: Job Name
TIME-##, ## = group number.
Job Class
C
Target Server
Leave empty
Continued on next page
518
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Time-Based Scheduling of Jobs
1. step
Program RSPFPAR with variant DISPATCHER or DISP_##
Start Condition
Period
Daily
Hint: Bear in mind that the system time (System → Status) is the determining factor for jobs. a)
Start transaction SM36.
b)
Under Job Name, enter TIME-## .
c)
Choose Step. Enter the specifications for the step that are listed in the task and choose Save. Then choose Back ( ).
d)
Choose Start Condition. Choose Date/Time and enter a time . Select the Periodic Job checkbox and under Period Values, select Daily. Then choose Save.
e)
Finally, on the initial screen of transaction SM36, choose Save once.
Result You can schedule time-dependent jobs with different tools.
Task 4: Monitor Jobs Use the job overview to monitor jobs. 1.
Display all your jobs for today. a)
2.
Start transaction SM37. Include scheduled jobs in the selection too. Then choose Execute.
Find out details for the job RSPFPAR such as the priority, client, job ID, user who scheduled and released the job, and the work process that executed the job. a)
In transaction SM37, double-click the job RSPFPAR.
b)
Choose Job Details to display a dialog box that contains all the information you require.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
519
Unit 11: Scheduling Background Tasks
3.
TADM12_1
Take a look at the spool list for the job TIME-WIZ-##. a)
In transaction SM37, select the job TIME-WIZ-##.
b)
Use the Spool pushbutton to go to the spool request that was generated.
c)
Select the spool request and choose Display Contents ( ). You should see a user overview similar to the output of transaction AL08. Spool lists are only created for job steps that contain ABAP programs with output. They are only printed immediately if you have made the corresponding setting in the printer settings during the definition of the job step or in your user defaults.
4.
Determine whether the job TIME-## was delayed, and if so, the length of the delay. a)
Depending on the setting, you will already see a column headed Delay in SM37. After you have selected the job TIME-##, you can choose Job Log to display the job's progress over time. Delays could be due to busy background work processes or the fact that the time-dependent Job Scheduler runs periodically.
5.
In SM37, why do you see the next job TIME-WIZ-##, but not the next job TIME-##? a)
520
With the default values, the job monitor SM37 displays today's jobs. If you adjust the selection accordingly, the next job TIME-## (released for the following day) is displayed too.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Time-Based Scheduling of Jobs
Lesson Summary You should now be able to: • Schedule time-dependent jobs • Schedule standard jobs
Related Information SAP Notes: • • •
2012
16083 - Standard jobs, reorganization jobs 923228 - Background job sched.: using processes that have become free 1034532 - Changes for standard jobs
© 2011 SAP AG. All rights reserved.
521
Unit 11: Scheduling Background Tasks
TADM12_1
Lesson: Event-Based Scheduling of Jobs Lesson Overview In this lesson, you learn about event-based scheduling of jobs.
Lesson Objectives After completing this lesson, you will be able to: • •
Schedule event-dependent jobs Define and trigger events
Business Example The administrator schedules background jobs and monitors the correct process of the system's background processing.
Event-Based Scheduling An event is a signal to the background processing system that a particular status has been achieved in the SAP system. The background processing system receives events and then starts all jobs that are linked to this event.
522
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Event-Based Scheduling of Jobs
Figure 197: Event-Dependent Start of a Job
Hint: In older releases, the parameter rdisp/btcname was very significant for event-dependent scheduling. Since the following kernel patches: Basis Release 640: patch 220 Basis Release 700: patch 147 this parameter is no longer evaluated (the parameter value is usually empty). For more information, see SAP Notes 1038669 and 104574 . Event-dependent jobs can be scheduled with one of the following three start conditions: After event The job starts after a defined event is received by the SAP system. At operation mode With this option, you can link a job to the activation of an operation mode when scheduling the job. After job In this way, you can create simple job chains where the execution of the successor job can be made dependent on the status of the predecessor job.
2012
© 2011 SAP AG. All rights reserved.
523
Unit 11: Scheduling Background Tasks
TADM12_1
Events New events are defined by the system administrator in CCMS (transaction SM64). When doing so, the administrator differentiates between system events and user events. System events are events predefined by SAP that you should not or cannot modify or trigger.
Figure 198: Definition and Triggering of Events
Events can be triggered in various ways: • •
•
Manually in CCMS for test purposes (transaction SM64) With the ABAP program BTC_EVENT_RAISE or within an ABAP program (by using the function module BP_EVENT_RAISE or the RAISE method for the CL_BATCH_EVENT class) Outside the SAP system at operating system level using the program sapevt.
A parameter can also be transferred when an event is triggered. In this way, you can define jobs that wait for the occurrence of the event together with the specified parameter. You can access a history of events by way of the Event History (transaction SM62). The syntax for the program sapevt is: sapevt are several single switches from the following: { | event=} [{-p } | param=system>_ProcessServer. Select it and choose Edit from the context menu. On the Parameters tab, click New and select SAP_EnableRfcServer. As a value, enter true. Save and close. Start the process server: Select the process server, and from the context menu choose start. As soon as the Process Server is running, a connection to the system is established. You can have a look in TA SM59, TCP/IP connections: cronacle-@SAP:-, created by user CPSCOMM.
Now you can start to run jobs with SAP CPS.
2012
© 2011 SAP AG. All rights reserved.
551
Unit 11: Scheduling Background Tasks
TADM12_1
Create and Schedule a Job You have several options to create jobs in SAP CPS: • • •
Start from the Submit Job button in the top level navigation and select a job definition (template) there or manually script a job Start from the navigation bar Definitions → Job Definitions, choose a job definition and select Submit from the context menu Create a job chain (with help of a graphical display) and choose Definitions → Job Chains
Figure 209: Create and Schedule a Job
You can observe the job in the job monitor under Monitoring → Jobs. From the detailed view of each job you can open the logs and output file, if applicable. You can even reschedule the job from the monitoring view, selecting Schedule → Resubmit from the context menu. For a complete overview of the functionality and features of SAP CPS refer to the Administration Guide you can open with a click on the info button in the top level navigation.
552
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood
Create and run Job Chains A job chain executes one or more job definitions (job definition jobs) in parallel or sequentially. The job definition jobs are grouped into steps. All jobs in a step are executed simultaneously (parallel processing). The process server waits until all jobs in a step get a final job status before proceeding with the next step (sequential processing). The main advantage over the core CCMS functionality is that steps can be skipped or restarted based on the final status of a step using Status Handlers. Job chains have two levels of status handlers, on the step level and on the job chain level: When no status handler is found on the step level, the status handler on the job chain level is used. When there is none on the job chain level either, then the default behavior is used. The default behavior is the following: • • •
When a step has reached status completed the following step is started or, when this is the final step, the chain status is set to completed. When a step has reached status error the job chain status is set to error. When a step has been canceled the job chain status is set to error.
Figure 210: Create a Job Chain with Step Status Handler
2012
© 2011 SAP AG. All rights reserved.
553
Unit 11: Scheduling Background Tasks
TADM12_1
Status handlers overrule the default and set the step or chain to a preselected status or take distinct actions if a certain status is reached. The following actions are available: • • • • • • •
Goto Step - to go to another step within the job chain Raise Error - To raise an error by returning the Return Code Mark Completed - To change the status of the step to completed (independent from the actual result) Restart Step - To restart the current step Restart Chain - To restart the chain Request Restart - Creates an Operator Message in case of an error and asks for a manual restart of the job chain Continue - To continue with the processing of the chain
Event based Scheduling In SAP CPS, jobs and job chains cannot only be triggered by entering a start time and a period. It is a lot more effective to start jobs based on their dependencies to other jobs, for example as soon as data has been transferred by a predecessor job. This can be done by events: • •
A Raise Event that is added to a job/job chain starts a new job/job chain under the status you have defined A Wait Event that is added to job/job chain makes this job waiting for the event to be raised (by the assigned job or manually)
Events allow the creation of complex dependencies, as they can be raised and cleared by completed jobs. As long as one or more events are not raised a job waiting on those events will not start. This guaranties that a job will not start unless all conditions are met for it to start.
554
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood
Figure 211: Create a Dependency between to job chains with an Event
If you want to work with events, you first have to create event definitions. 1. 2. 3. 4. 5. 6. 7.
Choose Definitions → Event Definitions from the navigation bar. From the context menu choose create and enter an event definition and a description. Save and close. Assign the event to job chains. You do this by editing the job chain. Edit the job chain and go to the tab Raise Event if you want to add an event that starts another job chain. Select the event from the dropdown list and select the status in which the event shall be raised. Save and close. Add the same event as a wait event to the job chain you want to make dependent from the first one. Submit the job chain with the wait event. The job now waits for the event to be raised.
Import Jobs from the ABAP System If you want to run and control background jobs you have previously submitted in your SAP system via transaction SM36 now by SAP CPS, you can use the function ImportCCMSJobs. You can import CCMS job steps as separate job definitions or
2012
© 2011 SAP AG. All rights reserved.
555
Unit 11: Scheduling Background Tasks
TADM12_1
just make the job chains use the SAP_AbapRun job definition; the latter keeps the number of job definitions in SAP CPS low and allows you have a better overview. The downside is that you cannot easily schedule a step on its own without filling in the parameters yourself or submitting the job chain with steps disabled. To import your CCMS jobs from an SAP System: 1. 2. 3.
Choose Definitions → Job Definitions and locate the job definition SAP_ImportCCMSjobs. From the context menu, choose Submit. Fill in the corresponding information in the tabs Parameters and Generation Settings. The following fields are mandatory on the Parameters tab: • • •
SAP System SAP Client SAP Job Name
The following fields are mandatory on the Generation Settings tab:
4. 5.
556
• Name for the generated job definition • Overwrite existing job definitions? • Application • Create a job definition for each step? • Add step numbers to SAP job names? • Retrieve joblog? • Retrieve spoollist? • Delete job when finished? Choose scheduling on the left-hand side and choose the queue belonging to the SAP System. Choose Submit.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood
Exercise 28: Job Scheduling with SAP CPS Exercise Objectives After completing this exercise, you will be able to: • Create an isolation group for your user and assign the SAP system. • Create and submit a job chain with Status Handler.
Business Example To use the basic version of SAP CPS you have to create an isolation group for each system you want to schedule jobs in. Hint: In this exercise you use your system as central job scheduling system to schedule a job in the system of your partner group. That means the DEV group is using their SAP CPS to schedule a job in System QAS and vice versa.
Task 1: Isolation Group and System Connection Create an isolation group in SAP CPS and assign your user and your system to it. 1.
Open the SAP CPS browser with the URL http://twdfxxxx.wdf.sap.corp:/scheduler, for example http://twdf9999.wdf.sap.corp:50000, and log on with your user -##. Create an isolation group and add your user to the isolation group.
2.
In the new isolation group create the SAP system entry for a remote system.
Result You successfully connected an SAP system to SAP CPS.
Task 2: Job Chain Create and submit a Job Chain with Status Handler
2012
1.
Create a Job Chain with name JobChain##.
2.
Assign a Step Status Handler to Step 1.
3.
Submit the Job Chain and monitor the processing of the Job Chain.
© 2011 SAP AG. All rights reserved.
557
Unit 11: Scheduling Background Tasks
TADM12_1
Solution 28: Job Scheduling with SAP CPS Task 1: Isolation Group and System Connection Create an isolation group in SAP CPS and assign your user and your system to it. 1.
2.
Open the SAP CPS browser with the URL http://twdfxxxx.wdf.sap.corp:/scheduler, for example http://twdf9999.wdf.sap.corp:50000, and log on with your user -##. Create an isolation group and add your user to the isolation group. a)
After logging on you may need to first create a license. To do this enter SAP AG as Company Name and choose Activate Free of Charge License.
b)
As you work with a basic version of SAP CPS, you have to create an isolation group (scheduling can only be set up and administered in one system per logon). In the navigation bar, select Security → Isolation Group. From the context menu, choose New. Create the isolation group _##, for example DEV_06. Save and close.
c)
Select the isolation group and choose Import Users from the context menu. Search for your user -## and import the user.
In the new isolation group create the SAP system entry for a remote system. a)
Log off from the scheduler and log on again. You are directed to the newly created isolation group. (If you create more than one isolation group, you can select the isolation group from a list of all groups your user is assigned to.)
b)
From the navigation bar, choose Environment → SAP Systems From the context menu, choose New. Make the following settings: • •
•
•
Name: ##_, for example QAS03_twdf9999. RFC Connect String: ASHOST= SYSNR= TRACE=0, for example ASHOST=twdf9999 SYSNR=10 TRACE=0 J2EE URL: http://:, for example http://twdf9999.wdf.sap.corp:51000 Default Job Time Zone: Europe/Berlin (enter eu and wait for the system to give a preselection) Continued on next page
558
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood
Test the connection. Switch to the XBP tab and click on New. Make the following settings: • • • • •
Client Number: 100 Username: Password: Mark the Enabled checkbox Mark the Default Client checkbox
Check the Connection Settings. Select Save and Close. Once the system is created, CPS automatically creates a process server for the system and a job queue. For the process server you have to enter additional parameters: From the navigation bar, select Environment → Process Servers A process server has been created with name _ProcessServer. Select it and choose Edit from the context menu. On the Parameters tab, click on New and select SAP_EnableRfcServer. As a value, enter true. Save and close.
Result You successfully connected an SAP system to SAP CPS.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
559
Unit 11: Scheduling Background Tasks
TADM12_1
Task 2: Job Chain Create and submit a Job Chain with Status Handler 1.
Create a Job Chain with name JobChain##. a)
From the navigation bar, choose Definitions → Job Chains. From the context menu choose New. In the new window click on the rectangle with the job chain symbol. This leads to a display of the job chain details. Enter the name for the job chain JobChain## and select the queue _Queue.
b)
Click on the rectangle and select Add Step from the context menu. Add a name, e.g. Step 1, and description for the step. Click on the step rectangle and select Add Job from the context menu. Click in the Job Definition field and select SAPAbapRun from the list. Make the following entries: • •
Scheduling - Queue: _Queue Input Parameters: – – – –
c)
SAP System - Expression: . SAP Client - Expression: 100 SAP Job Name - Expression: DEMOJOB##_1 ABAP Program - Expression: RSDEMO03
Click on the Job Chain rectangle and select Add Step from the context menu. Add a name, e.g. Step 2, and description for the second step. Click on the step rectangle and select Add Job from the context menu. Click in the Job Definition field and select SAP_AbapRun from the list. Make the following entries: • •
Scheduling - Queue: _Queue Input Parameters: – – – – –
SAP System - Expression: . SAP Client - Expression: 100 SAP Job Name - Expression: DEMOJOB##_2 ABAP Program - Expression: RSPFPAR ABAP Variant - Expression: SAP&SPOOL
Continued on next page
560
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Job Scheduling with SAP Central Process Scheduling by Redwood
2.
Assign a Step Status Handler to Step 1. a)
Go back to Step 1. Under Final Status Handlers open On Error and make the following entries: • •
Action: Go to Step Go to Step: Step 2
Save and Close. 3.
Submit the Job Chain and monitor the processing of the Job Chain. a)
In the Job Chain Definitions view, click on your new job chain and select Submit from the context menu. Leave the default settings and choose Submit. Open the Job Monitor and refresh the list. Now you see your job chain running.
Result Although one of the jobs in the job chain has failed, the whole job chain is processed and end with status Completed. The status handler allows for overwriting statuses on step level and sets rules how to proceed within the job chain if certain conditions are met.
2012
© 2011 SAP AG. All rights reserved.
561
Unit 11: Scheduling Background Tasks
TADM12_1
Lesson Summary You should now be able to: • Explain how to use SAP Central Process Scheduling by Redwood • Name the most important features of SAP CPS
562
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Appendix: Job Management
Lesson: Appendix: Job Management Lesson Overview This lesson gives you an overview of the Work Center Job Management.
Lesson Objectives After completing this lesson, you will be able to: •
Use the Work Center Job Management to schedule and monitor background jobs
Business Example You want to get a general survey about the jobs in your system landscape by using the work center Job Management.
Work Center: Job Management The work center Job Management is the central access to all functions for documenting, scheduling, and monitoring background jobs. It comprises views to display and edit job requests, job documentation, scheduled jobs, and job alerts. You can perform typical tasks in job scheduling. As a prerequisite to use this work center, a business partner is assigned to your system user.
2012
© 2011 SAP AG. All rights reserved.
563
Unit 11: Scheduling Background Tasks
TADM12_1
Figure 212: Work Center Job Management
The work center Job Management offers the following features; Overview information Overview information is available for the following views: • • • • •
Job requests Job Documentation Central process scheduling Job Scheduling Task Inbox
Job Requests Job Requests are listed. You see: • • •
All job requests you created All job requests you are assigned to as processor All Service Desk messages from Job Monitoring that the system reports in the context of Business Process Monitoring
Job Documentation
564
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Appendix: Job Management
You get a list of job documentation. You can define queries and set filters to select data. When you select job documentation from the list, the system displays details of the job documentation below the list, for example, further information about the steps. To reach job documentation, select the job documentation and choose Display. If authorized, you can edit job documentation. Job Monitoring • • •
Gives an overview about background jobs. Provides Job Analysis, Job Scheduling, Display of Job Logs, and the Job Documentation Overview SAP Central Process Scheduling by Redwood is integrated here as well.
Common Tasks The following functions could be performed from any view in the work center: • • • • • •
Create a Job Request for a new job Create Job Documentation Call a template Analyze jobs Scheduling Jobs Directly Importing Jobs into Job Documentation
Job Scheduling Management The Job Scheduling Management component enables you to do the following: • •
Central and complete job documentation Management of jobs using, for example, the following standardized workflow:
•
Scheduling of jobs (according to authorizations with or without release) centrally from the SAP Solution Manager system to connected SAP systems. You can import jobs from systems connected using SAP Solution Manager into job documentation. You can import jobs from job documentation into systems connected using SAP Solution Manager.
• • •
2012
You can monitor jobs and see in the analyses to which business processes and business process steps the job belongs.
© 2011 SAP AG. All rights reserved.
565
Unit 11: Scheduling Background Tasks
TADM12_1
Figure 213: Workflow for Managing Jobs
Note: Additional information about the Job Scheduling Management standard is available under http://service.sap.com/supportofferings SAP Support Offerings → Support Standards → Media Library → Job Scheduling Management .
566
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Appendix: Job Management
Lesson Summary You should now be able to: • Use the Work Center Job Management to schedule and monitor background jobs
Related Information •
SAP Education Course SM100 - SAP Solution Manager Operation and Configuration SAP Library for SAP Solution Manager 7.0 EHP1, SAP Solution Manager → Using the Work Center
2012
© 2011 SAP AG. All rights reserved.
567
Unit Summary
TADM12_1
Unit Summary You should now be able to: • Describe the uses of background processing • Schedule and monitor jobs • Schedule time-dependent jobs • Schedule standard jobs • Schedule event-dependent jobs • Define and trigger events • Use additional, special functions of background processing • Explain how to use SAP Central Process Scheduling by Redwood • Name the most important features of SAP CPS • Use the Work Center Job Management to schedule and monitor background jobs
568
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Test Your Knowledge
Test Your Knowledge 1.
. An ABAP program or an A job contains one or more command or program can be executed in such a can be triggered at a particular or when a defined
. A job occurs.
Fill in the blanks to complete the sentence.
2.
What status can a job have? Choose the correct answer(s).
□ □ □ □ □ □ 3.
A B C D E F
Running Released Waiting Finished Error Active
Which of the listed options for time-dependent scheduling of a job can be implemented with the standard resources of the SAP system? Choose the correct answer(s).
□ □ □ □ □ 4.
A B C D E
Daily at 1500 The second-last working day of every month Every nine days, but not on Sundays Only tomorrow at 2355 Every year on April 1 at 0800
Which of the listed options for event-dependent scheduling of a job can be implemented with the standard resources of the SAP system? Choose the correct answer(s).
□ □ □ □
2012
A B C D
Whenever the system switches to the Night operation mode After the job Job1 has run successfully Whenever a particular event has been triggered Whenever the periodic job Job2 has run successfully
© 2011 SAP AG. All rights reserved.
569
Test Your Knowledge
5.
TADM12_1
If one of the system's ten background work processes is reserved for class A jobs, and jobs are being processed in the other nine work processes, the reserved work process remains free even if a class A job is waiting for execution. Determine whether this statement is true or false.
□ □ 6.
True False
If a user has authorization to schedule an external program as a step of a background job, he or she can run any operating system command. Determine whether this statement is true or false.
□ □
570
True False
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Test Your Knowledge
Answers 1.
A job contains one or more steps. An ABAP program or an external command or program can be executed in such a step. A job can be triggered at a particular time or when a defined event occurs. Answer: steps, external, step, time, event After the job is triggered, it is processed without interruption by a single background work process.
2.
What status can a job have? Answer: B, D, F In addition to the three correct answers, a job could have the status Scheduled, Ready, or Canceled.
3.
Which of the listed options for time-dependent scheduling of a job can be implemented with the standard resources of the SAP system? Answer: A, B, C, D, E You can implement all the options mentioned with standard AS ABAP tools.
4.
Which of the listed options for event-dependent scheduling of a job can be implemented with the standard resources of the SAP system? Answer: A, B, C Option D cannot be implemented directly in the standard system. However, you can implement it as one of many additional possibilities (for example, by using function modules to enhance the standard).
5.
If one of the system's ten background work processes is reserved for class A jobs, and jobs are being processed in the other nine work processes, the reserved work process remains free even if a class A job is waiting for execution. Answer: False The work processes that are reserved for class A jobs process class A jobs. The option to reserve work processes for class A jobs should only prevent all work processes being occupied with class B or C jobs.
2012
© 2011 SAP AG. All rights reserved.
571
Test Your Knowledge
6.
TADM12_1
If a user has authorization to schedule an external program as a step of a background job, he or she can run any operating system command. Answer: True If you do not want, as an administrator, to assign this critical authorization, but want to enable your users to run a specific operating system command, you can define an external command in the SAP system.
572
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
573
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit Summary
574
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Unit 12 SAPconnect and SMTP Unit Overview The connection of external communication systems is important in many business processes. This unit discusses the connection of different communication systems, such as fax or mail servers, to SAP systems using SAPconnect. First, the functions of SAPconnect will be discussed. The SAP system will then be configured for sending and receiving e-mails in SMTP format.
Unit Objectives After completing this unit, you will be able to: • • • •
Outline the function of SAPconnect Create a node for sending a remote mail to a different SAP system List the steps required to connect the SAP system to a mail server Configure the SAP system for the connection to a mail server
Unit Contents Lesson: Communication with SAPconnect ...................................... 576 Procedure: Example: Creating a Node for Sending Remote Mail to a Partner System ................................................................. 582 Lesson: Communication Using SMTP ........................................... 586 Exercise 29: Sending and Receiving E-Mails by SMTP with AS ABAP. 597
2012
© 2011 SAP AG. All rights reserved.
575
Unit 12: SAPconnect and SMTP
TADM12_1
Lesson: Communication with SAPconnect Lesson Overview SAPconnect is a standard interface for external communication that enables data to be sent via telecommunication services, such as fax, text messages (pager / SMS), Internet e-mail, and X.400, as well as to printers and between different SAP systems. It allows you to connect external communication components to the SAP system. In this lesson, you will learn the fundamentals of SAPconnect.
Lesson Objectives After completing this lesson, you will be able to: • •
Outline the function of SAPconnect Create a node for sending a remote mail to a different SAP system
Business Example As a member of the system administration team, you want to enable the connection of SAP systems to external communication services.
Overview of the Message Flow in SAP Systems The SAP system offers application developers many ways in which messages can be created and processed. For example, there could be a need to automatically send a confirmation message to the sold-to party after the creation of a sales order.
576
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication with SAPconnect
Figure 214: Message Flow in the SAP System
Business Communication Services (BCS) are of central importance in message processing. As of SAP Web AS 6.10, these services allow application developers to integrate sending messages internally and externally in their applications without any great effort. In addition to controlling sending and receiving, BCS takes on extensive status handling and makes available all sending information about of an application object. Business Communication Services are the successor to the Business Communication Interface (BCI) and offer the advantage of an object-oriented interface. The sending of messages from SAP applications can be performed directly using BCS. Alternatively, the Post Processing Framework (PPF) can also be addressed first. The PPF provides a uniform interface for generating actions in response to certain conditions (such as printing delivery notes, faxing order confirmations, or triggering approval processes). The PPF is the successor to message control and provides a greater range of functions, simpler connection to the applications, and greater flexibility than its predecessor. BCS (and its predecessor, BCI) can also be used from the tool for forms, SAP Smart Forms (and its predecessor, SAPscript).
2012
© 2011 SAP AG. All rights reserved.
577
Unit 12: SAPconnect and SMTP
TADM12_1
In addition to automated message creation and processing, you can, of course, also create messages manually using the Business Workplace (previously known as SAP Office). The Business Workplace (transaction SBWP) provides a standard working environment in which every SAP user can perform his or her part of the business and communication processes in the company. BCS forwards external messages to SAPconnect.
What Can SAPconnect Do? SAPconnect is the central interface for external communication in SAP systems. SAPconnect supports the use of telecommunication services such as fax, text messages (pager / SMS), Internet e-mail, and X.400, as well as sending data to printers and between different SAP systems. SAPconnect allows you to connect external communication components to the SAP system. SAPconnect provides a direct connection to the Internet using the SMTP plug-in of the AS ABAP. The SMTP plug-in for Internet e-mail is available as of SAP Web AS 6.10. Communication possibilities with SAPconnect:
Figure 215: Communication Possibilities with SAPconnect
578
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication with SAPconnect
As you can see from the figure above, there are different ways of producing the same result (such as sending mail to the Internet). It has been possible to use external communication systems for many years; however, the use of plug-in technology requires the Internet Communication Manager (ICM) as well as at least SAP Web AS 6.10, and newer plug-ins may have even higher requirements (such as at least SAP Web AS 6.20).
SAPconnect: Transaction SCOT Use transaction SCOT to configure SAPconnect. You can set up communication types here (such as fax, Internet e-mail, and so on) by creating and configuring communication nodes. You can use various views of the communication infrastructure in transaction SCOT. You usually start with the view View → System status.
Figure 216: Transaction SCOT: The View of the System Status
To be able to send messages using a communication type, you must perform the following steps: 1. 2.
2012
You require at least one configured (communication) node for the communication type if you want to use it to send documents. All programs that may be required must be available and configured.
© 2011 SAP AG. All rights reserved.
579
Unit 12: SAPconnect and SMTP
TADM12_1
Basic Process of Communication Using SAPconnect The following list clarifies the process of a generic communication step in SAPconnect. 1. 2. 3.
A message is created, for example as a WebFlow item, in the Business Workplace (transaction SBWP) or by an application. The message is assigned to a node based on the selected communication type and address area stored in the queue. The send process (report RSCONN01 - should run periodically in the background) starts, reads the message from the queue, and transfers it to the SMTP plug-in or an RFC destination. Note: You can easily schedule the send process periodically in transaction SCOT, by choosing View → Jobs. Caution: SAPconnect must be set up client dependent. For example, the RML nodes that you use for communication between two SAP systems (via Remote Mail) use RFC connections that are valid system wide, but the nodes themselves are only known within a client. Note: External communication systems log onto the SAP system as a system user. The authorizations for this user are contained in the profile S_A.SCON. The SAPconnect administrator requires the authorizations for the system user and the authorizations for table maintenance, which are checked using the authorization object S_TABU_DIS. These authorizations are contained in the roles SAP_BC_SRV_COM_ADMIN and SAP_BC_SRV_GBT_ADMIN.
The figure below shows an example of a node configured for sending remote mail to an SAP system.
580
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication with SAPconnect
Figure 217: Setting up a Node for Remote Mail Sending
2012
© 2011 SAP AG. All rights reserved.
581
Unit 12: SAPconnect and SMTP
TADM12_1
Example: Creating a Node for Sending Remote Mail to a Partner System 1.
Start transaction SCOT.
2.
Choose View → System status.
3.
Choose Create (Ctrl+F5).
4.
Choose to create an RFC Node (with wizard)
5.
Enter a name for the node (for example, RML) and a description (for example, Remote mail to partner system).
6.
Specify the RFC connection PARTNER or another RFC connection that points to a client of another SAP system.
7.
Choose the address type R/3.
8.
Specify :100:* for the address type. = DEV or QAS (ID of your partner system).
9.
Leave the conversion rules and the screen for restricting the send time on the default settings.
10. Do not set any additional address types. 11. Keep the default settings for failed send attempts. 12. The node is to be monitored by the alert monitor (initially, you may have to restart the data collection method in transaction SCOT by choosing Utilities → Alert monitor → Start data collection method so that the node is displayed in the alert monitor). 13. Declare the node to be ready for use in use and check the Node supports: connection test, status, trace checkbox. Perform the test.
Result The Remote Mail to partner node is ready to use.
Continued on next page
582
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication with SAPconnect
Test this node by following the procedure below: 1. 2. 3.
4. 5.
Start transaction SBWP. Choose New Message. Enter a title and content for your mail, and specify the receiver as follows: system_name:client:user. The system name corresponds to the SID of your partner system (in the setup for the ADM102 course therefore QAS for the DEV groups and DEV for the QAS groups) and the client is the ID of the client in which the specified user exists, such as QAS:100:ADM102-30. Specify the recipient type as R (= remote mail address). Choose Send.... Start the send process for the address type RML in transaction SCOT. Check that the mail has been received in the partner system using transaction SBWP. Hint: To successfully send RML mails you require an RML address, which you have to maintain in transaction SU01 (choose Other Communication...).
Troubleshooting Various troubleshooting tools are available, some of which are mentioned as examples: •
• •
For outbound messages, you can use routing tests (Utilities → Routing test) to check whether the error during the node determination was caused by the recipient address. This test checks whether routing for outgoing messages runs correctly in the communication environment. The test provides information on how the appropriate node is determined using the specified recipient address and whether fax and paging numbers are converted according to the rules for recipient number adjustment. A trace can be activated for incoming and/or outgoing messages (Utilities → Trace settings). The messages that are sent can be evaluated according to their current status (Utilities → Overview of send orders). For example, all documents with transmission errors can be displayed and resent. This report can be used to create overviews of the documents that have been sent in the current client. Overviews can be limited according to send times, communication methods, and send status. The entire send history of each document can also be called up. Overviews enable recipients to be notified and documents to be sent again.
Frequently Asked Questions How do I configure SAPconnect in the context of system monitoring so that an auto-reaction (sending mail) runs correctly?
2012
© 2011 SAP AG. All rights reserved.
583
Unit 12: SAPconnect and SMTP
TADM12_1
If an alert occurs in a system according to transaction RZ20, and a correctly set up auto-reaction method is assigned, the following happens: 1. 2.
The alert is marked red in transaction RZ20 shortly after it occurs. This red alert must be recognized by the AutoABAP SAPMSSY8, which runs every five minutes. The AutoABAP then starts the assigned auto-reaction method. Caution: Since SAPMSSY8 is executed in client 000, SAPconnect must also be correctly configured in client 000.
3.
After the auto-reaction method is active, there is a message that is ready to send in client 000. This message is sent the next time that report RSCONN01 runs. That is, the send process must be scheduled periodically. Caution: Documents are only sent correctly if the send user (which is declared in the auto-reaction method) is assigned a mail address in client 000.
For more information, see SAP Note 176492 – Automatic email when an alert occurs (RZ20). How can I connect Microsoft Exchange Server to my SAP systems? The SAP Exchange Connector connects the MS Exchange Server to the SAPconnect mail interface. However, the SAP Exchange Connector is no longer delivered by SAP. Instead, it has been replaced by the SMTP plug-in. See also SAP Note 122657 – SXC: Version overview and history.
584
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication with SAPconnect
Lesson Summary You should now be able to: • Outline the function of SAPconnect • Create a node for sending a remote mail to a different SAP system
Related Information For more information about SAPconnect and its use, see the following areas in the online documentation for SAP NetWeaver 7.0 (including enhancement package 2) and in the SAP Notes listed: •
•
• • • • • • •
2012
SAP NetWeaver 7.02 online documentation, path SAP NetWeaver → SAP NetWeaver by Key Capability → Application Platform by Key Capability → Business Services → Business Communication Services → Generic Business Tools for Application Developers (BC-SRV-GBT). SAP NetWeaver 7.02 online documentation, area SAP NetWeaver → SAP NetWeaver by Key Capability → Application Platform by Key Capability → Platform-Wide Services → Connectivity → Communication Interfaces for Mail and Telephony → SAPconnect (BC-SRV-COM). In the Administration → Inbound Distribution (sub)area, you can also find information about distributing incoming mails. SAP Note 455127: E-mail (SMTP) in different SAP releases SAP Note 17194: Telefax in various SAP Releases SAP Note 455129: Paging/SMS in different SAP releases SAP Note 312690: SAPconnect: Collective note SAP Note 455140: Configuration of e-mail, fax, paging or SMS using SMTP SAP Note 455142: SAPconnect: Configuration paging/SMS via HTTP SAP Note 598718: SAPconnect - Performance
© 2011 SAP AG. All rights reserved.
585
Unit 12: SAPconnect and SMTP
TADM12_1
Lesson: Communication Using SMTP Lesson Overview Connecting an SAP system to a mail server has become significantly easier due to the ICM process with SMTP plug-in available as of AS ABAP 6.10. This lesson provides you with an overview of configuring the SAP system for SMTP. We will discuss both sending and receiving e-mails.
Lesson Objectives After completing this lesson, you will be able to: • •
List the steps required to connect the SAP system to a mail server Configure the SAP system for the connection to a mail server
Business Example Your company uses SAP systems based on Application Server ABAP (AS ABAP). As a member of the system administration team, it is your task to implement the exchange of e-mails between an SAP system and an SMTP-compatible mail server without external components.
Introduction to Communication Using SMTP As of AS ABAP 6.10, SMTP (Simple Mail Transfer Protocol) is supported directly by the ICM process. This means that it is possible to exchange e-mails between the SAP system and any SMTP-compatible mail server without using additional external components (such as connectors or gateways). You can use any product that meets the SMTP standard as a mail server. The following figure shows a simplified e-mail system landscape for a company. If an e-mail is sent to the address
[email protected], it first reaches a Mail Transfer Agent (MTA). This is a program (such as sendmail) that is responsible for forwarding and delivering e-mails: When a mail is received from a Mail User Agent (MUA) (the actual e-mail program) or a different MTA, the MTA analyzes the mail and either sends it to the local user (that is, his or her MUA) or forwards it to a different MTA (if alias rules have been defined, for example). In the example shown here, the inbound e-mail is forwarded to the SAP CRM system with the local domain crm.sap.com.
586
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication Using SMTP
Figure 218: Task of a Mail Transfer Agent (MTA)
As of AS ABAP 6.20, faxes and text messages (pager / SMS) can also be exchanged using SMTP. Faxes and text messages are packed into e-mails for this purpose. For receipt, the fax/text message server or provider sends e-mails to addresses with the SAP system domain (such as to
[email protected]).
Restrictions of the AS ABAP with Regard to Receiving SMTP Mails As of AS ABAP 7.02, in the outbound direction the SAP system can transfer mails that were created in one client to different mail servers. You can specify the host address and port number of this mail servers in the definition of the SAPconnect SMTP node. The AS ABAP can receive e-mails via SMTP and redistribute these e-mails to Business Workplace (previously: SAP Office) users. In the inbound direction, the SAP system can receive mails from any number of mail servers. Each client can be reached by a separate virtual mail server (host name, port number) that is configured in transaction SICF. The best approach to addressing the SAP system and its clients is to use a separate subdomain for each client (such as training.sap.com). These
2012
© 2011 SAP AG. All rights reserved.
587
Unit 12: SAPconnect and SMTP
TADM12_1
subdomains are assigned to host names and port numbers using routing rules on the mail servers. The following restriction applies: SAPconnect cannot be an MTA itself, that is, it cannot forward the mails to other mail servers.
Configuring the SAP System for SMTP If you want to use the SMTP function, you have to set the following profile parameters for the AS ABAP. Note: The following restriction applies: The SAPconnect send job can only be scheduled for application servers on which SMTP is activated. You should therefore activate SMTP on all application servers of the SAP system. •
rdisp/start_icman = true This parameter starts the ICM process automatically during the system startup.
• •
exe/icman = icm/server_port_ = PROT=SMTP,PORT= This parameter opens a TCP/IP port for receiving mails using the SMTP plug-in. describes the port number. If no mails are to be received in this SAP system, set to zero. Hint: The parameter is/SMTP/virt_host_ defines a virtual mail host for receiving mails. If all inbound mails (including status notifications) are to be received and processed in a single client of the SAP system, this parameter is not required and is/SMTP/virt_host_0 = *:*; is taken as the default. If multiple clients are intended as receivers, you must create a virtual host for each client.
To avoid performance bottlenecks due to high numbers of SMTP requests (or, optionally, HTTP/S), you can use parameters to restrict the context usage in the backend SAP system for a protocol. You specify the percentage of all available contexts that can be used for the relevant protocol. In the SAP system, the maximum number of contexts in the system is limited by the profile parameter value of rdisp/tm_max_no (this parameter restricts the maximum number of users per instance). If the following quotas are exceeded, the requests are rejected in the ICM. • •
icm/HTTP(S)/context_quota icm/SMTP/context_quota
For example, with the setting icm/SMTP/context_quota = 20, you specify that only 20 percent of the available contexts can be used for SMTP (mail functions). This means that you have more capacity for HTTP(S) requests if there is a high workload.
588
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication Using SMTP
Sending E-Mails from an SAP System E-mails are created either automatically using an application or manually in the SAP mail client (Business Workplace, transaction SBWP), and are sent to a mail server by SMTP. These e-mails can now also be displayed with a suitable mail client for this mail server, as shown in the following figure.
Figure 219: Outbound Mails: Process
2012
© 2011 SAP AG. All rights reserved.
589
Unit 12: SAPconnect and SMTP
TADM12_1
Note: Short explanations of the abbreviations used in the figure: •
•
•
•
POP is the abbreviation for Post Office Protocol. POP was defined in 1984 in connection with TCP/IP and allows the receipt of e-mails even on systems that cannot guarantee permanent connection to the mail server. POP3 is, therefore, together with SMTP (for sending messages), the standard protocol for most mail clients in the Internet. The POP3 protocol can delete messages on the server or leave them there, and can delete messages directly without first transferring them from the server. If more is required, such as hierarchical mailboxes, or filters, you should use the functions of the client; the protocol does not provide anything of this sort - you may have to use IMAP. IMAP : is the abbreviation for Internet Message Access Protocol. This is an e-mail protocol that allows the client to process mails on the server. You can also create folders on the mail server (remote mailboxes) to sort mails. IMAP was developed to transfer messages only when required: The user can choose (unlike with POP3) which data he or she actually wants to transfer to his or her own computer. SMTP: This is the abbreviation for Simple Mail Transfer Protocol. SMTP is the standard for exchanging e-mails between servers in the network. Mail clients use SMTP to send e-mails to a server, but not to receive e-mails. MIME: This is the abbreviation for Multipurpose Internet Mail Extensions. It consists of Internet extensions (coding procedures) for including binary data in Internet mails. In addition, MIME supports multipart mails to allow different data types in a mail or binary attachments, and mails in HTML format.
Follow the procedure below to configure a send process for SMTP: 1. 2.
As described in the section Configuring the SAP System for SMTP, the key profile parameters for SMTP must be maintained. Maintain the user addresses, as every user that wants to send e-mails requires an Internet e-mail address. This is used as the sender address. You can use transaction SU01 to enter the Internet address under E-Mail on the Address tab page. For security reasons, if a user is maintaining his or her own data (transaction SU3), he or she cannot maintain the entries for the communication types E-mail (INT or SMTP) and Remote Mail (RML). Note: You can use report RSADRCK7 to create e-mail addresses of type @ automatically for all (SU01) users in your client. This report is described in more detail in SAP Note 104263.
590
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication Using SMTP
3.
In transaction SCOT, define the domain of the SAP system client under Settings → Default Domain. You need to do this for the following reasons: • • •
The SMTP plug-in logs onto the mail server with the domain as an ID. The message ID of the outbound e-mails is compiled using this domain. If an SAP user sends an e-mail without an Internet e-mail address, a sender address consisting of the SAP user name and this domain is generated. Note: You must make SAPconnect settings in transaction SCOT for every client from which you send messages.
4.
Every client has an SMTP node. This node is created by the SAP system and cannot be deleted. The following steps are required to configure the SMTP node to send an Internet mail: • • •
Set the node in use. In the Mail Host and Mail Port fields, specify the mail server to which the outbound mails are to be transferred. If you want to use a Multi-Display, Multi-Processing (MDMP) or Unicode system, enter 4110 Unicode UTF-8 in the Code Page field (if applicable) Note: For more information about mails to and from SAP systems with several code pages, see SAP Notes 633265 and 664833.
•
5.
When you configure the node, enter the address range of recipient addresses that can be reached via this node (such as *, if this node is to process all SMTP mails). • Enter the output format for SAP documents, such as PDF for SAPscript/Smart Forms, HTM for ABAP lists, and TXT for and Business Object/links and RAW text. It is also useful to schedule a send job, as e-mails sent from an SAP application are initially placed in a wait queue. A background job that runs periodically, the SAPconnect send job, collects e-mails from the wait queue and sends them to the mail server. In the Jobs view in transaction SCOT, create a background job, for example with the variant SAP&CONNECTALL, and schedule it periodically (with a period value of, for example, 10 minutes). Hint: Make sure that you schedule the job on an instance in which an ICM process is also configured and active.
You can also configure the node for sending faxes or text messages in the same way.
2012
© 2011 SAP AG. All rights reserved.
591
Unit 12: SAPconnect and SMTP
TADM12_1
The figure below shows a configured SMTP node in transaction SCOT.
Figure 220: Configuring an SMTP Node
Receiving E-Mails in an SAP System When you send an e-mail from a mail client to a user in an SAP system, the e-mail is first forwarded to a mail server and then forwarded to the SAP system by the MTA. The e-mails are sent to the mail client in the SAP system (Business Workplace) on a client-dependent basis using SAPconnect. This is illustrated by the following figure.
592
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication Using SMTP
Figure 221: Incoming Mails: Process
Follow the procedure below to configure the process for receiving SMTP mails: 1. 2. 3.
4. 5.
2012
As described in the section Configuring the SAP System for SMTP, the key profile parameters for SMTP must be maintained. In addition, a user is required for processing inbound mails in each client. Use transaction SU01 to create a system user with the profile S_A.SCON. You need to maintain an Internet mail address for every user that is to receive e-mails in an SAP system. This is also used as the sender address. Enter the Internet mail address in transaction SU01 on the Address tab page under E-Mail. For security reasons, if a user is maintaining his or her own data (transaction SU3), he or she cannot maintain the entries for the communication types E-mail (INT or SMTP) and Remote Mail (RML). In transaction SCOT, define the domain of the SAP system client under Settings → Default Domain. For every client of an SAP system in which inbound mails (or status notifications for sent mails) are to be received and possibly processed, you must create an SMTP server for which an assignment to a virtual mail host and logon data are stored. In transaction SICF, SAP already ships an SMTP server note for every SAP system. Use this for the first client that you want to be able to receive mails, and create a new SMTP server for each additional client. If you are working with multiple clients, you must create a virtual host for each client in which messages are received using the SMTP plug-in. Make the following settings in transaction SICF by double-clicking the SAPconnect menu entry (see also SAP Note 546147):
© 2011 SAP AG. All rights reserved.
593
Unit 12: SAPconnect and SMTP
•
TADM12_1
On the Host Data tab page, maintain the parameter is/SMTP/virt_host_= :,,...; This parameter defines a virtual mail host for receiving mails. If all inbound mails (including status notifications) are to be received and processed by a single client in the SAP system, this parameter is not required. In this case, is/SMTP/virt_host_0= :; is used as the default. If multiple clients are intended as receivers, you must create a virtual host for each client. and describe the name of the host and the port to which inbound mails are addressed.
•
•
On the Logon Data tab page, enter the client to which the mails received by the virtual mail host are to be forwarded and maintain the logon data of the system user that was created in this client for the inbound mails. On the Handler List tab page, add (if it does not already exist) CL_SMTP_EXT_SAPCONNECT at position 1. Note: As of AS ABAP 6.20, every SMTP server must be activated (in transaction SICF under Service/Virtual Host → Activate or by clicking the right mouse button and using the context menu) after it has been created or changed.
The steps required to configure the mail connection in the SAP system are summarized again in the figure below.
594
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication Using SMTP
Figure 222: Configuring the Mail Connection via SMTP
Outlook: New Functionality for the Administration of Business Communication Services – Transaction SOADM As of AS ABAP 7.02 SAPconnect contains a new integrated administration interface, which you can use to set up external communication of an SAPsystem using SMTP and monitor sending. You can navigate from this interface to all settings that are relevant for SAPconnect. There are also functions to help you to maintain and manage your SAPconnect environment. You access the new SAPconnect administration interface by calling transaction SOADM.
2012
© 2011 SAP AG. All rights reserved.
595
Unit 12: SAPconnect and SMTP
TADM12_1
Figure 223: Outlook: New Administration Interface for SAPconnect – Transaction SOADM
For future releases of AS ABAP it is intended that when you start transaction SCOT, you will end up in the new administration interface whereas the former transaction SCOT can be called by starting transaction SCON. Note: Note that the new administration interface allows to monitor inbound STMP messages as well but it does not support remote mail (RML) any longer. The following areas may be helpful (examples): • • •
596
Administration → System Status corresponds to the System Status view in transaction SCOT. Settings → Outbound Messages → Send Jobs corresponds to the Jobs view in transaction SCOT. Administration → Outbound Send Requests corresponds to Utilities → Overview of send orders transaction SCOT.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication Using SMTP
Exercise 29: Sending and Receiving E-Mails by SMTP with AS ABAP Exercise Objectives After completing this exercise, you will be able to: • Send e-mails from an SAP system using SMTP • Receive e-mails in an SAP system using SMTP
Business Example As a member of the system administration team, you want to implement the exchange of e-mails between an SAP system and an SMTP-compatible mail server without external components.
2012
© 2011 SAP AG. All rights reserved.
597
Unit 12: SAPconnect and SMTP
TADM12_1
Task 1: Access to the External Mail Inbox
Figure 224: Overall Scenario of the Training Landscape for the Outbound Mail
Access to your external mail inbox. Note: For the purposes of this training course, we will use the JAMES mail server that is running on the instructor's host. Access is via a prepared Web Dynpro ABAP application ZMAIL. 1.
Call the Web Dynpro ABAP application to access “your” mail inbox -##@training.sap.com on the JAMES mail server. In standard ADM102 courses, the ADM102-## users have a prepared menu entry to launch transaction ZMAIL in their role-based SAP Easy Access user menu (in the folder that corresponds to this unit of the course). Double-click this menu item. In installation courses such as TADM12_1, you must enter the following URL manually: http://twdfSSSS.wdf.sap.corp:80$$/sap/bc/webdynpro/sap/zmail. Note: Note that this URL is case-sensitive. When the course materials are published, a hyphen “-” may be displayed at the end of the line. This hyphen is not part of the URL.
Continued on next page
598
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication Using SMTP
Result You can see the incoming mails for your e-mail recipients on the shared mail server.
Task 2: Check the SMTP Configuration of Your SAP System Check whether your SAP system has been configured for SMTP. If this is not the case, configure your SAP system accordingly. 1.
For each of your application servers, determine the port at which requests in the SMTP protocol are processed.
2.
If your SAP system has not yet been configured for SMTP, use transaction RZ10 to add the parameter icm/server_port_ for your default profile and assign it the value PROT=SMTP,PORT=250$$. Save and activate the profile and then restart all the ICM processes of your system in transaction SMICM. Then repeat the first step of the task.
Task 3: Setting Up the Sending of E-Mails in the SAP System Generate Internet addresses, set the default domain and receipt confirmation, and configure the SMTP node. 1.
Assign all users in your client the Internet address @domain##.sap.com, where ## is your (two-digit) group number. Then check the changes using your user (for example, ADM102-##).
2.
In your SAP system, enter domain##.sap.com as the default domain.
3.
Configure SAPconnect so that no confirmation of receipt is expected for Internet mails.
4.
Set up the SMTP node in your SAP system so that e-mails addressed to recipients in the domain training.sap.com can be sent to the external mail server (running on the instructor's host). Hint: If the external mail server also operates as a Mail Transfer Agent (MTA) and you have only specified 1 STMP node in transaction SCOT, you could also use enter * as the SAPconnect domain. However, in the training landscape, the mail server does not forward any e-mails, but rather processes only the specified domain. Continued on next page
2012
© 2011 SAP AG. All rights reserved.
599
Unit 12: SAPconnect and SMTP
TADM12_1
Result Your SMTP node is now ready for use and is responsible for all e-mails sent to the specified address range. It is this easy to connect to an SMTP-compatible mail server.
Task 4: Sending an E-Mail from an SAP System Create an e-mail and start the send process. 1.
In the SAP system, create an e-mail to the recipient ##@training.sap.com.
2.
Start the send process manually.
3.
Check the external mail server to see whether your mail has arrived.
4.
Optional: Schedule the send process for Internet mails periodically (every five minutes). Then send a list output (such as report SHOWCOLO) to recipient -##@training.sap.com and observe how the output is sent during the next send process.
Result Congratulations on successfully connecting your SAP system to a mail server.
Continued on next page
600
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication Using SMTP
Task 5: Receiving E-Mails in the SAP System Setting up the SAP system for receiving e-mails.
Figure 225: Overall Scenario of the Training Landscape for Inbound Mail
1.
In your SAP system, create a user, MAILDISP##, to distribute e-mails in the current client. This user should be of the type System. The user should have the initial password chosen by you and it should have the authorization profile S_A.SCON provided by SAP.
2.
Enter the user that you have just created in the virtual host for SAPconnect (transaction SICF). Remember to activate the virtual host after changing it.
3.
Using the Web Dynpro ABAP application ZMAIL, send an e-mail to “your” AS ABAP system, either as a “Reply” to an e-mail received previously or as a “New” message. Fill in the mail popup as follows:
4.
To
-##@domain##.sap.com
Subject
arbitrary
Mail server
twdfSSSS.wdf.sap.corp:
Message
arbitrary
Check your inbox in the SAP system. Continued on next page
2012
© 2011 SAP AG. All rights reserved.
601
Unit 12: SAPconnect and SMTP
TADM12_1
Task 6: New Administration Interface Male yourself familiar with the new administration interface for SAPconnect 1.
602
Enter the new administration interface for SAPconnect. Find out how many outbound SMTP send requests have been transmitted and how many inbound STMP send requests have been processed today.
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication Using SMTP
Solution 29: Sending and Receiving E-Mails by SMTP with AS ABAP Task 1: Access to the External Mail Inbox
Figure 226: Overall Scenario of the Training Landscape for the Outbound Mail
Access to your external mail inbox. Note: For the purposes of this training course, we will use the JAMES mail server that is running on the instructor's host. Access is via a prepared Web Dynpro ABAP application ZMAIL. 1.
Call the Web Dynpro ABAP application to access “your” mail inbox -##@training.sap.com on the JAMES mail server. In standard ADM102 courses, the ADM102-## users have a prepared menu entry to launch transaction ZMAIL in their role-based SAP Easy Access user menu (in the folder that corresponds to this unit of the course). Double-click this menu item.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
603
Unit 12: SAPconnect and SMTP
TADM12_1
In installation courses such as TADM12_1, you must enter the following URL manually: http://twdfSSSS.wdf.sap.corp:80$$/sap/bc/webdynpro/sap/zmail. Note: Note that this URL is case-sensitive. When the course materials are published, a hyphen “-” may be displayed at the end of the line. This hyphen is not part of the URL. a)
See the task description. ZMAIL is a Web Dynpro ABAP application that has been created especially for this course.
Result You can see the incoming mails for your e-mail recipients on the shared mail server.
Task 2: Check the SMTP Configuration of Your SAP System Check whether your SAP system has been configured for SMTP. If this is not the case, configure your SAP system accordingly. 1.
For each of your application servers, determine the port at which requests in the SMTP protocol are processed. a)
There are a number of ways to determine the port responsible for SMTP. The simplest method is to call transaction SMICM and choose Services. You can see the number under which the SMTP service is running in the system in the first column (it is represented here by xx). The associated profile parameter is called icm/server_port_. You can also find the value of this parameter, for example: • • •
b)
In transaction SMICM, by choosing Goto → Parameters → Display By calling report RSPFPAR In Profile Maintenance (transaction RZ10)
Note that the port determined in this way (such as 25011) applies only for the application server to which you are currently logged on. Log on to the other instance of your SAP system (for example using transaction SM51), to determine the port that is set there.
Continued on next page
604
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication Using SMTP
2.
If your SAP system has not yet been configured for SMTP, use transaction RZ10 to add the parameter icm/server_port_ for your default profile and assign it the value PROT=SMTP,PORT=250$$. Save and activate the profile and then restart all the ICM processes of your system in transaction SMICM. Then repeat the first step of the task. a)
If, during the previous step of this exercise, you discovered in transaction SMICM that SMTP is not configured, switch to transaction RZ10 and open the extended maintenance of the DEFAULT profile in change mode. Hint: You may have to load the profiles by choosing Utilities → Import profiles → Of active servers.
b)
Choose Create Parameter. Enter icm/server_port_ as the parameter name and PROT=SMTP,PORT=250$$ as the parameter value.
c)
Save your changes by choosing Copy → Back → Copy → Back → Save. If a dialog box appears with information about an incorrect parameter value, choose Yes and ensure that your parameter is displayed correctly. If you are prompted to do so, activate the profile at operating system level. Confirm the following dialog boxes by choosing Continue.
d)
Instead of now starting the entire SAP system, you can just start the ICM processes. To do so, call transaction SMICM and choose Administration → ICM → Restart → Yes and then Administration → ICM → Exit Hard → Global. Confirm the query by choosing Yes. Then choose Services again and check whether your changes have been made.
Task 3: Setting Up the Sending of E-Mails in the SAP System Generate Internet addresses, set the default domain and receipt confirmation, and configure the SMTP node. 1.
Assign all users in your client the Internet address @domain##.sap.com, where ## is your (two-digit) group number.
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
605
Unit 12: SAPconnect and SMTP
TADM12_1
Then check the changes using your user (for example, ADM102-##). a)
Start the report RSADRCK7 (using transaction SA38, for example).
b)
In the Domain field, enter domain##.sap.com (where ## is your group number). Deselect the Keep existing addresses and Test mode checkboxes and set the Use user names checkbox. Once you have chosen Execute, the system displays a log of all the changes made.
c)
2.
In your SAP system, enter domain##.sap.com as the default domain. a)
3.
In transaction SU01, enter the user -## (for example, ADM102-##) and choose Display. On the Address tab page, the E-Mail field should contain the value -##@domain##.sap.com (where ## is your group number).
Start SAPconnect Administration (transaction SCOT), choose Settings → Default Domain and enter the value domain##.sap.com (where ## is your group number).
Configure SAPconnect so that no confirmation of receipt is expected for Internet mails. a)
In transaction SCOT choose Settings → Confirmation of receipt and define that SAPconnect does not expect receipt confirmation for Internet mail. Hint: This setting means that sent messages of the type Internet mail are immediately assigned the status “Completed” (otherwise, they remain in the status “In transit” until a confirmation of receipt is received). In the SAP system, the sending application determines whether a confirmation of receipt is actually requested.
Continued on next page
606
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication Using SMTP
4.
Set up the SMTP node in your SAP system so that e-mails addressed to recipients in the domain training.sap.com can be sent to the external mail server (running on the instructor's host). Hint: If the external mail server also operates as a Mail Transfer Agent (MTA) and you have only specified 1 STMP node in transaction SCOT, you could also use enter * as the SAPconnect domain. However, in the training landscape, the mail server does not forward any e-mails, but rather processes only the specified domain. a)
If you have not already done so, switch to View → Node. Hint: You should see a “-” icon next to the SMTP node, as this node is not yet operational.
b)
Double-click the SMTP node and enter the following information: Description
enter a self explaining text
Maximum waiting time...
30 minutes
Node in use
Check this field
Mail Host
twdfSSSS.wdf.sap.corp
Mail Port
The port entered for the external JAMES mail server (typically 25)
For Supported address types, choose the Set button in the Internet line. In the Address area (on the resulting screen) enter *training.sap.com, and choose Continue. Choose Continue to save your settings. c)
In the node display in transaction SCOT, check that the SMTP node no longer contains any “-” characters and that it appears*TRAINING.SAP.COM when you expand the address range.
Result Your SMTP node is now ready for use and is responsible for all e-mails sent to the specified address range. It is this easy to connect to an SMTP-compatible mail server. Continued on next page
2012
© 2011 SAP AG. All rights reserved.
607
Unit 12: SAPconnect and SMTP
TADM12_1
Task 4: Sending an E-Mail from an SAP System Create an e-mail and start the send process. 1.
2.
In the SAP system, create an e-mail to the recipient ##@training.sap.com. a)
Call the SAP Business Workplace (transaction SBWP) and choose New Message.
b)
In the new window, create a message (using any title and content). When you press ENTER to transfer the address -##@training.sap.com for the Recipient (in ADM102 this would be ADM102-##@training.sap.com), the SAP system identifies from the structure of the address that it is an Internet address. Messages can be sent to different types of address (see the F4 help for the Recip. Type field).
c)
Finally, choose Send...
Start the send process manually. a)
View the information in SAPconnect Administration (transaction SCOT) under View → System Status. There should be a message with status “Waiting”.
b)
Now choose the Start send process function for the Address Type INT (for Internet mail address). Use the default values under No. Work Processes and Server group and choose Start.
c)
3.
View the status once the send process is completed. If an error occurs, you can choose Utilities → Overview of send orders to analyze the cause of the error.
Check the external mail server to see whether your mail has arrived. a)
If the window is still open from the first task of this exercise, simply click on the Last refreshed at [...] link. If it is not, repeat the first task of this ecercise.
Continued on next page
608
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication Using SMTP
4.
Optional: Schedule the send process for Internet mails periodically (every five minutes). Then send a list output (such as report SHOWCOLO) to recipient -##@training.sap.com and observe how the output is sent during the next send process. a)
In transaction SCOT, choose View → Jobs. The system displays the number of times the send process has already run in your client (you can change the evaluation period).
b)
Choose Create and enter a job name (such as Send Internet e-mails). SAP delivers a variant, SAP&CONNECTINT, for this address type. On the next screen, select this entry and choose Schedule. On the next screen, adjust the time if required (you can view the system time by choosing System → Status) and then choose Schedule Periodically. As the period, enter 5 minutes and choose Create. The job that you have just created now appears in the job overview (transaction SM37).
c)
Call any list display in the SAP system (proposal: use transaction SA38 to execute report SHOWCOLO). Choose System → List → Send and enter ##@training.sap.com as the Recipient. The system proposes the report title as the default Title of the message. If desired, enter some text as the Document contents. Choose Send... to transfer your message to SAPconnect.
d)
The message is processed by the send process during the following five minutes. If the e-mail finally is displayed in the browser, the attachment is displayed in the bottom area of the browser screen. Note: By default, ABAP lists are converted to HTML format. As you can see from the selection options in the Output Formats for SAP Documents area in the definition of the SMTP node, other formats are supported in the definition of the SAPconnect node as well. Feel free to change the format for ABAP lists from HTM to PDF.
Result Congratulations on successfully connecting your SAP system to a mail server. Continued on next page
2012
© 2011 SAP AG. All rights reserved.
609
Unit 12: SAPconnect and SMTP
TADM12_1
Task 5: Receiving E-Mails in the SAP System Setting up the SAP system for receiving e-mails.
Figure 227: Overall Scenario of the Training Landscape for Inbound Mail
1.
In your SAP system, create a user, MAILDISP##, to distribute e-mails in the current client. This user should be of the type System. The user should have the initial password chosen by you and it should have the authorization profile S_A.SCON provided by SAP. a)
In User Maintenance (transaction SU01), create the user MAILDISP## as described in the task. On the Logon Data tab page, set the user type to System. On the Profiles tab, assign the authorization profile S_A.SCON to this user. Choose Save to save your entries. Hint: Users of the type System are intended for dialog-free communication between different systems and are excluded from the checks for expired passwords. For more information, see SAP Note 622464 – Change: Password change req. entry for “SYSTEM” user type.
Continued on next page
610
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication Using SMTP
2.
Enter the user that you have just created in the virtual host for SAPconnect (transaction SICF). Remember to activate the virtual host after changing it. a)
On the initial screen of transaction SICF, select the hierarchy type SERVICE and choose Execute. On the following screen, double-click the SAPconnect entry. On the Logon Data tab page, switch to change mode. Enter the data for user MAILDISP## (client, user, password, and language). Leave all other fields unchanged and save your changes. Create a transport request at this point, if needed. Hint: If you receive an error message when you select the language for the user because a code page is not supported, you have to activate your language using report RSCPINST. To do so, add your language on the left-hand side of the initial screen of this report and then choose Activate.
b)
In transaction SICF, click the SAPconnect entry with the right mouse button, choose Activate SMTP Host and confirm the subsequent dialog box by choosing Yes. Hint: An SMTP server is required for each client of an SAP system in which e-mails can be received. You have now created the connection to a virtual mail host. If e-mails were also to be delivered to other clients in your SAP system, you would have to create additional virtual mail hosts for these clients in transaction SICF.
3.
Using the Web Dynpro ABAP application ZMAIL, send an e-mail to “your” AS ABAP system, either as a “Reply” to an e-mail received previously or as a “New” message. Fill in the mail popup as follows:
Continued on next page
2012
© 2011 SAP AG. All rights reserved.
611
Unit 12: SAPconnect and SMTP
To
-##@domain##.sap.com
Subject
arbitrary
Mail server
twdfSSSS.wdf.sap.corp:
Message
arbitrary
a)
Call the Web Dynpro ABAP application, as described in the first task of this exercise.
b)
Choose one of the following two functions: • •
4.
TADM12_1
Send a New mail message, or Reply, after selecting a message received previously
c)
Fill in the fields as mentioned in the exercise.
d)
Choose OK to send the message.
Check your inbox in the SAP system. a)
As user -## in the SAP system, call the SAP Business Workplace (transaction SBWP). You should find your e-mail in the Inbox area.
Continued on next page
612
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Lesson: Communication Using SMTP
Task 6: New Administration Interface Male yourself familiar with the new administration interface for SAPconnect 1.
Enter the new administration interface for SAPconnect. Find out how many outbound SMTP send requests have been transmitted and how many inbound STMP send requests have been processed today. a)
Enter transaction SOADM.
b)
To find out how many outbound SMTP send request have been transmitted, open the area Business Communication Administration → Administration → System Status in the tree structure on the left hand side. On the right hand side then open the tree () → Internet. Here you can see for each SMTP node how many SMTP message have been transmitted with the help of this node.
c)
To find out how many inbound SMTP send request have been processed today, open the area Business Communication Administration → Administration → Inbound Send Requests in the tree structure on the left hand side. On the right hand side then switch to the Received At tab. Make sure that the Date received and Time received fields are maintained accordingly and choose Update. As a result you get a list of message that have been received within the selected time frame.
Result You are now able to connect SMTP for an SAP system in both directions. We wish you every success in implementing this in your company.
2012
© 2011 SAP AG. All rights reserved.
613
Unit 12: SAPconnect and SMTP
TADM12_1
Lesson Summary You should now be able to: • List the steps required to connect the SAP system to a mail server • Configure the SAP system for the connection to a mail server
Related Information For more information about configuring the mail connection, see •
SAP NetWeaver 7.02 online documentation, area SAP NetWeaver → SAP NetWeaver by Key Capability → Application Platform by Key Capability → Platform-Wide Services → Connectivity → Communication Interfaces for Mail and Telephony → SAPconnect (BC-SRV-COM). In the Administration → Inbound Distribution (sub)area, you can also find information about distributing incoming mails.
For more information about the procedures for configuring an e-mail connection in the SAP system, see the following SAP Notes: • • • • • • • •
614
SAP Note 455140: Configuration of e-mail, fax, paging or SMS using SMTP SAP Note 455127: E-mail (SMTP) in different SAP releases SAP Note 312690: SAPconnect: Collective note SAP Note 546147: SMTP plug-in: MS Exchange sends only to port 25 SAP Note 104263: Generating Internet addresses for users SAP Note 690020: SAPconnect send process hangs with large mails SAP Note 607108: Problem analysis when you send or receive e-mails SAP Note 633265, 664833, 694151 and 883840: SMTP PlugIn: Multi-codepage ability
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Unit Summary
Unit Summary You should now be able to: • Outline the function of SAPconnect • Create a node for sending a remote mail to a different SAP system • List the steps required to connect the SAP system to a mail server • Configure the SAP system for the connection to a mail server
2012
© 2011 SAP AG. All rights reserved.
615
Unit Summary
616
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Test Your Knowledge
Test Your Knowledge 1.
Which of the following statements regarding SAPconnect are correct? Choose the correct answer(s).
2.
□
A
□ □
B C
□ □
D E
As of SAP Web AS 6.10, a Microsoft Exchange Infrastructure must be set up outside the SAP system to be able to send mail from SAP systems. It is not possible to connect the UNIX-based sendmail to SAP systems. SAPconnect allows you to send mail both by RFC and the SMTP plug-in of the SAP AS ABAP. SAPconnect is configured cross-client. A send process automatically runs periodically in every SAP system after the system installation.
The connection of a mail server to an SAP system to send e-mails using SMTP from the SAP system runs through an SAPconnect node. Determine whether this statement is true or false.
□ □
2012
True False
© 2011 SAP AG. All rights reserved.
617
Test Your Knowledge
TADM12_1
Answers 1.
Which of the following statements regarding SAPconnect are correct? Answer: C SAPconnect contains two methods for sending mails: using an RFC connection or directly using a plug-in of the AS ABAP. The other statements are incorrect.
2.
The connection of a mail server to an SAP system to send e-mails using SMTP from the SAP system runs through an SAPconnect node. Answer: True To configure a send process for SMTP in the SAP system, you must, among other things, also have configured and activated an SMTP node in transaction SCOT (SAPconnect).
618
© 2011 SAP AG. All rights reserved.
2012
Test Your Knowledge
619
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Course Summary
TADM12_1
Course Summary You should now be able to: •
620
process basic tasks within the technology environment of SAP systems
© 2011 SAP AG. All rights reserved.
2012
Glossary central system A central SAP system consists of a single central instance that provides all required SAP services and the associated database. In the case of a central system, these are usually on the same host. Communication Type Type of communication supported by SAPconnect, such as sending data by e-mail or fax, transferring data to archiving systems or communication services, and so on, that allow data to be sent to pagers, or as an SMS. Communication types are configured in SAPconnect. dispatcher (ABAP) Central process of an AS ABAP instance. It is responsible, amongst other things, for starting work processes and distributing the transaction load across work processes. dispatcher (Java) Central process of a Java instance. It is, amongst other things, responsible for distributing the transaction load across server processes. instance Administrative unit in which components of an SAP system that provide one or more services are grouped together. These services are started and stopped at the same time. Instance Number Two-digit number that identifies the instance. Each instance of the SAP system requires its own instance number. Two instances with the same number can not run on one machine, because of the associated ports. Internet Communication Manager The Internet Communication Manager (ICM) is the component in the SAP architecture that allows the SAP system to communicate directly via http and related protocolls. It is started by the dispatcher of an instance. language import The import of language-dependent texts of an additional language into an SAP system.
2012
© 2011 SAP AG. All rights reserved.
621
Glossary
TADM12_1
maintenance certificate A maintenance certificate enables the SAP software logistics tools (for example, SPAM, SAINT, and JSPM) to identify the system to be maintained and to determine the extent of maintenance required. It is also used to ensure that only customers with a valid maintenance contract can perform the relevant maintenance transactions. maintenance transaction To import Support Packages, among other things, SAP recommends that you create a maintenance transaction with the Maintenance Optimizer. This maintenance transaction is used to calculate a consistent combination of Support Packages for a specific system or a combination of systems in the landscape and to approve this combination for download. Modification Adjustment If SAP objects were modified by the customer, and these objects are imported with a Support Package, enhancement package, or a release upgrade, the objects have to be adjusted when they are imported. If these objects are not adjusted, the customer's modifications that have been made to the SAP objects are reset to the SAP delivery status. MTA Mail Transfer Agent; The program that is responsible for forwarding and delivering e-mails: When a mail is received from a Mail User Agent (MUA) (the actual e-mail program) or a different MTA, the MTA analyzes the mail and either sends it to the local user (that is, his or her MUA) or forwards it to a different MTA. The MTA that is still used most frequently in the Internet is sendmail. output request An output request contains the data from a spool request in a format for a particular printer model. PAL Printing Assistant for Landscapes (PAL): PAL allows output devices to be maintained in a (central) system, and then distributed across additional (target) systems. patch To be able to correct smaller problems in the SAP system, individual corrections, known as single patches are available as SAP Notes. SAP enhancement package An SAP system consists of various software components with a particular release level. Importing parts of an SAP enhancement package updates some of these software components to a higher release level.
622
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Glossary
SAP Note SAP Notes enable you to make adjustments on the basis of changes in legal requirements, correct errors in the standard SAP software and enhance existing functions, or make new functions available. An SAP Note mainly affects changes to an individual object. Compare also “Support Packages”. server process Process that uses its services to work through requests to the AS Java. In contrast to ABAP work processes, Java server processes are multi-threaded, and can therefore process a number of requests at the same time. SMTP Simple Mail Transfer Protocol (SMTP) is an Internet standard for a host-to-host mail transport protocol. SMTP uses TCP and standard port 25. Software Component Archive Physical representation of a status of a software component. An SCA contains a specific number of Software Deployment Archives (SDAs), the set of which describes a precisely defined version status. Software Deployment Archive Delivery format for SAP applications in programming languages other than ABAP. It is a ZIP-compatible archive format that can act as a container for other archives. SPAM/SAINT update 100% patch for the Support Package Manager (transaction SPAM) and the Add-On Installation Tool (transaction SAINT). The SPAM/SAINT update is used to update these two tools. spool request A spool request contains information about data to be output, its formatting, and the printer model used. Support Package A Support Package enables you to make adjustments on the basis of changes in legal requirements, correct errors in the standard SAP software and enhance existing functions, or make new functions available. A Support Package contains a number of changed objects. Compare also “SAP Note” and “Support Package Stack”. Collection of corrections for software errors in the SAP system. Support Packages are summarized in periodic intervals and made available by SAP. Support Package Manager (SPAM) Tool (transaction SPAM) for importing Support Packages. With the Support Package Manager, the tool itself is patched too. See also “SPAM/SAINT update”.
2012
© 2011 SAP AG. All rights reserved.
623
Glossary
TADM12_1
Support Package Stack A Support Package Stack is a recommended combination of Support Packages and other patches for an SAP system. Compare also “Support Package”. TemSe Abbreviation for Temporary Sequential (database); file that temporarily includes information such as spool request data and background processing job logs. variant Preassignment of the input fields of a selection screen for reports, for example to enable the execution of the report in the background. work process Process that handles requests in an SAP system. The following work process types exist: Dialog (for executing dialog programs), update (for changing database entries), background (for executing background jobs), spool (for print formatting) and enqueue (for executing lock operations).
624
© 2011 SAP AG. All rights reserved.
2012
Index A
external program, 534
access method, 426 Activation of business functions, 236 Additional usage type, 160 AS ABAP, 9 AS ABAP ports, 112 AS Java, 9
F
B background users, 533 Backup, 175
C central instance, 9 Central Service instance, 14 central system, 9 Central system, 9 Change and Transport System (CTS), 220 Client copy, 227 communication types, 579 Configuration Wizard, 245 Configure local SLD, 82 Create own user, 218
D deployment, 404 device type, 432 Disk layout, 114 Dispatcher ABAP, 10 Java, 11 Distributed system, 9
E
front-end printing, 428 function module BP_EVENT_RAISE, 524
H Hardware sizing, 106 Help type, 208
I IMAP, 590 Installation check, 228 Installation DVDs, 34 Installation guide, 34 Installation guides, 36 Installation user, 56 instance, 10 Instance Number, 10
J Java Support Package Manager (JSPM), 160 JAVA_HOME environment variable, 40 JCE policy files, 41 JDK installation, 38 job class, 499 job server group, 532 Job Wizard, 502 JRE Installation, 38
K Kernel, 6 Kernel patch, 186, 309
external command, 534
2012
© 2011 SAP AG. All rights reserved.
625
Index
TADM12_1
L language import, 231 Language installation, 229 local printing, 426
M maintenance certificate, 335 Maintenance Optimizer, 186, 309, 340 maintenance transaction, 338 MDMP, 16 Message Transfer Agent (MTA), 586 MIME, 590 Multi Display Multi Processing (MDMP), 16 multilingual capability, 229
R Release, 5, 378 remote printing, 427 REORGJOBS, 514
N
S
Network load, 113 Note Assistant, 328 NTFS file system, 55
SAP Application, 2 SAP Application Server, 6 SAP Business Suite, 2 SAP component, 2 SAP CPS, 548 SAP ECC, 5 SAP enhancement package, 180, 410 SAP ERP, 2 SAP Gateway instance, 254 SAP GUI for HTML, 270 SAP GUI for Java, 270 SAP GUI for Windows, 270 SAP GUI installation package, 293 SAP GUI Installation Server, 286 SAP instance, 6 SAP license, 204 SAP Load Generator (SGEN), 236 SAP NetWeaver, 2 SAP Note, 186, 309, 326 SAP Solution, 2
O Online documentation, 207 Operation modes, 224 Output Request, 424
P PAL, 470 PAL Printer, 472 patch, 378 POP, 590 Prerequisite Checker, 42 Primary application server, 90 Printer Group, 472 product, 378 profile parameter icm/HTTP(S)/context_quota, 588 icm/SMTP/context_quota, 588 rdisp/btcname, 523 rdisp/btctime, 511, 517
626
rdisp/max_wprun_time, 497 rdisp/tm_max_no, 588 rdisp/wp_no_btc, 512 rdisp/wp_no_spo_Fro_max, 429 rspo/local_print/server, 430 rspo/store_location, 425 zcsa/installed_languages, 234 Profile parameters, 223 program BTC_EVENT_RAISE, 524
© 2011 SAP AG. All rights reserved.
2012
TADM12_1
Index
SAP Solution Manager, 76 SAP Solution Manager key, 48 SAP Support Package, 186, 309 SAP Support Package stack, 186, 309 SAP system, 2 SAPconnect, 578 sapevt, 524 SAPinst, 26 SAPINST_JRE_HOME environment variable, 40 SAProuter, 210 SAPSprint, 428 sapxpg, 534 Secondary application server, 90 Single Code Page (SCP), 16 SMTP, 586 SMTP plug-in, 578 software component, 378 Software component, 6 Software Component Archive, 402 Software Deployment Archive, 402 Software Deployment Manager (SDM), 402 SPAM/SAINT update, 353 spool request, 424 Spool Request, 424 Standard background jobs, 226 standard jobs, 513 Standard users, 174 Start and stop, 174 Support Package, 326, 378 Support Package Manager (SPAM), 353 Support Package Stack, 326 System Landscape Directory (SLD), 118
2012
T Target System, 472 Target System Group, 472 TemSe, 425 transaction code RZ04, 532 SBWP, 580 SCOT, 579 SE95, 368 SICF, 587, 594 SM36, 502 SM36WIZ, 502 SM37, 503 SM61, 533 SM64, 524 SM69, 537 SMLT, 229 SNOTE, 328 SP01, 461 SPAD, 430 SPAM, 353, 362 SPAU, 368 SPDD, 368 SU3, 441, 445 Transport host, 58 Transport Management System (STMS), 221
U Unicode, 16 Usage type, 15, 110
W Windows domain, 55 Windows domain installation, 56 Windows file system cache, 55 Windows local installation, 56 Workprocess, 9
© 2011 SAP AG. All rights reserved.
627
Index
628
TADM12_1
© 2011 SAP AG. All rights reserved.
2012
Feedback SAP AG has made every effort in the preparation of this course to ensure the accuracy and completeness of the materials. If you have any corrections or suggestions for improvement, please record them in the appropriate place in the course evaluation.
2012
© 2011 SAP AG. All rights reserved.
629
