Engineering charge injection interfaces in hybrid light-emitting electrochemical cells

Emission spectra and lifetime measurements of Langmuir–Schaefer films

Chapter 4 Thin films in LECs

4.1 Engineering charge injection interfaces in hybrid light-emitting electrochemical cells

Lesson: R3SETUP/SAPINST

Lesson Overview

Contents

The role of R3SETUP and SAPINST in the homogeneous or heterogeneous system copy process

Lesson Objectives

After completing this lesson, you will be able to:

• Understand how R3SETUP and SAPINST control the export and import processes of homogeneous or heterogeneous system copies and how to influence their behavior.

• Recognize the structure of the R3SETUP *.R3S control files, and be able to adjust their contents if necessary.

Business Example

The export or import phase of a R3LOAD based system copy should be improved.

For that purpose the installation tool R3SETUP/SAPINST must be stopped in certain phases. You need to know how to prepare the tools for that.

Figure 61: R3SETUP: *.R3S Files

The command file DBEXPORT.R3S controls the database export of a homogeneous or heterogeneous system copy.

CENTRAL.R3S calls other *.R3S files as selected.

DBRELOAD.R3S is only used for re-loading an already finished installation (that is, after the test migration). Available for Oracle only.

ADM545 Lesson: R3SETUP/SAPINST

Older *.R3S files are: CENTRDB.R3S for a combined installation of central instance and database, and CEDBMIG, used for a combined installation of central instance and database for homogeneous or heterogeneous system copies.

Figure 62: R3SETUP: *.R3S File Structure

The command file consists of several sections. The beginning of a section is always indicated by the section name in square brackets. Each section contains a set of keys and corresponding parameter values.

The [EXE] section represents an installation roadmap with all of the steps listed in sequence. The steps are executed as listed (the step with the lowest number first).

Some parameters are not written to the R3SETUP command file until runtime.

Parameters which are preset by editing the *.R3S file will not be overwritten from default values.

After a section has been successfully executed, it receives the status OK.

R3SETUP stops on error if a section can not be executed. The section receives the status ERROR.

R3SETUP always reads the [EXE] section first to get the execution order, and then examines the status of each section. The first section with an ERROR status or without any status will be executed next. Removing the OK status from a section will force R3SETUP to execute this section again.

83

Unit 5: R3SETUP/SAPINST ADM545

Figure 63: R3SETUP: User-Defined Break-Points

Between the execution of two command sections in a *.R3S file, you may need to stop and make manual changes to the R3LOAD control files, modify database settings, or even call MIGMON. As shown in the graphic, R3SETUP can be forced to stop, by implementing user-defined break-points.

The R/3 installation kits for Windows operating systems provide R3SEDIT.EXE for modifying *.R3S files in an easy way.

SAP Note: “118059 Storage parameter for system copy with R3load” describes how to implement user break-points.

SAP Note: “784118 System Copy Java Tools” explains how to find the MIGMON software on the SAP Marketplace. The MIGMON*.SAR archive contains a PDF-document which shows how to use MIGMON with R3SETUP.

ADM545 Lesson: R3SETUP/SAPINST

Figure 64: R3SETUP: LABEL.ASC

The content of the LABEL.ASC file in the export directory will be compared against the expected string inside DBMIG.R3S to make sure that the import is read from the right location. The same mechanism is used by SAPINST.

Figure 65: SAPINST: *.XML Files

SAPINST records the installation progress in the “keydb.xml” file. SAPINST can continue the installation from a failed step, without having to repeat previous steps.

The package.xml file contains the name of installation media (CDs) and the expected LABEL.ASC content.

85

Unit 5: R3SETUP/SAPINST ADM545

Figure 66: SAPINST: User-Defined Break-Points

The current version of SAPINST can be checked by executing “SAPINST –v”.

As long as the used SAPINST version does not provide a documented way to implement user break-points, the program must be forced to stop by intended error situations.

SAPINST starting with 7.0 SR2 offers the possibility to manipulate step execution via a graphic user interface, the so-called “Step Browser”. The Step Browser shows the components and steps that make up an installation. You may manipulate the state of single steps, groups of steps, and even whole components and their sub-components. By invoking the context menu for a step and choosing “Insert Dialog Exit Step above Selection” or “Insert Dialog Exit Step below Selection”

you may stop an installation before or after a certain step.

To activate the Step Browser, call SAPINST with the command line parameter

“SAPINST_SET_STEPSTATE=true”.

Please be aware, the “Step Browser” functionality is not supported officially, so the usage is done on own risk!

Figure 67: Size of the Target Database

ADM545 Lesson: R3SETUP/SAPINST

The values calculated for ABAP database storage units are estimates, like the values for the initial extents, and primarily serve as guidelines for sizing the target database. You will probably have to increase or decrease individual values during, or after the first test migration.

ABAP Tables and indexes that are larger than 1.78 GB will be normalized to an initial extent of 1.78 GB. The target database size calculation is based on estimations. Adjust the database size manually if required.

The JAVA DBSIZE calculation does not have table or index size limitations, but the result is based on estimations as well.

87

Unit 5: R3SETUP/SAPINST ADM545

ADM545 Lesson: R3SETUP/SAPINST

Exercise 5: R3SETUP/SAPINST

Exercise Objectives

After completing this exercise, you will be able to:

• Know how R3SETUP and SAPINST can be influenced and adapted to special needs.

Business Example

You want to force a specific behavior of R3SETUP/SAPINST.

Task 1:

The installation program R3SETUP will be started with a command line

containing the name of a “*.R3S” file to read (i.e. “RESETUP –f DBMIG.R3S”).

The purpose of “*.R3S” files is not only to define installation steps; it is also used to store parameters and status information. R3SETUP sets the status of completed steps to OK and stops on error if a step can not be executed successfully. An erroneous step will get the status “ERROR”. Every time R3SETUP is started, the

“*.R3S” file will be copied first, to have a backup of the original content. Next, R3SETUP will begin the execution at the first step that has the status “ERROR”, or no status at all.

For repeated test migrations or for the final migration of a production system, it would be helpful to have a DBMIG.R3S file that rebuilds the database without reinstalling the database software again. For this purpose, we need a

“DBMIG.R3S” file which starts with the generation of an empty database.

1. What can be done to create such a “*.R3S” file? Different methods are possible.

2. What happens to R3SETUP parameters that were preset by hand?

Task 2:

SAPINST stores all its installation information in “*.XML” files. As the file structure is neither easy to read nor documented, modifying the files can be risky, as it might cause unexpected side effects.

1. What can be done to force SAPINST to stop before a certain installation step?

2. In the case where we need to repeat a system copy import, it would be useful to have a SAPINST that starts at a certain step. How could this be achieved without modifying the files?

89

Unit 5: R3SETUP/SAPINST ADM545

Solution 5: R3SETUP/SAPINST

Task 1:

The installation program R3SETUP will be started with a command line

containing the name of a “*.R3S” file to read (i.e. “RESETUP –f DBMIG.R3S”).

“*.R3S” file will be copied first, to have a backup of the original content. Next, R3SETUP will begin the execution at the first step that has the status “ERROR”, or no status at all.

“DBMIG.R3S” file which starts with the generation of an empty database.

1. What can be done to create such a “*.R3S” file? Different methods are possible.

a) Insert a break point in the “*.R3S” file at the place where R3SETUP should stop. Copy the “*.R3S” file using a new name.

b) Remove the “STATUS=OK” lines from completed “*.R3S” files. Begin editing the section where R3SETUP should start later on.

Caution: The step order is defined in the [EXE] section. If you reuse an already executed “*.R3S” file, be sure to remove the STATUS=OK lines from all sections following an [EXE] order.

Do not skip steps. Use this method only if you want to repeat the installation exactly like it was done before!

2. What happens to R3SETUP parameters that were preset by hand?

a) R3SETUP does not overwrite preset parameters with default values.

A description of each installation step and related parameters can be found in the installation directory (sub-directory “doc”), or on the installation CD.

Continued on next page

ADM545 Lesson: R3SETUP/SAPINST

Task 2:

1. What can be done to force SAPINST to stop before a certain installation step?

a) Since SAPINST NetWeaver 7.0 SR2 the step browser can be used to insert an exit dialog before or after an installation step. Earlier SAPINST versions can only be stopped by forcing intended errors.

2. In the case where we need to repeat a system copy import, it would be useful to have a SAPINST that starts at a certain step. How could this be achieved without modifying the files?

a) Stop SAPINST before the step where you would like to start later on. Copy the entire installation directory as it is. Restore the saved installation directory to its original location to redo the installation.

91

Unit 5: R3SETUP/SAPINST ADM545

Lesson Summary

You should now be able to:

• Understand how R3SETUP and SAPINST control the export and import processes of homogeneous or heterogeneous system copies and how to influence their behavior.

• Recognize the structure of the R3SETUP *.R3S control files, and be able to adjust their contents if necessary.

ADM545 Unit Summary

Unit Summary

You should now be able to:

• Understand how R3SETUP and SAPINST control the export and import processes of homogeneous or heterogeneous system copies and how to influence their behavior.

• Recognize the structure of the R3SETUP *.R3S control files, and be able to adjust their contents if necessary.

93

Unit Summary ADM545

Unit 6

Technical Background Knowledge

Unit Overview

This unit explains where all the information is coming from that is stored in the various R3LOAD and JLOAD control files. This is the key to understand why things are as they are. It also gives a better understanding of the ABAP dictionary.

• ABAP table types and storage parameters.

• ABAP data types and data access through the DBSL interface.

• JAVA data types and data access through the JDBC interface.

Unit Objectives

After completing this unit, you will be able to:

• Explain how Data Classes are used to map tables to database storage units

• Understand how Data Classes are handled by R3LDCTL and R3LOAD

• Create customer Data Classes

• Explain the purpose of table DBDIFF

• Understand how the R3LOAD/JLOAD data access is working

• Distinguish between the R3SZCHK behavior if the target database type is the same or different than the source database type

Unit Contents

Lesson: Data Classes (TABARTs) ... 96 Lesson: Miscellaneous Background Information ...105 Exercise 6: Technical Background Knowledge ... 111

95

In document TITULO: Formación de nuevas estructuras moleculares en películas ultrafinas. Preparación de dispositivos electroluminiscentes y fotovoltaicos. Molecular Arrangement in ultrathin films. Thin films in optoelectronic devices AUTOR: Cristina Roldán Carmona (página 193-200)