java system copy sap

System Copy for SAP Systems based on AS JavaOliver NoconSAP NetWeaver RIG EMEANW Foundation & KMC, SAP AG

KHNC, Sep. 20, 2006

System Copy - Overview

Technical Background

Procedure Details

Usage Scenarios

© SAP AG 2006, Java System Copy / O. Nocon / 3

Terminology

There are three different "kinds" of System Copy:

1. Homogeneous system copyOperating system platform and database platform remain unchanged.

2. Heterogeneous system copy (migration)During the system copy the following is being changed:– operating system (OS migration)– database (DB migration) or– operating system and database (OS/DB migration)

3. Unicode Conversion (only for ABAP)During the system copy the system is changed from non-unicode to unicode. This can happen with a homogeneous or a heterogeneous system copy.


Reasons For System Copy

Several Reasons for performing a System CopyCopy/migrate production systems to create duplicates for tests, …Change the HW or DB vendorMigrate to UnicodeSwitch from 32bit to 64bit platformPlatform switch during Portal migration…


DB Dependent vs. DB Independent Method

System copy can be doneDatabase-specificDatabase independent

Database-specificAvailable for many platformsSuitable for homogenous system copy

Database independentUsing jload mechanismIndependent of platformSuitable for heterogeneous and homogeneous system copy


Restrictions

Only the copy of the whole system is supported! It is not possible to copy dedicated components.

It is not supported to change the stack-type, e.g. to export a Java-Only system and import it into an ABAP+Java environment.

When copying an ABAP+Java stack both stacks must be copied!

Copying the system by ‘refreshing‘ the database is not supported!

Copying the database only is not supported!

Copying the central instance only is not supported!

Certain restrictions based on SPS stack of components (please refer to SAP notes for details)


Compatibility

So far there is no compatibility across releases for copying the Java stack!

SAP NetWeaver 04can only be copied using the NW 04 installation tools

SAP NetWeaver 2004scan only be copied using the NW 2004s installation tools.


Related Documentation

NW 04 SR1service.sap.com/instguidesnw04 Installation SAP Web AS SAP Web AS 6.40 SR1 and Related Documentation Homogenous and Heterogeneous System Copy Homogenous and Heterogeneous System Copy for SAP Systems Based on SAP Web Application Server Java 6.40 SR1and SAP Note 785848

NW 2004sservice.sap.com/installNW2004s Installation 2 - Installation SAP NetWeaver 2004s System Copy for SAP Systems Based on NW2004sand SAP Note 870863

SAP Service Marketplacehttp://service.sap.com/systemcopy

Additional Notes884452, 937362, 966752, 757692



Procedure Details

Usage Scenarios


Java System Copy: Server Infrastructure

CentralInstance

Dialog Instance

J2EE

Server

Dispatcher

File SystemFile System

JavaDatabase

J2EE

Server Migration Controller

ICM

Dispatcher

SDM

Jload

ICM

Components persistdata in

• Java database

• File system

Tools for system copy


Java System Copy: Java Server in Database

GUI ConfigTool snapshot of a J2EE Engine

System specific data

Instances are stored in thedatabase. Instance ID ~ ‘box number‘ (<SID><Instancename><host>)

instance.property.IDXXXXX (~ Java server instance profile) is stored in thedatabase and synchronized to the file system as instance.properties


Java System Copy: Basic Approach (1)

Basic idea:Export Java database schemaArchive SDM (in an operating system independent way)Install target system using database and SDM export

Challenges with NW 04/2004s:System specific data stored within the database (SID, paths, host names, …)Java server instances are stored within the databaseApplications store data neither using SDM nor the Java database

Solution for NW 04/2004s:Migrate system specific data and re-organize the instances in the database (Java Migration Toolkit/Migration Controller)Archive application specific parts persistent in the file system only



Source System Export

• <ID of CI>• <ID of DI #1>• <ID of DI #2>• …

CentralInstance

SDM

SCSInstance

SDMKIT.JAR

Jload

DB dump



Source System Target System


SCSInstance’

CentralInstance’

SDM

SDMKIT.JAR

DB dump

Import


CentralInstance

SDM

SCSInstance

Jload



Source System


CentralInstance

SDM

SCSInstance

Target System


SCSInstance’

CentralInstance’

SDM

• <ID of CI’>• <ID of DI #1>• <ID of DI #2>• …

Migration Controller:

• Changes the ID of the CI

• Deletes all other instances


Jload Architecture Overview

Open SQL

JAVAIO

Jload

Java DDIC

DB(Java

Schema)

JDBC

Data Files

DML DDL

Data file handling:•I/O via streams and proprietary Fileformat•Splitting•Compression•Restartable


Jload Background and Operating Mode

JloadWritten in JavaUsage of SAP‘s OpenSQL for data accessUsage of SAP‘s DDIC API for creation of objectsone tool for export/import of data and meta datacontrolled via xml files containing job descriptions

Operating Modecomplete export of the whole DB schema (apart from DDIC tables, i.e. BC_DDDB*)data files contain data and meta datadata files can be splitted automatically



Procedure Details

Usage Scenarios


System Copy Procedure – Main Phases

Preliminary TasksPlanning and preparationInformation gathering, …

Preparation of target environmentMainly required if a refresh of the target system should be performed

Preparation of source systemsPreparations on source system in accordance with the plans

Perform system copy

Final activities on source landscapePut source system back into production mode

Final activities on target landscapePost installation stepsAdoptions…


Java System Copy NW 04: SAPinst Installation Services

ABAP and Java system copy are separate installation services

Java system copy services not available in standard catalogSAP Inst needs to be started with separate product catalog

SAPinst control files update available on SAP Service Market Place

Migration key is required when copying a Java only systemonly for heterogeneous system copy

Subject to change, please observe SAP Notes!


Java System Copy NW 04: Export

The Java export is created by SAPinst (NetWeaver Installation Master DVD)

Export Java database schema using JloadArchive SDM, that is tell SDM to create an SDMKIT.JARCreate application specific SAR archives

If the database is copied using database tools the Java schema isnot exported by Jload/SAPinst!

Note:Jload and the Java Migration Toolkit are shipped together witheach NW 04 Support Package Stack (≥ SPS 9) in theSLTOOLS.SDAThe same Jload is used for export and import and it is of thesame SPS as the system


Java System Copy NW 04: Import (Central System)

The target system (NW 04 SR1) is installed by SAPinst (Installation Master) using the Java export + the Java DVD and RDBMS DVDs:

Install SAP System prerequisites (OS user, file system, shares, profiles, etc…)Install SAP Central Services (SCS instance)Install databaseInstall SDM (SDMKIT.JAR from Java export)Redeploy file system SDAs (from unpacked SDMKIT.JAR)Create Secure Store in the file systemLoad Java DB using Jload / Restore database using database toolsMigrate system specific settings (Java Migration Toolkit/Migration Controller)Extract bootstrap folder and instance.properties (batchconfig tool)Extract application specific archivesManual post installation steps …

Note: The Engine is NOT started!


Java System Copy NW 04: Import (Distributed System)

Note which actions are performed on which host when installing adistributed system (database and central instance on different hosts) e.g. on Oracle:

Database hostDatabase softwareDatabase schemaRestore backup (if copy is done by database tools)

Central instance hostCreate SecureStore in the file systemLoad database with JloadRun Migration Controller


Java System Copy With SAP NetWeaver 2004s

The system copy has been released (Feb 2006) for the Java stack ofSAP NetWeaver 2004sSAP CRM 2005SAP ERP 2005SAP SRM 2005

System Copy using database tools supported for all databases

The general restrictions are the same as forNW 04!

Restrictions specific for NW 2004s:See SAP Note 870863.


Java System Copy NetWeaver 2004s vs. NetWeaver 04

Installation servicesAll services available with standard catalog One installation service for exporting a double stack (ABAP + Java)Database export is performed on the database host (Oracle)Database import + SecureStore creation is performed on the database hostNo Migration key is required when copying a Java Only system

ToolsSLTOOLS.SDA is now deployed in $SAPGlobalDir/sltoolsUsageTypes library is used to get information about the installed components → only running database is required for export!


Manual Steps to be Performed (Extract)

Configuration of KMC Post-Installation Step:1. Log on to the portal as user with the content administrator role2. Navigate to→ Content Administration→ Collaboration Content→ Collaboration Launch Pad Configuration

3. Navigate under Related Links to Configure Real-Time Collaboration → Application Sharing4. Enter your server and port number in the section ServerName and ServerPort5. Save your entries6. Restart your application / J2EE server

Portal Post-Installation Step:Clear Portal Runtime cache according to SAP note 798876

Please refer to system copy documentationfor a complete list of post steps!



Procedure Details

Usage Scenarios


System Copy During Portal Migration

Limited platform support for Portal MigrationEP 5.0 SAP NetWeaver 04EP 6.0 SP2 SAP NetWeaver 04

System copy procedure needs to be planned as part of the migration project:

First: migrate to intermediate (supported) platformSecond: Perform Java heterogeneous system copy to final platform

Details about portal migration:http://service.sap.com/nw-epmig


System Landscape Copy for e.g. Test Purposes (1)

Scenario:Production system should be copied for test purposes

Questions:Which components belong to the solution?Which components are required in the target landscape?How can the impact on the production system be minimized?How can production system be protected from any potential damage?…


System Landscape Copy for e.g. Test Purposes (2)

Precautionary measure:Isolate target system from production landscape

Potential steps to be performed:Disconnect from productive LDAP directoryDisconnect productive KM repositories (non DB repositories)Remove confidential data from KM DB repositories– E.g. by running a custom specific report based on defined document

attributes– Attributes must be existing which identify confidential data!

New/different user-role assignments…


Questions?

??? ?

?

??

?

? ?


Copyright 2006 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.


Copyright 2006 SAP AG. Alle Rechte vorbehalten

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten.Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® und SQL Server® sind eingetragene Marken der Microsoft Corporation.IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix und Informix® Dynamic ServerTM sind Marken der IBM Corporation.ORACLE® ist eine eingetragene Marke der ORACLE Corporation.UNIX®, X/Open®, OSF/1® und Motif® sind eingetragene Marken der Open Group.Citrix®, das Citrix-Logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® und andere hier erwähnte Namen von Citrix-Produktensind Marken von Citrix Systems, Inc.HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.JAVA® ist eine eingetragene Marke der Sun Microsystems, Inc.JAVASCRIPT® ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie.MaxDB ist eine Marke von MySQL AB, Schweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, und weitere im Text erwähnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet.Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherige Ankündigung geändert werden.SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte, Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.SAP haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialien entstehen können. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.

java system copy sap

Documents