Oracle Fusion Middleware provides a series of scripts that you can use to move your environment, for example replicating a test environment to a production environment. The scripts enable you to copy an Oracle home, Oracle WebLogic Server domains and standalone domains, as well as the configuration of certain Oracle Fusion Middleware components, such as Oracle HTTP Server and Oracle SOA Suite. This appendix explains the scripts you can use to move these entities. It also describes the move plan properties that you edit when you move your environment.
Topics:
The movement scripts copy the binary files of an Oracle home and the configuration of a domain and its components from a source environment and paste them at the target environment.
Use these scripts in conjunction with the procedures described in Chapter 20.
Oracle Fusion Middleware uses the following jar file to execute the scripts necessary to move the binary and configuration files:
(UNIX) ORACLE_HOME/oracle_common/jlib/cloningclient.jar (Windows) ORACLE_HOME\oracle_common\jlib\cloningclient.jar
Table A-1 shows the scripts you use to move an Oracle home or a domain and its components.
| TO: | Script | See: |
|---|---|---|
|
Copy the binary files of the source Oracle home |
(UNIX) ORACLE_HOME/oracle_common/bin/copyBinary.sh (Windows) ORACLE_HOME\oracle_common\bin\copyBinary.cmd |
|
|
Apply the copied Oracle home to the target |
(UNIX) ORACLE_HOME/oracle_common/bin/pasteBinary.sh (Windows) ORACLE_HOME\oracle_common\bin\pasteBinary.cmd |
|
|
Copy a WebLogic Server domain and component configuration |
(UNIX) ORACLE_HOME/oracle_common/bin/copyConfig.sh (Windows) ORACLE_HOME\oracle_common\bin\copyConfig.cmd |
|
|
Copy a standalone domain and component configuration |
(UNIX) ORACLE_HOME/oracle_common/bin/copyConfig.sh (Windows) ORACLE_HOME\oracle_common\bin\copyConfig.cmd |
|
|
Copy the Node Manager configuration |
(UNIX) ORACLE_HOME/oracle_common/bin/copyConfig.sh (Windows) ORACLE_HOME\oracle_common\bin\copyConfig.cmd |
|
|
Extract a move plan from the domain or component |
(UNIX) ORACLE_HOME/oracle_common/bin/extractMovePlan.sh (Windows) ORACLE_HOME\oracle_common\bin\extractMovePlan.cmd |
|
|
Apply the copied configuration for the WebLogic Server domain and component configuration to the target |
(UNIX) ORACLE_HOME/oracle_common/bin/pasteConfig.sh (Windows) ORACLE_HOME\oracle_common\bin\pasteConfig.cmd |
|
|
Apply the copied standalone domain and component configuration to the target |
(UNIX) ORACLE_HOME/oracle_common/bin/pasteConfig.sh (Windows) ORACLE_HOME\oracle_common\bin\pasteConfig.cmd |
|
|
Apply the copied configuration for the Node Manager to the target |
(UNIX) ORACLE_HOME/oracle_common/bin/pasteConfig.sh (Windows) ORACLE_HOME\oracle_common\bin\pasteConfig.cmd |
|
|
Generate a file containing an obfuscated password |
(UNIX)ORACLE_HOME/oracle_common/bin/obfuscatePassword.sh (Windows) ORACLE_HOME\oracle_common\bin\obfuscatePassword.cmd Note that Oracle Fusion Middleware also provides an API to generate a file containing an obfuscated password. |
To view the help on any of these scripts, use the -help option. For example:
./pasteConfig.sh -javaHome /scratch/oracle/jdk1.8.0_40 -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.
Note:
If you are using an IBM JDK, set the maximum permanent generation space (-XX:MaxPermSize=value) using the T2P_JAVA_OPTIONS parameter of the copyConfig and pasteConfig scripts.Note:
For the temporary directory, do not provide a path that contains a space.
A Universal Uniform Naming Convention (UNC) path is not supported on Windows. For example, the following is not supported:
\\host_name\oracle\java\win64\jdk8\jre\bin\java
This section contains the following topics:
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 that on Windows, the temp directory path should not contain \x. If it does the scripts fail.
To set the log level using T2P_JAVA_OPTIONS, you can use one of the following:
Specify a configuration file to set the log level. This allows you to set the level for other log files, as well as the movement scripts log files. For example:
setenv T2P_JAVA_OPTIONS -Dt2p.logging.config.file=log_config_file
For example, the log configuration file can contain the following, which sets the level of all loggers to FINE, but sets the level of org.hibernate to FINEST:
#Root logger .level = FINE # Set the level of external loggers. org.hibernate.level = FINEST
Set the log level in the environment variable. For example:
setenv T2P_JAVA_OPTIONS -Dt2p.logging.level=level
The level can be one of the following: OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, ALL.
Alternatively, the -debug option for the scripts sets the log level to FINE if the option is set to false (the default) or to FINEST if the option is set to true.
The precedence is as follows:
The configuration file, set by the environment variable:
setenv T2P_JAVA_OPTIONS -Dt2p.logging.config.file=log_config_file
The log level set by the environment variable:
setenv T2P_JAVA_OPTIONS -Dt2p.logging.level=level
The -debug option on the command line.
The following topics describe the syntax of the movement scripts. The options are described in the tables that follow the syntax.
Notes:
Most options have shortcut names, as described in the tables later in this chapter.
The value of options must not contain a space. For example, on Windows, you cannot pass the following as a value to the -archiveLoc option:
C:\tmp\Archive Files
However, the value of the JavaHome option can contain a space.
On Windows, unless the command prompt uses MKS or another application to support Unix commands, and if the values contain a Windows-specific delimiter, such as an equals sign (=) or comma (,) you must wrap the entire value in double quotation marks ("). For example:
-additionalParams "search.encrypt.key=C:\T2P\encrypt.txt"
The vendor and version of Java used in the javaHome option must match the vendor and version of the JAVA_HOME property defined in the following file (note the period (.) before the filename):
ORACLE_HOME/wlserver/.product.properties
Creates an archive file of the source Oracle home by copying the binary files of that Oracle home, including its WebLogic Server home, into the archive file.
The copyBinary script is located in:
(UNIX) ORACLE_HOME/oracle_common/bin/copyBinary.sh (Windows) ORACLE_HOME\oracle_common\bin\copyBinary.cmd
The syntax is:
copyBinary -javaHome path_of_jdk -archiveLoc archive_location -sourceOracleHomeLoc ORACLE_HOME_location [-logDirLoc log_dir_path] [-silent {true | false}] [-ignoreDiskWarning {true | false}] [-debug {true | false}]
The following example shows how to create an archive of an Oracle home on Linux:
copyBinary.sh -javaHome /scratch/oracle/jdk1.8.0_40
-archiveLoc /tmp/oh_copy.jar
-sourceOracleHomeLoc /scratch/oracle/Oracle_home1
Note:
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 A-2 describes the options for the copyBinary script.
Table A-2 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. Ensure that the archive location is not within the Oracle home structure. |
Mandatory |
|
-sourceOracleHomeLoc |
-soh |
The absolute path of the Oracle home to be archived. You can only specify one Oracle home. |
Mandatory |
|
-invPtrLoc |
-ipl |
This option is deprecated. If you specify it, it will be ignored. On UNIX and Linux, the absolute path to the Oracle Inventory pointer. |
Ignored |
|
-logDirLoc |
-ldl |
The absolute path of a directory. The directory may or may not exist. 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, which is the default. To specify that it does 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 |
|
-debug |
NA |
Sets the log level for the script to provide debugging information. The default is false, which sets the log level to FINE. If you set this to true, the log level is set to FINEST. See Section A.1.1 for other options for setting the log level. |
Applies the archive to the target destination, by pasting the binary files of the source Oracle home to the target environment. You can apply the archive to the same host or a different host.
Before you execute this script, see Section 20.2.4 for information about steps you may need to take to prepare your target environment.
The pasteBinary script is located in:
(UNIX) ORACLE_HOME/oracle_common/bin/pasteBinary.sh (Windows) ORACLE_HOME\oracle_common\bin\pasteBinary.cmd
The syntax is:
pasteBinary -javaHome path_of_jdk -archiveLoc archive_location -targetOracleHomeLoc target_Oracle_Home_location [-targetOracleHomeName Oracle_home_name] [-ouiParam key1=value], key2=value] [-ohAlreadyCloned {true | false}] [-executeSysPrereqs {true | false}] [-invPtrLoc Oracle_InventoryLocation] [-logDirLoc log_dir_path] [-silent {true | false}] [-ignoreDiskWarning {true | false}] [-debug {true | false}]
The following example shows how to apply the archive to the directory /scratch/oracle/Oracle_home_prod, on Linux:
pasteBinary.sh -javaHome /scratch/oracle/jdk1.8.0_40
-archiveLoc /tmp/oh_copy.jar
-targetOracleHomeLoc /scratch/oracle/Oracle_home_prod
-targetOracleHomeName Oracle_home_prod
Table A-3 describes the options for the pasteBinary script.
Table A-3 Options for the pasteBinary 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 with the copyBinary script. The location must exist. This option is mutually exclusive with the -ohAlreadyCloned option. |
Mandatory |
|
-targetOracleHomeLoc |
-toh |
The absolute path of the target Oracle home. Ensure that the Oracle home directory does not exist at that location, or if it does, it is an empty directory. Otherwise, the script returns an error message. The -targetOracleHomeLoc cannot be inside another Oracle home. |
Mandatory |
|
-targetOracleHomeName |
-tohn |
The name for the Oracle home. This name is used to register the Oracle home with Oracle Inventory. Spaces are not allowed in the name. |
Optional |
|
-ouiParam |
-op |
Additional variables to be passed to Oracle Universal Installer, which is run as part of this script. You must pass the variables as key=value pairs. Separate multiple variables with commas. On Windows, surround the entire value pair with double quotation marks ("). |
Optional |
|
-ohAlreadyCloned |
-ohac |
A flag specifying that the script reconfigure an already existing Oracle home that was created using a storage-level cloning tool. If this flag is set to true, then the target Oracle home should exist and it should contain Oracle home binaries. Valid values are You cannot use this option when you use the -archiveLoc option. |
Optional |
|
-executeSysPrereqs |
-esp |
Specifies whether the pasteBinary operation checks the prerequisites of the Oracle home. The default is that it checks the prerequisites. To specify that it does not check the prerequisites, specify this option with the value |
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 register the Oracle homes with the central Oracle inventory specified in the Oracle Inventory pointer file. If the oraInst.loc is not present at default location, you must create this file either at default location as a root user or at any other location as a root or normal user. The following shows an example of the contents of the file: inventory_loc=/scratch/oraInventory inst_group=dba If the directory specified as the inventory_loc does not exist, the operation will create it. You must have write permission to the inventory location. On AIX and Linux, the default location is /etc/oraInst.loc. In other UNIX platforms, the default location is /var/opt/oracle/oraInst.loc This parameter is only supported on UNIX. On Windows, if you specify this parameter, the script returns an error. |
Optional, if the inventory is in the default location. Otherwise, it is mandatory on Linux. |
|
-logDirLoc |
-ldl |
The absolute path of a directory. The directory may or may not exist. 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, which is the default. To specify that it does 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 |
|
-debug |
NA |
Sets the log level for the script to provide debugging information. The default is false, which sets the log level to FINE. If you set this to true, the log level is set to FINEST. See Section A.1.1 for other options for setting the log level. |
Creates a configuration archive that contains the snapshot of the configuration of a WebLogic Server domain. The underlying components of a 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 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_HOME/oracle_common/bin/copyConfig.sh (Windows) ORACLE_HOME\oracle_common\bin\copyConfig.cmd
The syntax is:
copyConfig -javaHome path_of_jdk -archiveLoc archive_location -sourceDomainLoc domain_location -sourceOracleHomeLoc Oracle_home_location -domainHostName domain_host_name -domainPortNum domain_port_number -domainAdminUserName domain_admin_username -domainAdminPasswordFile domain_admin_password_file [-mdsDataExport {true | false}] [-opssDataExport {true | false}] [-trustKeyStoreLoc custom_trust_keystore_path] [-additionalParams property1=value1[, property2=value2] [-logDirLoc log_dir_path] [-silent {true | false}] [-debug {true | false}]
The following example copies the configuration of a WebLogic Server domain:
copyConfig.sh -javaHome /scratch/oracle/jdk1.8.0_40
-archiveLoc /tmp/a.jar
-sourceDomainLoc /scratch/oracle/config/domains/WLS_domain
-sourceOracleHomeLoc /scratch/oracle/Oracle_home1
-domainHostName myhost.example.com
-domainPortNum 7001
-domainAdminUserName weblogic
-domainAdminPasswordFile /home/oracle/password_file.txt
Table A-4 describes the options for the copyConfig script for Oracle WebLogic Server domains.
Table A-4 Options for the copyConfig Script for Oracle WebLogic Server Domains
| 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 |
|
-sourceOracleHomeLoc |
-soh |
The absolute path of the source Oracle 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. If the Administration port is enabled, you must specify an administration port. |
Mandatory |
|
-domainAdminUserName |
-dau |
The name of the administrative user for the domain. |
Mandatory |
|
-domainAdminPasswordFile |
-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. |
Mandatory |
|
-mdsDataExport |
-mde |
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 |
|
-opssDataExport |
-ode |
Specifies whether to export the Oracle Platform Security Services data. The default is true. If this option is set to true, the subsequent pasteConfig script that copies the component to the target imports the Oracle Platform Security Services data to the target. Note: If this option is set to true, you must set the following environment variable before you run the pasteConfig script: CONFIG_JVM_ARGS "-Xmx2048M -Xms2048M" |
Optional |
|
-trustKeyStoreLoc |
-tkl |
The absolute path of the trust keystore location. Use this parameter if the domainPortNum is an SSL port or administration port and the server is configured with CustomIdentityAndCustomTrust or CustomIdentityAndCommandLineTrust keystores. |
Optional |
|
-logDirLoc |
-ldl |
The absolute path of a directory. The directory may or may not exist. 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. You must pass the variables as key=value pairs. Separate multiple variables with commas. On Windows, surround the entire value pair with double quotation marks ("). |
Optional |
|
-silent |
NA |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation, which is the default. To specify that it does prompt for confirmation, specify this option with the value of |
Optional |
|
-debug |
NA |
Sets the log level for the script to provide debugging information. The default is false, which sets the log level to FINE. If you set this to true, the log level is set to FINEST. See Section A.1.1 for other options for setting the log level. |
Optional |
Creates a configuration archive that contains the snapshot of the configuration of a standalone domain. The underlying components of the domain retain their configuration information in different data stores, such as a file system or a database.
You must run the copyConfig script for each domain in the source environment. A configuration archive is created for each source domain.
The copyConfig script is located in:
(UNIX) ORACLE_HOME/oracle_common/bin/copyConfig.sh (Windows) ORACLE_HOME\oracle_common\bin\copyConfig.cmd
The syntax is:
copyConfig -javaHome path_of_jdk -archiveLoc archive_location -sourceDomainLoc domain_location -sourceOracleHomeLoc Oracle_home_location [-additionalParams property1=value1[, property2=value2] [-logDirLoc log_dir_path] [-silent {true | false}] [-debug {true | false}]
The following example copies the configuration of a standalone domain:
copyConfig.sh -javaHome /scratch/oracle/jdk1.8.0_40
-archiveLoc /tmp/a.jar
-sourceDomainLoc /scratch/oracle/config/domains/base_domain
-sourceOracleHomeLoc /scratch/oracle/Oracle_home1/
Table A-4 describes the options for the copyConfig script for standalone domains.
Table A-5 Options for the copyConfig Script for Standalone Domains
| 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 component. Note that on Windows, you should not include a backslash at the end of the path. |
Mandatory |
|
-sourceOracleHomeLoc |
-soh |
The absolute path of the source Oracle home. |
Mandatory |
|
-logDirLoc |
-ldl |
The absolute path of a directory. The directory may or may not exist. 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. You must pass the variables as key=value pairs. Separate multiple variables with commas. On Windows, surround the entire value pair with double quotation marks ("). |
Optional |
|
-silent |
NA |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation, which is the default. To specify that it does prompt for confirmation, specify this option with the value of |
Optional |
|
-debug |
NA |
Sets the log level for the script to provide debugging information. The default is false, which sets the log level to FINE. If you set this to true, the log level is set to FINEST. See Section A.1.1 for other options for setting the log level. |
Creates a configuration archive that contains the snapshot of the configuration of Node Manager.
You must run the copyConfig script for each per host Node Manager in the source environment. A configuration archive is created for each source Node Manager.
Note:
For a per domain Node Manager, you do not need to move it explicitly. It is moved when you move the domain.The copyConfig script is located in:
(UNIX) ORACLE_HOME/oracle_common/bin/copyConfig.sh (Windows) ORACLE_HOME\oracle_common\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}] [-debug {true | false}]
The following example shows how to create a copy of the source Node Manager configuration located in /scratch/oracle/Oracle_home1/wlserver/common/nodemanager:
copyConfig.sh -javaHome /scratch/oracle/jdk1.8.0_40
-archiveLoc /tmp/nm.jar
-sourceNMHomeLoc /scratch/oracle/Oracle_home1/wlserver/common/nodemanager
Table A-6 describes the options for the copyConfig script for Node Manager.
Table A-6 Options for the copyConfig Script for Node Manager
| Options | Shortcut | Description | Mandatory or Optional |
|---|---|---|---|
|
|
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 |
|
|
|
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 absolute path of a directory. The directory may or may not exist. A new log file is created in the directory. The default is the system Temp location. |
Optional |
|
|
NA |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation, which is the default. To specify that it does prompt for confirmation, specify this option with the value of |
Optional |
|
-debug |
NA |
Sets the log level for the script to provide debugging information. The default is false, which sets the log level to FINE. If you set this to true, the log level is set to FINEST. See Section A.1.1 for other options for setting the log level. |
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_HOME/oracle_common/bin/extractMovePlan.sh (Windows) ORACLE_HOME\oracle_common\bin\extractMovePlan.cmd
The syntax is:
extractMovePlan -javaHome path_of_jdk -archiveLoc archive_location -planDirLoc move_plan_directory [-optimizationHints fusionApps,sameSchemaNameSinglePassword, rpdDataSource} [-logDirLoc log_dir_path] [-silent {true | false}] [-debug {true | false}]
The following example extracts the plans from the archive j2ee.jar:
extractMovePlan.sh -javaHome /scratch/oracle/jdk1.8.0_40
-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 example, it might 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
Table A-7 describes the options for the extractMovePlan script:
Table A-7 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 or, if it exists, it is empty. |
Mandatory |
|
-optimizationHints |
-opth |
Specifies the configuration values to auto-populate based on the topology on the target environment. These values are omitted from the move plan. You can use this option in the case of a single archive or multiple archive files. Use of the hints is recommended if they apply to your environment. This option takes the following arguments:
|
Optional |
|
-logDirLoc |
-ldl |
The absolute path of a directory. The directory may or may not exist. A new log file is created in the directory. The default is the system Temp location. |
Optional |
|
|
NA |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation, which is the default. To specify that it does prompt for confirmation, specify this option with the value of |
Optional |
|
-debug |
NA |
Sets the log level for the script to provide debugging information. The default is false, which sets the log level to FINE. If you set this to true, the log level is set to FINEST. See Section A.1.1 for other options for setting the log level. |
For information about the properties in the move plans, and which properties you should edit, see Section A.2.
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 domain 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_HOME/oracle_common/bin/pasteConfig.sh (Windows) ORACLE_HOME\oracle_common\bin\pasteConfig.cmd
The syntax is:
pasteConfig -javaHome path_of_jdk -archiveLoc archive_location -targetDomainLoc trgt_domain_path -targetOracleHomeLoc trgt_Oracle_Home_path -movePlanLoc move_plan_path [-domainAdminUserName domain_admin_username -domainAdminPasswordFile domain_admin_password_file [-appDir WLS_application_directory] [-logDirLoc log_dir_path] [-silent {true | false}] [-debug {true | false}]
The following example shows how to apply the archive of the domain to the Oracle home Oracle_home1:
pasteConfig.sh -javaHome /scratch/oracle/jdk1.8.0_40
-archiveLoc /tmp/java_ee_cl.jar
-targetDomainLoc /scratch/oracle/config/domains/dom_cl
-targetOracleHomeLoc /scratch/oracle/Oracle_home1
-movePlanLoc /scratch/oracle/java_ee/move_plan.xml
-domainAdminPasswordFile /scratch/pwd_dir/pass.txt
-logDirLoc /tmp/log
Note:
If you are moving an environment that includes Oracle JRF, as in an Oracle Fusion Middleware Infrastructure installation, in the move plan, you must specify a different database for the target than is used in the source. The database host, port, service name, and schemas cannot be the same.Table A-8 describes the options for the pasteConfig script for Oracle WebLogic Server domains.
Table A-8 Options for the pasteConfig Script for Oracle WebLogic Server Domains
| 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 directory must not exist or, if it exists, it must be empty. The domain directory may be located outside of the directory structure of the Oracle home. |
Mandatory |
|
-targetOracleHomeLoc |
-toh |
The absolute path of the target Oracle home. It will be used to configure the domain. |
Mandatory |
|
-movePlanLoc |
-mpl |
The absolute path of the updated version of the move plan that was extracted from the source. |
Mandatory |
|
-domainAdminUserName |
-dau |
The name of the administrative user for the target domain. Use this argument if you want a different administrative user on the target than on the source. |
Optional |
|
-domainAdminPasswordFile |
-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. |
Mandatory. |
|
-appDir |
-ad |
The absolute path of the Oracle WebLogic Server application directory on the target. |
Optional |
|
-logDirLoc |
-ldl |
The absolute path of a directory. The directory may or may not exist. 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, which is the default. To specify that it does prompt for confirmation, specify this option with the value of |
Optional |
|
-debug |
NA |
Sets the log level for the script to provide debugging information. The default is false, which sets the log level to FINE. If you set this to true, the log level is set to FINEST. See Section A.1.1 for other options for setting the log level. |
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 domain and the location of the modified move plan. The pasteConfig script re-creates the configuration information for the standalone 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_HOME/oracle_common/bin/pasteConfig.sh (Windows) ORACLE_HOME\oracle_common\bin\pasteConfig.cmd
The syntax is:
pasteConfig -javaHome path_of_jdk -archiveLoc archive_location -targetDomainLoc trgt_domain_path -targetOracleHomeLoc trgt_Oracle_Home_path -movePlanLoc move_plan_path [-appDir WLS_application_directory] [-logDirLoc log_dir_path] [-silent {true | false}] [-debug {true | false}]
The following example shows how to apply the archive of the domain to the Oracle home Oracle_home1:
pasteConfig.sh -javaHome /scratch/oracle/jdk1.8.0_40
-archiveLoc /tmp/java_ee_cl.jar
-targetDomainLoc /scratch/oracle/config/domains/dom_cl
-targetOracleHomeLoc /scratch/oracle/Oracle_home1
-movePlanLoc /scratch/oracle/java_ee/move_plan.xml
-logDirLoc /tmp/log
Table A-8 describes the options for the pasteConfig script for standalone domains.
Table A-9 Options for the pasteConfig Script for Standalone Domains
| 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 directory must not exist or, if it exists, it must be empty. The domain directory may be located outside of the directory structure of the Oracle home. |
Mandatory |
|
-targetOracleHomeLoc |
-toh |
The absolute path of the target Oracle home. It will be used to configure the domain. |
Mandatory |
|
-movePlanLoc |
-mpl |
The absolute path of the updated version of the move plan that was extracted from the source. |
Mandatory |
|
-appDir |
-ad |
The absolute path of the Oracle WebLogic Server application directory on the target. |
Optional |
|
-logDirLoc |
-ldl |
The location of a directory. The directory may or may not exist. 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, which is the default. To specify that it does prompt for confirmation, specify this option with the value of |
Optional |
|
-debug |
NA |
Sets the log level for the script to provide debugging information. The default is false, which sets the log level to FINE. If you set this to true, the log level is set to FINEST. See Section A.1.1 for other options for setting the log level. |
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 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 using the pasteConfig script to apply the archive copy of Node Manager (from the copyConfig script) to the target environment. In addition, the Administration Server must be running.You must run the pasteConfig script for each per host Node Manager in the target environment.
The syntax is:
pasteConfig -javaHome path_of_jdk -archiveLoc archive_location -targetNMHomeLoc trgt_Node_Manager_Home_path -targetOracleHomeLoc trgt_Oracle_Home_path -movePlanLoc move_plan_path [-logDirLoc log_dir_path] [-silent {true | false}] [-debug {true | false}]
The following example shows how to apply the copy of Node Manager to the Node Manager home located in /scratch/Oracle_home1/wlserver/common/nodemanager:
pasteConfig -javaHome /scratch/oracle/jdk1.8.0_40
-archiveLoc /tmp/nm.jar
-targetNMHomeLoc /scratch/oracle/Oracle_home1/wlserver/common/nodemanager
-targetOracleHomeLoc /scratch/oracle/Oracle_home1
-movePlanLoc /scratch/oracle/t2pplans/nm/moveplan.xml
Table A-10 describes the options for the pasteConfig script for Node Manager.
Table A-10 Options for the pasteConfig Script for Node Manager
| Options | Shortcut | Description | Mandatory or Optional |
|---|---|---|---|
|
|
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 |
|
|
|
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 Oracle home that will be used to configure Node Manager. |
Mandatory |
|
|
|
The absolute path of the modified move plan in the target environment. |
Mandatory |
|
|
|
The absolute path of a directory. The directory may or may not exist. A new log file is created in the directory. The default is the system Temp location. |
Optional |
|
|
NA |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation, which is the default. To specify that it does prompt for confirmation, specify this option with the value of |
Optional |
|
-debug |
NA |
Sets the log level for the script to provide debugging information. The default is false, which sets the log level to FINE. If you set this to true, the log level is set to FINEST. See Section A.1.1 for other options for setting the log level. |
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 syntax is:
(UNIX) ORACLE_HOME/oracle_common/bin/obfuscatePassword.sh -javaHome path_to_java_home (Windows) ORACLE_HOME\oracle_common\bin\obfuscatePassword.cmd -javaHome path_to_java_home
The script prompts you to enter the password and the path, including the file name, where the password file is to be written.
Alternatively, you can use an API to generate the obfuscated password file:
Load the following file:
ORACLE_HOME/oracle_common/jlib/obfuscatepassword.jar
Invoke the following API:
oracle.as.t2p.framework.externalutils.ObfuscatePassword.createPasswordFile(String password, String filePath)
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.
This section provides the following topics:
You can modify move plan properties with the scope of READ_WRITE. Do not modify the properties with the scope of READ_ONLY.
Note the following:
Do not add, comment, or remove any section of a move plan.
You must generate a move plan using the extractMovePlan script each time you create an archive, even if you have made no changes to the move plan. If you use a move plan that was created with a different archive, the archive will not be accepted and the pasteConfig script will fail.
If the move plan properties use IP addresses, all of the addresses must use the same IP protocol format. For example, all should use the IPv4 format or all should use the IPv6 format.
The listen address of all servers must use the same format, irrespective of how they are configured in the source file. You can use any of the following formats, but all listen addresses must use the same format:
The actual host name. For example, hostname.domainname
The IPv4 address
The IPv6 address
localhost
All Local Addresses
For the Oracle Coherence configuration to work properly in production mode, you must use the actual host name or the IP address, either IPv6 or IPv4, for all listen addresses in the move plan.
Most move plans contain multiple configGroup elements. When a property is associated with a particular configGroup element, the tables that list the properties group the properties by configGroup element. For example, Table A-13, 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. To use obfuscated passwords, you can use the obfuscatePassword script, as described in Section A.1.2.10.The properties that you edit differ depending on the type of component. Table A-11 provides pointers to the appropriate list of properties for each component.
Table A-11 Move Plan Properties for Components
| Component | Where to find the list of properties: |
|---|---|
|
All Java components and Node Manager |
|
|
Node Manager for standalone domains |
|
|
Oracle ADF connections |
|
|
Oracle B2B and Oracle B2B for Healthcare |
|
|
Oracle Business Activity Monitoring |
|
|
Oracle Coherence |
|
|
Oracle Data Integrator |
|
|
Oracle Enterprise Scheduler |
|
|
Oracle HTTP Server |
|
|
Oracle Managed File Transfer |
|
|
Oracle Service Bus |
|
|
Oracle SOA Suite |
|
|
Oracle Traffic Director |
|
|
Oracle User Messaging Service |
|
|
Oracle Web Services Manager |
|
|
Oracle WebCenter Capture |
|
|
Oracle WebCenter Content Server |
|
|
Oracle WebCenter Content: Imaging |
|
|
Oracle WebCenter Content: Inbound Refinery |
|
|
Oracle WebCenter Content: Records |
Table A-12 describes the move plan properties that you can change for a Node Manager that is configured for a standalone domain. (Additional Node Manager properties for standalone domains and WebLogic Server domains are listed in Table A-13.) Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table A-12 Move Plan Properties for Node Manager in a Standalone Domain
| Property | Description | Sample Value |
|---|---|---|
|
Properties in the NODEMANAGER_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 Manager. |
5557 |
|
Keystores |
The keystores for the Node Manager. Valid values are:
|
DemoIdentityAndDemoTrust |
|
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/Oracle_home1/wlserver/server/lib/example_identity.jks |
|
Custom Identity Keystore Passphrase File |
The absolute path to the secure file containing the custom identity keystore password. If the source environment uses DemoTrust, this property is optional. If left blank, the pasteConfig script displays a warning message and proceeds. If the source environment uses Custom, this property is mandatory. |
/scratch/oracle/i_passwd |
|
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. |
WLS_domain |
|
Domain Location |
The absolute path of the domain location. |
/scratch/oracle/config/domains/WLS_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 File |
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. This property is mandatory. |
weblogic |
|
Node Manager Password File |
The absolute path to the secure file containing the Node Manager user's password. If this property is present, it is mandatory. |
/scratch/oracle/nm_passwd |
|
Node Manager Log File |
The absolute location of the log file for Node Manager. The parent directory must exist. |
/scratch/nodemanager.log |
|
Custom Trust Keystore File |
The absolute path to the secure file containing the custom trust keystore password. This property is present in the move plan only if the config property AdminServer Listen Port represents the SSL port of the server. |
/scratch/oracle/trust_key_passwd |
Table A-13 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 A-13 Common Move Plan Properties for Java Components
| Property | Description | Sample Value |
|---|---|---|
|
Startup Mode |
No change required |
|
|
Properties in the SERVER_CONFIG configGroup: |
Common Java component properties |
|
|
Keystores |
The keystores for all servers. This property is present only once in the move plan and pertains to all servers. If the value is DemoIdentityAndDemoTrust,the other keystore properties in this configGroup will be ignored. In this case, the value of Keystore Type will be |
One of the following: DemoIdentityAndDemoTrust CustomIdentityAndCustomTrust CustomIdentityAndJavaStandardTrust CustomIdentityAndCommandLineTrust |
|
Keystore Type |
The keystore type for all servers. This property is present only once in the move plan and pertains to all servers. |
JKS or KSS |
|
Administration Port |
The port number for the Administration Server. |
7001 |
|
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 front end 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 front end to the server. |
10605 |
|
Frontend HTTPS Port |
The number of the HTTPS Server port. This property is present in the move plan only if the HTTPS Server is set as the front end to the server. |
10606 |
|
Log File Location |
The location of the server log file, if it is not in the default location. |
/scratch/servers/ms1/ms1.log |
|
Unicast Listen Address |
The unicast listen address. This property is present for each server that is configured for unicast. |
10.240.98.232 |
|
Unicast Listen Port |
The unicast listen port. This property is present for each server that is configured for unicast. |
7036 |
|
Default File Store Directory |
Controls the configuration of the default persistent store on the server. The default store maintains its data in a data/store/default directory inside the servername subdirectory of a domain's root directory. You can, however, specify another location for the default store. Note: This property will be populated in the move plan only if it is configured in the source environment and the path is an absolute path. This property is present for each server that is configured for unicast. |
DOMAIN_HOME/servername/data/store/default |
|
Keystore properties |
The following properties are per server. |
|
|
Custom Identity Keystore File |
If the keystore type is JKS, the absolute path of custom identity keystore file location. If the keystore type is KSS, the URI pattern. This property is mandatory if the keystores are not DemoIdentityAndDemoTrus.t. |
JKS: /scratch/keystores/identity.jks KSS: kss://appstripe/keystore |
|
Custom Identity Keystore Passphrase File |
The absolute path to the secure file containing the custom identity keystore password. This property is mandatory if the keystores are not DemoIdentityAndDemoTrust. |
/scratch/oracle/i_passwd.txt |
|
Custom Trust Keystore File |
If the keystore type is JKS, the absolute path of custom trust keystore file location. If the keystore type is KSS, the URI pattern. This property is mandatory if the keystores are CustomIdentityAndCustomTrust or CustomIdentityAndCommandLineTrust. |
JKS: /scratch/keystores/trust.jks KSS: kss://appstripe/keystore |
|
Custom Trust Keystore Passphrase File |
The absolute path to the secure file containing the custom trust keystore password. This property is mandatory if the keystores are CustomIdentityAndCustomTrust. |
/scratch/oracle/key_passwd.txt |
|
Custom Identity Private Key Alias |
The string alias used to store and retrieve the server's private key. This property is mandatory if the keystores are not DemoIdentityAndDemoTrust. |
Identity_key_alias
|
|
Custom Identity Private Key Passphrase File |
The absolute path to the secure file containing the custom identity private key password. This property is mandatory if the keystores are not DemoIdentityAndDemoTrust. |
/scratch/oracle/i_passwd.txt |
|
IdentityKeystoreFileToBeImported |
The absolute path of the identity keystore file (jks file) to be imported to the Keystore service. This property is mandatory if the keystore type is KSS and the keystores are not DemoIdentityAndDemoTrust. |
/scratch/keystores/trust.jks |
|
TrustKeystoreFileToBeImported |
The absolute path of trust keystore file to be imported to the Keystore service. This property is mandatory if the keystore type is KSS and the keystores are CustomIdentityAndCustomTrust. |
alias1_trust,alias2_trust |
|
AliasesToBeImportedFromTrustKeystoreFile |
A comma-separated list of aliases of the entries to be imported from the trust keystore file (specified through the property TrustKeystoreFileToBeImported) to the Keystore service. This property is mandatory if the keystore type is KSS and the keystores are CustomIdentityAndCustomTrust. |
alias1_trust,alias2_trust |
|
PasswordFilesForAliasesToBeImportedFromTrustKeystoreFile |
A comma-separated list of password files containing the aliases (specified through the property AliasesToBeImportedFromTrustKeystoreFile) to be imported from the trust keystore file to Keystore service. This property is mandatory if the keystore type is KSS and the keystores are CustomIdentityAndCustomTrust. |
/scratch/pass/alias1_trust_pass.txt, /scratch/pass/alias2_trust_pass.txt |
|
Network Channel Listen Address |
If you use session replication, the replication channel listen address. |
example.host.com |
|
Network Channel Listen Port |
If you use session replication, the replication channel listen port. |
7005 |
|
Network Channel External Listen Address |
If you use session replication, the external replication channel listen address. |
example.host.com |
|
Network Channel External Listen Port |
If you use session replication, the external replication channel listen port. |
7077 |
|
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 |
|
Frontend HTTPS Port |
The HTTPS port number for the front-end host for the cluster. |
7009 |
|
Properties in the MACHINE_CONFIG configGroup: |
Machine configuration properties |
|
|
Machine Name |
The name of the machine. |
example.com |
|
Node Manager Name |
The name of the node manager. This property will be present in the move plan if the name is different than the Machine Name property. |
example2.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.txt |
|
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 Administering 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 contains the host name, the database port number, and SID. 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.txt |
|
ONS Node List |
The list of Oracle Notification Service (ONS) hosts and ports, in the following format: ons_host1:port1,ons_host2:port2 |
myhost1:6100,myhost2:6101 |
|
ONS Wallet File |
The absolute path to the credential store file, which contains keys and certificates. This property is configured only if SSL is enabled. |
/scratch/wallet |
|
ONS Wallet Password File |
The absolute path to the file containing the password for the wallet. |
/scratch/ons_pass.txt |
|
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.txt |
|
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. |
WLS_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 FILESTORE_CONFIG configGroup |
The configuration for the JMS file store. |
|
|
Directory |
The directory for the JMS file store. If the directory is configured in the source environment to be outside the domain directory or if it is explicitly configured in the source environment and path is absolute (not relative), this property is exposed in the move plan. |
/scratch/fmw/work0304/log/jms |
|
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 file-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.) When you configure the move plan, you can change from a file-based to an LDAP or database-based store. You can only use one type of store. To use one, uncomment the section in the move plan and ensure the other is commented. 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. |
|
|
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.txt |
|
DataSource Name |
The name of the data source. The name cannot contain a slash (/). |
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. |
WLS_domain |
|
Driver Class |
The driver class of the data source. Refer to "Selecting a JDBC Driver" in Administering 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 contains the host name, the database port number, and SID. 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 |
|
PropConnectionURL |
The URL used by the WebUI to connect to the Content Server. |
idc://[IPv6_address:port} |
|
Properties in the RDBMS Security Store configGroup: |
Database-based security store configuration |
|
|
URL |
The URL of the database for the data source. It contains the host name, the database port number, and SID. 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 Administering 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.txt |
|
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 |
|
Properties in the Node Manager Config ConfigGroup |
Node Manager configuration for the Node Manager for the Administration server host. |
|
|
Node Manager Home |
The absolute location of Node Manager. This property is populated if the Node manager type is either ManualNodeManagerSetup or CustomLocationNodeManager. |
/scratch/oracle/domains/base_domain/nodemanager |
|
Node Manager User Name |
The user name for Node Manager. If the Node Manager is per domain or in a custom location, this property is present in the move plan. If Node Manager has been configured manually and you do not specify a value, the pasteConfig script will log an error, but proceed. |
weblogic |
|
Node Manager Password File |
The absolute path to a secure file containing the password for Node Manager. For an Oracle WebLogic Server domain, if Node Manager is per domain or in a custom location and if the user name is the same as the source and you do not provide a password file, the password will default to the Administration password. For an Oracle WebLogic Server domain, if Node Manager is per domain or in a custom location and if the user name is different than the source, this property is mandatory. For a standalone domain, if Node Manager is per domain or in a custom location, this property is mandatory. If Node Manager has been configured manually and if you do not specify a value, the pasteConfig script will log an error, but proceed. |
/scratch/oracle/nm_pass.txt |
|
Node Manager Log File |
The absolute location of the log file for Node Manager, if Node Manager is per domain and the log file is not in the default location. The parent directory must exist. |
/scratch/nodemanager.log |
|
The following properties are populated if the Node Manager type is not ManualNodeManagerSetup, and the Listen Address and Listen Port are not populated in the MACHINE_CONFIG configGroup. |
||
|
Listen Address |
The Listen address of Node Manager. |
example.com |
|
Listen Port |
The number of the Listen port of Node Manager. |
5557 |
|
The following properties are populated if the Secure Listener property in nodemanager.properties is present and not true and the Node Manager type is not ManualNodeManagerSetup. |
||
|
Keystores |
The keystores for the Node Manager. Valid values are:
|
DemoIdentityAndDemoTrust |
|
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. During pasteConfig, this property will be ignored if the keystore type is DemoIdentityAndDemoTrust. |
/scratch/oracle/identity.jks or if Custom Identity Keystore type is KSS: kss:appstripe/keystore |
|
Custom Identity Keystore Passphrase File |
The absolute path to the secure file containing the custom identity keystore password. If the source environment uses DemoTrust, this property is optional. If left blank, the pasteConfig script shows a warning message and proceeds. If the source environment uses Custom, this parameter is mandatory. During pasteConfig, this property will be ignored if the keystore type is DemoIdentityAndDemoTrust. |
/scratch/oracle/i_passwd.txt |
|
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. During pasteConfig, this property will be ignored if the keystore type is DemoIdentityAndDemoTrust. |
identity_key_alias |
|
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. During pasteConfig, this property will be ignored if the keystore type is DemoIdentityAndDemoTrust. |
/scratch/oracle/key_passwd |
|
The following property is populated in the move plan if the Node Manager type is not ManualNodeManagerSetup and the CustomIdentityKeyStoreType property in nodemanager.properties is present and is KSS. |
Note that the CustomIdentityKeyStoreType value can be only KSS in a JRF domain and the Node Manager type is PerDomainNodeManager. |
|
|
IdentityKeystoreFileToBeImported |
The absolute path of the identity keystore file (.jks file) to be imported to the Keystore Service. This property is mandatory if the keystore type is KSS and the keystores are not DemoIdentityAndDemoTrust. |
/scratch/keystores/trust.jks |
Table A-14 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 A-14 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 are 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 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 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 |
|
Oracle Web Center Content |
OBJECT_NAME_PROPERTY type is Oracle WebCenter Content - Web UI |
|
|
PropConnectionURL |
The URL used by the WebUI to connect to the Content Server. |
idc://[IPv6_address:port} |
Table A-15 describes the move plan properties that you can change for Oracle Coherence. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table A-15 Move Plan Properties for Oracle Coherence
| Property | Description | Example |
|---|---|---|
|
Properties in the COHERENCE_SERVER_CONFIG configGroup |
The configuration of Oracle Coherence servers. |
|
|
Unicast Listen Address |
The unicast listen address. This property is not present in the move plan if the value is localhost or a loopback address or the value is empty. |
10.240.98.232 |
|
Unicast Listen Port |
The unicast listen port. |
7036 |
|
Properties in the COHERENCE_CLUSTER_CONFIG configGroup |
The configuration of Oracle Coherence clusters. |
|
|
Custom Cluster Configuration File |
An external custom configuration file used to configure this cluster. |
/scratch/external_custome_config.xml |
|
Multicast Listen Address |
The multicast listen address. If the clustering mode is not unicast, this property is present in the move plan. |
224.12.1.0 |
|
Cluster Listen Port |
The cluster listen port. |
12100 |
|
Listen Address |
The listen address for the Well Known Address Name configuration property. |
|
|
Properties in the SERVER_TEMPLATES_CONFIG configGroup |
If server templates are configured, then these properties will be exposed if the coherence cluster configuration is overridden in the server templates. |
|
|
Unicast Listen Address |
The unicast listen address. This property is not present in the move plan if the value is localhost or a loopback address or the value is empty. |
10.240.98.232 |
|
Unicast Listen Port |
The unicast listen port. |
7036 |
Table A-16 describes the move plan properties that you can change for Oracle Web Services Manager. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment. Do not edit the value of the configProperty id.
Table A-16 Move Plan Properties for Oracle Web Services Manager
| Property | Description | Sample Value |
|---|---|---|
|
Properties in the bootstrap.configmanager componentType |
The bootstrap properties used by the Oracle Web Services Manager agent to connect to the Oracle Web Services Manager Policy Manager. |
|
|
pm.url |
The URL of the policy manager. If you are using the same policy manager in the target environment as in the source environment, you do not need to modify this property. |
t3://example.com:7003 |
|
keystore.path |
The keystore path. This can be an absolute path or a path relative to the DOMAIN_HOME/config/fmwconfig directory. |
/scratch/oracle/domains/domain_name/config/fmwconfig/default-keystore.jks
|
|
truststore.path |
The truststore path. This can be an absolute path or a path relative to the DOMAIN_HOME/config/fmwconfig directory. |
/scratch/oracle/domains/domain_name/config/fmwconfig/default-keystore.jks
|
|
Properties in the wsm.respository componentType |
The Oracle Web Services Manager repository configuration in the move plan if the Policy Manager is installed in the domain. However, if you set the -mdsDataExport parameter of the copyConfig script to false, this component type will not be present in the move plan. This component will not be present if wsm-pm is not installed in the domain. |
|
|
Properties in the configurations configGroup |
The domain configuration. This configGroup is present in the move plan if applications or domains are registered in the source environment or domain configuration documents are created on the source environment. There is one configGroup per domain. |
|
|
domain |
The domain name of the context for which a configuration document is created in the repository. This property is present in the move plan when you have made changes to the default configuration for a particular context. If you do not modify this property, the configurations properties will have same context as on source environment. |
domain1 |
|
KerberosLoginModule:principal |
The name of the principal to be used. |
HOST/localhost@example.com |
|
KerberosLoginModule:key.tab |
The path to the keytab to get the secret key for the principal. This can be an absolute path or a path relative to the DOMAIN_HOME/config/fmwconfig directory. |
./mylocation/krb5.keytab |
|
ConfigManager:pm.url |
The URL that specifies the location of the policy accessor. |
t3://host.example.com:7003 |
|
ConfigManager:keystore.path |
The path to the keystore. This can be an absolute path or a path relative to the DOMAIN_HOME/config/fmwconfig directory. |
./mylocation/mykeystore.jks |
|
ConfigManager:truststore.path |
The truststore path. This can be an absolute path or a path relative to the DOMAIN_HOME/config/fmwconfig directory. |
/mylocation/mykeystore.jks |
|
KeystoreConfig:location |
The location of the keystore used for message protection. This can be an absolute path or a path relative to the DOMAIN_HOME/config/fmwconfig directory. |
mycustomlocation/key.tab |
|
Properties in the policysets configGroup |
The configuration of policy sets. This configGroup is present in the move plan if policy sets have been created in the source environment. |
|
|
attach To |
The scope of the policy sets. If the attachTo expression scope is DOMAIN or DOMAIN term, this property is present in the move plan. However, if it is |
domain1 |
|
Properties in the policies configGroup |
The configuration of policies. This configGroup is present in the move plan if policies with assertions have been modified in the source environment.There can be multiple configGroups, one for each policy. The ID attribute is the name of the policy for which configGroup is created. |
|
|
wsdl-uri |
The actual endpoint URI of the WSDL. |
http://host:port/sts?wsdl
|
|
port-uri |
The actual endpoint URI of the STS port. |
http://host:port/sts-service |
|
sts.auth.service.principal.name |
The name of the principal that should be used by the service. |
HOST/localhost@EXAMPLE.COM |
|
sts.auth.keytab.location |
The location of the client's keytab file. This property is present when Security Token Service (STS) is configured with Kerberos tokens. |
mycustomlocation/key.tab |
|
sts.auth.caller.principal.name |
Client's principal name. |
testuser |
|
service.principal.name |
The name of the principal that should be used by the service. |
HOST/localhost@EXAMPLE.COM |
|
caller.principal.name |
Client's principal name. |
testuser |
|
keytab.location |
The location of the client's keytab file. |
mycustomlocation/key.tab |
Table A-17 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 Listen.
Table A-17 Move Plan Properties for Oracle HTTP Server
| Property | Description | Sample Value |
|---|---|---|
|
Properties in the httpd.conf configGroup |
The overall configuration. These properties correspond to properties in the httpd.conf file |
|
|
Listen |
The Listen address. It can include the host name and port or just the port. |
orcl3.example.com:8888 or 8888 |
|
ServerName |
The name of the server for Oracle HTTP Server or its URL. If the host does not have a registered DNS name, use the IP address. |
orcl1.example.com http://host.example.com:2222 |
|
Allow |
Controls which hosts can access an area of the server. Valid values are |
from all |
|
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 |
|
DocumentRoot |
The directory that stores the main content for the Web site. |
/scratch/oracle/base_domain/config/fmwconfig/components/OHS/instances/ohs_1/htdocs |
|
SSLWallet |
The location of the SSL wallet, if the wallet is not in the default location. |
/scratch/oracle/base_domain/config/fmwconfig/components/OHS/ohs_1/keystores/mywallets |
|
Properties in the ssl.conf configGroup |
The SSL configuration. These properties correspond to properties in the ssl.conf file. |
|
|
Listen |
The Listen address for SSL. It can include the host name and port or just the port. |
orcl3.example.com:4443 or 4443 |
|
VirtualHost |
The name of the virtual host. The port number listed should also be listed in the Listen property. |
*.4443 |
|
Properties in the admin.conf configGroup |
The administration configuration. These properties correspond to properties in the admin.conf file. |
|
|
Listen |
The Listen address. It can include the host name and port or just the port. |
orcl3.example.com:8888 or 8888 |
|
VirtualHost |
The name of the virtual host. The port number listed should also be listed in the Listen property. |
orcl3.example.com:8888 |
|
Allow |
Controls which hosts can access an area of the server. Valid values are |
from all |
|
Properties in the mod_wl_ohs configGroup |
The mod_wl_ohs configuration. These properties correspond to properties in the mod_wl_ohs.conf file. |
|
|
WebLogicCluster |
A comma-separated list of the host name and port of Managed Servers in the cluster |
host.example.com:8002,host.example.com:8003 |
|
MatchExpression |
A parameter that allows you to modify the values of existing parameters or add a new parameter for a particular configuration. |
/integration/worklistapp WebLogicHost=host.example.com|WebLogicPort=23446
|
|
Properties in the webgate.conf configGroup |
The webgate configuration. These properties correspond to properties in the webgate.conf file. |
|
|
WebGateInstalldir |
The location of the WebGate installation directory, as specified in the webgate.conf file. |
/scratch/oracle/oh_home/Oracle_OAMWebGate1/webgate/ohs |
|
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/" |
|
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 |
|
Properties in the dads.conf configGroup |
The configuration parameters for the PL/SQL database access descriptor. These properties correspond to properties in the dads.conf file. |
|
|
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.txt |
|
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 |
Table A-18 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 A-18 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 A-19 describes the move plan properties that you can change for Oracle Business Activity Monitoring. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table A-19 Move Plan Properties for Oracle Business Activity Monitoring
| Property | Description | Sample Value |
|---|---|---|
|
ApplicationURL |
The URL for Oracle BAM web applications and Oracle BAM Server. Note that you do not need to update this value, unless the Oracle BAM web applications and Oracle BAM Server are deployed on separate hosts. |
http://DEFAULT:0000 |
|
DURABLE_SUBSCRIBER_NAME |
The durable subscriber name to be used for the EMS sample value. |
myDURABLE_SUBSCRIBER_NAME |
|
INITIAL_CONTEXT_FACTORY |
The initial context factory to be used for the EMS sample value. |
weblogic.jndi.WLInitialContextFactory |
|
JNDI_URL |
The JNDI URL for EMS. |
t3://example.com:7001 |
|
JNDI_USERNAME |
The JNDI user name. |
myJMSUserName |
|
JNDI_PASSWORD_FILE |
The absolute path of a secure file containing the password. You must provide a password file, even if you are not changing the configuration. |
/scratch/pass/jndi_pass.txt |
|
JMS_USERNAME |
The JMS user name. |
user1 |
|
JMS_PASSWORD_FILE |
The absolute path of a secure file containing the password. You must provide a password file, even if you are not changing the configuration. |
/scratch/pass/jms_pass.txt |
Table A-20 describes the move plan properties that you can change for Oracle Service Bus. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table A-20 Move Plan Properties for Oracle Service Bus
| Property | Description | Sample Value |
|---|---|---|
|
osb.configuration.passphrase.file |
The absolute path to the passphrase file. The file must be accessible on the target environment. This property is required if you passed the osb.configuration.passphrase.file to the copyConfig script using the -additionalParams option. The passphrase must be the same as the one for the source environment. |
/scratch/passwd/osb_passwd.txt |
Table A-21 describes the move plan properties that you can change for Oracle User Messaging Service. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Note that you also edit the properties in Table A-13. If you upgraded Oracle User Messaging Service from 11g, you must change the User property for the data source from prefix_ORASDPM to prefix_UMS. See the task "Upgrade the Schema" in Upgrading Oracle SOA Suite and Business Process Management.
Table A-21 Move Plan Properties for Oracle User Messaging Service
| Property | Description | Sample Value |
|---|---|---|
|
Properties for the componentType UMS: |
These properties apply to all driver types. |
|
|
DefaultSenderAddress |
The default address of the sender. If the UMS Message has no Sender Address of the specific DeliveryType that the driver supports, then the driver may use the DefaultSenderAddress as the Sender Address. |
SMS:1234 |
|
SenderAddresses |
The list of sender addresses that the driver is configured to handle. A driver with specified SenderAdresses will be selected only for an outgoing message that has a matching Sender Address. A driver that has not specified any SenderAdresses is considered to be able to handle any outgoing message regardless of the Sender Address of the message. The list should consist of UMS addresses separated by comma. The matching is case insensitive. |
EMAIL:alice@example.com,EMAIL:bob@example.com. |
|
Properties in the EmailDriver componentType: |
These properties apply to email drivers. |
|
|
IncomingMailServer |
The host name of the incoming mail server. |
usmdemo.example.com |
|
IncomingMailServerPort |
Port number of IMAP4 (that is, 143 or 993) or POP3 (that is, 110 or 995) server. |
110 |
|
IncomingUserIDs |
The list of user names of the mail accounts from which the driver instance is polling. Each name must be separated by a comma, for example, user1,user2. |
username.pop3@umsdemo.example.com
|
|
IncomingMailIDs |
The email addresses corresponding to the user names. Each email address is separated by a comma and must reside in the same position in the list as its corresponding user name appears on the usernames list. |
username.pop3@umsdemo.example.com
|
|
IncomingUserPasswords |
The absolute path of a secure file containing the password. You must provide a password file, even if you are not changing the configuration. The file contains a list of passwords corresponding to the user names. Each password is separated by a comma and must reside in the same position in the list as their corresponding user name appears on the usernames list. |
/scratch/oracle/ums_in_passwd.txt |
|
OutgoingMailServer |
The name of the SMTP server. |
usmdemo.example.com |
|
OutgoingMailServerPort |
The port number of the SMTP server. |
25 |
|
OutgoingDefaultFromAddr |
The default FROM address (if one is not provided in the outgoing message). |
username.pop3@umsdemo.example.com
|
|
OutgoingUsername |
The user name used for SMTP authentication. |
username.pop3@umsdemo.example.com
|
|
OutgoingPassword |
The absolute path of a secure file containing the password used for SMTP authentication. This is required only if SMTP authentication is supported by the SMTP server. You must provide a password file, even if you are not changing the configuration. The file includes the type of password (choose from Indirect Password/Create New User, Indirect Password/Use Existing User, and Use Cleartext Password) and Password.) |
/scratch/oracle/ums_out_passwd.txt |
|
Properties in the ExtensionEndpoint configGroup: |
These properties apply to extension drivers. |
|
|
EndpointURL |
Remote endpoint listener URL |
http://hostname:7001/integrationtest-war/extension |
|
mappedDomain |
The extension endpoint used to deliver messages where the domain part of the recipient URI matches this value. |
test |
|
Properties in the SMPPDriver componentType: |
These properties apply to SMPP drivers. |
|
|
SmsAccountId |
The Account Identifier on the SMS-C. |
myusername |
|
SmsServerHost |
The name (or IP address) of the SMS-C server. |
example_host |
|
TransmitterSystemId |
The account ID that is used to send messages. |
myusername |
|
ReceiverSystemId |
The account ID that is used to receive messages. |
myusername |
|
TransmitterSystemType |
The type of transmitter system. |
Logica |
|
ReceiverSystemType |
The type of receiver system. |
Logica |
|
ServerTransmitterPort |
The TCP port number of the transmitter server. |
9001 |
|
ServerReceiverPort |
The TCP port number of the receiver server. |
9001 |
|
TransmitterSystemPassword |
The absolute path of a secure file containing the password of the transmitter system You must provide a password file, even if you are not changing the configuration. The file contains the type of password. Valid values are: Indirect Password/Create New User, Indirect Password/Use Existing User, and Use Cleartext Password) and Password. |
/scratch/oracle/ums_trans_passwd.txt |
|
ReceiverSystemPassword |
The absolute path of a secure file containing the password of the receiver system You must provide a password file, even if you are not changing the configuration. The file contains the type of password. Valid values are: Indirect Password/Create New User, Indirect Password/Use Existing User, and Use Cleartext Password) and Password.) |
/scratch/oracle/ums_rec_passwd.txt |
|
Properties in the XMPPDriver componentType: |
These properties apply to XMPP drivers. |
|
|
IMServerHost |
The Jabber/XMPP server host name. |
example.domain.com |
|
IMServerPort |
The corresponding Jabber/XMPP server port. The default is 5222. |
5222 |
|
IMServerUsername |
The Jabber/XMPP user name with which you log in. You may also enter a complete Jabber ID if its domain name is different from the Jabber/XMPP server host name. |
myUserName@xmpp-domain
|
|
IMServerPassword |
The absolute path of a secure file containing the corresponding password for the IMServerUsername. You must provide a password file, even if you are not changing the configuration. The file contains the type of password. Valid values are: Indirect Password/Create New User, Indirect Password/Use Existing User, Use Cleartext Password) and Password.) |
/scratch/oracle/ums_im_passwd.txt |
|
Properties in the TwitterDriver componentType |
The properties for the Twitter driver. |
|
|
Authentication Mode |
The authentication mode that the Twitter driver must use. Valid values are OAuth and xAuth. |
OAuth |
|
Username |
The user name of the Twitter user. |
MrSmith |
|
Password |
The password of the Twitter user. |
password
|
|
ConsumerKey |
The public key of the Twitter user. |
Kr7px6KavOphOGLHQxa91W |
|
ConsumerSecret |
The private key of the Twitter user. |
ezDK6Ky9tIBxqMDIAPm752nFzIBdqgJF5Q4G9Bzotu |
|
Access Token |
The public key of a registered Twitter application. |
1091745185-SVKSxv7PFsBrFgSrywnqylWp3ANr8aS9QRMohnj |
|
Access Token Secret |
The private key of a registered Twitter application. |
Q1PcWeDTVhaKH3DhJ9ilk1osXAtfXwXR257JEiqeYu |
Table A-22 describes the move plan properties that you can change for Oracle B2B and Oracle B2B for Healthcare. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment You can also change contacts and identifiers.
Table A-22 Move Plan Properties for Oracle B2B and Oracle B2B for Healthcare
| Property | Description | Sample Value |
|---|---|---|
|
Property in the B2B System Parameters configGroup: |
B2B system parameter configuration. |
|
|
Callout Directory |
The absolute path of the Callout directory. |
/tmp/calloutDirectory |
|
Large PayLoad Directory |
The absolute path of the large payload directory. |
/tmp |
|
SMTP Host |
The host name of the SMTP server in the enterprise to send the negative MDN to the trading partner for an AS1 exchange. |
host.example.com
|
|
Webservice policy |
The URI for the security policy used to secure the Web service. |
oracle/wss_username_token_service_policy |
|
SSL Private Key Password |
The absolute path of a secure file containing the password. If a password file is not provided, the value will not be set in target. |
/tmp/passwordfile/sslpwd.txt |
|
Properties in the Channel ConfigGroup: |
Properties related to channels. |
|
|
Encryption Alias |
The alias for your encryption key. If you use these properties, make sure that the Keystore Location and Keystore Password properties are provided. |
example |
|
Signature Alias |
The alias for the digital signature key. |
acne2Key |
|
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-password |
The absolute path of a secure file containing the password. If a password file is not provided, the value will not be set in target.The source configuration will be retained. |
/tmp/password/pass.txt |
|
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 Enter this on one line. |
|
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-password |
The absolute path of a secure file containing the password. If a password file is not provided, the value will not be set in target.The source configuration will be retained. |
/tmp/password/pass.txt |
|
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-password |
The absolute path of a secure file containing the password. If a password file is not provided, the value will not be set in target.The source configuration will be retained. |
/tmp/password/pass.txt |
|
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 |
|
as2-param-Receipt-Delivery-Option |
The fully qualified HTTP URL. |
http://example:8001/b2b/httpReceiver |
|
Properties for the SFTP transport protocol: |
The SFTP configuration. |
|
|
sftp-param-password |
The absolute path of a secure file containing the password. If a password file is not provided, the value will not be set in target.The source configuration will be retained. |
/tmp/password/pass.txt |
|
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-password |
The absolute path of a secure file containing the password. If a password file is not provided, the value will not be set in target.The source configuration will be retained. |
/tmp/password/pass.txt |
|
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-password |
The absolute path of a secure file containing the password. If a password file is not provided, the value will not be set in target.The source configuration will be retained. |
/tmp/password/pass.txt |
|
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 |
|
Properties in the B2B Identifiers ConfigGroup: |
Properties for B2B identifiers. The move plan can contain one or more than one B2B identifiers. Each identifier can contain one Trading Partner and one or more identifiers belonging to that Trading Partner. See the table "Identifier Types Defined in Oracle B2B" in the User's Guide for Oracle B2B. |
|
|
B2B_identifier |
The B2B Identifier for the Trading Partner. |
MyPartner |
|
Properties in the B2B Contacts Information ConfigGroup: |
Properties for B2B contact information. Each Trading Partner has one or more contacts. |
|
|
Contact Name |
The name of the contact. |
gcemail@email.com |
|
Properties in the B2B Keystore Details ConfigGroup: |
Properties related to the B2B keystore. |
|
|
Keystore Location |
The absolute path of the keystore. |
/scratch/b2b/keystore/keystore.jks |
|
Keystore Password |
The absolute path of a secure file containing the password used for the keystore authentication.You must provide a password file, even if you are not changing the configuration. |
/tmp/oracle/pwd/ks_pwd.txt |
Table A-23 describes the move plan properties that you can change for Oracle Enterprise Scheduler. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment. The move plan can also contain properties that you have defined in your source environment. Modify any READ_WRITE properties with values that are valid for the target environment.
Table A-23 Move Plan Properties for Oracle Enterprise Scheduler
| Property | Description | Sample Value |
|---|---|---|
|
Properties in the ESS_CONFIG_XML configGroup: |
Configuration properties for Oracle Enterprise Scheduler |
|
|
RequestFileDirectory |
The directory for request and log output. |
/tmp/ess/RequestFileDirectory |
|
RequestFileDirectoryShared |
A flag indicating whether the request file directory is shared. Valid values are |
false |
|
Properties in the ESS_ADF_DOMAIN_CONFIG configGroup: |
Properties configured in adf-domain-config.xml, to assist Oracle Enterprise Scheduler request output and post processing. |
|
|
essappFilePersistenceMode |
The file persistence mode for storing the output of request execution. |
file |
|
essappRequestFileDirectory |
The directory for request and log output for the Oracle Enterprise Scheduler application. |
/tmp/ess/MyRFD |
|
essappCallbackClientSecurityPolicyURI |
The security policy URI 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 |
|
umsAppInternalHost |
The UMS Server NotificationServiceURL host name. |
example.domain.com
|
|
umsAppInternalPort |
The UMS Server NotificationServiceURL port. |
10999 |
|
umsAppInternalProtocol |
The UMS Server NotificationServiceURL protocol. |
http |
|
ucmAppInternalSamlTokenPolicyURI |
The SAML Policy URI. |
|
Table A-24 describes the move plan properties that you can change for Oracle Managed File Transfer. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table A-24 Move Plan Properties for Oracle Managed File Transfer
| Property | Description | Sample Value |
|---|---|---|
|
Properties in the MFT System Properties configGroup: |
The system properties configuration |
|
|
Server Properties |
Server properties |
|
|
Payload Storage Directory |
The full path to the file system location where files being transferred are stored. |
/scratch/oracle/mft/storage |
|
Callout Directory |
The location where custom callouts are stored. |
/scratch/oracle/mft/callouts |
|
External Address |
The external IP address or host name of the load balancer. If the load balancer is not being used, then it can refer to any external address with which payload references can be sent to customers. |
host.example.com |
|
Internal Address |
The internal IP address or host name of the load balancer. If the load balancer is not being used, it can refer to any internal address with which payload references can be sent to customers. |
host.example.com |
|
KeyStore Properties |
The keystore properties |
|
|
Default Keystore Password File |
The absolute path of a secure file that contains the password for the default keystore. |
/scratch/oracle/t2p/mft_db_pass.txt |
|
Default Keystore Private Key Password File |
The absolute path of a secure file that contains the password for the default keystore private key. |
/scratch/oracle/t2p/mft_pvt_pass.txt |
|
SSH Keystore Private Key Password File |
The absolute path of a secure file that contains the password for the SSH keystore private key. |
/scratch/oracle/t2p/mft_ssh_pass.txt |
|
PGP Keystore Private Key Password File |
The absolute path of a secure file that contains the password for the PGP keystore private key. |
/scratch/oracle/t2p/mft_pgp_pass.txt |
|
Embedded Server Properties |
Properties for embedded FTP and sFTP servers. |
|
|
Embedded Server Root Directory |
The root directory location for the embedded FTP and sFTP servers. |
$DOMAIN_HOME/mft/ftp_root |
|
Domains Properties |
The configuration properties for the domain. |
|
|
Domain Alias |
The alias for the domain. It is used to refer to the domain details while configuring the source or target. |
B2B Remote |
|
Connection URL |
The URL for connecting to the domain. |
t3://localhost:7001 |
|
User Name |
The user name for the domain. |
weblogic |
|
Password File |
The absolute path of a secure file that contains the password for the domain. |
/scratch/oracle/t2p/mft_dom_pass.txt |
|
Type |
The domain type: B2B, Healthcare, SOA, Service Bus, or ODI. |
B2B |
Table A-25 describes the move plan properties that you can change for Oracle Traffic Director. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table A-25 Move Plan Properties for Oracle Traffic Director
| Property | Description | Sample Value |
|---|---|---|
|
Property in the http-listener configGroup: |
HTTP listener configuration |
|
|
Ip |
The IP Address of the HTTP listener or an asterisk (*) |
* |
|
Port |
The port number of the HTTP listener |
7001 |
|
ServerName |
The server name of the HTTP listener The plan is extracted during the extractMovePlan script. |
hostname.example.com
|
|
Property in the tcp-listener configGroup: |
TCP listener configuration |
|
|
Ip |
The IP Address of the TCP listener or an asterisk (*) |
* |
|
Port |
The port number of the TCP listener |
7001 |
|
Property in the origin-server-pool configGroup: |
The origin server pool configuration |
|
|
origin-server-n |
The location of the origin server. You may have more than one server. |
hostname.example.com:port |
|
Property in the failover configGroup: |
Failover configuration |
|
|
virtual-ip |
The virtual IP address. |
ip_address
|
Table A-26 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 A-26 Move Plan Properties for WebCenter Content Server, Records, and Inbound Refinery
| Property | Description | Sample Value |
|---|---|---|
|
Properties in componentType |
The componentType is Content Server, or Inbound Refinery. |
|
|
MoveType |
The flag indicating whether to copy the entire source system instance, including configuration and data, or to create a new content server instance, based on the source system configuration. Valid values are This property is not applicable to Inbound Refinery. |
copy |
|
Properties in the copy configGroup: |
Copy the configuration and data. Use these properties when you use the MoveType of |
|
|
IntradocDir |
The path to the Intradoc directory. The directory value can begin with the string |
/scratch/oracle/config/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/oracle/config/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/oracle/config/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/oracle/config/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 (|). If the source uses IPv6, update this property with the IPv6 address. In addition, you must update the Listen Address for all servers and the PropConnectionURL with the IPv6 address. |
127.0.0.1|0.0.0.0.0.0.0.1
or for IPv6:
*.*.*.*|IPv6_address
|
|
Properties in the init configGroup: |
Create a new instance with the configuration of the source. Use these properties when you use the MoveType of |
|
|
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 A-27 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 A-27 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 A-28 describes the move plan properties that you can change for Oracle WebCenter Capture. Edit all properties, such as host names, port numbers, listen addresses, that have different values in the target environment.
Table A-28 Move Plan Properties for Oracle WebCenter Capture
| Property | Description | Sample Value |
|---|---|---|
|
oracle.odc.importprocessor.email.connection_retries |
Determines the number of connection retries, if the initial attempt to connect to an email server fails. When not specified, the default value is 0 (connections are not retried). |
0 |
|
oracle.odc.importprocessor.email.operation_timeout |
After connecting to an email server, this timeout (in milliseconds) applies to all other email server-related functions. |
6000 |
|
oracle.odc.emailbroadcast.smtp_userid |
User ID for the capture SMTP server |
username
|
|
oracle.odc.emailbroadcast.smtp_message_from |
The name which will appear in the |
username
|
|
oracle.odc.orphaned_import_token_check_interval |
Frequency (in seconds) to check for orphaned import tokens. |
60 |
|
oracle.odc.gd_font_path |
For Unix systems, specify the location of the Unix font directory. This path is used by the PDF Image Only Export driver to render the fonts for PDF documents. |
/usr/share/X11/fonts |
|
oracle.odc.offlinejob_processing_delay |
The length of time in minutes to wait before checking to see if an offline job is back online and ready to process. |
5 |
|
oracle.odc.max_processing_attempts |
The number of retry attempts that will be made before putting a batch that has failed to process into an error state. |
5 |
|
oracle.odc.audit_ids |
A comma-delimited list of action IDs of events that will be audited. See "Auditing Capture" in Administering Oracle WebCenter Enterprise Capture for a list of valid IDs. |
1001,1004,1005,1006,1011,1014,2001,2002,2003 |
|
oracle.odc.importprocessor.email.buffer_size |
The buffer size of messages that are fetched from the server. |
262144 |
|
oracle.odc.systemid |
A unique identifier used to identify the Capture system within an organization. |
Capture_01 |
|
oracle.odc.importprocessor.email.javamail_debug |
Enables JavaMail debugging output, which is placed into the server's .out log file when set to true. (When not specified, the default value is false.) |
false |
|
oracle.odc.poll_for_client_bundles |
The frequency, in seconds, to check for updated client bundles. |
30 |
|
oracle.odc.days_to_retain_batches |
The Default Days to Retain Batches, which is the number of days that the cache will be maintained on client workstations. If a batch is locked, it will not be deleted. Batches that are older than this value will be purged when the client application is loaded. |
3 |
|
oracle.odc.max_property_updates_t2p |
The maximum number of custom properties that can be modified in a T2P operation. |
1 |
|
oracle.odc.import_token_expiration |
The number of minutes before an import processor token is considered expired. |
5 |
|
oracle.odc.import_job_refresh_interval |
The Import Job Refresh Interval, which is the time, in seconds, of how often an internal timer will fire to check for import jobs that need to be processed. |
60 |
|
oracle.odc.emailbroadcast.smtp_ssl |
Indicates whether the Valid values are |
1 |
|
oracle.odc.emailbroadcast.smtp_start_tls |
Indicates whether the SMTP server should start TLS. Valid values are |
1 |
|
oracle.odc.doc_conversion_max_paper_size_oit |
A string representing the maximum paper size to use when images are created with the document conversion processor. Valid values separated by commas are as follows: A1, A2, A3, A4, LETTER, LEGAL, LEDGER |
LETTER |
|
oracle.odc.importprocessor.email.connection_timeout |
The timeout period (in milliseconds) that Capture will wait to establish a connection to the email server. When not specified, the default value is 120000 (2 minutes). |
6000 |
|
oracle.odc.emailbroadcast.smtp_host |
The host name of the email server that will be used to send out system related messages. |
test@example.com |
|
oracle.odc.emailbroadcast.smtp_port |
The port number of the SMTP host. |
80 |
|
oracle.odc.max_batch_search_rows |
The default value for the maximum number of batches that will be returned in a batch search. |
100 |
Table A-29 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 A-29 Move Plan Properties for Oracle Data Integrator
| Property | Description | Sample Value |
|---|---|---|
|
Properties in the Master Repository configGroup: |
Master repository configuration |
|
|
Url |
JDBC URL for connecting to the master repository. |
jdbc:oracle:thin:@localhost:1522:orcl |
|
Schema name |
The name of the schema in the target database where the target ODI repository will be created. |
odi_master_12c |
|
Schema password file |
The absolute path of a secure file that contains the password for the schema. |
/scratch/oracle/odi_schema_passwd.txt |
|
SUPERVISOR user |
The name of the ODI user SUPERVISOR. |
SUPERVISOR |
|
SUPERVISOR password file |
The absolute path of a secure file that contains the password for the ODI user SUPERVISOR. |
/scratch/oracle/odi_passwd.txt |
|
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. |
jdbc:oracle:thin:@localhost:1521/example.com |
|
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.txt |
|
Properties in the Agents configProperty: |
Agents configuration |
|
|
Host name |
The Agent host name. |
localhost |
|
Host port |
The Agent host port number. |
12311 |
|
Properties in the Work Repositories configProperty: |
Work repositories configuration |
|
|
Url |
JDBC URL for connecting to the work repository. |
jdbc:oracle:thin:@localhost:1521/example.com |
|
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.txt |