02 - Architecture & Tools J2EE Engine

7/27/2019 02 - Architecture & Tools J2EE Engine

1/74

SAP XI 3.0 System Administration

Acti ve Global Support , SAP AG

SAP J2EE Engine

Architecture &Tools


2/74

SAP AG 2007, Architecture&Tools J2EE 2

Vendors

J2EE Servers

Websphere (IBM)

Weblogic (BEA) Sun ONE Application Server (Sun, former iplanet server)

Enterprise Appl ication Server (Sybase)

JRun (Macromedia, former Allaire)

Oracle 9 iAS (Oracle)

JBoss (Open Source)

SAP J2EE Engine ( former InQMy Java Application Server)

JSP/Servlet Engine (Web Container) Tomcat (Apache Foundation, Open Source)


3/74

Admin Tools

Architecture

SAP J2EE Engine


4/74


Web Application Server - Installation Options

SAP Web Application Server - Java Stack

JAVA Scheme

HTTP

Server Server. . .

Java-Dispatcher

JAVA

SAP Web Application Server - ABAP and Java Stack

Server Server. . .

Java-Dispatcher

JAVAABAP

WP WP. . .

ABAP-Dispatc her

ICMMPIHTTP

JCo

JAVA Scheme

ABAP Scheme

MS

ICMMPI

ABAP

WP WP. . .

ABAP-Dispatc her

ABAP Scheme

MS

SAP Web Application Server - ABAP Stack

DIAG

DIAG


5/74


SAP Web Application Server 6.10

SAP

Basis

InternetCommunication

Manager (ICMan)

SAP J2EE Engine 6.10(InQMy 4.3.5 SP02)

ITSJSP/Servlet EJB BSPRFCJCoDIAG

RFC

Java VM (SUN, IBM, )

BAPI

HTTP HTTPHTTP

SAP Web Appl ication Server 6.10


6/74



SAP

Web

Appl icationServer

ITSBSPRFC

BAPI


DIAG

RFC

HTTP


Manager (ICMan)

SAP J2EE Engine

JSP/Servlet EJB JCo



7/74



SAP

Web

Appl icationServer

ITSBSPRFC

BAPI

SAP Web Appl ication Server 6.40

HTTP


Manager (ICMan)

SAP J2EE Engine

JSP/Servlet EJB JCo



8/74


SAP J2EE Engine Instance

A SAP J2EE Engine instance

consists of two types of

nodes:

A dispatcher node

receives the client

requests and dispatches

them to the server node

with the lowest load.

On a server node the

application logic is

executed.

Each node is running in

its own JVM (process).

A J2EE Engine cluster

may consist of several

instances running on the

same or different hosts.

Host n

Dispatcher

Server

Server

Server

Server

Java Scheme

Client


9/74


SAP WAS 6.40 Architecture for SAP J2EE

Minimum Cluster

Archi tecture: one

J2EE Instance and

one Central Services

Instance.

Server installed in this

way only processes

J2EE queries.

One Central Service

Instance is required

within the Cluster.

Use of a central database

as configuration and

application store.

SDM

Cl

ientApplication

HTTP/JCO


10/74


SAP System Architecture: Central Java Instance


11/74


SAP System Architecture: ABAP Instance


12/74


SAP System Architecture: ABAP Instance


13/74


SAP WebAS Java System 6.40 SAP J2EE Details

JControl Reads J2EE instance description from profile and instance.properties

Create SHM segment holding administrative instance data

Starts/Stops JVM hosting processes (JLaunch)

JLaunch (J2EE Dispatcher, J2EE Server, SDM) Reads process specific properties

Attach to SHM segment created by JControl

Parametrizes, loads and hosts JVM

startsap (UNIX) / SAP Service (Windows) starts 1 instance of

Database Instance (if local)

J2EE Message Server

J2EE Enqueue Server

starts n instances of

SAPOsCol

SAP J2EE

Startup

Framework


14/74


Jcontrol Java Instance Controller I

JControl controls J2EE processes,

is the master process of all J2EE worker processes

controls the lifecycle of the J2EE instance

Restart of crashed processed

Termination of hanging processes

Sends shutdown s ignal to instance processes

responsible for starting the processes in the right order(bootstrapping..)

integration o f dif ferent processes into one J2EE instance (SDM,

ICM, ...)

provides the monitoring information in a shared memory

segment

supports SAP profiles to share configurations with the ABAP

Stack


15/74


JControl Java Instance Controller II


16/74


JLaunch Java Program Launcher

JLaunch has following tasks:

to read the program properties

to read the VM properties from the database during startup

process

to attach to the administration shared memory segment

to load the shared lib rary of the Java VM


17/74


Starting and Stopping a Java Instance


18/74


Bootstrap files


19/74


J2EE Startup Framework Developer Trace Files

dev_jcontrol Trace f ile of JControl

Detailed property description

Descr iption of the processes started by JControl

dev_bootstrap Trace file of the init ial bootstrap process

dev_bootstrap_ID.... Trace file of the node bootstrap

process

dev_dispatcher Trace file of the J2EE dispatcher node

dev_server Trace files of the J2EE server nodes

dev_sdm Trace f ile of the SDM process


20/74


Most relevant information about s tartup of the different Java

processes can e found in the JLaunch traces:

dev_server - Trace-file of the jlaunch process

std_server.out - output of J2EE engine (like error.log and

output.log in SAPJ2EE 6.20)

jvm_server.out - output of the JVM

Low level process trace in the SAP developer trace files

dev_*

Trace files and JVM output files are in the work d irectory of the

instance

e.g. /usr/sap//>instance>/work

Al l processes are star ted with the SAP instance prof ile

Single point of management

Profile parameters for the startup framework

Profile directory /usr/sap//SYS/profile

J2EE Startup Framework Troubleshooting and Support


21/74


Directory Structure of WEB AS 6.40

j2ee sdm

SCS


22/74


Directory Structure of J2EE Instance


23/74


J2EE Instance on File System

Different types of Instances

JC

J2EE Engine Instance

SCS

Central Services Instance

DVEBMGS

ABAP Instance


24/74


Folder Sructure

System IDInstance number 0

Instance number 1 = central services

Visual Administrator

Configtool

start & instance profiles

Logfiles


25/74


System Profiles


26/74


Parameter jstartup/keep_old_logfiles - Motivation

Motivation

During startup/restart of the J2EE-Engine, the logfiles of the Startupand Control Framework are overwritten. Errors causing a restart are

difficult to analyse.

Definition

Name: jstartup/keep_old_logfiles

Values: [1..99]

Where to set: ABAP Instance-profile

Effect: Keeps n generations of the logfiles of the Startup Framework

Implementation

Profile-Parameter set at instance-level

Already set with defaul t-value of 2 in NW04s (PI 7.0)


27/74


Parameter jstartup/keep_old_logfiles

The parameter has effect on the following files:

In general: log- and tracefiles of the J2EE Startup Framework,i.e.:

Dev_jcontrol

Dev_bootstrap

Dev_bootstrap

Dev_dispatcher

Dev_serverN

Dev_sdm

Dev_jcmon

Also these f iles start ing wi th jvm_* and std_*


28/74


Parameter jstartup/keep_old_logfiles

Naming Convention:

The last 2 characters of the 3-character Extension are used for

numbering

If there is no extension, the extension bnn will be used with nn as a

number start ing with 00, 01,

Example:

Std_server1.out, std_server1.o00, std_server1.o01,

Dev_bootst rap, dev_bootstrap.b00, dev_boots trap.b01,


29/74

Admin Tools

Architecture

SAP J2EE Engine


30/74


SAP Web AS Java 6.40 Standard Ports

SAP Web AS Java port calculation:

50000+100*snr+port_index

snr= instance number

Port_index= left table column

Examples:

AdminTool: por t 50004

Telnet: port 50008

This way port conflic ts should be

avoided.You can individually conf igure every

port the J2EE Engine uses

Port numbers are configured in


Remember that all requests go

through dispatcher!

0 HTTP port

1 HTTP SSL port

2 IIOP Initial Context port

3 IIOP SSL port

4 P4 port

5 P4 HTTP Tunneling port

6 P4 SSL port

7 IIOP port

8 Telnet port

9 Monitor port

10 JMS port

Message Serverport: 3600+instance number of the central services instance


31/74


Administration and Configuration Options

Administ ration and Configurat ion Needs

Add, delete, configure addit ional server processes

Configure pool sizes, thresholds, etc.

User Management

...

Tools:

Online


Telnet

Offline

Config Tool


32/74

Config ToolVisual Admin

Telnet

JCmon

NWA

System Information PageSoftware Deployment Manager

Admin Tools


33/74


Preconditions

DB has to run SAP Web AS Java has to run

Usage

VM Settings configuration

Configuration of Servicesand Managers

Remote Configuration

Starting and stopping of Services

Stopping a SAP Web AS JavaInstance ABAP

Java

Config Tool


34/74


Offline Administration: Config Tool

Configure global, instance based,

and local properties:

Create/Delete

server processes

Set Java parameters

Change Manager and

Service settings

Act ivate/DeactivateServices

Change Log

configuration


35/74


Telnet

JCmon

NWA


Admin Tools


36/74


Preconditions


Usage






Java



37/74


Path to go.bat to start


Use the administration

tool to administer and

configure a running

cluster or server.You can administer

local and remote

servers.

Online Administration: Visual Administrator


38/74


Visual Administrator - Login

Log in using a user name

with administratorpermissions

Standard Login:

User:Administ rator

Password:

Host: or other

P4 Port: defaul t 50004

Choose transport protocol

No layer: use Java RMI / P4 (P4 is a internal proprietary protocol)

HTTP Tunneling: Allows communication through proxies and fi rewalls

SSL: Provides privacy over the Internet using cryptographic security

HTTPS: Using SSL with HTTP Tunneling


39/74


Online System Configuration


Change:

Ports

Log and Trace Configuration

Thread counts, queue sizes

...

Manage:

HTTP Aliases

JDBC Drivers/Data Sources

JCO RFC Destinations

JMS Topics, Queues,Connection Factories

User and User Groups

Online System Configuration: Visual Administrator


40/74


Administration of Applications

Appl ication start, stop, configure, moni tor


Telnet

Open command prompt

Enter: telnet

Log in with Administrator

and Password SAP


41/74


Telnet

JCmon

NWA


Admin Tools


42/74


Preconditions


Usage






Java

Telnet


43/74


J2EE Engine Telnet Console

The J2EE Engine has an own Telnet port which can be useful to

collect information.

telnet://localhost:50008


44/74



As soon as the Dispatcher is started can you establish the telnet

connection and execute commands like lsc :

Helpful commands:

jump changes the act ive node

lsc shows the active nodes in the cluster

lss shows started services

lsp shows all used ports

msc shows memory usage

man shows a list of avail. commands

shutdown shuts the active node down


45/74




46/74


Telnet

JCmon

NWA


Admin Tools


47/74


JCmon

Started from os_libs directory:

/usr/sap//j2ee/os_libs/jcmon pf=/

Pick 20 from menu to select Local Administration.


48/74


JCmon Menu Local Administration


49/74

Config Tool

Visual Admin

Telnet

JCmon

NWA


Admin Tools


50/74


NWA: Monitoring and Management Big Picture


51/74


Setting Up NWA Big Picture


52/74


NWA: The Entry Page

The NWA can be used as an administration tool for the whole SAP NetWeaver system

landscape, as well as for local system administration

For the central use, a setup has to be performed, including configurationSystemLandscape Directory, central monitoring, and connection remote systems to the

central monitoring system and NWA


53/74


NWA What IsInside Administration?

Administration

Monitoring


54/74


Administration: Manage the Selected Systems

Choose System ManagementAdministration .

From the detailed navigation on

the left, select Systems. A l ist of

the instances you selected when

defining your system selection will

appear in a tree view.

Start stop J2EE instances

separate J2EE processes and

services.


55/74


Administration: Manage Applications

With the NWA you can start and stop applications of the

selected Java systems as well as display their status, their

modules, resources, and references

An advanced search option is also available, which helps you

to apply more sophisticated filtering criteria when searching for

deployed applications


56/74


NWA What IsInside Administration?

Administration

Monitoring


57/74


Monitoring: Availability Check

All systems that aremonitored in theCentral Monitor ingSystem can beobserved by anavailability check.

This check is realizedby the agentCCMSPING, whichcalls the messageservers of themonitored systemsand sends availabilitydata every minute.


58/74


Monitoring: Availability Details


59/74


Monitoring: Central Reports (RZ20 Web View)

M it i C t l R t D t il


60/74


Monitoring: Central Reports Details

M it i C t l R t A l O ti


61/74


Monitoring: Central Reports Analyze Option

M it i J P f R t


62/74


Monitoring: Java Performance Reports

M it i C t N J S t R t


63/74


Monitoring: Create New Java System Reports

You can define Java System Reports and charts out of all available

counters, such as performance counters from the monitoring tree, JARM

requests, and application components


64/74

Config Tool

Visual Admin

Telnet

JCmon

NWA


Admin Tools

S stem Information Page 1


65/74


System Information Page - 1

http://server:j2ee_http_port/

System Information Page 2


66/74



A

1 2

3 4 5

B



67/74



3

XI components version(1),

support package (2) and

patch level (3) details

SAP-XIAFC

1000.3.0.15.1.20051219120424

1 2 3



68/74



1

2

3

4

B



69/74



JVM Settings

2


70/74

Config Tool

Visual Admin

Telnet

JCmon

NWA


Admin Tools

Deployment of the libraries with SDM


71/74


Deployment of the libraries with SDM

Vendor Specific Driver (JMS JDBC): Check Deployment


72/74


Vendor Specific Driver (JMS, JDBC): Check Deployment

Check Deployment Class Load Viewer


74/74

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Formauch immer, ohne die ausdrckliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikationenthaltene Informationen knnen ohne vorherige Ankndigung gendert werden.

Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte knnen Softwarekomponenten auchanderer Softwarehersteller enthalten.

Microsoft, Windows, Outlook, und PowerPoint sind eingetragene Marken der Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, und Informix sind Marken odereingetragene Marken der IBM Corporation in den USA und/oder anderen Lndern.

Oracle ist eine eingetragene Marke der Oracle Corporation.

UNIX, X/Open, OSF/1, und Motif sind eingetragene Marken der Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, und MultiWin sind Marken oder eingetrageneMarken von Citrix Systems, Inc.

HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des W3C, World Wide Web Consortium,Massachusetts Institute of Technology.

Java ist eine eingetragene Marke von Sun Microsystems, Inc.

JavaScript ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscapeentwickelten und implementierten Technologie.

MaxDB ist eine Marke von MySQL AB, Schweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver und weitere im Text erwhnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschlandund anderen Lndern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligenFirmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte knnenlnderspezifische Unterschiede aufweisen.

In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden. Die vorliegendenAngaben werden von SAP AG und ihren Konzernunternehmen (SAP-Konzern) bereitgestellt und dienen ausschlielichInformationszwecken. Der SAP-Konzern bernimmt keinerlei Haftung oder Garantie fr Fehler oder Unvollstndigkeitenin dieser Publikation. Der SAP-Konzern steht lediglich fr Produkte und Dienstleistungen nach der Magabe ein, die inder Vereinbarung ber die jeweiligen Produkte und Dienstleistungen ausdrcklich geregelt ist. Aus den in dieserPublikation enthaltenen Informationen ergibt sich keine weiterfhrende Haftung.

Copyright 2007 SAP AG. Alle Rechte vorbehalten

02 - Architecture & Tools J2EE Engine

Documents

Transcript of 02 - Architecture & Tools J2EE Engine