Applying Oracle JRF Template to a Managed Server or Cluster

Using the Movement Scripts 20-5 setenv T2P_JAVA_OPTIONS -Djava.io.tmpdir=homet2ptemp export T2P_JAVA_OPTIONS ■ On Windows: set T2P_JAVA_OPTIONS=-Djava.io.tmpdir=c:\home\t2p\temp

20.3.1 Movement Scripts Syntax

The following topics describe the syntax of the movement scripts. The options are described in the tables that follow the syntax. ■ copyBinary Script ■ pasteBinary Script ■ copyConfig Script for Java Components ■ copyConfig Script for System Components ■ copyConfig Script for Node Manager ■ extractMovePlan Script ■ pasteConfig Script for Java Components ■ pasteConfig Script for System Components ■ pasteConfig Script for Node Manager Note: If you are applying the archive of a Middleware home on a host that does not yet have Oracle Fusion Middleware installed, note the following: ■ The host must have JDK 1.6.04 or higher installed. In addition, ensure that the PATH, CLASSPATH, and JAVA_HOME environment variables point to the JDK. ■ Copy the pasteBinary script from the following location in the source host to the target host: UNIX ORACLE_COMMON_HOMEbinpasteBinary.sh Windows ORACLE_COMMON_HOME\bin\pasteBinary.cmd ■ Copy the following file from the following location in the source host to the target host: UNIX ORACLE_COMMON_HOMEjlibcloningclient.jar Windows ORACLE_COMMON_HOME\jlib\cloningclient.jar ■ If you run the pasteBinary script from a different location than ORACLE_COMMON_HOMEbin, then the pasteBinary script and the cloningclient.jar file must be in the same directory. If you are running pasteBinary on a host that has no prior Oracle Fusion Middleware installations, ORACLE_COMMON_homebin will not exist prior to running pasteBinary, and therefore the pasteBinary script and cloningclient.jar must be in the same directory. ■ Ensure that the files have execute permission. 20-6 Oracle Fusion Middleware Administrators Guide

20.3.1.1 copyBinary Script

Creates an archive file of the source Middleware home, by copying the binary files of that Middleware home, including all of its Oracle homes and its WebLogic Server home, into the archive file. The syntax is: copyBinary -javaHome path_of_jdk -archiveLoc archive_location -sourceMWHomeLoc MW_HOME [-invPtrLoc Oracle_InventoryLocation] [-logDirLoc log_dir_path] [-silent {true | false}] [-ignoreDiskWarning {true | false}] The following example shows how to create an archive of a Middleware home on Linux: copyBinary.sh -javaHome scratchOracleMiddleware1jrockit_160_20_D1.1.0-18 -archiveLoc tmpmw_copy.jar -sourceMWHomeLoc scratchOracleMiddleware1 -invPtrLoc scratchoracleoraInst.loc Table 20–1 describes the options for the copyBinary script. Note: ■ All movement scripts ask if you want to continue whenever you do not specify the -silent true option. To continue, you must type yes, which is not case sensitive. Any words other than yes causes the script to return an error. Also note that, in silent mode, the scripts generate an error if you do not provide passwords where they are needed. ■ Most options have shortcut names, as described in the tables later in the following sections. ■ The value of options must not contain a space. For example, on Windows, you cannot pass the following as a value to the -javaHome option: C:\Program Files\jdk ■ The value of the javaHome option must use the JAVA HOME that is defined in the following file note the period . before the filename: MW_HOMEwlserver_n.product.properties Note: Before you execute the copyBinary script, ensure that all Oracle homes in the Middleware home are either 32 bit or 64 bit. The operation does not support a mix of 32-bit and 64-bit Oracle homes. When you execute the command, you must specify a matching Java home. That is, if the Oracle homes are 64 bit, you must specify a 64-bit Java home. If the Oracle homes are 32 bit. you must specify a 32-bit Java home.