SAP NetWeaver 7.

5 - Java Application Server

System Administration
Features & Architecture

SAP Digital Business Services

e only with an image

Use this title slid
SAP AS Java 7.5 Features & Architecture
Agenda

SAP AS 7.5 Java - Features

SAP AS 7.5 Java - Architecture

SAP AS 7.5 Java - Startup & Control Framework

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 2

SAP AS Java 7.5 Features
HANA and Cloud Ready

 Possibility to use SAP HANA as database.

 Supports new and evolved technology trends like the Internet of Things (IoT), Big Data and Analytics.

 Easier Cloud integration with e.g. SAP HANA Cloud Platform (HCP).

 Runs on SAP JVM 8 to keep up the speed of innovation and benefit from new Java features.

 Build Java Hubs in single systems like SAP Enterprise Portal and SAP Business Warehouse or SAP Process

Orchestration which combines the power of SAP Business Process Management and SAP Process Integration.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 3

SAP AS Java 7.5 Features
User Experience (mostly relevant for EP)

 SAP Fiori as cross-application user experience.

 Out Of the Box mobile readiness with Fiori Launchpad on Portal.

 Standard SAP UI5 based applications like Unified Inbox or BPM Inbox.

 Leverage SAP UI5 1.38 libraries and above for custom UIs and applications.

 Seamless Integration with NetWeaver Business Client.

 Latest Browser support (Chrome, Edge, Safari, Firefox).

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 4

SAP AS Java 7.5 Features
Monitoring

Monitoring information available:

 Technical infrastructure (e.g. startup framework, ICM …)
 Processes, threads, queues, sessions, caches …
 VM details (e.g. GC) via SAP’s own Java VM

Easy and structured access to all monitoring data:

 Shared memory based approach
 Always available even if the VM doesn’t respond anymore
 Passive monitoring  no active request to retrieve information
 Everywhere accessible
 Web Service
 SAP MMC
 Java Management Console

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 5

SAP AS Java 7.5 Features
Robust and Easy to Maintain
JEE Engine Internal
 User request waiting for the processing are stored in a failover safe request queue based on shared memory.
 A Central Session Management controls the life-cycle of all sessions and enables to store & reactivate them
based on shared memory.
 A Central Cache Management to better control the memory consumption of the application’s caches.
 Java Connector (JCo) 3.0 Support.
 Better tools to detect and identify resource consumption problems.

NetWeaver Lifecycle
 Simplified migration and upgrade capabilities.
 True Zero Downtime maintenance.
 Leverages SAP Maintenance Planner.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 6

SAP AS Java 7.5 Features
Problem Tracking

On-the-fly debugging
 Switch on debug mode for a VM on-the-fly
 No restart of server node required
 No separate and isolated debugging node necessary
 SAP MMC Integration

Application debugging allows to debug only specific code areas

 Can be used in productive environments
 Switch on debug mode for a single thread of a VM on-the-fly
 Simulates a single threaded application for the debugging client (IDE)
 Isolates system-debugging from application-debugging

-> Those capabilities are based on SAP’s Java VM

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 7

SAP AS Java 7.5 Features & Architecture
Agenda

SAP AS 7.5 Java - Features

SAP AS 7.5 Java - Architecture

SAP AS 7.5 Java - Startup & Control Framework

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 8

SAP AS Java 7.5 Architecture
High Level Overview
A Java instance consists of an Internet Communication The database stores system and
Manager (ICM) and one or several server processes. application data. There is one central
The ICM handles requests coming from clients and database. It is also possible to have
dispatches them to the available server processes. several application databases.

Java Cluster
ICM Instance J01

Server Server Server Server

ICM
Node
Instance J02
Node Node Node
Database
Server Server Server Server
NodeJ03Node
Instance Node Node
ICM SAP Central Services

Server Server Server Server Messag Enqueue

Node Node Node Node
e Server Server

The central services instance consists

of a Message and Enqueue Server.
They are responsible for lock
administration, message exchange and
load balancing within the Java cluster.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 9

SAP AS Java 7.5 Architecture
Request Handling
Fast Channel Architecture
(FCA) – Inter-process
communication based on Shared Memory
shared memory.
for request and
response data
Java Server Process
Internet
Communication SAP JVM 8
Manager

for session data

Shared Memory
Database
HTTP Handler
FCA Java Server Process

P4 Handler SAP JVM 8 Java Schema

JMS Handler
Java Server Process
Shared Memory
for monitoring SAP JVM 8
data
Shared memory separated from Java
heap areas to share objects between
different JVMs.
Startup Framework

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 10

SAP AS Java 7.5 Architecture
Components View
Holds all
Applications like
Applications WebApps, EJBs etc.
in their runtime
containers like
WebContainer, EJB
Container etc.
JEE API SAP API
API Access

Startup Order

Provides various
Facades SAP Java EE runtime functions
System and programming
APIs
Libraries Services Interfaces Components

Comprises low-
Framework API level subsystems
that provide
functions such as
class loading,
cluster
Managers SAP Java Enterprise Runtime communication,
persistent
configuration data
management, and
so on.
© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 11
SAP AS Java 7.5 Architecture
Thread Manager

 The thread system is responsible for handling system and application threads.
 Comprises two main managers - Application Thread Manager and Thread Manager:

 Application Thread Manager

It handles client requests coming to the system. When a client request comes, the system tries to find a free thread in the
Application Thread Manager. If no free thread is available, the thread system buffers the request in a request queue.

 Thread Manager

The Thread Manager pool is used for system activities such as internal cluster communication, event processing, backup of log
records, background processes for collecting and storing data, and so on.

 Division into two thread pools prevents situations where there are too many clients that block the system.
 Monitor thread system information using the SAP Management Console.
 SAP JVM provides additional thread information like user name or CPU usage.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 12

SAP AS Java 7.5 Architecture
Cache Manager
CML Basic Functionalities
 The user API is comparable with commonly used caches and offers common cache functionalities.
 Eviction handling of objects by the framework.

Configurability
 Central configuration of all caches.
 User is able to change the behavior (scope, thresholds, eviction …).

Administration
 Central monitoring of all caches (hit rate, miss rate, request count, update count, remove count, eviction
count, utilization etc.).
 Allowing system wide cache analysis and optimization via SAP MMC.

Advanced Concepts
 Sharing of caches between all nodes of an instance.
 Cluster wide invalidation of cached objects.
 Tools to analyze the cache size & behavior for each region.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 13

SAP AS Java 7.5 Architecture
Session Manager

Session Management System

 Sessions are used to keep the state of a user accessing an application between several requests.

 The Session Manager, is responsible for enhanced control of sessions lifecycle and mechanisms for

session failover in case of a server failure.

 Separation of inactive user sessions and active sessions provides higher session count per VM.

 Active sessions are stored in the VM memory while inactive sessions are stored in shared memory.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 14

SAP AS Java 7.5 Architecture

Hands On Session
Basic Architecture

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 15

SAP AS Java 7.5 Features & Architecture
Agenda

SAP AS 7.5 Java - Features

SAP AS 7.5 Java - Architecture

SAP AS 7.5 Java - Startup & Control Framework

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 16

Startup & Control Framework
Overview

 The Startup Framework is used to centrally manage the process lifecycle of the AS Java.

 It is used to start, stop and monitor the AS Java.

 It restarts processes in case of process failure.

 It displays the trace files, the system environment, and the SAP system environment.

 Can be used to trigger thread dumps and view VM trace files.

 Can be administrated with the SAP MC or Jsmon.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 17

Startup & Control Framework
Components
JStart - Instance controller
 Starts, Stops, and Monitors the processes of a Java instance.
 The program implements the SAP signal handling to start and stop the instance.
 As the master process of all the JEE processes JStart starts the child JStart processes.

Offline deployment
 This Java program deploys and updates services and kernel components into the Java database.

Bootstrap
 This Java program synchronises the binary data from the Java database with the local file system and creates a
property file, which describes the processes of the Java instance.

JStart – Child Processes

 Starts a Java program.
 Loads the JVM into its own address space and then represents the required cluster element.
 Receives notifications from parent JStart via named pipes to stop the cluster element(s).
 Terminates the process if the parent JStart stops running.

JSMon
 A native command based control and monitoring program, equivalent to the SAP MC.
 Can disable / enable processes controlled by the Instance Controller JStart.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 18

Startup & Control Framework
Architecture

R
SAP MMC
R
SAP Start Service JSMon / JCMon
Webservice
control control

Java instance controller (JStart)

control control

R Database
Java
monitoring and Application
HTTP session Java data
Java
management Java
server
server Configuration
ICM server
nodes
nodes
Request & nodes
(JStart)
(JStart)
R response (JStart)
data File System
P4
Shared Memory Java Archives

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 19

Startup & Control Framework
Startup Sequence
1. SAP Start Service starts JStart

2. Read instance descriptions from file system

instance Profile
startup.properties

JStart (Instance Controller) 3. Start Offline deployment

Deploy and update
JStart components in Java DB

JVM
Offline deploy DB

JAVA

Store Instance
4. Start Bootstrap Process Description in a file
instance.properties
JStart

JVM
Bootstrap
Synchronize Binaries from DB DB
with the local file System
JAVA

5. Start the JEE Instance processes

ICM

6. Control the JEE Instance processes

Server
ServerNode

JVM
- restart after crash Node

JVM
Server Node

JVM
- send shutdown signal
JVM - terminate hanging processes
Java Instance

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 20

Startup & Control Framework
Trace Files & Troubleshooting
Developer Trace Files are located in folder:
/usr/sap/<SID>/<JXX>/work

 The trace files are per default written with trace level 1.
dev_jstart
trace file of JStart
• Detailed property description
• Description of the processes started by JStart 0: No trace
 dev_deployment 1: Write error messages in the trace file.
trace file of the deployment process 2: Full trace. The trace entries that are actually
 dev_bootstrap written can vary with the program that is being
trace file of the bootstrap process traced.
 dev_icm 3: Additionally, trace data blocks.
trace file of the icm process
 dev_server<x>
-> Change Trace Level with the SAP MC on the fly if
trace files of the JEE server nodes necessary.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 21

SAP AS Java 7.5 Architecture

Hands On Session
Start & Stop

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Customer 22

Thank You!