The ABAP/J2EE Intersection

Installation & Administration Primer

Introduction
There is much ABAP Basis knowledge in SAP Consulting and in marketplace. There is a lot of <NW04 SAP J2EE Engine Java-only knowledge in SAP Consulting and among SAP Enterprise Portal 6.0 customers. Focus in this presentation is on characteristics of WebAS 6.40 ABAP+JAVA presuming readers JAVA-only familiarity or ABAPonly familiarity.

SAP AG 2002, Title of Presentation, Speaker Name / 2

Topics Covered
SAP WebAS 6.40 ABAP + JAVA installation and distribution options SAP WebAS 6.40 ABAP+Java planning, installation and postinstallation basics for:
n n n ABAP JAVA Add-In Dialog Instances

SAP WebAS 6.40 ABAP technology basics SAP Web AS 6.40 ABAP and JAVA integration technology SAP WebAS 6.40 ABAP+JAVA basic administration

SAP AG 2002, Title of Presentation, Speaker Name / 3

SAP Web AS 6.40 ABAP + JAVA

Installation and Distribution Options

SAP AG 2002, Title of Presentation, Speaker Name / 4

SAP Web AS 6.40 Installation Options (<= (at least) Stack 05)

SAP WebAS 6.40 ABAP SAP WebAS 6.40 ABAP + JAVA

Is same in every way as 1. above but adds JAVA instance.

WebAS 6.40 JAVA

1. No ABAP; no possibility of ABAP since ABAP+JAVA is created only one way, in the following order ABAP installation then JAVA Add-In installation. Enterprise Portal 6.0 supported on this option only.

2.

SAP AG 2002, Title of Presentation, Speaker Name / 5

SAP Web AS 6.40 Installation Options (II)

SAP AG 2002, Title of Presentation, Speaker Name / 6

SAP Web AS 6.40 Installation Options (III)

NW04 Technical Scenario

Variant ABAP

Variant ABAP/JAVA

Variant JAVA

Development Environment ABAP and BSP Java application with ABAP functionality Developer Studio and Workplace JDI

SAP AG 2002, Title of Presentation, Speaker Name / 7

SAP Web AS 6.40 Installation Options (IV)

NW04 Technical Scenario Variant ABAP Variant ABAP/JAVA Variant JAVA

SAP Exchange Infrastructure* SAP Business Information Warehouse* BI Information Broadcasting* SAP Enterprise Portal 6.0 SAP Mobile Infrastructure SAP Knowledge Warehouse
SAP AG 2002, Title of Presentation, Speaker Name / 8

Distribution of SAP Web AS 6.40 ABAP + JAVA Central System Distributed System
Landscape types in a single installation; either/or

Central Instance (ABAP) Central Services Instance (JAVA) Database Instance

Actual technical components in installations implementing processes and functions;and

SAP AG 2002, Title of Presentation, Speaker Name / 9

Distribution of SAP Web AS 6.40 ABAP+JAVA (II)

Central System

All components on a single system

Central Instance Central Services Instance Database Instance

SAP AG 2002, Title of Presentation, Speaker Name / 10

Distribution of SAP Web AS 6.40 ABAP+JAVA (III)

Distributed System

Central Instance and Central Services Instance always installed together in a ABAP+JAVA installation.

Database instance on a different system

SAP AG 2002, Title of Presentation, Speaker Name / 11

SAP Web AS 6.40 ABAP + JAVA

Planning, Installation, Post-Installation

SAP AG 2002, Title of Presentation, Speaker Name / 12

SAP WebAS 6.40 ABAP + JAVA Installation Planning: Installation Documents

Planning
n Master Guide SAP NetWeaver 04 n Upgrade Master Guide SAP NetWeaver 04

Installation
n Planning Guide SAP Web AS on UNIX:Oracle n Parameter Guide Central/Distributed SAP Web AS installation option
u

Only UNIX/Oracle has these guides at this time.

n n n n n n

Inst. Guide- SAP Web AS ABAP 6.40 on operating_system: database Inst. Guide- SAP Web AS JAVA 6.40 on operating_system: database Installation Guide Additional Instances on operating system SAP Software on UNIX: OS Dependencies Troubleshooting Guide for SAP Web AS Java Installation SAP Front End Installation Guide

Upgrade
n Component Upgrade Guide SAP Web AS 6.40: operating_system

SAP AG 2002, Title of Presentation, Speaker Name / 13

SAP Web AS 6.40 ABAP + JAVA Installation (II) Planning

nPlatform Availability Matrix
n http://service.sap.com/nw04 > Product Availability Matrix nSynonyms used may confuse you:
n n n n n SAP Master DVD = SAP Installation Master DVD SAP System = SAP Web AS 6.40 SAP Web AS Java system = SAP Web AS J2EE system SAP Web AS ABAP+Java system = SAP Web AS ABAP+J2EE system 2-4 bits per character vs. 1-2 bits per character.

nUnicode installation requires 50% more RAM.

nSAP Notes are critical to successful installation!

n And there are roughly twice as many as any single ABAP or JAVA installation! nCentral Instance is installed first, Database Instance second. nAll UNIX installations begin with important O/S settings defined in SAP Software on UNIX: OS Dependencies. nSAP Gateway instance is installed by default on ABAP instance.* Can integrate at ABAP installation LDAP server:
n n Enables SAP Logon and MMC to reference LDAP server for system information. Not to be confused with using LDAP as user persistence store in Enterprise Portal, for example.

SAP AG 2002, Title of Presentation, Speaker Name / 14

SAP Web AS 6.40 ABAP+JAVA Installation (III) Database Planning

Standard:
n 1 DB per system/instance n ABAP and J2EE schemas in the same database

MCOD: Multiple Components in One Database

n One logical and physical database instance that contains all the data from different SAP components. n Cannot install Unicode and non-Unicode systems in this fashion! n See http://service.sap.com/mcod for details.

ABAP database installation planning is critical due to potential size of database and nature of general use of ABAP installation as business transaction system (performance).
n Example: SAP Business Information Warehouse and SAP Exchange Infrastructure on SAP Web AS 6.40 each >13K tables, > 10GB at installation
u

BW DBs famously in terabyte range

Oracle RAC support for ABAP (CSN 527843) is in progress but Java does not yet support it at all.

SAP AG 2002, Title of Presentation, Speaker Name / 15

SAP Web AS 6.40 Installation - Java Add-In Planning

nSame planning as for ABAP installation but some decisions already made in ABAP installation:
n Central or Distributed Systems n JAVA Central Services always installed with ABAP Central Services n Database ABAP and JAVA schemas created in same database n Java memory and disk requirements must be determined and added to ABAP requirements to get total requirements

nJ(ava)dk version required presently >=1.4.2_05

n Installation notes define version required.

nABAP installation creates default clients. Additional clients are nearly always required and their creation is part of ABAP postinstallation activities. ABAP client copy must precede JAVA Add-In installation* nSAPinst option:
n SAP NetWeaver 04 ABAP + JAVA Add-In > database > uni- or non-Unicode > JAVA System Completion **

SAP AG 2002, Title of Presentation, Speaker Name / 16

SAP Web AS 6.40 Installation: Java Add-In (II)

Planning: Considerations unique to ABAP/JAVA integration

nSAPinst: SAP System Communication Parameters (ABAP<>JAVA):

n Will enter DDIC user ID password for productive client n SAPJSF user (in ABAP system for authenticating to ABAP system) creation/password n J2EE Administrator/Guest IDs are J2EE_ADMIN/J2EE_GUEST in JAVA Add-In installation (Administrator and Guest in JAVA-only installation)

nSystem Landscape Directory (SLD) connection is possible (and required for some solutions, i.e. SAP XI) nABAP as J2EE User Persistence must have performed planning prior to making this selection (may be irreversible!).*

SAP AG 2002, Title of Presentation, Speaker Name / 17

SAP Web AS 6.40 Installation: Dialog Instance Planning nABAP dialog instance must be installed first. nJAVA dialog instance must be installed second. nAny SAP Web AS 6.40 ABAP+JAVA installations JAVA dialog instances must have both ABAP and JAVA dialog instances installed on the system. nWhile planning is critical the scope is much smaller than Central and Database instances.

SAP AG 2002, Title of Presentation, Speaker Name / 18

SAP Web AS 6.40 ABAP Installation Post-Installation

nABAP installation creates default clients. Additional clients are nearly always required and their creation is part of post-installation activities. Client copy must precede JAVA Add-In installation** nOnline Documentation is standard installation requirement for ABAP systems and is a post-installation activity. nInstalling additional languages is a post-installation activity in some cases. nLike JAVA environment, default resources (i.e. Work Processes) are not necessarily adequate and may need to be configured (ABAP Tx SM50, RZ10, RZ11)
n n n http://help.sap.com/saphelp_nw04/helpdata/en/02/962817538111d1891b0000e8322f96/frameset.htm http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a5ef8505211d189550000e829fbbd/frameset.htm http://help.sap.com/saphelp_nw04/helpdata/en/76/e670375fbf307ee10000009b38f8cf/frameset.htm ***

nTransport Management System configuration is a necessary post-installation activity (Transaction STMS in client 000). nSAPGui for Windows installation on user workstation is always required.* nDefault client (000) User ID and passwords:
n n SAP* 06071992 DDIC 19920706

nAnalogous to SAP Web AS 6.40 Java instance, ABAP instance may require Support Package installation immediately after installation (Transaction SPAM).

nUse initial installation check transaction SM28

SAP AG 2002, Title of Presentation, Speaker Name / 19

SAP Web AS 6.40 ABAP Installation (II) Technical Components After Installation

SAP AG 2002, Title of Presentation, Speaker Name / 20

SAP Web AS 6.40 ABAP + Java Add-In Post-Installation* Logging Onto the System ABAP: Via SAPGui: Client 000 SAP* default pw or password set during installation

JAVA: http://<j2ee_engine_host>:<5<instance_no>00> > J2EE Engine Examples > J2EE_ADMIN/password Example: http://cdphl827:50000

SAP AG 2002, Title of Presentation, Speaker Name / 21

SAP Web AS 6.40 ABAP + Java Add-In Post-Installation (II) Installing SAP License nTemporary license after installation lasts four weeks nInstall only on the ABAP system!
n Covers the JAVA system

nABAP transaction SLICENSE

SAP AG 2002, Title of Presentation, Speaker Name / 22

SAP Web AS 6.40 ABAP + Java Add-In Post-Installation (III) Deleting SAP Installation nJAVA Add-In may be deleted without affecting the ABAP installation. nProcess is well documented between the three (ABAP,JAVA, Additional Instances) Installation Guides.

SAP AG 2002, Title of Presentation, Speaker Name / 23

SAP Web AS 6.40 ABAP + JAVA Installation Technical Components After Java Add-In installation

SAP AG 2002, Title of Presentation, Speaker Name / 24

SAP Web AS 6.40 ABAP + JAVA Installation Technical components after Dialog Instance installation

SAP AG 2002, Title of Presentation, Speaker Name / 25

SAP Web AS 6.40 ABAP + JAVA

ABAP Technology Basics

SAP AG 2002, Title of Presentation, Speaker Name / 26

SAP Web AS 6.40 ABAP Technology File System

SAP AG 2002, Title of Presentation, Speaker Name / 27

SAP Web AS 6.40 ABAP Technology (II) Instance Name ABAP instances are named: DVEBMGS<nn> These letters represent the type of work processes in an ABAP application server, which implement the ABAP runtime. <nn> represents the instance number and is chosen by the human installer arbitrarily and avoids certain numbers (see installation guide). File structure is then: /usr/sap/<SID>/DVEBMGS<nn>/

SAP AG 2002, Title of Presentation, Speaker Name / 28

SAP Web AS 6.40 ABAP Technology (III) ABAP Personality

SAP AG 2002, Title of Presentation, Speaker Name / 29

SAP Web AS 6.40 Technology (IV) Client/Server Architecture

SAP AG 2002, Title of Presentation, Speaker Name / 30

SAP Web AS 6.40 ABAP Technology (V) ABAP Application Server

SAP AG 2002, Title of Presentation, Speaker Name / 31

SAP Web AS 6.40 ABAP Technology (VI) Dispatching Dialog Steps

SAP AG 2002, Title of Presentation, Speaker Name / 32

SAP Web AS 6.40 ABAP Technology (VII) Work Processes

SAP AG 2002, Title of Presentation, Speaker Name / 33

SAP Web AS 6.40 ABAP + JAVA

ABAP and JAVA Integrating Technology

SAP AG 2002, Title of Presentation, Speaker Name / 34

SAP Web AS 6.40 ABAP + JAVA Integrating Technology

SAP AG 2002, Title of Presentation, Speaker Name / 35

SAP Web AS 6.40 ABAP + JAVA Integrating Technology (II) Internet Communication Framework (ICF) Is the Web AS 6.40 infrastructure which: Enables SAP Web AS 6.40 ABAP to use HTTP(S) to expose ABAP functions to the Internet (BSPs, e.g.) in the server or client role by: Handling HTTP(S) requests to ABAP function modules and producing HTML HTTP(S) response. The ICF HTTP request handler for Business Server Pages is most commonly used. To operate the JAVA engine with ABAP basic ICF settings must be confirmed. An administrative interface (ABAP transaction SICF) is provided.

SAP AG 2002, Title of Presentation, Speaker Name / 36

SAP Web AS 6.40 ABAP+JAVA Integrating Technology (III) Internet Communication Manager (ICM)

SAP AG 2002, Title of Presentation, Speaker Name / 37

SAP Web AS 6.40 ABAP+JAVA Integrating Technology (IV) Internet Communication Manager (ICM) to ABAP

To J2EE

SAP AG 2002, Title of Presentation, Speaker Name / 38

SAP Web AS 6.40 ABAP+JAVA Integrating Technology (V) Internet Communication Manager (ICM) to JAVA

Java Dispatcher

From/To ICM

SAP AG 2002, Title of Presentation, Speaker Name / 39

SAP Web AS 6.40 ABAP+JAVA Integrating Technology (VI) SAP Web Dispatcher

SAP AG 2002, Title of Presentation, Speaker Name / 40

SAP Web AS 6.40 ABAP + JAVA Basic Administration

SAP AG 2002, Title of Presentation, Speaker Name / 41

SAP Web AS 6.40 ABAP + JAVA Administration Starting and Stopping the System - MMC

Right-click on any object to start and stop (and perform other functions)

SAP AG 2002, Title of Presentation, Speaker Name / 42

SAP Web AS 6.40 ABAP + JAVA Administration (II) Starting and Stopping the System - UNIX
Always from <sid>adm! On a Central System ABAP+JAVA: /exe/[start | stop]sap /exe/[start | stop]sap DB* /exe/[start | stop]sap R3 or J2EE all components database Central Instance and Central Services Instance On a Distributed System ABAP+JAVA: /exe/[start | stop]db* /exe/[start | stop]sap R3 or J2EE on database host CI/CSI

On a Dialog Instance ABAP+JAVA: /exe/[start | stop]sap

SAP AG 2002, Title of Presentation, Speaker Name / 43

SAP Web AS 6.40 ABAP + JAVA Administration (III) Starting and Stopping the System - UNIX
With Multiple Instances on Same Host: Stopping:
/exe/stopsap <instance ID>* OR**

/exe/stopsap R3 or J2EE <Instance ID of central instance> /exe/stopsap R3 or J2EE <Instance ID of central services instance>
.../stopdb*** Starting: /exe/startsap <instance ID>* OR /startdb /exe/startsap R3 or J2EE <Instance ID of Central Services Instance> /exe/startsap R3 or J2EE <Instance ID of Central Instance>

SAP AG 2002, Title of Presentation, Speaker Name / 44

SAP Web AS 6.40 ABAP + JAVA Administration (IV) Starting and Stopping the JAVA System ABAP Tx SMICM From inside ABAP you can stop and restart the JAVA instance:

SAP AG 2002, Title of Presentation, Speaker Name / 45

SAP Web AS 6.40 ABAP + JAVA Administration (V) File System Logs, traces, executables

ABAP Instance JAVA Instance

JAVA Central Services Instance

ABAP startup/shutdown trace files

JAVA startup/shutdown trace files ABAP Executables ABAP/JAVA startup parameter files (profiles)

SAP AG 2002, Title of Presentation, Speaker Name / 46

SAP Web AS 6.40 ABAP + JAVA Administration (VI) Support Packages

Support Packages for SAP NetWeaver are distributed as a Stack.
n Each SAP NetWeaver Stack identifies and implements component Support Package levels for each SAP NetWeaver component being used.

JAVA Support Packages installed with SAPinst and are cumulative. ABAP Support Packages installed with ABAP transaction SPAM and are not cumulative. ABAP Support Packages are per application component and always include at least Basis, ABAP and PI_Basis Support Packages. ABAP Support Packages also include kernel patch requirements (executable replacement). Normally upgrade ABAP before JAVA since ABAP has the component which is central to both systems the Internet Connection Manager (ICM). Upgrade flow and details very well documented in SAP NetWeaver 04 Support Package Stack <nn> guide released for each Stack.

SAP AG 2002, Title of Presentation, Speaker Name / 47

SAP Web AS 6.40 ABAP + JAVA Administration (VII) Support Packages http://service.sap.com/patches

SAP AG 2002, Title of Presentation, Speaker Name / 48

SAP Web AS 6.40 ABAP + JAVA Administration (VIII) Support Packages http://service.sap.com/patches

Select Support Package

Download

SAP AG 2002, Title of Presentation, Speaker Name / 49

SAP Web AS 6.40 ABAP + JAVA Administration (VIV) Support Packages http://service.sap.com/patches

SAP AG 2002, Title of Presentation, Speaker Name / 50

SAP Web AS 6.40 ABAP + JAVA Administration (X) Support Package Manager ABAP Transaction SPAM

SAP AG 2002, Title of Presentation, Speaker Name / 51

SAP Web AS 6.40 ABAP + JAVA Administration (XI) Support Package Manager ABAP Transaction SPAM (II)

SAP AG 2002, Title of Presentation, Speaker Name / 52

SAP Web AS 6.40 ABAP + JAVA Administration (XII) ABAP Work Processes Transaction SM50

SAP AG 2002, Title of Presentation, Speaker Name / 53

SAP Web AS 6.40 ABAP + JAVA Administration (XIII) ABAP Initial Installation Check ABAP Transaction SM28

SAP AG 2002, Title of Presentation, Speaker Name / 54

SAP Web AS 6.40 ABAP + JAVA Administration (XIV) Internet Communication Framework (ICF) ABAP Tx SICF

SAP AG 2002, Title of Presentation, Speaker Name / 55

SAP Web AS 6.40 ABAP + JAVA Administration (XV) Internet Communication Framework (ICF) ABAP Tx SICF

SAP AG 2002, Title of Presentation, Speaker Name / 56

SAP Web AS 6.40 ABAP + JAVA Administration (XVI) Internet Communication Manager (ICM) ABAP Tx SMICM

Status Summary

SAP AG 2002, Title of Presentation, Speaker Name / 57