System Copy Guide SAP Systems Based on the Application Server ABAP of SAP NetWeaver Using Software Provisioning Manager 1.0 Valid for SAP Systems Based on: ■ SAP NetWeaver 7.3 ■ SAP NetWeaver 7.3 including EHP 1 Target Audience ■ System administrators ■ Technology consultants CUSTOMER Document version: 1.1 – 2012-09-25
146
Embed
System Copy Guide Using Software Provisionning Manager 1.0
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
System Copy GuideSAP Systems Based on the Application Server ABAP of SAP NetWeaverUsing Software Provisioning Manager 1.0
Valid for SAP Systems Based on:■ SAP NetWeaver 7.3■ SAP NetWeaver 7.3 including EHP 1
Target Audience ■ System administrators ■ Technology consultants
CUSTOMERDocument version: 1.1 – 2012-09-25
Document History
CAUTION
Before you start the implementation, make sure you have the latest version of this document.
You can find the latest version on SAP Service Marketplace http://service.sap.com/
instguides.
The following table provides an overview on the most important document changes:
The software provisioning manager 1.0 archive containing the installer as such.You always have to download the latest version of the software provisioning manager 1.0 archive.
■ UC or NUC Kernel (folder K_<N or U>_<Version>_<OS>) where U means Unicode and N means non-Unicode.
NOTE
Every new installation of an SAP system is Unicode. You can only use the non- Unicode kernel if you perform the system copy for a non-Unicode SAP system that has been upgraded to the current release.
Make sure that you have the appropriate installation kit version for your SAP kernel and that the
versions of the SAP systems and the installation media are the same on the target and source
systems. Exceptions are only allowed if they are described in an SAP Note.
CAUTION
The source system must be in a consistent state before you can copy it.
2. Make the required media available.
1. Download the latest version of the software provisioning manager 1.0 archive
The installer GUI starts automatically by displaying the Welcome screen.
4. On the Welcome screen, choose <Your Product> <Your Database> System Copy Source System
Based on <Technical Stack> .
5. Select the corresponding system copy option from the tree structure according to the sequence
of the process flow for the database-independent system copy procedure [page 21].
CAUTION
Make sure you choose the system copy options exactly in the order they appear for each
system variant.
The following table provides an overview about the installation options available for the export:
NOTE
Do not perform these steps if you use a database-specific method.
Export Options
Export Option Remarks
Export Preparation Optional step that is required only if you want to perform export processes in parallel to import processes.The installer performs the following steps:
4 Database Independent System Copy
4.5 Exporting the Source System Using the Installer
30/146 CUSTOMER 2012-09-25
Export Option Remarks
■ Creates the export directory structure ■ Not valid for SAP HANA database: Calculates the size of the target
database (DBSIZE.XML)
NOTE
In the case of a distributed system or a high-availability system, you need to perform this step on the database instance host.
Table Splitting Preparation Optional step.The installer performs the following steps: ■ Creates the export directory DATA ■ Creates database structure files (*.STR) for the tables to be split ■ Splits the generated STR files ■ Creates where-conditions for the tables to be split ■ Splits the generated WHR files ■ Copies the resulting WHR files to the export directory DATA
Database Instance Export Mandatory step.The installer performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.STR) ■ Updates database statistics (…) ■ Not valid for SAP HANA database: Calculates the size of the target
database (*.EXT, DBSIZE.XML) ■ Exports the database content
6. After you have selected the required option, choose Next.
7. If you generated SQL files with DDL statements (see Generating DDL Statements [page 24]) during the
database instance export, copy the generated files into the installer installation directory as soon
as it has been created by the installer. The installation directory will have been created as soon as
the first input screen appears.
8. Follow the instructions in the installer input dialogs and enter the required parameters.
CAUTION
You must choose parameter mode Typical when performing a system copy with database
tools.
NOTE
■ If parallel export and import has been prepared, ensure the following:
● You choose parameter mode Custom.
● You select the expert option Parallel Export and Import for the database instance export
on the SAP System > Database Export screen.
■ If table splitting for ABAP tables has been prepared before the data export via the installer,
the installer export automatically does the following:
● It forces package splitting.
● It forces the use of an input file for table splitting.
● It uses the existing whr.txt file from the dump directory as default for the package
splitter input file.
4 Database Independent System Copy
4.5 Exporting the Source System Using the Installer
2012-09-25 CUSTOMER 31/146
NOTE
For more information about input parameters in the installer, position the cursor on the
parameter field and choose F1 .
After you have entered all required input parameters, the installer starts the export and displays the
progress during the processing phase.
Running the Installer on UNIX
1. Log on to your host as user root.
CAUTION
■ Make sure that this user has not set any environment variables for a different SAP system
or database.
■ Do not use an existing <sapsid>adm user.
2. Make the installation media available on your host. For more information, see Preparing the Installation
Media [page 19].
CAUTION
If you want to use a different installation directory than the default, make sure that you create
it locally. Otherwise, you might experience problems when starting the SAP Java tools.
3. Start the installer from the directory to which you unpacked the SWPM10SP<support package
number>_<version number>.SAR file by executing the following command:
<path to unpack directory>/sapinst
NOTE
If you use a virtual host name for the primary application server, or the database instance, or
both (for example, in a high availability environment), start the export with the property
<path to unpack directory>/sapinst SAPINST_USE_HOSTNAME=<virtual host>.
CAUTION
Make sure that the installation directory is not mounted with NFS, or there might be problems
when the Java Virtual Machine is started.
If you want to use an alternative installation directory, set the environment variable TEMP, TMP, or
TMPDIR.
NOTE
Be aware of the following:
■ Make sure that your operating system does not delete the contents of the temporary
directory /tmp or the contents of the directories to which the variables TEMP, TMP, or
TMPDIR point, for example, by using a crontab entry.
■ Make sure that your current working directory is not an IM_<OS> directory belonging
to another operating system.
EXAMPLE
For example, the following causes an error:
4 Database Independent System Copy
4.5 Exporting the Source System Using the Installer
32/146 CUSTOMER 2012-09-25
$ cd /sapcd2/IM_HPUX_IA64
$ /sapcd2/IM_HPUX_PARISC/sapinst
To correct this, enter the following:
$ cd /sapcd2/IM_HPUX_PARISC
$ /sapcd2/IM_HPUX_PARISC/sapinst
The installer GUI starts automatically by displaying the Welcome screen.
4. On the Welcome screen, choose <Your Product> <Your Database> System Copy Source System
Based on <Technical Stack> .
5. Select the corresponding system copy option from the tree structure according to the sequence
of the process flow for the database-independent system copy procedure [page 21].
CAUTION
Make sure you choose the system copy options exactly in the order they appear for each
system variant.
The following table provides an overview about the installation options available for the export:
NOTE
Do not perform these steps if you use a database-specific method.
Export Options
Export Option Remarks
Export Preparation Optional step that is required only if you want to perform export processes in parallel to import processes.The installer performs the following steps: ■ Creates the export directory structure ■ Not valid for SAP HANA database: Calculates the size of the target
database (DBSIZE.XML)
NOTE
In the case of a distributed system or a high-availability system, you need to perform this step on the database instance host.
Table Splitting Preparation Optional step.The installer performs the following steps: ■ Creates the export directory DATA ■ Creates database structure files (*.STR) for the tables to be split ■ Splits the generated STR files ■ Creates where-conditions for the tables to be split ■ Splits the generated WHR files ■ Copies the resulting WHR files to the export directory DATA
Database Instance Export Mandatory step.The installer performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.STR) ■ Updates database statistics (…) ■ Not valid for SAP HANA database: Calculates the size of the target
database (*.EXT, DBSIZE.XML) ■ Exports the database content
4 Database Independent System Copy
4.5 Exporting the Source System Using the Installer
2012-09-25 CUSTOMER 33/146
6. After you have selected the required option, choose Next.
7. If you generated SQL files with DDL statements (see Generating DDL Statements [page 24]) during the
database instance export, copy the generated files into the installer installation directory as soon
as it has been created by the installer. The installation directory will have been created as soon as
the first input screen appears.
8. Follow the instructions in the installer input dialogs and enter the required parameters.
CAUTION
You must choose parameter mode Typical when performing a system copy with database
tools.
NOTE
■ If parallel export and import has been prepared, ensure the following:
● You choose parameter mode Custom.
● You select the expert option Parallel Export and Import for the database instance export
on the SAP System > Database Export screen.
■ If table splitting for ABAP tables has been prepared before the data export via the installer,
the installer export automatically does the following:
● It forces package splitting.
● It forces the use of an input file for table splitting.
● It uses the existing whr.txt file from the dump directory as default for the package
splitter input file.
NOTE
For more information about input parameters in the installer, position the cursor on the
parameter field and choose F1 .
After you have entered all required input parameters, the installer starts the export and displays the
progress during the processing phase.
Troubleshooting
See Useful Information About the Installer [page 118].
Only valid for: IBM i5/OS |
4.5.2 Running the Installer on IBM i to Perform the Export
4.5.2.1 Starting the Installer on IBM i
CAUTION
Make sure that you shut down all SAP application servers before the export. Otherwise, the target
system might be inconsistent.
This procedure tells you how to run the installer to export the database of your SAP system. The
installer includes an installer GUI and a GUI server, which both use Java.
4 Database Independent System Copy
4.5 Exporting the Source System Using the Installer
34/146 CUSTOMER 2012-09-25
This section describes an export where the installer and the installer GUI server runs on the host and
the GUI runs on a Windows 32-bit host.
NOTE
When you start the installer, the installer GUI server is also started. The installer GUI connects
using a secure SSL connection to the GUI server and the GUI server connects to the installer.
For more information about the installer, see Useful Information About the Installer [page 118].
Procedure
1. Log on to your host as a user with similar authorization rights as QSECOFR. For more information,
see Preparing an IBM i User Profile [page 38].
CAUTION
Do not user existing <SID>ADM user.
Make sure that the installation user has not set any environment variables for a different SAP
system or database.
2. Make the required media available on your host.
For more information about making the installation media available, see Copying the Installation Media
Manually Using the ROOTBIN Share [page 39].
3. Start the installer in one of the following ways:
■ Using the default installation directory (recommended)
Enter the following commands:
CD DIR(<path to unpack directory>)
CALL PGM(QP2TERM) PARM('./sapinst' '-nogui)
NOTE
● As a default, there is no GUI on IBM i, so you cannot see an installer Welcome screen.
You must start the installer GUI separately on a Windows 32-bit platform. For more
information, see Starting the Installer GUI Separately [page 128].
● For advanced users only:
PASE, which is similar to AIX, allows you to set the DISPLAY variable. If your X server
for Microsoft Windows or Linux is already configured and running, you can try to
direct the graphical output of SAPinst to an XWindow by setting the DISPLAY
variable. If this works, you do not have to use the remote SAPinst GUI separately.
We do not recommend that you start the SAPinst using the DISPLAY variable as there
is no support available.
● Only valid for: HA (UNIX) |
If you are installing a high-availability system and you have not already set the
environment parameter SAPINST_USE_HOSTNAME to specify the virtual host name,
you can start the installer as follows:
4 Database Independent System Copy
4.5 Exporting the Source System Using the Installer
If you want to use an alternative installation directory, set the environment variable TEMP,
TMP, or TMPDIR.
NOTE
To receive a list of all available installer properties, enter the following command:
CALL PGM(QP2TERM) PARM('./sapinst' '-p')
■ If you use virtual host names for the primary application server or the database instance or
both (for example, in a high availability environment), start the export with the property
SAPINST_USE_HOSTNAME=<virtual host>.
4. On the Welcome screen, choose <Your Product>. <Your Database> System Copy Source System
Based on <Technical Stack> .
5. Select the corresponding system copy option from the tree structure according to the sequence
of the process flow for the database-independent system copy procedure [page 21].
CAUTION
Make sure that you choose the system copy options exactly in the order they appear for each
system variant.
6. The following table provides an overview about the system copy options available for the export:
NOTE
Do not perform these steps if you use a database-specific method.
4 Database Independent System Copy
4.5 Exporting the Source System Using the Installer
36/146 CUSTOMER 2012-09-25
Export Options
Export Option Remarks
Export Preparation Optional step that is required only if you want to perform export processes in parallel to import processes.The installer performs the following steps: ■ Creates the export directory structure ■ Not valid for SAP HANA database: Calculates the size of the target
database (DBSIZE.XML)
NOTE
In the case of a distributed system or a high-availability system, you need to perform this step on the database instance host.
Table Splitting Preparation Optional step.The installer performs the following steps: ■ Creates the export directory DATA ■ Creates database structure files (*.STR) for the tables to be split ■ Splits the generated STR files ■ Creates where-conditions for the tables to be split ■ Splits the generated WHR files ■ Copies the resulting WHR files to the export directory DATA
Database Instance Export Mandatory step.The installer performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.STR) ■ Updates database statistics (…) ■ Not valid for SAP HANA database: Calculates the size of the target
database (*.EXT, DBSIZE.XML) ■ Exports the database content
7. After you have selected the required installation option, choose Next.
8. If you generated SQL files with DDL statements (see Generating DLL Statements [page 24]) during the
database instance export, copy the generated files into the installer installation directory as soon
as it has been created by the installer. The installation directory will have been created as soon as
the first input screen appears.
9. Follow the instructions in the installer input dialogs and enter the required parameters.
CAUTION
You must choose parameter mode Typical when performing a system copy with database
tools.
NOTE
■ If parallel export and import has been prepared, ensure the following:
● You choose parameter mode Custom.
● You select the expert option Parallel Export and Import for the database instance export
on the SAP System > Database Export screen.
■ If table splitting for ABAP tables has been prepared before the data export via the installer,
the installer export automatically does the following:
4 Database Independent System Copy
4.5 Exporting the Source System Using the Installer
2012-09-25 CUSTOMER 37/146
● It forces package splitting.
● It forces the use of an input file for table splitting.
● It uses the existing whr.txt file from the dump directory as default for the package
splitter input file.
NOTE
For more information about input parameters in the installer, position the cursor on the
parameter field and choose F1 .
After you have entered all required input parameters, the installer starts the installation and displays
the progress of the installation.
Troubleshooting
See Useful Information About the Installer [page 118].
Only valid for: IBM i5/OS |
4.5.2.2 Preparing an IBM i User Profile
For the installation you need to create a user account on the IBM i you want to install.
The following requirement applies:
■ The IBM i user profile must have user class *SECOFR and all special authorities that belong to user
QSECOFR.
Procedure
NOTE
The user name SAPIUSR and the password SAP are used in the procedures as examples.
IBM i:
Execute the following command:
CRTUSRPRF USRPRF(SAPIUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT('Test User for SAP
Partial example of a LOG when you start the target system for the first time:
SYNTAX
.
.
.
. DSNR005I -D8B0 RESTART...COUNTS AFTER FORWARD 604 RECOVERY IN COMMIT=0, INDOUBT=0 DSNR006I -D8B0 RESTART...COUNTS AFTER BACKWARD 605 RECOVERY INFLIGHT=0, IN ABORT=0, POSTPONED ABORT=0 DSNP012I -D8B0 DSNPCNP0 - ERROR IN VSAM CATALOG 606 LOCATE FUNCTION FOR D8A0.DSNDBC.DSNDB07.DSN4K01.I0001.A001 CTLGRC=AAAAAA08 CTLGRSN=AAAAAA08 CONNECTION-ID=D8E0, CORRELATION-ID=003.RCRSC 02, LUW-ID=* IKJ56228I DATA SET D8A0.DSNDBC.DSNDB07.DSN4K01.I0001.A001 NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED DSNB207I -D8B0 DYNAMIC ALLOCATION OF DATA SET 608 FAILED. REASON=17080002.DSNAME=D8A0.DSNDBC.DSNDB07.DSN4K01.I0001.A001 DSNT501I -D8B0 DSNITFFS RESOURCE UNAVAILABLE 609 CORRELATION-ID=D8E0 CONNECTION-ID=D8E0 LUW-ID=D8E0.D8E0.000000000000=0 REASON 00D70024....and so on
We strongly recommend that you maintain different RACF settings for different DB2 subsystems. If
not, the target system has access to the data sets of the source system and the data of the source system
could be changed by mistake.
The work file database data must be changed later in the clone process.
5.6.10 Step 9c: Creating a New STOGROUP Using the HLQ of the Target System
With this JCL job, you create a new STOGROUP using the HLQ of the target system (D8B0).
This JCL job is located at
HSCProcedure\Step9c\CRTMPSTO.JCL
.zip file [page 68] attached to SAP Note 680746. For more information, see the section JCL Jobs and SQL
6. FI customers: Run the jobs RFUMSV00 (tax on sales/purchases), RAGITT01 (asset history sheet),
RAZUGA01 (asset acquisitions), andRAABGA01 (fixed asset retirements) and compare the results to
those gained on the source system before the system copy.
7. CO customers: Run the report group 1SIP and compare the results to those gained on the source
system before the system copy.
Only valid for: z/OS |
7.2.2 Performing Jobhead Correction after Homogeneous System Copy
NOTE
This section is only relevant for customers using CCMS to monitor their SAP systems.
After copying your system, the CCMS jobhead still points to the former database SSID. To complete
the homogeneous system copy, the SSID needs to be set to the target system.
CAUTION
Only experienced users should use this utility.
Procedure
To set the SSID to the target system:
1. Call transaction DBACOCKPIT.
2. Choose Configuration Homogeneous System Copy: Jobhead Correction
3. Modify the necessary data.End of: z/OS |
7 Follow-Up Activities
7.2 Performing Follow-Up Activities in the Target System
2012-09-25 CUSTOMER 97/146
This page is left blank for documents that are printed on both sides.
8 Additional Information
8.1 R3load Procedures Using the Migration Monitor
Purpose
The Migration Monitor is a tool that helps you to perform and control the unload and load process
during the system copy procedure. As of SAP NetWeaver 04 SR1 the Migration Monitor is integrated
into the installer, but you can also use the Migration Monitor to copy previous releases by starting it
manually.
For more information about how to start the Migration Monitor manually, see Starting the Migration
Monitor [page 109].
The Migration Monitor does the following:
■ Creating R3load command files
■ Creating R3load task files if required
■ Starting the R3load processes to unload the data
■ Transferring packages from the source to the target host if required
■ Starting the R3load processes to load the data as soon as a package is available
■ Informing the person performing the system copy in case of errors
Tool
The tool is located in the MIGMON.SAR SAPCAR archive. The archive file contains the following:
■ User Guide
● MigrationMonitor.pdf
■ Scripts
● export_monitor.sh / export_monitor.bat
● import_monitor.sh / import_monitor.bat
● res_check.sh / res_check.bat
● import_dirs.sh / import_dirs.bat
■ jar archives
● migmon.jar
● rescheck.jar
● activation.jar
● mail.jar
■ Property files
● export_monitor_cmd.properties
8 Additional Information
8.1 R3load Procedures Using the Migration Monitor
2012-09-25 CUSTOMER 99/146
● import_monitor_cmd.properties
Prerequisites
The correct directory structure for R3load dump files must exist on both the source and target hosts.
8.1.1 Configuration
The following options can be provided via the property file or via command line. Command line
parameters take precedence over parameters specified in the property file. Options are case sensitive,
that is, options that are not recognized are ignored.
Help
With the following command line option, the tool displays all parameters available: -help
Version
With the following command line option, the tool displays version information: -version
General Options
General Options
Name Description Comments
monitorTimeout Monitor timeout in seconds During a timeout, the monitor thread sleeps and does not analyze any files or analyze its processing state. The default timeout value is 30 seconds.
E-Mail Options
Name Description Comments
mailServer SMTP server Server name or IP address of the company SMTP server
mailFrom “From” e-mail address non
mailTo “To” e-mail address Can contain an address list separated by “;” or blanks.
Additional Options
Name Description Comments
bg Enables background mode Takes effect only as command line option.If the tool is running in background mode, the UNIX shell windows or Windows command prompt can be closed after startup.
secure Enables secure mode Takes effect only as command line option.If the tool is running in secure mode, command line parameters (for example, passwords) are hidden for Java processes. Secure mode implicitly enables background mode.
8 Additional Information
8.1 R3load Procedures Using the Migration Monitor
100/146 CUSTOMER 2012-09-25
Name Description CommentsNOTE
You should use this mode if you have to specify passwords on the command line.
installDir Installation directory Directory where the installation tool (installer, R3SETUP) is started. If you run the Migration Monitor without using the installation tools, then the installation directory is the directory where the R3load TSK and log files will be written.
exportDirs List of export directories Separator on Windows: “;”Separator on UNIX, IBM i: “:”The exportDirs parameter points to the directory where the R3load dump files will be written. In the exportDirs directory, the subdirectories DATA, DB, and DB/<TARGET_DBTYPE> (for example, DB/ORA must exist.
client Client operating mode Running in client mode means that the Migration Monitor runs parallel to standard installer export process and transfers the exported dump files to the import server.
server Server operating mode Running in server mode means that the Migration Monitor creates R3load TSK files (if necessary), R3load cmd files, and starts the R3load processes.
All options below are for server mode. The import monitor always runs in the server mode. If you want to run the export monitor in the server mode, specify the server parameter in the export monitor's properties file.
orderBy Package order Can be the name or path of the file that contains package names. If the option value is omitted then package order is not determined.
ddlFile DDL control file Path or filename of DDL control fileThe default is DDL<DBTYPE>.TPL.If the filename is used without path, then the DDL control file from the export DB subdirectory is used.
ddlMap DDL mapping file File with mapping between DDL files and package names
r3loadExe Path of the R3load executable
Optional; default is R3load. If only the name of the R3load executable is available, then JVM looks for the R3load executable using OS-specific process search rules.
tskFiles yes to create task files; no to skip
Up to and including version 4.6, this must be set to no; as of version 4.7 set to yes. If the R3load task files
8 Additional Information
8.1 R3load Procedures Using the Migration Monitor
2012-09-25 CUSTOMER 101/146
Option Description Comments*.TSK already exist, then the monitor will not overwrite them.
dataCodepage Code page for data files See SAP Note 552464. Possible values: 4102, 4103, 1100
taskArgs Additional R3load arguments for the TASK phase
Appended to the R3load command line.Options already set by the monitor: -ctf; -l
loadArgs Additional R3load arguments for the LOAD phase
Appended to the R3load command line. Options already set by the monitor: -e; -datacodepage; -l; -p; -r; -socket (if the socket option is specified); -o (if the omit argument is specified and task files are not used, that is, the value of the ‘tskFiles’ option is ‘no’).
jobNum Number of parallel export jobs, default:1
Any positive number; 0 for an unlimited number of jobs. The value can be changed dynamically at runtime.
Network Exchange Options
Option Description Comments
net Network operating mode Exported dump files must be visible on the import host to use this mode.
netExchangeDir Network exchange directory CAUTION
Clean up the netExchangeDir before starting a new export!
Used for communication between the export and import monitors. Must be writable for the export monitor and readable for the import monitor. The export monitor writes a <package>.SGN file to the network exchange directory as a signal to the import monitor that the package has been exported successfully and that the import can be started.
FTP Exchange Options
Option Description Comments
ftp FTP operating mode Exported dump files will be transferred automatically from the source host (directory exportDirs) to the target host (directory importDirs) using FTP.
ftpHost Remote FTP host Name or IP address of the import server.
ftpUser Name of the remote FTP user The FTP user specified here should be <sapsid>adm to make sure that
Option Description Commentsthe package files can be read by during the import (which is started as <sapsid>adm).
ftpPassword Password of the remote FTP user CAUTION
Security risk!
For more information, see the secure parameter in section Additional Options.
ftpExportDirs List of remote FTP directories for export dump
Both “;” and “:” separators are valid. This is the directory on the target host to which the dump will be transferred. The value will be the same as for importDirs in the import monitor's property file.
ftpExchangeDir Remote FTP exchange directory Used for communication between the export and import monitors. Must be writable for the export monitor and readable for the import monitor. The export monitor writes a <package>.SGN file to the FTP exchange directory as a signal for the import monitor that the package is exported successfully and that the import can be started.
ftpJobNum Number of parallel FTP jobs; the default is 1.
Any positive number; 0 for an unlimited number of jobs. The value can be changed dynamically at runtime.
Export Socket Host
Option Description Comment
socket Socket operating mode R3load will not write dump files to the file system but the export and import work through the socket connection.
host Remote import host Name or IP address of the import host.
port Host port number Must be the same as the port number on the import host. Any free port on the import host from 1024 to 65535.
FTP Copy Options
Option Description Command
ftpCopy FTP copy operating mode
Used as a separate program call for migration with sockets if no share directory is used. All files produced by R3lctl and
8 Additional Information
8.1 R3load Procedures Using the Migration Monitor
2012-09-25 CUSTOMER 103/146
Option Description CommandR3szchk will be transferred from the source to the target host using FTP.
exportDirs List of export directories Separator on Windows: “;”Separator on UNIX, IBM i: “:”In the exportDirs directory, the subdirectories DATA, DB, and DB/<TARGET_DBTYPE> (for example, DB/ORA) must exist. The R3load STR files have to exist in the subdirectory DATA, the DDL*.TPL files in the subdirectory DB, and the R3load EXT files (if required) in the subdirectory DB/<TARGET_DBTYPE>.
ftpHost Remote FTP host Name or IP address of the import server
ftpUser Name of the remote FTP user
The FTP user specified here must be <sapsid>adm to make sure that the package files can be read during the import (which is started as <sapsid>adm).
ftpPassword Password of the remote FTP user
CAUTION
Security risk
ftpExportDirs List of remote FTP directories for export dump
Both “;” and “:” separators are valid. This is the directory on the target host to which the dump will be transferred. The value will be the same as for importDirs in the import monitor's property file.
Any other option is ignored by the export monitor.
Mandatory Options for Export Monitor
■ Client mode:
installDir, exportDirs,
one of the options ftp, net (and their related parameters)
■ Server mode:
installDir, exportDirs, tskFiles,
one of the options ftp, net, socket (and their related parameters)
The value of the dbType option is determined automatically in the shell script or batch files from
the dbms_type environment variable.
Import Monitor – Options
Import Options
Option Description Comment
installDir Installation directory The installation directory is the directory in which the installation tools (installer, R3SETUP) are started.When you run the Migration Monitor without using the installation tools, the installation directory is the
8 Additional Information
8.1 R3load Procedures Using the Migration Monitor
104/146 CUSTOMER 2012-09-25
Option Description Commentdirectory where the R3load TSK and log files are created.
importDirs List of import directories Separator on Windows: “;”Separator on UNIX, IBM i: “:”The importDirs parameter points to the directory where the R3load dump files are written. In the importDirs directory, the subdirectories DATA, DB, and DB/<TARGET_DBTYPE> (for example, DB/ORA) must exist.
orderBy Package order This option is used only if the import monitor works without the export monitor in standalone mode, that is, all export dump files are available on the import host before the import monitor is started.Values can be: ■ name: load packages in alphabetical order ■ size: load packages starting with the largest one ■ path of the file that contains package namesIf the option is omitted then package order is not defined.
ddlFile DDL control file Path or file name of DDL control fileThe default is DDL<DBTYPE>.TPL. If the file name is used without path, then the DDL control file from the export DB subdirectory is used.
ddlMap DDL mapping file File with mapping between DDL files and package names
r3loadExe Path of the R3load executable
Optional; default is R3load.If only the name of the R3load executable is available, then JVM looks for the R3load executable using OS-specific process search rules.
tskFiles yes to create task files; no to skip
Up to and including version 4.6, this must be set to no; as of version 4.7, it must be set to yes. If the R3load task files *.TSK already exist, the monitor will not overwrite them.
extFiles yes to include EXT files; no to skip them
Add EXT file entries to cmd files.If the EXT files cannot be found in the DB/<TARGET_DBTYPE> import dump subdirectory, the package processing is aborted.
dbCodepage Database code page for the target database
See SAP Note 552464. Possible values: 4102, 4103, 1100
migrationKey Migration key non
omit R3load omit value Can contain only DTPIV letters.-o D: omit data; do not load data-o T: omit tables; do not create tables-o P: omit primary keys; do not create primary keys-o I: omit indexes; do not create indexes-o V: omit views; do not create views.If you want to combine several omit options, list these options without blank (for example,-o TV).
taskArgs Additional R3load arguments for the TASK phase
Appended to the R3load command line.Options already set by the monitor:-ctf; -l; -o (if the omit argument is specified).
loadArgs Additional R3load arguments for the LOAD phase
Appended to the R3load command line.Options already used by the monitor:-i; -dbcodepage; -l; -p; -k; -r; -socket (if the socket option is specified); -o (if the omit argument is specified and task files are not used, that is, the value of tskFiles option is no).
jobNum Number of parallel import jobs; the default is 1.
Any positive number; 0 for an unlimited number of jobs.The value can be changed dynamically at runtime.
Import Exchange Options
Option Description Comment
exchangeDir Exchange directory If this option is not set, the monitor runs in standalone mode, that is, without the export monitor. All the export dump files or the SAP export CDs from the installation kit must be available on the import host and be specified with the importDirs parameter (for example, in the properties file).If there is an old export_statistics.properties file (for example, from a previous export run), remove this file.
Import Socket Options
Option Description Command
socket Socket operating mode non
port Server port number Any free port from 1024 to 65535.
Any other option is ignored by the import monitor.
Mandatory Options for Import Monitor
■ Server mode (default):
installDir, importDirs, tskFiles, extFiles,
one of the options exchangeDir or socket (and their related parameters)
■ Standalone mode:
installDir, importDirs, tskFiles, extFiles
■ Only valid for: IBM i5/OS |
IBM i-specific:
loadArgs= -nojournal
End of: IBM i5/OS |
NOTE
The value of the dbType option is determined automatically in the shell script or batch files from
the dbms_type environment variable.
8 Additional Information
8.1 R3load Procedures Using the Migration Monitor
106/146 CUSTOMER 2012-09-25
8.1.2 Assigning DDL Files to Packages
It is possible to use several different DDL*.TPL templates during the export or import. The assignment
of a specific DDL file to a single package is done within a simple text file, which then has to be specified
using the ddlMap option within the properties file of the Migration Monitor. Packages not listed in the
DDL mapping file use the default DDL control file.
Example
SYNTAX
DDL Mapping File
# DDL mapping file ddl_mapping.txt# !!! line with [GROUP_NAME] can be skipped# used for documentation purposes only[ SORTED UNLOAD ]# DDL file for sorted unloadddlFile = /export_dump/ABAP/DB/ORA/DDLORA.TPL# package namesSAPAPPL0SAPAPPL1SAPSDIC[ UNSORTED UNLOAD ]DDL file for unsorted unloadddlFile = ./DDLORA_LRG.TPL# table namesTABLE_ATABLE_BTABLE_C
8.1.3 Defining Groups of Packages
The “package group” feature is an enhancement to defining a package order. By defining groups, you
can prevent certain packages being executed in parallel and you can define how many large tables are
exported or imported at the same time. In addition, you can specify different values for the parameters
jobNum and taskArgs or loadArgs for each package. Package groups can be defined in the same text
file in which the package order can be defined (see parameter orderBy). The previous package order
format is also fully supported.
A group starts with any arbitrary name in brackets and ends when the next group starts.
If package groups are defined, the maximum number of parallel R3load jobs is the sum of jobNum of
all packages. All packages without a package group will be assigned to a “default group” with the number
of jobs that was defined in the Migration Monitor's properties file.
EXAMPLE
Package order file with group:
# custom package order
# package names
SAPAPPL0
8 Additional Information
8.1 R3load Procedures Using the Migration Monitor
2012-09-25 CUSTOMER 107/146
SAPAPPL1
SAPAPPL2
# package group
[ SEQUENTIAL GROUP ]
jobNum = 1
# table names
TABLE_A
TABLE_B
TABLE_C
8.1.4 Processing Split Tables
If tables have been split during the export, ensure before the import starts that the table exists (only
once) and that the primary key and the indexes are created (only once) before or after (as defined in
the DDL template) the table data has been imported. These tasks will automatically be synchronized
by the Migration Monitor.
WHR files are part of the package and have to be copied to the DATA export subdirectory to make sure
that the same WHR file is used for the export and import of the corresponding package.
The following database platforms do not support parallel data import:
■ IBM DB2 UDB for UNIX and Windows
■ MS SQL
You can ensure this by using the Defining Groups of Packages [page 107] feature.
EXAMPLE
Target database does not support parallel data import
During the export you have split the table MY_FIRST_TABLE into 3 packages and
MY_SECOND_TABLE into 5 packages. Now you want to run a maximum of 10 R3load processes for
parallel data import.
Create the file inputFile.txt with the following content:
[ MY_FIRST_TABLE ]
jobNum = 1
MY_FIRST_TABLE-1
MY_FIRST_TABLE-2
MY_FIRST_TABLE-3
[ MY_SECOND_TABLE ]
jobNum = 1
MY_SECOND_TABLE-1
MY_SECOND_TABLE-2
MY_SECOND_TABLE-3
8 Additional Information
8.1 R3load Procedures Using the Migration Monitor
108/146 CUSTOMER 2012-09-25
MY_SECOND_TABLE-4
MY_SECOND_TABLE-5
In this file, you can also define the processing order of packages or you can assign DDL files to
packages.
The inputFile.txt file has to be specified as a value for the Migration Monitor parameter
orderBy.
An R3load job is started for every group (MY_FIRST_TABLE and MY_SECOND_TABLE). The number
of parallel R3load jobs will be the total of the number of R3load jobs of each group plus the number
of R3load jobs defined for the default group (which is made up of all packages without an explicit
group name) defined by the parameter jobNum.
In this example, the parameter jobNum in the import_monitor_cmd.properties file has to be set
to 8 to ensure that no more than 10 R3load processes run in parallel.
Procedure
Re-Starting the Import of a Split Table Package
If the import of a package fails, the rows that belong to this package have to be deleted using the
WHERE condition assigned to this package before the data import is started again. The deletion with a
WHERE clause can be very time consuming, therefore it is faster to delete all rows of the corresponding
table manually and re-import all packages instead.
Restart for all other database platforms:
1. Eliminate the reason for the failure of the import of the packages.
2. Manually delete all rows of the table for which the import of one or more packages failed.
3. Remove the TSK files of all packages that import data into this table (<table name>-
<counter>__TPI.TSK). Do not remove the TSK files that create either the table or the indexes for
this table.
4. Adapt the file import_state.properties in the installation directory. Replace the status “+” of
all packages for the corresponding table that had been imported successfully and has to be re-
imported by “0” (see Restarting R3load Processes [page 41]).
5. Restart the import.
8.1.5 Starting the Migration Monitor
The Migration Monitor has to be started on the source database host (export monitor) and on the
target database host (import monitor).
You can specify options in the command line or in the export or import property files (see
Configuration [page 100]). The names of the property files are export_monitor_cmd.properties and
import_monitor_cmd.properties. Templates for these files are included in the application archive and
must be located in the current user's working directory.
8 Additional Information
8.1 R3load Procedures Using the Migration Monitor
2012-09-25 CUSTOMER 109/146
Any options specified in the command line take precedence over the corresponding options in the
application property file. Options are case sensitive, that is, options that are not recognized are ignored.
Prerequisites
■ Make sure that the export dump directory and its subdirectory exist as described in the following
table:
Directory Description
<export dump dir>/DATA Contains the STR files generated by R3ldctl
<export dump dir>/DB Contains the DDL<DBTYPE>.TPL files generated by R3ldctl
<export dump dir>/DB/<DBTYPE> Contains the EXT files generated by R3szchk (optional)
■ Make sure that the export dump directory can be accessed from the target host, either using a
shared directory (local to the export host) or by using Migration Monitor's FTP feature.
Procedure
1. Start the tool using one of the following ways:
6. The R3load log files, cmd files, and TSK files (if required) will be located in the directory /
<install_dir>/start (installDir parameter).
7. The DDLORA.TPL file must be copied to the /install_dir/start directory (installDir parameter)
before you start the import monitor.End of: Oracle |
8 Additional Information
8.1 R3load Procedures Using the Migration Monitor
114/146 CUSTOMER 2012-09-25
8.1.6 Output Files
Export
■ export_monitor.log
■ export_state.properties
■ ExportMonitor.console.log
Import
■ import_monitor.log
■ import_state.properties
■ ImportMonitor.console.log
Both the export and import state files contain package state lines such as SAPUSER=+.
The format of state lines is <PACKAGE>=<STATE>. Possible values for state are listed in the following
table:
Value Description
0 Package export/import not yet started
? Package export/import in progress
- Package export/import finished with errors
+ Package export/import finished successfully
If any ftp or net exchange options are used, then the export state file may contain a second <STATE>
column that refers to the state of the package transfer.
Then the export state file contains package state lines such as SAPUSER=++.
The format of state lines is <PACKAGE>=<STATE>. Possible values for state are listed in the following
table:
Value Description
0 Package export not yet started
? Package export in progress
- Package export finished with errors
+0 Package export finished successfully; package transfer not yet started
+? Package transfer in progress
+- Package transfer finished with errors
++ Package transfer finished successfully
8.1.7 Restarting R3load Processes
The state files export_state.properties and import_state.properties (see Output Files [page 115])
allow package states to be manually updated to restart failed R3load processes.
8 Additional Information
8.1 R3load Procedures Using the Migration Monitor
2012-09-25 CUSTOMER 115/146
EXAMPLE
If package processing failed and the package state has the value “–”, the state can be set to “0” and
processing of the package is restarted.
Procedure
■ To restart package processing, set the package state from “–” to “0”.
■ To skip package processing, set the package state from “0” or “–” to “+”. (This is not recommended,
because it can cause inconsistent data files or database content.)
■ If the package is currently being processed (the package state is “?”), then any manual modifications
of the package state are ignored.
If you restart the Migration Monitor itself, the tool automatically recognizes which R3load packages
have not been finished successfully and starts R3load processes to complete the missing packages. It is
not necessary to modify the state file.
8.1.8 Installing the Target System Using the Migration Monitor
This section describes the steps that you have to perform to install the target system using the Migration
Monitor.
Prerequisites
Make sure there is enough free space on the target system for the database load. To find out the size of
the export and the sizes of the tablespaces or dbspaces that are created, look at the file DBSIZE.XML
located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE> (Windows) or <EXPDIR>/DB/
<DATABASE> (UNIX).
Procedure
1. If you want to start the installation of the target host using the Migration Monitor, make sure that
at least the dump directory with the following files is accessible on the target host and that it
contains the correct data before you start the installer:
■ <dump dir>/LABEL.ASC
■ <dump dir>/DB/<DBTYPE>/DBSIZE.XML
■ <dump dir>/DB/DDLORA.TPL
If the dump directory is not shared on the target host, copy the files from the source system to the
target system as soon as they have been created on the source host using the (export) Migration
Monitor's FTP copy options.
2. Start the installer as described in the installation documentation for your SAP component.
8 Additional Information
8.1 R3load Procedures Using the Migration Monitor
116/146 CUSTOMER 2012-09-25
3. To install the target system, follow the instructions in the installer input dialogs and enter the
required parameters as far as the ABAP System > Database screen. On this screen, choose Standard
System Copy/Migration (R3load-Based).
4. Select the Use Migration Monitor option.
NOTE
If you need more information about input parameters, position the cursor on the field of the
respective parameter and press F1 .
5. When the installer displays the CD browser window and asks for the Export Migration CD, enter the
path to the export directory <EXPDIR>.
6. Continue as described in the installation documentation for your SAP component until a dialog
box appears that states:
If the export has been started on the source system and the export monitor is
running, you can now start the data load by starting the import monitor.
7. Check that the prerequisites in the dialog box are fulfilled by your system. If so, start the Migration
Monitor.
8. Complete the installation as described in the installation documentation for your SAP solution.
CAUTION
If you have to restart the import after an error, just restart the installer. The import is
continued with the table that was not imported successfully.
8.2 Additional Information About the Installer
The following sections provide additional information about the installer:
■ Useful Information About the installer [page 118]
■ Interrupted Installation [page 121]
■ Performing a Remote Installation [page 124]
■ Starting the Installer GUI Separately [page 128]
■ Running the Installer in Accessibility Mode [page 132]
■ Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle;SAP HANA DB;SAP HANA DB for i5/OS |
Entries in the Services File Created by the Installer [page 134]End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle;SAP HANA DB;SAP HANA DB for i5/OS |
■ Troubleshooting with the Installer [page 136]
■ Only valid for: IBM i5/OS |
Troubleshooting during the Database Load [page 137]End of: IBM i5/OS |
8 Additional Information
8.2 Additional Information About the Installer
2012-09-25 CUSTOMER 117/146
8.2.1 Useful Information About the Installer
This section provides information to consider when performing the export with the installer.
Integration
■ When you start the installer, the GUI, and the GUI server are also started. The installer GUI connects
using a secure SSL connection to the GUI server and the GUI server connects to the installer.
Only valid for: UNIX |
■ The installer normally creates the directory sapinst_instdir directly below the temporary
directory. The installer finds the temporary directory by checking the value of the environment
variables TEMP, TMP, or TMPDIR. If no value is set for these variables, the installer uses /tmp as default
directory.
■ The installer Self-Extractor extracts the installer executables to the temporary directory. These
executables are deleted again after the installer has stopped running. If required, you can terminate
the installer and the installer Self-Extractor by pressing Ctrl+C.End of: UNIX |
Only valid for: Windows |
■ The installer normally creates the installation directory sapinst_instdir, where it keeps its log
files, and which is located directly in the Program Files directory. If the installer is not able to
create sapinst_instdir directly below the Program Files directory, the installer tries to create
sapinst_instdir in the directory defined by the environment variable TEMP.
■ The installer creates a subdirectory for each installation option, called <sapinst_instdir>
\<installation_option>, which is located in %ProgramFiles%.
■ The installer Self-Extractor extracts the executables to a temporary directory (TEMP, TMP,
TMPDIR, or SystemRoot). These executables are deleted after the installer has stopped running.
Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You
can safely delete them.
The temporary directory also contains the installer Self-Extractor log file dev_selfex.out, which
might be useful if an error occurs.
If you want to terminate the installer and the installer Self-Extractor, do one of the following:
● Right-click the icon for the installer output window located in the Windows tray and choose
Exit.
● Click the icon for the installer output window located in the Windows tray and choose File
Exit .End of: Windows |
CAUTION
■ If the installer cannot find a temporary directory, the installation terminates with the error
FCO-00058.
8 Additional Information
8.2 Additional Information About the Installer
118/146 CUSTOMER 2012-09-25
■ I you want to use a different installation directory than the default, make sure that you create
it locally. Otherwise, you might experience problems when starting the SAP Java tools.
Only valid for: UNIX |
■ Before starting the export, make sure that you have at least the same amount of disk space available
in /sapmnt/<SAPSID>/<InstanceName>/SMD/program as is used in /sapmnt/<SAPSID>/
<InstanceName>/SMD/root/origin.
During the export, some archives are written to the program subdirectories and the installer aborts
if there is not enough space.
■ Make sure that the DISPLAY environment variable is set to <host_name>:0.0, where
<host_name> is the host where the installer GUI is displayed.End of: UNIX |
Only valid for: Windows |
■ Before starting the export steps on the primary application server instance of the source system,
make sure that you have at least the same amount of disk space available in \\SAPLOC\<SAPSID>
\<InstanceName>\SMD\program as is used in \\SAPLOC\<SAPSID>\<InstanceName>\SMD\root
\origin. During the export some archives are written to the program subdirectories and the
installer aborts if there is not enough space.End of: Windows |
Only valid for: IBM i5/OS |
■ Before you start the export of the existing SAP System, you have to download the current version
of R3szchk at http://service.sap.com/patches and copy it to directory /usr/sap/<>/SYS/exe/
run/.End of: IBM i5/OS |
NOTE
For a list of all available installer properties, enter the following command: sapinst —p.
■ If you use virtual host names for the primary application server or the database instance both (for
example, in a high availability environment), start the export with the property
SAPINST_USE_HOSTNAME=<virtual host>.
Only valid for: Windows |
■ During the installation, the default ports 21200, 21212, and 4239 are used for communication
between the installer, GUI server, GUI, and HTTP server, as follows:
● The installer uses port 21200 to communicate with the GUI server.
● The GUI server uses port 21212 to communicate with the GUI client.
● 4239 is the port of the HTTP server, which is part of the GUI server.
If these ports are already in use, execute sapinst.exe with the following command line parameters:
■ To display a list of all available installer properties, start the installer as described above with the
option -p:
./sapinst -p.End of: UNIX |
NOTE
For more information about input parameters in the installer, position the cursor on the
parameter field and choose F1 .
Troubleshooting during the Export Process
Processing Phase
If the export process aborts during the processing phase (for example, due to a hardware failure, such
as power outage, operating system crash, file system full), you have to repeat the export of the complete
package.
1. Remove the <package>.<nnn> dump files, the <package>.TOC file, and the <package>.log file.
2. Make sure that all tables in the <package>.*TSK* file have the status flag xeq or err set.
3. Repeat the export of the complete package.
Dialog Phase
If an error occurs during the dialog phase, the installer stops and displays a dialog that informs you
about the error.
You can now:
■ View the log file directly by choosing View Logs.
■ Try to solve the problem.
■ Stop the process by choosing Cancel in the installer menu.
8 Additional Information
8.2 Additional Information About the Installer
120/146 CUSTOMER 2012-09-25
For more information, see Interrupted Installation with the Installer [page 121].
■ After resolving the problem, you can continue by choosing Retry.
Only valid for: UNIX |
System Copy – export on UNIX (especially for upgraded systems)
Symptom:
Processes started as <sapsid>adm or ora<sid> OS users cannot create or open files in the installation
directory.
Reason:
Only members of sapinst UNIX group can access the installation directory. This group is created by
the installer as of SAP NetWeaver 7.1.
Solution:
1. Manually associate <sapsid>adm and ora<sid> OS users with sapinst group if this association is
missing.
2. Verify the /etc/group file and check if the sapinst group exists and OS users are members of this
group.
3. If the sapinst group does not exist yet, start the installer. The installer creates this group during
startup before the product catalog list is displayed.
4. Edit /etc/group file and associate OS users with sapinst group.
5. Continue with the export.End of: UNIX |
More Information
Additional Information About the Installer [page 117]
8.2.2 Interrupted Installation
The SAP system installation might be interrupted for one of the following reasons:
■ An error occurred during the Define Parameters or Execute phase:
The installer does not abort the installation in error situations. If an error occurs, the installation
pauses and a dialog box appears. The dialog box contains a short description of the choices listed
in the table below as well as a path to a log file that contains detailed information about the error.
■ You interrupted the installation by choosing Cancel in the SAPinst menu.
CAUTION
If you stop an option in the Execute phase, any system or component installed by this option
is incomplete and not ready to be used. Any system or component uninstalled by this option
is not completely uninstalled.
The following table describes the options in the dialog box:
8 Additional Information
8.2 Additional Information About the Installer
2012-09-25 CUSTOMER 121/146
Option Definition
Retry The installer retries the installation from the point of failure without repeating any of the previous steps.This is possible because the installer records the installation progress in the keydb.xml file.We recommend that you view the entries in the log files, try to solve the problem, and then choose Retry.If the same or a different error occurs, the installer displays the same dialog box again.
Stop The installer stops the installation, closing the dialog box, the installer GUI, and the GUI server.The installer records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps. See the procedure below.
Continue The installer continues the installation from the current point.
View Log Access installation log files.
Procedure
This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to
continue an interrupted installation after an error situation.
1. Only valid for: Windows |
Log on to your remote host as a user who is a member of the local administrators group.End of: Windows |
2. Only valid for: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |
Log on to your local UNIX host as user root.
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database.
End of: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |
3. Only valid for: IBM i5/OS |
Log on to your local IBM i host as the installation user with similar authorization rights as
QSECOFR.End of: IBM i5/OS |
4. Only valid for: Windows |
Make the medium for the installation master (folder <Product>_IM_<OS>_<DB>) available on the
installation host.End of: Windows |
5. Only valid for: UNIX |
Make sure that the installation media are still available on the installation host.
For more information, see Preparing the Installation Media [page 19].
8 Additional Information
8.2 Additional Information About the Installer
122/146 CUSTOMER 2012-09-25
Only valid for: UNIX |
RECOMMENDATION
Make installation media locally available. For example, if you use Network File System (NFS),
reading from media mounted with NFS might fail.
End of: UNIX |
Only valid for: Solaris |
NOTE
If you mount installation media, make sure that you do this with option nomaplcase.
End of: Solaris |
End of: UNIX |
6. Only valid for: IBM i5/OS |
Make available the installation master media.
NOTE
Make sure that the media is available locally. We do not recommend using Network File
System (NFS).
End of: IBM i5/OS |
7. Only valid for: Windows |
Restart the installer by double-clicking sapinst.exe from the directory to which you unpacked
the SWPM10SP<support package number>_<version number>.SAR file.End of: Windows |
8. Only valid for: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |
Restart the installer from the directory to which you unpacked the SWPM10SP<support package
number>_<version number>.SAR file by executing the following command: /<path to unpack
directory>/sapinst
End of: UNIX | IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;No Database;Oracle;SAP HANA DB |
9. Only valid for: IBM i5/OS |
Restart the installer from the directory to which you unpacked the SWPM10SP<support package
number>_<version number>.SAR file.
Enter the following commands:
CD DIR('<path to unpack directory>')
CALL PGM(QP2TERM) PARM('./sapinst') or
CALL PGM(QP2TERM) PARM('./sapinst' '-nogui') (if using the remote installer GUI)End of: IBM i5/OS |
10. From the tree structure in the Welcome screen, select the installation option that you want to
continue and choose Next.
The What do you want to do? screen appears.
11. In the What do you want to do? screen, decide between the following alternatives and continue with
Next:
Alternative Behavior
Run a new option The installer does not continue the interrupted installation option. Instead, it moves the content of the old installation directory and all installation-
8 Additional Information
8.2 Additional Information About the Installer
2012-09-25 CUSTOMER 123/146
Alternative Behaviorspecific files to a backup directory. Afterwards, you can no longer continue the old installation option.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds>.
NOTE
All actions taken by the installation before you stopped it (like creating directories, or users) will not be revoked.
EXAMPLE
log_01_Oct_2008_13_47_56
CAUTION
The installer moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.
Continue with the old option The installer continues the interrupted installation from the point of failure.
8.2.3 Performing a Remote Installation
You use this procedure to install your SAP system on a remote host. In this case, the installer and the
GUI server run on the remote host, and the installer GUI client (the “installer GUI” for short) runs on
the local host. The local host is the host from which you control the installation with the installer GUI.
Only valid for: IBM i5/OS;UNIX |
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know root credentials on the remote host, you can specify
another operating system user for authentication purposes. You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command
line. You have to confirm that the user is a trusted one. For more information, see SAP Note
1745524.End of: IBM i5/OS;UNIX |
Only valid for: Windows |
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host, you can
specify another operating system user for authentication purposes. You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinst.exe from the command line. You
have to confirm that the user is a trusted one. For more information, see SAP Note 1745524.End of: Windows |
– where <port_number_gui_server_to_gui_client> is the port the GUI server uses to
communicate with the GUI client (21212 by default).
● If you are performing a remote installation with the installer and the installer GUI running
on different hosts, execute the following command:
sapinstgui.exe -host <remote_host> -port
<port_number_gui_server_to_gui_client>
– where <remote_host> is the name of the remote host, and
<port_number_gui_server_to_gui_client> is the port the GUI server uses to
communicate with the GUI client (21212 by default).
The installer GUI starts and connects to the installer.
Starting the Installer GUI on UNIX
1. Make the installer software available on the host on which you want to start the installer GUI.
For more information, see Preparing the Installation Media [page 19].
8 Additional Information
8.2 Additional Information About the Installer
130/146 CUSTOMER 2012-09-25
Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |
NOTE
If you want to start the installer GUI on a Linux 32-bit operating system, make the
SWPM10SP<support package number>_<version number>.SAR file for Linux I386 available.
End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;No Database;Oracle;SAP HANA DB |
2. Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;Oracle;SAP HANA DB;SAP HANA DB for i5/OS |
Start the installer by executing the following command: /<path to unpack directory>/
sapinstgui using the appropriate command line parameters:End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows);IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;Oracle;SAP HANA DB;SAP HANA DB for i5/OS |
■ If you want to perform a remote installation, proceed as follows:
1. Check the version of the sapinstgui executable by entering the following command:
/<path to unpack directory>/sapinstgui –sfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation [page 124]).
2. Start the installer GUI by entering the following command:
/<path to unpack directory>/sapinstgui -host <remote_host> -port
<port_number_gui_server_to_gui_client>
– where <remote_host> is the name of the remote host, and
<port_number_gui_server_to_gui_client> is the port the GUI server uses to
communicate with the GUI client (21212 by default).
■ If you closed the installer GUI using File Exit and want to reconnect to the installer,
proceed as follows:
● If you are performing a local installation with the installer and the installer GUI running
on the same host, execute the following command:
/<path to unpack directory>/sapinstgui -port
<port_number_gui_server_to_gui>
– where <port_number_gui_server_to_gui> is the port the GUI server uses to
communicate with the GUI client (21212 by default).
● If you are performing a remote installation with the installer and the installer GUI running
on different hosts, execute the following command:
/<path to unpack directory>/sapinstgui -host <remote_host> -port
<port_number_gui_server_to_gui>
– where <remote_host> is the name of the remote host, and
<port_number_gui_server_to_gui> is the port the GUI server uses to communicate with
the GUI client (21212 by default).
The installer GUI starts and connects to the installer.
8 Additional Information
8.2 Additional Information About the Installer
2012-09-25 CUSTOMER 131/146
3. Only valid for: z/OS |
Start the installer GUI in one of the following ways:
■ If the installer GUI runs on the same host as the installer and the installer GUI, enter the
following command without any additional parameters:
./startInstGui.sh
By default the installer GUI uses the local host.
■ If the installer runs on a different host from the installer GUI (remote installation), enter the
following command with additional parameters:
./startInstGui.sh -host <host_name>
<host_name> is the host name of the installation host
NOTE
● If you enter the command without additional parameters, the installer GUI uses the
local host as default. The installer GUI starts and tries to connect to the installer.
Since the installer is running on another host, the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears.
In this case, enter the name of the host on which the installer is running and choose
Log on.
The first dialog of the installation appears and you can perform the remote
installation from your local host.
● For a list of options to start the installer GUI, change to the same directory as your
the installer executable and enter the command:
./startInstGui.sh -h
End of: z/OS |
8.2.5 Running the Installer in Accessibility Mode
You can also run the installer in accessibility mode. The following features are available:
■ Keyboard access:
This feature is available for all operating systems.
■ High-contrast color:
Only valid for: Windows |
This feature is derived from the Windows display properties. You can use it either for a local
installation or for a remote installation.End of: Windows |
Only valid for: IBM i5/OS;UNIX |
This feature is derived from the Windows display properties. Therefore, to enable this feature, you
must perform a remote installation with the installer GUI running on a Windows host.End of: IBM i5/OS;UNIX |
■ Custom font setting:
8 Additional Information
8.2 Additional Information About the Installer
132/146 CUSTOMER 2012-09-25
Only valid for: Windows |
This feature is derived from the Windows display properties. You can use it either for a local
installation or for a remote installation.End of: Windows |
Only valid for: IBM i5/OS;UNIX |
This feature is derived from the Windows display properties. Therefore, to enable this feature, you
must perform a remote installation with the installer GUI running on a Windows host.End of: IBM i5/OS;UNIX |
Procedure
Activating and Adjusting Accessibility Settings on Windows
You first have to activate and adjust the relevant settings for the font size and color schemes before
you start the installer or the installer GUI.
NOTE
The following procedure applies for Windows Server 2008 and might be different when using
another Windows operating system.
1. Right click on your Windows desktop and choose Personalize.
2. Choose Adjust font size (DPI) and choose Larger scale (120 DPI).
To define other font size schemes, choose Custom DPI.
3. In the right-hand pane, select Window Color and Appearance.
Select a color scheme from the Color scheme dropdown box.
To define your own color schemes, choose Advanced.
Running the Installer in Accessibility Mode
Only valid for: Windows |
You can either perform a local installation, where the installer and the installer GUI are running on
the same host, or a remote installation, where the installer and the installer GUI are running on different
hosts.
■ Local installation:
Start the installer as described in Running the Installer on UNIX or Windows to Perform the Export [page 29]
by executing the following command:
sapinst.exe –accessible
■ Remote installation:
1. Start the installer on the remote host by executing the following command from the
command line as described in Performing a Remote Installation [page 124]:
sapinst.exe –nogui
2. Start the installer GUI on the local host by executing the following command from the
command line as described in Starting the installer GUI Separately for a Remote Installation [page 128]:
<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.
ExampleExample
Arrows separating the parts of a navigation path, for example, menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
http://www.sap.com Textual cross-references to an internet address
/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.
■ Cross-references to other documentation or published works
Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE
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, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the United States and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.Oracle and Java are registered trademarks of Oracle and its affiliates.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.Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.IOS is a registered trademark of Cisco Systems Inc.RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited.Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.INTERMEC is a registered trademark of Intermec Technologies Corporation.Wi-Fi is a registered trademark of Wi-Fi Alliance.Bluetooth is a registered trademark of Bluetooth SIG Inc.Motorola is a registered trademark of Motorola Trademark Holdings LLC.Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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 other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.
140/146 CUSTOMER 2012-09-25
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.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.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.
Legal Software Terms
Terms for Included Open Source Software
This SAP software contains also the third party open source software products listed below. Note that for these third party products the following special terms and conditions shall apply.1. This software includes ANTLR, which is released under the following BSD license:
[The BSD License]Copyright (c) 2010 Terence ParrAll rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: ■ Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer. ■ Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution. ■ Neither the name of the author nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
2. SAP License Agreement for STLportSAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingDietmar-Hopp-Allee 1669190 Walldorf, Germany(hereinafter: SAP)andyou(hereinafter: Customer)1. Subject Matter of the Agreement
2012-09-25 CUSTOMER 141/146
1. SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++ library (STLport) and its documentation without fee.
2. By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws, and to all of the terms and conditions of this Agreement.
3. The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions.
4. Customer shall maintain the following copyright and permissions notices on STLport sources and its documentation unchanged: Copyright 2001 SAP AG
5. The Customer may distribute original or modified STLport sources, provided that: ■ The conditions indicated in the above permissions notice are met; ■ The following copyright notices are retained when present, and conditions provided in accompanying
permission notices are met:Copyright 1994 Hewlett-Packard CompanyCopyright 1996,97 Silicon Graphics Computer Systems Inc.Copyright 1997 Moscow Center for SPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AG
Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice.Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. SAP makes no representations about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications.
2. Support and MaintenanceSAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore shall be not included.All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions and shall be subject to a separate contract.
3. Exclusion of warrantyAs the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the STLport is error-free, without material defects or suitable for a specific application under third-party rights. Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes.
4. Limited Liability
142/146 CUSTOMER 2012-09-25
1. Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this (i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based on the failure of a guaranteed attribute.
2. If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract, due to the circumstances known to it at that point in time representing a typical transfer of the software.
3. In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a defect or lost profit.
4. SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5,000.
5. The Customer shall take adequate measures for the protection of data and programs, in particular by making backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and its recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by observing this obligation.
6. The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees or agents of SAP.
3. Adobe Document ServicesAdobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries. For information on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer, see SAP Note 854621.
4. Apache License, Version 2.01. Definitions:
■ "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
■ "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
■ "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
■ "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. ■ "Source" form shall mean the preferred form for making modifications, including but not limited to software
source code, documentation source, and configuration files. ■ "Object" form shall mean any form resulting from mechanical transformation or translation of a Source
form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
■ "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
■ "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
■ "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
■ "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright LicenseSubject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent LicenseSubject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
4. RedistributionYou may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:1. You must give any other recipients of the Work or Derivative Works a copy of this License; and2. You must cause any modified files to carry prominent notices stating that You changed the files; and3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent,
trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
5. Submission of ContributionsUnless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
6. TrademarksThis License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of WarrantyUnless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
144/146 CUSTOMER 2012-09-25
8. Limitation of LiabilityIn no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional LiabilityWhile redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides