SAP SYSTEM COPY AUTOMATION
Anwendertage
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
Highly Sheer number of steps & people,
manual order of the tasks, landscape complexity
Error Hundreds or thousands of steps
prone + databases, infrastructure, security
Fragmented Internal & external people, multiple IT
resources departments, constant communication
Drivers to Change
More frequent
New projects, test systems, migrations,
and complex
upgrades, disaster recovery
copies
Finite System copy eats up the resources
resources needed for critical projects
Fewer resources, less time, smaller
Cost
budgets
End-to-End Automation
Production System
Production System Preparation Execute Copy Verification
(cloned)
Copy of SAP
SAP system
Automate pre-copy Automate post copy production system
identified for copy Core Copy
requirements requirements running and
or cloning
available for use
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 After
14 days 5 days
13-15 people, 20 man- 8 people, 2 hours total
hours per day per day
Q&A system only, and More thorough, more
only once a year accurate, more often
Procedures on 87% of procedures are
paper checklist automated
We immediately saw a huge difference
How it works
1. Initialization
1. Initialization
Export
Redwood
System 2. Preprocessing
Copy File
SAP SAP
System
(source) (target)
Import
4. Postprocessing
3. Copy
Database Database
SAP system refresh process
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
Linux/Unix Windows ABAP
Oracle Native/JDBC JDBC BW
MS SQL JDBC PI
DB2 Native/JDBC JDBC Java
MaxDB JDBC JDBC Trex
Sybase JDBC JDBC LiveCache
HANA JDBC JDBC BO
All SAP databases are supported, including DB2/zOS Supported
All SAP ABAP stacks are supported, including BW on HANA Planned
Not supported
N/A
Questions?
Thank you!