SAP System Copy Workshop - Redwood · PDF fileEnd-to-End Automation Execute Copy Core Copy...

Anwendertage

SAP SYSTEM COPY AUTOMATION

Pain Questions

� How long does your System Copy process take?

� How often do you perform the System Copy process?

� Are you increasing the frequency of this process?

� How many people/teams are involved in the process?

� How much is this costing you?

� How many projects are delayed due to the System Copy process?

� What types of projects are delayed?

� How does this impact the business?

Challenges

Hundreds or thousands of steps

+ databases, infrastructure, security

Errorprone

Sheer number of steps & people,

order of the tasks, landscape complexity

Highlymanual

Internal & external people, multiple IT

departments, constant communication

Fragmentedresources

Drivers to Change

New projects, test systems, migrations,

upgrades, disaster recovery

More frequent and complex

copies

System copy eats up the resources

needed for critical projects

Finiteresources

Fewer resources, less time, smaller

budgets Cost

End-to-End Automation

Execute Copy

Core Copy

Production System

(cloned)

Copy of SAP

production system

running and

available for use

Verification

Automate post copy

requirements

Preparation

Automate pre-copy

requirements

Production System

SAP system

identified for copy

or cloning

Automating System Copy

� Template based design

� Automate pre- and post-refresh tasks

� Complete detail view of each step in the process

� Dashboard for a quick overview

Fortune 500 Industrial Supply Company

Before

� 14 days

� 13-15 people, 20 man-

hours per day

� Q&A system only, and

only once a year

� Procedures on

paper checklist

“We immediately saw a huge difference”

After

� 5 days

� 8 people, 2 hours total

per day

� More thorough, more

accurate, more often

� 87% of procedures are

automated

How it works

DatabaseDatabase

SAP

(source)

RedwoodSystemCopy

2. Preprocessing

4. Postprocessing

3. Copy

SAP

(target)

SAP system refresh process

FileSystem

Exp

ort

Imp

ort

1. Initialization

1. Initialization

Done ☺

Pre-processing

� Save system data

� Logical systems

� Logon groups

� RFC destinations (with passwords)

� User master

� SLD

� TMS

� qRFC

� ALE configuration

� SECSTORE

� ….

Post-processing 1/4

� Import preserved data into the SAP system

� Logical systems

� Logon groups

� RFC destinations

� User master

� SLD

� TMS

� qRFC

� ALE configuration

� SECSTORE

� ….

Post-processing 2/4

� BDLS

� Prepare database for BDLS

� Test logical systems

� Convert logical systems

� Reconfigure database

Post-processing 3/4

� Clean up the SAP system

� Batch jobs

� Joblogs

� TemSe

� Dumps

� Output devices

� …

Post-processing 4/4

� Configure the system

� Open/close clients

� Set login screen

� Create system message

Configuration Overview

System Configuration

Refresh in Acton

Refresh in Process Monitor

Landscape Refresh

Demo

Benefits

� Fast

� Reliable

� Repeatable

� Consistent

� Automatic notifications / Alerting

Value

Redwood SAP System Copy Automation Value

� Reduced Risk

� Eliminate manual actions

� Less potential for errors

� Higher Quality of Service

� Transparent SAP System Copy process

� Consistent process – every copied system will look the same

� Better Cost Efficiency

� More efficient use of computing resources

� More efficient use of manpower

� Faster SAP System Copy process

� Individual copies are executed faster

� Synchronized copies of entire SAP landscapes are possible

SAP System Copy - PAM

ABAP

BW

PI

Java

Trex

LiveCache

BO

Supported

Planned

Not supported

N/A

• All SAP databases are supported, including DB2/zOS

• All SAP ABAP stacks are supported, including BW on HANA

Linux/Unix Windows

Oracle Native/JDBC JDBC

MS SQL JDBC

DB2 Native/JDBC JDBC

MaxDB JDBC JDBC

Sybase JDBC JDBC

HANA JDBC JDBC

Questions?

� Thank you!