BEST PRACTICE GUIDE – CLASSICAL MIGRATION OF SAP NETWEAVER AS ABAP TO SAP HANA
5
This accelerated delivery option is especially important for customers performing a classical migrating of
ABAP systems to SAP HANA – for more information about latest corrections in software provisioning
manager for the migration to SAP HANA, see the corresponding blog Migration to SAP HANA: Latest News
about Software Provisioning Manager 1.0 in SAP Community Network.
2.3.2 Migration Monitor (Migmon)
Migration Monitor is part of software provisioning manager. It uses the EXT, WHR, STR, TPL files to control the
unload and load, to accelerate the load by automatic parallelization, and to generate the R3load task and
command files (TSK and CMD files). Migration Monitor does the following:
Creates R3load command files
Creates R3load task files if required
Starts R3load processes to unload the data
Transfers packages from source to target host if required
Starts R3load processes to load data as soon as a package is available
Informs the person performing the system copy in case of errors
As of SAP NetWeaver 2004 SR1, the Migration Monitor is integrated in SAPinst/software provisioning
manager, but it is also possible to start Migration Monitor manually (there is a corresponding option in the
software provisioning manager) – for this, you require a properties file. When you start the Migration Monitor
manually:
You can adjust any parameters according to the Migmon user guide
You get flexible (for example, you can repeat, test and abort runs of the Migration Monitor)
The process gets more complex, as it requires many additional manual activities
The properties file has to be created manually (hint: re-use an existing properties file from previous
runs of software provisioning manager as template)
Especially for SAP HANA, the Migration Monitor comprises a migmonctrl.jar add-on that gets invoked
automatically to adjust the amount of R3load jobs dynamically during the import – this is described in the
Import section below.
For more information, see:
The Migration Monitor User's Guide explains parameters, functions, and control files in more detail.
The guide can be extracted from the archive MIGMON.SAR in the software provisioning manager
package.
SAP Note 784118 (System Copy Tools for ABAP Systems)
Section Restarting R3load Processes in the System Copy Guide.
2.3.3 R3load
R3load performs all load tasks in a database- and platform-independent format. It generates the database
export of all SAP objects that are defined in the ABAP Dictionary and archives the configuration and
components in the file system. Then, it performs the load of ABAP tables into the target database. It is
available via the kernel of the ABAP application server.
2.3.4 R3ldctl
R3ldctl makes information of source system database tables available for migration tools offline by reading
ABAP Dictionary structures from the source database. It creates structure (STR) files that describe the
definition of tables, indexes and views, and it creates database-specific template (TPL) files containing
commands in Data Definition Language (DDL), which define data structures. For more information, see the
System Copy Guide Exporting the Source System Using the Installer. R3ldctl is also available via the
kernel of the ABAP application server.
2.3.5 R3ta
To copy large tables, use the R3ta table splitter tool – it automatically generates WHERE conditions with which
a subset of table data can be accessed and with which the export and import of one table can be performed
in parallel by starting several R3load processes that work on packages. These WHERE conditions are