TADM10-1-en-Col99-2013

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1 SAP NetWeaver AS – Implementation & Operation I SAP NetWeaver

Date Training Center Instructors Education Website

Participant Handbook Course Version: 99 Course Duration: 10 Day(s) Material Number: 50118031

An SAP course - use it to learn, reference it for work

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Copyright Copyright © 2013 SAP AG or an SAP affiliate company. 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 Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Apple, App Store, FaceTime, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. Bluetooth is a registered trademark of Bluetooth SIG Inc. Citrix, ICA, Program Neighborhood, MetaFrame now XenApp, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. Edgar Online is a registered trademark of EDGAR Online Inc., an R.R. Donnelley & Sons Company. Facebook, the Facebook and F logo, FB, Face, Poke, Wall, and 32665 are trademarks of Facebook. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik, and Android are trademarks or registered trademarks of Google Inc. HP is a registered trademark of the Hewlett-Packard Development Company L.P. HTML, XML, XHTML, and W3C are trademarks, registered trademarks, or claimed as generic terms by the Massachusetts Institute of Technology (MIT), European Research Consortium for Informatics and Mathematics (ERCIM), or Keio University. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. INTERMEC is a registered trademark of Intermec Technologies Corporation. IOS is a registered trademark of Cisco Systems Inc. The Klout name and logos are trademarks of Klout Inc. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Mozilla and Firefox and their logos are registered trademarks of the Mozilla Foundation.

g201342101942

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Novell and SUSE Linux Enterprise Server are registered trademarks of Novell Inc. OpenText is a registered trademark of OpenText Corporation. Oracle and Java are registered trademarks of Oracle and its affiliates. QR Code is a registered trademark of Denso Wave Incorporated. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry AppWorld are trademarks or registered trademarks of Research in Motion Limited. SAVO is a registered trademark of The Savo Group Ltd. The Skype name is a trademark of Skype or related entities. Twitter and Tweet are trademarks or registered trademarks of Twitter. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Wi-Fi is a registered trademark of Wi-Fi Alliance. SAP, R/3, ABAP, BAPI, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, Sybase, Adaptive Server, Adaptive Server Enterprise, iAnywhere, Sybase 365, SQL Anywhere, Crossgate, B2B 360° and B2B 360° Services, m@gic EDDY, Ariba, the Ariba logo, Quadrem, b-process, Ariba Discovery, SuccessFactors, Execution is the Difference, BizX Mobile Touchbase, It's time to love work again, SuccessFactors Jam and BadAss SaaS, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany or an SAP affiliate company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

Disclaimer These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

g201342101942

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

g201342101942

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

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.

2013/Q1

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.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

v

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

About This Handbook

TADM10_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.

vi

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Contents Course Overview .............................................................................. ix Course Goals................................................................................. ix Course Objectives ............................................................................ x

Unit 1: SAP Portfolio Overview..............................................................1 Unit 2: Navigation ..............................................................................5 Unit 3: The System Core ......................................................................9 Logon Groups in AS ABAP................................................................ 10 Fundamental Concepts of Java........................................................... 19 Java Cluster Architecture .................................................................. 33 The Internal Structure of SAP NetWeaver AS Java.................................... 39

Unit 4: Starting and Stopping SAP Systems ........................................... 51 System Start: Process ..................................................................... 53 System Start: AS ABAP and AS ABAP+Java Process ................................ 60 Overview of the Process for Starting and Stopping an SAP NetWeaver AS Java . 69 Tools for Starting and Stopping SAP Systems.......................................... 78 Tools for Starting and Stopping .......................................................... 100 System Start: AS ABAP Logs............................................................ 121 Java Startup and Control Framework ................................................... 126 Logs of the Start and Stop Processes of SAP NetWeaver AS Java ................ 136 Appendix: Downtime Management ..................................................... 142

Unit 5: Introduction to System Configuration ........................................155 How the System Evaluates Its Parameters ............................................ 157 How to set Profile Parameters ........................................................... 166 Setting up Operation Modes ............................................................. 177 Overview of the Administration Tools ................................................... 194 Basic Configuration of AS Java with the Config Tool ................................. 213 Configuring AS Java with SAP NetWeaver Administrator............................ 241 Further Configuration Activities .......................................................... 247

Unit 6: Software Development in SAP Systems ......................................261 Glossary .......................................................................................265

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

vii

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Contents

TADM10_1

Index ............................................................................................267

viii

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Course Overview Course TADM10 is the foundation for various, further training courses for consultants. After TADM10, you can continue your training either by taking course TADM12 to further expand your knowledge of SAP NetWeaver AS, or by training to become a (Technical) PI or Portal Consultant. This training content is largely independent of the type of operating system and database technology. Like the other TADM courses, TADM10 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 TADM10 is based on content taken from the following courses: 1. 2. 3.

SAPTEC ADM100 ADM800

Week 2 of course TADM10 is based on content taken from the following courses: 1. 2. 3. 4.

SAPTEC ADM100 ADM103 ADM800

Target Audience This course is intended for the following audiences: •

SAP Technology Consultants (Associate Level)

Course Prerequisites Required Knowledge • •

2013/Q1

Basic knowledge of IT Basic knowledge of operating systems and databases

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

ix

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Course Overview

TADM10_1

Course Goals This course will prepare you to: • • •

Work as an Associate Consultant (Junior Consultant) within the SAP technology environment Configure and manage SAP NetWeaver AS ABAP Configure and manage SAP NetWeaver AS Java

Course Objectives After completing this course, you will be able to: •

x

Process basic tasks within the technology environment of SAP systems

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 1 SAP Portfolio Overview Unit Overview Caution: This unit is distributed as a separate training material.

Unit Objectives After completing this unit, you will be able to:

Unit Contents

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit Summary

TADM10_1

Unit Summary You should now be able to:

2

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit Summary

3

TADM10_1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit Summary

4

TADM10_1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 2 Navigation Unit Overview Caution: This unit is distributed as a separate training material.

Unit Objectives After completing this unit, you will be able to:

Unit Contents

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

5

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit Summary

TADM10_1

Unit Summary You should now be able to:

6

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit Summary

7

TADM10_1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit Summary

8

TADM10_1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3 The System Core Unit Overview Caution: Some lessons of this unit are distributed as a separate training material. The trainer will provide you the correct order of these lessons.

Unit Objectives After completing this unit, you will be able to: • • • • • • •

Explain the benefits of logon groups in AS ABAP Set up logon groups in AS ABAP Use basic Java terminology Explain the term Central Services of SAP NetWeaver AS Java Understand and use concepts such as Java instance, ICM, and server Name the most important managers of the SAP NetWeaver AS Name the most important services of the SAP NetWeaver AS

Unit Contents Lesson: Logon Groups in AS ABAP............................................... 10 Exercise 1: Setting Up Logon Groups ........................................ 13 Lesson: Fundamental Concepts of Java ......................................... 19 Lesson: Java Cluster Architecture................................................. 33 Lesson: The Internal Structure of SAP NetWeaver AS Java .................. 39

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

9

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

TADM10_1

Lesson: Logon Groups in AS ABAP Lesson Overview This lesson introduces the concept of logon groups in AS ABAP.

Lesson Objectives After completing this lesson, you will be able to: • •

Explain the benefits of logon groups in AS ABAP Set up logon groups in AS ABAP

Business Example You want to use logon groups to restrict user logons to certain application servers of your system.

Using Logon Groups SAP systems sometimes have significantly more than just one or two instances. Each of these instances offers a specific number of work processes of various types and can access the resources of “your” hardware. Situations are conceivable in which the tasks to be performed on an instance place massive demands on the underlying hardware, thus slowing down all work that is carried out on this instance. Long dialog response times are particularly annoying, since the end users affected by this incur real costs due to poor “system availability”. Examples of such situations would be: • • •

Heavy load due to large numbers of incoming RFC requests Heavy load due to complex background work processes Heavy load due to numerous update tasks

Use of dialog groups to separate the dialog load from other loads • • • •

10

Set up a special logon group to receive RFC requests Set up a special logon group for background tasks Set up update work processes on just a few selected instances Set up a special logon group for dialog tasks

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Logon Groups in AS ABAP

Note that (to use this concept successfully) RFC communication from external systems must reference the specially created logon group. It may be worth setting up a logon group named “RFC” on all your systems, and referencing this logon group for every RFC communication to an SAP system. See also SAP Note 593058: New RFC load balancing procedure. Note: For background tasks, special job server groups are created as a logon group in transaction SM61. Using a logon group to ensure the best possible distribution of dialog load SAP recommends you set up a single logon group for dialog requests if you want your end users to have comparable response times. This logon group is given the name PUBLIC for example. If you think that it is useful, you can decide not to include the central instance of your SAP system in this logon group. By default, every instance of an SAP system (including the central instance) is assigned to the logon group SPACE.

Setting Up Logon Groups Logon groups are set up in transaction SMLG (Tools → CCMS → Configuration → Logon Groups)). Here, you can set up a new logon group and assign the individual instances to this. You can display the current status of the instances under Goto → Load distribution, as well as view which instance the next user is assigned to depending on which logon group is being used. When logging on using a logon group, the ABAP message server is always contacted first in order to identify the instance with the best performance within the selected logon group. The load information is determined by a report on each instance, which is run automatically every five minutes. This report saves the information in a special memory area in the message server, which the SAP GUI can then use to request the best current instances of a group. To avoid the best current instances of the group becoming overloaded with new logons whenever a large number of users attempt to logon within the five minute period, the load information is updated for each instance after every fifth logon.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

11

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

12

TADM10_1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Logon Groups in AS ABAP

Exercise 1: Setting Up Logon Groups Exercise Objectives After completing this exercise, you will be able to: • Set up logon groups

Business Example You want to use logon groups to restrict user logons to certain application servers of your SAP System.

Task: Setting Up Logon Groups Create a logon group. 1.

If not already done. Start in your training environments, the SAP Logon program.

2.

Create a logon group called DIALOG- that includes the Additional Application Server (AAS) instance of your system. Hint: The name of the logon group to DIALOG* indicates that dialog requests should be answered using this logon group.

2013/Q1

3.

Create a new entry for your SAP systems. Use the logon group you created in the previous exercise.

4.

Test the newly created SAP Logon entry and Log on to the System with your user and password.

5.

Check on which instance you are logged on. (Should be the Additional Application Server (AAS) instance).

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

13

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

TADM10_1

Solution 1: Setting Up Logon Groups Task: Setting Up Logon Groups Create a logon group. 1.

If not already done. Start in your training environments, the SAP Logon program. a)

The exact path to the SAP Logon program depends on your environment. A SAP Logon program may be available. • • •

in your classroom on the Common Training WTS on the operating system of your server twdfSSSS.wdf.sap.corp

Continued on next page

14

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Logon Groups in AS ABAP

2.

Create a logon group called DIALOG- that includes the Additional Application Server (AAS) instance of your system. Hint: The name of the logon group to DIALOG* indicates that dialog requests should be answered using this logon group. a)

Log in to your own ECC system using the SAP Logon entry . User: - Password:

b)

Call the transaction SMLG (or Tools → CCMS → Configuration → Logon Groups).

c)

Either select from the menu: Edit → Create assignment or button Create assignment (symbol: white sheet) or the key (F8)

d)

In the resulting window that opens called Create Assignment, enter in field Logon Group the following value: DIALOG-. For example: DIALOG-04

e)

In the field instance choose the F4 help and choose the instance of the Additional Application Server (AAS) named _ _ . The instance number must match to the instance number used in your landscape of the AAS. Hint: In practice, this could now be ALL of your Additional Application Server (AAS) instances for this SAP System.

f)

Press the button Copy

g)

Within the overview screen you should now see in front of the instance name of the AAS also your entry called DIALOG- in the column logon group.

h)

Please confirm your entries pressing the Save button (the disk icon)

i)

Leave the transaction SMLG with the symbol: Green arrow back or F3.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

15

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

3.

TADM10_1

Create a new entry for your SAP systems. Use the logon group you created in the previous exercise. a)

Within SAP Logon, select Connections

b)

Press New (Symbol white piece of Paper).

c)

Press User Specified System (Default) and select Next Hint: Note that in SAP training, SIDs are not unique. This is why you have to enter some system details manually.

d)

As Connection Type, choose Group/Server Selection

e)

As Description, enter any text (e.g.( SAP ECC _Logon Group Own System)

f)

In the field System ID enter the corresponding 3-digit system ID of the system.

g)

In the field message server enter the hostname of the application server on which the message server is running (e.g. twdfSSSS.wdf.sap.corp)

h)

Field SAProuter-String leave blank (unless otherwise specified by the teacher).

i)

In the field Group/Server, enter the Logon group, (for example DIALOG-XX) you created in the previous exercise. (If it does not appear cancel your entry with the button Cancel, wait one to two minutes and try again)

j)

Press the Next button

k)

In the next step called Network settings leave them on the default values and press the button Next.

l)

In the next step Select front-end input… leave them on the default values and press the button Finish

m)

In SAP Logon should now see a new entry, which bears the name of your choice in the Description field. Hint: You can after you insert the Group/Server field directly choose the button finish to speed up.

Continued on next page

16

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Logon Groups in AS ABAP

4.

5.

2013/Q1

Test the newly created SAP Logon entry and Log on to the System with your user and password. a)

Test the newly created SAP Logon entries in which you double-click it or select the entry and press the button Log on

b)

If you see a login screen, a dispatcher could be reached with these settings. If this is not the case, and you get an error message, check the SAP logon entry for this system.

c)

Check on the login screen at the bottom right, if the system identifier (SID) appears which you have entered in the previous exercise in the field description.

d)

In the Client field, can be the default value. In the field User enter your user -. In the Password field enter your production password. The field Logon Language you left at the default value. Press the Enter or use the icon on the top left (green check mark)

Check on which instance you are logged on. (Should be the Additional Application Server (AAS) instance). a)

Select from the top menu in the SAP System→ Status.

b)

Within the window: System: Status check the Server Name field. This panel displays the following information (syntax: ] _ _ . The last two digits should match the instance number of this system, which identifies the instance of Additional Application Server (AAS) (e.g. 01). If this is not the case, verify your SAP Logon entry, or check with the transaction SMLG if your logon group points to the correct instance.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

17

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

TADM10_1

Lesson Summary You should now be able to: • Explain the benefits of logon groups in AS ABAP • Set up logon groups in AS ABAP

Related Information • • • • • • •

18

SAP Note 51789: Poor user distribution in logon distribution SAP Note 64015: Description of test program lgtst SAP Note 113440: Default logon group 'SPACE' for load balancing SAP Note 118093: Concepts of defining 'limits' in logon load balancing SAP Note 888279: Regulating / distributing the workflow load SAP Note 986373: RFC load distribution SAP Note 593058: New RFC load balancing procedure

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Fundamental Concepts of Java

Lesson: Fundamental Concepts of Java Lesson Overview This lesson provides a short overview of the fundamental Java concepts for all participants that have not yet been confronted with Java. The architectural concept and the properties of Java are briefly outlined.

Lesson Objectives After completing this lesson, you will be able to: •

Use basic Java terminology

Business Example As of SAP Web Application Server 6.20, you have the option of using Java as well as the ABAP programming language. You should therefore familiarize yourself with the fundamental concepts of the Java environment.

Introduction If you search for the meaning of the word Java in an encyclopedia, you find the following definitions, among other things: • • • • •

One of the four main islands of the Indonesian republic in the Indian Ocean. A programming language developed by the company Sun Microsystems. An aromatic type of coffee, particularly used to make espresso. A popular dance of the 1920s. A coarse, loose mesh canvas for embroidery, made of linen or cotton.

It would undoubtedly be worthwhile to investigate each of these definitions individually in more detail. In this course, we want to concentrate exclusively on the second definition in this list. The Java programming language was first introduced in 1995 by Sun Microsystems Inc.™. Java is an object-oriented and platform-independent programming language that has spread across many areas. The powerful concept of Java allows the development of a large number of different types of application - from the classic application using applets implemented in Web pages to client/server applications. Java has been designed to be platform independent. This means that the same Java program can be executed on any system for which a Java Runtime Environment (JRE) is available. In particular, Java applications can run on different systems that

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

19

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

TADM10_1

are based on different hardware. Java can be used to create programs for UNIX, Microsoft Windows, Linux, MacOS, or OS/2, for workstations or servers; for x86, MIPS, Alpha, or Sparc; for computers, organizers, or cell phones, and for the micro computers built into household and industry devices, such as washing machines, video recorders, cars, and traffic lights.

Properties of Java You need to differentiate between two basic types of Java programs: applications and applets. •

Applications Java applications are computer programs with the full functional range also provided by other programming languages. Applications can run as local programs on the user's computer or as client/server systems across the Internet or using an Intranet, or as server programs (servlets, CGI programs) on a Web server.

•

Applets The term applet essentially means "little application". It usually means a Java applet, a small computer program that runs in a Web browser and is written in the Java programming language. Java applets are intended for execution within the Java Runtime Environment of a browser. They are transferred (as is also the case, for example, with embedded images) with the HTML page using the HTTP protocol, and then executed on the client computer. Special security guidelines apply to Java applets; that is, they are not permitted to perform everything on the client that locally-installed programs are permitted to. In this way, for example, they can only create network connections to the host from which they were downloaded. Hint: You need to be careful when using the name “Java”. Not everything that has Java as its linguistic root is actually connected to Java; JavaScript is completely unrelated to Java. JavaScript is a script language that can be embedded in HTML and, with some Web browsers (Netscape, Microsoft Internet Explorer), produces the execution of certain functions and actions within the Web browser. JavaScript was developed with the intention of dynamically organizing static HTML pages. Unlike server-side script languages such as Perl or PHP, JavaScript is executed on the client. In contrast to Java, JavaScript is not an independent programming language, is not independent of the browser version, and does not have the required security mechanisms.

20

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Fundamental Concepts of Java

Initially, Java is a programming language like any other. Unlike traditional compilers for a programming language, which generate machine code for a specific platform (see the Compiled Programming Languages figure), the Java compiler produces program code for a virtual machine (the Java Virtual Machine). This is known as bytecode. A virtual machine is a model of a processor (which often does not exist as real hardware) and the associated system architecture. It is a computer program that emulates a processor. The effort required to transfer this software to other real CPUs is small in comparison. The virtual machine is therefore viewed as the interface between Java and the actual hardware. It must therefore be developed for each processor architecture and, as such, is the only platform-dependent component of a Java development system (see the figure Concept of the Java Virtual Machine). SAP also uses the concept of a cross-platform virtual machine in the ABAP world. The ABAP programs of the SAP system are also converted into a bytecode, which is interpreted by the ABAP Virtual Machine, the ABAP work process.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

21

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

TADM10_1

Figure 1: Compiled Programming Languages

Hint: Virtual machines play an important role nowadays, since Microsoft has followed Sun's example of the Java Virtual Machine (Java VM) with its .NET architecture. The concept of the virtual machine was already in use in the late 1960s; Martin Richards' O code for the BCPL programming language is an early example. Better-known examples are the Pascal P code system (UCSD Pascal) from the 1970s, and the virtual machine on which programs in the Smalltalk programming language run. The bytecode generated by the Java compiler is comparable to microprocessor code for a conceived processor , which understands instructions such as arithmetic operations, gotos, and so on. A Java compiler, such as the one from Sun, which is itself implemented in Java, generates this bytecode. However, so that the program code of the virtual processor can be executed, after the conversion phase, the runtime environment (also known as the runtime interpreter), the Java Virtual Machine, runs the bytecode. In this way, Java is a compiled, but also an interpreted programming language.

22

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Fundamental Concepts of Java

Figure 2: Concept of the Java Virtual Machine

The interpretation causes speed problems, since the identification, decoding, and execution of the commands takes time. Java programs are generally slower than programs that were converted specifically for the target environment (such as C(++) programs). The technology of the Just In Time (JIT) compiler alleviates the problem. A JIT compiler accelerates the execution of the programs by converting the program statements of the virtual machine for the physical machine. There is then a program adjusted for the architecture available in memory, which is executed quickly without interpretation. Even with this technology, the speed is slower than that of C in many cases, but the difference is smaller. A Java Development Kit (JDK) is required to write platform-independent Java programs. The Java Development Kit includes the software required to create and test Java applications and applets, the packages with the Java classes that are part of the basic configuration, and the online documentation. The software includes the Java compiler, the Java Runtime Environment (the Java Virtual Machine) for running applications, the applet viewer for running applets, a Java debugger, and various utilities. The online documentation describes all language elements and all classes of the Application Program Interface API. Java is a relatively new programming language and is therefore still in development, that is, new versions with extensions and improvements are constantly being released: the original version is JDK 1.0 (1995). Since Version 1.2, the JDK has also been called “Java Platform 2” and in Version 1.3.0 to Version 1.4, the JDK is called “Java 2

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

23

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

TADM10_1

Software Development Kit (SDK)”. It is called JDK again from Version 1.5.0 and SDK is used in another context. From Version 1.6.0, Java™ Platform 2 is no longer used, rather Java™ Platform is used. From Version 1.5.0, there is a differentiation between a developer version and a product version with 1.5.0 as the developer version. The related product version is “5.0”. Product version “6” belongs to developer version 1.6.0. •

•

•

Java Standard Edition (Java SE). The standard edition is the normal software environment and defines the Java™ SE Development Kit (JDK). This includes the Java SE Runtime Environment (JRE). Java Enterprise Edition (Java EE). The enterprise edition builds on the JDK and integrates additional packages such as Enterprise JavaBeans (EJB), servlets, JavaServer Pages (JSP), Java Mail API, and Java Transaction Service (JTS). The Java EE SDK (Software Development Kit) includes the Sun Java System Application Server and requires a JDK. Java Micro Edition (Java ME). The micro edition is a small runtime environment for small devices such as Personal Digital Assistants (PDAs) or telephones.

The following figure “SDK Structure” describes the interaction between the terms “Java EE SDK”, “JDK” and “JRE”.

Figure 3: SDK Structure

24

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Fundamental Concepts of Java

The Java SE Runtime Environment is also referred to as JRE and contains the runtime environment to which the JVM and other libraries with which Java applications can be executed belong. The JRE cannot be used to develop any Java programs. The JDK is required for this. It contains the JRE with the Java compiler “javac” and other tools which are of use for programming. When performing client-server programming, you need a server. The SDK contains the reference implementation of an application server, namely the “Sun Java System Application Server”. You can use the Java EE SDK to program, among other things, “Enterprise Java Beans”, “Servlet”s and “JSP”; however, a JDK is required.

Figure 4: AS Java with SAP JVM

SAP NetWeaver AS Java is the SAP implementation for a Java-based application server. SAP NetWeaver AS Java 7.3x is Java™ EE 6-compliant and was the first (along with Sun) to correspond to this standard. SAP NetWeaver AS Java 7.3x does not require a JDK from the operating system manufacturer (unlike its predecessors); instead, the SAP-specific JDK is used on all operating systems.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

25

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

TADM10_1

The SAP Java Virtual Machine (JVM) is a Java Virtual Machine for application servers that are reliable, scalable and can be supported for using SAP products. The SAP JVM implements the standard Java SE 5.0 and provides a reliable foundation for SAP NetWeaver AS Java. Some of the SAP JVM properties were developed especially to meet the requirements of SAP customers: •

Additional “Supportability” The SAP JVM provides functions for supporting complex Java applications. One prominent function here is the “extended stack trace”. It helps developers to identify problems and software errors.

•

“Profiling” and “Memory Debugging” Discovering problems in memory management has the same value as identifying functional errors. Therefore, the SAP JVM provides enhanced options in the area of performance and memory profiling.

•

“Debugging on demand” You can use the SAP JVM in productive use to switch to and back from debugging mode without restarting the VM. This dramatically reduces the amount of effort required for troubleshooting.

For details of available SAP JVM patches, see SAP Note 1434916: How to find out the SAP JVM build version.

Programming in Java When creating Java programs, the developer first creates a source file in the format “MyProgram.java” (see the figure Tools of the Java Development Kit). The Java compiler generates a separate file for each class from the source file that contains the bytecode for this class. The file name is then the name of the class with the extension “.class”, and therefore has the format “MyProgram.class”. In accordance with the object-oriented approach, Java “functions” are grouped in classes. Each Java source file may only contain one public class. The file name of the source file must then be the name of this class (which is case-sensitive) with the extension “.java”. This bytecode is platform-independent: irrespective of the type of system on which the Java compiler was called, the bytecode can also be executed on any other computer system, at least in the case of “100% pure Java”, which unfortunately cannot be guaranteed for all products.

26

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Fundamental Concepts of Java

Figure 5: JDK tools

You can also combine multiple class files into a compressed archive file. Java archive files of this type then have, for example, names in the format “MyArchive.jar”. A Java archive contains files and possibly also entire directory structures in the same compressed format used by PKZIP and WinZip. They are administered with the program jar (Java Archiver); the call is similar to that of the UNIX program tar (tape archiver). It is not usually necessary to extract or unpack archive files: The Java compiler and the Java Virtual Machine can read and load the class files directly from the archive files. For this purpose, the file name of the archive file must be specified in a defined format. The bytecode of a Java application is executed by calling the Java Virtual Machine JVM (in the Java Runtime Environment JRE) in the format java MyProgram. In a similar way to sub program libraries in other programming languages, in Java there are also small Java programs (classes) with precisely defined conventions for the interfaces that allow reuse in multiple applications (applications and applets). These programs are known as Java Beans.

Java EE Specification Java became popular with the Internet as a language of the World Wide Web. Life can be added to static HTML pages using Applets and Java Script. By extending Web servers with the Common Gateway Interface (CGI), these can perform simple database accesses and display the results formatted in the browser. However, these technologies are limited in the case of simultaneous accesses from very large numbers of users who expect reliable information and quick response times. Sun provides a solution to these problems in terms of server-side architecture for Internet applications with the Java Platform Enterprise Edition (Java EE). Java EE is a vendor standard for a complete palette of software components, which are

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

27

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

TADM10_1

primarily created in the Java programming language. Sun wishes to ensure that developments comply with the specification of the Java Enterprise Edition using compatibility tests for Java EE. The purpose of the specifications is to make available a generally accepted framework for developing distributed, multilayer applications with modular components. Clearly defined interfaces between the components and layers ensure that software components from different vendors are interoperable, provided they adhere to the specifications. With the Java EE specification, Sun wishes to ensure that Web applications that conform to the specification run on all Java EE-compatible servers. The application logic is packed in components (Enterprise Java Beans) in accordance with the Java EE specifications. They represent modular java program components. A container provides the components implicitly with the services of the runtime environment. Three-level client/server architectures for enterprise applications can be realized in accordance with the Java EE specifications. The Java EE application server forms the core of these architectures (see the figure Three-Level Java(TM) EE Architecture).

Figure 6: Three-Level Java(TM) EE Architecture

The Java EE application server processes client requests, executes the application logic, and returns the results to the clients. The application data is accessed from the database level. The application logic is implemented in the form of Enterprise

28

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Fundamental Concepts of Java

Java Beans. These are executed in an EJB Container, which is part of the Java EE Application Server. The communication between the client and the Java EE is based on Web standards such as HTTP, HTML, and XML. The Java EE server uses Java Server Pages (JSP) and Java Servlets to generate HTML pages or XML data. Java Server Pages and Java servlets are executed in a Web Container, which is, in turn, part of the Java EE Application Server. Java applets can be included in the HTML pages that are sent to the Web browser. These applets are executed in the browser. Java Server Pages (JSP) are a technology developed by Sun, which essentially allow the simple dynamic generation of HTML and XML output for a Web server. This technology enables Java code and specific JSP actions to be embedded in static content. The advantage of this technology is that the logic can be implemented independent of the design. JSP are converted Java source code using a special JSP compiler. This source code, which corresponds to a Java servlet, is then converted to bytecode by the Java compiler.

Figure 7: Architecture of the Java(TM) EE Application Server

Each application component is executed in a container. These containers provide the application components with services in accordance with the Java EE specification. Examples of these services are transaction management, availability, security, scalability, client connection, and database access. This means that the developer can concentrate purely on the application logic and does not need to deal with these system functions. The following figure shows an example of the processing of a client request by a Java EE Server.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

29

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

TADM10_1

Figure 8: Processing of a Client Request by the Java™ EE 6 Server

To achieve the aims of quick response times and reliable information, the Java EE application server must also provide scalability and reliability in addition to the functional side. The Java EE Server must handle clustering and load balancing for this.

Java EE Server in the SAP Environment SAP takes into account the increasing importance of Java for creating business applications, together with the larger market of Java developers. SAP began a fundamental evaluation of Java as early as 1998 and, since SAP Web Application Server 6.20, provides a complete Java EE-compatible runtime infrastructure. Up to Release SAP NetWeaver AS Java 7.0, they were AS Java J2EE 1.3-compliant; since AS Java 7.1x, they are EE 5-compliant, since AS Java 7.3x they are EE 6-complient. The architecture of an application server in accordance with the Java EE specification is similar to the ABAP runtime environment used for SAP solutions, since both are platform-independent, executed in a multi-level architecture, and have a separate presentation logic and business logic.

30

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Fundamental Concepts of Java

The use of Java EE in SAP technology has the following advantages for SAP NetWeaver Application Server: • • • • •

2013/Q1

The open integration architecture SAP NetWeaver integrates perfectly into the openness of Java EE. Java EE is further proof of the strategy of platform-independence pursued by SAP. The Java EE Connector architecture allows standardized integration of external applications. Web Services technologies are supported directly by Java. The quickly-growing Java community provides simple access to experienced developers.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

31

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

TADM10_1

Lesson Summary You should now be able to: • Use basic Java terminology

32

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Java Cluster Architecture

Lesson: Java Cluster Architecture Lesson Overview This lesson describes the architecture of SAP NetWeaver AS Java. The individual components of SAP NetWeaver AS Java and their functions are introduced. A Java cluster encompasses all Java components of an SAP system.

Lesson Objectives After completing this lesson, you will be able to: • •

Explain the term Central Services of SAP NetWeaver AS Java Understand and use concepts such as Java instance, ICM, and server

Business Example After the installation of a SAP NetWeaver Application Server Java, configuration is still required. You should therefore be familiar with the basic architecture of the cluster of SAP NetWeaver Application Server Java.

The Java Instance Concept SAP NetWeaver Application Server Java takes the instance concept of SAP Basis, which combines multiple components that are monitored, started, and stopped together into an administrative unit. The following components are part of a Java instance: • •

The server processes provide the infrastructure in which the Java™ EE 6 applications run. The Internet Communication Manager distributes the client requests to the free server processes of the instance.

An instance always runs on one physical server, but there can be multiple instances on one server. Within an SAP system, an instance is defined using the system ID (SID) of the SAP system and the instance number. An SAP system consists of a database and one or more instances. These instances can either be purely ABAP or Java instances, or instances with ABAP and Java infrastructure, with the instances of a system always having the same infrastructure (that is, there is no system that has ABAP instances (without Java) and Java instances (without ABAP).

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

33

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

TADM10_1

The Central Services form a special Java instance. They provide the basis of communication and synchronization within a Java cluster. Another special instance is the instance that is installed first. It is often referred to as the Primary Application Server Instance or PAS for short. Further instances for a system are referred to as Additional Application Server Instances or AAS for short. To ensure high-performance when processing Java requests, the SAP system can be scaled using the number of server processes for each instances or using the number of instances.

Java Cluster Architecture All Java components of an SAP system are known as a Java cluster. A Java cluster consists of: • • • •

A Java instance with an ICM and at least one server process. The Central Services, which contain a message server and an enqueue server. A database for the central storage of data. Optionally, additional Java instances

The following figures illustrate an installation with several SAP NetWeaver AS Java instances.

34

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Java Cluster Architecture

Figure 9: Cluster with Multiple SAP NetWeaver AS Java Instances

ICM and Server Processes Client requests to SAP NetWeaver AS Java are received by ICM. It selects a free server process to process the request and creates the connection between the client and the server process. The ICM distributes new incoming requests to the available server processes using a “round robin” algorithm. If a connection to the client exists, the request is forwarded to the server process that is already processing requests for this client. The server process of the SAP NetWeaver Application Server Java runs the Java applications. The server processes are implemented as multi-threaded servers and can therefore process multiple requests in parallel. The system or application threads take over the processing of the requests.

Central Services The Central Services run on one host and form a separate Java instance. They consist of the Java message server and the Java enqueue server.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

35

Unit 3: The System Core

TADM10_1

The Central Services provide the basis for communication and synchronization for the Java cluster: •

•

The message service administers a list of the ICM and the server processes of the Java cluster. It represents the infrastructure for data exchange (small datasets only) between the participating nodes. In the case of load balancing between a large number of Java instances, it also provides the load balancing information for the SAP Web Dispatcher. The enqueue service administers logical locks that are set in a server process by the executed application program. It is also used for cluster-wide synchronization.

The Central Services are essentially required when a Java cluster is installed. They are started on a host with a separate system number and the system ID (SID) of the entire system.

Message Service The message service is an individual program used to communicate between the elements of a Java cluster. The message service knows all active Java instances. The terms message server and message service are used with the same meaning in the training material. To be precise, the message server is a program/process that provides the message service. The message service performs the following tasks in the Java cluster: •

• • • • •

Notification of events that arise in the cluster, for example, if a node of the cluster disappears (due to failure or the instance being shut down), or when a service is started or stopped. Communication between different services Forwarding of messages and requests to all participants (broadcast) Prepare logon information for the SAP Web Dispatcher Guaranteed message transmission Exchange of cache information in the cluster

The same technology is used as with the SAP Message Server for the earlier SAP NetWeaver AS versions without Java.

Enqueue Service The enqueue service runs on the Central Services instance of the Java cluster. It manages the lock table in the main memory and receives requests for setting or releasing locks. It uses the tried and tested SAP lock concept.

36

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Java Cluster Architecture

The terms enqueue server and enqueue service are used with the same meaning in the training material. To be precise, the enqueue server is the program or process that provides the enqueue service. The enqueue service has the following tasks: • •

2013/Q1

Internally, it is used for synchronization within the Java cluster The applications can lock objects are release locks again. The enqueue service processes these requests and manages the lock table with the existing locks.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

37

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

TADM10_1

Lesson Summary You should now be able to: • Explain the term Central Services of SAP NetWeaver AS Java • Understand and use concepts such as Java instance, ICM, and server

38

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: The Internal Structure of SAP NetWeaver AS Java

Lesson: The Internal Structure of SAP NetWeaver AS Java Lesson Overview This lesson introduces the internal architecture of SAP NetWeaver AS. This architecture is the foundation for realizing a Java™ EE 6 application server in accordance with the Java™ EE 6 specification.

Lesson Objectives After completing this lesson, you will be able to: • •

Name the most important managers of the SAP NetWeaver AS Name the most important services of the SAP NetWeaver AS

Business Example SAP NetWeaver AS Java consists internally of several managers and services. To be able to configure these managers and services, you should first understand their significance and functions.

Introduction The internal structure of SAP NetWeaver AS Java is divided into three logical levels (see the figure Internal Structure of SAP NetWeaver AS Java): •

• •

2013/Q1

SAP Java Enterprise Runtime - provides fundamental functions of the runtime environment, such as class loading, cluster communication, management of configuration data, and so on . AS Java System Components - contain interfaces, libraries, services and facades. Applications Layer - relates to the applications that are deployed and run in SAP NetWeaver Application Server Java.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

39

Unit 3: The System Core

TADM10_1

Figure 10: Internal Structure of SAP NetWeaver AS Java

The following general rule applies to the interaction between these three logical entities in SAP NetWeaver AS Java: higher-level components can use the functions of the lower-level layers. On the other hand, the lower levels are not aware of the higher levels and cannot therefore use their functions. This rule is a consequence of the start sequence of the individual modules of the system. First, the runtime environment is started, then the services are started, and then the applications are started. Communication between the individual components takes place using defined Application Programming Interfaces (APIs). The components of the higher levels use these APIs to use functions of the lower levels. The AS Java System components use the Framework APIs to talk to the SAP Java Enterprise Runtime. The applications can talk with the AS Java System components either using APIs defined by the Java™ EE 6 specifications, or using proprietary SAP APIs. The functions of these logical levels and their interaction are described in the following.

40

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: The Internal Structure of SAP NetWeaver AS Java

SAP Java Enterprise Runtime The SAP Java Enterprise Runtime provides the core functions of the system. These core functions are realized by multiple subsystems of the lowest level. These subsystems are called managers. A selection of these managers with a short description is listed below: •

Log Manager: manages the process of logging system events. It configures the logging routines of the kernel. The Log Manager is the first manager that is started during the startup of SAP NetWeaver Application Server Java.

•

Application Thread Manager: manages inbound client requests. Searches for free threads to process inbound requests. If no threads are free, the requests are buffered in a request queue.

•

Thread Manager: manages threads in which internal operations of SAP NetWeaver AS Java are executed.

•

Locking Manager: Represents the interface between the server process and the enqueue service.

•

Configuration Manager: Allows SAP NetWeaver AS Java to store and access data in a relational database. Uses the Open SQL for Java Framework to do this.

•

Classloading Manager: Central location for the registration and removal of loaders and references between them.

•

Cluster Manager: Manages the elements of a cluster (server processes) and is responsible for the communication in the cluster. It updates information about the status of the individual elements of a cluster and the services that are provided by it. Important settings:

•

– element.joinPort: Port with which servers listen for inbound connections. – ms.host: Host on which the Java message server runs. Service Manager Represents a container in which all services in the cluster are executed.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

41

Unit 3: The System Core

TADM10_1

AS Java System Components The AS Java System components form the second level within the three-level structure of SAP NetWeaver AS Java. They provide the complete infrastructure for executing Java™ EE 6 applications and proprietary SAP applications. Four types of AS Java System components can be classified: •

Interfaces: Agreements that define how different components of SAP NetWeaver AS Java work together. They do not provide any runtime functions themselves, but rather are used by services that provide their implementation.

•

Libraries: They provide names, classes, and objects within SAP NetWeaver AS Java. These objects are created by the system when it loads the library, or when an object is first requested.

•

Services: The services that SAP NetWeaver AS Java provides for processing requests are defined and configured using the Services. Service components can access and utilize functions of the runtime environment through the Framework API. They are the most important of these four types of AS Java System components.

•

Facades: The facades are special APIs that the Java EE API and SAP API use to access libraries, interfaces and services.

42

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: The Internal Structure of SAP NetWeaver AS Java

A selection of the most important services with a short description is listed below: •

Security Provider: Administration of users and groups and authorization administration. Controls access to resources or applications deployed in SAP NetWeaver AS Java.

•

Monitoring Service: Allows access to information about the current system status. Provides general and statistical information, among other things, about the nodes in the cluster, memory utilization, performance, applications, and user connections.

•

Log Configurator service Manages the configuration of the logging and tracing mechanism of SAP NetWeaver AS Java.

•

Deploy Service: Manages the deployment of Java applications.

•

EJB Container Service: Manages all Enterprise Java Beans (session beans, entity beans, and message-driven beans), which are executed in the EJB Container of SAP NetWeaver AS Java.

•

HTTP Provider: Is responsible for processing HTTP requests.

Applications Layer The applications form the third level within the architecture of SAP NetWeaver AS Java. The boundary between the applications and the AS Java System components is defined by the Java EE APIs and a few proprietary SAP APIs. Applications use these APIs to utilize the functions of the AS Java System components.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

43

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 3: The System Core

TADM10_1

An enterprise application can contain different types of application components: •

•

•

•

Servlet: A program module written in the Java programming language, which is used to respond to requests to a Web server in such a way that the content of the returned HTML Web page is dynamically generated. Servlets are standardized in the context of the Java™ EE 6 specification. Java Server Pages (JSP): Technology for dynamically generating HTML and XML output of a Web server. This technology enables Java code and specific JSP actions to be embedded in static content. The advantage of this technology is that the logic can be implemented independent of the design. Java Server Pages are converted to Java source code, which corresponds to a Java servlet, using a special JSP compiler. Enterprise Java Beans (EJB): Used for the standardized, simplified development of business applications using Java. They are part of the central elements of the Java™ EE 6 specification. Java Database Connectivity (JDBC): Uniform interface to databases from different vendors, defined specifically for relational databases. The tasks of JDBC include creating and managing database connections, forwarding SQL queries to the database, and converting the results into a format that is usable for Java and making them available to the program.

These components reside in different containers of SAP NetWeaver AS Java (see the figure Containers of SAP NetWeaver AS Java). The containers provide runtime services for the application components.

44

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: The Internal Structure of SAP NetWeaver AS Java

Lesson Summary You should now be able to: • Name the most important managers of the SAP NetWeaver AS • Name the most important services of the SAP NetWeaver AS

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

45

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit Summary

TADM10_1

Unit Summary You should now be able to: • Explain the benefits of logon groups in AS ABAP • Set up logon groups in AS ABAP • Use basic Java terminology • Explain the term Central Services of SAP NetWeaver AS Java • Understand and use concepts such as Java instance, ICM, and server • Name the most important managers of the SAP NetWeaver AS • Name the most important services of the SAP NetWeaver AS

46

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Test Your Knowledge

Test Your Knowledge 1.

Which of the programming languages listed below are implemented platform-independently? Choose the correct answer(s).

□ □ □ □ 2.

2013/Q1

A B C D

Fortran ABAP Java C/C++

Briefly describe the function of the Java Virtual Machine (JVM).

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

47

Test Your Knowledge

TADM10_1

Answers 1.

Which of the programming languages listed below are implemented platform-independently? Answer: B, C ABAP and Java are programming languages that are implemented platform-independently.

2.

Briefly describe the function of the Java Virtual Machine (JVM). Answer: The JVM executes the platform-independent bytecode generated by the Java compiler on the relevant hardware.

48

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit Summary

49

TADM10_1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit Summary

50

TADM10_1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4 Starting and Stopping SAP Systems Unit Overview The topic of this lesson is the starting and stopping of an SAP system. These are two of the basic tasks of system administration. You will also learn about the available log and trace options, to be able to react correctly if an error occurs.

Unit Objectives After completing this unit, you will be able to: • • • • • • • • • • • • • • • •

2013/Q1

Describe the process of the start procedure of an SAP system Describe the structure of the file system for SAP instances Describe the general start process for an SAP NetWeaver AS ABAP. Describe the general start process for an SAP NetWeaver AS ABAP+Java. Describe which profiles are evaluated. Describe the sequence in which the components of an SAP system and started and stopped Describe the general start process for an SAP NetWeaver AS Java Describe the general start process for an SAP NetWeaver AS ABAP + Java Operate the tools to start and stop an SAP NetWeaver AS ABAP Operate the tools to start and stop SAP NetWeaver AS ABAP + Java Operate the tools to start and stop SAP NetWeaver AS Java Use the AS ABAP start logs to analyze problems Use the term Startup and Control Framework Describe the individual steps during the start and stop processes of a Java instance Find the storage locations of trace and log files of the Startup and Control Framework. Name the most important trace and log files of the Startup and Control Framework and review their content.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

51

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

•

TADM10_1

Plan and schedule downtimes in your SAP Systems using the SAP Solution Manager.

Unit Contents Lesson: System Start: Process .................................................... 53 Lesson: System Start: AS ABAP and AS ABAP+Java Process............... 60 Lesson: Overview of the Process for Starting and Stopping an SAP NetWeaver AS Java ................................................................. 69 Lesson: Tools for Starting and Stopping SAP Systems......................... 78 Exercise 2: Starting and Stopping the SAP System ........................ 93 Lesson: Tools for Starting and Stopping ......................................... 100 Exercise 3: Tools for Starting and Stopping................................. 115 Lesson: System Start: AS ABAP Logs .......................................... 121 Lesson: Java Startup and Control Framework.................................. 126 Exercise 4: Java Startup and Control Framework ......................... 133 Lesson: Logs of the Start and Stop Processes of SAP NetWeaver AS Java 136 Exercise 5: Logs of the Start and Stop Processes of SAP NetWeaver AS Java .............................................................................. 139 Lesson: Appendix: Downtime Management .................................... 142

52

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: System Start: Process

Lesson: System Start: Process Lesson Overview This lesson provides a general overview of how to start and stop SAP systems. It will discuss the areas of the file system that contain the important data for starting instances.

Lesson Objectives After completing this lesson, you will be able to: • •

Describe the process of the start procedure of an SAP system Describe the structure of the file system for SAP instances

Business Example As the administrator of SAP systems, you need to stop the systems for maintenance purposes or after changing system parameters, and then restart them.

Start Process of the SAP System The starting of an SAP system is the basic prerequisite for being able to work with the system. Restarts of SAP systems are also required after maintenance work on the hardware in use and changes to the SAP system's profile. Starting an SAP system is an initial process with which every administrator should be familiar. The start process covered in this lesson describes the process for starting an SAP system. Every SAP system has a database and at least one instance. An SAP system with a Java stack also has a Central Services instance. A system with an ABAP stack can contain an ABAP Central Services instance that provides the ABAP enqueue service and the ABAP message server. In this case, the PAS instance does not have an enqueue work process or a message server. An SAP system with an ABAP and Java stack can therefore have two Central Services instances: one for Java, and one for ABAP. The figure Start Process of an SAP System shows the start process of an SAP system. If the SAP system has an ABAP Central Services instance or a (Java) Central Services instance, these are started first.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

53

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Figure 11: Start Process of an SAP System

Then the PAS instance is started. The PAS instance requires a running database (as do the ASS instances). If the database has not yet been started, this is started first during the start process of the PAS instance. The database can also be started before the actual SAP system is started or with SAP MC via SAP Host Agent. The start sequence will be explained in more detail below. The instances of SAP systems can be divided into three different categories with different priorities for the start and stop process. 1. 2. 3.

Instances with enqueue but without ABAP dispatcher Instances with enqueue and with ABAP dispatcher All other instances

The enqueue process, which occurs on only one instance for each ABAP/Java stack, plays a special role in the start sequence. These instances, which normally also include the message server, must be started before all other instances. The (Java) Central Services instance or an ABAP Central Services instance (priority 1) do not require a running database, which is why the database is not started when either of these instances is started. PAS instances with an ABAP dispatcher and an enqueue work process (priority 2) as well as AAS instances (priority 3) require a started database

54

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: System Start: Process

that the ABAP work processes or the Java server processes log on to. Therefore, the first step is to start the database when starting this type of instance (unless it is already running and installed on the computer on which the PAS- and AAS instance is installed.). If the SAP system has an ABAP Central Services instance, then this system does not contain a Priority 2 instance. Fundamentally, the start process is performed in multiple steps. The start process is triggered with the operating system user adm: •

Starting the Central Services instance(s) The (Java) Central Services consist of the Java message server and the Java enqueue server, and the ABAP Central Services provide the ABAP message server and the ABAP enqueue server.

•

Starting the database The underlying element of the entire SAP system is the database. This must be in an operational state before starting SAP instances that provide ABAP work processes or Java server processes. However, it may not run or be started before the Central Services instance is started. When a PAS or AAS instance is started, the system checks whether the database is running when the start process is triggered, and starts it if necessary.

•

Starting the PAS instance In an AS ABAP or ABAP+Java system, the PAS instance has priority 2 if there is no ABAP Central Services instance and the instance has an enqueue work process; otherwise the PAS instance has priority 3 just like the AAS instances. A PAS instance with priority 2 is started before the AAS instances, while a PAS instance with priority 3 is started at the same time as the AAS instances. In an AS Java system, the PAS instance always has priority 3, and is always started with the AAS instances.

•

Starting the AAS instance(s) If the PAS instance has priority 3, the AAS instances are started at the same time as the PAS instance. If the PAS instance has priority 2, the AAS instances are started once the PAS instance start process has finished.

Stop Process An SAP system is stopped in the opposite sequence. The instances with enqueue are always stopped last.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

55

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Evaluating the Profiles in the Start Process Each instance of an SAP system requires data in the file system. This includes data that all instances can access (globally), and data that can only be accessed by an instance individually. In the file system, the data for the instances is contained in the usr/sap directory, where it is further organized into subdirectories. The figure Structure of the File System of an AS ABAP+Java (simplified) shows this structure. The structure of an AS ABAP system differs the fact that the j2ee directories are missing in the instance directories and no SCS directory exists. Hint: The business data and similar data is contained in the database, which has its own structures in the file system depending on the database manufacturer. This data is not contained in the usr/sap directory.

Figure 12: Structure of the File System of an AS ABAP+Java (simplified)

The directory contains all data that must only be accessed by this SAP system. The data for the PAS instance of an SAP system with an ABAP stack is located in the DVEBMGS directory (where is the instance number). This directory includes other directories such as work, which contains the logs of the start process for example, the j2ee directory, which contains data about the Java nodes and other information, and the exe directory, which contains the kernel. The kernel directory includes the programs that are started when the system is started. The

56

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: System Start: Process

directories of the AAS instances for a SAP system with an ABAP stack have the name D and have the same structure as the PAS instance. The directory SCS is for the Central Services instance of an SAP system with a Java stack. Usually, the PAS instance and all AAS instances are located on separate hosts. This means each AAS instance also has its own directory. If several AAS instances are installed on one host, these have different instance numbers. The SYS directory contains data that can be accessed by all instances: On Windows operating systems, it is usually located in the file system in which the PAS instance is located. On other operating systems, the SYS directory is located in its own file system with the name sapmnt. On Windows operating systems, “share” is created on the sap directory above SYS with the name sapmnt. This Share allows all instances to access the SYS directory. On other operating systems, a SYS directory is created in the file system of each instance, which contains links to the subdirectories of the sapmnt file system. The SYS directory contains the following subdirectories in particular: global contains global data profile contains the default profile and the start and instance profiles exe contains the kernel. During the start process of an instance, the kernel of the global exe directory is replicated to the local exe directory of the respective instance with the sapcpe program. On a Windows operating system, the exe directory also contains the subdirectory, which itself contains the subdirectory. is uc for Unicode, and nuc for non-Unicode. For an AS ABAP+Java system running on a Windows operating system in which the ABAP stack is non-Unicode (the Java stack is always Unicode), this means the exe directory contains the two subdirectories nuc and uc. As of Basis release 7.11, operating systems other than Windows have an identical structure to the Windows operating systems listed above. For SAP NetWeaver 7.0 systems running on operating systems other than Windows, the kernel is contained in the global exe directory. An AS ABAP+Java system with a non-Unicode ABAP stack is an exception. In this case, the non-Unicode kernel is still located in the global exe directory. There is also a uc subdirectory, in which the Unicode kernel is located in the subdirectory. The sapstartsrv program reads the start profile or instance profile at the beginning. Hint: From Release SAP NetWeaver AS 7.1x the entries for the starting procedure are integrated in the instance profile. Start profiles are e.g. in systems of the type ECC 6.06 available.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

57

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

The start profile or instance profile defines which steps must be performed during the start process or which processes of the instance are started by sapstartsrv. First, sapcpe (Central Patch Environment) is executed, which replicates, copies or links directories and programs. sapcpe is used to replicate the kernel from the global directories to the local exe directory of the instance. For example, the start profile or instance profile defines that the database should be started if it is not yet running for the PAS instance and the AAS instances. The IGS watchdog is also started, and on a system with an ABAP stack, the ABAP dispatcher is started and if necessary, the ABAP message server. Normally, the start profile or the entries for the starting procedure in instance profile are not changed. If these entries for the start process are changed in the start profile despite this, sapstartsrv has to be restarted.

Figure 13: Start and Profile Evaluation of an Instance

If an instance is started, the parameters of the default and instance profile are evaluated, and the instance is started with these parameters. Parameters are defined in the default profile for all instances. For each instance, there is a separate instance profile that defines the parameterization for the respective instance.

58

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: System Start: Process

Lesson Summary You should now be able to: • Describe the process of the start procedure of an SAP system • Describe the structure of the file system for SAP instances

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

59

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Lesson: System Start: AS ABAP and AS ABAP+Java Process Lesson Overview Depending on the installation, the SAP NetWeaver Application Server (AS) may run as an AS ABAP, AS ABAP+Java, or AS Java system. However, the infrastructure for starting and stopping is basically identical, and is introduced in this lesson using an AS ABAP+Java system as an example. On an SAP NetWeaver AS running as an ABAP+Java system, the Java stack is automatically started and stopped by the ABAP dispatcher using the Startup and Control Framework (which this lesson does not describe in more detail). The tools used to run the start/stop process are discussed in a later lesson.

Lesson Objectives After completing this lesson, you will be able to: • • •

Describe the general start process for an SAP NetWeaver AS ABAP. Describe the general start process for an SAP NetWeaver AS ABAP+Java. Describe which profiles are evaluated.

Business Example As the administrator of SAP systems, you need to stop the systems for maintenance purposes or after changing system parameters, and then restart them.

Starting and Stopping an SAP NetWeaver AS ABAP The instances are started and stopped using tools such as the SAP Management Console (SAP MC). In an instance of a dual-stack system (ABAP+Java), the Java stack is started by the ABAP dispatcher using the Startup and Control Framework, which then starts the Java dispatcher and the server processes. The Java cluster elements are started using the Startup and Control Framework.

60

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: System Start: AS ABAP and AS ABAP+Java Process

Figure 14: Starting an SAP NetWeaver AS ABAP without an ABAP Central Services Instance

The tools (explained in more detail in a later lesson) can be used to start or stop individual instances or also the entire system. To start and stop individual instances, follow the sequence of priority of individual instances. However, the infrastructure also allows the entire system to be started, stopped, or restarted. The tools for starting and stopping communicate with the sapstartsrv process, which also provides the functions of a Web service. The sapstartsrv process is a service in Windows operating systems; in other operating systems, it is scheduled as a daemon. There is a separate sapstartsrv process for each instance, which is responsible for starting and stopping the instance. If a sapstartsrv process now receives the start command for the system, it must forward this to the other sapstartsrv processes, which is done through HTTP(S). The sapstartsrv processes write a 1-byte control file to the $(DIR_GLOBAL)\sapcontrol directory every minute. The name of the control file indicates the port and host on which the process can be accessed, and the priority of its instance. Using the control files, the sapstartsrv process recognizes which other sapstartsrv processes are still active, and starts them according to their priority.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

61

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

In the above figure, the PAS instance is started first when the overall SAP system is started (step 1). This is because it has an enqueue work process and is therefore priority 2. It also has no (Java) Central Services or ABAP Central Services instance. At this point, a check is performed to see whether the database is running (step 2). If it is not running, it is started. For the sake of simplicity, the sapcpe (Central Patch Environment) step has been omitted. This is run as the first step in the start process of every instance (and, if relevant, before the database is started). The ABAP message server and the ABAP dispatcher are now started (step 3). The ABAP dispatcher starts its work processes and the ICM. The AAS instance is then started since it has priority 3. The start process is similar to the PAS instance start process, but no ABAP message server is started because there is only one per system. In step 4, the system checks whether the database is running. The database was started when the PAS instance was started. Although this appears unnecessary, the reason becomes clear in the next example based on an AS ABAP system with an ABAP Central Services instance. In step 5, the ABAP dispatcher is started, which starts its work processes and the ICM. Hint: The database is only started if it runs on the same host as the instance. In a distributed installation, the database has to be started separately. In the start process, a timeout is specified for starting instances with the next highest priority. This means that all instances with the same priority have to be started within the timeout so that instances with the next highest priority can be started. With a timeout of 300 seconds, in our case this means that the AAS instance is not started if the start process of the PAS instance lasts longer than five minutes. The AAS instance can be started subsequently, or the value for the system start timeout can be adjusted.

62

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: System Start: AS ABAP and AS ABAP+Java Process

Figure 15: Starting an SAP NetWeaver AS ABAP with an ABAP Central Services Instance

In the above figure, when the overall SAP system is started (step 1), the ABAP Central Services instance is started first (step 2) because it has priority 1. PAS instance and all AAS instances are then started. Note: In a system with an ABAP Central Services instance, the enqueue work process and the message server into the ASCS instance have been relocated. This means that besides the ASCS instance, there are only instances with priority 3. PAS und AAS instances do not differ. The PAS instance is installed first. During the start process of the PAS or AAS instances, the system first checks whether the database is already running (step 3). If it is not running, it is started. In step 4, all instances are starting the ABAP dispatcher. The ABAP dispatcher starts its work processes and the ICM.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

63

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

If the instances are started separately, the ABAP Central Services instance must be started first. Each PAS or AAS instance can then be started separately and in any order. It is therefore important that each instance checks whether the database is running, and starts it if necessary. Hint: The database is only started if it runs on the same host as the instance. In a distributed installation, the database has to be started separately.

Starting and Stopping an SAP NetWeaver AS ABAP+Java from 7.1x In an instance of a dual-stack system (ABAP + Java), the Java Stack is started by the ABAP dispatcher using the Startup and Control Framework and which than starts the Java dispatcher and server processes. The Java cluster elements are started using the Startup and Control Framework.

Figure 16: Starting an SAP NetWeaver AS ABAP+Java from 7.1x

In the above figure, when the overall SAP system is started (step 1), the Central Services instance is started first because it has priority 1. The PAS instance has priority 2 (since no ABAP Central Services instance was installed); therefore, it is the next one to be started. At this point, a check is performed to see whether the database is running (step 3). If it is not running, it is started. The ABAP message server and

64

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: System Start: AS ABAP and AS ABAP+Java Process

the ABAP dispatcher are now started (step 4). The ABAP dispatcher starts its work processes, the ICM, and the Startup and Control Framework (step 5), which the Java dispatcher, the SDM (Software Deployment Manager), and the Java server processes belong to. The AAS instance is then started (steps 6, 7 and 8) since it has priority 3. The start process is similar to the PAS instance start process, but no ABAP message server is started because there is only one per system. Hint: The database is only started if it runs on the same host as the instance. In a distributed installation, the database has to be started separately.

Starting and Stopping an SAP NetWeaver AS ABAP+Java till 7.0x In an instance of a dual-stack system (ABAP + Java), the Java Stack is started by the ABAP dispatcher using the Startup and Control Framework and which then starts the Java dispatcher and server processes. The Java cluster elements are started using the Startup and Control Framework.

Figure 17: Starting an SAP NetWeaver AS ABAP+Java till 7.0x

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

65

Unit 4: Starting and Stopping SAP Systems

TADM10_1

This figure shows the starting process of a SAP NetWeaver AS ABAP + Java systems till 7.0x as it is for example used in an SAP Solution Manager 7.1. The starting process differs only in the Startup and Control Framework, which includes in addition to the server processes also a Java dispatcher and by the Central Instance a SDM.

Stop Process: Flow An SAP system is stopped in the opposite sequence. The instances with enqueue are always stopped last. If the ABAP dispatcher receives the stop command (and the system is an AS ABAP+Java system), it transfers this to the Startup and Control Framework and the processes of the Startup and Control Framework, and the processes, which ABAP dispatcher has started, are stopped. The SDM is also stopped in the PAS instance.

Start Process of an Individual Instance and Evaluation of Profiles

Figure 18: Evaluation of the Start, Default, and Instance Profiles

Using an example of the PAS instance of a dual-stack system without an ABAP Central Services instance, the start process of an individual instance is shown here, as well as the step in which the particular profiles are evaluated. The sapstartsrv process evaluates the start profile or instance profile when it starts. This defines which programs the process has to start or execute when its instance starts.

66

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: System Start: AS ABAP and AS ABAP+Java Process

First, the sapcpe program is executed, which replicates the kernel. After this, the system checks whether the database is already running, and if necessary started (this step is omitted in the case of an ABAP Central Services instance and (Java) Central Services). The start profile or instance profile for the PAS instance specifies that the sapstartsrv process first starts the ABAP message server. The ABAP message server evaluates the parameters of the default and instance profile, and starts with this parameterization. The sapstartsrv process then starts the ABAP dispatcher, which evaluates the default and instance profile, and starts with this parameterization. The profile parameters define several functions including what the ABAP dispatcher should start (for example, work processes, ICM, Java Startup and Control Framework, and so on). These processes evaluate during their start the default profile too the instance profile to and start with this parameterization. Furthermore, the ABAP dispatcher starts the Startup and Control Framework, which also evaluates the default and instance profile. If necessary, the sapstartsrv process also starts additional programs such as IGS Watch Dog. The process saposcol (SAP Operating System Collector), which collects the performance data of the operating system, will be started by the SAP Host Agent.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

67

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Lesson Summary You should now be able to: • Describe the general start process for an SAP NetWeaver AS ABAP. • Describe the general start process for an SAP NetWeaver AS ABAP+Java. • Describe which profiles are evaluated.

68

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Overview of the Process for Starting and Stopping an SAP NetWeaver AS Java

Lesson: Overview of the Process for Starting and Stopping an SAP NetWeaver AS Java Lesson Overview There are different techniques for initiating the start and stop processes for the SAP NetWeaver AS, depending on the installation (with or without an ABAP stack). The Java part of a SAP NetWeaver AS ABAP + Java is automatically started and stopped by the ABAP dispatcher. The start and stop process for an SAP NetWeaver AS Java (without ABAP stack) can be performed using the SAP Management Console (SAP MC).

Lesson Objectives After completing this lesson, you will be able to: • • •

Describe the sequence in which the components of an SAP system and started and stopped Describe the general start process for an SAP NetWeaver AS Java Describe the general start process for an SAP NetWeaver AS ABAP + Java

Business Example An SAP system should be stopped before maintenance work to the hardware and started again later. To be able to do this, it is necessary to become familiar with the tools for starting and stopping the system, and the process flow.

System Start: Process The starting of an SAP system is the basic prerequisite for being able to work with the system. The start process presented in this lesson describes the process flow when starting an SAP system with ABAP and Java stack as well as when starting an SAP system with a Java stack but without an ABAP stack. Every SAP system has

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

69

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

a database and at least one instance. Systems with the Java stack have at least two instances. The instances can be divided into three different categories with different priorities for the start and stop process. 1. 2. 3.

Instances with enqueue but without ABAP dispatcher Instances with enqueue and with ABAP dispatcher All other instances

The enqueue plays a special role in the ABAP stack and in the Java stack for the start sequence; the enqueue is on one instance only for each stack. These instances that usually also contain the message server must be started before all other instances. The Java Central Services instance (priority 1) does not require a running database; therefore, the database is not started when this instance is started. An instance with an ABAP dispatcher and an enqueue work process (priority 2) requires a started database that the ABAP work processes log on to. Therefore, the first step is to start the database when starting this type of instance (unless it is already running). The starting of the database is done by scripts which comes with the installation. These scripts are able to start the database if the database is installed on the same server as the instance. In the “SAP MC” tool for starting and stopping purpose, there is a special option implemented, which allow to start and stop a database seperatly or during the start or stop of the SAP System regardless of the server where the database is installed. This special option will be discussed in the lesson about the “SAP MC”.

70

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Overview of the Process for Starting and Stopping an SAP NetWeaver AS Java

In principle, the start process is performed in multiple steps. The start process is performed with the operating system user adm: 1.

Starting the Central Services Instance The Central Services consist of the Java message server and the Java enqueue server. The ICM and server Java cluster elements connect to the Java message server during their own start process.

2.

Starting the database The database is the fundamental element of the entire SAP system. This must be in an operational state before SAP instances that contain an ABAP dispatcher or Java server process are started. However, it may run or be started before the Central Services instance is started.

3.

Starting the PAS or AAS The Primary Application Server Instance (PAS) or Additional Application Server Instance (AAS) first checks whether the database is started; it starts the database if it is not already started. If there is an enqueue work process in a PAS or AAS (usually in a PAS with ABAP stack), this instance must be given priority and started before the other instances.

For the start process, you differentiate between the starting of SAP systems with purely Java instances (without ABAP) and instances with Java and ABAP stack. Additional details are provided in the following sections.

System Stop: Process The stopping of an SAP system is performed in reverse sequence. The instances with enqueue are always stopped last. For SAP system installations on the Microsoft Windows operating system, the database is not stopped at the same time. This can be done with the tools of the relevant database or the special option in the “SAP MC”. In the case of SAP system that are installed on UNIX operating systems, the database is generally stopped at the same time.

Hard Shutdown The hard shutdown tops the system or the instance immediately, regardles if user requests are currently processed or not.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

71

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Soft Shutdown If the soft shutdown for an instance is triggered, there is no logon to the instance possible anymore. The instance is removed from the load balancing list of the message server. However, requests of logged on users are still dispatched to the related instance by the message server (e.g. http requests). On the AS ABAP, no more long running tasks are scheduled and it is been waiting for the end of long running tasks e.g. batch jobs or updates. If there is no long running task anymore, than it is been waited until all user sessions are ended. Afterwards all internal tasks are stopped and if all work processes are idle, the instance shuts down. On the AS Java, every server process enters the state preparing to stop if no critical task is running. If there is no user session alive, the server process stops the application and shuts down. In case that user sessions exists, the server process waits, until all user sessions have ended. In case of an AS ABAP+Java system, the behavior is nearly the same except that the stopping of the ABAP internal tasks is delayed, until the Java part is stopped already.

Starting and Stopping an SAP NetWeaver AS ABAP + Java The instances are started and stopped using appropriate tools - such as the SAP Management Console (SAP MC). The start of the Java stack is controlled by the ABAP dispatcher within an instance of a dualstack system. In concrete terms, this means that the start and stop processes are triggered by the ABAP dispatcher. To do this, the ABAP dispatcher sends a start command to the so-called Startup and Control Framework. The corresponding Java cluster elements are started using the Startup and Control Framework. Note: The Startup and Control Framework consists of the Java Instance Controller and the server processes in a dualstack system. The ICM also belongs to the Startup and Control Framework in an SAP NetWeaver AS Java system.

72

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Overview of the Process for Starting and Stopping an SAP NetWeaver AS Java

Figure 19: Starting an SAP NetWeaver AS ABAP+Java

The tools (explained in more detail in the next lesson) can be used to start or stop individual instances or also the entire system. You should proceed as described above for the start process. If the complete system is started, you can be selected, for example in the SAP MC All Instances. The tools communicate with sapstartsrv. This is a service in Windows operating systems; it should be scheduled as a daemon in other operating systems. There is an sapstartsrv for each instance; this is responsible for starting and stopping the instance. If an sapstartsrv now receives the start command for the system, it must pass this on to the other sapstartsrv; this happens via HTTP or HTTPS. The sapstartsrv write a 1 byte control file every minute to the directory $(DIR_GLOBAL)\sapcontrol whose name specifies, among other things, the port and host on which it can be reached and the priority that its instance has. Using the control files, the sapstartsrv recognizes which other sapstartsrv are still active and passes the start signal on to them according to the priority. Therefore, the above figure shows that the Central Services instance is started first because it has priority 1. The PAS has priority 2 (since no ABAP Central Services instance was installed); therefore, it is the next one to be started. At this point, a check is performed to see whether the database is running (step 3). If it is not running, it is started. The

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

73

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

ABAP message server and the ABAP dispatcher are now started (step 4). The ABAP dispatcher starts its work processes, the ICM and the Startup and Control Framework (step 5) to which the Java server processes belong. The AAS is then started since it has priority 3. The start process is similar to PAS; however, there is no ABAP message server started. In the start process, a timeout is specified for the start of the instances with the next highest priority. This means that all instances with the same priority have to be started within the timeout for the instances with the next highest priority to be started. The timeout is regarding to the enqueu and message server. In such a Dual-Stack system you will recognize, that if the PAS starts, a short time later all AAS instances are started, while the PAS is still starting, but the enqueue and message server is already up and running. This happens because nowadays the timeout is regarding the enqueue and message server. The stop process is performed by the ABAP dispatcher in the same way as the start process. The ABAP dispatcher also informs the Startup and Control Framework and transfers the stop command in this case.

Starting an SAP NetWeaver AS Java In an SAP NetWeaver AS Java system, the Startup and Control Framework is started directly by the sapstartsrv. The ICM also belongs to the Startup and Control Framework along with the Java Instance Controller, the server processes. Using the relevant tools, for example SAP Management Console (SAP MC) or the Microsoft Management Console (SAP MMC) under Windows, the start command is passed on to an sapstartsrv, which forwards this to the appropriate sapstartsrv, which starts “its” instance.

74

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Overview of the Process for Starting and Stopping an SAP NetWeaver AS Java

Figure 20: Starting an SAP NetWeaver AS Java (without ABAP)

If the start command for the system start is passed on to an sapstartsrv, the procedure here is the same as described above for starting an SAP NetWeaver AS ABAP + Java system. The Central Services instance is started first because it has priority 1. The PAS and AAS are then started (step 4) since they have priority 3. The sapstartsrv of the PAS and AAS check before the start of the instance (step 3) whether the database is running; if it is not, it is started before the PAS or AAS is started if the database is installed on the same host where PAS or AAS is installed..

Evaluating the Profiles in the Start Process There are no start profiles in SAP NetWeaver 7.10 and later releases. Information for the start process is integrated into the instance profiles. Therefore, the instance profile is also used to start the sapstartsrv. If information for the start process is changed in the instance profile, the sapstartsrv has to be restarted as before.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

75

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Figure 21: Evaluation of Default and Instance Profiles

If an instance of a dualstack system is started, the ABAP message server (if it belongs to the instance) evaluates the parameters of the default and instance profile and starts with this parameterization. Similarly, the ABAP dispatcher evaluates the default and instance profile and starts with this parameterization. The work processes and the ICM also evaluate the default and instance profile during their start. Furthermore, the ABAP dispatcher starts the Startup and Control Framework, which also evaluates the default and instance profile. In an SAP NetWeaver AS Java system, the sapstartsrv starts the Startup and Control Framework.

76

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Overview of the Process for Starting and Stopping an SAP NetWeaver AS Java

Lesson Summary You should now be able to: • Describe the sequence in which the components of an SAP system and started and stopped • Describe the general start process for an SAP NetWeaver AS Java • Describe the general start process for an SAP NetWeaver AS ABAP + Java

Related Information •

2013/Q1

SAP Help Portal: help.sap.com → SAP NetWeaver

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

77

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Lesson: Tools for Starting and Stopping SAP Systems Lesson Overview This lesson presents the tools for a technical implementation of start and stop processes for SAP systems. The SAP Management Console (SAP MC) and the sapcontrol program can be used for the start and stop process regardless of the operating system.

Lesson Objectives After completing this lesson, you will be able to: •

Operate the tools to start and stop an SAP NetWeaver AS ABAP

Business Example You are using an SAP NetWeaver Application Server with operating system platforms such as Microsoft Windows or UNIX. To start and stop the SAP systems, you require information about the use of the available tools.

The SAP Management Console (SAP MC) As of SAP NetWeaver Release 2004, a new operating system-independent application is supplied with the SAP Management Console (SAP MC) (see SAP Notes 1014480 and 995116). This allows you to display various monitoring information and perform administration tasks such as start and stop operations in the same interface on different operating systems. The tool is a standalone Java application, which can be started either as an applet or locally. The SAP MC is supplied as standard with the kernel and is ready for use without any additional installation. The SAP MC is a Java application, which is started as a Java applet by default. All you need is a web browser. To use the applet correctly, you need a JRE (Java Runtime Environment) Version 1.4.2 or higher. The relevant Java plug-in for the browser must also be activated correctly. To start the SAP MC after installing the relevant SAP NetWeaver AS, enter the following URL in your browser: http://:513 Or, if you have configured https in sapstartsrv (see SAP Note 1036107): https://:514 The sapstartsrv process now uses its web service function and sends the Java applet to the browser that is starting the SAP Management Console.

78

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Tools for Starting and Stopping SAP Systems

Figure 22: The SAP Management Console

The SAP Management Console (SAP MC) indicates the status of all instances of the system using colors. The colors have the following meaning for the system or an instance: Gray Stopped Yellow Not fully running Green Fully running Red Errors The left section of the SAP MC shows the system as a tree structure in which the individual elements can be expanded to view additional details. When you select the system, the status of the individual instances is shown in the right section of the SAP MC, and the Features field shows which services the instances provide.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

79

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Starting and stopping the database with the SAP Management Console and SAP Host Agent The SAP MC provides the possibility to start and stop the database. This function is not implemented in other tools such as the SAP Microsoft Management Console or sapcontrol. With tools such as sapcontrol the database is only started, when a PAS or AAS instance is started on the same computer on which the DB is installed too (Condition: DB belongs to the same SAP system as the instance). On the computer on which the DB of the SAP system is installed, a SAP Host Agent must be installed too. It starts and stops the DB and also provides monitoring data to the SAP MC using the operating system. The SAP MC receives the information from sapstartsrv, on which computer the DB runs and connects with the SAP Host Agent, which starts or stops DB through the Port 1128 (or 1129 for secure network communications). A stopped DB is displayed in “gray” and a started DB is displayed in “green”. If the DB is not started correctly, the DB symbol is displayed in “yellow”. Expand the DB icon and select the DB icon with the marking as in the Figure Stopping DB with SAP MC. You reach the context menu with the right mouse button and can start or stop the DB depending on its current status.

80

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Tools for Starting and Stopping SAP Systems

Figure 23: Stopping DB with SAP MC

Hint: In the SAP MC, if the DB is displayed in “blue”, then probably no SAP Host Agent is installed on the DB computer, or the SAP host Agent is an old version. Hint: Special features of SAP MaxDB: For an SAP MaxDB a user must be specified with a password(if SAP MaxDB runs on Windows), so that the state of the DB can be displayed and it can be started or stopped. If no user has been specified with a password, but this is needed, the DB is displayed in “blue”. To enter a user name, click on the “blue” DB icon, a popup will ask you for the user name and password. If the SAP system is started with the SAP MC, then the SAP Host Agent is called first so that it can start the DB if it is in the state Stopped. Then the instances of the SAP system can be started according to their priorities. Here, the communication takes place directly between the sapstartsrv processes. The SAP MC receives information regarding the status of each instance through direct communication with the relevant sapstartsrv. The instances with Priority 1 are started after the DB, although it would be possible to use these to start before the DB. The SAP MC has the Option to stop the DB as well when stopping the SAP system. If this is selected, then the DB from the SAP Host Agent stops when all instances are stopped.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

81

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Figure 24: Start sequence during the start with the SAP MC

The Figure Start sequence during the start with the SAP MC shows the start process of an SAP system with the instances of priority 1 and 3. The administrator has started the SAP MC through the sapstartsrv process of the instance with priority 1 (port 513) (solid line to the sapstartsrv). The SAP MC has received the information about all other sapstartsrv processes of the system and their ports, so has the SAP MC the connection to each sapstartsrv process of the SAP system (shown as a dashed line). Additionally SAP MC has received the information on which computer the DB is running and has opened the connection to the local SAP Host Agent (port 1128) (shown also as a dashed line). The lines to the sapstartsrv and to the SAP Host Agent are not technically different, the solid line symbolize only the call of the SAP MC.

82

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Tools for Starting and Stopping SAP Systems

If the administrator now selects the SID of the SAP system and with the right mouse button selects Start ... (individual step 1), then the following process runs: 1. 2. 3. 4. 5. 6.

The SAP Host Agent receives the command to start the database. The SAP Host Agent starts the DB if it is in the state “stopped”. The sapstartsrv of the instance with the priority 1 gets the command to start the instances according to their priority. The sapstartsrv of the instance with the priority 1 starts its instance. The sapstartsrv of the instance with the priority 1 triggers the sapstartsrv of the instance with the priority 3 to start its instance. The sapstartsrv of the instance with the priority 3 starts its instance.

On each computer on which an SAP instance was installed, a SAP Host Agent should be installed too (this is not shown in the figure above for reasons of clarity). The SAP MC connects with the SAP Host Agents of the individual instances and provides for them the information about memory, file system and operating system processes.

Starting the SAP System with the SAP Management Console Once the system is selected, you can use the right mouse button to start, restart, or stop the entire system. The SAP MC works according to the start priorities, and starts or stops the SAP system in the correct sequence. When the SAP MC is reopened, the user is prompted for the user name and password of the adm user at the first start, stop or restart process. This is the user on the operating system where the instance or SAP system is installed. This user is authorized to start or stop an SAP system or instance. The figure SAP MC: System Start shows the start process of the entire system where the priority 2 instance (in this case, the PAS instance) is still running through its start process.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

83

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Figure 25: SAP MC: System Start

When an instance is started, the following statuses are shown in this view: “Started”, “Running but not connected to Message Server”, “Running”. If all processes of an instance are running, this view shows the status “Running”. Sometimes, the status “Dialog Queue standstill” is displayed during the start process of an AS ABAP system. This indicates that the start process of the AS ABAP has not fully finished running, and that work processes may not yet be fully initialized. We recommend logging on to the system or instance after the start process to check system availability. During the start process for the system, a start timeout query is sent. If all instances with the same priority do not start within this period, instances with a higher priority cannot be started. The default value is 300 seconds, but this value can be customized in the query dialog box. The timeout then starts again, if the start process of a priority is finished. If the start timeout for the instance of a priority is up, the start process is not terminated, but continues to run.

Stopping the SAP System with the SAP Management Console When an SAP system is stopped using the SAP MC, the process follows the opposite sequence to the start process of the system, taking the priorities into account. However, the database is not stopped. After calling the stop process, a hard or soft shutdown query is sent. A soft shutdown means that no further user requests are received by the instance, and processes are terminated if no process is handling a query. The database will here be only stopped, if it is selected explicitly via selection in the following query.

84

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Tools for Starting and Stopping SAP Systems

The stop timeout specifies how much time instances with the same priority are given to complete the stop process before instances with the next lowest priority are stopped. If all AAS instances cannot be stopped within 300 seconds, the PAS instance is stopped once this timeout has expired, and so on.

Starting an Instance with the SAP Management Console In addition to starting and stopping entire systems, individual instances can also be started, stopped, or restarted with the SAP MC. To do so, select the instance and use the right mouse button to perform the required action. The administrator is responsible for maintaining the correct sequence.

Figure 26: SAP MC: Instance Start

When you expand the instance, other elements are displayed in the SAP MC including the Process List, AS ABAP WP Table. The Process List provides information about the start process, and indicates which processes have been started by the sapstartsrv process along with their status. At the beginning of the start process, you can also use the Process List to view the sapcpe process, and if relevant, check whether the database has started (strdbs). As shown in the figure SAP MC: Instance Start, you can also see the ABAP message server, the IGS Watchdog, and the ABAP dispatcher under the PAS instance. In this example, the ABAP dispatcher also shows the status

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

85

Unit 4: Starting and Stopping SAP Systems

TADM10_1

“Running, Message Server connection ok1.” as dis In the AS ABAP WP Table, you can check whether work processes have already been started, and whether they have completed their initialization processes (the Start column shows yes). In an AS ABAP+Java system, the status of the ABAP dispatcher only changes to green once all Java processes and all ABAP processes are running. This is shown in the figure SAP MC: Start Process of the Instance is Complete.

Stopping an Instance with the SAP Management Console The stop process of an instance is the same as the stop process of a system: only the selected instance is stopped. Once any of the processes that belong to an instance are no longer running, or processes are stopping, the instance is colored yellow. As with the start process of an instance, the Process List shows the status of the individual processes. In an AS ABAP+Java system, the ABAP dispatcher is only stopped once all ABAP processes and all Java processes have been stopped.

Further Information about the SAP MC and sapstartsrv You can view the SAP MC version in the menu by selecting ? → About. Very old versions of the SAP MC do not show any version information, and should be replaced with a later version. The SAP MC allows you to display Developer Traces. For example, for work processes or the ABAP dispatcher, this is possible using the right mouse button. The sapstartsrv process contains a web service interface, which provides a number of functions for managing and monitoring an SAP instance, in particular the SAP Management Console (SAP MC). The sapstartsrv process also has a limited web server function that allows you to download all files under DIR_EXECUTBALE/servicehttp using HTTP(S). This can be used, for example, to start the SAP Management Console from a web browser on any host. If no other URL is specified (such as http://:5$$13), the system automatically redirects you to http://:5$$13)/servicehttp/sapmc/sapmc.html, for example, to start the SAPMC. The sapstartsrv process manages an internal list of protected operations. These can be changed, if necessary, with the start profile parameter service/protectedwebmethods. With the start profile parameter service/hostname, you can also determine the IP address / host name to which the web service port should be connected (default: all / 0.0.0.0) to limit accessibility in the network. You then have to restart sapstartsrv. To do this, refer to SAP Note 927637 - Web service authentication in sapstartsrv as of release 7.00.

86

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Tools for Starting and Stopping SAP Systems

SAPControl SAPControl allows the web services of the sapstartsrv processes to be addressed. SAPControl is part of the kernel, and is available on all operating systems. Calling sapcontrol without any other options provides the syntax description. The figure SAPControl: Syntax and Examples shows the basic structure of the syntax with some selected examples.

Figure 27: SAPControl: Syntax and Examples

In the first example “sapcontrol -user dccadm password -nr 10 -function StartSystem LEVEL 2”, the web method StartSystem is called with the parameter LEVEL and the value 2 for the level. As with the SAP MC, a sapstartsrv process that is used to start the instances is addressed. “LEVEL 2” means that all instances with priority 1 are started first (if available or they are already running). In our AS ABAP system, no Central Services instance is available, so only the PAS instance (and if relevant, the database) is started, but no further instances. It is not important whether the instances are running on the same or different hosts. With StartSystem LEVEL 3 (corresponds to StartSystem ALL), all the instances of the system are started according to their priority, unless they are already running. This is the same procedure used to start the system using the SAP MC. StopSystem LEVEL 2 means that all priority 3 and priority 2 instances are stopped if they are still running. StopSystem ALL has the same meaning as StopSystem LEVEL 1.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

87

Unit 4: Starting and Stopping SAP Systems

TADM10_1

In the second example, “sapcontrol -prot PIPE -nr 11 -function Start”, a Trusted Connection is used. No user name or password are specified because the operating system authentication as adm is sufficient. However, it is only possible to call web methods for the local computer. In the example, the AAS instance (instance number 11) is started. The function StartSystem LEVEL 3 is not possible because StartSystem may have to communicate with instances outside the host, which is not permitted under Trusted Connections. This means only functions for instances are possible. Caution: Trusted Connection for Windows: -prot PIPE Trusted Connection for Unix: -prot NI_HTTP; this is the default value. See also SAP Note 927637 - Web service authentication in sapstartsrv as of release 7.00

Special Features when Starting and Stopping Under Microsoft Windows With the Microsoft Windows operating system, you can use both the SAP Management Console and the Microsoft Management Console with an SAP snap-in (SAP MMC) to start and stop an SAP system. The SAP MMC allows you to start and stop the instances of the SAP system. For some databases, you can also display administration information and the status of the database. Some database types can also be managed using the SAP MMC. The information displayed in the SAP MMC, and the start and stop procedures are the same as the browser-based SAP Management Console (SAP MC). This is illustrated by the next two figures.

88

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Tools for Starting and Stopping SAP Systems

Figure 28: SAP MMC

One small difference to the SAP MC is shown in the figure SAP MMC. Here, the instances are not marked with their directory name of the file system, but with the host name and instance number. In exactly the same way as the SAP MC, you can see which instance is the central instance in the Process List, and so on. Equally, you can use the SAP MMC to start and stop the entire system according to the priorities of the instances. It is also possible to start and stop individual instances. When you restart the SAP MMC, you must enter the adm password the first time you start or stop the system or instance. Hint: In future, the latest versions of the SAP MMC will be available on the SCN. You can find the update link and further information at the bottom of the following page http://scn.sap.com/docs/DOC-8294

Special Features of Starting and Stopping Under UNIX Previously on SAP systems installed under UNIX, you executed the scripts startsap and stopsap to initiate the start and stop processes. If multiple SAP instances are installed on one physical server, you add the instance name to the names of the scripts startsap and stopsap.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

89

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

The script startsap can be called with the following options: • • • •

DB: starts the database system; R3: starts the instances and associated processes for the instance J2EE: starts the instances and associated processes for the instance ALL: starts the database system and the instance (default setting, can be omitted).

The stopsap script can be called with the following options: • • • •

DB: stops the database system using the script stopdb; R3: stops the instances of the SAP system; J2EE: stops the instances of the SAP system; ALL: stops the database system and the instance (default setting, can be omitted).

The database and SAP instances can each be started and stopped separately with the options DB or R3, for example startsap R3 DVEBMGS00 or with the new style startsap -t R3 -i DVEBMGS00. You get help for startsap and stopsap with the –h option. Caution: The option J2EE can be used in the same way as the option R3. In the case of the SAP NetWeaver AS ABAP+Java, both the ABAP stack and the Java stack are started and stopped.

Organizational Information: Stopping the SAP System It may be necessary to stop an SAP system for a variety of reasons, such as to restart after permanently changing profile parameters, before installing kernel patches, or to allow hardware upgrades to be carried out.

90

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Tools for Starting and Stopping SAP Systems

Figure 29: Before Stopping the SAP System

Before you stop the system, you should check the status of the system. This includes checks such as: •

Active users: Check which users are logged on using the User List (SM04 (per instance) or AL08 (system wide)).

•

Background processing: Check which jobs are active using the Job Overview (SM37). If jobs are terminated by starting the system, these must be rescheduled. Jobs that are scheduled for the time in which the system is stopped run automatically once the system is restarted.

•

Batch Input: The transaction Batch Input: Session Overview (SM35) displays running batch input jobs.

•

Update: Use the Update Overview (SM13) to check whether update processes are terminated by the system stop. These update records are rolled back during the stop, and are set to the status “init”. These records are then updated again during the restart.

Before you stop your system, you should inform users using a system message (SM02).

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

91

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Generally, it is not easy to stop a system or an instance; there are some organizational conditions to note. The “downtime” must be scheduled together with the relevant department, or downtimes must be logged. SAP Solution Manager provides the Work Mode Management work center to simplify planning and execution. Systems and instances can also be started or stopped in Work Mode Management. Just like the SAP MC and SAPControl, the work center also uses the sapstartsrv process.

92

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Tools for Starting and Stopping SAP Systems

Exercise 2: Starting and Stopping the SAP System Exercise Objectives After completing this exercise, you will be able to: • Start and stop an SAP system.

Business Example As the administrator of SAP systems, you need to stop the systems for maintenance purposes or after changing system parameters, and then restart them.

Task 1: Stopping with the SAP Management Console Stop the SAP system using the SAP Management Console. 1.

Optionally: Before you stop the SAP system, check which users are logged on to your system. Send a system message.

2.

Stop the SAP system using the SAP Management Console. To do this, log on to the server for your training system with the Terminal Server Client. Log on with the user adm and the password, that was given to you.

Task 2: Starting with the SAP Management Console Start the SAP system using the SAP Management Console. 1.

Start the SAP system using the SAP Management Console. Monitor the start of the processes in your system. Your instructor will provide you with the name of the server on which you can start the SAP MC.

2.

Which process types are started at operating system level after your system is started up?

3.

Check whether your system started correctly. To do this, log on to your SAP system and check in the SAP MC or SAP MMC that all processes are running.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

93

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Task 3: (Optional) stopping from the Command Line Stop the SAP system using a command call. 1.

To do this, log on to the server for your training system with the Terminal Server Client. Log on with the user adm and the password, that was given to you.

2.

Check whether your SAP system is running at operating system level.

3.

Use the sapcontrol command to stop the entire SAP system.

Task 4: (Optional) starting from the Command Line Start the SAP system using a command call.

94

1.

Check whether your SAP system has stopped at operating system level.

2.

Use the sapcontrol command to start the entire SAP system.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Tools for Starting and Stopping SAP Systems

Solution 2: Starting and Stopping the SAP System Task 1: Stopping with the SAP Management Console Stop the SAP system using the SAP Management Console. 1.

Optionally: Before you stop the SAP system, check which users are logged on to your system. Send a system message. a)

You can use the global user overview to display the users logged on to your SAP system: Tools → Administration → Monitor → Performance → Exceptions/Users → Active Users → Global Users (transaction AL08). In this transaction, you will find your own user more than once. Transaction AL08 uses RFC connections to collect the user information for all instances. This means that your own user, which initiates the RFC connections, is displayed additionally once per instance. To send a system message to the users, choose Tools → Administration → Administration → System Messages (transaction SM02). Choose the Create pushbutton, enter the system message text, and choose Save.

2.

Stop the SAP system using the SAP Management Console. To do this, log on to the server for your training system with the Terminal Server Client.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

95

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Log on with the user adm and the password, that was given to you. a)

Start a Web browser and enter http://twdfxxxx.wdf.sap.corp:5$$13 in the address bar (where xxxx stands for the number of the server assigned to your group and $$ represents the instance number). In the SAP MC, select the required system or individual instance, and choose the Stop function from the context menu (right mouse button). If you have selected Stop for your system, then a popup will appear with the question whether a hard or soft shutdown and whether the DB should be stopped (including Database). Select hard and don not stop the database. The system now requires you to authenticate your ID. To do this, enter the user adm with the password assigned for your user. Depending on whether you selected an individual instance or the SAP system, either an individual instance or the entire SAP system is stopped. Hint: You should always stop the instances regarding their reverse priority (first stop priority 3, last stop priority 1). The priority of an central services instance is 1 The priority of an PAS instance is 2, if a enqueue workprocess is configured on the PAS instance. The priority of all other instances is 3.

Task 2: Starting with the SAP Management Console Start the SAP system using the SAP Management Console. 1.

Start the SAP system using the SAP Management Console. Monitor the start of the processes in your system.

Continued on next page

96

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Tools for Starting and Stopping SAP Systems

Your instructor will provide you with the name of the server on which you can start the SAP MC. a)

Start a browser on the host specified by your instructor and enter http://twdfxxxx.wdf.sap.corp:5$$13 in the address bar. Choose the node for the PAS instance in the SAP Management Console tree. Select the desired instance and choose the Start function from the context menu (right mouse button). Start the AAS instance in the same way. Hint: You should always start the instances regarding their priority. The priority of an central services instance is 1 The priority of an PAS instance is 2, if a enqueue workprocess is configured on the PAS instance. The priority of all other instances is 3. If you select the node of the SAP system in the tree of the SAP Management Console to start the system, you will be asked for a user of the database. Enter the appropriate user and PW, which was given to you by your trainer.

2.

Which process types are started at operating system level after your system is started up? a)

You can monitor the processes at operating system level with the Process Explorer (Toolbar: SAP Training → Tools → Process Explorer). The following processes are started at operating system level after your system is started up: msg_server.exe, gwrd.exe, icman.exe, and several disp+work.exe. Furthermore, Java processes can belong to your instance (these have the process names: jlaunch or jcontrol).

3.

Check whether your system started correctly. To do this, log on to your SAP system and check in the SAP MC or SAP MMC that all processes are running. a)

Log on to your SAP system.

b)

In the SAP MC check the Process List of every instance, if every process is running. You can drill down to the AS ABAP WP Table or AS Java Process Table and find out the status of the regarding processes.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

97

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Task 3: (Optional) stopping from the Command Line Stop the SAP system using a command call. 1.

To do this, log on to the server for your training system with the Terminal Server Client. Log on with the user adm and the password, that was given to you. a)

2.

Check whether your SAP system is running at operating system level. a)

3.

Use the tool specified by the instructor to create a connection to your server. Log on with the user adm and the password assigned for your user.

You can do this, for example, by executing the Process Explorer program to display an overview of operating system processes or the SAP MC or SAP MMC.

Use the sapcontrol command to stop the entire SAP system. a)

In command prompt, enter the command sapcontrol -user adm -nr -function StopSystem ALL to stop your system. Replace the specifications in the angled brackets with the values for your system. For example, sapcontrol -user dccadm password -nr 00 -function StopSystem ALL.

Task 4: (Optional) starting from the Command Line Start the SAP system using a command call. 1.

Check whether your SAP system has stopped at operating system level. a)

2.

Use the sapcontrol command to start the entire SAP system. a)

98

You can do this, for example, by executing the Process Explorer program to display an overview of operating system processes or the SAP MC or SAP MMC.

In command prompt, enter the command sapcontrol -user adm -nr -function StartSystem ALL to start your system. Replace the specifications in the angled brackets with the values for your system. For example, sapcontrol -user dccadm password -nr 00 -function StartSystem ALL.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Tools for Starting and Stopping SAP Systems

Lesson Summary You should now be able to: • Operate the tools to start and stop an SAP NetWeaver AS ABAP

Related Information •

•

http://www.sdn.sap.com/irj/scn, Quick Link http://scn.sap.com/docs/DOC8922: From here you can download the SAP Microsoft Management Console (SAP MMC) and access the document How to use the SAPControl Web Service Interface For further information about the SAP Management Console, refer to the following SAP Notes: – – – – – –

2013/Q1

SAP Note 936273: sapstartsrv for all platforms SAP Note 927637: Web service authentication in sapstartsrv as of release 7.00 SAP Note 823941: SAP Start Service on Unix SAP Note 995116: Backward porting of sapstartsrv for earlier releases SAP Note 1014480: SAP Management Console (SAP MC) SAP Note 927637: Web service authentication in sapstartsrv as of release 7.00

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

99

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Lesson: Tools for Starting and Stopping Lesson Overview This lesson presents the tools for the technical implementation of a start and stop process for SAP systems. The SAP Management Console (SAP MC) can be used for the start and stop process independently of the operating system.

Lesson Objectives After completing this lesson, you will be able to: • •

Operate the tools to start and stop SAP NetWeaver AS ABAP + Java Operate the tools to start and stop SAP NetWeaver AS Java

Business Example You are using an SAP NetWeaver Application Server with Java and different operating system platforms such as Microsoft Windows and UNIX. To start and stop the SAP systems you require information about the use of the available tools.

The SAP Management Console (SAP MC) As of SAP NetWeaver Release 2004, a new operating system-independent application is supplied with the SAP Management Console (SAP MC) (see SAP Notes 1014480 and 995116). This allows you to display monitoring information and perform administration tasks such as start and stop operations. The tool is a standalone Java application which can be started either as an applet or locally. The SAP MC is supplied as standard with the kernel and is ready for use without any additional installation. For the different operation systems, see SAP Note 93673. SAP MC is a Java application which is supplied as a Java applet as standard. You simply use a Web browser to do this.. To use the applet correctly, you require a JRE (Java Runtime Environment) of version 1.4 or higher. In addition, the corresponding Java plugin for the browser must be activated correctly. To start SAP MC after installing the corresponding SAP NetWeaver AS, enter the following URL in your browser: http://:513 Or, if you have configured https in sapstartsrv (see SAP Note 1036107): https://:514

100

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Tools for Starting and Stopping

Figure 30: Starting and Stopping with the SAP Management Console

The SAP MC allows you to start and stop all the SAP NetWeaver AS ABAP+Java instances as well as the Central Services. You can also display information about the instances of the SAP system and the employed database (name, manufacturer and name of the host on which the database is located). Starting and Stopping with the SAP Management Console). The SAP Management Console (SAP MC) indicates the status of all instances of the system using colors. The colors have the following meaning for the system or an instance: Gray Stopped Yellow Not fully running Green Fully running Red Errors

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

101

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Starting and stopping the database with the SAP Management Console and SAP Host Agent The SAP MC provides the possibility to start and stop the database. This function is not implemented in other tools such as the SAP Microsoft Management Console or sapcontrol. With tools such as sapcontrol the database is only started, when a PAS or AAS instance is started on the same computer on which the DB is installed too (Condition: DB belongs to the same SAP system as the instance). On the computer on which the DB of the SAP system is installed, a SAP Host Agent must be installed too. It starts and stops the DB and also provides monitoring data to the SAP MC using the operating system. The SAP MC receives the information from sapstartsrv, on which computer the DB runs and connects with the SAP Host Agent, which starts or stops DB through the Port 1128 (or 1129 for secure network communications). A stopped DB is displayed in “gray” and a started DB is displayed in “green”. If the DB is not started correctly, the DB symbol is displayed in “yellow”. Expand the DB icon and select the DB icon with the marking as in the Figure Stopping DB with SAP MC. You reach the context menu with the right mouse button and can start or stop the DB depending on its current status.

102

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Tools for Starting and Stopping

Figure 31: Stopping DB with SAP MC

Hint: In the SAP MC, if the DB is displayed in “blue”, then probably no SAP Host Agent is installed on the DB computer, or the SAP host Agent is an old version. Hint: Special features of SAP MaxDB: For an SAP MaxDB a user must be specified with a password(if SAP MaxDB runs on Windows), so that the state of the DB can be displayed and it can be started or stopped. If no user has been specified with a password, but this is needed, the DB is displayed in “blue”. To enter a user name, click on the “blue” DB icon, a popup will ask you for the user name and password. If the SAP system is started with the SAP MC, then the SAP Host Agent is called first so that it can start the DB if it is in the state Stopped. Then the instances of the SAP system can be started according to their priorities. Here, the communication takes place directly between the sapstartsrv processes. The SAP MC receives information regarding the status of each instance through direct communication with the relevant sapstartsrv. The instances with Priority 1 are started after the DB, although it would be possible to use these to start before the DB. The SAP MC has the Option to stop the DB as well when stopping the SAP system. If this is selected, then the DB from the SAP Host Agent stops when all instances are stopped.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

103

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Figure 32: Start sequence during the start with the SAP MC

The Figure Start sequence during the start with the SAP MC shows the start process of an SAP system with the instances of priority 1 and 3. The administrator has started the SAP MC through the sapstartsrv process of the instance with priority 1 (port 513) (solid line to the sapstartsrv). The SAP MC has received the information about all other sapstartsrv processes of the system and their ports, so has the SAP MC the connection to each sapstartsrv process of the SAP system (shown as a dashed line). Additionally SAP MC has received the information on which computer the DB is running and has opened the connection to the local SAP Host Agent (port 1128) (shown also as a dashed line). The lines to the sapstartsrv and to the SAP Host Agent are not technically different, the solid line symbolize only the call of the SAP MC.

104

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Tools for Starting and Stopping

If the administrator now selects the SID of the SAP system and with the right mouse button selects Start ... (individual step 1), then the following process runs: 1. 2. 3. 4. 5. 6.

The SAP Host Agent receives the command to start the database. The SAP Host Agent starts the DB if it is in the state “stopped”. The sapstartsrv of the instance with the priority 1 gets the command to start the instances according to their priority. The sapstartsrv of the instance with the priority 1 starts its instance. The sapstartsrv of the instance with the priority 1 triggers the sapstartsrv of the instance with the priority 3 to start its instance. The sapstartsrv of the instance with the priority 3 starts its instance.

On each computer on which an SAP instance was installed, a SAP Host Agent should be installed too (this is not shown in the figure above for reasons of clarity). The SAP MC connects with the SAP Host Agents of the individual instances and provides for them the information about memory, file system and operating system processes.

Starting and Stopping an SAP NetWeaver AS ABAP + Java When SAP NetWeaver AS ABAP + Java is started, the entire instance is always started. If the instance is started then the Java stack can be stopped and started again individually by the ABAP dispatcher.

Starting and Stopping instances of SAP NetWeaver AS ABAP + Java

Figure 33: Starting and Stopping instances of SAP NetWeaver AS ABAP + Java

Instances of SAP NetWeaver AS ABAP + Java can be can be started and stopped independently of the operating system using the SAP Management Console (SAP MC). For each instance, SAP MC displays information about the ABAP and Java stack processes (see figure: SAP Management Console: Process Information).

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

105

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Figure 34: SAP Management Console: Process Information

The SAP Management Console also allows you to display the trace files for the individual processes.. You can use these trace files to analyze problems (see figure: SAP Management Console: Trace Files). You can also use the SAP MC to evaluate the developer traces (as well as the log and trace files) (as with the previous lesson about the SAP MMC).

106

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Tools for Starting and Stopping

Figure 35: SAP Management Console: Trace Files

Stopping and Starting AS Java in an SAP NetWeaver AS ABAP + Java System

Figure 36: Stopping and Starting the Java Stack in an SAP NetWeaver AS ABAP+Java System

In the case of SAP NetWeaver AS ABAP + Java, it is possible to allow the ABAP stack to continue running, and only stop and then restart the Java stack. You do this using transaction SMICM. You can either start/stop the (local) instance onto which

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

107

Unit 4: Starting and Stopping SAP Systems

TADM10_1

you are logged in the transaction SMICM or start/stop all the instances in the (global) Java cluster (see figure: Starting and Stopping the Java Stack of an SAP NetWeaver AS ABAP + Java from transaction SMICM). Hint: Up to NetWeaver 7.0x, the Java dispatcher was also started or stopped at this point. The Java dispatcher was replaced by the ICM in SAP NetWeaver 7.1x systems or higher. However, in the above case, the ICM is not started or stopped because it does not belong to the Startup and Control Framework in an SAP NetWeaver ABAP + Java 7.3 system.

Figure 37: Starting and Stopping the Java Stack of an SAP NetWeaver AS ABAP+Java from Transaction SMICM

It is not possible, and also not useful, to stop only the ABAP stack and leave the Java stack started in the case of AS ABAP + Java.

108

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Tools for Starting and Stopping

Starting and Stopping an SAP NetWeaver AS Java

Figure 38: Starting and Stopping an SAP NetWeaver AS Java

SAP NetWeaver AS Java is started and stopped in the same way as SAP NetWeaver AS ABAP + Java usingf the SAP Management Console (see figure: Starting and Stopping SAP NetWeaver AS Java with the SAP Management Console).

Figure 39: Starting and Stopping SAP NetWeaver AS Java with the SAP MC

In SAP NetWeaver AS Java, the instance names are J.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

109

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

SAPControl SAPControl allows the Web services of the sapstartsrv processes to be addressed. SAPControl is part of the kernel, and is available on all operating systems. Calling sapcontrol without any other option provides the syntax description. The figure SAPControl: Syntax and Examples shows the basic structure of the syntax with some selected examples.

Figure 40: SAPControl: Syntax and Examples

In the first example “sapcontrol -user adm password -nr -function StartSystem LEVEL 2”, the Web method StartSystem is called with the parameter LEVEL and the value 2 for the level. As with the SAP MC, a sapstartsrv process that is used to start the instances is addressed. “LEVEL 2” means that all instances with priority 1 are started first (unless they are already running). In a AS ABAP+Java system, this is the Central Services instance. Then the central instance (and if relevant, the database) is started, but no further instances. It is not important whether the instances are running on the same or different hosts. With StartSystem LEVEL 3 (corresponds to StartSystem ALL), all the instances of the system are started according to their priority, unless they are already running. This is the same procedure used to start the system using the SAP MC. StopSystem LEVEL 2 means that all priority 3 and priority 2 instances are stopped if they are still running. StopSystem ALL has the same meaning as StopSystem LEVEL 1.

110

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Tools for Starting and Stopping

In the second example, “sapcontrol -prot PIPE -nr -function Start”, a Trusted Connection is used. No user name or password are specified because the operating system authentication as adm is sufficient. However, it is only possible to call Web methods for the local computer. In the example, the dialog instance (instance number 11) is started. The function StartSystem LEVEL 3 is not possible because StartSystem may have to communicate with systems outside the host, which is not permitted under Trusted Connections. This means only functions for instances are possible. Caution: Trusted Connection for Windows: -prot PIPE Trusted Connection for Unix: -prot NI_HTTP; this is the default value. See also SAP Note 927637 - Web service authentication in sapstartsrv as of release 7.00

Special Characteristics of Starting and Stopping Under Microsoft Windows With the Microsoft Windows operating system, you can use both the SAP Management Console and the Microsoft Management Console with an SAP plug-in (SAP MMC) to start and stop an SAP system. The SAP MMC allows you to start and stop all the instances of the SAP system as well as the Central Services. For some databases, you can also display administration information and the status of the database. Some database types can also be administered using the SAP MMC. The information displayed in the SAP MMC and the start and stop procedures are similar to the browser-based SAP Management Console (SAP MC). This is illustrated by the next two figures.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

111

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Figure 41: Starting/Stopping an SAP Net Weaver AS ABAP + Java under Microsoft Windows

112

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Tools for Starting and Stopping

Figure 42: Starting and Stopping an SAP NetWeaver AS Java under Microsoft Windows

Hint: In the environment of SAP NetWeaver AS Java development, there is a special Java development environment, which is installed locally on every PC. It usually consists of an SAP NetWeaver Developer Studio and an SAP NetWeaver AS Java as a test environment for Java developments. The SAP NetWeaver Application Server Java can be “restarted” from the SAP NetWeaver Developer Studio. Under Windows, the SAP system can also be started and stopped without a GUI by calling a command by means of the executable files startsap.exe and stopsap.exe. This can be done using a simple telnet access. To start an instance of the SAP system, open a telnet connection and enter the following command: startsap name= nr= SAPDIAHOST= To stop an instance of the SAP system, open a telnet connection and enter the following command: stopsap name= nr= SAPDIAHOST= For the SAPDIAHOST parameter, enter the name of the host on which the instance is to be started.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

113

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Special Characteristics of Starting and Stopping Under UNIX For SAP systems that are installed under UNIX, you run the scripts startsap and stopsap to initiate the start and stop processes. If multiple SAP instances are installed on one physical server, you add the instance name to the names of the scripts startsap and stopsap. The script startsap can be called with the following options: • • • •

DB: starts the database system R3: starts the instances and associated processes for the instance J2EE: starts the instances and associated processes for the instance ALL: starts the database system and the instance (default setting, can be omitted)

The script stopsap can be called with the following options: • • • •

DB: stops the database system via the script stopdb; R3: stops the instances of the SAP system; J2EE: stops the instances of the SAP system; ALL: stops the database system and the instance (default setting, can be omitted)

To start the SAP system, the script startsap calls the process sapstart with the start profile specified in the script in the variable START_FILES. The database and SAP instances can each be started and stopped separately with the options DB or R3, for example startsap R3 DVEBMGS00 or with the new style startsap -t R3 -i DVEBMGS00. You get help for startsap and stopsap with the –h option. Caution: The option J2EE can be used in the same way as the option R3. In the case of SAP NetWeaver AS ABAP + Java, both the ABAP stack and the Java stack are started and stopped.

114

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Tools for Starting and Stopping

Exercise 3: Tools for Starting and Stopping Exercise Objectives After completing this exercise, you will be able to: • Start and stop an SAP NetWeaver AS Java under Microsoft Windows

Business Example You are using an SAP NetWeaver Application Server with Java. There is a special tool for starting and stopping an SAP system under Microsoft Windows operating systems. This is the SAP Micrsoft Management Console. The operating system-independent SAP Management Console can be used on all operating systems.

Task 1: Stopping with the SAP Management Console Stop the SAP system using the SAP Management Console. 1.

Stop the SAP system using the SAP Management Console. To do this, log on to the server for your training system with the Terminal Server Client. Log on with the user adm and the password, that was given to you.

Task 2: Starting with the SAP Management Console Start the SAP system using the SAP Management Console. 1.

Start the SAP system using the SAP Management Console. Monitor the start of the processes in your system. Your instructor will provide you with the name of the server on which you can start the SAP MC.

2.

Check whether your system started correctly. To do this, log on to your SAP system and check in the SAP MC or SAP MMC that all processes are running.

Task 3: (Optional) stopping from the Command Line Stop the SAP system using a command call. 1.

To do this, log on to the server for your training system with the Terminal Server Client. Log on with the user adm and the password, that was given to you. Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

115

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

2.

Check whether your SAP system is running at operating system level.

3.

Use the sapcontrol command to stop the entire SAP system.

TADM10_1

Task 4: (Optional) starting from the Command Line Start the SAP system using a command call.

116

1.

Check whether your SAP system has stopped at operating system level.

2.

Use the sapcontrol command to start the entire SAP system.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Tools for Starting and Stopping

Solution 3: Tools for Starting and Stopping Task 1: Stopping with the SAP Management Console Stop the SAP system using the SAP Management Console. 1.

Stop the SAP system using the SAP Management Console. To do this, log on to the server for your training system with the Terminal Server Client. Log on with the user adm and the password, that was given to you. a)

Start a Web browser and enter http://twdfxxxx.wdf.sap.corp:5$$13 in the address bar (where xxxx stands for the number of the server assigned to your group and $$ represents the instance number). In the SAP MC, select the required system or individual instance, and choose the Stop function from the context menu (right mouse button). If you have selected Stop for your system, then a popup will appear with the question whether a hard or soft shutdown and whether the DB should be stopped (including Database). Select hard and do not stop the database. The system now requires you to authenticate your ID. To do this, enter the user adm with the password assigned for your user. Depending on whether you selected an individual instance or the SAP system, either an individual instance or the entire SAP system is stopped. Hint: You should always stop the instances regarding their reverse priority (first stop priority 3, last stop priority 1). The priority of an central services instance is 1 The priority of an PAS instance is 2, if a enqueue workprocess is configured on the PAS instance. The priority of all other instances is 3.

Task 2: Starting with the SAP Management Console Start the SAP system using the SAP Management Console. 1.

Start the SAP system using the SAP Management Console. Monitor the start of the processes in your system.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

117

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Your instructor will provide you with the name of the server on which you can start the SAP MC. a)

Start a browser on the host specified by your instructor and enter http://twdfxxxx.wdf.sap.corp:5$$13 in the address bar. Choose the node for the central services instance in the SAP Management Console tree. Select the desired instance and choose the Start function from the context menu (right mouse button). Start the PAS instance and the AAS instance in the same way. Hint: You should always start the instances regarding their priority. The priority of an central services instance is 1 The priority of an PAS instance is 2, if a enqueue workprocess is configured on the PAS instance. The priority of all other instances is 3. If you select the node of the SAP system in the tree of the SAP Management Console to start the system, you will be asked for a user of the database. Enter the appropriate user and PW, which was given to you by your trainer.

2.

Check whether your system started correctly. To do this, log on to your SAP system and check in the SAP MC or SAP MMC that all processes are running. a)

Log on to your SAP system.

b)

In the SAP MC check the Process List of every instance, if every process is running. You can drill down to the AS Java Process Table and find out the status of the regarding processes.

Task 3: (Optional) stopping from the Command Line Stop the SAP system using a command call. 1.

To do this, log on to the server for your training system with the Terminal Server Client. Log on with the user adm and the password, that was given to you. a)

Use the tool specified by the instructor to create a connection to your server. Log on with the user adm and the password assigned for your user.

Continued on next page

118

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Tools for Starting and Stopping

2.

Check whether your SAP system is running at operating system level. a)

3.

You can do this, for example, by executing the Process Explorer program to display an overview of operating system processes or the SAP MC or SAP MMC.

Use the sapcontrol command to stop the entire SAP system. a)

In the command prompt, enter the command sapcontrol -user adm -nr -function StopSystem ALL to stop your system. Replace the specifications in the angled brackets with the values for your system. For example, sapcontrol -user depadm password -nr 30 -function StopSystem ALL.

Task 4: (Optional) starting from the Command Line Start the SAP system using a command call. 1.

Check whether your SAP system has stopped at operating system level. a)

2.

Use the sapcontrol command to start the entire SAP system. a)

2013/Q1

You can do this, for example, by executing the Process Explorer program to display an overview of operating system processes or the SAP MC or SAP MMC.

In command prompt, enter the command sapcontrol -user adm -nr -function StartSystem ALL to start your system. Replace the specifications in the angled brackets with the values for your system. For example, sapcontrol -user depadm password -nr 30 -function StartSystem ALL.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

119

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Lesson Summary You should now be able to: • Operate the tools to start and stop SAP NetWeaver AS ABAP + Java • Operate the tools to start and stop SAP NetWeaver AS Java

Related Information •

•

http://www.sdn.sap.com/irj/scn, Quick Link http://scn.sap.com/docs/DOC8922: From here you can download the SAP Microsoft Management Console (SAP MMC) and access the document How to use the SAPControl Web Service Interface For further information about the SAP Management Console, refer to the following SAP Notes: – – – – –

120

SAP Note 936273: sapstartsrv for all platforms SAP Note 927637: Web service authentication in sapstartsrv as of release 7.00 SAP Note 823941: SAP Start Service on Unix SAP Note 995116: Backward porting of sapstartsrv for earlier releases SAP Note 1014480: SAP Management Console (SAP MC)

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: System Start: AS ABAP Logs

Lesson: System Start: AS ABAP Logs Lesson Overview In this lesson, you will become familiar with the most important log and trace files, in which the start of an ABAP-based SAP system is logged.

Lesson Objectives After completing this lesson, you will be able to: •

Use the AS ABAP start logs to analyze problems

Business Example Problems occurred when starting an SAP system. To correct these problems, the administrator analyzes logs and trace files that were generated during the system start.

Logging the Start Process The start process is an especially important phase, which is logged by the operating system, the SAP system, and the database. If the SAP system does not start up, you can find the relevant error message in the log files. It may be that there were problems starting the database, meaning that the SAP system could not subsequently be started.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

121

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Figure 43: Logging the Start Process in the SAP System

Logs about the start process of the SAP system are stored in the file system. If there are problems during the start, these logs can provide useful information such as error messages or problem descriptions. These files are stored in the home directory (DIR_HOME) of the relevant instance. The log files STDERR are created by sapstartsrv during the start process. The starting processes write to the individual files, depending on the sequence in which they are listed in the start profile. The contents of these log files therefore depends on the individual system setup, and could, for example, be as follows: • • •

STDERR1 Information about the start process of the database system. STDERR2 Information about the start process of the message server. STDERR3 Information about the start process of the dispatcher.

You can set the granularity of the logged information using the profile parameter rdisp/TRACE profile parameter. The possible values for this parameter are: • • • •

122

0: 1: 2: 3:

No trace Error messages Full trace. The trace entries depend on the SAP program that is being traced. As 2: but data blocks are also traced.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: System Start: AS ABAP Logs

The higher the trace level, the larger the amount of logged information, and therefore the larger the size of the files. You should therefore only increase the default value for short periods for problem analysis. The trace level can be set separately for individual work processes in the process overview (transaction SM50). The times in which the instance was started and stopped are logged on available.log.

Problem Analysis

Figure 44: Problem Analysis

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

123

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

If the SAP system does not start correctly, this can be due to a variety of reasons. To analyze the problem, proceed as follows: • • • • •

Check the error messages and warnings of the respective operating system with the corresponding operating system tools. Check the status of the respective database system using the error log files. Check the start logs in the SAP MC. To do this, select the relevant instance, and choose List Developer Traces in the context menu. Check the error files stderr that were created by the sapstartsrv process. Check the trace files of the individual SAP work processes: – – – –

dev_ms: Developer trace for the message server dev_rd: Developer trace for the gateway dev_disp: Developer trace for the dispatcher dev_w (m denotes the number of the work process): Developer trace for the work processes

If you can still log on to the SAP system, check the system log of the SAP system using transaction SM21.

124

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: System Start: AS ABAP Logs

Lesson Summary You should now be able to: • Use the AS ABAP start logs to analyze problems

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

125

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Lesson: Java Startup and Control Framework Lesson Overview The Java Startup and Control Framework coordinates the proper starting and stopping of the Java stack. It consists of the JStart processes (as the instance controller and server process) and the ICM. In an SAP NetWeaver AS ABAP+Java system, the ICM does not belong to the Java Startup and Control Framework. The functions of the processes are described in this lesson.

Lesson Objectives After completing this lesson, you will be able to: • •

Use the term Startup and Control Framework Describe the individual steps during the start and stop processes of a Java instance

Business Example Starting and stopping an SAP system is a basic task for administrators of SAP systems. Understanding the process flow of the start process is crucial to troubleshooting when start problems occur.

Startup and Control Framework SAP provides a separate Startup and Control Framework for SAP NetWeaver Application Server Java. This framework is used to start, stop, and monitor the Java stack processes within the SAP system (not the Central Services however). It consists of the following processes:

126

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Java Startup and Control Framework

JStart - Instance Controller: •

• • • •

The Instance Controller starts, stops, and monitors the processes of a Java instance – primarily the server and ICM process. SAP Signal Handling is implemented with the Instance Controller to forward the start and stop commands to the processes of the Java stack. The Instance Controller restarts terminated processes, ends hanging processes, and sends a shutdown signal to the processes of the Java stack. The Instance Controller reads the description of the instance from profile files. The Instance Controller starts the server processes and the ICM, as well as the processes for the offline deployment and the bootstrap. The Instance Controller creates a shared memory segment for the internal administration data of all processes.

JStart - Offline Deployment, Bootstrap, Server Process: •

2013/Q1

Other JStarts that act in the role for the offline deployment, the bootstrap or as a server process are started by the JStart (Instance Controller). The SAP JVM is loaded in the individual address space for this purpose. The parameterizing of the JVM is imported before the loading.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

127

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Start Process of a Java Instance

Figure 45: Starting with the Startup and Control Framework

Start procedure in the Startup and Control Framework; several “run-levels” are run at this point:

128

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Java Startup and Control Framework

(See also figure: Starting with the Startup and Control Framework) 1. 2. 3. 4.

The Instance Controller is started: The Instance Controller connects to the Central Services instance. The Instance Controller reads the file instance.properties in the cluster directory. Run-level 1: The Instance Controller reads configuration files from the file system (different .properties files and for example the instance profile) and starts a jstart process that transfers the offline deployment (if an offline deployment is required, for example when importing particular Support Packages). The jstart process finishes after the offline deployment. jstart requires files from the Cluster/bootstrap directory to start.

5.

Run-level 2: The Instance Controller reads configuration files from the file system (different .properties files and for example the instance profile) and starts a jstart process that carries out the bootstrap process. The bootstrap process synchronizes data from the database to the file system. For example, instance.properties is regenerated (it contains information about, among other things, the amount of server processes to be started) and the directories for the server processes server are synchronized. The bootstrap process also synchronizes all required binaries for the Java nodes from the database to the file system. This is necessary, since the Class Loading is performed using the file system in the Java environment. The database always contains the current (deployed) binaries and properties and distributes these to every Java node when starting. The jstart process finishes after the bootstrap process. jstart requires files from the Cluster/bootstrap directory to start.

6. 7.

The Instance Controller reads the file instance.properties in the cluster directory again. Run-level 3: The Instance Controller reads configuration files from the file system (different .properties files and for example the instance profile) and starts the ICM and for each server process a jstart process. The jstart processes require the binaries from the Cluster/bin directories to start. These jstart processes run with the JVM parameters (usually several gigabytes of memory). You will get to know the settings for this in a later unit. The server processes connect to the database.

The Instance Controller monitors the Java instance processes during their runtime, restarts terminated processes, ends hanging processes, and sends the shutdown signal to the ICM or the server processes.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

129

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

The profile files are located on the operating system in the directory DIR_PROFILE (Microsoft Windows: :\usr\sap\\SYS\profile or UNIX: /usr/sap//SYS/profile) and are generated at installation time. The following profile files exist: the default profile (Default.pfl) and the instance profile (__). Note: The Central Services profiles are imported when the Central Services are started.

Figure 46: Profiles

130

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Java Startup and Control Framework

Stop Process of a Java Instance

Figure 47: Stopping with the Startup and Control Framework

1. 2. 3.

The Signal Handler of the Instance Controller receives a stop signal from the sapstartsrv. The Instance Controller passes the signal on to all running server processes via named Pipe and waits until they are stopped. When the server processes of this instance are all stopped, the Instance Controller sends the stop signal to the ICM. In an SAP NetWeaver AS ABAP+Java system, the ICM does not belong to the Startup and Control Framwork; therefore, the ICM is not stopped by the Instance Controller at this point either.

If a soft shutdown is triggerd, the server process enters the state Preparing to stop and stays in this state until all user sessions are ended. If there is no more user session, the server changes his state to Ready to stop and continues the stop process as usual.

JSmon The JSmon tool can be used to monitor the Instance Controller. JSmon belongs to the kernel and is located in the kernel directory.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

131

Unit 4: Starting and Stopping SAP Systems

TADM10_1

JSmon can be started with the command JSmon pf=. JSmon provides an administration interface for elements in the Java cluster that can be called from the operating system.

Figure 48: JSmon

In the Process menu option, processes can be started, stopped or their trace level can be changed. In the Instance menu option, an instance can be started or stopped. The Instance Controller is not stopped at this point; that is, the Instance menu option refers only to the processes of the Startup and Control Framework. In an SAP NetWeaver AS ABAP + Java system, this means that neither the ABAP dispatcher with its work processes nor the ICM is stopped; only the server processes are stopped. In the test menu option, parameters can be evaluated. Thus, test get rdisp/TRACE supplies the value of the set trace level. Caution: This evaluation refers to the parameters of the default and instance profiles for the start time of jsmon. Another useful command is repeat. You can use repeat process view to monitor the start process of an instance very effectively. The commands can also be shortened so long as they are distinct; r p v has the exact same effect as rep proc view for example. Choose "Return" to exit repeat mode.

132

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Java Startup and Control Framework

Exercise 4: Java Startup and Control Framework Exercise Objectives After completing this exercise, you will be able to: • Identify the processes of the Startup and Control Framework at operating system level

Business Example Starting and stopping an SAP system is a basic task for administrators of SAP systems. To understand parameter maintenance, it is important to understand how parameters are transferred to Java instances.

Task 1: Startup and Control Framework The Startup and Control Framework consists of ICM (icman on OS level) and JStart processes. How many ICM and JStart processes exist on your host? 1.

Log on to the operating system of your host and display the process overview.

Task 2: JSmon Start the JSmon tool and display the Java processes of the PAS that are started.

2013/Q1

1.

Log on to the operating system as for task 1. Navigate to the profile directory and open a command prompt there (cmd). Enter the command jsmon pf=.

2.

Display all the processes of your PAS with the command process view.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

133

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Solution 4: Java Startup and Control Framework Task 1: Startup and Control Framework The Startup and Control Framework consists of ICM (icman on OS level) and JStart processes. How many ICM and JStart processes exist on your host? 1.

Log on to the operating system of your host and display the process overview. a)

Follow the instructions of your instructor to log on to the operating system. You can obtain an overview of the started processes in the Task Manager on your host. Open the Task Manager by right-clicking on the taskbar at the bottom of the screen and choosing Task Manager. Open the Processes tab page, and ensure that you are viewing all processes of the instances on your host (select “Show processes from all users”). Sort by the column User Name and search for the processes icman and JStart. You have to search for the user name SAPService e.g. SAPServiceDEP because on windows OS the processes are started from the User SAPService instead of adm. You will find an ICM process for each Java PAS or AAS instance (that is 2 x icman) and a JStart for each server process (that is 2) and Instance Controller (that is 2) started.

Task 2: JSmon Start the JSmon tool and display the Java processes of the PAS that are started. 1.

2.

Log on to the operating system as for task 1. Navigate to the profile directory and open a command prompt there (cmd). Enter the command jsmon pf=. a)

Navigate to the directory d:\usr\sap\\SYS\profile and open a command prompt there using the context menu available by right-clicking.

b)

Enter the command jsmon pf=. You can find the instance profile under: d:\usr\sap\\SYS\profile\__.

Display all the processes of your PAS with the command process view. a)

134

There you see all the processes with their status.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Java Startup and Control Framework

Lesson Summary You should now be able to: • Use the term Startup and Control Framework • Describe the individual steps during the start and stop processes of a Java instance

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

135

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Lesson: Logs of the Start and Stop Processes of SAP NetWeaver AS Java Lesson Overview The start process of an SAP system is a critical process. If problems occur during this phase, you should be familiar with the relevant log and trace files. This lesson focuses on the most important logs of an SAP NetWeaver AS Java.

Lesson Objectives After completing this lesson, you will be able to: • •

Find the storage locations of trace and log files of the Startup and Control Framework. Name the most important trace and log files of the Startup and Control Framework and review their content.

Business Example The start process of an SAP system is a critical action. If problems occur during it, the administrator must be familiar with the most important logs that are written during the start process. The administrator uses these to perform an error analysis, identify the cause, and solve the problem as quickly as possible. These files are also used for error logging during operation.

Log and Trace Files In the case of an error or unexpected behavior of the Startup and Control Framework, it is important to check the following trace and log files: • • • • •

136

dev_jstart dev_, such as dev_server0 jvm_.out, such as jvm_bootstrap.out std_server.out, e.g. std_server0.out log_bootstrap.log, e.g. log_bootstrap.0.log

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Logs of the Start and Stop Processes of SAP NetWeaver AS Java

Figure 49: Log Files for Starting and Stopping

The trace and log files are stored in the work directory of an instance. This directory is called /usr/sap///work (UNIX) and analogously in the Microsoft Windows environment. dev_jstart is the trace file for the Instance Controller. dev_jstart is the most important trace file for problem messages when starting NetWeaver AS Java. Current messages are written at the end of the file. dev_ is the trace file for the server processes, the ICM and so on. The trace file dev_ is written for each process started and thus for each ICM and server process. jvm_.out is the output file for the Java Virtual Machine (JVM). Each node (except ICM) process represents a Java node such as a bootstrap or a server and therefore a JVM. The output of a JVM is forwarded to the file jvm_.out in the work directory of a Java instance. std_server.out is the default output files for the started managers and services of the the corresponding nodes.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

137

Unit 4: Starting and Stopping SAP Systems

TADM10_1

For most of the log files listed above, you will also find log files in the work directory with the ending ., with older versions of the files, which can also often be used for troubleshooting. In the start process of an instance, the files mentioned above are rewritten and the file names are changed from x. to x.. The number of the old versions complies with the parameter jstartup/keep_old_logfiles (default = 2). Beside the node names for ICM and Server there are also developer traces for data collections (datcol). In case of start problems, the data collector collects information about the problem and write these information in his developer traces.

Figure 50: Evaluate log files with the SAP MMC

The developer traces from the work directory can also be evaluated easily with the SAP MC or SAP MMC. See the above figure. The analysis displays the Error messages from the dev_ files (as well as other messages from the log and trace files that you will get to know in the Monitoring unit. Warnings or other lines from the dev_ files may also be displayed.

138

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Logs of the Start and Stop Processes of SAP NetWeaver AS Java

Exercise 5: Logs of the Start and Stop Processes of SAP NetWeaver AS Java Exercise Objectives After completing this exercise, you will be able to: • Name the most important logs for the start/stop processes of an SAP NetWeaver AS Java

Business Example The start process of an SAP system is a critical action. If problems occur during it, the administrator must be familiar with the most important logs that are written during the start process. The administrator uses these to perform an error analysis, identify the cause, and solve the problem as quickly as possible.

Task: Start Logs Check the most important logs that are written when starting an SAP NetWeaver AS Java.

2013/Q1

1.

List the most important log files that are written when starting and stopping.

2.

Open the most important log files (see task 1) and perform a time-based search for errors.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

139

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Solution 5: Logs of the Start and Stop Processes of SAP NetWeaver AS Java Task: Start Logs Check the most important logs that are written when starting an SAP NetWeaver AS Java. 1.

List the most important log files that are written when starting and stopping. a)

The most important logs are: • • • •

2.

140

dev_jstart dev_, such as dev_icm std_.out, such as std_server0.out jvm_.out, such as jvm_bootstrap.out

Open the most important log files (see task 1) and perform a time-based search for errors. a)

Start the Terminal Server Client, enter the physical host name under Server and then choose connect. Log on to the operating system as the adm user. Open an Explorer window, and navigate to the following directory: D:\usr\sap\\\work.

b)

Open the relevant files and scroll to the end. Check the entries since the last start of the system.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Logs of the Start and Stop Processes of SAP NetWeaver AS Java

Lesson Summary You should now be able to: • Find the storage locations of trace and log files of the Startup and Control Framework. • Name the most important trace and log files of the Startup and Control Framework and review their content.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

141

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Lesson: Appendix: Downtime Management Lesson Overview This lesson, gives you an overview of workmode management.

Lesson Objectives After completing this lesson, you will be able to: •

Plan and schedule downtimes in your SAP Systems using the SAP Solution Manager.

Business Example You want to get a general survey about the system downtimes in your system landscape.

Introduction Within SAP Solution Manager you can use work modes to plan, notify, and execute work modes for technical systems, databases, technical scenarios, instances and logon groups. On the one hand Work Mode Management is used to define Business Work Modes, which helps you to adapt the monitoring thresholds of the involved systems to the current system load. On the other hand you can use Technical Work Modes. This helps you to inform users of planned downtime and maintenance windows for activities like: • • • • •

Patch upgrades Upgrades Database, hardware, or operating system maintenance Configuration or customizing changes Migration

The types of work modes are:

142

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Appendix: Downtime Management

Available work modes Area

Type

Description

Business

Peak Business Hours

Work mode during which the system is technically up and you have access. Most users are logged on to the system and load peaks are expected.

Business

Non-Peak Business Hours

Work mode during which the system is technically up and you have access. Fewer users are logged on to the system, and load peaks are not expected.

Business

Non-Business Hours

Work mode during which the system is technically up and you have access. Most users are not logged on to the system and load peaks are not expected

Technical Planned Downtime

Work mode during which the system is technically down and you do not have access. System administrators can use this work mode to perform planned administration tasks that can only be performed during downtime.

Technical Maintenance

Work mode during which the system is technically up and you have no access. System administrators can use this work mode to perform planned administration tasks that can only be performed during maintenance.

You must plan your downtime and ensure that: • •

Downtime does not occur during critical and peak hours of system availability Downtime does not have any impact on the Service Level Agreement (SLA) and avoids any penalty

Using technical Work Modes for Downtime Management The work mode management comprises all tasks to handle downtime management in your system landscape. These are: • • • • •

2013/Q1

Downtime Planning Notification Management Alert Management Task Management Execution of the Downtime

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

143

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Figure 51: Overview: Downtime Management

To create work modes proceed as follows:

144

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Appendix: Downtime Management

Figure 52: Create a work mode

1. 2. 3.

Within SAP Solution Manager System call the transaction SM_WORKCENTER Choose the work center Technical Administration Choose Work Mode Management from the navigation area and a component type within the Type Selection area Hint: In the Detailed Selection area, you can select a predefined tab or choose New Query to create your own selection

4. 5. 6.

2013/Q1

In the tabular view, select the technical component you want to create a work mode for. Choose Work Mode Management Start Embedded or Start New Window and select the component from the list. Choose the button Schedule Work Mode(s)

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

145

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 4: Starting and Stopping SAP Systems

TADM10_1

For all work mode types you can enter the following information: • • • • • •

Enter a title for the work mode Select the status Active or Inactive Select a category (for technical work modes to specify the kind of planned downtime or maintenance) Select a start date/time and an end date/time Enter a reason for the work mode and the business impact on the description tab define templates and specify recurrent work modes

Figure 53: Technical work mode functions

If you are using the work modes for planning a downtime for the selected component you have the following additional options:

146

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Appendix: Downtime Management

In the tab execution: • • •

Check the Status of the Component (from CCMS) Direct Physical Execution (using SAPControl or SAP NetWeaver Adaptive Computing Controller Tool) Support Execution through creation of Tasks from suitable Task Templates which creates tasks for the specified user in their task inbox within the work center Technical Administration → Task Inbox

In the tab Notification Management: • • • • •

Texts to be sent in notifications for this Work Mode/Sequence of Work Modes which is E-Mails, sms and system message Add receipts from the system settings Add receipts especially for this technical work mode Release scheduled notification Send Instant Notification

In the tab CCMS Monitoring Settings: •

Set the Status of CCMS based Monitoring like Monitoring Pause or Suppress Alerts.

More information can be found in the course SM100.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

147

Unit 4: Starting and Stopping SAP Systems

TADM10_1

Lesson Summary You should now be able to: • Plan and schedule downtimes in your SAP Systems using the SAP Solution Manager.

Related Information •

148

SAP Education Course SM100 - SAP Solution Manager Operation and Configuration

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Unit Summary

Unit Summary You should now be able to: • Describe the process of the start procedure of an SAP system • Describe the structure of the file system for SAP instances • Describe the general start process for an SAP NetWeaver AS ABAP. • Describe the general start process for an SAP NetWeaver AS ABAP+Java. • Describe which profiles are evaluated. • Describe the sequence in which the components of an SAP system and started and stopped • Describe the general start process for an SAP NetWeaver AS Java • Describe the general start process for an SAP NetWeaver AS ABAP + Java • Operate the tools to start and stop an SAP NetWeaver AS ABAP • Operate the tools to start and stop SAP NetWeaver AS ABAP + Java • Operate the tools to start and stop SAP NetWeaver AS Java • Use the AS ABAP start logs to analyze problems • Use the term Startup and Control Framework • Describe the individual steps during the start and stop processes of a Java instance • Find the storage locations of trace and log files of the Startup and Control Framework. • Name the most important trace and log files of the Startup and Control Framework and review their content. • Plan and schedule downtimes in your SAP Systems using the SAP Solution Manager.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

149

Unit Summary

150

TADM10_1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Test Your Knowledge

Test Your Knowledge 1.

When you start an SAP system without an ABAP stack, the database is started only after the Java instances. Determine whether this statement is true or false.

□ □ 2.

True False

In the case of SAP NetWeaver AS Java, it is not possible to stop individual instances under a UNIX operating system. Determine whether this statement is true or false.

□ □ 3.

True False

. Log information for the dispatcher is stored in the file You can control the granularity of the logged information using the profile parameter . There are trace levels; error by default. messages and warnings are displayed at level Fill in the blanks to complete the sentence.

4.

The most important trace and log files are stored in the work directory of each instance, that is, for example, under /usr/sap//DVEBMGS00/work. Determine whether this statement is true or false.

□ □

2013/Q1

True False

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

151

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Test Your Knowledge

TADM10_1

Answers 1.

When you start an SAP system without an ABAP stack, the database is started only after the Java instances. Answer: False The database is always started before the PAS or AAS, or must be available before these instances are started. The Central Services instance is started before the database if the database is not running. The Central Services instance can also be started after the database, for example if the database is already running.

2.

In the case of SAP NetWeaver AS Java, it is not possible to stop individual instances under a UNIX operating system. Answer: False You can stop individual instances using the command stopsap R3 or stopsap J2EE or simply using the SAP MC.

3.

Log information for the dispatcher is stored in the file dev_disp. You can control the granularity of the logged information using the profile parameter rdisp/TRACE. There are four trace levels; error messages and warnings are displayed at level 1 by default. Answer: dev_disp, rdisp/TRACE, four, 1

4.

The most important trace and log files are stored in the work directory of each instance, that is, for example, under /usr/sap//DVEBMGS00/work. Answer: True All developer traces and all important start files are stored in the work directory of each instance.

152

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit Summary

153

TADM10_1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

Unit Summary

154

TADM10_1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 5 Introduction to System Configuration Unit Overview In this unit, you will learn how you can use profile parameters to configure an SAP system. This unit introduces the configuration and administration tools of AS Java and describes their application areas. Selected settings for Java instances and the Central Services are presented.

Unit Objectives After completing this unit, you will be able to: • • • • • • • • •

Determine the configuration of profile parameters Adjust the profile parameters using profiles Set up a dynamic switch of work process types using operation modes Name various configuration and administration tools for SAP NetWeaver AS Java Describe the primary usage areas of configuration and administration tools Maintain settings for the SAP NetWeaver AS Java with the Config Tool Display system properties in the SAP NetWeaver Administrator Get an overview of the Configuration Wizard Check and maintain properties of the Central Services

Unit Contents Lesson: How the System Evaluates Its Parameters ........................... 157 Exercise 6: Configuration of Profile Parameters ........................... 163 Lesson: How to set Profile Parameters .......................................... 166 Exercise 7: Maintaining the System Parameters........................... 171 Lesson: Setting up Operation Modes ............................................ 177 Exercise 8: Setting up Operation Modes .................................... 189 Lesson: Overview of the Administration Tools .................................. 194

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

155

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 5: Introduction to System Configuration

TADM10_1

Exercise 9: Calling the Administration Tools ................................ 209 Lesson: Basic Configuration of AS Java with the Config Tool ................ 213 Exercise 10: Configuration with the Config Tool............................ 229 Lesson: Configuring AS Java with SAP NetWeaver Administrator........... 241 Exercise 11: Configuring AS Java with SAP NetWeaver Administrator . 243 Lesson: Further Configuration Activities ......................................... 247 Exercise 12: Further Configuration Activities ............................... 253

156

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: How the System Evaluates Its Parameters

Lesson: How the System Evaluates Its Parameters Lesson Overview This lesson explains the order in which the system evaluates profile parameters and where these parameters are stored.

Lesson Objectives After completing this lesson, you will be able to: •

Determine the configuration of profile parameters

Business Example You want to determine the profile parameters for your SAP system.

Configuration of Profile Parameters The individual instances and the SAP system are configured using profile parameters. The default values for these parameters are defined in the program code of the kernel.

Figure 54: Assigning the Profile Parameters

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

157

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 5: Introduction to System Configuration

TADM10_1

You can change these default values using the profile files, which are read when an instance is started. These profile files are created during the installation of the system and can also be edited later. As the profile files are only read when the system is started, you must restart the instance or the entire system after changing individual parameters. Dynamic switching while the system is running is only possible for a small number of profile parameters.

Figure 55: Profile Files at Operating System Level

The profile files are automatically created during installation. After installation is complete, the profile files are stored at operating system level in the directory: \usr\sap\\SYS\profile. This directory can be read by all instances of an SAP system using the share or mount technique. The SAP system has two or three types of profiles. These are: • • •

Start profile (only until release SAP NetWeaver 7.0x) Default profile Instance profile

In principle, you can change these files with operating system tools (editors). In the process, users must themselves ensure that the changes are performed correctly. Parameters that are set incorrectly can lead to the system not starting. It is far more convenient and safer to change the profile parameters using the tools in the SAP system.

158

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: How the System Evaluates Its Parameters

Figure 56: Profile Files: Overview

The instance-specific start profile (START_), specifies which processes are to be started for each instance. These are, for example, the message server and the dispatcher. From Release SAP NetWeaver 7.10, the start profile is integrated in the instance profile. There is only one default profile (DEFAULT.PFL) for each SAP system, and it is read by all instances. It contains system-wide settings such as the system name, the name of the database server, the name of the enqueue server, or also the default logon client. The instance profile (__) defines parameters that apply for one instance, such as the number and type of work processes, or the definition of the size and allocation of the main memory area used by the SAP system. The instance profile is therefore instance-specific. From Release SAP NetWeaver 7.10, the start profile is integrated in the instance profile.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

159

Unit 5: Introduction to System Configuration

TADM10_1

Figure 57: View of the Profile Parameters

The current values of the profile parameters can be displayed in the system. There are two ways to do this: Transaction RSPFPAR (can also be run as a report with the same name) and transaction RZ11. Both functions display the profile parameters for the instance in which the user is currently logged on. Transaction RSPFPAR displays a list of all instance-specific profile parameters, which is updated with the system-wide parameters. You can restrict this list to specific parameters. A table displays the system default value for the individual parameters as defined in the program code of the kernel or in the default profile. If the default value is overridden in the instance profile or dynamically, the table also shows the user-defined value. A short description and, if required, documentation for the parameters can also be displayed. Transaction RZ11 displays information and documentation for individual profile parameters. It also shows whether the parameter can be changed while the system is running with the DynamicallySwitchable indicator. Note: In the TPFYPROPTY table, all dynamically switchable profile parameters are identified with the Dynamic indicator. You can use transaction SE16, for example, to display this table. Outside the SAP system, you can display the values of the profile parameters at operating system level using the user adm and the program sappfpar. You can display the current value of a parameter with sappfpar . The command sappfpar all returns a list of all parameters. You can check the parameters that are set using sappfpar check. The command sappfpar help returns a short overview of possible options.

160

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: How the System Evaluates Its Parameters

You can also specify an instance profile, an instance number, or the SAP system name with this command using the options pf=, nr=, or name=. Hint: Note that to evaluate of profile parameters using the tools described above, some profile parameters are the same system-wide, while others can be set differently for each instance. Transaction RSPFPAR displays the configuration of the instance on which you are running the report.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

161

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 5: Introduction to System Configuration

162

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

TADM10_1

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: How the System Evaluates Its Parameters

Exercise 6: Configuration of Profile Parameters Exercise Objectives After completing this exercise, you will be able to: • Determine the configuration of profile parameters

Business Example You want to determine the profile parameters for your SAP system.

Task: Determine Values of Profile Parameters Determine the values of a number of profile parameters. 1.

Determine the values of the following profile parameters: Name of the application server, number of work processes on the PAS instance (dialog, batch, enqueue, update, spool), maximum runtime of a program in the dialog.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

163

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 5: Introduction to System Configuration

TADM10_1

Solution 6: Configuration of Profile Parameters Task: Determine Values of Profile Parameters Determine the values of a number of profile parameters. 1.

Determine the values of the following profile parameters: Name of the application server, number of work processes on the PAS instance (dialog, batch, enqueue, update, spool), maximum runtime of a program in the dialog. a)

You can determine the values of profile parameters by running the report RSPFPAR (with transaction SA38 or transaction RSPFPAR). The parameter names are as follows: Name of the local application server: rdisp/myname. Number of work processes on the central instance: Dialog:

rdisp/wp_no_dia

Batch:

rdisp/wp_no_btc

Enqueue:

rdisp/wp_no_enq

Update:

rdisp/wp_no_vb

Spool:

rdisp/wp_no_spo

This parameter limits the maximum runtime of a process step within a dialog process: rdisp/max_wprun_time.

164

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: How the System Evaluates Its Parameters

Lesson Summary You should now be able to: • Determine the configuration of profile parameters

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

165

Unit 5: Introduction to System Configuration

TADM10_1

Lesson: How to set Profile Parameters Lesson Overview In this lesson, you will learn how you can change the values of profile parameters.

Lesson Objectives After completing this lesson, you will be able to: •

Adjust the profile parameters using profiles

Business Example You are an administrator, and want to adjust the configuration of the profile parameters.

Administering and Maintaining Profiles If you want to change profile parameters, you can make these changes using operating system-specific editors. However, this procedure has certain dangers, as the user must ensure that the changes are performed, and also documented, correctly. Incorrectly set parameters can prevent an instance starting. The SAP system therefore provides integrated profile administration and parameter maintenance.

166

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: How to set Profile Parameters

Figure 58: Profile Administration

Profile administration in the SAP system offers a number of advantages to the user: • • • •

Central administration and maintenance of the instances Changes in profiles checked for consistency Administration of multiple versions of a profile Comparison of the actively used profile and the profile stored in the database Caution: Before you make changes to the profile files, create backups. If an error should occur, you can then start the SAP system with the restored files and perform troubleshooting.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

167

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 5: Introduction to System Configuration

TADM10_1

Figure 59: Profile Maintenance 1/2

After installation, the profile parameters are, at first, only present at operating system level. To use the profile administration of the SAP system, the profiles must be imported into the database. During this import, the system performs a consistency check and a check of the way in which the parameters interact. Changes to profile parameters can then be performed in the SAP system, with the previously mentioned advantages. These changes are then stored in the database, and written back to file level. The changes only take effect when they are read by the system; that is, at a restart of the system. You 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 individual profile parameters. There are three different levels for maintaining the profiles. The administration data contains the type of profile (start, default, or instance profile), a short description, the path of the file, the name of the instance, and the time of the last activation. Start profiles exist only until release SAP NetWeaver 7.0x. At higher releases, the start profile is integrated in the instance profile. You can perform the maintenance of the parameters of the individual profiles through either basic maintenance or extended maintenance. Basic maintenance allows you to adjust the most important parameters and supports the user through the use of logical descriptions. Extended maintenance displays the unformatted content

168

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: How to set Profile Parameters

of the profile; that is, the technical names of the profile parameters. In extended maintenance, you can not only change the values of individual parameters, but also add new parameters and delete existing parameters. The changes are stored in two steps. In the first step, the changes are temporarily copied when you choose Copy. The values are permanently saved to the database in a second step when you choose Save. The changes are therefore successfully saved to the database and must now be written at operating system level. This is done either automatically during saving by confirming the relevant query, or manually from the menu by choosing Profile → Activate.

Figure 60: Profile Maintenance 2/2

Changes to instance-specific profiles take effect after a restart of the corresponding instance. Changes to the default profile take effect only after a restart of all instances in the entire system. Changes to these files are, however, the exception rather than the rule. Hint: From release SAP NetWeaver 7.1 all the old versions of profile files will be stored also in the profile directory in the operating system, starting with .1. In previous releases, there was only an old version per profile that ends in .BAK.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

169

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 5: Introduction to System Configuration

TADM10_1

Consistency Check Additional functions available in transaction RZ10 are the consistency check and the comparison of profiles.

Figure 61: Profile Consistency Checks

During a consistency check, the system checks the syntax and the semantics for individual or for all profiles. The Utilities → Check all profiles option also contains a consistency check between the profiles of a type. This means that, for example, the system checks for the start profile or the instance profile whether only one message server is being started for each system. During the comparison of profiles, the system compares the profile that is in active use with the profile stored in the database. This comparison is automatically performed when an instance is started. If the system identifies a difference between the active profile and the profile stored in the database, the system displays a message in the Alert Monitor. You can view a change history of the parameters in transaction TU02 (Tools → Administration → Monitor → Performance → Setup/Buffers → Parameter Changes).

170

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: How to set Profile Parameters

Exercise 7: Maintaining the System Parameters Exercise Objectives After completing this exercise, you will be able to: • Adjust the system parameters using profiles

Business Example As an administrator, you are to adjust the configuration of the system parameters.

Task 1: Save Profile Files First back up the profile files. 1.

Save your “runnable” profile files in a backup directory. To do this, create a Backup directory under C:\Temp and copy all the profile files to this directory. Replace with the system ID of your SAP system.

Task 2: Import and Maintain Profiles Use transaction RZ10 (Tools → CCMS → Configuration → System Profile) to perform the following tasks. 1.

Import all the profiles into your SAP system.

2.

Change the values of the following parameters: Decrease the number of dialog work processes for the AAS instance by 2. Set the value for the maximum runtime of a process step to 750 seconds. To do this, you may need to add a new parameter to a profile. At the end of the exercise, save and activate your changes. Caution: Consider the profiles in which you want to make changes. The solution tells you the relevant parameters, but not which parameters you should enter in which profile.

3.

Check the number of work processes in the process overview and the maximum runtime for a process step.

4.

Check your changes in the profile files at operating system level. What do you still need to do in order that your changes take effect in the system? Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

171

Unit 5: Introduction to System Configuration

TADM10_1

Task 3: Activating the Changed Profile Parameters Check the changed system parameters after a system restart.

172

1.

Restart the system so that your changes are activated.

2.

Check your changes in the system again.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: How to set Profile Parameters

Solution 7: Maintaining the System Parameters Task 1: Save Profile Files First back up the profile files. 1.

Save your “runnable” profile files in a backup directory. To do this, create a Backup directory under C:\Temp and copy all the profile files to this directory. Replace with the system ID of your SAP system. a)

Log on to your server. Copy the profile files from the \usr\sap\\SYS\profile directory to the Backup directory.

Task 2: Import and Maintain Profiles Use transaction RZ10 (Tools → CCMS → Configuration → System Profile) to perform the following tasks. 1.

Import all the profiles into your SAP system. a)

You can import all the profile files together by choosing: Utilities → Import profiles → Of active servers. A check log displays the result of the import. The Back (F3) pushbutton takes you back to the Edit Profiles entry screen

2.

Change the values of the following parameters: Decrease the number of dialog work processes for the AAS instance by 2. Set the value for the maximum runtime of a process step to 750 seconds. To do this, you may need to add a new parameter to a profile. At the end of the exercise, save and activate your changes.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

173

Unit 5: Introduction to System Configuration

TADM10_1

Caution: Consider the profiles in which you want to make changes. The solution tells you the relevant parameters, but not which parameters you should enter in which profile. a)

To change the values of individual parameters, select the corresponding profile (default or instance profile): In the Profile field, choose the corresponding profile (DEFAULT or __) using F4 help. The system automatically fills the Version field with the most recent version. Then select the Extended maintenance radio button, and change the selected profile by choosing the Change icon. If you can't see a Change pushbutton in the next entry screen Profile '' Version '', select the Display Change pushbutton (Shift F8) to switch to change mode. Select the desired parameter and choose Change or double click the relevant parameter. To create a new parameter, select the line in which you want to add the parameter in the Profile '' Version '' entry screen. Then choose the Create Parameters (F5) pushbutton. . Hint: The parameter is inserted above the line you selected The required parameters are listed below: • •

rdisp/wp_no_dia rdisp/max_wprun_time

After you have made your changes, choose Copy and then Save. In the list view, choose Copy and then Back. Save the new version of the profile and confirm the activation of the profile in the dialog box.

Continued on next page

174

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: How to set Profile Parameters

3.

4.

Check the number of work processes in the process overview and the maximum runtime for a process step. a)

Check the number of processes by calling the server overview (Tools → Administration → Monitor → System Monitoring → Servers, transaction SM51), selecting the dialog instance, and then choosing Processes (Ctrl+Shift+F6).

b)

Check the maximum runtime of a process step by displaying the parameter with the transaction RZ11. In the Parameter Name field, enter rdisp/max_wprun_time, and choose the Display pushbutton. The Current Value field should still display the previous value 7200.

Check your changes in the profile files at operating system level. What do you still need to do in order that your changes take effect in the system? a)

Open the profile files at operating system level (in the directory \usr\sap\\SYS\profile with an editor, and use this to view the changes that have been made.

b)

Your changes to profile parameters will only take effect after a restart of the affected instance or the entire system.

Task 3: Activating the Changed Profile Parameters Check the changed system parameters after a system restart. 1.

Restart the system so that your changes are activated. a)

2.

2013/Q1

Log on to your server in the same way as you did in the exercises for the Starting and Stopping unit, and restart the system.

Check your changes in the system again. a)

Check the number of processes by calling the server overview (Tools → Administration → Monitor → System Monitoring → Servers, transaction SM51), selecting the dialog instance, and then choosing Processes (Ctrl+Shift+F6).

b)

Check the maximum runtime of a process step by displaying the parameter with the transaction RZ11. In the Parameter Name field, enter rdisp/max_wprun_time, and choose the Display pushbutton. The Current Value field should now display the value 750 that you entered.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

175

Unit 5: Introduction to System Configuration

TADM10_1

Lesson Summary You should now be able to: • Adjust the profile parameters using profiles

176

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Setting up Operation Modes

Lesson: Setting up Operation Modes Lesson Overview In this lesson, you will learn about the concept of operation modes. You will learn how to set up a dynamic switch of work process types using operation modes.

Lesson Objectives After completing this lesson, you will be able to: •

Set up a dynamic switch of work process types using operation modes

Business Example The configuration of the work processes using the profiles usually meets the requirements for day operation. The administrator can use operation modes to optimize the performance of the system for the different requirements during the day and during the night.

Concept of Operation Modes The demands of users on the SAP system vary during the course of the day. During the day, a large number of dialog users, who want to be served with high performance by the system, are working. Therefore, a large number of dialog work processes should be available for users during the day. During the night, however, only a small number of these dialog work processes are used, and more of the system can be used to process jobs.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

177

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 5: Introduction to System Configuration

TADM10_1

Figure 62: Concept of Operation Modes

The type and number of work processes for each instance is defined in the profiles. The distribution of work processes in the profiles is optimized for fast dialog response times; that is, there are usually lots of dialog work processes and a small number of background work processes. This means that during the night, system resources, such as the main memory, are tied to the dialog work processes, or are not fully utilized by the background processes, such as the CPU. It is therefore practical to define different types and numbers of work processes for these different demands on the SAP system. This is realized through the concept of operation modes.

178

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Setting up Operation Modes

Figure 63: Adjusting Instances to the Load Distribution

Using the operation modes, you can adjust the type and distribution of the work processes to the varying load distribution during the day. You can also adjust the distribution of the work processes to business requirements that only occur once. By defining operation modes, you cannot change the configurable number of work processes defined in the profiles, but only the type and distribution of the individual work process types within this configurable number. The switch between the work process types is performed dynamically during the runtime of the SAP system. The switch is triggered using a defined schedule. A reserved work process is not immediately terminated, but marked for switching. This means that certain delays may occur. This type change is logged in the system log. During the switch of the operation modes, neither the instance nor the affected work processes needs to be restarted. This means that the quality of the buffer of the SAP system is retained during an operation mode switch, and that the processing of the current request that is being processed by a work process is completed. The individual work processes retain their process ID after the switch. You can observe this in the process overview (SM50).

Setting Up Operation Modes The operation modes are set up in a number of steps.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

179

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 5: Introduction to System Configuration

TADM10_1

Steps to Configure Operation Modes • •

•

•

First, the operation modes are created as empty containers in transaction RZ04. Next, all active instances of the system are detected and the work processes defined in the instance profile are assigned to the operation modes as default values. You can now make allocations for the individual operation modes in the total number of work processes taken from the instance profile. The allocation should be made primarily between the dialog and background work processes. You then specify the periods for which the operation modes are valid and when the switch between the operation modes should occur in the time table (SM63).

Figure 64: Setting Up Operation Modes

180

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Setting up Operation Modes

Figure 65: Scheduling Operation Modes

If you do not define a timetable for normal operation, no switch of operation modes is made. The configuration in the instance profile remains active. The exception operation can only be defined as a unique event. You can trigger an operation mode switch from a program that you have written yourself using a function module (RZL_PERFORM_BA_SWITCH).

Dynamic and Reserved Work Processes in Mode Switching Two particular types of work processes are the reserved work processes and the dynamic work processes.

Reserved Work Processes The reserved work processes are always of type dialog. They are started by system start ( if they are defined through profile parameter rdisp/wp_no_restricted. They are not used in “normal” operation i.e. even if all dialog work processes are occupied and further requests are waiting in the dialog queue to be processed. These reserved dialog work processes are used, if all “normal” dialog work processes have the status

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

181

Unit 5: Introduction to System Configuration

TADM10_1

on hold. This is intended to avoid possible deadlocks, which could possibly occur otherwise. If all dialog work processes no longer have the status on hold, then the dialog work processes will become reserved work processes again.

Dynamic Work Processes Dynamic work processes as well as the reserved work processes are not used in “normal” operation. They are started through the ABAP dispatcher when they are needed and can be of any type. Dynamic work processes are started only if the profile parameter rdisp/dynamic_wp_check=TRUE is set. If the dynamic work processes are no longer needed, they will be stopped again and don not consume any system resources anymore. The dynamic work processes are started when all work processes of the same type have the status on hold. As with the reserved work processes deadlocks should be avoided. But it will take longer until they are available, because they have to be started first. However, they don’t consume any operating system resources if they are stopped. The number of dynamic work processes can be defined only indirectly. The profile parameter rdisp/wp_max_no=DEFAULT specifies that each instance have two dynamic work processes. This setting is recommended and if necessary make the adjustment to the number of the dynamic work processes through the operation mode switching. The number of dynamic work processes results from the difference between the configured value of the parameter rdisp/wp_max_no and the work processes configured through other parameters. If the constant value rdisp/wp_max_no is set and the number of work processes is changed through other parameters, then the parameter rdisp/wp_max_no must also be adjusted. With the setting DEFAULT always two work processes are set more than which are defined through other parameters.

Operation Mode Switching During the mode switching the allocation of the configurable work processes can be adjusted. If you don’t allocate all configure work processes to the different work process types, then the remaining work processes will become dynamic work processes.

182

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Setting up Operation Modes

Figure 66: Operation mode switching with dynamic and reserved work processes

The figure “Operation mode switching with dynamic and reserved work processes” shows that the reduction of dialog work processes by two, the reduction of reserved work processes by one and increase of Batch(background)processes by one results the following image by the operating type Night: a free dialog work process becomes a Batch work process, a free dialog work process and a reserved work process will be stopped, because they became dynamic work processes, because not all configurable work processes were distributed across different types. While switching to the operation mode day again a free Batch work process will become a dialogue and the two dynamic work processes will become a dialogue or a reserved work process.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

183

Unit 5: Introduction to System Configuration

TADM10_1

Figure 67: Work process distribution during mode switching

In transaction RZ04 is defined the mode switching and the work processes allocation. The figure “work process distribution in the mode switching” shows for the instance twdf1927_DCC_00 the example above. In night mode, two dialog work processes and a reserved work process are switched to the batch- and two dynamic work processes more. The configurable and maximum number of work processes cannot be changed. You cannot arbitrarily change the work process distribution.

184

Work Process Type

Type of Changeability (+ = increase number, - = reduce number)

Dialog

+: possible (at least 2D-WP remains) -: possible

Reserved

+: possible -: possible

Background

+: possible -: possible

Class A

defines the subset of the B-WPs that only process Class A jobs.

Update

+: possible, if there is at least 1 V-WP -: possible, if at least 1 V-WP remains

V2 Update

+: possible, if there is at least 1 V2-WP, -: possible, if at least 1 V2-WP remains

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

TADM10_1

Lesson: Setting up Operation Modes

Enqueue

+: possible, if there is at least 1 E-WP, -: possible, if at least 1 E-WP remains, You should only increase the number of E-WPs if this procedure is suggested by SAP Support.

Spool

cannot be changed

Sum

can be changed only indirectly

Configurable

cannot be changed

Maximum

cannot be changed

Note: Note the following: A change in the allocation should be made primarily between the dialog and background work processes. The time table (SM63) differentiates between normal operation and exception operation. A general time definition that applies almost all of the time is set using normal operation. In rare cases, in which a special distribution of the work processes for unusual system loads is required, they are defined using exception operation.

Figure 68: Process overview during the mode switching with dynamic and reserved work processes

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

185

Unit 5: Introduction to System Configuration

TADM10_1

The figure “Process overview during the mode switching with dynamic and reserved work processes” shows the impact of profile parameters and of the mode switching by day and by night. In the transaction SM50 you can see that the reserved work processes get the status reserved. The work processes which are switched into dynamic work processes and therefore were stopped are not visible, but you can see in transaction SM50 in the numbering of the work processes in the mode “Night” a Gap between the work processes two and five. Hint: The reserved work processes will be once listed separately in the textual area and will be calculated total in addition to the dialog work processes, but not under free.

Monitoring and Consistency Check The Control Panel (RZ03) allows you to monitor the instances and the operation modes and provides functions to: • • • •

Check the status of all instances and of the operation modes Manually switch operation mode Display an overview of the work processes Switch to the Alert Monitor

Figure 69: Control Panel (RZ03)

186

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Setting up Operation Modes

You can switch the operation mode either for all instances (Control → Switch operation mode → All servers) or for a selected instance (Control → Switch operation mode → Selected servers). You can first simulate the switch of operation modes (Control → Switch operation mode → Simulation). The system checks for which instances a switch can be performed. You can display a detailed analysis of the status of the individual instances by choosing Monitoring → Status Details. If it is not possible to switch between operation modes, this is usually due to inconsistencies in the SAP system. These inconsistencies can occur if the number of work processes is defined differently in different places in the system. These are the instance profiles at operating system level, the instance profile in the database, and the definition of the operation modes themselves.

Figure 70: Profile Consistency Checks

If, for example, the number of work processes in the profiles is changed, the system can no longer switch operation modes until after a restart of the instance. You must therefore adjust the configuration of the operation modes after any change to the work process distribution.

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

187

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 5: Introduction to System Configuration

188

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

TADM10_1

2013/Q1

TADM10_1

Lesson: Setting up Operation Modes

Exercise 8: Setting up Operation Modes Exercise Objectives After completing this exercise, you will be able to: • Set up a dynamic switch of work process types using operation modes

Business Example The configuration of the work processes using the profiles usually meets the requirements for day operation. The administrator can use operation modes to optimize the performance of the system for the different requirements during the day and during the night.

Task 1: Create Operation Modes Create operation modes using transaction RZ04 to perform the following steps. 1.

Create two operation modes, Day and Night.

2.

Now create a definition for the work process distribution for all instances of your system.

3.

Change the distribution of the work processes of your instances for each of the operation modes. Note that there should be at least two dialog and two background work processes in all operation modes.

Task 2: Schedule Operation Modes Schedule the operation modes that you have created. 1.

In the timetable, schedule the operation modes that you have created for normal operation.

Task 3: Manual Switch of Operation Modes

2013/Q1

1.

To observe the change in work process distribution when the operation mode is switched, switch to the Night operation mode manually in the Control Panel.

2.

How can you observe the change of the work process distribution?

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

189

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

Unit 5: Introduction to System Configuration

TADM10_1

Solution 8: Setting up Operation Modes Task 1: Create Operation Modes Create operation modes using transaction RZ04 to perform the following steps. 1.

Create two operation modes, Day and Night. a)

You can maintain operation modes in transaction RZ04 (Tools → CCMS → Configuration → Operation Modes/Instances). You can create operation modes by choosing the Create operation mode (F5) pushbutton. Enter the name of the operation mode and a short description and choose Save. Repeat the procedure for the second operating mode. When you have finished, you should see two operation modes in the input screen CCMS: Maintain Operation Modes and Instances.

2.

Now create a definition for the work process distribution for all instances of your system. a)

Switch to the Instances/Operation Modes view by choosing the Instances/operation modes (F6) pushbutton. This is identified by the line Productive instances and their WP distribution. You define work process distribution for all instances of your system by choosing Settings → Based on current status → New instances → Generate. Result: Two additional lines appear at the end of the input screen. Activate your entries by choosing the Save pushbutton.

3.

Change the distribution of the work processes of your instances for each of the operation modes.

Continued on next page

190

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

2013/Q1

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

TADM10_1

Lesson: Setting up Operation Modes

Note that there should be at least two dialog and two background work processes in all operation modes. a)

To change the distribution of the work processes for the operation modes of the instances, double click the operation modes entries. Start with the operation mode Day. You change and then save the distribution of the work processes in the dialog box: CCMS: Maintain Work Process Distribution. To do this, place the cursor in the column of the work process type that you want to change. You can change the number by choosing + and -. Do not forget to change the operation mode Night as well. The easiest way to do this is by using the pushbutton Other operation mode. To the right of the field for Operation Mode, press F4 to select the operation mode Night. Then save the work process distribution for both operation modes by choosing Save. After you have changed the distribution for all operation modes and instances, choose the Save pushbutton in the input screen CCMS: Maintain Operation Modes and Instances in the system function bar.

Task 2: Schedule Operation Modes Schedule the operation modes that you have created. 1.

In the timetable, schedule the operation modes that you have created for normal operation. a)

You can schedule operation modes using the operation mode calendar (Tools → CCMS → Configuration → Operation Mode Calendar, transaction SM63) or you can use the Back (F3) icon to navigate back to the entry screen of transaction RZ04. From there, select Operation mode → Timetable to navigate to transaction SM63. In the input template Display/Maintain Operation Mode Set, select the radio button Normal operation (24 hr), and choose the Change pushbutton. Select the start and end of the time interval for the operation mode Day by double-clicking the relevant line (you can recognize this because the line changes from blue to black). Choose the Assign pushbutton, and use F4 help to select the operation mode Day. Follow the same procedure to assign the operation mode Night. After you have assigned the entire 24-hour period to your operation modes, choose Save.

Continued on next page

2013/Q1

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

191

Unit 5: Introduction to System Configuration

TADM10_1

Task 3: Manual Switch of Operation Modes 1.

To observe the change in work process distribution when the operation mode is switched, switch to the Night operation mode manually in the Control Panel. a)

You can switch the operation modes manually in the Control Panel (Tools → CCMS → Control/Monitoring → Control Panel, transaction RZ03). As a first step, select the operation mode where you want to switch to, by choosing Choose operation mode. Select the operation mode and then Choose. In the input screen CCMS Control Panel: Display Server Statuses and Alerts, you can check this in the line Active op. mode: Night, and in the configuration message informing you that the operation mode and work processes are different. The switch is performed in a second step, by choosing Control → Switch Operation Mode → All Servers. Confirm the dialog box Switch all servers with Yes. You should then see no more configuration messages. That is, all process have been switched according to the configuration of this operation mode.

2.

How can you observe the change of the work process distribution? a)

192

Check the changed distribution of the work processes in the process overview (Tools → Administration → Monitor → System Monitoring → Process Overview, transaction SM50). This shows you that individual work process types have changed accordingly or that the number of the work processes has decreased, if you didn’t allocated all configurable work processes during the mode switching and so additional dynamic work processes have been configured (Sum