Extending a Domain to Support Additional Components

20-2 Oracle Fusion Middleware Administrators Guide cloningclient.jar file and movement scripts that are compatible with the version of the Middleware home you want to copy. You can apply the copy of the Middleware home to the same host or a different host. ■ Java components: You can copy the configuration of a domain containing Java components, such as Oracle SOA Suite and Oracle Business Activity Monitoring to the same or a different Middleware home, on the same host or a different host. ■ System components: You can copy the configuration of a domain containing system components, such as Oracle HTTP Server and Oracle Internet Directory, to the same or a different Oracle instance, to the same or a different Middleware home, on the same host or a different host.

20.2 Understanding the Movement Process

When you move an entity of Oracle Fusion Middleware, the scripts take a snapshot of the information required for the movement. The following topics describe the movement process: ■ Understanding the Movement of a Middleware Home ■ Understanding the Movement of Components

20.2.1 Understanding the Movement of a Middleware Home

When you move a Middleware home, you create an archive of the source Middleware home and use the archive to create the copy of the Middleware home: 1. At the source, you run the copyBinary script, specifying the Middleware home that you want to copy. The script prepares the source and creates an archive. It also records the file permissions of the Middleware home and the Oracle homes within the Middleware home. The archive contains the Oracle WebLogic Server home and all of the Oracle homes in the Middleware home. 2. At the destination, you run the pasteBinary script, specifying a destination for the Middleware home. The script checks to see that the prerequisites are met at the destination. It extracts the files from the archive file, registers the Oracle homes with the Oracle inventory and registers the WebLogic Server home with the Middleware home. The script then restores the file permissions and relinks any files if that is necessary. Note the following: ■ The copyBinary and pasteBinary scripts do not carry over all the dependencies of the source Middleware home, WebLogic Server home, and Oracle homes, such as loadable modules or application-specific libraries to the target home, because the scripts proceed by copying the Middleware home and the entire source WebLogic Server home and Oracle homes to the destination Middleware home. Any files outside the source WebLogic Server or Oracle home are not automatically copied. Hence, any applications that refer to files outside the source WebLogic Server or Oracle home may not work properly in the target home. See Also: Chapter 21 for information about moving from a test environment to a production environment Using the Movement Scripts 20-3 The Oracle home that is copied as a part of the Middleware home contains only the binary files. ■ When you copy a Middleware home, only the read-only portions of the Middleware home are copied. Any user configuration files, such a the user_ projects directory, are excluded from the archive. The WebLogic Server domain is not copied. Use the copyBinary and pasteBinary scripts to copy the domain. ■ You cannot move a Middleware Home if its path is a symbolic link. See Section 21.3.3 for detailed information about these steps.

20.2.2 Understanding the Movement of Components

When you move Oracle Fusion Middleware components, you create an archive of the source components configuration and use the archive to create the component at the target. You use the following: ■ For Java components, such as Oracle SOA Suite, you use the copyConfig, extractMovePlan, and pasteConfig scripts to copy the configuration, including the domain, the Administration Server, and the Managed Servers. ■ For Node Manager, you use the copyConfig, extractMovePlan, and pasteConfig scripts to copy the configuration. ■ For some system components, such as Oracle HTTP Server, you use the copyConfig, extractMovePlan, and pasteConfig scripts to copy the configuration, including the Oracle instance. To move components, you take the following general steps: 1. You move the Middleware home, as described in Section 20.2.1 . 2. At the source, make sure that the Administration Server and all Managed Servers are started. 3. At the source, you run the copyConfig script, specifying the source component that you want to copy. The script creates a configuration archive file that contains a snapshot of the configuration of an Oracle WebLogic Server domain or system component instance. 4. You extract a move plan from the source using the extractMovePlan script. A move plan contains configuration settings of the source environment. You can edit the move plan, specifying properties for the target environment. 5. At the target, you run the pasteConfig script, specifying the destination for the component and the move plan. The script checks to see that the prerequisites are met at the target. It extracts the files from the archive file and uses the information in the move plan to modify the configuration on the target. Then, it restores the file permissions. In addition, the pasteConfig scripts starts the Administration Server. Note: The scripts replicate the topology of the source. For example, if the source domain contains Managed Servers server_1 and server_2 on Host A and Managed Servers server_3 and server_4 on Host B, you must specify a similar relationship between Managed Servers and hosts at the target. You specify the hosts for each Managed Server in the move plan. 20-4 Oracle Fusion Middleware Administrators Guide Note that you must ensure that components, such as Oracle WebLogic Server and Oracle Coherence, are installed in the directory structure of the source Middleware home. See Section 21.3.4 and Section 21.3.5 for detailed information about these steps.

20.3 Movement Scripts

Oracle Fusion Middleware uses the following jar file to execute the scripts necessary to move the binary and configuration files: UNIX ORACLE_COMMON_HOMEjlibcloningclient.jar Windows ORACLE_COMMON_HOME\jlib\cloningclient.jar You use the following scripts to move a Middleware home or component: ■ To copy the binary files of the source Middleware home: UNIX ORACLE_COMMON_HOMEbincopyBinary.sh Windows ORACLE_COMMON_HOME\bin\copyBinary.cmd See Section 20.3.1.1 for the syntax of the script. ■ To apply the copied Middleware home to the target: UNIX ORACLE_COMMON_HOMEbinpasteBinary.sh Windows ORACLE_COMMON_HOME\bin\pasteBinary.cmd See Section 20.3.1.2 for the syntax of the script. ■ To copy the source component configuration: UNIX ORACLE_COMMON_HOMEbincopyConfig.sh Windows ORACLE_COMMON_HOME\bin\copyConfig.cmd See Section 20.3.1.3 , Section 20.3.1.4 , Section 20.3.1.5 for the syntax of the script. ■ To extract a move plan from the source component: UNIX ORACLE_COMMON_HOMEbinextractMovePlan.sh Windows ORACLE_COMMON_HOME\bin\extractMovePlan.cmd See Section 20.3.1.6 for the syntax of the script. ■ To apply the copied component configuration to the target: UNIX ORACLE_COMMON_HOMEbinpasteConfig.sh Windows ORACLE_COMMON_HOME\bin\pasteConfig.cmd See Section 20.3.1.7 , Section 20.3.1.8 , and Section 20.3.1.9 for the syntax of the script. To view the help on any of these scripts, use the -help option. For example: .pasteConfig.sh -javaHome scratchOracleMiddlewarejdk160_21 -help Note that the help shows the UNIX version of the parameter values. For other platforms, such as Windows, change the parameter values for the platform. To specify additional Java options, define the T2P_JAVA_OPTIONS environment variable and specify the options in the variable definition. The following examples set the value for the Java temp directory: ■ On Linux or UNIX: