Agenda

1 2 Start up Procedure of EP Startup control Frame Work

3
4 5

Shutdown Procedure of EP File System Layout

Directory Structure
1

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 portals after a system reboot. It also enables scripting the startup/shutdown sequence. The following sequence is to be maintained for starting and shutting down the portal. Startup or shutdown of Web Server is not required as SAPJ2EE Engine servers as the Web Server. Startup Oracle Database SAPJ2EE Engine Dispatcher (also starts the Server and State Controller) Shutdown SAPJ2EE Engine Dispatcher (also starts the Server and State Controller) Oracle Database Some scripts have been developed to automate the starting and shutdown of the portal by the operational personnel, like backup operators, etc. Note: There is no separate startup and shutdown for Enterprise Portal. EP Content can be accessed after Starting WEBAS JAVA
2

6/7/2012

Startup Sequence

6/7/2012

Startup Process
The starting of the system is performed in multiple steps, and is the task of the operating system user <sid>adm: 1. Starting the database The database is the fundamental element of the entire SAP system. This must be in an operational state before SAP instances are started. 2. Starting the Central Services and then starting the central instance The Central Services consist of the Java message server and the Java enqueue server. The dispatcher and server Java cluster elements connect to the Java message server during their own start process. After the Central Services have been started, the central Java instance is started with its dispatcher and servers. A Java instance is started and stopped by the Java Startup and Control Framework. The Software Deployment Manager (SDM) is also started with the central Java instance. 3. Other Java dialog instances are started. When an instance is started, its dispatcher and servers are started.

6/7/2012

Starting a Standalone Java System

6/7/2012

Agenda
1 2 Start up Procedure of EP Startup control Frame Work

3
4 5

Shutdown Procedure of EP File System Layout

Directory Structure
6

6/7/2012

Startup and Control Framework

JControl JControl starts, stops, and monitors the processes of a Java instance . primarily the server and dispatcher processes. SAP Signal Handling is implemented with JControl to forward the start and stop commands to a Java instance. JControl restarts terminated processes, ends hanging processes, and sends a shutdown 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 as dispatchers or servers. JControl creates a shared memory segment for the internal administration data of all JLaunch processes. JLaunch JLaunch receives commands from the JControl process (through named pipes) to stop Java node elements such as dispatchers or servers. The JLaunch process ends itself if its parent process JControl is no longer running. JLaunch loads a JVM in a separate process. The parameterizing of the JVM is imported before the loading.

6/7/2012

Startup and Control Framework

6/7/2012

Agenda
1 2 Start up Procedure of EP Startup control Frame Work

3
4 5

Shutdown Procedure of EP File System Layout

Directory Structure
9

6/7/2012

Shutdown Procedure

10

6/7/2012

Stop Process
1. The Signal Handler of JControl receives a stop signal from the stopsap script (UNIX) or from the Windows Service. 2. JControl forwards the signal through named pipes to all running JLaunch processes (Java servers and dispatchers). 3. The JLaunch process of a Java cluster element should react to this notification (soft shutdown) within a certain period of time. After this time has expired,the JLaunch process is terminated by JControl. When this is done, the JVM within the JLaunch process is ended, as is the JVM of the JLaunch process.

11

6/7/2012

JCMON
JCmon The JCmon tool can be used to monitor the JControl process. JCmon is part of the Startup and Control Framework, and is located in the JControl/JLaunch home directory, that is, in the executable directory /usr/sap/<SID>/<instance>/j2ee/os_libs. JCmon can be started with the command JCmon pf=<SAP instance profile> JCmon provides an administration interface for Java instances that can be called from the operating system.

12

6/7/2012

JCMON

13

6/7/2012

Agenda
1 2 Start up Procedure of EP Startup control Frame Work

3
4 5

Shutdown Procedure of EP File System Layout

Directory Structure
14

6/7/2012

File System-Log Files

15

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/<SID>/<instance name>/work (UNIX) and Analogously in the Microsoft Windows environment. dev_jcontrol is the trace file for the JControl process. dev_jcontrol is the most important trace file for problem messages when starting the entire Java instance. Current messages are written at the end of the file. dev_<node name> is the trace file for JLaunch processes. The trace file dev_<node name> is written for each started JLaunch process, and therefore, for every dispatcher and server process. jvm_<node name>.out is the output file for the Java Virtual Machine (JVM). This JLaunch process represents 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_<node name>.out in the work directory of a Java instance.

16

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. If this 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 the central instance. The central instance must be started, and the message server must be 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_<node name>: *** ERROR => Can.t load VM shared library (JVM.DLL) (rc=-2) .... To correct this error, you should check and, if necessary, change the parameter javaVMLibPath in the VM property file instance.properties.vmprop in the cluster directory of the Java instance. . Problems in the environment of the administration of shared memory can occur, in particular under UNIX. Error messages of the type *** ERROR => Can.t attach to administration shared Memory appear in the files dev_jcontrol and dev_<node name>. The cause of this is an existing shared memory segment with an incorrect size. To solve the problem, stop the Java instance and change the os_libs directory of the Java instance. Clear the shared memory using the command jcontrol pf=<SAP instance profile> -c. You can then restart the Java instanc

17

6/7/2012

Profiles

18

6/7/2012

File System
<J2EE_Dir>/ admin/ go.bat cluster/ dispatcher/ go.bat server/ go.bat log/ managers/ settings/*.properties log/ thread/*.log services/ admin/ admin.jarproperties runtime.xml state configtool deploying docs

19

6/7/2012

Config Tool

Configtool Setup cluster nodes Display log info Does not require server/dispatcher running To Start, Run the file go (go.bat in Windows) in the folder: /<J2EE_directory >/configtool

20

6/7/2012

Visual Administrator
Visual Administrator Default account: Administrator (case sensitive!), empty password To start , Run the file go (go.bat in Windows) in the folder: /<J2EE_directory>/admin.

21

6/7/2012

Telnet Tool

Command Line Administration Shell Cluster node consoles Telnet Always connects to the dispatcher To start, telnet:50008 from command line

22

6/7/2012

Usage Type Properties

23

6/7/2012

Agenda
1 2 Start up Procedure of EP Startup control Frame Work

3
4 5

Shutdown Procedure of EP File System Layout

Directory Structure
24

6/7/2012

WEB AS JAVA Home Directory

25

6/7/2012

SDM Directory

26

6/7/2012

Visual Administrator Directory

27

6/7/2012

Content Directory

28

6/7/2012

Config Tool Directory

29

6/7/2012

Work Directory

30

6/7/2012

Kernel Directory

31

6/7/2012

DEMO

Demo Portal File Locations and Navigation

32

6/7/2012

Questions?

Thank you!
33

6/7/2012