Oracle Fusion Middleware provides a series of scripts that you can use to move your environment, for example replicating (cloning) a test environment to a production environment. The scripts enable you to copy a Middleware home and the Oracle homes and Oracle WebLogic Server domains, as well as the configuration of certain Oracle Fusion Middleware components, such as Oracle SOA Suite, Oracle HTTP Server, Oracle Internet Directory, and Oracle Virtual Directory. This chapter explains the scripts you can use to move these entities.
This chapter includes the following topics:
Note:
For detailed procedures for moving Oracle Fusion Middleware from one environment to another, see Chapter 21. That chapter describes using these scripts, and other steps for moving from a source environment to a target environment.
The movement scripts minimize the amount of work that would otherwise be required to reapply all the customization and configuration changes made in one environment to another. You can use these scripts to:
Create a Middleware home that is a copy of a production, test, or development environment. The scripts create a new Middleware home with all patches applied to all of the Oracle homes and the WebLogic Server home in a single step. This is in contrast to separately installing and applying any patches to the WebLogic Server home and separate Oracle homes.
Prepare a "gold" image of a patched Middleware home and deploying it to many hosts.
Move the configuration of a domain or Oracle instance, including the components in the domain or Oracle instance, from one environment to another.
You can move the following, to the same host or a different host. The source and target environments must share the same operating system and the same platform architecture (in terms of number of bits).
Middleware home: You can copy the Middleware home, the Oracle WebLogic Server home, and all of the Oracle homes within the Middleware home. (You can copy a Middleware home that contains no Oracle homes, but you must use the cloningclient.jar file and movement scripts that are compatible with the version of the Middleware home that you want to copy.)
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.
An Oracle instance: You can copy the configuration of an Oracle instance to the same or a different Middleware home. When you move an Oracle instance, you move all configuration files in that instance for all system components in that Oracle instance.
Alternatively, you can move one of the system components, such as Oracle HTTP Server, within an Oracle instance. In that case, the configuration of the Oracle instance and the specified component are moved. You can move the following system components in this way:
Oracle HTTP Server
Oracle Virtual Directory
Oracle Internet Directory
Oracle BI Enterprise Edition
Note:
The movement scripts support moving most of the Oracle Fusion Middleware components, but for some components, you must take manual steps in addition to, or instead of, using the scripts. See Chapter 21 for the procedures for moving Oracle Fusion Middleware components from a source to a target environment, including when to use the scripts.
Table 20-1 shows which Oracle Fusion Middleware components support the movement scripts and provides pointers to the procedures for moving each component.
Table 20-1 Support for Movement Scripts
Component | Supported? | Procedure Documented |
---|---|---|
Oracle Access Management Access Manager |
Yes |
|
Oracle Access Management Identity Federation |
Yes |
|
Oracle Access Management Mobile and Social |
Yes |
|
Oracle Access Management Secure Token Service |
Yes |
|
Oracle Adaptive Access Manager |
Yes |
|
Oracle B2B |
Yes |
|
Oracle Business Activity Monitoring |
No |
|
Oracle Business Intelligence |
Yes |
|
Oracle Business Intelligence Discoverer |
No |
|
Oracle Business Process Management |
Yes |
|
Oracle Data Integrator |
Yes |
|
Oracle Directory Integration Platform |
Yes |
|
Oracle Enterprise Performance Management Workspace |
No |
|
Oracle Entitlements Server |
Yes |
|
Oracle Essbase |
No |
|
Oracle Forms Services |
No |
|
Oracle HTTP Server |
Yes |
|
Oracle Human Workflow |
Yes |
|
Oracle Hyperion Calculation Manager |
No |
|
Oracle Hyperion Financial Reporting |
No |
|
Oracle Hyperion Provider Service |
No |
|
Oracle Hyperion Smart View for Office |
No |
|
Oracle Identity Manager |
Yes |
|
Oracle Identity Navigator |
Yes |
|
Oracle Information Rights Management |
No |
|
Oracle Internet Directory |
Yes |
|
Oracle Platform Security Services |
Yes |
|
Oracle Portal |
No |
|
Oracle Privileged Account Manager |
Yes |
|
Oracle Real-Time Decisions |
Yes |
|
Oracle Reports |
No |
|
Oracle Service Bus |
No |
"Customization" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus. |
Oracle SOA Suite |
Yes |
|
Oracle Unified Directory |
No |
"Moving From a Test to a Production Environment" in the Oracle Fusion Middleware Administrator's Guide for Oracle Unified Directory. |
Oracle User Messaging Service |
No |
|
Oracle Virtual Directory |
Yes |
|
Oracle Web Cache |
No |
|
Oracle Web Services Manager |
Yes |
|
Oracle WebCenter Content |
Yes |
|
Oracle WebCenter Content: Imaging |
Yes |
|
Oracle WebCenter Content: Inbound Refinery |
Yes |
|
Oracle WebCenter Content: Records |
Yes |
|
Oracle WebCenter Portal |
Yes |
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:
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:
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.
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.
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 as the user_projects directory, are excluded from the archive. The WebLogic Server domain is not copied. (Use the copyConfig and pasteConfig scripts to copy the domain.)
You cannot move a Middleware Home if its path is a symbolic link.
See Section 21.3.4 for detailed information about these steps.
When you move Oracle Fusion Middleware components, you create an archive of the source component's configuration and use the archive to create the component at the target. You use the following:
For Node Manager, you use the copyConfig, extractMovePlan, and pasteConfig scripts to copy the configuration.
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 Oracle instances, you use the copyConfig, extractMovePlan, and pasteConfig scripts to copy the configuration of the Oracle instance, including all system components in the Oracle instance.
Alternatively, you can specify that only one of the components, such as Oracle HTTP Server, within an Oracle instance be copied. In that case, the configuration of the Oracle instance and the specified component are moved.
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.)
To move components, you take the following general steps:
You move the Middleware home, as described in Section 20.2.1.
At the source, make sure that the Administration Server and all Managed Servers are started.
At the source, run the copyConfig script, specifying the source entity, such as a domain, Node Manager, or Oracle instance, 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, Node Manager, or system component instance.
At the source, extract a move plan using the extractMovePlan script. A move plan contains configuration settings of the source environment.
Edit the move plan specifying properties for the target environment.
At the target, run the pasteConfig script, specifying the destination for the domain, Node Manager, or Oracle instance, and the move plan location. 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 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.6 and Section 21.3.7 for detailed information about these steps.
Oracle Fusion Middleware uses the following jar file to execute the scripts necessary to move the binary and configuration files:
(UNIX) ORACLE_COMMON_HOME/jlib/cloningclient.jar (Windows) ORACLE_COMMON_HOME\jlib\cloningclient.jar
Table 20-2 shows the scripts you use to move a Middleware home or component.
TO: | Script | See: |
---|---|---|
Copy the binary files of the source Middleware home |
(UNIX) ORACLE_COMMON_HOME/bin/copyBinary.sh (Windows) ORACLE_COMMON_HOME\bin\copyBinary.cmd |
|
Apply the copied Middleware home to the target |
(UNIX) ORACLE_COMMON_HOME/bin/pasteBinary.sh (Windows) ORACLE_COMMON_HOME\bin\pasteBinary.cmd |
|
Copy the domain and Java component configuration |
(UNIX) ORACLE_COMMON_HOME/bin/copyConfig.sh (Windows) ORACLE_COMMON_HOME\bin\copyConfig.cmd |
|
Copy the Oracle instance configuration |
(UNIX) ORACLE_COMMON_HOME/bin/copyConfig.sh (Windows) ORACLE_COMMON_HOME\bin\copyConfig.cmd |
|
Copy the system component configuration |
(UNIX) ORACLE_COMMON_HOME/bin/copyConfig.sh (Windows) ORACLE_COMMON_HOME\bin\copyConfig.cmd |
|
Copy the Node Manager configuration |
(UNIX) ORACLE_COMMON_HOME/bin/copyConfig.sh (Windows) ORACLE_COMMON_HOME\bin\copyConfig.cmd |
|
Extract a move plan from the domain or component |
(UNIX) ORACLE_COMMON_HOME/bin/extractMovePlan.sh (Windows) ORACLE_COMMON_HOME\bin\extractMovePlan.cmd |
|
Apply the copied configuration for the domain and Java components to the target |
(UNIX) ORACLE_COMMON_HOME/bin/pasteConfig.sh (Windows) ORACLE_COMMON_HOME\bin\pasteConfig.cmd |
|
Apply the copied configuration for the Oracle instance to the target |
(UNIX) ORACLE_COMMON_HOME/bin/pasteConfig.sh (Windows) ORACLE_COMMON_HOME\bin\pasteConfig.cmd |
|
Apply the copied configuration for a system component to the target |
(UNIX) ORACLE_COMMON_HOME/bin/pasteConfig.sh (Windows) ORACLE_COMMON_HOME\bin\pasteConfig.cmd |
|
Apply the copied configuration for the Node Manager to the target |
(UNIX) ORACLE_COMMON_HOME/bin/pasteConfig.sh (Windows) ORACLE_COMMON_HOME\bin\pasteConfig.cmd |
|
Generate a file containing an obfuscated password |
(UNIX) ORACLE_COMMON_HOME/bin/obfuscatePassword.sh (Windows) ORACLE_COMMON_HOME\bin\obfuscatePassword.cmd |
To view the help on any of these scripts, use the -help option. For example:
./pasteConfig.sh -javaHome /scratch/Oracle/Middleware/jdk160_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:
setenv T2P_JAVA_OPTIONS "-Djava.io.tmpdir=/home/t2p/temp" export T2P_JAVA_OPTIONS
On Windows:
set T2P_JAVA_OPTIONS="-Djava.io.tmpdir=c:\home\t2p\temp"
Note:
A Universal Uniform Naming Convention (UNC) path is not supported on Windows. For example, the following is not supported:
\\host_name\oracle\java\win64\jdk6\jre\bin\java
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_HOME/bin/pasteBinary.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_HOME/jlib/cloningclient.jar (Windows) ORACLE_COMMON_HOME\jlib\cloningclient.jar
If you run the pasteBinary script from a different location than ORACLE_COMMON_HOME
/bin
, 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_home/bin
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.
The following topics describe the syntax of the movement scripts. The options are described in the tables that follow the syntax.
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
If any argument passed to a movement script contains an equals sign (=), the value must be enclosed in double quotation marks ("). For example:
-additionalParam "search.encrypt.key=C:\T2P\encrypt.txt"
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_HOME/wlserver_n/.product.properties
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 copyBinary script is located in:
(UNIX) ORACLE_COMMON_HOME/bin/copyBinary.sh (Windows) ORACLE_COMMON_HOME\bin\copyBinary.cmd
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 /scratch/Oracle/Middleware1/jrockit_160_20_D1.1.0-18 -archiveLoc /tmp/mw_copy.jar -sourceMWHomeLoc /scratch/Oracle/Middleware1 -invPtrLoc /scratch/oracle/oraInst.loc
Note:
Before you execute the copyBinary script, ensure that all Oracle homes in the Middleware home are either all 32 bit or all 64 bit. The operation does not support a mix of 32-bit and 64-bit Oracle homes.
When you execute the script, 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.
Table 20-3 describes the options for the copyBinary script.
Table 20-3 Options for the copyBinary Script
Options | Shortcut | Description | Mandatory or Optional |
---|---|---|---|
-javaHome |
NA |
The absolute path of the Java Developer's Kit. The script detects if the operating system is 64 bit and passes the -d64 option to the scripts in the command line. |
Mandatory |
-archiveLoc |
-al |
The absolute path of the archive location. Use this option to specify the location of the archive file to be created with the copyBinary script. The archive location must not exist, but its parent directory must exist and have write permission. Ensure that the archive location is not within the Middleware home structure. |
Mandatory |
-sourceMWHomeLoc |
-smw |
The absolute path of the Middleware home to be archived. You can only specify one Middleware home. |
Mandatory |
-invPtrLoc |
-ipl |
On UNIX and Linux, the absolute path to the Oracle Inventory pointer. Use this option if the inventory location is not in the default location, so that the operation can read the Oracle homes specified in the inventory. The file, oraInst.loc, must exist. If it does not exist, create it as a root user or user with normal privileges. The following shows an example of the contents of the file: inventory_loc=/scratch/oraInventory You must have write permission to the inventory location. On UNIX and Linux, the default location is /etc/oraInst.loc. On Windows, if you specify this parameter, the script ignores it. In previous releases, the shortcut was -invLoc, but that shortcut is now deprecated. |
Optional, if the inventory is in the default location. Otherwise, it is mandatory on Linux. |
-logDirLoc |
-ldl |
The location of an existing directory. A new log file is created in the directory. The default is the system Temp location. |
Optional |
-silent |
NA |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation. The default is that the operation prompts for confirmation. To continue, you must type To specify that it does not prompt for confirmation, specify this option with the value of |
Optional |
-ignoreDiskWarning |
-idw |
Specifies whether the operation ignores a warning that there is not enough free space available. The default is false. You may need to use this flag if the target is NFS mounted or is on a different file system, such as Data ONTAP. |
Optional |
Applies the archive to the target destination, by pasting the binary files of the source Middleware home to the target environment. You can apply the archive to the same host or a different host.
The pasteBinary script is located in:
(UNIX) ORACLE_COMMON_HOME/bin/pasteBinary.sh (Windows) ORACLE_COMMON_HOME\bin\pasteBinary.cmd
The syntax is:
pasteBinary -javaHome path_of_jdk -archiveLoc archive_location -targetMWHomeLoc target_MW_Home_location [-executeSysPrereqs {true | false}] [-invPtrLoc Oracle_InventoryLocation] [-logDirLoc log_dir_path] [-silent {true | false}] [-ignoreDiskWarning {true | false}]
The following example shows how to apply the archive to the directory /scratch/oracle/MW_Home_prod, on Linux:
pasteBinary.sh -javaHome /scratch/Oracle/Middleware1/jrockit_160_20_D1.1.0-18 -archiveLoc /tmp/mw_copy.jar -targetMWHomeLoc /scratch/oracle/MW_Home_prod
Table 20-4 describes the options for the pasteBinary script.
Table 20-4 Options for the pasteBinary Script
Options | Shortcut | Description | Mandatory or Optional |
---|---|---|---|
-javaHome |
NA |
The absolute path of the Java Developer's Kit. If the source Middleware home was installed with the JDK and Oracle JRockit outside of the Middleware home, the path you specify is used to configure the Middleware home. The script detects if the operating system is 64 bit and passes the -d64 option to the scripts in the command line. |
Mandatory |
-archiveLoc |
-al |
The absolute path of the archive location. Use this option to specify the location of the archive file created with the copyBinary script. The location must exist. In previous releases, this option was named archiveLocation, but that name is now deprecated. |
Mandatory |
-targetMWHomeLoc |
-tmw |
The absolute path of the target Middleware home. Ensure that the Middleware home directory does not exist at that location. If it does exist, the script returns an error message. The targetMWHomeLoc cannot be inside another Middleware home. In previous releases, this option was named targetLocation and the shortcut was -tl, but those are now deprecated. |
Mandatory |
-executeSysPrereqs |
-esp |
Specifies whether the pasteBinary operation checks the prerequisites of the Oracle homes. The default is that it checks the prerequisites. To specify that it does not check the prerequisites, specify this option with the value In previous releases, the shortcut was -exsysprereqs, but that shortcut is now deprecated. |
Optional |
-invPtrLoc |
-ipl |
On UNIX and Linux, the absolute path to the Oracle Inventory pointer. Use this option if the inventory location is not in the default location, so that the operation can read the Oracle homes specified in the inventory. The file, oraInst.loc, must exist. If it does not exist, create it as a root user or user with normal privileges. The following shows an example of the contents of the file: inventory_loc=/scratch/oraInventory You must have write permission to the inventory location. On UNIX and Linux, the default location is /etc/oraInst.loc. On Windows, if you specify this parameter, the script ignores it. In previous releases, the shortcut was -invLoc, but that shortcut is now deprecated. |
Optional, if the inventory is in the default location. Otherwise, it is mandatory on Linux. |
-logDirLoc |
-ldl |
The location of an existing directory. A new log file is created in the directory. The default is the system Temp location. |
Optional |
-silent |
NA |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation. The default is that the operation prompts for confirmation. To continue, you must type To specify that it does not prompt for confirmation, specify this option with the value of |
Optional |
-ignoreDiskWarning |
-idw |
Specifies whether the operation ignores a warning that there is not enough free space available. The default is false. You may need to use this flag if the target is NFS mounted or is on a different file system, such as Data ONTAP. |
Optional |
Creates a configuration archive that contains the snapshot of the configuration of an Oracle WebLogic Server domain. The underlying components of an Oracle WebLogic Server domain retain their configuration information in different data stores, such as a file system, Oracle Metadata Services (MDS), LDAP, or a database.
You must run the copyConfig script for each Oracle WebLogic Server domain in the source environment. A configuration archive is created for each source domain.
The Administration Server and all Managed Servers in the domain must be started when you run the script.
The copyConfig script is located in:
(UNIX) ORACLE_COMMON_HOME/bin/copyConfig.sh (Windows) ORACLE_COMMON_HOME\bin\copyConfig.cmd
The syntax is:
copyConfig -javaHome path_of_jdk -archiveLoc archive_location -sourceDomainLoc domain_location -sourceMWHomeLoc Middleware_home_location -domainHostName domain_host_name -domainPortNum domain_port_number -domainAdminUserName domain_admin_username -domainAdminPassword domain_admin_password_file [-mdsDataImport {true | false}] [-additionalParams property1=value1[, property2=value2] [-logDirLoc log_dir_path] [-silent {true | false}]
The following example copies the configuration of a domain containing Java components:
copyConfig.sh -javaHome /scratch/jrockit_160_20_D1.1.0-18 -archiveLoc /tmp/a.jar -sourceDomainLoc /scratch/mw_home1/user_projects/domains/WLS_SOAWC -sourceMWHomeLoc /scratch/work/mw_home1/ -domainHostName myhost.example.com -domainPortNum 7001 -domainAdminUserName weblogic -domainAdminPassword /home/oracle/password -silent true
Table 20-5 describes the options for the copyConfig script for Java components.
Table 20-5 Options for the copyConfig Script for Java Components
Options | Shortcut | Description | Mandatory or Optional |
---|---|---|---|
-javaHome |
NA |
The absolute path of the Java Developer's Kit. The script detects if the operating system is 64 bit and passes the -d64 option to the scripts in the command line. |
Mandatory |
-archiveLoc |
-al |
The absolute path of the archive location. Use this option to specify the location of the archive file to be created by the copyConfig script. |
Mandatory |
-sourceDomainLoc |
-sdl |
The absolute path of the source domain containing the Java component. Note that on Windows, you should not include a backslash at the end of the path. |
Mandatory |
-sourceMWHomeLoc |
-smw |
The absolute path of the source Middleware home. |
Mandatory |
-domainHostName |
-dhn |
The name of the host on which the domain is configured. |
Mandatory |
-domainPortNum |
-dpn |
The port number of the Administration Server for the domain. In previous releases, this option was named domainPortNo, and the shortcut was -domainport, but those are now deprecated. |
Mandatory |
-domainAdminUserName |
-dau |
The name of the administrative user for the domain. In previous releases, the shortcut was -domainuser, but that shortcut is now deprecated. |
Mandatory |
-domainAdminPassword |
-dap |
The absolute path of a secure file containing the password for the administrative user for the domain on the source environment. You must provide a password file, even if you are not changing the configuration. In previous releases, the shortcut was -domainpass, but that shortcut is now deprecated. |
Mandatory |
-mdsDataImport |
-mdi |
Specifies whether to export the application MDS metadata to the archive so that it can be imported into the target. The default is true. Specify false if you do not want to export the application MDS metadata. If this option is set to true, the subsequent pasteConfig script that copies the component to the target imports the application MDS metadata to the target. |
Optional |
-logDirLoc |
-ldl |
The location of an existing directory. A new log file is created in the directory. The default is the system Temp location. |
Optional |
-additionalParams |
-ap |
An additional parameter and its value to be passed to the script. |
Optional |
-silent |
NA |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation. The default is that the operation prompts for confirmation. To continue, you must type To specify that it does not prompt for confirmation, specify this option with the value of |
Optional |
Creates a configuration archive that contains the snapshot of the configuration of an Oracle instance. The copyConfig script moves the Oracle instance and the configuration of all the system components in the Oracle instance.
You must run the copyConfig script for each Oracle instance in the source environment. A configuration archive is created for each Oracle instance.
The Administration Server and all Managed Servers in the domain must be started when you run the script.
The copyConfig script is located in:
(UNIX) ORACLE_COMMON_HOME/bin/copyConfig.sh (Windows) ORACLE_COMMON_HOME\bin\copyConfig.cmd
The syntax is:
copyConfig -javaHome path_of_jdk -archiveLoc archive_location -sourceInstanceHomeLoc src_instance_path [-logDirLoc log_dir_path] [-silent {true | false}]
The following example shows how to create an archive of the Oracle instance located in /scratch/Oracle/Middleware/im_1 on Linux:
copyConfig.sh -javaHome /scratch/Oracle/Middleware1/jrockit_160_20_D1.1.0-18 -archiveLoc /tmp/ovd1.jar -sourceInstanceHomeLoc /scratch/Oracle/Middleware1/im_1
Table 20-6 describes the options for the copyConfig script for Oracle instances. It also describes the options for the copyConfig Script for individual system components. the only difference is that you use the -sourceComponentName option to move individual system components.
Table 20-6 Options for the copyConfig Script for Oracle Instances and System Components
Options | Shortcut | Description | Mandatory or Optional |
---|---|---|---|
-javaHome |
NA |
The absolute path of the Java Developer's Kit. The script detects if the operating system is 64 bit and passes the -d64 option to the scripts in the command line. |
Mandatory |
-archiveLoc |
-al |
The absolute path of the archive location. Use this option to specify the location of the archive file to be created by the copyConfig script. In previous releases, this option was named archiveLocation, but that name is now deprecated. |
Mandatory |
-sourceInstanceHomeLoc |
-sih |
The absolute path of the Oracle instance for the source component. |
Mandatory |
-additionalParams |
-ap |
An additional parameter and its value to be passed to the script. |
Optional |
-logDirLoc |
-ldl |
The location of an existing directory. A new log file is created in the directory. The default is the system Temp location. |
Optional |
-silent |
NA |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation. The default is that the operation prompts for confirmation. To continue, you must type To specify that it does not prompt for confirmation, specify this option with the value of |
Optional |
-sourceComponentName |
-scn |
The name of the component to be copied. For example, if your Oracle Internet Directory component is named oid1, specify oid1. |
Optional. Use if you want to move only one system component, as described in Section 20.3.1.5. |
Creates a configuration archive that contains the snapshot of the configuration of an Oracle instance and the specified individual system component, which retains its configuration information in different data stores, such as a file system, Oracle Metadata Services (MDS), LDAP, or a database.
Use this script instead of copyConfig for Oracle instances, if you want to move only one system component, along with the Oracle instance to the target environment.
The copyConfig script supports moving the following system components:
Oracle HTTP Server
Oracle Internet Directory
Oracle Virtual Directory
Oracle BI EE
The Administration Server and all Managed Servers in the domain must be started when you run the script.
The copyConfig script is located in:
(UNIX) ORACLE_COMMON_HOME/bin/copyConfig.sh (Windows) ORACLE_COMMON_HOME\bin\copyConfig.cmd
The syntax is:
copyConfig -javaHome path_of_jdk -archiveLoc archive_location -sourceInstanceHomeLoc src_instance_path -sourceComponentName src_component_name [-logDirLoc log_dir_path] [-silent {true | false}]
The following example shows how to create an archive of the Oracle Virtual Directory instance named ovd1 in the Oracle instance located in /scratch/Oracle/Middleware/im_1 on Linux:
copyConfig.sh -javaHome /scratch/Oracle/Middleware1/jrockit_160_20_D1.1.0-18 -archiveLoc /tmp/ovd1.jar -sourceInstanceHomeLoc /scratch/Oracle/Middleware1/im_1 -sourceComponentName ovd1
See Table 20-6 for description of the options for the copyConfig script for system components.
Creates a configuration archive that contains the snapshot of the configuration of Node Manager.
You must run the copyConfig script for each Node Manager in the source environment. A configuration archive is created for each source Node Manager.
The copyConfig script is located in:
(UNIX) ORACLE_COMMON_HOME/bin/copyConfig.sh (Windows) ORACLE_COMMON_HOME\bin\copyConfig.cmd
The syntax is:
copyConfig -javaHome path_of_jdk -archiveLoc archive_location -sourceNMHomeLoc source_Node_Manager_Home_location [-logDirLoc log_dir_path] [-silent {true | false}]
The following example shows how to create a copy of the source Node Manager configuration located in /scratch/Oracle/Middleware/wlserver_10.3/common/nodemanager:
copyConfig.sh -javaHome USER_HOME/jrockit_160_17_R28.0.0-679/
-archiveLoc /tmp/nm.jar
-sourceNMHomeLoc /scratch/Oracle/Middleware/wlserver_10.3/common/nodemanager
-silent true
Table 20-7 describes the options for the copyConfig script for Node Manager.
Table 20-7 Options for the copyConfig Script for Node Manager
Options | Shortcut | Description | Mandatory or Optional |
---|---|---|---|
|
None |
The absolute path of the Java Developer's Kit. The script detects if the operating system is 64 bit and passes the -d64 option to the scripts in the command line. |
Mandatory |
|
|
The absolute path of the archive location. Use this option to specify the location of the archive file to be created by the copyConfig script. |
Mandatory |
|
|
The absolute path of the source Node Manager home. |
Mandatory |
|
|
The location of an existing directory. A new log file is created in the directory. The default is the system Temp location. |
Optional |
|
None |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation. The default is that the operation prompts for confirmation. To continue, you must type To specify that it does not prompt for confirmation, specify this option with the value of |
Optional |
Extracts configuration information from the archive into a move plan. It also extracts any needed configuration plans. Then, you edit the move plan, specifying properties for the target environment.
The extractMovePlan script is located in:
(UNIX) ORACLE_COMMON_HOME/bin/extractMovePlan.sh (Windows) ORACLE_COMMON_HOME\bin\extractMovePlan.cmd
The syntax is:
extractMovePlan -javaHome path_of_jdk -archiveLoc archive_location -planDirLoc move_plan_directory [-logDirLoc log_dir_path]
The following example extracts the plans from the archive j2ee.jar:
extractMovePlan.sh -javaHome /scratch/Oracle/Middleware1/jrockit_160_20_D1.1.0-18 -archiveLoc /tmp/j2ee.jar -planDirLoc /scratch/Oracle/t2p_plans
The extractMovePlan script extracts the move plan to the specified directory. Depending on the type of component that you are moving, the extractMovePlan script may also extract other configuration plans.
For Java components, such as Oracle SOA Suite, it may extract the following:
/scratch/Oracle/t2p_plans/moveplan.xml /scratch/Oracle/t2p_plans/composites/configplan1.xml /scratch/Oracle/t2p_plans/composites/configplan2.xml /scratch/Oracle/t2p_plans/adapters/deploymentplan1.xml /scratch/Oracle/t2p_plans/adapters/deploymentplan2.xml
For system components, such as Oracle Internet Directory and Oracle Virtual Directory, it may extract the following:
/scratch/Oracle/t2p_plans/moveplan.xml
Table 20-8 describes the options for the extractMovePlan script:
Table 20-8 Options for the extractMovePlan Script
Options | Shortcut | Description | Mandatory or Optional |
---|---|---|---|
-javaHome |
NA |
The absolute path of the Java Developer's Kit. The script detects if the operating system is 64 bit and passes the -d64 option to the scripts in the command line. |
Mandatory |
-archiveLoc |
-al |
The absolute path of the archive location. Use this option to specify the location of the archive file created by the copyConfig script. |
Mandatory |
-planDirLoc |
-pdl |
The absolute path to a directory to which the move plan, along with any needed configuration plans, is to be extracted. The directory must not exist. |
Mandatory |
-logDirLoc |
-ldl |
The location of an existing directory. A new log file is created in the directory. The default is the system Temp location. |
Optional |
For information about the properties in the move plans, and which properties you should edit, see Section 20.4.
Applies the copied configurations from the source environment to the target environment. Inputs for the script include the location of the configuration archive created with the copyConfig script for the Java components and the location of the modified move plan. The pasteConfig script re-creates the configuration information for the Oracle WebLogic Server domain in the target environment. It also merges the move plan property values for the target environment.
The pasteConfig script is located in:
(UNIX) ORACLE_COMMON_HOME/bin/pasteConfig.sh (Windows) ORACLE_COMMON_HOME\bin\pasteConfig.cmd
The syntax is:
pasteConfig -javaHome path_of_jdk -archiveLoc archive_location -targetDomainLoc trgt_domain_path -targetMWHomeLoc trgt_Middleware_Home_path -movePlanLoc move_plan_path -domainAdminPassword domain_admin_password_file [-appDir WLS_application_directory] [-logDirLoc log_dir_path] [-silent {true | false}]
The following example shows how to apply the archive of the domain to the Middleware home MW_home1:
pasteConfig.sh -javaHome /scratch/Oracle/Middleware1/jrockit_160_20_D1.1.0-18 -archiveLoc /tmp/java_ee_cl.jar -targetDomainLoc /scratch/oracle/MW_home1/user_projects/domains/dom_cl -targetMWHomeLoc /scratch/oracle/MW_home1 -movePlanLoc /scratch/oracle/java_ee/move_plan.xml -domainAdminPassword /scratch/pwd_dir/pass -logDirLoc /tmp/log
Table 20-9 describes the options for the pasteConfig script for Java components.
Table 20-9 Options for the pasteConfig Script for Java Components
Options | Shortcut | Description | Mandatory or Optional |
---|---|---|---|
-javaHome |
NA |
The absolute path of the Java Developer's Kit. The script detects if the operating system is 64 bit and passes the -d64 option to the scripts in the command line. |
Mandatory |
-archiveLoc |
-al |
The absolute path of the archive location. Use this option to specify the location of the archive file created by the copyConfig script. |
Mandatory |
-targetDomainLoc |
-tdl |
The absolute path of the target domain. The domain location must not exist for the specified Middleware home. The domain directory may be located outside of the directory structure of the Middleware home. |
Mandatory |
-targetMWHomeLoc |
-tmw |
The absolute path of the target Middleware home in which the domain is to be copied. |
Mandatory |
-movePlanLoc |
-mpl |
The absolute path of the move plan extracted from the source. |
Mandatory |
-domainAdminPassword |
-dap |
The absolute path of a secure file containing the password for the administrative user for the domain on target environment. You must provide a password file, even if you are not changing the configuration. Note that the password is based on the authentication provider for the domain. For example, the authenticator can be an embedded LDAP or an external LDAP. In previous releases, the shortcut was -domainpass, but that shortcut is now deprecated. |
Mandatory. |
-appDir |
-ad |
The absolute path of the Oracle WebLogic Server application directory on the target. |
Optional |
-logDirLoc |
-ldl |
The location of an existing directory. A new log file is created in the directory. The default is the system Temp location. |
Optional |
-silent |
NA |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation. The default is that the operation prompts for confirmation. To continue, you must type To specify that it does not prompt for confirmation, specify this option with the value of |
Optional |
Applies the copied configurations from the source environment to the target environment. Inputs for the script include the location of the configuration archive created with the copyConfig script for the Oracle instance and the location of the modified move plan. The pasteConfig script iterates and re-creates the configuration information for the Oracle instance and all of its system components in the target environment. It also merges the move plan property values for the target environment.
The syntax is:
pasteConfig -javaHome path_of_jdk -archiveLoc archive_location -movePlanLoc move_plan_path -targetInstanceHomeLoc trgt_Instance_path [-targetInstanceName trgt_Instance_name] [-targetOracleHomeLoc trgt_ORACLE_HOME_path] [-logDirLoc log_dir_path] [-silent {true | false}] [ <Domain Detail> ] <Domain Detail> = -domainHostName domain_host_name -domainPortNum domain_port_number -domainAdminUserName domain_admin_username -domainAdminPassword domain_admin_password_file
The following example shows how to apply the archive to the target and name the Oracle instance im_2:
pasteConfig.sh -javaHome /scratch/Oracle/Middleware/jrockit_160_20_D1.1.0-18 -archiveLoc /tmp/ovd1.jar -movePlanLoc /scratch/oracle/ovd/move_plan.xml -targetOracleHomeLoc /scratch/Oracle/Middleware/Oracle_IM2 -targetInstanceHomeLoc /scratch/Oracle/Middleware/im_2 -targetInstanceName im_2 -domainHostName myhost -domainPortNum 7001 -domainAdminUserName domain_admin_username -domainAdminPassword domain_admin_password_file
Table 20-10 describes the options for the pasteConfig script for system components. It also describes the options for the pasteConfig Script for individual system components. The only difference is that you use the -sourceComponentName option to move individual system components.
Table 20-10 Options for the pasteConfig Script for Oracle Instances
Options | Shortcut | Description | Mandatory or Optional |
---|---|---|---|
-javaHome |
NA |
The absolute path of the Java Developer's Kit. The script detects if the operating system is 64 bit and passes the -d64 option to the scripts in the command line. |
Mandatory |
-archiveLoc |
-al |
The absolute path of the archive location. Use this option to specify the location of the archive file created by the copyConfig script. |
Mandatory |
-movePlanLoc |
-mpl |
The absolute path of the move plan extracted from the source. |
Mandatory |
-targetInstanceHomeLoc |
-tih |
The absolute path of the target Oracle instance. If the Oracle instance directory does not exist at that location, the script creates the directory. |
Mandatory |
-targetInstanceName |
-tin |
The name of the target Oracle instance, which is used to register the instance with the domain. The name must be unique in the domain. |
Optional, if the targetInstanceHomeLoc directory exists. In this case, the operation retrieves the name from the configuration. |
-targetComponentName |
-tcn |
The name of the target component to be copied. The name must be unique in the instance. |
Optional. Use if you want to move only one system component, as described in Section 20.3.1.5. |
-targetOracleHomeLoc |
-toh |
The absolute path of the target Oracle home. The target Oracle home must exist and it must contain the binaries for the component you are copying. |
Optional, if the targetInstanceHomeLoc exists. In this case, the operation retrieves the value from the configuration. |
-logDirLoc |
-ldl |
The location of an existing directory. A new log file is created in the directory. The default is the system Temp location. |
Optional |
-silent |
NA |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation. The default is that the operation prompts for confirmation. To continue, you must type To specify that it does not prompt for confirmation, specify this option with the value of |
Optional |
Domain-Detail Options |
|||
-domainHostName |
-dhn |
The name of the host on which the domain is configured. Use this option if you want to register the component with the domain. In previous releases, the shortcut was -domainhost, but that shortcut is now deprecated. |
Optional, if you do not want to register the component with the domain. |
-domainPortNum |
-dpn |
The port number of the domain. Use this option if you want to register the component with the domain. The domain port number is listed in the following file as the adminPort:
ORACLE_INSTANCE/config/OPMN/opmn/instance.properties
For example: |
Optional, if you do not want to register the component with the domain. |
-domainAdminUserName |
-dau |
The name of the administrative user for the domain. Use this option if you want to register the component with the domain. |
Optional, if you do not want to register the component with the domain. |
-domainAdminPassword |
-dap |
The absolute path of a secure file containing the password for the administrative user for the domain. You must provide a password file, even if you are not changing the configuration. Use this option if you want to register the component with the domain. |
Optional, if you do not want to register the component with the domain. |
Applies the copied configurations for individual system components from the source environment to the target environment. Inputs for the script include the location of the configuration archive created with the copyConfig script for the Oracle instance and the location of the modified move plan. The pasteConfig script re-creates the configuration information for the Oracle instance and the specified system component in the target environment. It also merges the move plan property values for the target environment.
The copyConfig script supports moving the following system components:
Oracle HTTP Server
Oracle Internet Directory
Oracle Virtual Directory
Oracle BI EE
The syntax is:
pasteConfig -javaHome path_of_jdk -archiveLoc archive_location -movePlanLoc move_plan_path -targetComponentName trgt_component_name -targetInstanceHomeLoc trgt_Instance_path [-targetInstanceName trgt_Instance_name] [-targetOracleHomeLoc trgt_ORACLE_HOME_path] [-logDirLoc log_dir_path] [-silent {true | false}] [ <Domain Detail> ] <Domain Detail> = -domainHostName domain_host_name -domainPortNum domain_port_number -domainAdminUserName domain_admin_username -domainAdminPassword domain_admin_password_file
The following example shows how to apply the archive to the Oracle instance im_2 and to name the target Oracle Virtual Directory instance ovd_cl:
pasteConfig.sh -javaHome /scratch/Oracle/Middleware/jrockit_160_20_D1.1.0-18 -archiveLoc /tmp/ovd1.jar -movePlanLoc /scratch/oracle/ovd/move_plan.xml -targetOracleHomeLoc /scratch/Oracle/Middleware/Oracle_IM2 -targetInstanceHomeLoc /scratch/Oracle/Middleware/im_2 -targetInstanceName im_2 -targetComponentName ovd_cl -domainHostName myhost -domainPortNum 7001 -domainAdminUserName domain_admin_username -domainAdminPassword domain_admin_password_file
See Table 20-10 for descriptions of the options for the pasteConfig script for system components.
Applies the copied configurations of Node Manager from the source environment to the target environment. Inputs for the script include the location of the configuration archive created with the copyConfig script for the Oracle WebLogic Server Node Manager and the location of the modified move plan. The pasteConfig script re-creates the configuration information for Node Manager in the target environment. It also merges the move plan property values for the target environment.
Note:
All the domains that are to be managed by Node Manager should be moved before applying the copy of Node Manager to the target environment. In addition, the Administration Server must be running.
Even if the source Node Manager connection between the Administration Server and Node Manager is configured with SSL, they will both change to plain socket connection type after the copy of Node Manager is applied to the target environment.
You must run the pasteConfig script for each Node Manager in the source environment.
The syntax is:
pasteConfig -javaHome path_of_jdk -archiveLoc archive_location -targetNMHomeLoc trgt_Node_Manager_Home_path -targetMWHomeLoc trgt_Middleware_Home_path -movePlanLoc move_plan_path [-logDirLoc log_dir_path] [-silent {true | false}]
The following example shows how to apply the copy of Node Manager to the Node Manager home located in /scratch/Oracle/Middleware1/wlserver_10.3/common/nodemanager:
pasteConfig -javaHome USER_HOME/jrockit_160_17_R28.0.0-679/
-archiveLoc /tmp/nm.jar
-targetNMHomeLoc /scratch/Oracle/Middleware1/wlserver_10.3/common/nodemanager
-targetMWHomeLoc /scratch/Oracle/Middleware1
-movePlanLoc /scratch/oracle/t2pplans/nm/moveplan.xml
-silent true
Table 20-11 describes the options for the pasteConfig script for Node Manager.
Table 20-11 Options for the pasteConfig Script for Node Manager
Options | Shortcut | Description | Mandatory or Optional |
---|---|---|---|
|
None |
The absolute path of the Java Developer's Kit. The script detects if the operating system is 64 bit and passes the -d64 option to the scripts in the command line. |
Mandatory |
|
|
The absolute path of the archive location. Use this option to specify the location of the archive file created by the copyConfig script. |
Mandatory |
|
|
The absolute path of the target Node Manager. |
Mandatory |
|
|
The absolute path of the target Middleware home in which the copy of Node Manager is to be applied. |
Mandatory |
|
|
The absolute path of the modified move plan in the target environment. |
Mandatory |
|
|
The location of an existing directory. A new log file is created in the directory. The default is the system Temp location. |
Optional |
|
None |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation. The default is that the operation prompts for confirmation. To continue, you must type To specify that it does not prompt for confirmation, specify this option with the value of |
Optional |
Generates a file that contains the obfuscated password. In the scripts and in the move plans, you often need to provide files containing passwords. The script prompts you to enter the password and the location where the password file is to be written.
The syntax is:
(UNIX) ORACLE_COMMON_HOME/bin/obfuscatePassword.sh (Windows) ORACLE_COMMON_HOME\bin\obfuscatePassword.cmd
When you move Oracle Fusion Middleware components, you run the extractMovePlan script to create a move plan for the entity that you are moving. The extractMovePlan script extracts configuration information from the archive into a move plan. It also extracts any needed configuration plans. Before you apply the archive to the target, you must edit the move plan to reflect the values of the target environment.
You can modify properties with the scope of READ_WRITE. Do not modify the properties with the scope of READ_ONLY.
Note:
Do not add, comment, or remove any section of a move plan.
This section provides the following topics:
Most move plans contain multiple configGroup elements. When a property is associated with a particular configGroup element, the tables listing the properties group the properties by configGroup element. For example, Table 20-14, which shows the properties for the move plan for Java components, shows multiple configGroup elements, such as SERVER_CONFIG and MACHINE_CONFIG.
The following example shows a portion of the move plan for Java components, with portions of the SERVER_CONFIG and MACHINE_CONFIG configGroup elements:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <movePlan> <movableComponent> <componentType>J2EEDomain</componentType> <moveDescriptor> <StartupMode>PRODUCTION</StartupMode> <configGroup> <type>SERVER_CONFIG</type> <configProperty id="Server1"> <configProperty> <name>Server Name</name> <value>AdminServer</value> <itemMetadata> <dataType>STRING</dataType> <scope>READ_ONLY</scope> </itemMetadata> </configProperty> . . . </configGroup> <configGroup> <type>MACHINE_CONFIG</type> <configProperty id="Machine1"> <configProperty> <name>Machine Name</name> <value>LocalMachine</value> <itemMetadata> <dataType>STRING</dataType> <scope>READ_WRITE</scope> </itemMetadata> </configProperty> <configProperty> <name>Node Manager Listen Address</name> <value>example.com</value> <itemMetadata> <dataType>STRING</dataType> <scope>READ_WRITE</scope> </itemMetadata> </configProperty> . . . </configGroup>
The tables in this section describe the move plan properties you can customize for Oracle Fusion Middleware entities and components.
Note:
Many move plan properties require that you provide the location of a file containing a password. If you want to use obfuscated passwords, you can use the obfuscatePassword script, as described in Section 20.3.1.12.
The properties that you edit differ depending on the type of component. Table 20-12 provides pointers to the appropriate list of properties for each component.
Table 20-12 Move Plan Properties for Components
Component | Where to find the list of properties: |
---|---|
Node Manager |
|
All Java components |
|
Oracle Access Management Access Manager |
|
Oracle Access Management Identity Federation |
|
Oracle Access Management Mobile and Social |
|
Oracle Access Management Secure Token Service |
|
Oracle Adaptive Access Manager |
|
Oracle ADF connections |
|
Oracle B2B |
|
Oracle BI EE |
Table 20-14, Table 20-15, Table 20-23, and optionally Table 20-24, Table 20-25, Table 20-26, Table 20-27 |
Oracle BI Publisher |
|
Oracle Data Integrator |
|
Oracle HTTP Server |
|
Oracle Internet Directory |
|
Oracle Identity Manager |
|
Oracle SOA Suite |
|
Oracle Virtual Directory |
|
Oracle WebCenter Content Server |
|
Oracle WebCenter Content: Imaging |
|
Oracle WebCenter Content: Inbound Refinery: |
|
Oracle WebCenter Content: Records |
Table 20-13 describes the move plan properties that you can change for Node Manager. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-13 Move Plan Properties for Node Manager
Property | Description | Sample Value |
---|---|---|
Properties in the NODE_MANAGER_PROPERTIES configGroup: |
Node Manager configuration |
|
Listen Address |
The Listen address of Node Manager. |
example.com |
Listen Port |
The number of the Listen port of Node Manage. |
5557 |
Custom Identity KeyStore File |
The absolute path of the custom identity keystore file location. This property is present in the move plan only if the source environment is configured with SSL. |
/scratch/Oracle/Middleware/wlserver_10.3/server/lib/example_identity.jks |
Custom Identity Private Key Alias |
The value of the identity key store alias. This property is present in the move plan only if the source environment is configured with SSL. |
mykey |
Custom Identity Private Key Passphrase File |
The absolute path to the secure file containing the private key used when creating a certificate. This property is present in the move plan only if the source environment is configured with SSL. |
/scratch/oracle/key_passwd |
Properties in the DOMAINS configGroup: |
Oracle WebLogic Server domain configuration |
|
Domain Name |
The name of the domain. |
SOA_domain |
Domain Location |
The absolute path of the domain location. |
/scratch/Oracle/Middleware/user_projects/domains/SOA_domain |
AdminServer Listen Address |
The Listen address of the Administration Server. |
example.com |
AdminServer Listen Port |
The number of the Listen port of the Administration Server. |
7001 |
AdminServer User Name |
The administration user name. |
weblogic |
AdminServer Password |
The absolute path to the secure file containing the administration user's password. |
/scratch/oracle/admin_passwd |
Node Manager User Name |
The Node Manager user name. |
weblogic |
Node Manager Password |
The absolute path to the secure file containing the Node Manager user's password. |
/scratch/oracle/nm_passwd |
Table 20-14 describes the move plan properties that you can change for Java components. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-14 Common Move Plan Properties for Java Components
Property | Description | Sample Value |
---|---|---|
Startup Mode |
The startup mode of an Oracle WebLogic Server domain. Valid values are:
The default is PRODUCTION. |
PRODUCTION |
Properties in the SERVER_CONFIG configGroup: |
Common Java properties |
|
Listen Address |
The Listen address of the WebLogic Server. Set it to the host name or set it to |
All Local Addresses |
Listen Port |
The number of the Listen port. If you do not provide a port number or if the port number you provide is not available, the operation returns an error. |
8001 |
SSL Listen Port |
The number of the SSL Listen port. This property is present in the move plan if SSL is enabled. |
7002 |
Frontend Host |
The host name of the HTTP Server. This property is present in the move plan only if the HTTP Server is set as the frontend to the server. |
example.com |
Frontend HTTP Port |
The number of the HTTP Server port. This property is present in the move plan only if the HTTP Server is set as the frontend to the server. |
10605 |
Custom Identity Keystore File |
The absolute path of custom identity keystore file location. |
/scratch/Oracle/Middleware/wlserver_10.3/server/lib/example_identity.jks |
Custom Identity Keystore Passphrase File |
The absolute path to the secure file containing the custom identity keystore password. |
/scratch/oracle/i_passwd |
Custom Trust Keystore File |
The absolute path of custom trust keystore file location. |
/scratch/Oracle/Middleware/wlserver_10.3/server/lib/example_trust.jks |
Custom Trust Keystore Passphrase File |
The absolute path to the secure file containing the custom trust keystore password. |
/scratch/oracle/key_passwd |
Custom Identity Private Key Alias |
The private key alias. |
fmw_key |
Custom Identity Private Key Passphrase File |
The absolute path to the secure file containing the custom identity private key password. |
/scratch/oracle/i_passwd |
Properties in the CLUSTER_CONFIG configGroup: |
Oracle WebLogic Server Cluster configuration properties |
|
Messaging Mode |
The cluster messaging mode. Acceptable values are |
multicast |
Cluster Address |
The cluster address. |
localhost |
Unicast Channel |
The name of the unicast channel. |
MyMulticastChannel |
Multicast Address |
The multicast address. |
239.192.0.0 |
Multicast Port |
The port number of the multicast address. |
8899 |
Frontend Host |
The name or IP address of the front-end host for the cluster. |
example.com |
Frontend HTTP Port |
The HTTP port number for the front-end host for the cluster. |
7008 |
Properties in the MACHINE_CONFIG configGroup: |
Machine configuration properties |
|
Machine Name |
The name of the machine. |
example.com |
Node Manager Listen Address |
The Listen address of the machine running Node Manager. |
example.com |
Node Manager Listen Port |
The port number of the Listen address of the machine running Node Manager. |
5556 |
Property in the DEPLOYMENT_PLAN_CONFIG configGroup: |
Deployment plans |
|
Deployment Plan |
The location where an application's deployment plan is to be extracted. The location is relative to the location of the move plan. |
deploy_plans/helloWorldEar_plan.xml |
Properties in the AUTHENTICATORS configGroup: |
Authenticator configuration |
|
Host Name |
The LDAP server host name. |
example.com |
Port |
The LDAP server port number. |
3060 |
Principal |
The administration user for the LDAP server. |
cn=orcladmin |
Password File |
The absolute path of a secure file containing the password for the LDAP user. You must provide a password file, even if you are not changing the configuration. |
/scratch/oracle/ldap_passwd |
User Base DN |
The user base distinguished name (DN). |
cn=users,dc=us,dc=oracle,dc=com |
User Object Class |
The user object class. |
person |
Group Base DN |
The group base distinguished name (DN). |
cn=groups,dc=us,dc=oracle,dc=com |
GUID Attribute |
The global unique identifier. |
orclguid |
Properties in the DATASOURCE configGroup: |
Data source configuration |
|
Driver Class |
The driver class of the data source. Refer to "Using JDBC Drivers with WebLogic Server" in the Oracle Fusion Middleware Configuring and Managing JDBC Data Sources for Oracle WebLogic Server to choose the appropriate class. |
oracle.jdbc.OracleDriver |
Url |
The URL of the database for the data source. It has the following format: jdbc:oracle:thin:@Db_host:Db_port:Db_SID |
jdbc:oracle:thin:@host.example.com:1521:orcl |
User |
The schema name of the data source. |
OFM_MDS |
Password File |
The absolute path to the secure file containing the password of the database schema. You must provide a password file, even if you are not changing the configuration of the data source. |
/scratch/oracle/ds_passwd |
Properties in the OPSS_SECURITY configGroup, in the configProperty with the ID of LDAP. |
LDAP-based policy and credential store configuration. If the source is a file-based store, these properties, as well as the LDAP-based and Database-Based Policy and Credential Store properties are present in the move plan. When you configure the move plan, you can change from a file-based to an LDAP or database-based store. If the source is LDAP-based, only the LDAP properties are present in the move plan. You cannot change it to a different type, but you can change the LDAP endpoints. If the source is database-based, only the database properties are present in the move plan. You cannot change it to a different type, but you can change the database-based endpoints. You can only use one type of store. To use one, uncomment the section in the move plan and ensure the other is commented. |
|
Password File |
The absolute path to the secure file containing the password of the LDAP Server Administrative user. You must provide a password file, even if you are not changing the configuration of the LDAP Server. |
/scratch/oracle/ldap_passwd |
LDAP User |
The LDAP Server administrative user name. |
cn=orcladmin |
Jps Root |
The LDAP Server context root. |
cn=jpsRoot |
Domain |
The name of the domain. |
SOA_domain |
LDAP Url |
The URL of the LDAP connection. It contains the host name and port number of the LDAP store. |
ldap://example.com:3060 |
Properties in the OPSS_SECURITY configGroup, in the configProperty with the ID of DB: |
Database-based policy and credential store configuration. If the source is a database-based store, these properties are present in the move plan. (The LDAP-based store is not present and you cannot move from a database-based to an LDAP-based store.) |
|
Password File |
The absolute path to the secure file containing the password of the OPSS schema owner. You must provide a password file, even if you are not changing the configuration. |
/scratch/oracle/ldap_passwd |
DataSource Name |
The name of the data source. |
opssds |
DataSource Jndi Name |
The JNDI name of the data source. |
jdbc/opss |
Jps Root |
The LDAP Server context root. |
cn=jpsRoot |
Domain |
The name of the domain. |
SOA_domain |
Driver Class |
The driver class of the data source. Refer to "Selecting a JDBC Driver" in the Oracle Fusion Middleware Configuring and Managing JDBC Data Sources for Oracle WebLogic Server to choose the appropriate class. |
oracle.jdbc.OracleDriver |
Url |
The database URL of the data source. It has the following format: jdbc:oracle:thin:@Db_host:Db_port:Db_SID |
jdbc:oracle:thin:@host.example.com:1521:orcl |
User |
The name of the OPSS schema owner of the data source. |
DEV_OPSS |
Properties in the RDBMS Security Store configGroup: |
Database-based security store configuration |
|
URL |
The database URL of the security store connection. It has the following format: jdbc:oracle:thin:@Db_host:Db_port:Db_SID |
jdbc:oracle:thin:@host.example.com:1521:orcl |
Driver Class |
The driver class of the RDBMS Security Store connection. Refer to "Using JDBC Drivers with WebLogic Server" in the Oracle Fusion Middleware Configuring and Managing JDBC Data Sources for Oracle WebLogic Server to choose the appropriate class. |
oracle.jdbc.OracleDriver |
User |
The name of the schema owner. |
admin |
Password File |
The absolute path to the secure file containing the password of the security store schema owner. You must provide a password file, even if you are not changing the configuration. |
/scratch/oracle/rbms_passwd |
Property in the ADAPTER configGroup: |
Resource adapter configuration |
|
Deployment Plan |
The path to the deployment plan to be used during movement to the target. The path can be absolute, or relative to the location of the move plan. The deployment plan is extracted by the extractMovePlan script. |
/scratch/adapters/adapters.xml |
Table 20-15 describes the move plan properties that you can change if you are using Oracle ADF connections. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment. The table is divided by component. For some components, the description column lists the OBJECT_NAME_PROPERTY type. You can search for the type to locate the relevant section.
Table 20-15 Move Plan Properties for Oracle ADF Connections
Property | Description | Sample Value |
---|---|---|
Oracle ADF URL Connection |
OBJECT_NAME_PROPERTY type is URLConnProvider |
|
Port |
The port number used for the URL connections. |
7000 |
URL |
The URL used for the connection. |
example.com |
Oracle ADF Business Components Service Connection |
OBJECT_NAME_PROPERTY type is ADFBCServiceConnection |
|
ServiceEndpointProvider |
The Business Components service endpoint provider. |
ADFBC |
JndiFactoryInitial |
The JNDI initial factory class. |
com.sun.java.jndi.InitialFactory |
JndiProviderUrl |
The URL of the JNDI provider. |
t3://example.com:7101 |
JndiSecurityPrincipal |
The JNDI security principal name. |
weblogic |
WebServiceConnectionName |
The Web service connection name. |
test |
Oracle Enterprise Scheduler |
OBJECT_NAME_PROPERTY type is EssConnection |
|
NotificationServiceURL |
The Oracle Enterprise Scheduler notification service URL. |
http://localhost:8001 |
RequestFileDirectory |
The path of the directory where request logs for jobs from OES ConcurrentProcessor (CP) extension is to be created. |
/tmp/ess/requestFileDirectory |
SAMLTokenPolicyURI |
The SAML Policy URI to be used by CP extension. |
oracle/wss11_saml_token_with_message_protection_service_policy |
EssCallbackClientSecurityPolicyURI |
The security policy to be used in the WS-Security headers for Web service invocations from Oracle Enterprise Scheduler for Web service callbacks. |
oracle/wss11_saml_token_with_message_protection_client_policy |
Oracle Business Activity Monitoring |
||
WEBTIER_SERVER |
The Oracle BAM Web server host. |
example.com |
USER_NAME |
The Oracle BAM user name. |
user |
PASSWORD |
The password for the Oracle BAM user. |
bam_password
|
WEBTIER_SERVER_PORT |
The port number for the Web server. |
9001 |
BAM_SERVER_PORT |
The JNDI port number. |
8001 |
BAM_WEBTIER_PROTOCOL |
The network protocol. The valid values are HTTP and HTTPS. |
HTTP |
BI Presentation Services connection |
OBJECT_NAME_PROPERTY type is BISoapConnection |
|
StaticResourcesLocation |
The location where the browser should fetch Oracle BI EE static resources. |
http://example.com:7001/analytics |
WSDLContext |
The Oracle BI EE context to use when making a Web services call. |
analytics-ws |
Host |
The host where Oracle BI EE is located. |
example.com |
Port |
The port that hosts the BI Presentation Services server. |
10621 |
ShouldPerformImpersonation |
Whether Oracle BI EE should perform impersonation. This should always be set to true. |
true |
Context |
The Oracle BI EE context to use when fetching content. |
analytics |
Protocol |
The protocol to use, depending on whether the Web server is configured with SSL. |
http or https |
IsStaticResourcesLocationAutomatic |
The flag indicating whether to auto-generate the StaticResourcesLocation from the Host, Port, and Context fields. |
true or false |
Oracle Essbase |
OBJECT_NAME_PROPERTY type is EssbaseConnProvider |
|
Host |
The host name for the Oracle Essbase server. |
example.com |
Cluster |
The name of the cluster of which the Oracle Essbase server is a member. |
esbCluster |
Port |
The Listen port number of the Oracle Essbase server. |
1423 |
Username |
The user name. |
user3 |
Oracle Secure Enterprise Search in Oracle WebCenter Portal |
The OBJECT_NAME_PROPERTY type is SesConnectionProvider |
|
SoapURL |
The Web services URL that Oracle SES exposes to enable search requests. |
http:/example.com:port/search/query/OracleSearch
|
Oracle WebCenter Portal Content Repository |
OBJECT_NAME_PROPERTY type is JCR |
|
ServerHost |
The host name of the machine where the Content Server is running. |
example.com |
ServerPort |
The port number on which the Content Server listens. |
4444 |
ServerWebUrl |
The Web server URL for the Content Server. |
http://example.com/cms/idcplg |
Oracle WebCenter Portal Announcements and Discussions |
OBJECT_NAME_PROPERTY type is ForumConnectionProvider |
|
AdminUser |
The name of the discussions server administrator. This account is used by the Discussions and Announcements services to perform administrative operations on behalf of WebCenter Portal users. |
admin |
Url |
The URL of the discussions server hosting discussion forums and announcements. |
http://example.com:8890/owc_discussions |
Oracle WebCenter Portal External Applications |
OBJECT_NAME_PROPERTY type is ExtAppConnectionProvider |
|
Url |
The login URL for the external application. |
https://example.com/config/login? |
Oracle WebCenter Portal Instant Messaging and Presence |
OBJECT_NAME_PROPERTY type is RtcConnectionProvider |
|
BaseConnectionURL |
The URL of the server hosting instant messaging and presence services. |
http://example.com:8888 |
Domain |
The network domain. |
example.com |
ExternalAppId |
The external application ID associated with the Presence server connection. If present, external application credential information is used to authenticate users against the instant messaging and presence server. |
extApp |
Oracle WebCenter Portal Mail Server |
OBJECT_NAME_PROPERTY is MailConnectionProvider |
|
ExternalAppId |
The external application ID associated with the mail server. |
extApp_Mail |
ImapHost |
The host name of the IMAP server. |
example.com |
ImapPort |
The port number of the IMAP server. |
993 |
ImapSecured |
The flag indicating whether the mail server connection to the IMAP server is SSL-enabled. Valid values are true and false. The default is false. |
true |
SmtpHost |
The host name of the computer where the SMTP (Simple Mail Transfer Protocol) service is running. |
example.com |
SmtpPort |
The port number of the SMTP host. |
587 |
SmtpSecured |
The flag indicating whether the SMTP server is secured. Valid values are true and false. The default is false. |
true |
Oracle WebCenter Portal Personal Events |
OBJECT_NAME_PROPERTY type is WebCenterPersonalEventConnectionProvider |
|
ExternalAppId |
The external application associated with the Microsoft Exchange Server providing personal events services. If specified, external application credential information is used to authenticate users against the Microsoft Exchange Server. |
ExtPEApp |
WebServiceURL |
The URL of the Web service exposing the event application. |
http://example.com:80/ExchangeWS/PersonalEventsWebService.asmx |
Oracle WebCenter Portal WSRP Producers |
OBJECT_NAME_PROPERTY type is WSRPProducerConnection |
|
ProxyHost |
The host name or IP address of the proxy server. |
example.com |
ProxyPort |
The port number of the proxy server. |
80 |
Oracle WebCenter Portal PDK-Java Producers |
OBJECT_NAME_PROPERTY type is WebProducerConnection |
|
Host |
The host name of the proxy server to be used for the PDK Java Producer connection. |
example.com |
Port |
The port number to be used for the PDK Java Producer connection. |
80 |
URL |
The URL for the PDK Java Producer connection. |
http:/example.com:port
|
Oracle WebCenter Portal Worklists |
OBJECT_NAME_PROPERTY type is BPEL |
|
URL |
The URL required to access the BPEL server. The BPEL server URL must be unique within the WebCenter application. |
protocol://example:port |
Oracle Web Services |
OBJECT_NAME_PROPERTY type is WebServiceConnection |
|
WsdlUrl |
The URL for the WSDL. |
http://example.com:port/MyWebService1?WSDL
|
Oracle Web Services |
OBJECT_NAME_PROPERTY type is Port |
|
AddressUrl |
The service endpoint URL. |
http://example.com:port/MyWebService1
|
ProxyHost |
The name of the host on which the proxy server is running. |
example.com |
ProxyPort |
The port number to which the proxy server is listening. |
80 |
Table 20-16 describes the move plan properties that you can change for Oracle SOA Suite. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-16 Move Plan Properties for Oracle SOA Suite
Property | Description | Sample Value |
---|---|---|
Property in the Composite configGroup: |
SOA Composites configuration |
|
Config Plan Location |
The location of the configuration plan to be used during movement to the target to redeploy the composite application. The path can be absolute, or relative to the location of the move plan. The plan is extracted during the extractMovePlan script. |
/scratch/app/config_plan.xml |
Table 20-17 describes the move plan properties that you can change for Oracle B2B. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-17 Move Plan Properties for Oracle B2B
Property | Description | Sample Value |
---|---|---|
Property in the File.DeliveryChannel configGroup: |
File Delivery Channel configuration. |
|
file-param-folder |
The absolute path of the folder. |
/tmp/file_deliv |
Property in the File.ListeningChannel configGroup: |
File Listening Channel configuration. |
|
file-param-folder |
The absolute path of the folder. |
/tmp/file_listen |
Properties in the JMS configGroup: |
JMS configuration. Each channel has its own set of property values. |
|
jms-param-is_topic |
A flag specifying whether or not this is a configured destination topic. Valid values are |
false |
jms-param-queue_name |
The JNDI name of the queue or topic. |
jms/b2b/B2B_IN_QUEUE |
jms-param-DestinationProviderProperties |
The JMS destination provider properties. Use a semicolon (;) as the separator for each key/value pair. |
java.naming.provider.url=t3://example.com:7001;java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.security.principal=weblogic;java.naming.security.credentials=weblogic |
jms-param-user |
The JMS user name. |
user1 |
Properties in the FTP configGroup: |
FTP configuration. Each channel has its own set of property values. |
|
ftp-param-folder |
The absolute path of the folder. |
/tmp/test1 |
ftp-param-host |
The FTP host name. |
example |
ftp-param-preserve_filename |
A flag that specifies whether the file name will be preserved. Valid values are |
false |
ftp-param-user |
The FTP user name. |
User |
Properties in the HTTP configGroup: |
HTTP configuration. Each channel has its own set of property values. |
|
http-param-use_proxy |
A flag that specifies whether to use a proxy server. Valid values are |
false |
http-param-additional_headers |
Additional transport headers, for example, headers for digest authentication. |
|
http-param-url |
The fully qualified HTTP URL. |
http://example:8001/b2b/httpReceiver |
Properties for the SFTP transport protocol: |
The SFTP configuration. |
|
sftp-param-host |
The SFTP host name. |
example |
sftp-param-port |
The SFTP port number. |
22 |
sftp-param-folder |
The absolute path of the folder. |
/scratch/b2b/sftp |
sftp-param-user |
The name of the SFTP user. |
user1 |
Properties for the Email transport protocol: |
The email configuration. |
|
email-param-host |
The email host name. |
example |
email-param-user |
The email user name. |
user1 |
email-param-email-id |
The email address to which messages are delivered (similar to specifying the path for a file channel or queues in AQ or JMS). |
user1@exampleb2b.com |
Properties for the AQ transport protocol: |
The AQ configuration. |
|
aq-param-datasource |
The JNDI name of the JDBC data source to access AQ queues. |
jdbc/SOADataSource |
aq-param-recipient |
The value used when delivering a message to the AQ queue. |
testuser |
aq-param-queue_name |
The AQ queue name. |
IP_OUT_QUEUE |
aq-param-consumer |
The client that receives the message. |
b2buser |
Properties for the TCP transport protocol: |
The TCP configuration. |
|
tcp-param-host |
The TCP host name. |
example |
tcp-param-port |
The TCP port number. |
23456 |
tcp-param-PermanentConnectionType |
A flag indicating whether or not a cached connection is used to exchange all the messages. Valid values are |
false |
tcp-param-timeout |
The TCP timeout, in seconds. |
300 |
Table 20-18 describes the move plan properties that you can change for Oracle HTTP Server. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
For Oracle HTTP Server, there are many configGroup elements in the move plan. Each configGroup element is associated with one Oracle HTTP Server configuration file. As a result, there may be more than one instance of a particular property, such as User.
Table 20-18 Move Plan Properties for Oracle HTTP Server
Property | Description | Sample Value |
---|---|---|
Listen |
The Listen address. It can include the host name and port or just the port. |
orcl3.example.com:8888 or 8888 |
User |
The Oracle HTTP Server administration user. |
admin_user
|
Group |
The group for the user. |
admin_group1
|
ServerAdmin |
The administrator's email address. |
Webmaster@example.com |
ServerName |
The name of the server for Oracle HTTP Server. If the host does not have a registered DNS name, use the IP address. |
orcl1.example.com |
WebLogicHost |
The name of the host on which Oracle WebLogic Server is listening for requests. |
orcl2.example.com |
WebLogicPort |
The port number that Oracle WebLogic Server uses to listen for requests. |
9002 |
WebLogicCluster |
The name of the host on which an Oracle WebLogic Server cluster is running and its port number. |
orcl3.example.com:9003 |
VirtualHost |
The name of the virtual host. The port number listed should also be listed in the Listen directive. |
*.8888 |
PlsqlDatabasePassword |
Specific to the PLSQL module, the name of a secure file containing the password. You must provide a password file, even if you are not changing the configuration. |
/scratch/orcl/plsql_passwd |
PlsqlDatabaseConnectString |
Specific to the PLSQL module, the service name of the database. |
orcl.example.com:1521:orcl1 |
PlsqlNLSLanguage |
Specific to the PLSQL module, the NLS_LANG variable for the database access descriptor (DAD). |
America_America.UTF8 |
ORAConnectSN |
Specific to the oradav module, the Oracle database to which to connect. |
db_host:db_port:db_service_name
|
ORAUser |
Specific to the oradav module, the database user (schema) to use when connecting to the service specified by the ORAConnectSN property. |
db6175_PORTAL |
ORACRYPTPASSWORD |
Specific to the oradav module, the absolute path to the secure file containing the password for oradav. You must provide a password file, even if you are not changing the configuration. |
/scratch/oracle/dav_passwd |
SSLWallet |
The location of the SSL wallet, if the wallet is not in the default location. |
/scratch/oracle/mw_home/ORACLE_INSTANCE/config/OHS/ohs1/keystores/mywallets
|
DocumentRoot |
The directory that stores the main content for the Web site. |
/scratch/oracle/mw_home/ORACLE_INSTANCE/config/ohs/ohs1/htdocs
|
Alias |
The location of the alias, if it is not in the default location. Note that you change the value within the double quotation marks. |
/icons/"/scratch/orcl/icons/" |
ScriptAlias |
The location of the script alias, if it is not in the default location. Note that you change the value within the double quotation marks. |
/cgi-bin/"/scratch/oraclcgi-bin/" |
WebGateInstalldir |
The location of the WebGate installation directory, as specified in the webgate.conf file. |
/scratch/oracle/mw_home/Oracle_OAMWebGate1/webgate/ohs |
primaryOAMServerHost |
The primary Access Manager server host. Note that the configuration for the secondary Access Manager server host is updated automatically the first time that WebGate communicates with the primary server. |
primary_oam_server_host.example.com
|
primaryOAMServerPort |
The port number for the Access Manager primary host. |
5575 |
Table 20-19 describes the move plan properties that you can change for Oracle Internet Directory. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-19 Move Plan Properties for Oracle Internet Directory
Property | Description | Sample Value |
---|---|---|
OID Non SSL Port |
The non-SSL port for Oracle Internet Directory. If you do not provide a port number or if the port number you provide is not available, the operation uses an available port. |
3060 |
OID SSL Port |
The SSL port for Oracle Internet Directory. If you do not provide a port number or if the port number you provide is not available, the operation uses an available port. |
3131 |
Namespace |
The Oracle Internet Directory namespace. |
dc=us,dc=oracle,dc=com |
OID Admin Password |
The absolute path of a secure file containing the password for the Oracle Internet Directory administrator. You must provide a password file, even if you are not changing the configuration. |
/scratch/oracle/oid_passwd |
ODS Schema Password |
The absolute path of a secure file containing the password for the ODS schema, which is the schema that contains metadata for Oracle Internet Directory. You must provide a password file, even if you are not changing the configuration. |
/scratch/oracle/ods_passwd |
ODSSM Schema Password |
The absolute path of a secure file containing the password for the ODSSM schema, which is used to access server manageability information for Oracle Internet Directory from the database. You must provide a password file, even if you are not changing the configuration. |
/scratch/oracle/odssm_passwd |
DB Host Name |
The name of the host on which the database is running, which can be found in the tnsnames.ora file. |
example.com |
DB Port |
The port number of the database listener, which can be found in the tnsnames.ora file. |
1521 |
DB Service Name |
The service name for the database, which can be found in the tnsnames.ora file. |
orcl.example.com |
Table 20-20 describes the move plan properties that you can change for Oracle Virtual Directory. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-20 Move Plan Properties for Oracle Virtual Directory
Property | Description | Sample Value |
---|---|---|
OVD Non SSL Port |
The LDAP non-SSL port number for Oracle Virtual Directory. If you do not provide a port number or if the port number you provide is not available, the operation uses the next available port. |
6501 |
OVD SSL Port |
The LDAP SSL port number for Oracle Virtual Directory. If you do not provide a port number or if the port number you provide is not available, the operation uses the next available port. |
7501 |
OVD Admin Port |
The administration port number for Oracle Virtual Directory. If you do not provide a port number or if the port number you provide is not available, the operation uses the next available port. |
8899 |
OVD Http Port |
The HTTP listener port number for Oracle Virtual Directory. |
8080 |
host.port |
The host name and port for the Oracle Virtual Directory adapter. |
example.com:3060 |
username |
The user name for the Oracle Virtual Directory adapter. |
cn=orcladmin |
root |
The root for the Oracle Virtual Directory adapter. |
dc=us,dc=oracle,dc=com |
remotebase |
The remote base for the Oracle Virtual Directory adapter. |
dc=us,dc=oracle,dc=com |
password |
The absolute path of a secure file containing the password for the Oracle Virtual Directory adapter user. |
/scratch/oracle/ovd_passwd |
Table 20-21 describes the move plan properties that you can change for Identity Federation. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-21 Move Plan Properties for Identity Federation
Property | Description | Sample Value |
---|---|---|
Properties in the ServerConfig configProperty: |
Server configuration |
|
Load Balancer Hostname |
The name of the host of the Load Balancer. |
example.com |
Load Balancer Port |
The port number of the Load Balancer. |
7500 |
SOAP Port |
The SOAP port number. |
7500 |
SSL Enabled |
The flag indicating that SSL is enabled. Valid values are |
true |
SOAP SSL Enabled |
The flag indicating that SSL is enabled for SOAP. Valid values are |
true |
Properties in the User Data Store configProperty: |
The user data store configuration. These properties are present in the move plan if the user data store uses LDAP. |
|
LDAP Server URL |
The URL of the LDAP connection. The property contains the host name and port number of the LDAP store. |
ldap://example.com:389 |
LDAP Username |
The LDAP Server administrative user name. |
cn=orcladmin |
LDAP Password File |
The absolute path of a secure file containing the password for the administrative user. |
/scratch/oracle/oif_ds_passwd |
Properties in the Federation Data Store configProperty: |
Federation data store configuration. These properties are in the move plan if the federation data store uses LDAP. |
|
LDAP Server URL |
The URL of the Federation LDAP connection. It contains the host name and port number of the Federation LDAP store. |
ldap://example.com:389 |
LDAP Username |
The Federation LDAP Server administrative user name. |
cn=orcladmin |
LDAP Password File |
The absolute path of a secure file containing the password for the Federation LDAP administrative user. |
/scratch/oracle/oif_fed_passwd |
Properties in the AuthnEngine configProperty: |
Authentication engine configuration. There may be multiple Authentication engines, which are independent of each other. |
|
LDAP Connection URL |
The URL of the LDAP connection. It contains the host name and port number of the LDAP store. This property is present in the move plan if LDAP is enabled as an Authentication Engine. |
ldap://example.com:389 |
LDAP Username |
The LDAP administrative user name. This property is present in the move plan if LDAP is enabled as an Authentication Engine. |
cn=orcladmin |
LDAP Password File |
The absolute path of a secure file containing the password for the administrative user. This property is present in the move plan if LDAP is enabled as an Authentication Engine. |
/scratch/oracle/oif_ae_pwd_passwd |
OAM11g Logout URL |
The URL for logging out of Access Manager 11g. It contains the host name and port number of Access Manager 11g. This property is present in the move plan if Access Manager 11g is enabled as an Authentication Engine. |
http://oam11g_host:oam11g_port/logout.jsp
|
HTTP Header Logout Redirect URL |
The URL for logging out. It contains the host name and port number of the Oracle HTTP Server. This property is present in the move plan if HTTP Header is enabled as an Authentication Engine. |
http://example.com:port/logout.jsp
|
Properties in the SPEngine configGroup: |
The SP engine configuration. There may be multiple SP engines, which are independent of each other. |
|
OAM11g Login URL |
The URL for logging in to Access Manager 11g. It contains the host name and port number of Access Manager 11g. This property is present in the move plan if an SP Engine uses Access Manager 11g. |
http://oam11g_hostname:oam11g_port/login
|
OAM11g Logout URL |
The URL for logging out of Access Manager 11g. It contains the host name and port number of Access Manager 11g. This property is present in the move plan if an SP Engine uses Access Manager 11g. |
http://oam11g_host:oam11g_port/logout.jsp
|
Table 20-22 describes the move plan properties that you can change for Oracle Identity Manager. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-22 Move Plan Properties for Oracle Identity Manager
Property | Description | Sample Value |
---|---|---|
Properties in the configGroup Role SoD |
Oracle Identity Manager Role Sod check connection information |
|
User name |
The OAACG username which OIM uses for Role SoD feature. |
oaacgAdminUser |
Service Url |
The OAACG service URL which OIM uses for Role SoD feature. |
|
Host:Port |
The OAACG host and port which OIM uses for Role SoD feature. |
example.com:1234 |
OAACG Password File |
OAACG password which OIM uses for Role SoD feature |
password
|
Properties in the configGroup Admin |
Oracle Identity Manager administration configuration |
|
OIM Admin Password File |
The absolute path of a secure file that contains the password for the Oracle Identity Manager administrator. |
/scratch/t2p/pwd/oimpwd.txt |
Properties in the configGroup LDAP |
Configuration for the LDAP for Oracle Identity Manager |
|
LDAP Password File |
The absolute path of a secure file that contains the password for the LDAP configured for Oracle Identity Manager. |
/scratch/t2p/pwd/oimldappwd.txt |
LDAP Url |
The URL of the LDAP connection. It contains the host name and port number of the LDAP store. |
ldap://example.com:3060 |
Directory Server Type |
The LDAP directory type Possible values are: OID, ACTIVE_DIRECTORY, IPLANET, OUD, OVD, LIBOVD |
OID |
Properties in the configGroup SOA Configuration |
Configuration for SOA for Oracle Identity Manager |
|
SOAP Url |
The SOA SOAP URL configured in Oracle Identity Manager. |
http://example.com:8001 |
User name |
The SOA user name configured in Oracle Identity Manager. |
username
|
SOA Password File |
The absolute path of a secure file that contains the password for SOA as configured in Oracle Identity Manager. |
/scratch/t2p/pwd/oimsoappwd.txt |
Properties in the configGroup UMS Configuration |
Configuration for Oracle User Messaging Service for Oracle Identity Manager |
|
Email Server Name |
The default email server name configured in Oracle Identity Manager. |
host.example.com |
UMS Web Service URL |
The UMS Web Service URL as configured in Oracle Identity Manager. |
host.example.com:8001/ucs/messaging/webservice |
Properties in the configGroup OIM OAM Configuration |
Configuration for Access Manager for Oracle Identity Manager |
|
Access Server Host:Access Server Port |
The Access Manager server host and port as configured in Oracle Identity Manager |
host.example.com:5575 |
SSO Access Gate Password File |
The absolute path of a secure file that contains the password for the SSO Access Gate as configured in Oracle Identity Manager. |
/scratch/t2p/pwd/oimssoaccpwd.txt |
SSO Keystore JKS Password File |
The absolute path of a secure file that contains the password for SSO keystore JKS as configured in Oracle Identity Manager. |
/scratch/t2p/pwd/oimssojkspwd.txt |
SSO Global Passphrase |
The absolute path of a secure file that contains the global SSO passphrase as configured in Oracle Identity Manager. |
/scratch/t2p/pwd/oimssopwd.txt |
Properties in the configGroup BI Publisher Configuration |
Configuration for Oracle BI Publisher for Oracle Identity Manager |
|
BI Publisher URL |
The Oracle BI Publisher URL as configured for Oracle Identity Manager |
http://localhost:9704 |
BI Publisher Password |
The absolute path of a secure file that contains the Oracle BI Publisher password as configured for Oracle Identity Manager. |
/scratch/t2p/pwd/oimbippwd.txt |
Table 20-23 describes the move plan properties that you can change for Oracle BI EE and Oracle BI Publisher. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-23 Move Plan Properties for Oracle BI EE and Oracle BI Publisher
Property | Description | Sample Value |
---|---|---|
Properties in the XMLP-SERVER-CONFIG configGroup: |
Oracle BI Publisher configuration |
|
SAW_SERVER |
The name of the host that is running the Oracle BI Presentation Services to which you must connect. |
example_host |
SAW_PORT |
The port number for connecting to Oracle BI Presentation Services. |
10217 |
SAW_PASSWORD |
The absolute path of a secure file that contains the password for Oracle BI Presentation Services. |
/scratch/oracle/bip_passwd |
SAW_USERNAME |
The user name for Oracle BI Presentation Services. |
user1 |
Properties in the XMLP-DATASOURCES configGroup: |
Data source configuration |
|
Properties in the connection configProperty: |
A sub-property of dataSource. Specifies that the data source is a Connection type. Each data source can be either a Connection or File type. |
|
url |
The URL of the connection. It has the following format: jdbc:oracle:thin:@Db_host:Db_port:Db_SID |
jdbc:oracle:thin:@host.example.com:1521:orcl |
driver |
The driver to use for the connection |
oracle.jdbc.OracleDriver |
username |
The user name for the connection. |
user1 |
password |
The absolute path of a secure file that contains the password for the connection. |
/scratch/oracle/ds_conn_passwd |
Property in the file configProperty: |
A sub-property of dataSource. Specifies that the data source is a File type. |
|
path |
The file system path that points to the relevant data source file. |
/scratch/oracle/Middleware/user_projects/domains/BIDomain/config/bipublisher/repository/DemoFiles |
Properties in the XDO-CLIENT_CONFIG configGroup: |
Oracle BI Publisher client |
|
XMLPClientDirPath |
The absolute path to the Oracle BI Publisher client directory. |
/scratch/instance/domains/example.com/CommonDomain/config |
* (any name) |
The Oracle BI Publisher configured endpoint connecting URL. The move plan may have more than one endpoint. |
http://example.com:10621/xmlpserver |
Properties in the XMLP-SCHEDULER-JMS-CONFIG configGroup: |
The Scheduler configuration |
|
JMS_WEBLOGIC_JNDI_URL |
The Oracle WebLogic Server JNDI URL for the Oracle BI EE Managed Server. |
cluster:t3://bi_cluster |
JMS_Shared_Temp_Directory |
The JMS shared temp directory used in an Oracle BI EE cluster environment. |
/scratch/oracle/instance/instance1/BIPublisher/biptemp |
Properties in the XMLP-PROVIDER-CONFIG configGroup, in the provider configProperty: |
Oracle BI Publisher provider There is a separate configProperty for each BI Publisher provider configured. |
|
uri |
The URI for the Oracle BI Publisher provider. |
http://example.com:10603/bip |
nonSSOUri |
The non-SSO URI for the Oracle BI Publisher provider. |
bip |
Property in the XDO-SERVER_CONFIG configGroup: |
Oracle BI Publisher Server |
|
XMLPServerConfigDirPath |
The absolute path to the Oracle BI Publisher server configuration directory. |
/scratch/oracle/Middleware/user_projects/domains/BIDomain/config/bipublisher |
Property in the RepositoryDirPath configProperty: |
The directory path of the Oracle BI Publisher server repository. |
|
path |
The directory of the Oracle BI Publisher server configuration repository. (It can be located outside of the BIDomain that is specified as the server |
/scratch/oracle/instance/instance1/BIPublisher/repository |
Property in the SawSourcePath configProperty: |
The Oracle BI Publisher server connection resource details for the Oracle BI EE Presentation Server |
|
source |
The path for the Oracle BI Publisher repository directory. |
/scratch/oracle/Middleware/user_projects/domains/BIDomain/config/bipublisher/repository |
Properties in the OracleInstances configGroup: |
Oracle BI EE domain configuration |
|
instanceHome |
The path of the Oracle instance in which Oracle BI EE is deployed. |
scratch/oracle/Middleware/instances/instance1 |
host |
The host where the Oracle BI EE Oracle instance is configured. |
example.com |
Properties in the BIInstanceDeployment configProperty: |
Instance configuration details. |
|
listenAddress |
The listen address for the host. It can be set to a virtual IP address or a subset on a multi-homed computer. You can specify an asterisk to specify multiple network addresses for the host. |
example.com * |
portRangeStart |
The start of the range of ports used by the Oracle BI EE system components. |
10206 |
portRangeEnd |
The end of the range of ports used by the Oracle BI EE system components. |
10214 |
Properties in the BIInstance configGroup, in the EmailOptions configProperty: |
Oracle BI EE instance configuration |
|
smtpServerName |
The host name of the SMTP server. |
example.com |
port |
The port number of the SMTP server. |
25 |
fromDisplayName |
The sender's name that is used as the display name by the Oracle BI EE system when it sends email. |
Oracle Business Intelligence |
emailAddressOfSender |
The email address used by the Oracle BI EE system when it sends email. |
defaultuser@defaultmailserver.com |
Property in the BIInstance configGroup, in the MarketingOptions configProperty: |
Oracle BI EE instance configuration |
|
url |
The base URL used by the Oracle BI EE system when the emails have embedded URLs. |
http://example.com:7012/_dav/cs/idcplg |
Property in the BIInstance configGroup, in the PresentationServerOptions configProperty: |
Presentation Server configuration. |
|
webCatalogLocation |
The absolute path of the location of the Oracle BI Presentation Catalog. |
/scratch/oracle/instance/instance1/OracleBIPresentationServicesComponent/coreapplication_obips1/catalog/OracleBIApps |
Property in the BIInstance configGroup, in the Scheduler configProperty: |
Scheduler configuration |
|
dataSource |
The connection details for the Oracle BI Scheduler data source. |
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=example.com)(PORT=1565)))(CONNECT_DATA=(SERVICE_NAME=d8b4lfc1)) |
Properties in the BIInstance configGroup, in the ServerOptions configProperty: |
Server options configuration |
|
repositoryDataSourceName |
The name of the data source for the Oracle BI repository (RPD) file. |
Star |
repositoryName |
The name of the RPD. |
OracleBI_BI0002 |
repositorySharedLocation |
The shared location for the RPD. |
/scratch/oracle/instance/BIShared/OracleBIServerComponent/coreapplication_obis1/repository |
Property in the BIInstance configGroup, in the PerformanceOptions configProperty: |
Performance options configuration |
|
globalCacheStoragePath |
The global location of the Oracle BI EE server cache. |
/scratch/oracle/instance/instance1/OracleBIServerComponent/coreapplication_obis1/cache |
Properties in the DEPLOY_USER_CREDENTIALS configGroup: |
Oracle RTD Inline Services (BI_RTD_SPE_ILS_DEPLOY_CONFIG) |
|
username |
The user name used to deploy the RTD SPE inline service. |
weblogic |
password |
The absolute path of a secure file that contains the password for the connection. |
/scratch/oracle/rtd_passwd |
Properties in the CONNECTIONPOOLS configGroup: |
RPD configuration |
|
user |
Connection pool user name (the database schema name). The name may be a variable, in the format |
VALUEOF(ORACLE_INITBLOCK_USER) |
datasource |
RPD connection pool data source name or definition. The name may be a variable, in the format |
VALUEOF(ORACLE_INITBLOCK_DSN) |
appServerName |
If this is an ADF connection, the Business Component URL. |
http://example.com:10603/fscmAnalytics/obieebroker |
password |
The absolute path of a secure file that contains the password for the connection to the RPD data source. |
/scratch/oracle/rpd_ds_conn_passwd |
Properties in the VARIABLES configGroup: |
Definition of variables |
|
name |
The name of the variable that is used in the RPD connection pool definitions. There can be multiple name/value pairs. |
ORACLE_INITBLOCK_USER |
value |
The value of the variable that is used in the RPD connection pool definitions. There are multiple name/value pairs. |
'ORA_INIT_USER' |
Table 20-24 describes the move plan properties that you can change for Oracle BI EE Data Warehouse Administration Console. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-24 Move Plan Properties for Oracle BI EE Data Warehouse Administration Console (DAC)
Property | Description | Example |
---|---|---|
Properties in the DAC-SERVER-CONFIGURATION configGroup: |
DAC configuration |
|
jdbc.url |
The URL to connect to the DAC repository. It has the following format: jdbc:oracle:thin:@Db_host:Db_port:Db_SID |
jdbc:oracle:thin:@host.example.com:1521:orcl |
jdbc.driver |
The name of the JDBC driver. |
oracle.jdbc.driver.OracleDriver |
Username |
The user name used to connect to the DAC repository. |
IMPORT_DAC |
Password File |
The absolute path of a secure file containing the password for the user to connect to the DAC repository. You must provide a password file, even if you are not changing the configuration. |
/scratch/biplatform/cloning/dac_passwd |
Properties in the EMAIL-CONFIGURATION configGroup: |
Email configuration |
|
email_host |
The host name of the email server. |
example |
email_protocol |
The protocol for the email server. |
smtp |
email_address |
The email address of the user. |
test@test.te |
needs_authentication |
The flag indicating whether the corporate email server requires authentication. Valid values are |
true |
needs_ssl |
The flag indicating whether an SSL connection is required. Valid values are |
false |
email_host_port |
The port where the email server listens. |
5555 |
email_user |
User name for the email account. |
test |
email_password |
The absolute path of a secure file containing the password for the user of the email server. (Only required if needs_authentication is true.) |
/scratch/biplatform/cloning/email_passwd |
Properties in the DATAWAREHOUSE-CONFIGURATION configGroup: |
Data Warehouse configuration |
|
jdbc.url |
The URL to connect to the Data Warehouse. It has the following format: jdbc:oracle:thin:@Db_host:Db_port:Db_SID |
jdbc:oracle:thin:@host.example.com:1521:orcl |
jdbc.driver |
The name of the JDBC driver. |
oracle.jdbc.driver.OracleDriver |
Username |
The user name used to connect to the Data Warehouse. |
IMPORT_DW |
Password File |
The absolute path of a secure file containing the password for the user to connect to the Data Warehouse. You must provide a password file, even if you are not changing the configuration. |
/scratch/biplatform/cloning/DW_passwd |
Properties in the INFORMATICA-CONFIGURATION configGroup: |
Informatica configuration |
|
Informatica server home |
The Informatica server home. |
/scratch/infahome/ |
Domains infa file location |
The domain's infa file location. |
/scratch/infahome/domains.info |
InformaticaParameterFileLocation |
The directory where the Informatica parameter files are stored (or DEFAULT). |
DEFAULT |
Properties in the DATASOURCES-CONNECTION-DETAILS configGroup: |
Data source connection information |
|
type |
The physical data source type. Possible values are: Source, Warehouse, Informatica Repository, DAC Repository, Other. |
Source |
Connection Type |
The type of database connection. Possible values are: BI Server, Oracle (OCI8), Oracle (Thin), DB2, DB2-390, MSSQL, Teradata, Flat File. |
Oracle (Thin) |
Connection String |
The data source connection string. If you are using:
|
orcl.example.com |
Table Owner |
The user name of the table owner. |
DB_USER |
Host |
The host name of the server where the database resides. |
example.com |
Port |
The port number where the database receives requests. |
1521 |
JDBC Driver (Optional) |
The JDBC driver for the data source connection. The value in this field must conform to the database specifications. |
oracle.jdbc.driver.OracleDriver |
URL (Optional) |
The JDBC URL for the data source connection. The value in this field must conform to the database specifications. It has the following format: jdbc:oracle:thin:@Db_host:Db_port:Db_SID |
jdbc:oracle:thin:@host.example.com:1521:orcl |
Password File |
The absolute path of a secure file containing the password for the user to connect to the data source. You must provide a password file, even if you are not changing the configuration. |
/scratch/biplatform/cloning/ds_passwd |
Connection Pool Name (BIPool) |
The connection pool name. |
FSCM_OLTP."Connection Pool" |
Database Type (BIPool) |
Database type of the transactional data source. |
Oracle |
Properties in the EXTERNAL-EXECUTORS configGroup: |
External executors configuration |
|
Execution type |
The execution type for the tasks that will be executed by the external executor. |
ODI 11g Embedded Agent |
name |
The name of the property that must be configured to integrate DAC with other Extract, Transform, and LoadExtract, Transform, and Load (ETL) tools. There are multiple properties for the external executors. Name is the name of the property. Value is the value that defines the property. |
<name>ODIUser</name> <value>TestUser</value> |
Table 20-25 describes the move plan properties that you can change for Oracle Essbase. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-25 Move Plan Properties for Oracle Essbase
Property | Description | Example |
---|---|---|
Properties in the EssbaseAgentConfig configGroup: |
Oracle Essbase configuration |
|
ARBORPATH |
The absolute path for ARBORPATH. |
/scratch/oracle/shared_essbase |
PortRange |
The port range for Oracle Essbase. |
9000-9499 |
agent-port |
The port number of the Oracle Essbase agent. |
9799 |
EssbaseAdminUserName |
The administration user name for Oracle Essbase. |
weblogic |
EssbaseAdminPassword |
The absolute path of a secure file containing the password for the Oracle Essbase administration user. |
/scratch/oracle/essbase_passwd |
Properties in the ASOAppsTableSpaceCustomizations configGroup: |
Aggregate Storage (ASO) application configuration. Each aggregate storage (ASO) application has a name and Table Space property, followed by the properties in the configGroup. |
|
file_location |
The absolute path of the application file. |
/scratch/oracle/aso |
max_file_size |
The maximum size of the file, in Bytes. |
1.34217727E8 |
max_disk_size |
The maximum size of the disk, in Bytes. |
4.294967295E9 |
Properties in the BSOAppsDiskVolumeCustomizations configGroup: |
Block Storage (BSO) application configuration. Each Essbase block storage (BSO) application has a name and database name property, followed by the properties in the configGroup. |
|
volume |
The location of the disk volume. |
/scratch/biplatform |
file_type |
The file type of the disk volume, such as index, data, or index_data. |
index_data |
file_size |
The size of the volume, in Bytes. |
2.147483648E9 |
partition_size |
The size of the partition, in Bytes. |
9.007199254739968E15 |
Table 20-26 describes the move plan properties that you can change for the EPM registry. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-26 Move Plan Properties for the EPM Registry
Property | Description | Example |
---|---|---|
Properties in the reg.properties configGroup: |
EPM Registry |
|
jdbc.url |
The URL to connect to the EPM Registry database. It has the following format: jdbc:oracle:thin:@Db_host:Db_port:Db_SID |
jdbc:oracle:thin:@host.example.com:17328:orcl |
jdbc.driver |
The name of the JDBC driver. |
oracle.jdbc.OracleDriver |
username |
The user name used to connect to the EPM database. |
USER_BIPLATFORM |
password |
The absolute path of a secure file containing the password for the user to connect to the EPM database. You must provide a password file, even if you are not changing the configuration. |
/scratch/biplatform/epm_jdbc_passwd |
Properties in the EPM_COMPONENTS configGroup, in the DATABASE_CONN configProperty: |
EPM components configuration |
|
host |
The database server host name. |
example.com |
dbUserName |
The database user name. |
FUSION_BIPLATFORM |
dbJdbcUrl |
The JDBC URL to connect to the database. It has the following format: jdbc:oracle:thin:@Db_host:Db_port:Db_SID |
jdbc:oracle:thin:@host.example.com:1570:orcl |
dbName |
The database name. For Oracle Database, use the service name or SID. |
db20258 |
dbPort |
The database port number. |
1570 |
dbPassword |
The absolute path of a secure file containing the password for the user to connect to the database. You must provide a password file, even if you are not changing the configuration. |
/scratch/biplatform/epm_db_passwd |
Properties in the EPM_COMPONENTS configGroup, in the Default configProperty: |
EPM components configuration |
|
host |
The host name of the front-end Web server or load balancer. |
example2.com |
port |
The port number of the front-end Web server or load balancer. This is a subentry to the Default property. |
10621 |
isSSL |
The flag indicating whether the front end is in SSL mode. Valid values are |
false |
SSLPort |
The SSL port number of the front-end Web server or load balancer |
10218 |
Properties in the WORKSPACE_APP configProperty: |
Workspace configuration. |
|
host |
The host name of the server hosting the Workspace Web application. |
example.com |
port |
The port where the Workspace Web application is running. |
10217 |
SSLPort |
The SSL port (if configured for SSL) where the Workspace Web application is running. |
10218 |
Properties in the EPM_COMPONENTS configGroup, in the WEB_SERVER configProperty: |
Web server configuration |
|
host |
The host name of the Web server that the Web application is configured to use. |
example.com |
port |
The port where the Web application is running. |
10217 |
isSSL |
The flag indicating whether the front end is in SSL mode. Valid values are |
false |
Properties in the EPM_COMPONENTS configGroup, in the CALC_WEBAPP configProperty: |
EPM components configuration |
|
host |
The host name of the server hosting the Oracle Calculation Manager Web application. |
example.com |
port |
The port where the Oracle Calculation Manager Web application is running. |
10217 |
SSL_Port |
The SSL port (if configured for SSL) where the Oracle Calculation Manager Web application is running. |
10218 |
name |
The name of the Oracle Essbase cluster. There may be more than one cluster. |
EssbaseCluster-1 |
Properties in the essbaseservern configProperty: |
Oracle Essbase server |
|
host |
The host name of the Oracle Essbase server. |
example.com |
arborPath |
The ARBORPATH of the Oracle Essbase server. |
/scratch/oracle/shared_essbase |
ess_AppLocation |
The location of the Oracle Essbase application location. |
/scratch/biplatform/instances/instance1/Essbase/essbaseserver1 |
agent_PortNumber |
The agent port number of the Oracle Essbase server. |
9511 |
agent_StartPort |
The start of the range of ports used by the agent for Oracle Essbase server. |
9000 |
agent_StopPort |
The end of the range of ports used by the agent for Oracle Essbase server. |
9499 |
Properties in the BIEE_WEBAPP configProperty: |
Oracle BI EE Web application configuration |
|
host |
The host name of the server hosting the Oracle BI EE Web application. |
example.com |
port |
The port where the Oracle BI EE Web application is running. |
10217 |
SSL_Port |
The SSL port (if configured for SSL) where the Oracle BI EE Web application is running. |
10218 |
Properties in the PROVIDER_SERVICES_WEB_APP configProperty: |
The Oracle Essbase APS Web application configuration |
|
host |
The host name of the server hosting the Oracle Essbase APS Web application. |
example.com |
port |
The port where the Oracle Essbase APS Web application is running. |
10217 |
SSL_Port |
The SSL port (if configured for SSL) where the Oracle Essbase APS Web application is running. |
10218 |
Properties in the PFINANCIAL_REPORTING_WEB_APP configProperty: |
The Financial Reporting Web application configuration |
|
host |
The host name of the server hosting the Financial Reporting Web application. |
example.com |
port |
The port where the Financial Reporting Web application is running. |
10217 |
SSL_Port |
The SSL port (if configured for SSL) where the Web application is running. |
10218 |
Table 20-27 describes the move plan properties that you can change for Oracle BI Action Framework. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-27 Move Plan Properties for Oracle BI Action Framework
Property | Description | Sample Value |
---|---|---|
Property in the location-alias configGroup: |
Action Framework configuration |
|
alias_name |
The URL corresponding to the action name. Note that there may be more than one name/value pair. |
http://example.com:9704/analytics |
Table 20-28 describes the move plan properties that you can change for Oracle WebCenter Content Server, Oracle WebCenter Content: Records, and Oracle WebCenter Content: Inbound Refinery. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
You must edit the properties for each component under the appropriate componentType.
Table 20-28 Move Plan Properties for WebCenter Content Server, Records, and Inbound Refinery
Property | Description | Sample Value |
---|---|---|
Properties in componentType |
The componentType is Webcenter Content - Records, Content Server, or Inbound Refinery. |
|
MoveType |
The flag indicating whether to copy the entire test system instance, including configuration and data, or to create a new content server instance, based on the test system configuration. Valid values are This property is not applicable to Inbound Refinery. |
copy |
Properties in the copy configGroup: |
Copy the configuration and data |
|
IntradocDir |
The path to the Intradoc directory. The directory value can begin with the string |
/scratch/mw_home1/user_projects/domains/domain_name/ucm/cs
or
{domainHome}/ucm/cs
|
WeblayoutDir |
The path to the Weblayout directory. The directory value can begin with the string This property may not be present if the WebLayoutDir is located in the default location, under the Intradoc directory. |
/scratch/mw_home1/user_projects/domains/domain_name/ucm/cs/weblayout
or
{domainHome}/ucm/cs/weblayout
|
VaultDir |
The absolute path to the Vault directory. The directory value can begin with the string This property may not be present if the VaultDir is located in the default location, under the Intradoc directory. |
/scratch/mw_home1/user_projects/domains/domain_name/ucm/cs/vault
or
{domainHome}/ucm/cs/vault
|
UserProfilesDir |
The absolute path to the user profiles directory. The directory value can begin with the string This property may not be present if it is located in the default location, under the Intradoc directory. |
/scratch/mw_home1/user_projects/domains/domain_name/ucm/cs/data/users/profiles
or
{domainHome}/ucm/cs/users/profiles
|
SocketHostAddressSecurityFilter |
The security filter which lists the hosts that are allowed to directly access the server port. You can specify multiple values by separating them with a vertical bar (|). |
127.0.0.1|0.0.0.0.0.0.0.1 |
Properties in the init configGroup: |
Create a new instance with the configuration of the source. |
|
SocketHostAddressSecurityFilter |
The security filter which lists the hosts that are allowed to directly access the server port. You can specify multiple values by separating them with a vertical bar (|). |
127.0.0.1|0.0.0.0.0.0.0.1 |
Table 20-29 describes the move plan properties that you can change for Oracle WebCenter Content: Imaging. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-29 Move Plan Properties for Oracle WebCenter Content: Imaging
Property | Description | Sample Value |
---|---|---|
AdminUser |
Administrative user ID used during the |
Admin2 |
Properties in the MBean Settings configGroup: |
MBeans configuration |
|
InputAgentInputDirectories |
A comma-separated list of directories where input sources look for work. |
IPM/InputAgent/Input |
InputSampleDirectory |
The directory that holds the sample data for the input UI. |
IPM/InputAgent/Input/Sample |
RenderGDFontPath |
Location of the TrueType (TTF) font files used by the OIT rendering package. |
/usr/share/X11/fonts/TTF |
Properties in the UCM Connection configGroup: |
The WebCenter Content connection configuration |
|
repository.machine |
The location of the repository. The value must be |
localhost |
repository.port |
The WebCenter Content server port used when the local content server is used. If not using local content server connection, remove the configuration property. |
4444 |
repository.useSSL |
A flag that specifies whether the connection to WebCenter Content systems use SSL. Valid values are |
false |
Property in the WORKFLOW Connection configGroup: |
The workflow connection configuration |
|
bpel.front.address |
The HTTP front-end address used in the Imaging SOA: Connection Settings UI. |
http://example.com:8001 |
Table 20-30 describes the move plan properties that you can change for Oracle Data Integrator. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-30 Move Plan Properties for Oracle Data Integrator
Property | Description | Sample Value |
---|---|---|
JPS configuration file |
The path of the JPS configuration file for JSE components. |
/private/t2p/jps-config.xml |
Properties in the Master Repository configGroup: |
Master repository configuration |
|
Master Repository Id |
Oracle Data Integrator master repository ID. It should be different than the ID for the source master repository. |
502 |
SUPERVISOR password file |
The absolute path of a secure file that contains the password for the ODI user SUPERVISOR. |
/scratch/oracle/odi_passwd |
Schema name |
The name of the schema in the target database where the target ODI repository will be created. |
odi_master_11g |
Schema password file |
The absolute path of a secure file that contains the password for the schema. |
/scratch/oracle/odi_schema_passwd |
Properties in the Physical Data Servers configProperty: |
Data servers configuration |
|
Schema name |
The name of the schema for the database data servers or the directory location for file type data servers. |
FG_Dir_Schema |
Work Schema |
The name of the Work schema for the database data servers or the directory location for file type data servers. |
/tmp/FG_Dir_Schema |
Url |
JDBC URL for connecting to the data server. It has the following format: jdbc:oracle:thin:@Db_host:Db_port:Db_SID |
jdbc:oracle:thin:@localhost:1521:orcl |
User |
User name for the physical data servers connection. |
username |
Password File |
The absolute path of a secure file that contains the password for the user for the physical data servers connection. |
/scratch/oracle/rpd_ds_conn_passwd |
Properties in the Agents configProperty: |
Agents configuration |
|
Password File |
The absolute path of a secure file containing the password for the physical data servers connection. |
/scratch/oracle/odi_ds_passwd |
Host name |
The Agent host name. |
localhost |
Host port |
The Agent host port number. |
12311 |
Properties in the Work repositories configProperty: |
Work repositories configuration |
|
Work Repository Id |
The ID for the work repository. It should be different than the ID for the source work repository. |
1 |
Url |
JDBC URL for connecting to the work repository. It has the following format: jdbc:oracle:thin:@Db_host:Db_port:Db_SID |
jdbc:oracle:thin:@localhost:1521:orcl |
User |
User name for connecting to the work repository. |
username |
Password File |
The absolute path of a secure file that contains the password for the user for the physical data servers connection. |
/scratch/oracle/odi_pds_passwd |
Properties in the ServiceProviders configProperty: |
Service provider configuration if an external Access Manager is used as an SP engine. |
|
OAM_SERVER_n |
The URL of the Access Manager server. |
http://example.com:14101 |
Properties in the Applications configProperty: |
This section is present if an external Access Manager is used as an application. |
|
ReturnURL |
The return URL. |
example.com:5575 |
Table 20-31 describes the move plan properties that you can change for Access Manager, Secure Token Service, and Mobile and Social. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-31 Move Plan Properties for Access Manager, Secure Token Service, and Mobile and Social
Property | Description | Sample Value |
---|---|---|
Properties in the Load Balancer configProperty: |
Load Balancer-related configuration properties. |
|
hostname |
The name of the host for the Load Balancer. |
example.com |
port |
The port number for the Load Balancer. |
368 |
Properties in the ManagedServer configGroup: |
The Managed Server-related configuration properties. Update the following property for all Managed Servers in the move plan. |
|
ProxyPort |
The port number for the proxy server. |
5555 |
Properties in the OIM Connection Information configProperty: |
Oracle Identity Manager-related configuration property. This property is present in the move plan when Access Manager and Oracle Identity Manager are integrated. |
|
host/Port |
The URL, with the name of the host and the port number for Oracle Identity Manager. |
http://example.com:7010 |
Properties in the LDAP configProperty: |
The LDAP configuration. These properties are present in the move plan only if an embedded LDAP is not being used. |
|
LDAP Url |
The URL of the LDAP connection. It contains the host name and port number of the LDAP store. |
ldap://example.com:3060 |
LDAP User |
The Administrative user for the LDAP server. |
cn=orcladmin |
Password File |
The absolute path of a secure file containing the password for the LDAP Admin user. You must provide a password file location, even if you are not changing the configuration. |
/scratch/oam/ldap_passwd |
Properties in the ServiceProviders configProperty: |
Service Provider properties. This section of the move plan is present if Access Manager acts as one of the Service Providers for Mobile and Social. |
|
OAM_server_name |
The URL, with the name of the host and the port number for the Access Manager server. |
http://example.com:14101 |
Properties in the Applications configProperty: |
Applications-related properties. This section of the move plan is present if Access Manager is present as one of the applications for Mobile and Social. |
|
ReturnURL |
The return URL, reflecting the URL for the target Access Manager server. |
example.com:5575 |
Properties in the MultiDataCenter configProperty: |
Multiple data center properties. |
|
ClusterID |
The ID of the cluster. This must be a unique value. It cannot be the same ID as the source cluster. The value in the move plan is blank. |
MyProdCluster |
Table 20-32 describes the move plan properties that you can change for Oracle Adaptive Access Manager. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table 20-32 Move Plan Properties for Oracle Adaptive Access Manager
Property | Description | Sample Value |
---|---|---|
Properties in the ServerConfig configProperty: |
The Oracle Adaptive Access Manager configuration properties. |
|
OAM PrimaryServerHost/Port |
The host name and port number of the primary server for Access Manager. This property is present if Oracle Adaptive Access Manager is integrated with an Access Manager instance. |
example.com:5575 |
OAM Secondary Server Host/Port |
The host name and port number of the secondary server for Access Manager. This property is present if Oracle Adaptive Access Manager is integrated with an Access Manager instance. |
example.com:5560 |
OIM Managed Server Host/Port |
The host name and port number of the Managed Server for Oracle Identity Manager. This property is present if Oracle Adaptive Access Manager is integrated with an Oracle Identity Manager instance. |
example.com:5000 |
OAAM Login URL for OIM |
The host name and port number of Oracle HTTP Server. This property is present if Oracle Adaptive Access Manager is integrated with an Oracle Identity Manager instance. |
example.com:ohsport
|
Webservice URL for OTP UMS Service |
The Web services URL. This property is present in the move plan if OTP User Messaging Service is enabled and use of ParlayX is disabled. |
http://WebserviceURL/endpoint |
Parlayx URL for OTP UMS Service |
The ParlayX URL. This property is present in the move plan if both OTP User Messaging Service and use of ParlayX is enabled. |
http://ParlayxURL/endpoint |
SOAP KeyStore File Location |
The location of the SOAP keystore. This property is present if SOAP Authentication is enabled and the configured SOAP Keystore is not located under the Domain home. Note: If the SOAP Keystore is located under the Domain Home, the SOAP Keystore is migrated to the corresponding location under the Domain Home on the target. |
/scratch/oaam/soapks.ks |
Location for OAAM images folder(Native Integration) |
The location of the Oracle Adaptive Access Manager images folder. This property is present in the move plan if SOAP Tracker is enabled and the configured OAAM image folder is not located under the Domain home. Note: If the OAAM image folder is located under the Domain Home, the images folder is migrated to the corresponding location under the Domain Home on the target. |
/scratch/oaam/oaam_images |
System Config Keystore File Location |
The location of the System Config Keystore. This property is present in the move plan if the System Config Keystore location is configured, but is not located under the Domain home. Note: If the System Config Keystore is located under the Domain Home, the System Config Keystore is migrated to the corresponding location under the Domain Home on the target. |
scratch/KS_loc2 |
System DB Keystore File Location |
The location for the keystore having keys for securing configuration values in the database. This property is present in the move plan if the System DB Keystore location is configured, but is not located under the Domain home. Note: If the System DB Keystore is located under the Domain Home, the System DB Keystore is migrated to the corresponding location under the Domain Home on the target. |
/scratch/KS_loc3 |