Installation of SAP S/4HANA System

Installation of SAP Filori front-end

Adapter
Installation of JAVA resource Adapter
Deploment options
-New system
-Existing System
-Co-deployment Model

It is recomanded that youplan for SAP fronend server log with 44hana system

SAP S/4hana Conversion

---In SAP Sollution Manager system
Impletemnt SAP Note: 2186164
Valid Read RFC detination to back-end technical system
---In SAP ERP back-end system
SPAM patch level version >59

---For maintenance planner precheck, SAP

s/HANA license is not mandatory

ADD-ON Compatibility Pre-check

Business Function Compatibility pre-check

Running Prechecks for SAP S4hana Conversion

Tile: Just to perform the Prechks.

But in order to generate stack file and to download the software you need
the valid license

It checks available product instances, product versions and softwares

componets are compatible for Sap S4HANA
As well as its checks the Business functions and connected JAVA Systems.

As part of single conversation process, you can perform Fronted

Installation and JAVA adapter system installation.

You can down load the result in PDF

If you have Valid License. You will find Continue Planning button:

Week -2

Week 2:
Unit 1: Introduction to Near-Zero Downtime Maintenance (nZDM) for Java

Near Zero Down time maintenance is a Procedure designed to minimize

the downtime of your maintenance activates in NetWeaver java based
systems.
It gives you the possibility to perform maintenance activities while the
business critical functionality is running and as a result highly minimizes
the downtime.

The Expected Downtime is around one system restart.

Business only mode.

System Switch Approach
Database switch approach

It Supports all kinds of support Activities

No additional charge for using the procedure

It has man 4 (Four) Phases

Prepare
Postprocess
Uptime
uptime

Maintain
Uptime

Switch
Downtime

NZDM JAVA Graphical user interface.

Which we use in order to start recording, Start the Replication and
Monitor the Progress of the all the whole procedure

We connect the Source system using it. (Using Graphical Interface) and
triger the recording there.
The Actual recording is triggered by Application server of the source
system it self.
After that we create our target system via cloning the source or via
system copy and then isolate it.

Completed. Question answerCompleted 100%

nZDM for JAVA More Details

Approach Comparison
NZDM can be finalized with system or Database Switch approach

1) SYSTEM Switch Approach

In the system Switch approach the target system replaces the source
system as the new production system.
The Source system is no longer needed and can be discarded

2) Database Switch Approach

The target system database replaces the Source System Database,
The Source system remains the Production system.
And the target system is no longer needed and can be discarded.

It Should be noted that the system switches approach is safer approach

then the database switch approach and it have less manual efforts.

Its uses some table in to Database

The tables are categorizing in three groups
1) Whitelist tables No triggers
2) Greylist Tables- recording triggers
3) Frozen Table- freeze triggers

1) Whitelist Tables are those tables whose information does not needed
have to retransferred to target system and you can ignore it.

2) Greylist Tables are those Record and then replicate

3) The Frozen Tables will be forbidden for any changes while the
procedure is running

While the recording is started, recording keytrigger are created on

Greylist tables and frozen tables
While the whitelist tables left without any triggers.

The table specification is preconfigured within procedure. There an

manual option to classify custom tables.

Once the Recording is running

Skiped Cluster setup

New One