TADMJ1+ +SAP+Java+Engine+Administration

(1)

TADMBO Implementation&Operation II

THE BEST-RUN BUSINESSES RUN SAP © SAP AG 2004

TADMJ1

SAP Java Engine Administration

2005/Q1

(2)

1

©SAP AG 2004, Web AS Java Installation and Upgrade

Course: SAP Java Engine Administration

1. Web AS Standalone Java Installation

2. Java Startup & Control Framework

3. Web AS Java Administration Tools Overview

4. SAP Java Administration

5. SAP Web Infrastructure

(3)

Unit: Web AS Standalone Java Installation

Installation of the SAP J2EE Engine

Lesson:

(4)

3

Installation of the

SAP J2EE Engine

(5)

Installation of SAP Web AS Java: Lesson Objectives

After completing this lesson, you will be able to: Plan your Web AS Java Installation.

Understand the document changes

Understand the changes in the SAPInst process

Migrate/upgrade your previous Web AS Java Installation. Understand the J2EE Engine installation steps

(6)

5

SAPInst Changes

Document Changes

J2EE Engine Migration and Upgrade

Introduction

(7)

The Web App Server provides a common foundation for NetWeaver

The Web Application Server is the complete infrastructure to develop, deploy and run:

All SAP NetWeaver components

mySAP Business Suite Customer-developed applications

3rd_{-party Java 2—Enterprise}

Edition-compliant applications

Integrates the proven ABAP and the innovative internet-driven Javatechnology in one application server

SAP NetWeaver™ CRM

mySAP Business Suite

BW EP XI MI MDM

Web Application Server

ERP SRM

J2EE ABAP

The SAP Web Application Server is the technical platform for SAP NetWeaver, providing the complete infrastructure to develop, deploy and run all SAP NetWeaver components, the mySAP Business Suite, customer-developed applications and 3rd-party J2EE 1.3 compliant applications.

SAP Web AS fully supports both the proven ABAP technology and the open source internet-driven technologies—Java and Java 2 Enterprise Edition, also called J2EE.

(8)

7

Basic System Variants of SAP Web AS

SAP Web Application Server

Database Instance

SAP Web AS ABAP

ABAP Schema

For SAP Web AS 6.40, the following basic system variants exist:

SAP Web AS Java

Java Schema

• SAP Web AS Java (J2EE Engine, but no ABAP Engine)

• SAP Web AS

ABAP+Java(ABAP Engine and J2EE Engine)

Detailed view: central instance consists of both ABAP and Java parts, SCS instance only required for Java

Central Instance ABAP Engine J2EE Engine Central Services Instance (SCS)

• SAP Web AS ABAP (ABAP Engine, but no J2EE Engine)

The SCS (Central Service Instance) is required only for Web AS Java.

The SCS consists of several Central Services which run on one physical server. The Central Services comprise the message service and the enqueue service.

The SCS forms the basis of communication and synchronization for the Java cluster. Central Services are always required when a Java cluster is installed. They are started on a server with their own system number and the system ID (SID) of the whole system.

(9)

SAPInst Changes

Document Changes

Introduction

(10)

9

Main SAP documentation types

Documentation types in the software life cycle

An overview of the most important documentation types that are needed in the various phases in the life cycle of SAP NetWeaver..

The changes to these guides are released as OSS notes, before going to the documents, you should look for released notes.

(11)

Documentation Roadmap

1. Master Guide – SAP NetWeaver

Which technical scenario do you want to install? Technical system landscape

Required components Installation sequence

2. Installation Guide – SAP Web AS ABAPand/or Installation Guide – SAP Web AS Java

3. If relevant: Planning Guide – SAP Web AS on UNIX: Oracle

Information about basic system variants, instances, distribution,

installation options (MCOD, LDAP, …), and detailed parameter tables for your installation service

4. UNIX only: SAP Software on UNIX: OS Dependencies 5. New Troubleshooting Guide for the Java installation

Master Guide

The Master Guide is the starting point for implementing SAP NetWeaver.. It lists the required SAP components and third party applications that are required for each scenario. It provides scenario-specific descriptions of preparation, execution, and follow-up of an implementation. It also offers references to other documents, such as Component Installation Guides and SAP Notes.

Target group:

Technology consultants System administrators

Project teams for implementations

The Master Guide is regularly updated on SAP Service Marketplace at service.sap.com/instguidesNW04. Make sure you have the latest version of the Master Guide by checking Service Marketplace immediately

before starting the installation.

Now there is only one NW - Master Guide, no longer separate master guides for the different components.

Component Installation Guide

The Component Installation Guide describes the technical implementation of an SAP component, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration.

Target group:

Technology consultants

Project teams for implementations

Current version is located on SAP Service Marketplace at service.sap.com/instguidesNW04

Application server installation guides are separated by ABAP and Java part. When doing Add-in installation both of them must be considered.

(12)

11

Installation Guide

Concept of Installation Checklists in Installation Guides List chronologically the actions that you must perform:

You choose and print outthe relevant installation checklist(s) for your installation (there is one checklist for each installation service).

If a step is required for your installation, you follow the linkfor that step to the corresponding section.

You performthe procedure described there.

After successfully completing the installation step, you markthe corresponding entry in the printed table with ! to log the progress of your installation.

You proceedwith the next step in the checklist

General Information Installation Checklists Step 1 Step 2 … Step n Preparation Installation Post-Installation Additional Information Planning

Concept not new, but essential for navigation in installation guides

Installation Checklists

References

Print

(13)

Evaluation of Planning Guide for UNIX/Oracle

All planning steps shifted to new guide

You choose a basic system variantof SAP Web AS. You choose the SAP instancesyou want to install.

You choose how you want to distributethe SAP instances to installation hosts.

You decide if you want to perform a MCODinstallation.

You decide if you want to use the LDAPfor SAP Logon or the Microsoft Management Console (MMC).

For every SAP instance, you collect the values of the installation parameterslisted in the corresponding parameter tables.

In the present installation guides, only tasks will remain that have to be performed ‘on the system‘

There is one parameter tablefor every installation service of SAPinst, contains description of the SAPinst dialogs for your installation

Usage of this documentation is mandatory for installations on UNIX/Oracle

This Planning Guide is new, and evaluated only for Unix/Oracle, evaluations for other platforms will come with the next releases.

The Planning Guide is mandatory for Unix/Oracle, because the planning information is removed from the normal installation guide..

(14)

13

Where are all the documents stored?

http://service.sap.com/instguides

-> SAP NetWeaver -> Release 04

NetWevaer 04 - Planning / Installation / Upgrade / Operation

-> SAP Components -> SAP Web Application Server Releases - 6.10 / 6.20 / 6.30

(15)

SAPInst Changes

Document Changes

Introduction

(16)

15

Shipment-Specific SAPinst Changes

SAP NetWeaver gets delivered exclusively on DVD

DVDs are only used as data carriers

If SAPinst prompts for a CD, it will be possible to select the corresponding sub-directory (browse the DVD)

New supported OS and Database versions:

Linux and Windows IA64 MySQL MaxDB 7.5

IBM DB2 Universal Database for UNIX and Windows IBM Informix (ABAP schema only)

See SAP Service Marketplace at http://service.sap.com/platforms for the latest information.

Check the installation guide before performing an installation for changes. For

example immediately after the installation you may need to apply a support package. The installation now is shipped on DVD, however the installation is still pointing to different CDs, you’ll find them all stored on this data carrier.

MySQL MaxDB is the former SAP DB Oracle 10g will be released at the Q1/2005

J2EE Engine is using Unicode enabled databases. Informix doesn’t support Unicode and is not possible to be used as J2EE Engine Database. For Add-in installation where the ABAP stack is using Informix, other (Unicode supporting) database must be used for the installation of the J2EE Engine.

(17)

Tool-Specific SAPinst Changes

You start SAPinst directly fromthe Master CD/DVD, manual creation of an installation directory is no longer required (but still possible) SAPinst normally creates

sapinst_instdir/<installation_service>automatically under:

UNIX: the temporary directory ($TEMP or $TMP or /tmp) Windows: %ProgramFiles%

JREis still required for the SAPinst GUI. Nevertheless, JRE is part of the SAPinst executable for Windows IA64, HP-UX, and Sun Solaris. For all other operating systems, you must still install JRE (or JDK, see below) as prerequisite.

(18)

17

Product-Specific SAPinst Changes

SAP System Landscape Directory (SLD) is part of SAP Web AS Java 6.40 installation

Possibility to configure User Management Engine (UME) of an SAP Web AS Java system against the user management of a separate SAP Web AS ABAP system

JDK 1.4is required for SAP Web AS Java 6.40. For exact version, see SAP Service Marketplace at

http://service.sap.com/platforms

On Windows, setting of JAVA_HOMEis no longer a prerequisite as SAPinst checks the registry for installed JVMs. If the environment variable JAVA_HOME points to a JVM with a valid version, it is used by default. If not, the JVM with the highest version in the required version range is used.

When only one central User Management is going to be used, the connection can be configured during the installation.

However this connection can be established later as well.

This feature is suitable for large cluster installations where every server is installed on different box.

(19)

Corresponding Installation Services

SAP Web AS ABAP+Java System

SAP Web AS Java System

When installing the Add-In installation, the ABAP installation is first, after comes the Java stack.

Different installation options are possible.

Central Instance on one box, Dialog instances on another.

(20)

19

Installation Options

Add Support Package Default Installation Add additional server instance

Installation options for different databases

The installation provides possibility to install Web AS Java + Java Developer

Workspace at once. This is fast and very convenient way for developer, where they have testing server and the developer IDE on one box. All configurations are

predefined.

The Java only installation is distributed by the different databases. The customer installation package contains one DB installation option only.

J2EE Engine is using Unicode enabled databases. Informix doesn’t support Unicode and is not possible to be used as J2EE Engine Database. For Add-in installation where the ABAP stack is using Informix, other (Unicode supporting) database must be used for the installation of the J2EE Engine.

(21)

Installation Options Specific SAPinst Changes

Simplified installation in default mode: Default values are used for most of the installation parameters:

Enables you to set up an SAP Web AS Java system in a more quick and easy way, if the default values are sufficient for your purposes.

Default Installation, doesn’t support all Data Bases yet only Oracle and MaxDB. The non supported will come in the next releases.

(22)

21

Post Installation: Apply NetWeaver ´04 SP Stack

NW Dev. Studio and JDI WebAS JAVA NW ABAP stack Released

SAP

NW `04 SP

Stack

NWDS 2.0 SP9 JDI 6.40 SP9 J2EE 6.40 SP9 SP9 + new Kernel patch Oct. 2004

Stack 09

Renumbering of all SAP NetWeaver `04 Support Package Stacks NWDS 2.0 SP8 JDI 6.40SP8 J2EE 6.40 SP8 SP5 + new Kernel patch Sept. 2004

Stack 05

NWDS 2.0 SP7 JDI 6.30 SP7 J2EE 6.30 SP7 SP4 + new Kernel patch Aug. 2004

Stack 04

NW Component – Overview

NetWeaver 04 ABAP stack

SAP_KERNEL 6.40 (incl. ITS) / SAP IGS 6.40 SAP_BASIS 6.40 (incl. XI 3.0 ABAP and KW 7.0) SAP_ABA 6.40 (incl. MI 2.5 ABAP)

PI BASIS 6.40 (PlugIn Basis)

SAP_BW 3.5 (incl. BI Content for BW installation option) NetWeaver 04 JAVA stack

WebAS 6.40 JAVA stack

SAP JAVA runtime 6.30 (J2EE, WebDynpro, UME, …incl. MI (Mobile Infrastructure) middleware) ADOBE (optional installation)

SAP DEV. INFRASTRUCTURE (JDI) (optional installation) NW JAVA Applications

XI Java 3.0 (divided into 4 sub-components + XI-Partner Connectivity Kit) BI 3.5 Java component (UDI / MMR for WebAS)

EP 6.0 (PP + KM) / incl. Unification as of FP (SP stack 04), BI Broadcasting contained in KM KW 7.0 Java components (PAW 7.0, SAP IKS 1.0)

NW Development Studio 2.0 (incl. Plug-Ins from all NW Java Applications) MI 2.5 client (NOT based on WebAS Java)

NetWeaver 04 other components

SAP GUI 6.20 available / 6.40 to be released as accessible WinGui mid 2004 SAP TREX 6.1 / SAP CS 6.30

PlugIns PI_BASIS (for BW) and WP_PI (for EP) available

(23)

Post Installation: Check Ports

SAP Web AS Java port calculation: 50000+100*snr+port_index

snr= instance number Port_index= left table column Examples:

AdminTool: port 50004 Telnet: port 50008

This way port conflicts should be avoided.

You can individually configure every port the J2EE Engine uses

Port numbers are configured in Visual Administrator

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

(24)

23

The Java Instances are using in general the same filesystem layout as it is known from the ABAP Instances.

The only different is the directory j2ee. In this directory most Java related files are stored (other directries are /usr/sap/<SID>/sys/profile

/usr/sap/<SID>/>InstnaceName>/work).

/usr/sap/CCMS is the monitoring file tructure not shown in the graphic (see TADMJ5 for details)

Directory Structure of WEB AS 6.40 ABAP+Java

(25)

/usr/sap/<SID>/<InstanceName>/ data Data directory e.g. Cachefiles

exe executables e.g. startsap, stopsap, saposcoll j2ee

log Log files

SDM Executables and Data of SDM / SDM Repository sec Security files

work Workdirectory

/usr/sap/<SID>/<CentralServicesInstanceName>/ data Data directory e.g. Cachefiles, Enqueue File exe executables e.g. startsap, stopsap, saposcoll log Logfiles e.g. Syslog

sec Security files work Workdirectory

Java Only Instance on File System

Different types of Instances JC<Instance number>

J2EE Engine Instance

SCS<Instance number>

Central Services Instance

DVEBMGS<XX>

(26)

25

/usr/sap/C11/JC00/j2ee

admin Executables Visual Administrator

cluster J2EE Cluster Executables and Configuration configtool Executables ConfigTool

deploying Directory of Deploytool

j2eeclient jar files for a P4 client

os_libs operating system dependend libraries and executables e.g. jcontrol, jlaunch …

/usr/sap/C11/<InstanceName>/j2ee/cluster

bootstrap JAR Files and properties for bootstrap

dispatcher JAR Files, logfiles and propertie files of the Dispatcher server<Number> JAR Files, logfiles and propertie files of the Dispatcher

/usr/sap/C11/JC00/<InstanceName>/cluster/dipatcher

bin JAR Files of Dispatcher

cfg propertie files for manager

dtd Data type definitions

log log Files of Services and Managers

temp temporary files

/usr/sap/C11/JC00/j2ee/cluster/server<number>

apps JAR Files of Applications

bin JAR Files of Server

cfg propertie files for manager

dtd Deployment Descriptoren

log log Files of Services and Managers META-INF

temp temporary files

(27)

DEFAULT.PFL Default profile of the Systeme START_JC00_P65028 Start profile of J2EE Instance with Instancenumber 00

START_SCS01_P65028 Start profile of Central Services Instance with Instancenumber 01

C11_JC00_P65028 Instance profile of J2EE Instance with Instancenumber 00

C11_SCS01_P65028 Instance profle of Central Services Instance with Instancenumber 01

(28)

27

You need a valid SAP license to log on to the SAP Web AS. When the SAP Web AS is installed, a temporary license is also installed, which you must replace with a permanent license.

Note that with a J2EE+ABAP installation (SAP Web Application Server with ABAP and J2EE), you have to import the ABAP license (see SAP License).

This section only describes the procedure for the J2EE only Installation.

In the Visual Administrator choose Server -> Services -> Licensing Adapter. The system data that you need to request the license from the SAP Service Marketplace appears.

Installation number (if it exists) System ID,

System number (if it exists) Hardware key

Current release

Under the Internet address service.sap.com/licensekey -> mysap Business Suite, you can get to the initial page of the license key requests in SAP Service Marketplace. Here you will find all the information you need to request license keys.

Enter your e-mail address in the request. The license key will be sent to you promptly by e-mail. Alternatively, you can also download the license key from the SAP Service Marketplace.

Do not make any changes to the license key. To import the license key, the file must not have been changed. In the Licensing Adapter in the Visual Administrator choose Install License from File.

Select the license file that you want from SAP.

You can view all the licenses installed in your SAP System, by choosing, in the Visual Administrator, Server -> Services -> Licensing Adapter, then tab Runtime -> Installed Licenses.

See SAP note 94998 for additional information about requesting license keys.

You could install multiple licenses, for example when running scenarios as EP and XI.

SAP License Key

You need a valid SAP licenseto log on to the SAP Web AS. When the SAP Web AS is installed, a temporary license (29 days) is also installed which you must replace with a permanent license.

With an ABAP + J2EE installation you need an ABAP license!

In the Visual Administrator choose Server 0 → Services → Licensing Adapter. The

system data appears that you need to request the license from the SAP Service Marketplace.

Installation number (if it exists) System ID

System number Hardware Key Current Release

service.sap.com → Software Distribution Center →

(29)

SAPInst Changes

Document Changes

Introduction

(30)

29

Status 6.20 / 6.30 / 6.40

Web A S 6. 40 W eb AS 6. 30 Web A S 6. 20

ABAP only ABAP + Java J2EE only

ABAP 6.20 J2EE 6.20 J2EE 6.20 ABAP 6.20 ABAP 6.20 ≥SP25 J2EE 6.30 ≥SP2 J2EE 6.30 ≥SP2 ABAP 6.40 Java Engine 6.30 ≥SP4 ABAP 6.40 Patch No Upgrade Upgrade No Upgrade Patch Patch Patch Up gra de + add J2E_E

Dependency APAB -> J2EE in WAS 6.40 optional A d d-In Java Engine 6.30 ≥SP4 ABAP 6.20 ≥SP25

ABAP and Java Engine version release of the Web AS 6.20 to 6.40 installations, and possible upgrades. The Web AS 6.20 and 6.30 support 3 installation options: ABAP only; ABAP + Java; Java only

The Web AS 6.40 – supports only 2 installation options: Add-In (ABAP + Java) and Java only. The ABAP only installation in not possible any longer, because of dependency of the applications on the Java Engine. Upgrades of the Web AS (ABAP only) installations:

Web AS 6.20 (ABAP 6.20) can be upgraded to Web AS 6.30 (upgraded ABAP 6.20)

Web AS 6.30 (ABAP 6.20) -> the last Web AS (ABAP only) installation option. Upgrade to Web AS 6.40 should be carried by upgrading the ABAP 6.20 to 6.40 and installing Java Engine. (The Web AS 6.40 Add-In installation consists of ABAP 6.40 + Java Engine 6.30 ≥ SP3)

Upgrades of the Web AS (Add-In) installations:

• Web AS 6.20 (ABAP 6.20 and optional J2EE Engine 6.20) – patch of the ABAP kernel to ABAP 6.20 SP 25 or newer, and full migration of the J2EE Engine 6.20 to 6.30 (upgrade of the J2EE Engine not possible!) • Upgrade of Web AS 6.30 to 6.40 – ABAP kernel upgrade from 6.20 to 6.40; J2EE 6.30 to 6.30 ≥ SP4 patch

with workarounds (see support package guide SP2 - SP4)! Upgrades of the Web AS (Java only) installations:

• Web AS 6.20 (J2EE 6.20) can only be migrated to Web AS 6.30 (J2EE 6.30)!

• Web AS 6.30 (J2EE 6.30) can be patched with workarounds to Web AS 6.40 (J2EE 6.30 ≥ SP4) J2EE Engine 6.20 -> 6.30 is a migration not an upgrade (Add-In and Java only installations)

(31)

Migration Scenarios – Next Releases

A direct migration of 6.20 to > 6.40 release is not

planed!

The required steps are:

Migration of the engine + applications 6.20 – 6.40

The applications on 6.40 need to comply with several rules to enable future upgrade.

An upgrade 6.40 – NextRelease will be provided.

Direct migration from 6.20 to newer but 6.40 release is not planed.

The required steps are: 6.20 – 6.30/6.40 migration and afterwards a

6.30/6.40 – NextRelease upgrade.

Upgrade of Web AS Java 6.30 to 6.40 should be carried by these steps.

Installation of Web AS Java 6.30 SP 0/1 Upgrade to SP2

Upgrade to SP4 (Web AS 6.40) Upgrade to latest SP release.

Upgrade of Web AS 6.30 SP 0/1 to latest Web AS 6.40 SP is not planned. Always going to 6.30 SP2 and SP4 first!

SP3 is the first Web AS 6.40 release – available as installation option.SP3 is not released for productive usage, always upgrade to the latest SP release.

(32)

31

J2EE Migration 620 – 630/640

6.20 – 6.30/6.40 is a migration and not an upgrade:

Application data has to move to the standard SAP schema Application tables need to fulfill the conditions of SAP JDDI

Namespace rules

Table and field name conventions Type restrictions due to portability

Major technological changes in the J2EE engine architecture

620 has file system persistency 630 has the engine data in DB tables

All application data has to be copied!

All engine configurations and data has to be copied / replaced!

Web AS Java 6.20 – 6.40 migration guide, and documents can be found in the documentation path:

SAP Library -> SAP NetWeaver -> Application Platform -> Java Technology in SAP Web Application Server -> Migration Manual

(33)

Migration 6.20 – 6.30/6.40 Scenarios

Stand alone J2EE engine:

Migration procedure available and tested Converter Tool

J2EE add-in installation in ABAP DB: Additional steps in the migration needed XI migration scenario is in development J2EE + ABAP with two databases:

Migrate the J2EE DB into the ABAP DB Migrate to another DB vendor:

Not all migration scenarios are supported yet.

The Converter Tool is used for converting J2EE applications developed to be deployed and run on the J2EE Engine 6.20 into applications that can be deployed and run on the J2EE Engine 6.40. The tool updates the standard deployment

descriptors and creates the necessary J2EE Engine-specific deployment descriptors. The Converter Tool can be started with the convertor script file from the <J2EE

Engine installation directory>/deployingdirectory.

The XI migration scenario will be available for the Mass Shipment (General Availability) of NetWeaver ‘04

(34)

33

Overview: Java component & technology upgrade

2. Application data (FS, DB) 1. Customer-modification & extension SAP J2EE 6.20 4. Security / User man. 3. Application config (FS, R/3) SAPInst 2. Application data (DB) 1. Customer-modification & extension SAP J2EE 6.30/6.40 4. UME 4.0 or ABAP backend 3. Application config (FS, R/3,DB) 2. Application data (DB) 1. Modification & extension framework SAP J2EE 7.0 4. UME or ABAP backend 3. C2-Server diff & merge diff & merge

migrate (if nec.)

merge & migrate merge & migrate

migrate (if nec.)

Engine config Engine config Engine config

Legend: Application specific Tools Standard / Generic Tools

a

:

standard Conflict vs reality manual ?

a

Standard ? Framework ? Standard ? Framework ? Modif adjust tool ? Modif adjust tool ? Standard ? Repository ? Standard ? Repository ? import tool ? import tool ? import tool ! import tool ! import tool ? import tool ?

This slide shows the efforts made to consolidate the different areas of the SAP J2EE Engine into a common infrastructure, so that the Java upgrade tools can work in a similar way to the Abap upgrade tools.

In SAP J2EE 6.20 to 6.30/6.40 migration mostly all areas are should be handle by application specific procedure.

In SAP J2EE 7.0 onwards the Java upgrade tools would be able to upgrade the most of the engine and applications with minimal manual interaction.

(35)

Applications running on J2EE Engine 6.20

Most customers …

only use one or two SAP Java apps productively have modified .jsp, .css files (not .java)

have used app specific enhancement framework(s)

have developed their own J2EE apps using SAP J2EE 6.20 run Java apps on separate WebAS (with Java stack only) Hard to tell exactly which source versions customers have

delivery hard to reconstruct without DTR Only few applications have >100 customers

EP5/6 CRM

SRM (mostly use of UME)

This is the typical use of SAP in our customers J2EE Engine, and thus has been taken into account to the current development of J2EE upgrade technology.

(36)

35

Appendix – J2EE Engine Installation

S

teps

(37)

J2EE Engine Installation Steps 0

Steps of Engine Installation

Engine CI

(38)

37

J2EE Engine Installation Steps 1

1) Install Database

Database

Engine CI

(39)

J2EE Engine Installation Steps 2

1) Install DB 2) Install SCS + bootstrap component Database Engine CI JControl SAPInst

(40)

39

J2EE Engine Installation Steps 3

1) Install DB 2) Install SCS + bootstrap component 3) Install SDM Database Engine CI SDM Repository SDM (standalone) JControl SAPInst

(41)

J2EE Engine Installation Steps 4

1) Install DB 2) Install SCS + bootstrap component 3) Install SDM 4) Configure SDM targets Database Engine CI SDM Repository SDM (standalone) JControl SAPInst

(42)

41

J2EE Engine Installation Steps 5

1) Install DB

2) Install SCS + bootstrap

component

3) Install SDM

4) Configure SDM targets

5) Configure JControl for SDM

Database

Engine CI

SDM Repository

SDM (standalone)

(43)

J2EE Engine Installation Steps 6

1) Install DB

component

3) Install SDM

6) Deploy Offline Deploy Tool, …

Database Engine CI SDM Repository SDM (standalone) Offline Deploy Tool JControl SAPInst

(44)

43

J2EE Engine Installation Steps 7

1) Install DB

component

3) Install SDM

7) Deploy tables for Config-DB

Database Engine CI Config DB: SDM Repository SDM (standalone) Offline Deploy Tool JControl SAPInst

(45)

J2EE Engine Installation Steps 8

1) Install DB

component

3) Install SDM

8) Deploy Engine Components

Database Engine CI Config DB: Engine comp's SDM Repository SDM (standalone) Offline Deploy Tool JControl SAPInst

(46)

45

J2EE Engine Installation Steps 9

1) Install DB

component

3) Install SDM

9) Start J2EE Engine

Database Engine CI Config DB: Engine comp's SDM Repository SDM (standalone) Offline Deploy Tool J2EE Server deploy service... J2EE Dispatcher JControl SAPInst

(47)

J2EE Engine Installation Steps 10

1) Install DB

component

3) Install SDM

10) Deploy Applications Database Engine CI Config DB: Engine comp's Appl DB: Appl data SDM Repository SDM (standalone) Offline Deploy Tool J2EE Server deploy service... J2EE Dispatcher JControl SAPInst

(48)

47

J2EE Engine Installation Steps 11

1) Install DB

component

3) Install SDM

10) Deploy Applications 11) Start SDM Server Database Engine CI Config DB: Engine comp's Appl DB: Appl data SDM Repository SDM Server (integrated) Offline Deploy Tool J2EE Server deploy service... J2EE Dispatcher JControl SAPInst

(49)

J2EE Engine Installation Steps 12

1) Install DB

component

3) Install SDM

10) Deploy Applications 11) Start SDM Server

12) Install Developer Studio (Optional) Database Engine CI Config DB: Engine comp's Appl DB: Appl data SDM Repository SDM Server (integrated) Offline Deploy Tool J2EE Server deploy service... J2EE Dispatcher JControl SAPInst SAP Netweaver Developer Studio

(50)

49

Installation of SAP Web AS Java: Lesson Objectives

You should now be able to:

Plan your Web AS Java Installation. Understand the document changes

Understand the changes in the SAPInst process

Migrate/upgrade your previous Web AS Java Installation. Understand the J2EE Engine installation steps

(51)

SAP Java Engine Administration – Exercises

Unit 1: Web AS Standalone Java Installation

Lesson 2: J2EE Engine Installation

At the conclusion of this exercise, you will be able to: • Install Web AS Java Engine with MaxDB

1. Installation of JDK 1.4

SUN JDK 1.4 latest SP is required for installing Web AS Java Engine.

http://java.sun.com/j2se/1.4.2/download.html

J2SE JRI is not enough to run Web AS Java, you must install JDK. 1-1 Check is the JDK installed on the box.

To check whether a JDK is installed in command prompt run command java –version

Note: The latest SP of the SUN JDK 1.4 may be newer than the shown on the screenshot.

(52)

2

1-2 Install JDK 1.4 if is not installed.

Take the JDK installation from the trainer. Or download it from SUN website.

(53)

2. Start the Web AS Installation

Go to the Web AS installation folder, provided from the trainer, or start the provided CD.

(54)

4

2-1 Install with SAPInst

After SAPInst has started navigate to -> SAP NetWeaver ’04 Java System (J2EE only) -> MaxDB -> Central System -> Custom Installation - Java System

And press Next.

Note: SAP distributes Web AS installation exclusively on DVD.

Nevertheless SAPInst is looking for CDs which you can find copied as folders in the DVD storage.

Choose SAP NetWeaver ’04 -> J2EE System -> Central System -> Install a J2EE Server in Custom Mode

Click on the icon in the white label bellow Package Location

(55)

G:/setup/SAP_NetWeaver_04_Java/J2EE

Choose the Installation CD label:

G:/setup/SAP_NetWeaver_04_Java/J2EE/LABEL.ASC And press OK.

On the next screen type ABC as a System ID

and press Next

(56)

6

G:/j2sdk1.4.2_03 (chosen by default) and press Next On the next screen choose Local installation!

and press next.

On the next screen type the passwords of the users: SAP Administrator Account: abcadm

Password: abcabc

SAP Service Account: SAPServiceABC Password: abcabc

(57)

Press Next

On the next screen choose 40 as SCS instance number. Leave empty the Message Server port.

(58)

8

On the next screen type 43 for the ABC J2EE Engine instance number Change the Number of J2EE Servers to 2.

Press Next

(59)

and press Next.

On the next screen type the passwords of the users: J2EE Administrator and Guest:

User: Administrator Password: abcabc User: Guest Password: guest

(60)

10

and press Next

On the next screen type the password of the SAP J2EE Engine schema DB user:

User: SAPABCDB Password: abcabc

(61)

and press Next

(62)

12

and press Next.

On the next screen click on the Package Location label

and navigate to the IGS installation folder G:/setup/SAP_NetWeaver_04_Java/IGS

(63)

Press OK, and press OK to go to next screen MaxDB CD: On the next screen MaxDB CD

(64)

14

Choose the folder:

G:/setup/MAX_DB_7.5.0_Build 07_RDBMS for the Package Location of MaxDB

and press OK to go to the next screen. On the next screen MaxDB CD

(65)

Choose the folder:

G:/setup/MAX_DB_7.5.0_Build 07_RDBMS for the Package Location of MaxDB

(66)

16

and press OK to go to the next screen.

(67)

On the next screen choose G:/ as DB Log folder and 500 MB as volume size:

and press Next.

On the next screen choose G:/ as DB Data folder and 500 as volume size:

(68)

18

and press Next

(69)

Check all the values on the next screen and press Start if everything is fine:

(70)

20

You see the installation screen:

(71)

If you get this message just press OK

The message saying that the installation has finished:

(72)

22

Note: You can monitor the installation steps and the SAPInst log file during the installation process.

(73)

3-1 Check installation.

When the installation finish start SAPMMS

Go to : Start -> Programs -> SAP Management Console

(74)

24

4-1 Installation of NetWeaver Developer Studio.

If the SAP NetWeaver Developer Studio is not installed on the master system…

…you can install it from: Navigate to the installation folder of Web AS -> sapinst -> opt -> J2EE-CD -> IDE

(75)

Note: When performing SAP NetWeaver ’04 Developer Workplace Installation, the NetWeaver Developer Studio is also installed!

(76)

26

4-1 Installation of SP7.

Now you have to continue with the upgrade to Support Package SP7.

The SP7 upgrade for MaxDB is available under folder:

G:\setup\ATP_Web_AS_6.40_TC_Track\TADMJ1\WAS_Installa tion\SP7_Upgrade

Start the sapinst.exe from folder:

G:\setup\ATP_Web_AS_6.40_TC_Track\TADMJ1\WAS_Installa tion\SP7_Upgrade\SAPINST-CD\SAPINST\NT\I386\sapinst.exe

(77)

and click Next.

On the next screen click Browse and navigate to the ABC Central instance profile:

G:\usr\sap\ABC\SYS\profile\ABC_SCS40_xxxx

(78)

28

and press Next.

On the next screen fill the Windows Domain name,

And the passwords of abcadm and SAPServiceABC users: The passwords should be abcabc if you haven’t chosen different ones during the previous installation.

(79)

and press Next

Press Start on the installation screen.

(80)

30

Check whether the ABCDB is running (with the SAPMMC), if it not - start it.

And press OK

(81)

(82)

32

The upgrade finishes successfully.

You can call the ABC main page using URL: http://localhost:54300/index.html

(83)

Course: SAP Java Engine Administration

1. Web AS Standalone Java Installation

2. Java Startup & Control Framework

3. Web AS Java Administration Tools Overview

4. SAP Java Administration

5. SAP Web Infrastructure

(84)

2

Unit: Web AS Standalone Java Installation

Java Start & Control Framework

Lesson:

(85)

Java Startup and

Control Framework

(86)

4

Java Startup and Control Framework: Lesson Objectives

After completing this lesson, you will be able to:

z Understand the startup process of SAP Web Application Server Java

z Understand the bootstrapping procedure.

z Understand what role they do play to locate and identify errors during server startup.

(87)

J2EE Startup Framework

(88)

6

This system provides the following functions: Operation using SAPGUI

z Users log on to the dispatcher and work processes perform the users’ tasks. Processing Web requests.

z Web requests are received by an Internet Communication Manager (ICM). These HTTP(S) requests may be designated for the Internet Communication Framework (ICF), that is, processed in an ABAP work process (for example, BSP Applications), or they may be J2EE requests, designated for the J2EE Engine.

z For each incoming HTTP request, the ICM must decide whether it should forward the request for processing to the ABAP engine (the ICF) or to the SAP J2EE engine. This decision is made using the URL prefix. A separate protocol is used for the communication between the ICM and Java Dispatcher. The ICM can be set up so that the communication with the J2EE Engine is SSL-encrypted.

The ICM server cache saves HTTP(S) objects before they are sent to the client. The next time an object is requested, then, the application gets the content directly from the cache before sending it to the client. You can also use the Internet Server Cache with the J2EE server, in order to store HTTP responses (such as

HTML pages or images). The next time, the request can be retrieved directly from the cache

The HTTP request handler uses the ICM Server Cache when, for example, response pages need to be re-used, such as the entry page of an online shop application. The ICM server cache saves the pages before they are sent to the client. When the page is next called, then the application gets the page directly from the ICM and sends it to the client.

Additionally to the ICM server HTTP(S) cash, the Java Dispatcher implements HTTP(S) cash as well.

To be able HTTP request to be redirected to the J2EE Engine, the following services must be active in the HTTP service tree (Transaction SICF):

/sap/public/icman - The ICM uses this service to forward requests to the J2EE Engine.

/sap/public/icf_info - Supplies the SAP Web Dispatcher with details of logon groups, server load, etc.

(89)

One Java Engine installation consists of:

One or more Java instances (Java Dispatcher, Server) and the Software Deployment Manager (SDM)

The Central Services (Messaging Service, Enqueue Service), which also create an instance (Central Instance)

Ax external database.

Changes in architecture of J2EE – Engine are made since 6.20

A J2EE Cluster now consists of an Central Service Instance. One Central Service Instance is required in the J2EE Cluster.

The Configuration of the J2EE Engines are now stored in a Database. Not any more stored in XML-Files in the file system. A database for the J2EE Cluster is required. An Startup and Stop Framework is used.

In a large Java cluster installation, the load is distributed from a load balancer onto the different Java dispatchers.

 Consists of a dispatcher process

and one ore more server processes

 Processes run on one host  Are started and stopped together  All server processes of all instances

of a system are grouped in a cluster

SAP Central Services

 Cluster wide communication  Central locking objects

Central Database

 System Software  Applications

 All configuration data

Software Delivery Manager

 keeps track of distributed software

Web AS Java Cluster Architecture

SAP Web AS Java Central Instance

SAP Web AS Java Central Instance J2EE Dispatcher Server Process Server Process Server Process SDM Central Services

SAP Web AS Java

J2EE Dispatcher Server Process Server Process

Server Process SAP Web AS JavaSAP Web AS Java J2EE Dispatcher

Server Process Server Process Server Process

J2EE

J2EE schemaschema

DB DB

SAP Web AS Java Cluster

(90)

8

The Central Services run on one physical server and are one Java instance. They comprise the Message service and the Enqueue service.

The Central Services form the basis of communication and synchronization for the Java cluster. Central Services are always required when a Java cluster is installed. They are started on a server

with their own system number and the system ID (SID) of the whole system.

When Central Services are running, further Java instances (Dispatcher, Server) are started with the program JControl

The message service is a separate program used for communication between the elements of a Java cluster. It keeps a list of all processes (dispatchers and server) of the Java cluster. It represents the infrastructure for data exchange (small datasets only) between the participating nodes. The message service also supplies information to the SAP Web Dispatcher about Load Balancing.

Processes on Operating system level NT: msg_server.exe UNIX: msg_server

Trace file:

dev_ms in work directory of Central Service Instance

The settings and the status of the message service are made accessible to the administrator via the message Info Service in Visual Administrator described bellow.

Message server and Message Service are used synonymously. The correct expression would be that the Message Server is a process or program that provides the Message Service.

Central Service - Message Service

Tasks of the Message service:

 Notification of events that arise in the cluster.  Communication between different services

 Forwarding of messages and requests to all participants (broadcast)

 Prepare logon information for the SAP Web Dispatcher  Support for message server failover

 Guaranteed message transmission

(91)

The message info service is the interface between the J2EE Engine and the Message Service, it is used it to monitor and administrate the message server. The message service doesn’t communicate direct to the Message Server, but it is

using the cluster manager, which has a direct connection to the message server. The message info service is not automatically started when the J2EE Engine is

started. If should be started manually:

zUsing the SAP J2EE Engine visual administrator. 1. Choose Cluster→ Server 0 → Services

2. Choose Message Info

3. Choose Start Service in the toolbar zUsing the telnet console.

1.In the console where the server process is running, enter the command: startservice msp

• The Message Info Service data should be used mostly for supportability purposes, be careful

(92)

10

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 also maps the logical locks to the database.

The Enqueue service can be configured for high availability, by setting it up with the replication server and a platform-independent high availability solution.

The status of the Enqueue service are made accessible to the administrator via the Locking Adapter Service in the Visual Administrator.

The terms Enqueue server and Enqueue service are used synonymously. The

correct expression is that the Enqueue server is the program or process that provides the Enqueue service.

Enqueue Service is represented by an en.sap<SAPSID> process

Central Service - Enqueue Service

Enqueue Servicemanages logical database locks, which are set by the executed application program in a server process. Enqueue Servicesynchronizes data across the cluster.

(93)

The locking adapter service establishes the interface between the J2EE Engine and the enqueue service. You can display and manage locks, carry out tests, and display statistics.

The locking adapter service is available on each server process, but it is not available on the dispatcher. It connects to the Enqueue Service and fetches requested data or sends changed data to it. As there is only one enqueue server in the system, all the locking services of the various server processes have the same information. Therefore it is not important on which server process you use the locking adapter service.

Locks are used for example during deployment of applications. The configuration manager requests a lock from the Locking Manager. The Locking Manager in turn requests the lock from the Enqueue Service. The relevant area in the database is locked

To look into the Locking Adapter use the following path: 1. Start the SAP J2EE Engine visual administrator. 2. Choose Cluster -> Server 0 -> Services 3. Choose Locking Adapter

 Choose the Runtime tab page to see a list of the functions offered in the locking adapter service: z To display existing locks; choose Display Locks.

z To set and release locks, choose Create/Release Lock.

z To delete existing locks, select the locks and choose Delete Selected Locks.

z To run test programs, choose Run Tests. To run functional tests choose Execute Functional Tests, and to load tests choose Execute Load Tests).

z To display files, choose View Files. You can view the profile data or the trace file of the lowest layer of the enqueue service. This is useful for looking for errors.

Locking Adapter in the Visual Administrator

With the Locking Adapter checks and tests of the Enqueue Service can be done.

(94)

12

A Java instance is a unit in the SAP Web Java cluster, which can be started,

stopped, and monitored separately. It runs on a physical server; but it is also possible to run several instances on one server. An instance is identified by the system ID (SID) and the instance number.

One Java instance contains at least one Dispatcher and one Server Process, the Central Services (Message, Enqueue) and the SDM.

A Java instance is started and stopped by the Java Startup and Control Framework. The Java dispatcher receives the client request and forwards it to the server process

with the lowest capacity usage. If there is already a connection to the client, the request goes to the server process that processes this client.

Dispatcher processes are represented by a jlaunch processes

The Java Dispatchers do not communicate to each other, they are light applications used for load balancing to the local servers only.

Interprocess communication Dispatcher on one box – Server on other box is not possible.

Java Instance – Java Dispatcher

Java Dispatcher components:

Connection request handler

receives the first request from a client. From this time point on, the client has a fixed connection to the dispatcher.

Connection managermanages the existing connections to the clients.

Session level servicesare services that are assigned to a session.

Communication handlerforwards the request to the server process. Accumulating requests are stored in the request queue.

(95)

The Server Processes of the J2EE Engine actually execute the J2EE application. Each server process is multi-threaded, and can therefore process a large number of requests simultaneously. Java Dispatcher assigns requests to the server processes. The identification of the jlaunch processes can be easy done with their PID, the PID

is also represented in the monitoring tools as the SAP Management Console.

Java Instance – Server Process

Server Process components:

Connection request handler

receives the first request from a client. From this time point on, the client has a fixed connection to the dispatcher.

Session level servicesare services that are assigned to a session.

Application-level servicesor the actual application program.

(96)

14

Another special instance is the one that installed the SDM (Software Deployment Manager). This one usually runs with the database and Central Services on the same machine and is then indicated as the central instance.

The Software Deployment Manager (SDM) is a tool with which you can manage and deploy software packages that you receive from SAP or created with NetWeaver Developer Studio.

The Software Deployment Manager (SDM) groups several different deployment types in a single network interface for the deployment of any software that you develop with the SAP NetWeaver Developer Studio.

In all modes SDM is only able to handle one access at a time.

SDM Instance

Software Deployment Manager (SDM)

 SDM Server

started automatically as part of WEB AS 6.40

one SDM Server per WEB AS 6.40 with J2EE Engine is necessary

 SDM Interfaces

Commandline Interface (sdm.bat or sdm.sh)

z A new SDM process is started each time a

command is executed

z No SDM Server may run at the same time

(this is checked).

JAVA API (SDMclient.sda) needs a running SDM Server

SDM Gui (sdmgui.bat or sdmgui.sh) needs a running SDM Server

J2EE Disp atch er J2EE Server process SDM

(97)

J2EE Startup Framework

(98)

16

The Java startup and control framework comprises the programs JControl and Jlaunch. JLaunch is started by JControl and itself starts the bootstrap Java program or an element of the Java Instance (dispatcher or server process). Whereas the Jcmon is a command line monitor program and is used to administrate the framework.

Java startup and control framework is used to start, monitor, and stop a Java instance: Integration of Java Processes into the SAP instance concept Inherit all management concepts from the ABAP stack

Integration into existing SAP instance management

Control and Restart functionality of J2EE processes (Watchdog) Daemons for NT (sapserv.exe)

Remote Control of all J2EE instances in the cluster Cluster wide management (shutdown, restart ...)

Integration of the Startup Framework Client into the IDE Preparation of Remote Debugging Support

J2EE Startup Framework – Overview

The J2EE Startup and Control Framework

 … is an infrastructure, situated between the operating system and

the Java VM

 … is used to start, stop, and monitor a Java Instance

 … loads the JVM and restarts processes, which have died/crashed  … comprises the programs Jcontrol, Jlaunch and Jcmon

(99)

Starting and Stopping

The Java startup and control framework is called in different ways according to the operating system and the installation type:

 Under Windows the SAP Management Console is used.

If you choose an instance containing a J2EE engine Action → Start, the JControl program is called.

 Under UNIX platforms and OS/400 the scripts startsap and

(100)

18

 On the SAP system host, choose Start -> Programs -> SAP Management Console. You use this procedure to start/stop and monitor the processes of the SAP system

after the installation. You can use also the SAP NetWeaver Developer Studio when in development to start and stop the SAP system.

You have to start/stop monitor the following components: Database (SAP DB)

Central Services (Enqueue Service and Message Service) J2EE instances

Software Deployment Manager (SDM)

Start and Stop with SAPMMC (Windows)

J2EE Instance: Dispatcher Server 0...n SDM Central Services: Message Server Enqueue Server Database J2EE Engine System ID = C11 Start/Stop with Context Menu Process List with

State sign

Process Table with detailed info

(101)

The start and stop of the SAP system are done using the scripts startsap and stopsap in the exe directory.

You have to be logged on to the SAP system hosts as user <sapsid>adm.

If there are multiple SAP instances on one host – for example, a central instance and a dialog instance you have to add an extra parameter to the scripts:

startsap <instanceID>; stopsap <instanceID> For example, enter: startsap DVEBMGS00

SAP Web AS J2EE only system: The instance name (instance ID) of the central instance is JC<Instance_Number>, the instance name of a J2EE dialog instance is J<Instance_Number>.

To view all the processes use command: ps -ef | grep jlaunch

Starting and Stopping with scripts (UNIX & Windows)

Starting the SAP System

 startsap [db|r3|j2ee|ccms|all|check] [<instance>] [<virtual hostname>] Examples

 startsap - to start the whole system

 startsap j2ee DVEBMGS00 - to start the J2EE-Engine of the instance

DVEBMGS00. The instance name is required if more than one instance is configured.

 startsap r3 - to start only the ABAP part of the system

Stopping the SAP System

 stopsap [db|r3|j2ee|ccms|all|check] [<instance>] [<virtual hostname>] Examples

 stopsap - to stop the whole system

 stopsap j2ee DVEBMGS00 - to stop the J2EE-Engine of the instance

DVEBMGS00. The instance name is required if more than one instance is configured.