advanced automation and optimization of system copy ... · pdf filewhite paper advanced...

WHITE PAPER

Advanced Automation and Optimization of System Copy Procedures for SAP® Systems

SAP® application environments include Quality Assurance (QA), Test, and other Staging

Systems in addition to actual Production Systems. These so called “non-production sys-

tems” are designated to manage the application lifecycle process. SAP recommends a

specific procedure called “system copy” to provide non-production systems with produc-

tion data for adequate and consistent testing.1

Typically, there are numerous manual tasks involved for executing the system copy proce-

dure which can spread over days and may block precious and expensive resources of the

most skilled SAP Basis professionals.

Libelle SystemCopy is a framework-based software solution to create fully automated

system copies. It furnishes ready-to-go QA or test system with fresh production data.

SystemCopy supports single- or dual-stack SAP software implementations on Oracle®,

SAP MaxDB® database, SAP HANA

®, Sybase/SAP

® Adaptive Server

® Enterprise, DB2

®,

or Microsoft SQL Server®

databases, and can be integrated into popular Storage Snap-

shots® or SnapMirror

® tools. As an alternative, the solution includes a copy tool for all plat-

forms. System copy tasks can run outside the ABAP® stack and include database im-

port/export operation, command scripts, SQL operations, or the execution of SAP transac-

tions.

This white paper describes the process involved in the creation of homogenous

system copies and outlines how procedures can be automated with the

SystemCopy solution.

1 SAP Help Files (Link)

http://help.sap.com/saphelp_nw70/helpdata/en/a2/2f0c173a5e43d19585724239ff4de7/content.htm

©Libelle AG. All rights reserved. April 15 1 / 13

WHITE PAPER

Table of Contents

SAP Application Life Cycle and System Copies .......................................................... 2

System Copy Terminology ........................................................................................... 3

System Copy Dependencies ........................................................................................ 3

System Copy Phases ................................................................................................... 3

System Copy Tasks ..................................................................................................... 4

System Copy Procedure: System Pre-Checks ......................................................... 5

System Copy Procedure: Pre-Processing ................................................................. 5

System Copy Procedure: Copy ................................................................................. 5

System Copy Procedure: Post-Processing ............................................................... 6

System Copy Challenges ............................................................................................. 6

Automating System Copies with Libelle SystemCopy ................................................ 7

The Libelle SystemCopy Framework .......................................................................... 7

SystemCopy Architecture ............................................................................................ 8

SystemCopy Tasks ................................................................................................... 10

Task Configuration and Repository ............................................................................ 11

Executing the System Copy ....................................................................................... 12

Managing Multiple Configurations .............................................................................. 12

Completing the Copy and Process Optimization ....................................................... 12

Summary .................................................................................................................... 13


WHITE PAPER

SAP Application Life Cycle and System Copies

SAP AG provides an organizational model to help companies with a holistic and integra-

ted ITIL-based approach for managing the lifecycle of SAP applications.1 Customers

typically implement a 3-tier deployment architecture comprised of (a) development or

test systems (DEV) where applications are developed and tested, (b) quality assurance

systems (QA, also commonly referred to as staging systems) where final testing takes

place, and (c) production systems to serve the actual SAP user. Customers may also

have additional nonproduction systems such as training or “sandbox” systems for other

purposes.

Application Life Cycle

The application life cycle for SAP systems is typi-cally managed with a 3-Tier Deployment Archi-tecture.

SAP specialists from external consulting firms or the internal SAP professionals are

usually in charge of providing these QA and DEV landscapes. The procedure is critical

to adequately simulate the production systems for coherent and consistent testing and

staging procedures. Providing these nonproduction systems with actual production data

is typically done by performing a homogenous system copy from production systems to

one or multiple nonproduction systems.

System Refresh

A Homogenous System Copy furnishes QA or Test Systems with pro-duction data.

1 SAP Developer Network (Link)

http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/b08e4bd4-b4ba-2c10-92a9-af4e46fdb59e


WHITE PAPER

System copy procedures are executed any time, from once a year to every month de-

pending on the SAP application and implementation. This also depends on in which

stage of the deployment project a customer is and what the internal testing procedures

require.

System Copy Terminology

In the various system copy guides that SAP AG provides on the SAP Service Market-

place extranet, there is consistent terminology in regard to the system copy procedure:1

System copy: Duplication of SAP systems; certain SAP parameters change

Source system: The SAP system containing the original production database

Target system: The system to which the database copy is copied

Homogenous system copy:2 System copy to the same operating system and

database platform as the Source system

Database copy: Database-dependent part of the system copy

System Copy Dependencies

SAP AG provides specific system copy guides for each of its enterprise applications that

may differ depending on factors such as:

Type of SAP application (e.g. SAP ERP application, SAP NetWeaver BW)

Version of SAP application

Type of implementation (single- or dual-stack)

Database type and version

Operating system

Within this procedural structure, customers typically enhance, add, or remove certain

system copy tasks to adjust to their very specific installations and circumstances. While

the general procedure is then similar for certain configurations, individual installations

vary in details.

System Copy Phases

Generally, all steps necessary to successfully complete a system copy procedure can

be categorized into three steps: Before the data on the target system is refreshed, there

is certain pre-processing required. This is followed by copying the actual data, and

completed with post-processing. The steps are defined as follows:

1 E.g. “System Copy for SAP Systems based on SAP NetWeaver 7.1 Java,” December 2009. link 2 SAP also lists a Heterogeneous System Copy procedure where the database or O/S platform changes. This is currently not covered in the Libelle

SystemCopy procedure and is not part of this white paper.


WHITE PAPER

1. Pre-Processing: All tasks for preparing the target system for the system copy

2. Copy: Providing a copy of the actual production database to target from source

3. Post-Processing: All tasks after the copy to complete the homogeneous system

copy procedure and to provide a complete QA or test system to the users

Distinguishing these three steps into pre-processing, copy, and post-processing is criti-

cal for structuring task details on and for determining how the tasks can be automated.

System Copy Phases

The system copy proce-dure is executed in three phases.

System Copy Tasks

The very core of a system copy procedure is to follow a number of specific, more or less

predefined steps such as executing a database backup or starting specific SAP transac-

tions in a specific order. For the purpose of automation, we encapsulate and abstract

these steps into tasks that are assigned to the system copy phases:

Tasks

Each phase of the proce-dure includes a number of encapsulated tasks.

Most tasks are executed on the target, but some of them may run on the source sys-

tem. System copy tasks are categorized into any of the following task types:

1. Execute prepared SQL statements on source or target systems

2. Execute database imports or exports

3. Execute ABAP transactions

4. Execute Windows® or UNIX

® shell scripts

5. Trigger external tools (e.g., Snapshots)

6. Manual breakpoints where an administrator wants to execute certain steps


WHITE PAPER

Tasks are executed sequentially and subsequent tasks depend on return values or suc-

cessful completion of previous tasks. The key to successful automation is to encapsu-

late system copy tasks according to SAP AG’s guidelines, internal necessities, and ex-

ternal best practices. Later in this white paper, you will learn how the Libelle System-

Copy tool handles this procedure and how the execution of all tasks can be automated

and managed – from starting the system copy up to the point where a finished QA sys-

tem can be handed over to the users.

System Copy Procedure: System Pre-Checks

Before executing the pre-processing, copy, and post-processing steps, the system copy

procedure implies that certain prerequisites are met. System pre-checks validate

system availability and disk space, match versions between source and target, verify

compatibility of parameters, and more. Especially if the procedure is automated later

and is scheduled to run overnight, we don’t want to find that missing system

permissions, disk space, or an SAP license prevented us from completing the

procedure.

System Copy Procedure: Pre-Processing

The pre-processing phase of the system copy procedure prepares the target system to

receive current production data. As the complete target database is overwritten with

fresh production data, certain information must be pulled from the target system ahead

of time. This mostly includes exporting various QA-specific tables, log-on groups, admin

tables, Remote Function Call (RFC) settings, development user tables, and much more.

For Java stacks, we may also want to export the target system configuration files. On

the target system it may also be necessary to stop scheduler, backup jobs, or anything

that we do not want interfering with the system refresh. Finally, the last task of the pre-

processing procedure is then to stop the target system.

Pre-Processing

Target System is pre-pared for the copy phase.

System Copy Procedure: Copy

The copy phase is replacing all the complete target database (and flat files for dual-

stack installations) with the source database and renaming the database (SID) from,

e.g., PR1 to QA1 (because the QA target system runs under a different database SID.)


WHITE PAPER

Copy

Target System is refreshed with fresh pro-duction data.

There are various ways to provide a copy of the database. Customers may utilize stor-

age snapshot tools and scripts to rename the database to provide this copy. Other op-

tions are database copy tools such as the Libelle BusinessShadow® tool to automati-

cally copy and rename Oracle, SAP MaxDB, SAP HANA®, Sybase/SAP

® Adaptive

Server® Enterprise, DB2, or MS SQL Server databases.

System Copy Procedure: Post-Processing

The last phase of the system copy procedure is by far the most complex since a large

number of tasks have to be executed. While the database was already renamed in the

copy phase, we need to adjust additional database settings to match the target envi-

ronment and perform other related tasks. Finally, the target system must be furnished

with a valid SAP license, and specific table entries must be replaced with the content

relevant to the target system (either preconfigured data or exported data from the pre-

processing phase).

Some of the tasks will be generic for most SAP applications, and some other tasks are

specific to the SAP application and version. An SAP NetWeaver BW component for

example, may require that the indexes be rebuilt; systems with Java stacks may require

additional imports or exports or a reset of configuration files. A common post-processing

task is also to rename all logical system names in the target system (running BDLS) that

may run for hours or even for days in very large systems. After all tasks are successfully

completed, the target QA system is ready for the user and the system copy procedure is

completed until the next refresh is due.

Post-Processing

Target System is pre-pared for the users.

System Copy Challenges

Most administrators or consultants experienced in executing the system copy process

may know that the procedure can be very lengthy and complex. The SAP application

landscape evolved from the fairly simple ABAP-based SAP R/3® software to a highly so-

phisticated service-oriented architecture with extended possibilities and a wide portfolio


WHITE PAPER

of applications ranging from standard ERP up to dozens of specialized applications.

With enhanced possibilities and scalability, the administrator will face many challenges

in managing the complexity.

The system copy process is one of the procedures where the complexity is most evident

because (a) most SAP systems require one or multiple system copies, (b) all aspects of

the SAP system are affected when a complete system is cloned, and (c) system copies

need to reflect a changing and evolving landscape.

Specifically, customers may experience the following challenges:

Manual Procedure: Many steps in the system copy procedure have to be done by

hand and consume the time of expensive SAP specialists.

Inconsistent Results: Any manual procedure may vary in the way certain steps are

completed or tables are updated. Some tables may not be updated at all. The end re-

sult is a QA system that does not properly reflect production.

Large Number of SAP systems: The increasing number of systems in the landscape

multiplies to many times a year what used to be a once- or twice-a-year challenge.

No Optimization: Some tasks, such as BDLS, have the potential to be optimized by

intelligent methods. As soon as a procedure is standardized and automated, optimiza-

tion and performance enhancements can be added easily.

Testing without Current Staging Systems: Because of the challenge, some cus-

tomers may even capitulate and not update their QA systems at all. This results in a

business risk as testing and staging are not done in actual production settings.

Automating and Optimizing System Copies with Libelle SystemCopy

When reviewing the tasks for the system copy, one can consider the overall procedure

as complex and the necessary steps to be completed as extensive. However, each and

every task is always very similar for each SAP system and for each specific customer

environment. If tasks are defined accordingly, executed properly, and managed in the

right order, the procedure is a prime candidate for automation by software.

Since the late 1990s, Libelle AG has been working with SAP customers through its

BusinessShadow division and providing standard software for data mirroring in high

availability and disaster recovery projects. Through its acquisition of the SAP consulting

firm “BasisTeam”, which has been providing basis support to SAP customers for almost

a decade, Libelle AG is in a unique position: Libelle covers the complete SAP basis side

and also has years of experience in enterprise software development and a corporate

structure to provide 24/7 service to large and midsize customers.

Libelle is providing its SystemCopy solution to SAP end users and partners to automate

and optimize the system copy procedure.

The Libelle SystemCopy Framework

Libelle SystemCopy is a framework-based software solution to create fully automated

homogeneous system copies for SAP applications. Key features of the solution are:

Quick update of QA, DEV, or TEST systems with fresh production data

Fully automated pre-processing, copy, and post-processing


WHITE PAPER

Fast turnaround and minimum manual intervention during the process

Standardized procedures with consistent results

No changes to existing SAP landscape necessary

The Libelle SystemCopy software solution can reduce the challenges and sometimes

tedious work involved when updating SAP system copies to just two tasks: (1) start an

automated process and (2) monitor the same. LSC is setup once specific to the data-

base, SAP instance, and SAP version. Then it will execute the system copy procedure

with consistent results as many times as desired with the flexibility to adapt to changing

environments.

For the copy process (phase 2 of the system copy procedure) of the databases (DB2,

SAP MaxDB, MS SQL, or Oracle) from source to target system, SystemCopy supports

existing copy infrastructure tools such as Snapshots or Backup/Restore. Alternatively,

Libelle provides an integrated copy tool based on the Libelle BusinessShadow solution

that has been used to mirror databases and flat files for over a decade.

SystemCopy Architecture

To setup Libelle SystemCopy, a “master” server agent is installed on the target system

(for example, QA). If Libelle BusinessShadow is used for copying all the database and

flat files from production or if other production data is required, an additional “slave” ser-

ver agent is installed on the production system. All agents run directly on the server so

they are able to execute any task type necessary – whether they have to run “inside”

the SAP application (ABAP programs, SAP transactions, etc.) or “outside” (database

exports, shell scripts, etc.). Installing the master agent on production system is optional;

SystemCopy can run solely on the target system.

Setting up system copy configurations and managing the procedure is done with a

modern GUI that lets the SAP consultant or customer manage the procedure:

Solution Architecture

LSC is based on master/ slave server agents. The system copy procedure is managed with a se-parate GUI.

Libelle SystemCopy can also run solely on the target system.


WHITE PAPER


WHITE PAPER

GUI

The Libelle SystemCopy GUI manages the set up and configuration of indi-vidual tasks.

After configuration, the system copy procedure will be managed and monitored with the GUI.

SystemCopy Tasks

Earlier in this white paper, we outlined some of the steps necessary to execute homog-

enous system copies. Libelle SystemCopy defines these steps as tasks that are de-

fined to encapsulate single steps and activities into functional units that belong together.

A task can be as simple as exporting a table and includes (1) the actual export, (2)

checking for successful execution, (3) storing the export file on disk, and (4) catching

the return signal which indicates that the next step can be taken. Specifically, LSC sup-

ports all the task types outlined earlier in this white paper:

1. Running ABAP programs

2. Running command scripts

3. Exporting or importing database tables

4. Waiting for administrator interaction (interactive task)

5. Executing SQL scripts

6. Executing SAP transactions

Tasks are assigned to any of the three system copy phases: Pre-processing, copy, and

post-processing. Once defined and configured, they are stored in a configuration file

and then executed automatically in the sequence defined in the system copy configura-

tion for the customer’s specific SAP application.


WHITE PAPER

Task Details

The GUI shows the pro-gress of each task.

Task Configuration and Repository

Libelle has been actively building an extensive repository of system copy tasks to ad-

dress the variety of SAP applications, O/S platforms, database platforms, and SAP ap-

plication versions. Even if one SAP software implementation is not matching another, all

that is necessary to set up the system copy procedure is to pull the respective tasks

from the repository and plug them into the Libelle SystemCopy framework.

The selection, sequence, and configuration of tasks are planned together with the

Libelle consultant or with the SAP partner. The majority of tasks are ready out of the

box; some may need to be adjusted to match the customer’s setting.

The system copy configuration is set up as a sequence of tasks assigned to the pre-

processing, copy, and post-processing phases. The configuration is stored in a single

XML configuration file that is accessed during the system copy procedure by the server

agents and is re-used for every subsequent system copy procedure.

Tasks Details

SystemCopy tasks are separated into functional units and can include executing simple SAP transaction or interaction with complex shell scripts.


WHITE PAPER

Executing the System Copy

All that is left for the system copy procedure is starting the execution and following the

process. All steps performed and return signals received are sent back to the GUI to

relay the procedure’s current status.

During the design phase of the GUI, the Libelle development teams place special em-

phasis on the administrator always being up to date on the exact status of the system

copy procedure. The LSC GUI shows all tasks in their respective categories, and pro-

gress bars indicate detailed status at any time during execution.

System Copy Execution

Doing a system copy with LSC begins with starting the process from the GUI, whereby actual tasks are executed on the server.

Managing Multiple Configurations

From the beginning, Libelle SystemCopy was designed to manage a large number of

systems and configurations. The hard-coded server agents can run on multiple systems

at the same time and are communicating on dedicated ports with their target or source

system and with the GUI. A single GUI can then manage a complete landscape with

multiple configurations and systems for customer environments. The following screen-

shot shows a GUI in the minimized view, in which the execution of multiple system

copies can be monitored at the same time.

Completing the Copy and Process Optimization

Aside from unexpected situations (e.g. the target system becomes unavailable) or inten-

tional breakpoints (e.g. the customer wants to check a table manually before continuing


WHITE PAPER

with the next step), the process will complete automatically and the QA system will be

ready for its staging procedure.

Once tasks and procedures are encapsulated and brought into sequence, LSC begins

actively optimizing the tasks to reduce the system copy duration. One prime example is

the parallel execution of BDLS transactions, which used to be a sequential process.

This can dramatically reduce the process from multiple days to a few hours.

GUI Views

The LSC GUI allows single-configuration view and minimized or list view for multiple configu-rations.

View is changed by clicking the View selec-tion at the bottom of the screen.

Summary

Libelle SystemCopy significantly reduces the time and resources necessary to create

homogeneous system copy for SAP applications. It is safe and easy to install in your

SAP environment and can be used immediately. Uniquely, Libelle SystemCopy can run

“outside” the ABAP stack and, as such, can execute both ABAP transactions and data-

base or server tasks necessary to support dual-stack SAP software implementations.

With the support of Snapshots and alternatively the provisioning of its very own copy

tool (Libelle BusinessShadow), Libelle SystemCopy can automate each and every

single task. From the very first step of connecting to the old QA system and up to

starting the newly refreshed system, it can all be done without any intervention.


WHITE PAPER

More Information

Headquarters United States

Libelle AG Libelle LLC Gewerbestr. 42 3330 Cumberland Blvd., Suite 500 70565 Stuttgart, Germany Atlanta, GA 30339 USA T +49 711 / 78335-0 T +1 770 / 435 1101

[email protected] [email protected] www.Libelle.com

Libelle does not guarantee that the information in this presentation is error free. The liability for consequential or indirect damages arising out of the reading or the use of this information is not warranted by Libelle AG within legal limits. All copyrights, especially distribution, reproduction, and translation, are reserved. No part of this presentation may be reproduced, processed, or reproduced or transmitted by electronic means without ex-plicit approval of Libelle. Under no circumstances, including, but not limited to, negligence, shall Libelle, its agents or assignees, including but not limited to its parent, subsidiary, or affiliate companies, be liable for any direct, indirect, incidental, special, or consequential damages that result from the use of the information provided herein. Libelle, the Libelle Logo and BusinessShadow are trademarks of Libelle AG in Germany and other countries. SnapMirror and Snapshot are trademarks or registered trademarks of NetApp, Inc. Windows, Microsoft, and SQL Server are regis-tered trademarks of Microsoft Corporation. Oracle is a registered trademark of Oracle Corporation. DB2 is a trademark or registered trademark of IBM Corp. MaxDB is a trademark of MySQL AB, Sweden. UNIX is a registered trademark of The Open Group. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affi liate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. V4

advanced automation and optimization of system copy ... · pdf filewhite paper advanced...

Documents