Scribd
Upload
158 views

Tools For System Copy and Migration

The document discusses tools for system copy and migration in ABAP systems. It describes tools like Migration Monitor, Package and Table Splitter, Time Analyzer and OraBRcopy that can be used to improve the system copy process. Each tool is briefly explained indicating its purpose and functionality.

Uploaded by

ilyas2sap
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
158 views

Tools For System Copy and Migration

The document discusses tools for system copy and migration in ABAP systems. It describes tools like Migration Monitor, Package and Table Splitter, Time Analyzer and OraBRcopy that can be used to improve the system copy process. Each tool is briefly explained indicating its purpose and functionality.

Uploaded by

ilyas2sap
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

Tools for System Copy and Migration

by Rajnikanth »

These are the new Java based tools that are developed to improve the system copy process for
ABAP systems. These tools can be used together with the old system copy procedures based on
R3SETUP as well as for copying older SAPinst based products.

Migration Monitor (MIGMON)


Package and Table Splitter (SPLIT)
Time Analyzer (MIGTIME)
OraBRcopy (ORABRCOPY)

Migration Monitor (MIGMON)


The Migration Monitor is a tool which helps you to perform and control the unload and load
process during the system copy procedure.From NetWeaver 04 SR1 on the Migration Monitor is
integrated into the SAPinst system copy tool, but it is also possible to use the monitor for
copying older releases by starting it manually.
The Migration Monitor will:

* create R3load command files

* create R3load task files if required

* start the R3load processes to unload the data

* transfer packages from the source to the target host if required

* start the R3load processes to load the data as soon as a package is available

* inform the person performing the system copy in case of errors

Package and Table Splitter (SPLIT)


Splitting packages is only available for release 4.0B and above.
Splitting tables is only available on project basis for release 6.20 and above.
The Splitter tool can be used for splitting the following:

* STR/EXT files

* 6.40: TSK files with WHERE clauses (including an adaptation of the corresponding STR/EXT
files)

* 7.00: WHR files with WHERE clauses (including an adaptation of the corresponding
STR/EXT files)
CAUTION: Please pay attention to note 833946.

Time Analyzer (MIGTIME)


Tool to analyze the runtimes of the Export/Import

* Calculates the runttime per package

* Lists the long running objects within a package for further splitting

* Creates a list with Start- and Enddate/Time per Package

OraBRcopy (ORABRCOPY)
Tool to prepare the system copy using Oracle Backup/Restore. This tool replaces the former
UNIX R3COPY shell script. The tool works on UNIX and Windows and generates the control
files and the new init<DBSID>.ora for the target system.

Conclusion: All listed tools are downwards compatible and SAP recommends always to use the
latest tool version available - unless not stated otherwise.

Migration Manual : Locate the document in its SAP Library structure


This manual describes the procedures for migrating applications that are running on J2EE Engine 6.20 to
the J2EE Engine as part of the SAP NetWeaver 2004s (the latter is referred to in the following texts as
J2EE Engine 2004s).

Migration issues may occur due to:

· The different implementations of the J2EE standards in J2EE Engine 6.20 and J2EE Engine 2004s

The J2EE Engine 2004s is a J2EE 1.3-compliant platform for running J2EE applications, whereas J2EE
Engine 6.20 is J2EE 1.2-compliant.

· The new cluster architecture, cluster communication, service infrastructure, and the new features of
J2EE Engine 2004s

· The new development and software logistics

· The unavailability of an upgrade procedure from J2EE Engine 6.20 to J2EE Engine 2004s

As a result of the new architecture in 2004s, it is not possible to upgrade from 6.20 to 2004s. You must
install SAP NetWeaver 2004s and redeploy on the J2EE Engine all applications that were running on J2EE
Engine 6.20.

The manual covers the following topics:

· Architectural Differences Between J2EE Engine 6.20 and 2004s

This section describes some of the main architectural differences between J2EE Engine 6.20 and 2004s
and their effect on the migration of applications.

· Porting Applications

¡ Porting a J2EE Application from J2EE Engine 6.20 to J2EE Engine 2004s

§ Web Components

§ EJB Components

¡ Using Additional/External Resources

§ Libraries

§ Changed External Libraries Delivered with the J2EE Engine

· Changes Between 6.20 and 2004s

Contains the main changes between J2EE Engine 6.20 and J2EE Engine 2004s in terms of architecture
implementation, different service and application settings, or other changes regarding the J2EE Engine or
application configuration and administration.

¡ General Issues

¡ System Management and Monitoring

¡ Logging Configuration and Usage

¡ JNDI Registry Service

¡ EJB Container

¡ Web Container

¡ Transactions and Resource Handling

¡ Deployment

¡ Security-Related Services
¡ Remote Objects Communication Services

¡ Web Services

¡ JMS Provider Service

¡ Utilities

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy