Startup Process

7/31/2019 Startup Process

1/33

1

6/7/2012

1

2

3

Agenda

4

5

Start up Procedure of EP

File System Layout

Directory Structure

Shutdown Procedure of EP

Startup control Frame Work


2/33

2

6/7/2012

Startup and Shut Down

After the installation, the SAPJ2EE Engine Dispatcher has been setup as an

NT Service so as to facilitate the automatic startup/shutdown of the portalsafter a system reboot. It also enables scripting the startup/shutdownsequence.The following sequence is to be maintained for starting and shutting downthe portal. Startup or shutdown of Web Server is not required as SAPJ2EEEngine servers as the Web Server.Startup

Oracle DatabaseSAPJ2EE Engine Dispatcher(also starts the Server and State Controller)

ShutdownSAPJ2EE Engine Dispatcher (also starts the Server and State Controller)

Oracle DatabaseSome scripts have been developed to automate the starting and shutdownof the portal by the operational personnel, like backup operators, etc.Note: There is no separate startup and shutdown for Enterprise Portal. EPContent can be accessed after Starting WEBAS JAVA


3/33

3

6/7/2012

Startup Sequence


4/33

4

6/7/2012

Startup Process

The starting of the system is performed in multiple steps, and is the

task of the operating system user adm :1. Starting the databaseThe database is the fundamental element of the entire SAP system. Thismust be in an operational state before SAP instances are started.2. Starting the Central Services and then starting the central instanceThe Central Services consist of the Java message server and the Java

enqueueserver. The dispatcher and server Java cluster elements connect to the Javamessage server during their own start process.After the Central Services have been started, the central Java instance isstarted with its dispatcher and servers. A Java instance is started and stoppedby the Java Startup and Control Framework.The Software Deployment Manager (SDM) is also started with the centralJava instance.3. Other Java dialog instances are started. When an instance is started, itsdispatcher and servers are started.


5/33

5

6/7/2012

Starting a Standalone Java System


6/33

6

6/7/2012

1

2

3

Agenda

4

5


File System Layout

Directory Structure




7/33

7

6/7/2012

Startup and Control Framework

JControlJControl starts, stops, and monitors the processes of a Java instance .primarily the server and dispatcher processes. SAP Signal Handling isimplemented with JControl to forward the start and stop commands to a Java instance.JControl restarts terminated processes, ends hanging processes, and sends ashutdown signal to Java instances.JControl reads the description of a Java instance from profile files.JControl starts the JLaunch processes, which in turn start Java nodes such asdispatchers or servers.JControl creates a shared memory segment for the internal administrationdata of all JLaunch processes.JLaunchJLaunch receives commands from the JControl process (through namedpipes) to stop Java node elements such as dispatchers or servers.The JLaunch process ends itself if its parent process JControl is no longerrunning.JLaunch loads a JVM in a separate process. The parameterizing of the JVMis imported before the loading.


8/33

8

6/7/2012

Startup and Control Framework


9/33

9

6/7/2012

1

2

3

Agenda

4

5


File System Layout

Directory Structure




10/33

10

6/7/2012

Shutdown Procedure


11/33

11

6/7/2012

Stop Process

1. The Signal Handler of JControl receives a stop signal fromthe stopsap script (UNIX) or from the Windows Service.

2. JControl forwards the signal through named pipes to allrunning JLaunch processes (Java servers anddispatchers).

3. The JLaunch process of a Java cluster element shouldreact to this notification (soft shutdown) within a certainperiod of time. After this time has expired,the JLaunchprocess is terminated by JControl. When this is done, theJVM within the JLaunch process is ended, as is the JVM ofthe JLaunch process.


12/33

12

6/7/2012

JCMON

JCmonThe JCmon tool can be used to monitor the JControl process.

JCmon is part of the Startup and Control Framework, andis located in the JControl/JLaunch home directory, that is,in the executable directory

/usr/sap///j2ee/os_libs.JCmon can be started with the command JCmon pf=JCmon provides an administration interface for Java

instances that can be called from the operating system.


13/33

13

6/7/2012

JCMON


14/33

14

6/7/2012

1

2

3

Agenda

4

5


File System Layout

Directory Structure




15/33

15

6/7/2012

File System-Log Files


16/33

16

6/7/2012

Log Files

The trace and log files are stored in the work directory of an instance. This

directory is called /usr/sap///work (UNIX) andAnalogously in the Microsoft Windows environment.dev_jcontrolis the trace file for the JControl process. dev_jcontrol is the most importanttrace file for problem messages when starting the entire Java instance.Current messages are written at the end of the file.

dev_is the trace file for JLaunch processes. The trace file dev_ iswritten for each started JLaunch process, and therefore, for every dispatcherand server process.jvm_.outis the output file for the Java Virtual Machine (JVM). This JLaunch processrepresents a Java node such as a dispatcher or a server and therefore, a JVM.The output of a JVM is forwarded to the file jvm_.out in thework directory of a Java instance.


17/33

17

6/7/2012

Error Messages

Error Messages of the Startup and Control Framework:

. When starting a Java instance, JControl attempts to connect to the message server. Ifthis is not successful, error messages such as *** ERROR => Can.t attach to message server are written in the file dev_jcontrol. The message server is started with thecentral instance. The central instance must be started, and the message server mustbe running on the host and port assigned to it.

. The Virtual Machine (VM) attempts to find the JVM shared libraries. If the path is invalid,the following error message appears in the file dev_: *** ERROR => Can.t load VM shared library (JVM.DLL) (rc=-2) ... . To correct this error, you shouldcheck and, if

necessary, change the parameter javaVMLibPath in the VM property fileinstance.properties.vmprop in the cluster directory of the Java instance.

. Problems in the environment of the administration of shared memory canoccur, in particular under UNIX. Error messages of the type *** ERROR => Can.t attach to administration shared Memory appear in the filesdev_jcontrol and dev_. The cause of this is an existing sharedmemory segment with an incorrect size. To solve the problem, stop the Javainstance and change the os_libs directory of the Java instance. Clear theshared memory using the command jcontrol pf= -c .You can then restart the Java instanc


18/33

18

6/7/2012

Profiles


19/33

19

6/7/2012

File System

/admin/

go.batcluster/

dispatcher/go.bat

server/go.bat

log/managers/settings/*.properties

log/thread/*.log

services/admin/

admin.jarpropertiesruntime.xml

stateconfigtooldeploying

docs


20/33

20

6/7/2012

Config Tool

ConfigtoolSetup cluster nodesDisplay log infoDoes not require server/dispatcher running

To Start, Run the file go (go.bat in Windows) in thefolder://configtool


21/33

21

6/7/2012

Visual Administrator

Visual AdministratorDefault account: Administrator (casesensitive!), empty passwordTo start , Run the file go (go.bat in Windows)

in the folder://admin.


22/33

22

6/7/2012

Telnet Tool

Command Line Administration ShellCluster node consoles

Telnet Always connects to the dispatcherTo start, telnet:50008 from command line


23/33

23

6/7/2012

Usage Type Properties


24/33


25/33

25

6/7/2012

WEB AS JAVA Home Directory


26/33

26

6/7/2012

SDM Directory


27/33

27

6/7/2012

Visual Administrator Directory


28/33

28

6/7/2012

Content Directory


29/33

29

6/7/2012

Config Tool Directory


30/33

30

6/7/2012

Work Directory


31/33

31

6/7/2012

Kernel Directory


32/33

32

6/7/2012

DEMO

Demo

Portal File Locations andNavigation


33/33

33

6/7/2012

Thank you!

Questions?

Startup Process

Documents

Transcript of Startup Process