| Oracle® Fusion Applications Administrator's Guide 11g Release 6 Refresh 4 (11.1.6) Part Number E14496-14 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Administrator's Guide 11g Release 6 Refresh 4 (11.1.6) Part Number E14496-14 |
|
|
PDF · Mobi · ePub |
Content movement" refers to the transfer of Fusion Applications components, configurations, and/or data from one environment to another. This chapter focuses on copying components from a test environment to a production environment. Test-to-production content movement differs from full cloning in that source transaction data is not retained on the production system.
This chapter contains the following topics:
Section 20.1, "Introduction to Test-to-Production Content Movement"
Section 20.2, "Understanding Test-to-Production Movement Operations"
Section 20.4, "Test to Production Content Movement Using Command-Line Scripts"
This chapter describes the most common scenario for moving an installation of Oracle Fusion Applications from one environment to another: the movement from a test to a production system. The process requires a combination of reinstallation (of the transaction Oracle Database and the Oracle Identity Management components) with a transfer of seed data, required user information, and the Oracle home directories and configuration files. The result is a destination environment that matches the source environment without having required you to install and reconfigure the system from scratch.
The movement steps are accomplished using various tools, which differ depending on the situation.
When using command-line scripts to perform test to production, it is helpful to review the concepts and technical requirements. See Section 20.2, "Understanding Test-to-Production Movement Operations" and Section 20.3, "General Prerequisites". Thereafter, there are three core pieces of the movement:
Install a fresh transactional database and seed it with core data from the source (Section 20.3.2);
Install a fresh Oracle Identity Management and use scripts to rewire so it matches the source Oracle Identity Management (Section 20.3.3);
Use command-line scripts to move the rest of the Fusion Applications installation Section 20.4. Note that small installations that have all the Fusion Applications components on machine, will use a somewhat simplified procedure.
This section gives an overview of what components are moved, what is not retained on the destination, and what must be configured before you begin component movement.
Although installations of Fusion Applications differ, it can be helpful to have an sample topography for reference purposes. The scenario depicted in Table 20-1 shows an installation with Supply Chain Management products installed. The Administration Servers of the Oracle WebLogic Server domains and all the system component instances run on the multiple hosts.
Table 20-1 Sample Oracle Fusion Supply Chain Management Topology
| System Component/Tier/Domain | Host in the Domain | Applications, Managed Servers, and System Components Running on the Host |
|---|---|---|
|
Web Tier |
|
OHS |
|
Oracle Identity Management Tier |
|
Oracle Identity Management components:
|
|
Mid Tier ( |
|
Oracle BI EE applications:
Oracle BI EE components:
|
|
Mid Tier ( |
|
|
|
Mid Tier ( |
|
|
|
Mid Tier ( |
|
|
|
Mid Tier ( |
|
|
|
Mid Tier ( |
|
|
|
Mid Tier ( |
|
|
|
Mid Tier ( |
|
|
|
Oracle Database Tier |
|
The following artifacts are copied from the source and retained on the destination environment:
Transaction database schemas, seed data, and configurations
Oracle Identity Management configurations
Oracle WebLogic Server domain configurations, stored in the file system
System component configurations, stored in the file system
Configurations and metadata stored in the Oracle Metadata Services (MDS), such as Oracle Application Development Framework (Oracle ADF) connections and service-oriented architecture (SOA) composites
Configurations and metadata stored in component-specific schemas outside of MDS
Non-user-related layer customizations, such as Site and Enterprise Layer, in MDS
Security artifacts created by the Oracle Fusion Applications Provisioning framework, such as application IDs and policies
Functional setup data
Note:
On Oracle HTTP Server (OHS), the contents of document root are moved as part of OHS movement, as they are part of application data.
Following are some of the artifacts that are not retained in the destination environment, because they are presumed to be test data only, and not needed:
Transactional data (assumed to be test transactions)
Standing data, such as customers, supplies, and items
Transient data, such as job status and process status
Content data, such as Oracle WebCenter Content data, wiki pages and discussion forums (These can be moved using data movement tools if necessary.)
Note:
If the WebCenter Portal Discussions feature was used in the source environment and the Discussions data that was generated must be moved to the destination, it is possible to do so. See Section 20.4.2.7.6 for details.
Any configuration or metadata associated with individual users on the source, such as:
Users in the identity store (assumed to be test users and therefore not moved)
User layer customizations in MDS
Component configurations associated with specific users, such as Oracle Human Workflow work groups
MDS sandboxes
All test-to-production movements begin with planning and preparing the environments. Section 20.3.1 outlines how to check your source configurations, ensure your destination environment meets basic requirements, and set up meaningful log levels for tracking your progress.
All test-to-production movements also require that an Oracle transaction database and an Oracle Identity Management system be installed and configured on destination hosts. Section 20.3.2 and Section 20.3.3 explain how this is done.
Moving your Oracle Fusion Applications components and configurations successfully requires that your source and destination topologies be configured correctly.
To prepare, perform the following tasks:
When moving an Oracle Fusion Applications installation, the movement scripts and instructions assume that the source environment is fully installed, configured, and functional. Specifically, this means:
The source transaction database was installed and the required schemas were created and seeded with data.
See the "Installing a Transaction Database" chapter in the Oracle Fusion Applications Installation Guide, if necessary.
The source Oracle Identity Management environment was installed and configured.
See the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management (Oracle Fusion Applications Edition) for details, if necessary.
The desired product families were installed through Oracle Fusion Applications provisioning.
See the Oracle Fusion Applications Installation Guide for details, if necessary.
The source setup data was created using Oracle Fusion Functional Setup Manager.
See the Oracle Fusion Functional Setup Manager User's Guide for details, if necessary.
Any required extensions and customizations were applied to the source environment.
See the Oracle Fusion Applications Extensibility Guide for details, if necessary.
If the Oracle Business Intelligence (BI) repository has been edited, the final repository file was uploaded through Fusion Applications Control before beginning the movement tasks.
See the "Configuring Repositories" chapter of the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition for details, if necessary.
All necessary patches were applied and the system was tested and found functional.
Note:
If you are upgrading from a RUP1 or RUP2 version of Fusion Applications, you will need to add two properties to the FUSION_prov.properties file to ensure successful test-to-production movement. Add OAM_ACCESS_SERVER_HOST and OAM_ACCESS_SERVER_PORT, along with their values, to the properties file.
Additional assumptions about the source and destination environments are as follows:
The environments must share the same operating system and platform architecture (number of bits). For example, you cannot move from a Microsoft Windows source to a UNIX target, nor from a 32-bit platform to a 64-bit platform.
The environment topologies must match.
The Oracle Fusion Applications domain name cannot be changed in the source environment nor during the movement tasks.
If the partition feature is activated in the source environment and the partition configuration is not using preexisting tablespaces owned by the SEARCHSYS schema, then you must create the same tablespace in the Oracle Secure Enterprise Search (Oracle SES) database of the target environment before invoking pasteConfig.
See the "Partitioning for Parallel Query" section in the Oracle Secure Enterprise Search Administration API Guide.
If Secure Sockets Layer (SSL) is required for communication with the Managed Servers, create the identity keystores and trust keystores for the middle tier Managed Servers and Node Manager.
See the "Creating the Identity Keystore on CRMHOST2" section in the Oracle Fusion Applications Customer Relationship Management Enterprise Deployment Guide.
Oracle Fusion Applications movement has a default logging level of INFO. Before running the various movement scripts, it can be helpful to set the logs to a finer level of detail.
To do so, set the T2P_JAVA_OPTIONS variable to include the following:
-Dt2p.logging.level=log_level
where log_level is one of the following (ordered from least- to most verbose):
SEVERE WARNING CONFIG FINE FINER FINEST ALL
Alternatively, it is possible to set -debug true at the command line. This is equivalent to setting the log_level to FINE.
Note:
If the -debug flag is used, and for any reason a step of the test-to-production movement fails, be aware that the incomplete archive created will not be automatically deleted. To re-start content movement, you must manually delete the incomplete archive.
To move the Oracle transaction database schemas and seed data from the source to the destination environment, perform the following tasks:
Test-to-production data movement begins with an exact clone of the source (test) database which is reworked to become a fresh production database.
NOTE: It is best to use matching database topographies. For example, if the source database is on Oracle RAC with four instances, it is best to configure a four-instance Oracle RAC destination database as well. See Section 19.4 for tips on handling movement completion if the RAC installations differ between source and target.
To create the destination database:
Perform the first two steps of installing a blank transaction Oracle database on the destination server, as described in the "Installing a Transaction Database" chapter in the Oracle Fusion Applications Installation Guide. Briefly, these steps use a Graphical User Interface (GUI) to guide you through creating the database file structure and uploading the Oracle Database itself.
The third step— installing schemas and seed data— was handled through the Oracle Fusion Applications Repository Creation Utility (RCU) in the source installation. In a movement scenario, you will NOT run the RCU from the GUI. Instead:
Create a clone of the source database (RMAN is suggested) and mount the clone to the new destination database.
Perform Task 2, "Run Scripts to Scrub the Destination Database". (Section 20.2.3 describes that data that will be removed or reworked.)
Note:
The T2PDataUtil tool is supported from Linux/Windows only. For Windows platforms, run the utility from Windows. For all Unix platforms, you must run the utility from Linux.
See NOTE at the end of this task if you encounter a failure message in Windows.
Use the following database utility to clean up the destination database for production:
On the source database server, from an operating system command prompt, navigate to the location of the T2PDataUtil executable:
(UNIX) FA_ORACLE_HOME/lcm/t2p/bin (Windows) FA_ORACLE_HOME\lcm\t2p\bin
FA_ORACLE_HOME is a directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home.
Run the T2PDataUtil script from the source to copy the relevant schemas, etc.:
(UNIX) T2PDataUtil.sh -dbhost host -dbsid sid -dbport port -mdir move_directory -command generate_move_data (Windows) T2PDataUtil.cmd -dbhost host -dbsid sid -dbport port -mdir move_directory -command generate_move_data
The following table describes the parameters for the T2PDataUtil command for the source environment:
| Parameters | Description |
|---|---|
|
|
The Oracle Database host name |
|
|
The Service Name for the Oracle Database |
|
|
The listen port number for the Oracle Database |
|
|
The directory where the move data will be placed. If this option is not specified, the (UNIX) FA_ORACLE_HOME/lcm/t2p/movedata (Windows) FA_ORACLE_HOME\lcm\t2p\movedata |
|
|
The command to execute. Enter |
|
-ldir |
Directory for log data output. |
Run the T2PDataUtil script on the destination. Ensure the move data specified in -mdir option in Step 2 is accessible by the script.
(UNIX) T2PDataUtil.sh -dbhost host -dbsid sid -dbport port mdir move_directory -command apply_move_data -arh /tmp/apps_rcu_home (Windows) T2PDataUtil.cmd -dbhost host -dbsid sid -dbport port -mdir move_directory -command apply_move_data -arh C:\tmp\apps_rcu_home
The following table describes the parameters for the T2PDataUtil command for the target environment:
| Parameters | Description |
|---|---|
|
|
The Oracle Database host name |
|
|
The Service Name for the Oracle Database |
|
|
The listen port number for the Oracle Database |
|
|
The directory where the move data was placed. If this option is not specified, the (UNIX) FA_ORACLE_HOME/lcm/t2p/movedata (Windows) FA_ORACLE_HOME\lcm\t2p\movedata |
|
|
The command to execute. Enter |
|
|
The Oracle Fusion Applications Repository Creation Utility location. |
|
-ldir |
Directory for log data output. |
When RMAN backup is complete, set the logs to "NO ARCHIVE LOG MODE".
Note:
If you encounter the following Windows error message-- error in creating database file-- do the following:
Bounce the database.
Rename all search-related DBF files: SEARCH_DATA_1.DBF, SEARCH_INDEX_1.DBF, and SEARCH_TEMP_1.DBF
Retry.
Oracle Identity Management handles users— their information, authentication, and access policies. Such data is required by various Oracle Fusion Applications products to function; therefore, the Oracle Identity Management system must be configured before the rest of the components can be moved. To accomplish this, you must have Oracle Identity Management installed, configured and working on the source environment, and have a second installation prepared on the destination environment.
Artifacts created by Oracle Fusion Applications provisioning in the source domain are distributed across the following Oracle Identity Management products:
Oracle Internet Directory (used as the identity store and policy store)
Oracle Virtual Directory (used as the identity store)
Oracle Access Manager
Oracle Identity Manager
Oracle Identity Federation
This section describes how to use the following scripts and properties files to transfer the various users, groups, roles, passwords, and system artifacts from the source environment to the destination.
Use the CopyIDM and PasteIMD scripts and associated properties files. This will move the artifacts from the Policy and Credentials stores, the Oracle Access Manager, and the Oracle Identity Manager. See Section 20.3.3.1.
Use the updateADF scripts and associated properties files. This will move the passwords and user names accessed internally by Oracle ADF functionality. See Section 20.3.3.2.
Use the MoveIDM script and associated properties files. This allows you to review the CSF entries created in the destination environment, and to insert user names and passwords for additional component security. See Section 20.3.3.3.
Note:
Data security policies are moved with the Functional Setup Manager. The business object name associated for data security is Application Data Security Policy.
For more information about moving data security policies, see the following documentation:
Section 20.4.4 for further information about how to move data Oracle Fusion Applications security policies using Functional Setup Manager export and import functions.
The "Moving Common Reference Objects" section in the "Importing and Exporting Setup Data" chapter in the Oracle Fusion Applications Common Implementation Guide to understand data security policy migration
The "Importing and Exporting Setup Data" chapter in the Oracle Fusion Functional Setup Manager Developer's Guide for information about moving setup data
To move the artifacts from the Policy and Credentials stores, the Oracle Access Manager, and the Oracle Identity Manager, perform the following tasks:
IDM.Properties FileCreate a text file and give it a meaningful name, such as IDM.properties.txt.
Populate the file with the following properties. Example values are given; replace these with the appropriate values for your source environment.
SOURCE_IDSTORE_HOST=example.com SOURCE_IDSTORE_PORT=3060 SOURCE_IDSTORE_BINDDN=cn=admin SOURCE_IDSTORE_PASSWD=password SOURCE_IDSTORE_SEARCHBASE=dc=us,dc=oracle,dc=com IDSTORE_READONLYUSER=cn=IDROUser,cn=Users,dc=us,dc=oracle,dc=com IDSTORE_READWRITEUSER=cn=IDRWUser,cn=Users,dc=us,dc=oracle,dc=com IDSTORE_SUPERUSER=cn=FAAdmin,cn=Users,dc=us,dc=oracle,dc=com SOURCE_WLSHOST=example.com SOURCE_WLS_ADMIN_PORT=17001 SOURCE_WLS_MANAGED_PORT=14000 SOURCE_WLS_ADMIN_USER=oim_admin SOURCE_WLS_ADMIN_PASSWD=password SOURCE_ARCHIVE_LOCATION=/net/example//scratch/work/oim/oim_home OPSS_POLICYSTORE_HOST=example.com OPSS_POLICYSTORE_PORT=3060 OID_ADMIN_USER=cn=oid_admin OID_ADMIN_PASSWORD=password OPSS_POLICYSTORE_JPSROOT=cn=FAPolicies
Note:
For security reasons, be sure to delete/destroy the properties files after completing all the movement tasks.
This task can be run from either the source Oracle Identity Management host or from another Fusion Applications source host. The result of running the CopyIDM script is the production of an /idmfat2p_data.zip file in a target directory, which must be located on the source Oracle Identity Management host.
Set the JAVA_HOME and APPTOP parameters before running CopyIDM.
Locate the required JAR files. You will need to enter the corresponding paths to each JAR file in the command line when running the CopyIDM script.
Run CopyIDM using the following syntax (on Unix):
Note:
For Windows, replace all colons (:) with semi-colons (;) in the classpath.
java -classpath T2PAutomation.jar:cloningclient.jar:ldapjclnt11.jar:obfuscatepassword.jar:ojmisc.jar:weblogic.jar:ldifloadtool.jar:idmfatools.jar:idmfatesttoproduction.jar:args4j-2.0.9.jar oracle.t2p.automation.T2PAutomationMain -archive archiveLocation -task CopyIDM -props prop_file -workdir working_dir
Create a text file and give it a meaningful name, such as PasteIDM.txt, on the destination Oracle Identity Management host.
Populate the file with the following properties relevant to the destination site. Example values are given; replace these with the appropriate values for your destination (target) environment.
OPSS_POLICYSTORE_HOST=example.com OPSS_POLICYSTORE_PORT=3060 OID_ADMIN_USER=cn=ooid_admin OID_ADMIN_PASSWORD=password OPSS_POLICYSTORE_JPSROOT=cn=FAPolicies TARGET_IDSTORE_HOST=example.com TARGET_IDSTORE_PORT=3060 TARGET_IDSTORE_BINDDN=cn=id_admin TARGET_IDSTORE_PASSWD=password TARGET_IDSTORE_SEARCHBASE=dc=us,dc=oracle,dc=com TARGET_WLSHOST=example.com TARGET_WLS_ADMIN_PORT=7001 TARGET_WLS_MANAGED_PORT=14000 TARGET_WLS_ADMIN_USER=oid_admin TARGET_WLS_ADMIN_PASSWD=password TARGET_WLS_ADMIN_PORT_OIM=17001 TARGET_WLS_ADMIN_USER_OIM=oim_admin TARGET_WLS_ADMIN_PASSWD_OIM=password TARGET_POLICYSTORE_DOMAIN=FusionDomain TARGET_ARCHIVE_LOCATION=/net/adcdat11//scratch/aime/work/oim/oim_home
Note:
For security reasons, be sure to delete/destroy the properties files after completing the movement tasks.
This task must be run on the destination IDM host. Before triggering the PasteIDM script, it is necessary to set the WebLogic Server user and password environmental variables. This is because during PasteIDM, the Oracle Internet Directory server is restarted and these credentials will be used.
Set JAVA_HOME, and set up credentials for the Administration Server, using environmental variables such as the following:
WLS_USER=oid_admin WLS_PW=password APPTOP=/u01
Run PasteIDM with the following syntax (on Unix):
Note:
For Windows, replace all colons (:) with semi-colons (;) in the classpath.
java -classpath T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar:ldifloadtool.jar:idmfatools.jar:args4j-2.0.9.jar:jps-mbeans.jar:weblogic.jar:idmfatesttoproduction.jar:pwdgen.jar:jps-api.jar:ldapjclnt11.jar:wlclient.jar:wljmxclient.jar: oracle.t2p.automation.T2PAutomationMain -task PasteIDM -props prop_file -workdir workingdir
Use Oracle Identity Manager to reconcile records from the identity store.
To reconcile records from the identity store:
Sign in to Oracle Identity Manager.
Click Advanced, then the System Management tab, and then Scheduler. Alternatively, you can click the Search Scheduled Jobs link on the Welcome screen.
Run each of the following scheduled tasks by selecting it and clicking Run Now. You must run one job at a time in the following sequence and wait for each job to complete successfully before running the next one:
Fusion Applications Role Category Seeding
LDAP Role Create and Update Full Reconciliation
LDAP Role Hierarchy Full Reconciliation
LDAP User Create and Update Full Reconciliation
LDAP Role Membership Full Reconciliation
The Application Developer Framework (ADF) credentials are used internally by the Oracle Identity Management components to communicate with each other. For security reasons, use the following process to update those internal credentials on the destination host.
Access the t2padfcreds.properties file.
Review the sample file, then edit the path to js_config.xml. Entering the ADF and CSF map names is optional.
Sample t2padfcreds.properties file:
# ADF credentials update #Name of the ADF map in the LDAP, optional property. adf.map.name=ADF #Name of the CSF map in the LDAP, optional property. csf.map.name=oracle.apps.security # This location will have the jps_config.xml, mandatory property. jps.config.location=/scratch/aime/name/t2p/work # Optional Cleanup properties #Remove the supplied jps-config.xml file on successful update. delete.config.file=false #Following properties not needed to be in the properties file as they are optional properties to override default behavior. #Map ADF keys to CSF keys, optional property, file to override default mapping. adf.csf.mapping.file=mapping properties file, for example: key-mapping.properties #CSF key suffix, optional, if the suffix in the CSF store is different. #Keeping RHS value empty will disable suffix mechanism and ADF key name will be the same as CSF key name without additional suffix. csf.key.suffix=-KEY
Access the jps_config.xml file.
Review the file and edit the necessary fields (marked with a bold asterisk*).
Sample jps_config.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<jpsConfig xmlns="http://xmlns.example.com/oracleas/schema/11/jps-config-11_1.xsd">
<serviceProviders>
<serviceProvider type="CREDENTIAL_STORE" name="ldap.credentialstore.provider" class="oracle.security.jps.internal.credstore.ldap.LdapCredentialStoreProvider" />
<serviceProvider class="oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider" name="credstoressp" type="CREDENTIAL_STORE">
<description>SecretStore-based CSF provider</description>
</serviceProvider>
</serviceProviders>
<serviceInstances>
<serviceInstance name="credstore_instance" provider="ldap.credentialstore.provider">
<property name="idstore.type" value="OID" />
* <property name="security.principal" value="cn=admin" />
* <property name="security.credential" value="password" />
* <property name="ldap.url" value="ldap://hostname:port" />
<property name="oracle.security.jps.ldap.root.name" value="cn=FAPolicies" />
<property name="oracle.security.jps.farm.name" value="cn=FusionDomain" />
</serviceInstance>
*<serviceInstance location="$APPTOP/instance/domains/primordial host/CommonDomain/config/fmwconfig/bootstrap" provider="credstoressp">
*<property name="location" value="/"APPLICATIONS_CONFIG/domains/host/CommonDomain/config/fmwconfig/bootstrap>
</serviceInstance>
</serviceInstances>
<jpsContexts default="default">
<jpsContext name="default">
<serviceInstanceRef ref="credstore_instance" />
</jpsContext>
<jpsContext name="bootstrap_credstore_context">
<serviceInstanceRef ref="bootstrap.credstore" />
</jpsContext>
</jpsContexts>
</jpsConfig>
The result of running this task is that the ADF credentials are read from the CSF store and written to the ADF store in the destination LDAP. It is an internal process for component use.
Note: Set APPTOP before running the UpdateADF Script.
Use the following syntax (on Unix):
Note:
For Windows, replace all colons (:) with semi-colons (;) in the classpath.
java -classpath T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar:customtasks.jar:jdom.jar:ldifloadtool.jar:APPLICATIONS_BASE/fusionapps/oracle_common/modules/oracle.jps_11.1.1/jps-manifest.jar oracle.t2p.automation.T2PAutomationMain -task UpdateADFCreds -props Properties_File -workdir working_dir
To update the Credential Store Framework (CSF) in the destination environment, perform the following tasks:
Create a text file and give it a meaningful name, such as MoveIDM.properties.txt.
Include the following parameters, with values that match your destination environment. The AdminURL corresponds to the host name and port of the Administration Server for the Oracle Identity Management domain, or IDMDomain.
#Mandatory properties. Connection info for IDM domain. AdminUser=fusion_apps_admin AdminPassword=password AdminURL=t3://hostname:port #Script location, must be the absolute path to scripts folder, inclusive. scripts-folder=/scratch/aime/work/t2p/scripts
Note:
For security reasons, be sure to delete/destroy the properties files after completing the movement tasks.
These files contain the properties for the CSF entries and are located in the /scripts directory. The are titled csf_maps.properties and csf_passwords.properties. See Table 20-2 for credentials descriptions. Edit the files to match your destination environment.
Note:
In the csf_passwords.properties, many entries take the form of user:password pairs, separated by a colon (:). If a user name or password includes a colon, use double back slashes (\\) to escape having it parsed.
Table 20-2 CSF Entries to Modify
| Map | Key | Description |
|---|---|---|
|
|
|
This entry stores the username used to log onto the GRCC server for Oracle Governance, Risk and Compliance Controls. |
|
|
|
This entry stores the password used to log onto the GRCC server for Oracle Governance, Risk and Compliance Controls. |
|
|
|
This entry stores the |
|
|
|
Oracle Fusion database credentials |
|
|
|
This entry stores the schema password for Oracle BI Scheduler schema. |
|
|
|
User credentials for the patch MDS SOA schema |
|
|
|
User credentials for the patch MDS SOA schema |
|
|
|
User credentials for the patch MDS SOA schema |
|
|
|
User credentials for the patch MDS Oracle Enterprise Scheduler schema |
|
|
|
User credentials for the patch MDS schema |
|
|
|
User credentials for the patch MDS Oracle WebCenter Portal Spaces schema |
|
|
|
Oracle Data Integrator schema credentials |
|
|
|
User credentials for the patch MDS SOA schema |
|
|
|
The credential for the |
|
|
|
The credential for the |
|
|
|
User credentials for patch |
|
|
|
User credentials for patching to connect to the Identity Store. Currently, this credential is a read-write user supplied to provisioning. |
|
|
|
User credentials for patching to connect the Policy Store |
|
|
|
User credentials for Oracle WebLogic Server administrator |
|
|
|
User credentials for Oracle WebLogic Server Node Manager |
|
|
|
User credentials for the patch MDS SOA schema |
|
|
|
User credentials for the patch MDS SOA schema |
|
|
|
User credentials for the patch MDS SOA schema |
|
|
|
User credentials for the patch MDS SOA schema |
|
|
|
Oracle SES data source credentials. Provide user name and password. Use the database connection string of the target environment for the user name in this format: host:port:database_service_name The password is the dummy value |
|
|
|
Oracle Data Integrator schema credentials |
|
|
|
Oracle WebLogic Server user credentials key. This credential corresponds to the user name and password of bootstrap credential, |
|
|
|
User credential for specifying which keystore alias to use for encrypting the message. Both |
|
|
|
The user credentials for the PeopleSoft Enterprise Application web service SOAP interaction. The user credentials corresponds to the PeopleSoft Enterprise Application application user with access privileges to invoke the PeopleSoft Application web service |
|
|
|
The credentials of the external service for the supplier synchronization service (integration) |
|
|
|
The Primavera P6 administration super user credentials designated for use with the integration between Oracle Fusion Projects Portfolio Management and Oracle Primavera P6 Enterprise Project Portfolio Management (P6 EPPM). |
|
|
|
User credential is for specifying the password of the |
|
|
|
User credential is for specifying which keystore alias to use for signing the message. Both |
This task can be run only on the source Fusion Applications host, as it requires access to"%APPLTOP%\fusionapps\oracle_common\common\bin\wlst.cmd"
Set APPTOP. Then run the script with the following syntax (on Unix):
Note:
For Windows, replace all colons (:) with semi-colons (;) in the classpath.
java -classpath T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain -task MoveIDM -props prop_file -workdir working_dir
See Table 20-3 for details.
Table 20-3 Options for the MoveIDM Command
| Options | Description |
|---|---|
|
|
The dependent library files containing classes required to run the command. Use the following value for the T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain |
|
|
The command to execute. Enter |
|
|
The absolute path to the MoveIDM properties file name. See Task 0 for details. The
|
|
|
The directory used for log files and any other temporary files generated by the automation framework. The log files are located at |
Note that when using the command line, the movement of the Oracle home directories (also known as the "binary files") and the configuration files in the Oracle Fusion Applications environment requires different steps depending on the installation:
For distributed environments, where the Oracle Fusion Applications components are installed on multiple machines, multiple movement scripts are provided;
For non-distributed environments, where the Oracle Fusion Applications components are installed on a single machine, a simplified script is provided.
Note:
For the purpose of visualization, this chapter pictures an installation topography of three or more servers.
It places the transaction Oracle Database on one machine, the Oracle Identity Management components on a second, and the rest of the Oracle Fusion Applications components (i.e. WebLogic Server domains, executables, and system component instances) on either one (non-distributed) or multiple (distributed) machines.
Source and destination topologies must match for a successful movement.
Whether the source environment is distributed or non-distributed, the necessary movement tasks include:
Installing a transaction Oracle Database on a destination server and moving database schemas and seed data (Section 20.3.2)
Installing an Oracle Identity Management system on a destination server and moving the Oracle Identity Management artifacts, OR upgrading an existing Oracle Identity Management system to work with Oracle Fusion Applications (Section 20.3.3)
Moving the Oracle Fusion Application binary files and configuration files. In the standard distributed installations, this is a two-part movement, described in Section 20.4.1 and Section 20.4.2.
In non-distributed QA environments, this movement is simplified (Section 20.4.3).
Moving the Functional Setup Data, required in both distributed and non-distributed scenarios (Section 20.4.4),
Completing post-movement tasks, required in both distributed and non-distributed scenarios (Section 20.4.5).
Moving installed binary files and patches in the Middleware home of an Oracle Fusion Applications source environment to a production target environment requires the use of a set of scripts. For more information, see the "Movement Scripts" section in the Oracle Fusion Middleware Administrator's Guide.
If you have a non-distributed QA environment, whereby the Administration Servers of all the domains and all the system component instances run on the same host, you can automate moving the binary files with a different set of scripts than those described in this section. For more information, see Section 20.4.3.
Notes:
If you want to create obfuscated password files for use with these scripts, use the following scripts:
(UNIX) FA_MW_HOME/oracle_common/bin/obfuscatePassword.sh (Windows) FA_MW_HOME\oracle_common\bin\obfuscatePassword.cmd
These interactive scripts prompt you to enter your password and the location of the password file to be written.
The Java version should be at least 1.6.04.
As shown in Figure 20-1, you can use the copyBinary script to copy the source Middleware home into an archive file, then use the pasteBinary script to apply the archive to the target environment.
Because the binary files are in shared storage and are shared by all Oracle Fusion Applications domains, copyBinary must be performed only once from the primordial machine and pasteBinary only once on the target primordial machine.
To move binary files in the Oracle Fusion Applications environment:
Create the binary archives by running the copyBinary script for each Middleware home in the source environment. See Section 20.4.1.1.
Apply the copied binary files from the source environment to the target environment by running the pasteBinary script in the target environment. See Section 20.4.1.2.
Manually move the Oracle Database installation from the source environment to the target environment. See Section 20.4.1.3.
Run the copyBinary script for each Middleware home in the source environment. This copies the binary files of each Middleware home, including all of its Oracle homes and its Oracle WebLogic Server home, into an archive file.
The copyBinary script is available in the following fusionapps Middleware directories:
(UNIX) FA_MW_HOME/oracle_common/bin (Windows) FA_MW_HOME\oracle_common\bin
Note:
The Oracle homes in the Middleware home must share the same platform architecture (in terms of number of bits). The copyBinary script does not support a mix of 32-bit and 64-bit Oracle homes.
When you run the script, you must specify a Java home of the same number of bits as the Oracle homes. For example, for 64-bit Oracle homes, you must specify a 64-bit Java home.
Before you create the binary archive of a Middleware home, ensure that the Oracle WebLogic Server product directories are installed in the Middleware home. Oracle WebLogic Server installed outside of Middleware home is not supported.
In a Windows environment, before creating an archive of a Middleware home, ensure that no Java or Oracle WebLogic Server processes are running from that Middleware home.
Use the following syntax to run the copyBinary script:
copyBinary -javaHome path_of_jdk -archiveLoc archive_location -sourceMWHomeLoc MW_HOME [-invPtrLoc Oracle_InventoryLocation] [-logDirLoc log_dir_path] [-silent {true | false}] [-ignoreDiskWarning {true | false}]
The following example shows how to create an archive of a Middleware home on UNIX:
copyBinary.sh -javaHome USER_HOME/jrockit_160_04
-archiveLoc /FIN_T2P/FIN_clone1.jar
-sourceMWHomeLoc /net/mount1/appbase/fusionapps
-invPtrLoc /etc/oraInst.loc
-logDirLoc /FIN_T2P/logs
-silent true
-ignoreDiskWarning true
/net/mount1/appbase represents the top-level applications base directory for binary files.
On Windows:
copyBinary.cmd -javaHome USER_HOME\jrockit_160_04
-archiveLoc C:\FIN_clone1.jar
-sourceMWHomeLoc C:\appbase\fusionapps
-logDirLoc C:\logs
-silent true
-ignoreDiskWarning true
Table 20-4 describes the options for the copyBinary script.
Table 20-4 Options for the copyBinary Script
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit. Note: On Window, if the path name contains a space, then the entire value must be enclosed in double-quotes.
|
Mandatory |
|
|
None |
If the operating system is 64-bit UNIX, pass the To set the runtime property, you can specify the setenv T2P_JAVA_OPTIONS "-d64 -Djava.io.tmpdir=/home/t2p/temp" |
Optional |
|
|
|
The absolute path of the archive location. Use this option to specify the location of the archive file to be created with the The archive location must not already exist, but its parent directory must exist and have write permission. Ensure that the archive location is not within the Middleware home structure. |
Mandatory |
|
|
|
The absolute path to the Oracle Inventory pointer file. Use this option if the inventory pointer file location is not /etc/oraInst.loc, for all Unix platforms. The copyBinary operation reads this file to find out which all Oracle Homes are present under the Middleware home. The following shows an example of the contents of the file: inventory_loc=/scratch/oraInventory inst_group=dba You must have write permission to the inventory location. |
Available on UNIX only. Optional, if the inventory is at |
|
|
|
The location of an existing directory. A new log file is created in the directory. |
Optional |
|
|
None |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation. The default is that the operation prompts for confirmation. To continue, you must type To specify that it not prompt for confirmation, specify this option with the value of |
Optional |
|
|
|
The absolute path of the Middleware home to be archived. You can specify only one Middleware home. |
Mandatory |
|
|
|
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 |
This section describes how to ensure your environment is prepared and then how to run the pasteBinary script.
Ensure that the necessary components are installed on the target machine and that necessary properties are set before applying the binary files.
JDK: The host must have JDK 1.6.04 or later installed. In addition, ensure that the PATH, CLASSPATH, and JAVA_HOME environment variables point to the JDK.
Inventory Properties: In a UNIX environment, properly set the inventory_loc and inst_group properties in the inventory file. For example:
inventory_loc=/FIN_T2P/oraInventory inst_group=dba
The inventory file location itself is specified through the invPtrLoc option of the copyBinary command. If the invPtrLoc option is not specified, the inventory pointer file is assumed to be in its default location of /etc/oraInst.loc.
Permissions: Ensure that the files have execute permission.
Middleware Home: The Middleware home must be created on the shared storage of the target environment.
Cloning Client: Copy the following file from the following location on the source host to the target host:
(UNIX) FA_MW_HOME/oracle_common/jlib/cloningclient.jar (Windows) FA_MW_HOME\oracle_common\jlib\cloningclient.jar
Note:
On Microsoft Windows, if ECM is not installed properly, ODI OFFLINE PREVERIFICATION fails with the following error:
[C:\AT\fusionapps\ecm\ucm\Distribution\Kofax\Autorun.inf (Access is denied)]
To avoid this issue, "Prevent remote creation of autorun files" from McAfeePolicy Orchestrator (ePO) in the FusionApp Windows boxes before starting pasteBinary.
Because the Webgate is moved along with the rest of binaries, preparations for it must be made on the target machine.
Windows: If the target machine is running Windows 64, ensure that the Microsoft Visual Studio C++ 2005 runtime libraries (MSVCR80.dll and MSVCP80.dll) are installed. You can copy the libraries from SYSVOL\windows\SysWOW64 on the source machine to the same directory on the target machine.
Linux or Solaris: On these operating systems, third-party GCC libraries must be installed on the target machine before the Webgate 11g is moved. For instructions, see the "Installing Third-Party GCC Libraries (Linux and Solaris Operating Systems Only)" section in the Oracle Fusion Middleware Installation Guide for Oracle Identity Management.
While executing the pasteBinary operation, provide the following argument:
-op oracle.as.oam.webgate.ohs:GCC_LIB_DIR=GCC-LIB_DIR_LOCATION
This section describes where to find the script and how to run it.
If you run the pasteBinary script from a different location than FA_MW_HOME/oracle_common/bin, then you must copy the cloningclient.jar file to the same directory.
The pasteBinary script must be run from the primordial machine.
Even though the absolute path need not be the same as the one in the source environment, the directory structure relative to APPLICATIONS_BASE should be the same.
Copy the pasteBinary script from the following location on the source host to the target host:
(UNIX) FA_MW_HOME/oracle_common/bin/pasteBinary.sh (Windows) FA_MW_HOME\oracle_common\bin\pasteBinary.cmd
Run the pasteBinary script to apply the archive to the target environment. This pastes the binary files of the source Middleware home into the target environment. You must run the pasteBinary script for each Middleware home in the target environment.
The pasteBinary script is available from the following fusionapps Middleware directories:
(UNIX) FA_MW_HOME/oracle_common/bin (Windows) FA_MW_HOME\oracle_common\bin
Note:
IGNORE WARNINGS. If, while running the pasteBinary script, you encounter warnings that the system cannot access the webtier, you can ignore these messages.
Use the following syntax to run the pasteBinary script:
pasteBinary -javaHome path_of_jdk -archiveLoc archive_location -targetMWHomeLoc target_MW_Home_location [-executeSysPrereqs {true | false}] [-invPtrLoc Oracle_InventoryLocation] [-logDirLoc log_dir_path] [-silent {true | false}] [-ignoreDiskWarning {true | false}] [-ouiParam key1=value1,key2=value2]
The following example shows how to apply the archive to the directory /net/mount1/appbase/fusionapps on UNIX:
pasteBinary.sh -javaHome USER_HOME/jrockit_160_04 -archiveLoc /FIN_T2P/FIN_clone1.jar -targetMWHomeLoc /net/mount1/appbase/fusionapps -logDirLoc /FIN_T2P/logs/ -silent true -ignoreDiskWarning true -op oracle.as.oam.webgate.ohs:GCC_LIB_DIR=GCC-LIB_DIR_LOCATION
/net/mount1/appbase represents the top-level applications base directory for binary files.
On Windows:
pasteBinary.cmd -javaHome USER_HOME\jrockit_160_04
-archiveLoc C:\FIN_clone1.jar
-targetMWHomeLoc C:\appbase\fusionapps
-logDirLoc C:\logs
-silent true
-ignoreDiskWarning true
-ouiParam "oracle.as.oam.webgate.ohs:GCC_LIB_DIR=GCC-LIB_DIR_LOCATION"
Note:
On Windows, unless the command prompt uses MKS or another application to support Unix commands, then if the value of any argument contains delimeters such as commas (",") or semicolons (";") or equal signs ("="), then enclose the whole value in double quotes.
Table 20-5 describes the options for the pasteBinary script.
Table 20-5 Options for the pasteBinary Script
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit. Note: On Windows, if the path name contains a space, then the entire value must be enclosed in double-quotes.
|
Mandatory |
|
|
None |
If the operating system is 64-bit UNIX, pass the To set the runtime property, you can specify the setenv T2P_JAVA_OPTIONS "-d64 -Djava.io.tmpdir=/home/t2p/temp" |
No longer needed. Handled internally. |
|
|
|
The absolute path of the archive location. Use this option to specify the location of the archive file created with the The location must exist. Ensure that the archive location is not within the Middleware home structure. |
Mandatory |
|
|
|
Specifies whether the |
Optional |
|
|
|
The absolute path to the Oracle Inventory pointer file. Use this option if the inventory pointer file location is not The pasteBinary operation registers the Oracle Homes with the central Oracle inventory specified in the Oracle Inventory pointer file. UNIX only; this option is not available on Windows. The following shows an example of the contents of the file: inventory_loc=/scratch/oraInventory inst_group=dba You must have write permission to the inventory location. If the inventory location specified in inventory pointer file does not exist, test-to-production will create it. |
Available on UNIX only. Optional, if the inventory is at / |
|
|
|
The location of an existing directory. A new log file is created in the directory. |
Optional |
|
|
None |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation. The default is that the operation prompts for confirmation. To continue, you must type To specify that it not prompt for confirmation, specify this option with the value of |
Optional |
|
|
|
The absolute path of the target Middleware home If a multihost target topology is being used, the path Ensure that the parent directory of Middleware home, for example, The |
Mandatory |
|
|
|
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 |
|
|
|
To provide additional Oracle Universal Installer (OUI) session variables, for configuring Oracle home. |
Optional |
The Oracle Database client home is in the following location:
(UNIX) APPLICATIONS_BASE/dbclient (Windows) APPLICATIONS_BASE\dbclient
Its contents must be manually moved from the source environment to the target environment.
Perform the following steps to move the dbclient installation on UNIX:
Copy or tar the /net/mount1/appbase/dbclient directory to the target directly or from source.
/net/mount1/appbase represents the top-level applications base directory for binary files.
Run the installer clone as shown in the following example:
/net/mount1/appbase/dbclient/oui/bin/runInstaller -clone
ORACLE_BASE=/net/mount1/appbase ORACLE_HOME=/net
/net/mount1/appbase/dbclient ORACLE_HOME_NAME="dbclient" -jreLoc
/net/mount1/appbase
/fusionapps/jrockit_160_17_R28.0.0-679 -defaultHomeName
You will be prompted to run the root.sh command during the process.
Use an account with root access and run net/oracle/dbclient/root.sh.
Note:
You will not be prompted for permission to copy to the local bin directory.
Perform the following steps to perform the dbclient installation on Windows:
Copy the APPLICATIONS_BASE\dbclient from source to target.
Run the installer clone command, as in the example:
C:\AT\dbclient\oui\bin>setup.exe -clone ORACLE_BASE=C:\AT ORACLE_HOME=C:\AT\dbclient ORACLE_HOME_NAME="dbclient" -defaultHomeName
For each Oracle Fusion application, you must move the configurations of each Oracle WebLogic Server domain, OHS instance, and Node Manager that is part of the source environment to the target environment. This configuration movement relies on the use of the configuration scripts. For information, see Section 20.4.2.1.
If you have a non-distributed, QA environment, whereby the Administration Servers of all the domains and all the system component instances run on the same host, you can automate moving the configuration files with a different set of scripts than those described in this section. For more information, see Section 20.2 and Section 20.4.3.
Note:
On Windows, before you move the configurations to the target environment, you must set a JVM System Variable. See Section 20.4.2.2.
To move configurations:
Create the configuration archives by running the copyConfig script for each domain, OHS instance, and Node Manager in the source environment. See Section 20.4.2.3.
Extract the move plan by running the extractMovePlan script on the list of configuration archive locations, which are separated by commas. See Section 20.4.2.4.
Modify the move plan to specify properties for the target environment. See Section 20.4.2.5.
Apply the copied configurations from the source environment to the target environment by running the pasteConfig script for each Oracle WebLogic Server domain, OHS instance, and Node Manager separately, using the same move plan. See Section 20.4.2.6.
Complete the component-specific configuration move by performing additional movement tasks on the Oracle Fusion Middleware components. See Section 20.4.2.7.
If there are multiple machines for the domain, re-create the local domain directory using the Oracle WebLogic Server pack and unpack mechanisms. See Section 20.4.2.8.
Notes:
If the database is not tuned correctly, copyConfig and pasteConfig operations can result in performance issues. To avoid these performance issues, in addition to following standard database performance tuning guidelines, ensure that you have sufficient RAM allocated for your RDBMS for the import of the MDS tables. Also run statistics against the target database by executing the following procedure:
BEGIN dbms_stats.gather_schema_stats( ownname => 'FUSION_MDS', METHOD_OPT => 'FOR ALL COLUMNS SIZE AUTO', CASCADE => TRUE, ESTIMATE_PERCENT => NULL); END;
where FUSION_MDS is the MDS schema name for your Oracle Fusion Applications installation.
The Java version should be at least 1.6.04.
The path relative to APPLICATIONS_CONFIG (i.e. after the Instance directory) should match the path used when the source environment was provisioned.
Moving configurations in the Oracle Fusion Applications environment requires the use of a set of configuration scripts. These scripts are available in FA_MW_HOME/oracle_common/bin. For more information, see the "Movement Scripts" section in the Oracle Fusion Middleware Administrator's Guide.
Using the copyConfig, extractMovePlan, and pasteConfig scripts enables you to create a copy of the source Oracle WebLogic Server domain home or OHS instance home configuration files into an archive file, extract the configuration information from one or more configuration archive into a move plan so you can edit the properties for the target environment, and apply the copied configurations (along with the move plan) to the target environment. Figure 20-2 illustrates the flow of the configuration movement from the source environment to the target environment.
You must create a configuration archive for each source. The environment-specific configuration information from each of the configurations archives is extracted to and consolidated in the source move plan that you must edit to specify the properties for the target environment. Then you apply the edited move plan and the copied configuration archives from each source to each target.
Note:
The configuration archive files should be copied to the target environment, preferably to the shared storage so they are visible to all the target domains. Similarly, the extracted move plan and the updated move plan must also be present in the shared storage.
The copyConfig script creates a configuration archive that contains the snapshot of the configuration of a source entity (for example, Oracle WebLogic Server domain, OHS instance, or Node Manager). The underlying components of a source entity persist their configuration information in different data stores, such as a file system, Oracle Metadata Services (MDS), Lightweight Directory Access Protocol (LDAP), and database.
You must run the copyConfig script for each source entity in the source environment. A configuration archive is created for each source domain or component instance.
The Administration Server and all Managed Servers in the domain must be up and running when you run the script.
The extractMovePlan script extracts the environment-specific configuration information from one or more configuration archives into a move plan (XML file).
The extractMovePlan script also extracts any Java EE component-specific configuration file, such as Oracle SOA composite configuration plans, application deployment plans, and adapter deployment plans.
A move plan contains the environment-specific configuration information, such as data source definitions, host names, port numbers, and end-point URLs, from one or more configuration archives created for each source domain or component instance in the source environment. You must edit the move plan to specify the properties for the target environment.
The pasteConfig script 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 each source entity and the modified move plan. The pasteConfig script re-creates the configuration information for the source entity in the target environment. It also merges the move plan property values for the target environment. You must run the pasteConfig script for each source entity in the target environment.
On Windows, by default, there may not be sufficient memory allocated on the system to successfully run the pasteConfig script. It is advised to set the USER_MEM_ARGS variable as follows, to avoid errors.
For systems using Sun JDK:
set USER_MEM_ARGS="-Xms512m -Xmx1536m -XX:CompileThreshold=8000 -XX:PermSize=512m -XX:MaxPermSize=1024m"
For systems running JRockit:
set USER_MEM_ARGS="-Xms512m -Xmx1536m"
Run the copyConfig script for each source entity (for example, Oracle WebLogic Server domain, OHS instance, Node Manager, or Oracle BI Enterprise Edition) to create a copy of the source entity configuration files into an archive file.
Note:
IGNORE WARNING.
During copyConfig, if you receive the following message, ignore it
SEVERE : [PLUGIN][NetworkInformation TopologyManagerServices is not in this domain
This section covers the following topics:
Section 20.4.2.3.1, "Running copyConfig for Oracle WebLogic Server Domains"
Section 20.4.2.3.2, "Running copyConfig for System Components"
Section 20.4.2.3.4, "Running copyConfig for Oracle BI Enterprise Edition"
Section 20.4.2.3.5, "Running copyConfig for the Oracle Global Order Promising Server Instance"
Java EE domains reside in the Oracle WebLogic Server Domain configuration home, APPLICATIONS_CONFIG/instance/domains. CRMDomain and FinancialDomain are two examples of Java EE domains.
Running copyConfig creates a copy of the source Oracle WebLogic Server Java EE component into a configuration archive file that contains the Oracle WebLogic Server domain configuration and all configurations stored in MDS. It also packs the other configuration information specific to components such as SOA composites, human workflow, Oracle B2B agreements, and Oracle Application Development Framework (Oracle ADF) connection settings for all connections.
Note:
If you have the following special conditions:
UMS is used, and
there are remote UMS servers in the source environment, and
shared disk is not used
then you will need to run a preliminary step. You will copy all the remote UMS configurations to the source Admin server.
To do so, perform the following on each remote server instance containing a UMS configuration:
cd <domain_home>/config/fmwconfig/servers
tar cvf umsconfig_<server>.tar <server>/applications/usermessaging*
Repeat if there are multiple servers running on this instance
Copy the tar file(s) to the Admin server
Extract the tar file(s) at the corresponding location on the Admin server
Then proceed with the CopyConfig steps below, as usual.
Later, after PasteConfig, you will perform pack.sh on the destination Admin server, and unpack on the destination remote hosts. Finally, there is a cleanup step to remove the duplicate UMS configuration information from the destination Admin server. See Section 20.4.2.8.
Before running copyConfig: clean up core*.dump and javacore*.txt or any huge log files
To begin: set the T2P_JAVA_OPTIONS before running copyConfig on domains, as follows:
export T2P_JAVA_OPTIONS="-Dhttp.proxyHost=www-proxy.example.com-Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost"
In Windows OS, Replace export with set in the command above.
You must also set the IPV6 address and Fully Qualified Domain Hostname for -Dhttp.nonproxyHosts, as follows:
set T2P_JAVA_OPTIONS="-Dhttp.proxyHost=www-proxy.example.com-Dhttp.proxyPort=80
-Dhttp.nonProxyHosts=localhost|<AAAA:BBBB:CCCC:DDDD:EEEE:FFFF:GGGG:HHHH>|
<fully_qualified_host_name>"
where <AAAA:BBBB:CCCC:DDDD:EEEE:FFFF:GGGG:HHHH> and <fully_qualified_host_name> are replaced by the IPV6 and FQDN hostname.
In AIX, Solaris SPARC environments and Solarisx64 , in addition to step 1, it is also necessary to set the following parameter before beginning copyConfig, to avoid an out-of-memory error:
export T2P_JAVA_OPTIONS="-Dhttp.proxyHost=www-proxy.example.com-Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost -Xmx5120m -Xms5120m -XX:MaxPermSize=512M"
Note:
copyConfig handles only global data sources defined in each Oracle WebLogic Server domain. For application-level data sources, you must manually configure them on the target domain.
Ignore warning:
If you receive the following message during copyConfig, ignore it.
SEVERE : [PLUGIN][NetworkInformation] TopologyManagerServices is not in this domain
Use the following syntax to run the copyConfig script for each Oracle WebLogic Server domain:
copyConfig -javaHome absolute_location_of_JDK -archiveLoc archive_location -sourceDomainLoc source_WebLogic_domain_location -sourceMWHomeLoc source_Middleware_home_location -domainHostName source_domain_admin_server_host_name -domainPortNum source_domain_admin_server_port -domainAdminUserName source_domain_admin_server_user_name -domainAdminPassword source_domain_admin_server_user_password_file_location [-mdsDataImport {true | false}] [-additionalParams search.encrypt.key=pwdfile] [-logDirLoc existing_log_directory_location] [-silent {true | false}]
The following example copies the configuration of the FinancialDomain domain on Unix:
copyConfig.sh -javaHome USER_HOME/jrockit_160_04
-archiveLoc /FIN_T2P/FIN_FinancialDomain1.jar
-sourceDomainLoc /net/mount2/instance/applications/FinancialDomain
-sourceMWHomeLoc /net/mount1/appbase/fusionapps
-domainHostName server.us.example.com
-domainPortNum 9001
-domainAdminUserName faadmin
-domainAdminPassword /FIN_T2P/domain_admin_server_pw.txt
-logDirLoc /FIN_T2P/logs
-silent true
On Windows:
copyConfig.cmd -javaHome C:\USER_HOME\jrockit_160_04
-archiveLoc C:\FIN_T2P\FIN_FinancialDomain1.jar
-sourceDomainLoc C:\instance\applications\FinancialDomain
-sourceMWHomeLoc C:\appbase\fusionapps
-domainHostName server.us.example.com
-domainPortNum 9001
-domainAdminUserName faadmin
-domainAdminPassword C:\FIN_T2P\domain_admin_server_pw.txt
-logDirLoc C:\FIN_T2P\logs
-silent true
Note:
On Windows, unless the command prompt uses MKS or another application to support Unix commands, the = sign must be passed within double-quotes, such as -additionalParams search.encrypt.key"="pwdfile
The following example copies the configuration of the CommonDomain domain. Notice the use of the -additionalParams option for Oracle SES.
copyConfig.sh -javaHome USER_HOME/jrockit_160_20_D1.0.1-1705
-archiveLoc /COMMON_T2P/COMMON_CommonDomain.jar
-sourceDomainLoc /net/mount2/instance/applications/CommonDomain
-sourceMWLoc /net/mount1/appbase/fusionapps
-domainHostName server.us.example.com
-domainPortNum 8001
-domainAdminUserName faadmin
-domainAdminPassword /COMMON_T2P/domain_admin_server_pw.txt
-additionalParams search.encrypt.key=/SES_T2P/encrypt_key.txt
/net/mount1/appbase represents the top-level applications base directory for binary files, whereas /net/mount2 represents the top-level applications configuration directory for configuration files.
Table 20-6 describes the options for the copyConfig script for Oracle WebLogic Server Java EE components.
Table 20-6 Options for the copyConfig Script for Oracle WebLogic Server Java EE Components
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit. Note: On Windows, if the path name contains a space, then the entire value must be enclosed in double-quotes.
|
Mandatory |
|
|
None |
If the operating system is 64-bit UNIX, pass the To set the runtime property, you can specify the setenv T2P_JAVA_OPTIONS "-d64 -Djava.io.tmpdir=/home/t2p/temp" |
Optional |
|
|
|
The absolute location of the archive. Use this option to specify the location of the archive file to be created by the |
Mandatory |
|
|
|
The absolute location of the source domain containing the Java EE component. |
Mandatory |
|
|
|
The absolute location of the source Middleware home. |
Mandatory |
|
|
|
The name of the host on which the source domain is configured. |
Mandatory |
|
|
|
The port number of the source domain. |
Mandatory |
|
|
|
The name of the administrative user for the source domain. |
Mandatory |
|
|
|
The password file location for the administrative user for the domain. For example, |
Mandatory |
|
|
|
Absolute path of the Oracle SES password file for the encryption key, for example, The encryption key in the file must be at least 8 characters, must contain both letters and numbers, and must only contain ASCII characters. Oracle SES is available in the |
Mandatory for the |
|
|
|
The location of an existing log directory. A new log file is created in the directory. |
Optional |
|
|
None |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation. The default is that the operation prompts for confirmation. To continue, you must type To specify that it not prompt for confirmation, specify this option with the value of |
Optional |
|
|
|
These two flags have the same meaning. Each specifies whether to export the application MDS metadata to the archive so that it can be imported into the target. The default is |
Optional |
Running copyConfig creates a copy of the source component instance for a system component, such as OHS, by copying the configuration files of that component instance into an archive file.
Use the following syntax to run the copyConfig script for system components:
copyConfig -javaHome absolute_location_JDK -archiveLoc archive_location -sourceInstanceHomeLoc source_instance_home_location -sourceComponentName source_component_name [-logDirLoc existing_log_directory_location] [-silent {true | false}]
The following example shows how to create a copy of the OHS instance named ohs1 in the Oracle instance home located in APPLICATIONS_CONFIG/instance/CommonDomain_webtier on UNIX:
copyConfig.sh -javaHome USER_HOME/jrockit_160_17_R28.0.0-679/
-archiveLoc /FIN_T2P/FIN_CommonDomain_webtier.jar
-sourceInstanceHomeLoc /net/mount2/instance/CommonDomain_webtier
-sourceComponentName ohs1
-logDirLoc /FIN_T2P/logs
-silent true
/net/mount2 represents the top-level applications configuration directory for configuration files.
On Windows:
Note:
Windows platform only: While executing copyConfig of OHS in Windows, shut down the ohs instance. To do so, use:
$INSTANCE_HOME/bin/opmnctl stopall
Then continue with the copyConfig process:
copyConfig.cmd -javaHome C:\jrockit_160_17_R28.0.0-679/ -archiveLoc C:\FIN_T2P\FIN_CommonDomain_webtier.jar -sourceInstanceHomeLoc C:\instance\CommonDomain_webtier -sourceComponentName ohs1 -logDirLoc C:\FIN_T2P\logs -silent true
Table 20-7 describes the options for the copyConfig script for system components.
Table 20-7 Options for the copyConfig Script for System Components
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit. Note: On Windows, if the path name contains a space, then the entire value must be enclosed in double-quotes.
|
Mandatory |
|
|
None |
If the operating system is 64-bit UNIX, pass the To set the runtime property, you can specify the setenv T2P_JAVA_OPTIONS "-d64 -Djava.io.tmpdir=/home/t2p/temp" |
Optional |
|
|
|
The absolute location of the archive. Use this option to specify the location of the archive file to be created by the |
Mandatory |
|
|
|
The location of an existing log directory. A new log file is created in the directory. |
Optional |
|
|
None |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation. The default is that the operation prompts for confirmation. To continue, you must type To specify that it not prompt for confirmation, specify this option with the value of |
Optional |
|
|
|
The name of the source component to be moved. For example, if your Oracle HTTP Server component is named ohs1, specify |
Mandatory |
|
|
|
The absolute location of the Oracle instance home for the source component. |
Mandatory |
Node Manager is an Oracle WebLogic Server utility that enables you to start, shut down, and restart the Administration Server and Managed Server instances from a remote location. The Node Manager for each host resides in Oracle WebLogic Server home, in wlserver_version/common/nodemanager/host_name.
Running copyConfig creates a copy of the source Node Manager configuration into an archive file.
Use the following syntax to run the copyConfig script for Node Manager on each machine within topology of the source environment:
copyConfig -javaHome absolute_location_of_JDK -archiveLoc archive_location -sourceNMHomeLoc source_Node_Manager_home_location [-logDirLoc existing_log_directory_location] [-silent {true | false}]
The following example shows how to create a copy of the source Node Manager configuration located in /net/domain/scratch/work/mw2903/wlserver_10.3/common/nodemanager/sampledomain.com (with a folder corresponding to each Node Manager) into an archive file, in UNIX:
copyConfig.sh -javaHome USER_HOME/jrockit_160_17_R28.0.0-679/
-archiveLoc /FIN_T2P/node_manager_domain.jar
-sourceNMHomeLoc /net/mount1/appbase/instance/nodemanager/ sampledomain.com
-silent true
On Windows:
copyConfig.cmd -javaHome C:\USER_HOME\jrockit_160_17_R28.0.0-679/
-archiveLoc C:\FIN_T2P/node_manager_domain.jar
-sourceNMHomeLoc C:\appbase/fusionapps/wlserver_10.3/common/nodemanager/sampledomain.com
-silent true
Table 20-8 describes the options for the copyConfig script for Node Manager.
Table 20-8 Options for the copyConfig Script for Node Manager
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit. Note: On Windows, if the path name contains a space, then the entire value must be enclosed in double-quotes.
|
Mandatory |
|
|
None |
If the operating system is 64-bit UNIX, pass the To set the runtime property, you can specify the setenv T2P_JAVA_OPTIONS "-d64 -Djava.io.tmpdir=/home/t2p/temp" |
Optional |
|
|
|
The absolute location of the archive. Use this option to specify the location of the archive file to be created by the |
Mandatory |
|
|
|
The absolute location of the source Node Manager home |
Mandatory |
|
|
|
The location of an existing log directory. A new log file is created in the directory. |
Optional |
|
|
None |
Specifies whether the operation operates silently. That is, it does not prompt for confirmation. The default is that the operation prompts for confirmation. To continue, you must type To specify that it not prompt for confirmation, specify this option with the value of |
Optional |
Running copyConfig creates a copy of the source Oracle BI Enterprise Edition configuration into an archive file. You do not need to use the copyconfig script for each component; run it once for all the Oracle BI Enterprise Edition components, which include:
Oracle BI Server
Oracle BI Presentation Services
Oracle BI Cluster Controller
Oracle BI Scheduler
JavaHost
Oracle Essbase server, if it is installed in your environment
Use the following syntax to run the copyConfig script to create a complete Oracle BI Enterprise Edition instance copy:
copyConfig -javaHome path_of_jdk -archiveLoc archive_location -sourceInstanceHomeLoc src_instance_path -additionalParams essbaseServerUserName=xxx,essbaseServerPassword=pwdfile [-logDirLoc existing_log_directory_location] [-silent {true | false}]
The following example shows how to apply the copy of Oracle BI Enterprise Edition to the Oracle BI Enterprise Edition home located in BIDomain.
/net/mount2/
On UNIX:
copyConfig -javaHome USER_HOME/jrockit_160_17_R28.0.0-679/ -archiveLoc /BI_T2P/BIInstance.jar -sourceInstanceHomeLoc /net/mount2/appbase/instance/BIInstance -additionalParams essbaseServerUserName=weblogic,essbaseServerPassword=/tmp/password.txt -silent true
On Windows:
copyConfig -javaHome C:\jrockit_160_17_R28.0.0-679
-archiveLoc C:\BI_T2P\BIInstance.jar
-sourceInstanceHomeLoc C:\appbase\instance\BIInstance
-additionalParams "essbaseServerUserName=weblogic,essbaseServerPassword=C:\password.txt"
-silent true
Note:
On Windows, unless the command prompt uses MKS or another application to support Unix commands, the = sign must be passed within double-quotes, such as -additionalParams search.encrypt.key"="pwdfile
Table 20-9 describes the options for the copyConfig script for Oracle BI Enterprise Edition.
Table 20-9 Options for the copyConfig Script for Oracle BI Enterprise Edition
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit. Note: On Windows, if the path name contains a space, then the entire value must be enclosed in double-quotes.
|
Mandatory |
|
|
|
The absolute path of the archive location |
Mandatory |
|
|
|
The absolute path of the Oracle BI Enterprise Edition instance for the source component |
Mandatory |
|
|
|
Specifies Oracle Essbase administrative user and password |
Mandatory |
|
|
|
The location of an existing directory |
Optional |
|
|
None |
Specifies whether the operation operates silently; i.e. will not prompt for confirmation, as it would by default. To specify that it not prompt for confirmation, set this option to |
Optional |
Running copyConfig copies the source Oracle Global Order Promising Server configuration into an archive file.
Use the following syntax to run the copyConfig script to create a complete Oracle Global Order Promising Server instance copy:
copyConfig -javaHome path_of_jdk -archiveLoc archive_location -sourceInstanceHomeLoc src_instance_path -sourceComponentName GlobalOrderPromisingServer1 [-logDirLoc existing_log_directory_location] [-silent {true | false}]
The following example shows how to create a copy of Oracle Global Order Promising Server configuration located in /net/mount1/appbase/instance/gop_1 into an archive file.
On UNIX:
copyConfig -javaHome USER_HOME/jrockit_160_17_R28.0.0-679/ -archiveLoc USER_HOME/gop_1.jar -sourceInstanceHomeLoc /net/mount1/appbase/instance/gop_1 -sourceComponentName GlobalOrderPromisingServer1 -logDirLoc USER_HOME/clone_logs -silent false
On Windows:
copyConfig -javaHome C:\jrockit_160_17_R28.0.0-679/
-archiveLoc C:\gop_1.jar
-sourceInstanceHomeLoc C:\appbase\instance/gop_1
-sourceComponentName GlobalOrderPromisingServer1
-logDirLoc C:\clone_logs
-silent false
Table 20-10 describes the options for the copyConfig script for Oracle Global Order Promising Server.
Table 20-10 Options for the copyConfig Script for Oracle Global Order Promising Server
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit. Note: On Windows, if the path name contains a space, then the entire value must be enclosed in double-quotes.
|
Mandatory |
|
|
|
The absolute path of the archive location. Use this option to specify the location of the archive file created by the |
Mandatory |
|
|
|
The name of the existing component which will be archived, |
Mandatory |
|
|
|
The absolute path of the Oracle Global Order Promising Server instance for the source component. |
Mandatory |
|
|
|
The location of an existing directory. A new log file is created in the directory. |
Optional |
|
|
None |
Specifies whether the operation operates silently; i.e. will not prompt for confirmation, as it would by default. To specify that it not prompt for confirmation, set this option to |
Optional |
Run the extractMovePlan script to extract the configuration settings from multiple configuration archives of the source environment into a single move plan (XML file). Extracting the move plan from multiple configuration archives consolidates and tries to remove duplicate configuration properties in the consolidated move plan. It also tries to remove the configuration properties that could be derived from other configuration properties. Running extractMovePlan also extracts other application-specific standard configuration plans, such as those for SOA composite and the deployment plan for Java EE.
Note:
Extract the move plan in a location that is shared by all systems in the configuration topology. You can then use the move plan and underlying configuration or deployment plans from the same location to re-create multiple domains or system component instances.
Before beginning the extractMovePlan script, you must export the T2P_JAVA_OPTIONS as follows:
T2P_JAVA_OPTIONS="-Dhttp.proxyHost=www.proxyhost.mycompany.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost"
Use the following syntax to run the extractMovePlan script.
On UNIX:
extractMovePlan -javaHome absolute_location_of_JDK -archiveLoc archive_location[,archive_location...] -planDirLoc move_plan_directory [-optimizationHints fusionApps,sameSchemaNameSinglePassword] [-logDirLoc existing_log_directory_location]
On Windows:
extractMovePlan -javaHome <>
-archiveLoc "archive_location[,archive_location..."
-planDirLoc move_plan_directory
-optimizationHints "hint,hint"
Note that commas (,) and equal signs (=) are converted to spaces in the Windows environment unless double-quotes (") are used.
The following example extracts configuration information from two configuration archives into a single move plan:
extractMovePlan.sh -javaHome USER_HOME/jrockit_160_20_D1.0.1-1705
-archiveLoc /FIN_T2P/FIN_CommonDomain1.jar,/FIN_T2P/FIN_FinancialDomain1.jar
-planDirLoc /FIN_T2P/CommonDomain1_plan
-opth fa,ssnsp
-logDirLoc /FIN_T2P/logs
Or, on Windows:
extractMovePlan.cmd -javaHome <>
-archiveLoc "C:\T2P_AL\BIDomain.jar,C:\T2P_AL\HCMDomain.jar"
-planDirLoc move_plan_directory
-optimizationHints "fusionApps,sameSchemaNameSinglePassword"
A list of configuration archive locations, which are separated by commas, is specified to create a single move plan containing the configuration settings from the listed configuration archives.
Note:
Ensure there is no space before or after the comma in the list of configuration archive locations.
You can also extract the configuration settings from each individual configuration archive to create multiple move plans. However, this neither consolidates nor optimizes the move plans.
Table 20-11 describes the options for the extractMovePlan script:
Table 20-11 Options for the extractMovePlan Script
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit. Note: On Windows, if the path name contains a space, then the entire value must be enclosed in double-quotes.
|
Mandatory |
|
|
None |
If the operating system is 64-bit UNIX, pass the To set the runtime property, you can specify the setenv T2P_JAVA_OPTIONS "-d64 -Djava.io.tmpdir=/home/t2p/temp" |
Optional |
|
|
|
The absolute location of one or more archives. Use this option to specify the locations of the archive files created by the If you specify more than one archive, separate the locations with a comma with no spacing in between. |
Mandatory |
|
|
|
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 already exist. |
Mandatory |
|
|
|
The location of an existing directory. A new log file is created in the directory. |
Optional |
|
|
|
Specifies the configuration values to auto-populate based on the topology on the target environment. These values are omitted from the move plan. Use of the hints is recommended if they apply to your environment.
|
Optional |
While extracting the move plans, the framework internally derives the properties and optimizes them. In those cases, you may not see all the properties in the move plan. If the framework can not derive the value of a config property from some other config properties by comparing their values, you will see those properties in the move plan
After the move plan is extracted, you must modify one consolidated plan with a text editor to specify the properties (such as data source definitions, host names, port numbers, and endpoint addresses) for the target environment before you apply the copied configurations from the source environment to the target environment.
The properties that you edit differ depending on the type of component. Table 20-12 provides pointers to the appropriate list of properties for each component. Some of the references link to tables in the "Move Plan Properties for Components" section of the Oracle Fusion Middleware Administrator's Guide; other links direct you to tables in this chapter. Tables referenced in the Oracle Fusion Middleware Administrator's Guide are generic tables that work for both Oracle Fusion Applications and Oracle Fusion Middleware environments. To avoid confusion, only use the tables referenced.
Table 20-12 Move Plan Properties for Components
| Component | Where to Find the List of Properties: |
|---|---|
|
Oracle Fusion Applications |
|
|
Oracle Fusion Applications patching framework |
|
|
Oracle Fusion Applications additional environment properties |
|
|
Node Manager |
|
|
All Java components |
|
|
Oracle BI EE |
|
|
Oracle ADF connections |
|
|
Oracle Data Integrator |
|
|
Oracle Enterprise Crawl and Search Framework |
|
|
Oracle Enterprise Scheduler Service (ESS) |
|
|
Oracle Global Order Processing |
|
|
Oracle Governance, Risk and Compliance Controls |
|
|
Oracle HTTP Server |
|
|
Oracle Secure Enterprise Search |
|
|
Oracle SOA Suite |
|
|
Oracle Topology Manager |
|
|
Oracle Virtual Directory |
|
|
Oracle WebCenter Content: Inbound Refinery |
"Move Plan Properties for WebCenter Content Server, Records, and Inbound Refinery" NOTE: Set the value of the property MoveType to ' |
|
Oracle WebCenter Content: Imaging |
Modify the move plan by editing the specific Oracle Fusion Applications entries within the movableComponent of type ApplicationTopology and name FusionAppsTopology according to the target environment.
Table 20-13 describes the FusionAppsTopology properties to edit in the move plan, if they are present.
Table 20-13 Move Plan Properties for Oracle Fusion Applications FusionAppsTopology Properties
| Configuration Group | Property | Description | Sample Value |
|---|---|---|---|
|
|
|
The listen address used by OHS on the webtier host. This is usually the host name of the machine where OHS server is running. |
|
|
|
|
The listen address used by Managed Servers on the host. This is usually the host name of the machine where Managed Server is running. |
|
|
|
The encrypted custom identity keystore's passphrase file. The location must match the sample value. |
|
|
|
|
The alias used when loading the private key for Oracle WebLogic Server from the keystore. |
|
|
|
|
Path to the password file which will be used while loading the private key for Oracle WebLogic Server into the keystore) |
|
|
|
|
Path to the file containing custom trust keystore. The location must match the sample value. |
|
|
|
|
JDBC connect string to be used as a Java EE data source |
|
|
|
|
|
The JDBC URL in the format of |
|
|
|
The Oracle database schema name (user name) to log in to the database. During execution of the During execution of the |
|
You must manually update the Oracle Fusion Applications patching framework configuration information to specify the properties for the target domain. To update the Oracle Fusion Applications patching framework configuration information, edit the values of the patching framework properties in the move plan.
Table 20-14 describes the move plan properties that you can change for the patching framework.
Table 20-14 Move Plan Properties for Oracle Fusion Applications Patching Framework
| Properties | Description | Example |
|---|---|---|
|
Top directories for various components used by Patching Framework |
The following properties are defined in |
|
|
|
Applications base directory, |
/u01/apptop |
|
Database-related properties |
The following properties are in the |
|
|
|
Database service as defined by the |
prod |
|
Taxonomy-related properties |
||
|
|
URL to connect to the MBean to fetch taxonomy information. This URL is usually the same as the Administration Server URL. See Section 2.4 to find the URL for the Administration Server. |
machinename.example.com:7001 |
|
Oracle Access Manager-related properties |
The following properties are defined in |
|
|
|
Host name for Oracle Access Manager |
machinename.example.com |
|
|
Port for Oracle Access Manager connection |
3060 |
|
|
Host for the Administration Server on the Oracle Access Manager |
machinename.example.com |
|
|
Host for the Administration Server on the Oracle Access Manager connection |
3060 |
|
|
Oracle Access Manager web domain used for Oracle Fusion Applications policies |
OraFusionApp |
|
|
Mode for the Oracle Access Manager server |
Simple Open |
This section describes the move plan properties for Oracle Fusion Applications, startup configuration, Oracle Human Workflow configuration, and Oracle Database client configuration.
Note:
The Oracle Database client configuration is reset to the initial out-of-box configuration set by provisioning. Any additional properties added to the source environment are not moved to the target environment. Therefore, you need to copy any additional properties to the target environment.
Table 20-15 describes the Oracle Fusion Applications properties.
Table 20-15 Move Plan Properties for Oracle Fusion Applications
| Configuration Group | Property | Description | Sample Value |
|---|---|---|---|
|
|
|
The top-level directory for the Oracle Fusion Applications binary files |
|
|
|
The top-level directory for the Oracle Fusion Applications configuration files (includes the |
|
|
|
|
|
OHS or load balancer URL value for the SOA cluster configured in |
|
|
|
|
Location of password file that contains password to create the database client wallet |
|
|
|
Database service name of the |
|
|
|
|
Database host name of the |
|
|
|
|
Database port number of the |
|
|
|
|
Database schema name (user name) to log in to the database |
|
|
|
|
Location of password file that contains schema password to log in to the database |
|
|
|
|
|
The external OHS URL for all the Oracle Fusion applications human workflow task flows. The format of FANamespace1=https://host1:port1::FANamespace2=https://host2:port2::*=https://host1:port1 where If For example, if SUPPLIER=https://supportportalFrontendHostName:port::*=https://OtherFAFrontendHostHame:port1 |
|
|
|
The external OHS URL for all the Oracle Fusion applications human workflow task flows ( |
|
This section describes the move plan properties for Oracle BI Enterprise Edition, Oracle BI EE Data Warehouse Administration Console, Oracle Essbase, EPM Registry, and Oracle BI Action Framework.
Table 20-16 shows the move plan properties that you can change for Oracle BI Enterprise Edition.
Table 20-16 Move Plan Properties for Oracle BI EE
| Properties | Description | Sample Value |
|---|---|---|
|
Properties in the XMLP-SERVER-CONFIG configGroup: |
Oracle BI Publisher configuration |
|
|
|
The name of the host that is running the Oracle BI Presentation Services to which you must connect |
example_host |
|
|
The port number for connecting to Oracle BI Presentation Services |
10217 |
|
|
The absolute path of a secure file that contains the password for Oracle BI Presentation Services |
/scratch/oracle/bip_pass.txt |
|
|
The user name for Oracle BI Presentation Services |
user1 |
|
Properties in the connection configProperty: |
Each data source can be either a Connection or File type. |
|
|
|
The URL of the connection |
jdbc:oracle:thin:@host:port:sid
|
|
|
The driver to use for the connection |
oracle.jdbc.OracleDriver |
|
|
The user name for the connection |
user1 |
|
|
The absolute path of a secure file that contains the password for the connection |
/scratch/oracle/ds_conn_pass.txt |
|
Properties in the file configProperty: |
|
|
|
|
The file system path that points to the relevant data source file |
/scratch/apptop/instance/domains/example.com/BIDomain/config/bipublisher/repository/DemoFiles |
|
Properties in the XDO-CLIENT_CONFIG configGroup: |
Oracle BI Publisher client |
|
|
|
The absolute path to the Oracle BI Publisher client directory |
/scratch/apptop/instance/domains/example.com/CommonDomain/config |
|
* (any name) |
The Oracle BI Publisher-configured endpoint connecting URL. The move plan may have more than one endpoint. |
http://example.com:10621/xmlpserver |
|
Properties in the XMLP-SCHEDULER-JMS-CONFIG configGroup: |
The Scheduler configuration |
|
|
|
The Oracle WebLogic Server JNDI URL for the Oracle BI EE Managed Server |
cluster:t3://bi_cluster |
|
|
The JMS shared temporary directory used in an Oracle BI EE cluster environment |
/scratch/apptop/instance/BIShared/BIPublisher/biptemp |
|
Properties in the XMLP-PROVIDER-CONFIG configGroup, in the provider configProperty: |
Oracle BI Publisher provider There is a separate |
|
|
|
The URI for the Oracle BI Publisher provider |
http://example.com:10603/financialCommon |
|
|
The non-SSO URI for the Oracle BI Publisher provider |
http://example.com:7404/financialCommon |
|
Properties in the XDO-SERVER_CONFIG configGroup: |
Oracle BI Publisher Server |
|
|
|
The absolute path to the Oracle BI Publisher server configuration directory |
/scratch/apptop/instance/domains/example.com/BIDomain/config/bipublisher |
|
The following property is in the |
||
|
|
The directory of the Oracle BI Publisher server configuration repository. (It can be located outside of the |
/scratch/apptop/instance/BIShared/BIPublisher/repository |
|
The following property is in the |
||
|
|
The path for the Oracle BI Publisher repository directory |
/scratch/apptop/instance/domains/example.com/BIDomain/config/bipublisher/repository |
|
Properties in the OracleInstances configGroup: |
Oracle BI EE domain configuration |
|
|
|
The path of the Oracle instance in which Oracle BI EE is deployed |
/scratch/apptop/instance/BIInstance |
|
|
The host where the Oracle BI EE instance is configured |
example.com |
|
Properties in the BIInstanceDeployment configProperty: |
Instance configuration details |
|
|
|
The listen address for the host. It can be set to a virtual IP address or a subset on a multi-homed computer. You can use an asterisk to specify multiple network addresses for the host. |
example.com * |
|
|
The start of the range of ports used by the Oracle BI EE system components |
10206 |
|
|
The end of the range of ports used by the Oracle BI EE system components |
10214 |
|
Properties in the BIInstance configGroup, in the EmailOptions configProperty: |
Oracle BI EE instance configuration |
|
|
|
The host name of the SMTP server |
example.com |
|
|
The port number of the SMTP server |
25 |
|
|
The sender's name that is used as the display name by the Oracle BI EE system when it sends email |
Oracle Business Intelligence |
|
|
The email address used by the Oracle BI EE system when it sends email |
defaultuser@defaultmailserver.com |
|
Property in the BIInstance configGroup, in the MarketingOptions configProperty: |
Oracle BI EE instance configuration |
|
|
|
The base URL used by the Oracle BI EE system when the emails have embedded URLs |
http://example.com:7012/_dav/cs/idcplg |
|
Property in the BIInstance configGroup, in the PresentationServerOptions configProperty: |
Presentation Server configuration |
|
|
|
The absolute path of the location of the Oracle BI Presentation Catalog |
/scratch/apptop/instance/BIShared/OracleBIPresentationServicesComponent/coreapplication_obips1/catalog/OracleBIApps |
|
Property in the BIInstance configGroup, in the Scheduler configProperty: |
Scheduler configuration |
|
|
|
The connection details for the Oracle BI Scheduler data source |
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=example.com)(PORT=1565)))(CONNECT_DATA=(SERVICE_NAME=d8b4lfc1)) |
|
Properties in the BIInstance configGroup, in the ServerOptions configProperty: |
Server options configuration |
|
|
|
The shared location for the Oracle BI repository |
/scratch/apptop/instance/BIShared/OracleBIServerComponent/coreapplication_obis1/repository |
|
Properties in the BIInstance configGroup, in the PerformanceOptions configProperty: |
Performance options configuration |
|
|
|
The global location of the Oracle BI EE server cache |
/scratch/apptop/instance/BIShared/OracleBIServerComponent/coreapplication_obis1/cache |
|
Properties in the DEPLOY_USER_CREDENTIALS configGroup: |
Oracle RTD Inline Services (BI_RTD_SPE_ILS_DEPLOY_CONFIG) |
|
|
|
The user name used to deploy the RTD SPE inline service |
weblogic |
|
|
The absolute path of a secure file that contains the password for the connection |
/scratch/oracle/rtd_pass.txt |
|
Properties in the CONNECTIONPOOLS configGroup: |
RPD configuration |
|
|
|
Connection pool user name (the database schema name). The name may be a variable, in the format |
VALUEOF(ORACLE_INITBLOCK_USER) |
|
|
Oracle BI repository connection pool data source name or definition. The name may be a variable, in the format |
VALUEOF(ORACLE_INITBLOCK_DSN) |
|
|
If this is an ADF connection, the Business Component URL |
http://example.com:10603/fscmAnalytics/obieebroker |
|
|
The absolute path of a secure file that contains the password for the connection to the Oracle BI repository data source |
/scratch/oracle/rpd_ds_conn_pass.txt |
|
Properties in the VARIABLES configGroup: |
Definition of variables |
|
|
|
The name of the variable that is used in the Oracle BI repository connection pool definitions. There can be multiple name/value pairs. |
ORACLE_INITBLOCK_USER |
|
|
The value of the variable that is used in the Oracle BI repository connection pool definitions. There are multiple name/value pairs. |
'ORA_INIT_USER' |
Table 20-17 describes the move plan properties that you can change for Oracle Business Intelligence Data Warehouse Administration Console (DAC).
Table 20-17 Move Plan Properties for Oracle Business Intelligence Data Warehouse Administration Console (DAC)
| Properties | Description | Example |
|---|---|---|
|
Properties in the DAC-SERVER-CONFIGURATION configGroup: |
DAC configuration |
|
|
|
The URL to connect to the DAC repository |
jdbc:oracle:thin:@example.com:1521/example.com |
|
|
The name of the JDBC driver |
oracle.jdbc.driver.OracleDriver |
|
|
The user name used to connect to the DAC repository |
IMPORT_DAC |
|
|
The absolute path of a secure file containing the password for the user to connect to the DAC repository. You must provide a password file, even if you are not changing the configuration. |
/scratch/biplatform/cloning/password_DAC.txt |
|
Properties in the EMAIL-CONFIGURATION configGroup: |
Email configuration |
|
|
|
The host name of the email server |
example |
|
|
The protocol for the email server |
smtp |
|
|
The email address of the user |
test@test.te |
|
|
The flag indicating whether the corporate email server requires authentication. Valid values are |
true |
|
|
The flag indicating whether an SSL connection is required. Valid values are |
false |
|
|
The port where the email server listens |
5555 |
|
|
User name for the email account The email user must be provided even though email is not configured. |
test |
|
|
The absolute path of a secure file containing the password for the user of the email server. (Only required if The email password must be provided even though email is not configured. |
/scratch/biplatform/cloning/password_email.txt |
|
Properties in the DATAWAREHOUSE-CONFIGURATION configGroup: |
Data Warehouse configuration |
|
|
|
The URL to connect to the Data Warehouse |
jdbc:oracle:thin:@example.com:1521/example.com |
|
|
The name of the JDBC driver |
oracle.jdbc.driver.OracleDriver |
|
|
The user name used to connect to the Data Warehouse |
IMPORT_DW |
|
|
The absolute path of a secure file containing the password for the user to connect to the Data Warehouse. You must provide a password file, even if you are not changing the configuration. |
/scratch/biplatform/cloning/password_DW.txt |
|
Properties in the INFORMATICA-CONFIGURATION configGroup: |
Informatica configuration |
|
|
|
The Informatica server home |
/scratch/infahome/ |
|
|
The |
/scratch/infahome/domains.info |
|
|
The directory where the Informatica parameter files are stored (or |
DEFAULT |
|
Properties in the DATASOURCES-CONNECTION-DETAILS configGroup: |
Data source connection information |
|
|
|
The physical data source type. Possible values are: |
Source |
|
|
The type of database connection. Possible values are: |
Oracle (Thin) |
|
|
The data source connection string. If you are using:
|
orcl.example.com |
|
|
The name of the table owner |
DB_USER |
|
|
The host name of the server where the database resides |
example.com |
|
|
The port where the database receives requests |
1521 |
|
|
The JDBC driver for the data source connection. The value in this field must conform to the database specifications. |
oracle.jdbc.driver.OracleDriver |
|
|
The JDBC URL for the data source connection. The value in this field must conform to the database specifications. |
jdbc:oracle:thin:@example.com:1521/orcl.example.com |
|
|
The absolute path of a secure file containing the password for the user to connect to data source. You must provide a password file, even if you are not changing the configuration. |
/scratch/biplatform/cloning/password_ds.txt |
|
|
The connection pool name |
FSCM_OLTP."Connection Pool" |
|
|
Database type of the transactional data source |
Oracle |
|
Properties in the EXTERNAL-EXECUTORS configGroup: |
External executors configuration |
|
|
|
The execution type for the tasks that will be executed by the external executor |
ODI 11g Embedded Agent |
|
|
The name of the property that must be configured to integrate DAC with other Extract, Transform, and Load (ETL) tools. There are multiple properties for the external executors. Name is the name of the property. Value is the value that defines the property. |
<name>ODIUser</name> <value>TestUser</value> |
Table 20-18 describes the move plan properties that you can change for Oracle Essbase.
Table 20-18 Move Plan Properties for Oracle Essbase
| Properties | Description | Example |
|---|---|---|
|
Properties in the EssbaseAgentConfig configGroup: |
Oracle Essbase configuration. |
|
|
|
The administration user name for Oracle Essbase |
weblogic |
|
|
The absolute path of a secure file containing the password for the Oracle Essbase administration password |
/scratch/oracle/essbase_passwd.txt |
|
Properties in the ASOAppsTableSpaceCustomizations configGroup: |
Aggregate Storage (ASO) application configuration Each ASO application has a name and |
|
|
|
The absolute path of the application file |
/scratch/oracle/aso |
|
Properties in the BSOAppsDiskVolumeCustomizations configGroup: |
Block Storage (BSO) application configuration. Each Essbase BSO application has a name and database name property, followed by the properties in the |
|
|
|
The location of the disk volume |
/scratch/biplatform |
|
|
The file type of the disk volume, such as |
index_data |
Table 20-19 describes the move plan properties that you can change for the EPM Registry.
Table 20-19 Move Plan Properties for the EPM Registry
| Properties | Description | Example |
|---|---|---|
|
Properties in the reg.properties configGroup: |
EPM Registry |
|
|
|
The URL to connect to the EPM Registry database |
jdbc:oracle:thin:@example.com:1570/db20258 |
|
|
The name of the JDBC driver |
oracle.jdbc.OracleDriver |
|
|
The user name used to connect to the EPM database |
FUSION_BIPLATFORM |
|
|
The absolute path of a secure file containing the password for the user to connect to the EPM database. You must provide a password file, even if you are not changing the configuration. |
/scratch/biplatform/password_epm_jdbc.txt |
|
Properties in the EPM_COMPONENTS configGroup, in the DATABASE_CONN configProperty: |
EPM components configuration |
|
|
|
The database server host name |
example.com |
|
|
The database user name |
FUSION_BIPLATFORM |
|
|
The JDBC URL to connect to the database |
jdbc:oracle:thin:@example.com:1570/db20258 |
|
|
The database name. For Oracle Database, use the service name or SID |
db20258 |
|
|
The database port number |
1570 |
|
|
The absolute path of a secure file containing the password for the user to connect to the database. You must provide a password file, even if you are not changing the configuration. |
/scratch/biplatform/password_epm_db.txt |
|
Properties in the EPM_COMPONENTS configGroup, in the Default configProperty: |
EPM components configuration |
|
|
|
The host name of the front-end web server or load balancer |
example2.com |
|
|
The port of the front-end web server or load balancer. This is a subentry to the |
10621 |
|
|
The flag indicating whether the front end is in SSL mode. Valid values are |
false |
|
|
The SSL port of the front-end web server or load balancer |
10218 |
|
Properties in the WORKSPACE_APP configProperty: |
Workspace configuration |
|
|
|
The host name of the server hosting the Workspace web application |
example.com |
|
|
The port where the Workspace web application is running |
10217 |
|
|
The SSL port (if configured for SSL) where the Workspace web application is running |
10218 |
|
Properties in the EPM_COMPONENTS configGroup, in the WEB_SERVER configProperty: |
Web server configuration |
|
|
|
The host name of the web server that the web application is configured to use |
example.com |
|
|
The port where the web application is running |
10217 |
|
|
The flag indicating whether the front end is in SSL mode. Valid values are |
false |
|
Properties in the EPM_COMPONENTS configGroup, in the CALC_WEBAPP configProperty: |
EPM components configuration |
|
|
|
The host name of the server hosting the Oracle Calculation Manager web application |
example.com |
|
|
The port where the Oracle Calculation Manager web application is running |
10217 |
|
|
The SSL port (if configured for SSL) where the Oracle Calculation Manager web application is running |
10218 |
|
|
The name of the Oracle Essbase cluster. There may be more than one cluster. |
EssbaseCluster-1 |
|
Properties in the essbaseservern configProperty: |
Oracle Essbase server |
|
|
|
The host name of the Oracle Essbase server |
example.com |
|
|
The |
/scratch/rmunugal/shared_essbase |
|
|
The location of the Oracle Essbase application location |
/scratch/biplatform/instances/instance1/Essbase/essbaseserver1 |
|
|
The agent port number of the Oracle Essbase server |
9511 |
|
|
The start of the range of ports used by agent for Oracle Essbase server |
9000 |
|
|
The end of the range of ports used by agent for Oracle Essbase server |
9499 |
|
Properties in the BIEE_WEBAPP configProperty: |
Oracle BI EE web application configuration |
|
|
|
The host name of the server hosting the Oracle BI EE web application |
example.com |
|
|
The port where the Oracle BI EE web application is running |
10217 |
|
|
The SSL port (if configured for SSL) where the Oracle BI EE web application is running |
10218 |
|
Properties in the PROVIDER_SERVICES_WEB_APP configProperty: |
The Oracle Essbase APS web application configuration |
|
|
|
The host name of the server hosting the Oracle Essbase APS web application |
example.com |
|
|
The port where the Oracle Essbase APS web application is running |
10217 |
|
|
The SSL port (if configured for SSL) where the Oracle Essbase APS web application is running |
10218 |
|
Properties in the PFINANCIAL_REPORTING_WEB_APP configProperty: |
The Financial Reporting Web application configuration |
|
|
|
The host name of the server hosting the Financial Reporting web application |
example.com |
|
|
The port where the Financial Reporting web application is running |
10217 |
|
|
The SSL port (if configured for SSL) where the Financial Reporting web application is running |
10218 |
Table 20-20 describes the move plan properties that you can change for Oracle BI Action Framework.
You must modify the move plan to specify the Oracle Data Integrator properties for the target environment before you apply the copied configurations from the source environment to the target environment.
Table 20-21 describes the Oracle Data Integrator properties. Edit the values of each property.
Table 20-21 Oracle Data Integrator Properties
| Configuration Group | Property | Description | Sample Value |
|---|---|---|---|
|
|
|
ODI Master Repository ID. It should be different than source repository ID |
|
|
|
Password for the |
|
|
|
|
|
Directory location for the data source of "file" technology |
|
|
|
Directory location for the data source of "file" technology |
|
|
|
|
Drive class for "Oracle" technology |
|
|
|
|
JDBC URL for connecting to the data server |
|
|
|
|
User name for the physical data servers connection |
|
|
|
|
Password file for the physical data servers connection |
|
|
|
|
|
Agent host name |
|
|
|
Agent host port |
|
The Oracle Enterprise Crawl and Search Framework (ECSF) seed data (data in the ECSF tables) is moved from the source environment to the target environment using the configuration scripts. Running the copyConfig script creates a configuration archive that contains the snapshot of the ECSF seed data. The extractMovePlan script extracts the environment-specific ECSF configuration properties from the source environment into the move plan. You must modify the move plan to specify the ECSF parameter values for the target environment before you execute the pasteConfig script.
ECSF plug-in execution varies from domain to domain. In the CommonDomain domain, it extracts all the data from ECSF tables from source database and imports the data into the target database. In the CRMDomain, HCMDomain, and FinancialDomain domains, if the corresponding search service component is active, it updates certain records specified in the move plan. The plug-in does not do anything in other domains.
Table 20-22 describes the ECSF properties. Edit the values of the ECSF properties in the move plan.
Table 20-22 ECSF Properties
| Property | Description | Sample Value |
|---|---|---|
|
|
URL to Oracle SES administrative web service endpoint. |
|
|
|
URL to Oracle SES Query web service endpoint. |
|
|
|
URL to ECSF servlets. This URL is used to construct configuration feeds for Oracle SES. |
|
|
|
URL to ECSF servlets. This URL is used to construct configuration feeds for Oracle SES. ECSF runtime URL and ECSF Security Service URL can be set to two different servers, which is also what Oracle SES supports. |
|
|
|
URL to ECSF feed servlets. This URL is used to redirect drilldowns or actionable results. |
|
Note:
Any properties that are internally derived do not appear in the move plan.
Modify the move plan by editing the environment.properties specific entries within the movableComponent of type ESS-EXT according to the target environment.
Table 20-23 describes the Oracle Enterprise Scheduler properties. Edit the following properties, if they are available in move plan. If one or more properties are not available, they will be auto-populated in the environment.properties file of the target environment. Most of the properties with values relative to target environment's Middleware home are derived automatically by the plug-in.
Note:
You do not need to change the value of the ID attribute in configProperty that corresponds to location of the environment.properties file.
Table 20-23 ESS Properties
| Property | Description | Sample Value |
|---|---|---|
|
|
The top-level directory of the product |
|
|
|
Colon-separated set of library directories |
|
|
|
The CSF wallet location in the Oracle Fusion Applications Middleware home |
|
|
|
The location of the |
|
|
|
The full path of the spawned job. In Windows environments, |
|
|
|
The top-level directory of the product |
|
|
|
The TNS name identifying the database to which spawned jobs should connect. In Windows environments, the environment variable is |
|
|
|
The top-level directory of the product |
|
You must modify the move plan to specify the Oracle Global Order Promising properties for the target environment before you apply the copied configurations from the source environment to the target environment.
Table 20-24 describes the Oracle Global Order Promising property that you must edit.
You must modify the move plan to specify the Oracle Governance, Risk and Compliance Controls properties for the target environment before you apply the copied configurations from the source environment to the target environment.
Table 20-25 describes the Oracle Governance, Risk and Compliance Controls properties. Edit the values of each property.
Table 20-26 describes the Oracle SES properties. Edit the values of these properties in the move plan.
Table 20-26 Oracle SES Properties
| Configuration Group | Property | Description | Sample Value |
|---|---|---|---|
|
|
|
The HTTP endpoint for authentication. This is the URL for the search application deployment endpoint for the Oracle Fusion customer. |
|
|
|
|
The file or HTTP URL of the configuration file. For Oracle Fusion sources, the value is the URL for the search application deployment endpoint. For WebCenter sources, the value is the WebCenter RSS crawl servlet endpoint. |
For Oracle Fusion sources:
For WebCenter sources:
For WebCenter Content sources:
|
|
|
(Optional) The Oracle Single Sign-On login URL that protects all Oracle Single Sign-On applications. This parameter is relevant when the authentication type is |
|
|
|
|
(Optional) The Oracle Single Sign-On action URL that authenticates Oracle Single Sign-On user credentials. This is the URL to which the Oracle Single Sign-On login form is submitted. This parameter is relevant when the authentication type is |
|
|
|
|
(Optional) Local directory where status files can be temporarily written |
|
|
|
|
The JDBC connect string for the database |
|
|
|
|
The password to log in to the database |
||
|
|
The prefix to the content of the URL column to form display URL. For Oracle WebCenter sources, use the Oracle WebCenter instance URL. |
|
|
|
|
|
The HTTP endpoint for Oracle Fusion authorization. For Oracle Fusion sources, the value is the URL for the search application deployment endpoint. |
For Oracle Fusion sources:
For WebCenter Content sources:
|
|
|
(Optional) The HTTP host to prefix the access URL to form the display URL. For Oracle Fusion sources, the value is the URL for the search application deployment endpoint. |
For Oracle Fusion sources:
For WebCenter Content sources:
|
|
|
|
The URL servicing the lookup of authorization information. For WebCenter sources, the value is the WebCenter authorization servlet endpoint. |
|
|
|
|
The JDBC connect string for the database |
|
|
|
|
The password to log in to the database |
||
|
|
|
The prefix to the content of the URL column to form the display URL. For WebCenter sources, use the WebCenter instance URL. |
|
Configuration information for Oracle Topology Manager is moved from a source environment to a target environment using the configuration scripts. However, you must modify the move plan to specify the Oracle Topology Manager properties for the target environment before you apply the copied configurations from the source environment to the target environment. These values specify things such as the host name and port numbers that will be used by any external applications embedded in your Oracle Fusion Applications environment. Some examples could include third-party location services, such as Google Maps, social networking applications such as LinkedIn, or any other application.
Table 20-27 describes the Oracle Topology Manager properties. Edit the property values to specify the desired destination information.
Table 20-27 Oracle Topology Manager Properties
| Configuration Group | Property | Description | Sample Value |
|---|---|---|---|
|
|
|
Protocol used by the external server for this deployed application |
|
|
|
Host name of the external server for this deployed application |
|
|
|
|
Port number of the external server for this deployed application |
|
|
|
|
Default URL for this deployed application |
|
|
|
|
|
Name of the external application |
ZmsStockQuote |
|
|
Protocol used by the external server for this deployed application |
|
|
|
|
Host name of the external server for this deployed application |
|
|
|
|
Port number of the external server for this deployed application |
|
|
|
|
Default URL for this deployed application |
|
|
|
|
|
Name of the Administration Server for this domain |
|
|
|
Protocol used by the Administration Server for this domain |
|
|
|
|
Administration Server host name for this domain |
|
|
|
|
Administration Server port number for this domain |
|
|
|
|
Protocol used by the internal server for this domain |
|
|
|
|
Host name of the internal server for this domain |
|
|
|
|
Port number of the internal server for this domain |
|
|
|
|
Protocol used by the external server for this domain |
|
|
|
|
Host name of the external server for this domain |
|
|
|
|
Port number of the external server for this domain |
|
|
|
|
Protocol used by the Node Manager for this domain |
|
|
|
|
Port number of the Node Manager for this domain |
|
|
|
|
JMX port number for this domain |
|
|
|
|
Full path of the location where Oracle Enterprise Manager is hosted for this domain |
|
|
|
|
|
Name of the environment |
|
You must modify the move plan to specify the Oracle WebCenter Content: Imaging properties for the target environment before you apply the copied configurations from the source environment to the target environment.
Table 20-28 describes the Imaging properties. Edit the value of each property.
Table 20-28 Oracle WebCenter Content: Imaging Properties
| Configuration Group | Property | Description | Sample Value |
|---|---|---|---|
|
|
Administrative user ID used during the |
|
|
|
|
|
A pipe-separated list of directories where input sources look for work. Input directory paths can be either relative or absolute. If relative paths, they are resolved against the current user directory.(The current user directory is calculated from |
|
|
|
Directory that holds the sample data for the input UI |
|
|
|
|
Location of the TrueType (TTF) font files used by the OIT rendering package |
|
|
|
|
|
Location of the repository. The value must be |
|
|
|
WebCenter Content server port used when the local content server is used. If not using local content server connection, remove the configuration property. |
|
|
|
|
Specifies ( |
|
|
|
|
|
HTTP Front End Address used in the IPM SOA: Connection Settings UI |
|
|
|
Credential alias used in the IPM SOA: Connection Settings UI |
|
Apply the copied configurations from the source environment to the target environment by running the pasteConfig script for each source entity (for example, Oracle WebLogic Server domain, OHS instance, or Node Manager) separately, using the same modified move plan. You must run the pasteConfig script on the target environment.
Run the pasteConfig script for the source entities in the following order:
CommonDomain
This must be moved first because the Metadata Services (MDS) operations for partitioning in Oracle Fusion Applications are located in the CommonDomain.
Oracle Fusion Applications domains, such as CRMDomain and FinancialDomain
All system component instances
All Node Managers
For Oracle WebLogic Server domains, run the pasteConfig script on the Administration Server host. For system components like OHS, run the script on the host where that component runs. For Node Manager, run the script on each host.
NOTE:
Before beginning all the pasteConfig activities, it is necessary to set some parameters, as follows:
To begin, set the T2P_JAVA_OPTIONS before running copyConfig on domains:
export T2P_JAVA_OPTIONS="-Dhttp.proxyHost=www-proxy.example.com-Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost"
In Windows OS, Replace export with set in the command above.
You must also set the IPV6 address and Fully Qualified Domain Hostname for -Dhttp.nonproxyHosts, as follows:
set T2P_JAVA_OPTIONS="-Dhttp.proxyHost=www-proxy.example.com-Dhttp.proxyPort=80
-Dhttp.nonProxyHosts=localhost|<AAAA:BBBB:CCCC:DDDD:EEEE:FFFF:GGGG:HHHH>|
<fully_qualified_host_name>"
where <AAAA:BBBB:CCCC:DDDD:EEEE:FFFF:GGGG:HHHH> and <fully_qualified_host_name> are replaced by the IPV6 and FQDN hostname.
In AIX, Solaris SPARC environments and Solarisx64 , in addition to step 1, it is also necessary to set the following parameter before beginning copyConfig, to avoid an out-of-memory error:
export T2P_JAVA_OPTIONS="-Dhttp.proxyHost=www-proxy.example.com-Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost -Xmx5120m -Xms5120m -XX:MaxPermSize=512M"
This section covers the following topics:
Section 20.4.2.6.1, "Running pasteConfig for Oracle WebLogic Server Domains"
Section 20.4.2.6.2, "Running pasteConfig for System Components"
Section 20.4.2.6.4, "Running pasteConfig for Oracle BI Enterprise Edition"
Section 20.4.2.6.5, "Running pasteConfig for Oracle Global Order Promising Server Instance"
Note:
If you extracted multiple move plans, you must use the move plan corresponding to each domain or system component instance.
Running pasteConfig applies the copy of the source Oracle WebLogic Server Java EE component to the target environment by unpacking and recreating the domain configuration, MDS, and component-specific configuration into the specified Middleware home.
Note:
Ensure the Oracle WebLogic Server administrator user name is the same on both source and target environments. The password will be the same across the environments if the authenticator is on an embedded LDAP, but the password can be different if the authenticator is on an external LDAP. The host name and listen port of any server can be different on the target environment, and you can modify those entries accordingly in the move plan.
You can only invoke pasteConfig once for each target entity (that is, Oracle WebLogic Server domain, OHS instance, or Node Manager). If you need to rerun pasteConfig on the same target entity, you must clean up the target environment before invoking pasteConfig again. For information about cleaning up target entities, see the "Recovering from pasteConfig Errors" section in the Oracle Fusion Applications Administrator's Troubleshooting Guide.
Use the following syntax to run pasteConfig for Oracle WebLogic Server domains:
pasteConfig -javaHome path_of_jdk -archiveLoc archive_location -targetDomainLoc trgt_domain_path -targetMWHomeLoc trgt_Middleware_Home_path -domainAdminPassword path_of_file_with_domain_admin_server_user_password -movePlanLoc move_plan_path [-appDir WLS_application_directory] [-logDirLoc log_dir_path] [-silent {true | false}]
The following example shows how to apply the copy of the domain to the /fusionapps Middleware home:
pasteConfig -javaHome USER_HOME/jrockit_160_20_D1.0.1-1705/ -archiveLoc /FIN_T2P/FIN_FinancialDomain1.jar -targetDomainLoc /net/mount2/instance/domains/server_name/FinancialDomain -targetMWHomeLoc /net/mount1/appbase/fusionapps -domainAdminPassword /home/oracle/password.txt -movePlanLoc /FIN_T2P/moveplan.xml -appDir /net/mount2/instance/applications/FinancialDomain -logDirLoc /FIN_T2P/logs -silent true
/net/mount1/appbase represents the top-level applications base directory for binary files, while /net/mount2 represents the top-level applications configuration directory for configuration files.
Table 20-29 describes the options for the pasteConfig script for Oracle WebLogic Server Java EE components.
Table 20-29 Options for the pasteConfig Script for Oracle WebLogic Server Java EE Components
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit. Note: On Windows, if the path name contains a space, then the entire value must be enclosed in double-quotes.
|
Mandatory |
|
|
None |
If the operating system is 64-bit UNIX, pass the To set the runtime property, you can specify the setenv T2P_JAVA_OPTIONS "-d64 -Djava.io.tmpdir=/home/t2p/temp" |
Optional |
|
|
|
The absolute path of the archive location. Use this option to specify the location of the archive file created by the |
Mandatory |
|
|
|
The absolute path of the target domain. The domain location must not already exist for the specified Middleware home. The domain directory may be located outside of the directory structure of the Middleware home. |
Mandatory |
|
|
|
The absolute path of the target Middleware home in which the copy of the domain will be applied. |
Mandatory |
|
|
|
The absolute path of the file containing the domain Administration Server user password. |
Mandatory |
|
|
|
The absolute path of the modified move plan in the target environment. |
Mandatory |
|
|
|
The absolute path of the Oracle WebLogic Server application directory on the target. |
Optional |
|
|
|
The location of an existing directory. A new log file is created in the directory. |
Optional |
|
|
None |
Specifies whether the operation operates silently; i.e. will not prompt for confirmation, as it would by default. To specify that it not prompt for confirmation, set this option to |
Optional |
Running pasteConfig applies the copy of a system component, such as OHS, to the target environment by pasting the configuration files of the source component into the specified Oracle instance.
Note:
You must use an Oracle home that contains the OHS binary files when you paste the OHS configuration files into the specified Oracle instance.
Use the following syntax to run pasteConfig for system components:
pasteConfig -javaHome path_of_jdk -archiveLoc archive_location -movePlanLoc move_plan_path -targetComponentName trgt_component_name -targetInstanceHomeLoc trgt_Instance_path [-targetInstanceName trgt_Instance_name] [-targetOracleHomeLoc trgt_ORACLE_HOME_path] [-silent {true | false}] [-logDirLoc log_dir_path] [-domainHostName domain_host_name] [-domainPortNum domain_port_number] [-domainAdminUserName domain_admin_username] [-domainAdminPassword domain_admin_password_file]
The following example shows how to apply the copy of the OHS instance to the Oracle instance CommonDomain_webtier and how to name the moved OHS instance ohs1:
pasteConfig -javaHome USER_HOME/jrockit_160_17_R28.0.0-679/
-archiveLoc /FIN_T2P/FIN_CommonDomain_webtier4.jar
-movePlanLoc /FIN_T2P/moveplan.xml
-targetComponentName ohs1
-targetInstanceHomeLoc /net/mount2/instance/CommonDomain_webtier
-targetInstanceName CommonDomain_webtier
-targetOracleHomeLoc /net/mount1/appbase/webtier_mwhome/webtier
-silent true
-logDirLoc /FIN_T2P/logs
/net/mount1/appbase represents the top-level applications base directory for binary files, while /net/mount2 represents the top-level applications configuration directory for configuration files.
Table 20-30 describes the options for the pasteConfig script for system components.
Table 20-30 Options for the pasteConfig Script for System Components
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit. Note: On Windows, if the path name contains a space, then the entire value must be enclosed in double-quotes.
|
Mandatory |
|
|
None |
If the operating system is 64-bit UNIX, pass the To set the runtime property, you can specify the setenv T2P_JAVA_OPTIONS "-d64 -Djava.io.tmpdir=/home/t2p/temp" |
Optional |
|
|
|
The absolute path of the archive location. Use this option to specify the location of the archive file created by the |
Mandatory |
|
|
|
The absolute path of the modified move plan in the target environment. |
Mandatory |
|
|
|
The name of the target component to be moved. The name must be unique in the instance. |
Mandatory |
|
|
|
The name of the target Oracle instance. The name must be unique in the domain. |
Mandatory for OHS |
|
|
|
The absolute path of the target Oracle instance. If the Oracle instance does not exist at that location, the command creates the instance. |
Mandatory |
|
|
|
The absolute path of the target Oracle home. The target Oracle home must exist and it must contain the binary files for the component you are moving. |
Optional, if the targetInstanceHomeLoc exists. In this case, the operation retrieves the value from the configuration. |
|
|
|
The location of an existing directory. A new log file is created in the directory. |
Optional |
|
|
None |
Specifies whether the operation operates silently; i.e. will not prompt for confirmation, as it would by default. To specify that it not prompt for confirmation, set this option to |
Optional |
|
Domain-Detail Options |
These parameters are optional. If you choose to use the domain parameters, you must use all four parameters. |
||
|
|
|
The name of the host on which the domain is configured. Use this option if you want to register the component with the domain. |
Optional, if you do not want to register the component with the domain. |
|
|
|
The port number of the domain. Use this option if you want to register the component with the domain. The domain port number is listed in the following file as the ORACLE_INSTANCE/config/OPMN/opmn/instance.properties
For example:
|
Optional, if you do not want to register the component with the domain. |
|
|
|
The name of the administrative user for the domain. For example, |
Optional, if you do not want to register the component with the domain. |
|
|
|
The password file for the administrative user for the domain. For example, Use this option if you want to register the component with the domain. |
Optional, if you do not want to register the component with the domain. |
Running pasteConfig applies the copy of Node Manager to the target environment by pasting the configuration files of the source Node Manager into the specified Node Manager home.
Note:
All the domains that are to be managed by the Node Manager should be moved before applying the copy of Node Manager to the target environment, and the Administration Server must be in running state.
After running pasteBinary, if the Node Manager directory exists in WL_HOME/common/nodemanager then remove it before running pasteConfig.
Use the following syntax to run pasteConfig for Node Manager on each machine within the topology in the target environment:
pasteConfig -javaHome path_of_jdk -archiveLoc archive_location -targetNMHomeLoc trgt_Node_Manager_Home_path -targetMWHomeLoc trgt_Middleware_Home_path -movePlanLoc move_plan_path [-logDirLoc log_dir_path] [-silent {true | false}]
The following example shows how to apply the copy of Node Manager to the Node Manager home located in CommonDomain_webtier:
pasteConfig -javaHome USER_HOME/jrockit_160_17_R28.0.0-679/
-archiveLoc /tmp/a.jar
-targetNMHomeLoc /net/mount1/appbase/fusionapps/wlserver_10.3/common/nodemanager/xyzexampledomain.com
-targetMWHomeLoc /net/mount1/appbase/fusionapps/
-movePlanLoc /FIN_T2P/moveplan.xml
-silent true
Table 20-31 describes the options for the pasteConfig script for Node Manager.
Table 20-31 Options for the pasteConfig Script for Node Manager
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit. Note: On Windows, if the path name contains a space, then the entire value must be enclosed in double-quotes.
|
Mandatory |
|
|
None |
If the operating system is 64-bit UNIX, pass the To set the runtime property, you can specify the setenv T2P_JAVA_OPTIONS "-d64 -Djava.io.tmpdir=/home/t2p/temp" |
Optional |
|
|
|
The absolute path of the archive location. Use this option to specify the location of the archive file created by the |
Mandatory |
|
|
|
The absolute path of the target Node Manager. |
Mandatory |
|
|
|
The absolute path of the target Middleware home in which the copy of Node Manager will be applied. |
Mandatory |
|
|
|
The absolute path of the modified move plan in the target environment. |
Mandatory |
|
|
|
The location of an existing directory. A new log file is created in the directory. |
Optional |
|
|
None |
Specifies whether the operation operates silently; i.e. will not prompt for confirmation, as it would by default. To specify that it not prompt for confirmation, set this option to |
Optional |
You paste the configuration of the following Oracle BI Enterprise Edition components:
Oracle BI Server
Oracle BI Presentation Services
Oracle BI Cluster Controller
Oracle BI Scheduler
JavaHost
Oracle Essbase server, if it is installed in your environment
Running pasteConfig applies the copy of Oracle BI Enterprise Edition to the target environment by pasting the configuration files of the source Oracle BI Enterprise Edition into the specified Oracle BI Enterprise Edition home.
Use the following syntax to run pasteConfig for Oracle BI Enterprise Edition on each machine within the topology in the target environment:
pasteConfig -javaHome path_of_jdk -archiveLoc archive_location -targetInstanceHomeLoc trgt_Node_Manager_Home_path -targetInstanceName trgt_Instance_name -targetOracleHomeLoc trgt_Middleware_Home_path -domainHostName domain_host_name -domainPortNum domain_port_number -domainAdminUserName domain_admin_user_name -domainAdminPassword domain_admin_password_file -movePlanLoc move_plan_path [-silent {true | false}] [-logDirLoc log_dir_path]
The following example shows how to apply the copy of Oracle BI Enterprise Edition to the Oracle BI Enterprise Edition home located in /net/mount1/appbase/instance/BIInstance on UNIX:
pasteConfig -javaHome USER_HOME/jrockit_160_17_R28.0.0-679/ -archiveLoc /FIN_T2P/BIInstance.jar -targetInstanceHomeLoc /net/mount1/appbase/instance/BIInstance -targetInstanceName BIInstance -targetOracleHomeLoc /net/mount1/appbase/fusionapps/bi -domainHostName server.us.example.com -domainPortNum 10201 -domainAdminUserName faadmin -domainAdminPassword /tmp/myencrypt.txt -silent true -movePlanLoc /FIN_T2P/moveplan.xml
Table 20-32 describes the options for the pasteConfig script for Oracle BI Enterprise Edition.
Table 20-32 Options for the pasteConfig Script for Oracle BI Enterprise Edition
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit. Note: On Windows, if the path name contains a space, then the entire value must be enclosed in double-quotes.
|
Mandatory |
|
|
|
The absolute path of the archive location. Use this option to specify the location of the archive file created by the |
Mandatory |
|
|
|
The absolute path of the target Oracle instance. If the Oracle instance does not exist at that location, the command creates the instance |
Mandatory |
|
|
|
The name of the target Oracle instance. The name must be unique in the domain. |
Mandatory |
|
|
|
The absolute path of the target Oracle home. The target Oracle home must exist and it must contain the binary files for the component you are moving. |
Mandatory |
|
|
|
The absolute path of the modified move plan in the target environment. |
Mandatory |
|
|
|
The location of an existing directory. A new log file is created in the directory. |
Optional |
|
|
None |
Specifies whether the operation operates silently; i.e. will not prompt for confirmation, as it would by default. To specify that it not prompt for confirmation, set this option to |
Optional |
|
|
|
The name of the host on which the domain is configured. |
Mandatory |
|
|
|
The port number of the source domain. |
Mandatory |
|
|
|
The name of the administrative user for the source domain. |
Mandatory |
|
|
|
The password file location for the administrative user for the domain. |
Mandatory |
Running pasteConfig applies the copy of the Oracle Global Order Promising Server configuration files on the source environment to the target environment.
Use the following syntax to run pasteConfig for Oracle Global Order Promising Server on each computer within the topology in the target environment:
pasteConfig -javaHome path_of_jdk -archiveLoc archive_location -movePlanLoc move_plan_path -targetInstanceHomeLoc target_instance_path -targetComponentName GlobalOrderPromisingServer1 -targetInstanceHomeLoc trgt_Instance_path -targetInstanceName gop_1 -targetOracleHomeLoc trgt_ORACLE_HOME_path -domainHostName domain_host_name -domainPortNum domain_port_number -domainAdminUserName domain_admin_user_name -domainAdminPassword domain_admin_password_file [-logDirLoc existing_log_directory_location] [-silent {true | false}]
The following example shows a sample pasteconfig operation configuration for an Oracle Global Order Promising Server instance:
pasteConfig -javaHome USER_HOME/jrockit_160_17_R28.0.0-679/ -archiveLoc USER_HOME/gop_1.jar -movePlanLoc USER_HOME/t2pPlans/moveplan.xml -targetComponentName GlobalOrderPromisingServer1 -targetInstanceHomeLoc /net/mount1/appbase/instance/gop_1 -targetInstanceName gop_1 -targetOracleHomeLoc /net/mount1/appbase/fusionapps/gop -logDirLoc USER_HOME/clone_logs -silent false -domainHostName server.us.example.com -domainPortNo 7051 -domainAdminUserName weblogic -domainAdminPassword USER_HOME/p1.txt
Table 20-33 describes the options for the pasteConfig script for Oracle Global Order Promising Server.
Table 20-33 Options for the pasteConfig Script for Oracle Global Order Promising Server
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit. Note: On Windows, if the path name contains a space, then the entire value must be enclosed in double-quotes.
|
Mandatory |
|
|
|
The absolute path of the archive location. Use this option to specify the location of the archive file created by the script. |
Mandatory |
|
|
|
The absolute path of the modified move plan in the target environment. |
Mandatory |
|
|
|
New name for the component to be restored. |
Mandatory |
|
|
|
The name of the target Oracle instance. The name must be unique in the domain. |
Mandatory |
|
|
|
The absolute path of the target Oracle home. The target Oracle home must exist and it must contain the binary files for the component you are moving. |
Mandatory |
|
|
|
Absolute path of instance home under which component will be restored. |
Mandatory |
|
|
|
The location of an existing directory. A new log file is created in the directory. |
Optional |
|
|
None |
Specifies whether the operation operates silently; i.e. will not prompt for confirmation, as it would by default. To specify that it not prompt for confirmation, set this option to |
Optional |
|
|
|
The name of the host on which the domain is configured. |
Mandatory |
|
|
|
The port number of the source domain. |
Mandatory |
|
|
|
The name of the administrative user for the domain. For example, |
Mandatory |
|
|
|
The password file location for the administrative user for the domain. |
Mandatory |
Moving the Oracle WebLogic Server domains from a source environment to a target environment also moves some Oracle Fusion Middleware components, but additional tasks are required for completing the move.
Section 20.4.2.7.1, "Moving Oracle BI Enterprise Edition Components,"
Section 20.4.2.7.2, "Moving Oracle BI Applications Components,"
Section 20.4.2.7.3, "Re-Installing Informatica Identity Resolution (IIR),"
Section 20.4.2.7.5, "Moving Oracle WebLogic Communication Services,"
Section 20.4.2.7.6, "Moving Oracle WebCenter Portal Data for Discussions (Optional),"
To complete the movement of Oracle BI EE, perform the following tasks:
If the passwords for following App IDs are not properly provided in move plan, you must the update target environment with the new passwords:
FUSION_APPS_PROV_PATCH_APPID
FUSION_APPS_PRC_BI_APPID
FUSION_APPS_BI_APPID
To update the APP ID passwords:
Obtain the APP ID passwords through the credential store. Use OPSS APIs or invoke CSF MBeans through scripting to retrieve passwords for FUSION_APPS_PROV_PATCH_APPID, FUSION_APPS_PRC_BI_APPID, and FUSION_APPS_BI_APPID.
For FUSION_APPS_PROV_PATCH_APPID, use CSF map as "oracle.patching" and CSF key as "FUSION_APPS_PATCH_WLS_ADMIN-KEY"
For FUSION_APPS_PRC_BI_APPID, use CSF map as "oracle.apps.security" and CSF key as "FUSION_APPS_PRC_BI_APPID-KEY"
For FUSION_APPS_BI_APPID, use CSF map as "oracle.apps.security" and CSF key as "FUSION_APPS_BI_APPID-KEY"
Change JDBC Data for the source configuration for FUSION_APPS_PROV_PATCH_APPID and FUSION_APPS_PRC_BI_APPID.
In Oracle Fusion Applications, there are two data sources which are configured using APP IDs:
BIDomain: BIAnalytics data-source
User: FUSION_APPS_PROV_PATCH_APPID
ProcurementDomain: BIAnalyticsServer data-source
User: FUSION_APPS_PRC_BI_APPID
To change JDBC data for the source configuration through the Oracle WebLogic Server Administration Console for the BIDomain and ProcurementDomain domains:
Locate the Change Center in the upper left of the Administration Console screen
Click Lock & Edit to lock the configuration edit hierarchy for the domain.
From the Domain Structure pane, choose Services > Data Sources.
The Summary of JDBC Data Sources page is displayed.
In the Data Sources table, click the BIAnalytics data source for the BIDomain domain or BIAnalysticsServer data source for the ProcurementDomain domain.
Click the Connection Pool subtab.
Locate the Password and Confirm Password fields, and modify the passwords.
Click Save.
Restart all the data source's target Managed Servers.
Change repository publishing directory connection pools through the Oracle BI Administration Tool.
Choose Start > Programs > Oracle Business Intelligence > BI Administration.
In the Administration Tool, choose File > Open > Offline.
Navigate to the repository you want to open, and then select Open.
In the Open Offline dialog box, type a valid user ID and password, and then click OK.
This opens the repository in offline mode. This mode enables you to view and modify a repository while it is not loaded into the Oracle BI Server. If you attempt to open a repository in offline mode while it is loaded into the Oracle BI Server, the repository opens in read-only mode. Only one Administration Tool session at a time can edit a repository in offline mode.
In Physical layer, select an Oracle Fusion application, for example, oracle.apps.crm*, oracle.apps.fscrm*, oracle.apps.hcm*.
Click the connection pool icon in the toolbar.
In the Connection Pool dialog, update the new password in the Connection Pool dialog, and then click OK.
Perform sub-steps e through g for other Oracle Fusion applications.
For more information about the Oracle BI administration Tool, see the section "Before You Begin" in the Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (Oracle Fusion Applications Edition).
Upload the newly update repository publishing directory to the BIDomain domain. See the section "Configuring Repositories" in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
If required, enable new agents. If new agents were created in the source environment, click each agent in the Oracle BI Presentation Services Catalog Manager (in the destination environment) to enable it. For more information about enabling new agents, see the "Working with the Properties of Catalog Objects" section of the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
To complete the movement of Oracle BI Applications, you need to move the Informatica Repository and Oracle BI Applications Configuration Manager components. You also need to ensure you have met the preconditions for moving an Oracle BI Applications environment. For instructions on completing the movement of Oracle BI Applications, see the section titled "Moving Oracle BI Applications Using the Full-Movement Scenario" in the Oracle Fusion Middleware Reference Guide for Oracle Business Intelligence Applications.
This Informatica product is installed with Fusion Applications in conjunction with Oracle Customer Relationship Management, and requires separate handling. It will need to be re-installed on the destination host. See the "Define Data Quality" chapter of the Oracle Fusion Applications Customer Data Management Implementation Guide. Search for the heading "Manually Installing Informatica Identity Resolution: Procedures."
Source types of portal, email, and mailing list are not moved from the source Oracle SES instance to the target Oracle SES instance. If you purchased an additional Oracle SES license and want to enable search non-Fusion sources, you must create these data sources in the target Oracle SES instance manually using the Oracle SES Administration GUI in the target Oracle SES instance. For information, see the Oracle Secure Enterprise Search Administrator's Guide.
Configure the following Oracle WebLogic Communication Services properties on the target environment:
pAssertedIdentityUri
controllerUri
preloadedRouteUri
Configure these attributes with the ThirdPartyCallConfiguration MBean. See Section 10.2 for configuration instructions.
If you enabled the Discussions feature of the Oracle WebCenter Portal in the source environment, then you must move the Discussions data to the destination environment. (If Discussions were not used, this step is not required.)
To move the Discussions data from the Discussions schema of Oracle WebCenter Portal, you must complete the tasks described in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal:
The domain directory is local to each machine, and pasteConfig is performed only on the Administration Server. Subsequently, if the domain has multiple machines, you must re-create the local domain by using the Oracle WebLogic Server pack and unpack commands. For more information, see Oracle Fusion Middleware Creating Templates and Domains Using the Pack and Unpack Commands.
Note:
If you have the following special conditions:
UMS is used, and
there are remote UMS servers in the source environment (and thereby also in the target environment), and
shared disk is not used
then you will need to run a cleanup step. After the pack/unpack commands have been executed, remove the temporary directories that exist on the production Admin server due to the steps described in 20.4.2.3.1. The directories to remove are the <domain_home>/config/fmwconfig/servers/<server>/applications/usermessaging directories, where <server> corresponds to the each remote server running UMS in the production environment.
After content movement is completed, all the managed servers are down. Use faststartstop to avoid having to restart each server individually. To do so:
You must create a boot.properties file in the target environment under <EACH_DOMAIN_HOME>/servers/AdminServer/security. The file contains the following properties:
password=<plain_test_password_for_admin_user> username=<admin_user_name>
The use faststartstop to restart the servers using the following command:
cd $APPTOP_LOC/fusionapps/applications/lcm/ad/bin fastartstop.sh -Start -all -appbase $APPTOP_LOC/fusionapps/applications -username FAadmin -startAdminServer true
Some environments are non-distributed, whereby the Administration Servers of all the domains and all the system component instances run on the same host. For these environments, you can automate moving binary and configuration files with a different set of these steps than those provided in Section 20.4.1 and Section 20.4.2. Note that these scripts are not intended for production, distributed environments, whereby the topology is located on multiple computers. The scripts for a non-distributed environment are intended for moving binary files and configuration files from one QA environment to another QA environment.
These scripts run in nonparallel mode rather. For example, while the CopyConfig command moves the configuration archives in one command, it runs the operation in nonparallel mode. Therefore, the operation can take some time to complete all the moves.
To move the binary files and configuration files from the source environment to the target environment:
Set the following variables on both the source and the target:
HOME: Location of the user's home directory
APPTOP: Location of the applications base, the top-level directory where the Oracle Fusion Applications binary files are located
JAVA_HOME: Location of the JDK
T2P_DIR: Location of the working directory for the movement scripts. You do not need to use this variable if you use the -workdir command is specified when running the commands.
For either UNIX or Windows, at an operating system command prompt, navigate to the following directories on both the source and the target:
(UNIX) FA_ORACLE_HOME/lcm/t2p/bin (Windows) FA_ORACLE_HOME\lcm\t2p\bin
FA_ORACLE_HOME is a directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home.
Use the following command to copy the binary files from the source environment to the target environment:
java -DT2PAdmin=user -DT2PAdminPassword=password -classpath T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain -archive archiveLocation -task CopyBinary -workdir working_dir
Note:
On Windows, separate classpath elements with a semicolon (;).
The options for the CopyBinary command follow:
| Option | Description |
|---|---|
|
|
The Oracle Fusion Middleware administration user. |
|
|
The password for the Oracle Fusion Middleware administration user. |
|
|
The dependent library files containing classes required to run the command. Use the following value for the T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain |
|
|
The absolute path of the archive location. Multiple archive files, plus a The archive location must not already exist, but its parent directory must exist and have write permission. Ensure that the archive location is not within the Middleware home structure. Once you've run both task=copyConfig,domain=BIDomain,jarfile=configBIDomain.jar,order=2 task=copyConfig,subtask=NodeManager,jarfile=configNodeManager.jar,order=4 task=copyConfig,subtask=OHS,jarfile=configOHS.jar,order=3 task=copyConfig,subtask=BIInstance,jarfile=configBIInstance.jar,order=3 task=copyConfig,domain=CommonDomain,jarfile=configCommonDomain.jar,order=1 task=copyConfig,domain=FinancialDomain,jarfile=configFinancialDomain.jar,order=2 task=copyConfig,domain=ProjectsDomain,jarfile=configProjectsDomain.jar,order=2 task=copyConfig,domain=ProcurementDomain,jarfile=configProcurementDomain.jar,order=2 task=copyConfig,domain=SCMDomain,jarfile=configSCMDomain.jar,order=2 task=copyConfig,domain=HCMDomain,jarfile=configHCMDomain.jar,order=2 task=copyConfig,domain=CRMDomain,jarfile=configCRMDomain.jar,order=2 task=copyBinary,jarfile=cloneBinary.jar,order=1 Data from this file will be used in |
|
|
The command to execute. Enter |
|
|
The directory used for log files and any other temporary files generated by the automation framework. The log files are located at |
This command moves the following from the source environment to the target environment:
binary files from the fusionapps Middleware home directory:
(UNIX) APPLICATIONS_BASE/fusionapps (Windows) APPLICATIONS_BASE\fusionapps
binary files from the webtier_mwhome Middleware home directory:
(UNIX) APPLICATIONS_BASE/webtier_mwhome (Windows) APPLICATIONS_BASE\webtier_mwhome
Files from the Oracle Database client home:
(UNIX) APPLICATIONS_BASE/dbclient (Windows) APPLICATIONS_BASE\dbclient
Binary from the Webgate Oracle home:
(UNIX) APPLICATIONS_BASE/webtier_mwhome/webgate (Windows) APPLICATIONS_BASE\webtier_mwhome\webgate
where APPLICATIONS_BASE (/net/mount1/appbase) represents the top-level applications base directory for binary files. For information about the Oracle Fusion Applications directory structure, see Section 1.2.3.
Use the following command to unpack all binary files in the target environment:
java -classpath T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain -archive archiveLocation -control T2PControl.dat_location -task PasteBinary -idmMap [map into work directory on idm server]-workdir working_dir [-invPtr <invPtr location>]
Note:
On Windows, separate classpath elements with a semicolon (;).
When checking pasteBinary process status in the logs, note that it is possible to have an exit status of 0 (success) along with a SEVERE message. This indicates that an error occurred. Check the log error file for information on how to resolve the failure and run pasteBinary again
The options for the PasteBinary command follow:
| Options | Description |
|---|---|
|
|
The dependent library files containing classes required to run the command. Use the following value for the T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain |
|
|
The absolute path of the archive location. Use this option to specify the location of the The location must exist. Ensure that the archive location is not within the Middleware home structure. |
|
|
The command to execute. Enter |
|
|
Map into the work directory on the IDM server. This is required for coping OAM artifacts. |
|
|
The directory used for log files and any other temporary files generated by the automation framework. The log files are located at |
|
|
Optional. Parameter for inventory location.Default on Linux is |
Extract the move plan by running the extractMovePlan script on the list of configuration archive locations, separated by comma. See Section 20.4.2.4.
Modify the move plan to specify properties for the target environment. See Section 20.4.2.5.
Export the T2P_JAVA_OPTIONS as follows:
T2P_JAVA_OPTIONS="-Dhttp.proxyHost=www.proxyhost.mycompany.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost"
Create the configuration archive from the source environment by running the CopyConfig command in the source environment:
java -classpath T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain -archive archiveLocation -task CopyConfig -workdir working_dir
Note:
On Windows, separate classpath elements with a semicolon (;).
The options for the CopyConfig command follow:
| Option | Description |
|---|---|
|
|
The dependent library files containing classes required to run the command. Use the following value for the T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain |
|
|
The absolute path of where all the JARs will be generated. Use this option to specify the location of the The archive location must not already exist, but its parent directory must exist and have write permission. Ensure that the archive location is not within the Middleware home structure. Data from this file will be used in |
|
|
The command to execute. Enter |
|
|
The directory used for log files and any other temporary files generated by the automation framework. The log files are located at |
Apply the copied configurations from the source environment to the target environment by running the PasteConfig command:
java -classpath T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain -archive archiveLocation -control T2PControl.dat location -task PasteConfig -plan moveplan -bihost bihost -workdir working_dir
Note:
On Windows, separate classpath elements with a semicolon (;).
The options for the PasteConfig command follow:
| Options | Description |
|---|---|
|
|
The dependent library files containing classes required to run the command. Use the following value for the T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain |
|
|
The absolute path of the archive location. Use this option to specify the location of the The directory must contain all files produced by the Ensure that the archive location is not within the Middleware home structure. |
|
|
The command to execute. Enter |
|
|
The absolute path of the modified move plans in the target environment. |
|
|
The host name of the target. |
|
|
The directory used for log files and any other temporary files generated by the automation framework. The log files are located at |
Create a properties file (for example, validate.properties), and enter the properties and values listed for -props in the table below.
Note: When setting NMConnectionType=SSL, you must also pass the WLST_PROPERTIES in the properties file.
Set the apptop location, as follows:
export APPROP=<apptop_LOC
Validate the domain, Managed Servers, Oracle HTTP Server, and Node Manager server status by running the Validate command:
java -classpath T2PAutomation.jar:cloningclient.jar:APPLICATIONS_BASE/fusionapps/wlserver_10.3/server/lib/weblogic.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain -task Validate -props validate.properties -hostfqdn host -workdir working_dir
The options for the Validate command follow:
| Option | Description |
|---|---|
|
|
The dependent library files containing classes required to run the command. Use the following value for the T2PAutomation.jar:cloningclient.jar:$APPTOP/fusionapps/wlserver_10.3/server/lib/weblogic.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain |
|
|
The command to execute. Enter |
|
-props |
The absolute path to the properties file name. This file provides all the required user names, passwords and has the following structure: #Properties file for a ValidateProperties file: #Script location, must be the absolute path to scripts folder, inclusive. scripts-folder=$APPTOP/fusionapps/applications/lcm/t2p/bin #Node manager information NMUser=bootstrap_admin NMPassword=password NMPort=5556
#Optional if set as environment variable.
wlserver_10.3/server/lib/fusion_trust.jks #Process id of node manager process, required on unix/linux MPid=pid #Service name of nodemanager, required on windows NMSvcName=node_manager_service #Path to domain from which to use the jps-config-jse.xml reconcile-guid-domain-path=APPLICATIONS_CONFIG/domains/host/ |
|
-hostfqdn |
The current host name. |
|
-workdir |
The directory used for log files and any other temporary files generated by the automation framework. The log files are located at |
Complete the component-specific configuration move by performing additional movement tasks on the Oracle Fusion Middleware components. See Section 20.4.2.7.
If there are multiple machines for the domain, re-create the local domain directory using the Oracle WebLogic Server pack and unpack mechanisms. See Section 20.4.2.8.
Functional Setup Manager enables users to implement and configure all Oracle Fusion Applications as well as to move the setup data across instances. An Application Implementation Consultant user can move the setup data using Functional Setup Manager export and import functionality. This functionality can be accessed from a command line.
To move setup data from the source environment to the target environment using command line scripts:
To prepare the environment prior to running the scripts:
Identify the implementation projects used to enter and define the setup data in the source environment.
Before you move the Functional Setup Data to the target environment, you must identify the implementation projects used to enter and define the setup data in the source environment. Ask your Application Implementation Consultant user to gather the codes of the implementation projects using the following procedure for each project:
You can gather the implementation codes using Oracle Fusion Functional Setup Manager or SQL.
To gather the implementation codes using Oracle Fusion Functional Setup Manager:
Sign in to Oracle Fusion Applications with a user account that is provisioned with the necessary role, such as the predefined Application Implementation Consultant role. Contact your security administrator for details.
From the Administration menu in the work area of Oracle Fusion Applications, choose Setup and Maintenance.
In the Tasks pane, under the Implementations group, click Manage Implementation Projects.
Click an implementation project name in the Search Results.
The Implementation Project page is displayed.
In the Basic Information section, copy the value for the Code field.
Perform Steps 4 and 5 for each project.
To obtain a list of the implementation codes using SQL, use the following query:
SQL> SELECT impl_project_name, short_name from asm_impl_projects_vl;
Ensure all the Managed Servers are started in the environment. See Section 4.4.4.1.
To export the data from the source:
Set the USER_MEM_ARGS variable as follows:
export USER_MEM_ARGS="-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=1024m"
For either UNIX or Windows, at an operating system command prompt, navigate to the location of the fsmConfigurationPackageExport executable:
(UNIX) ATGPF_ORACLE_HOME/fsm/scripts (Windows) ATGPF_ORACLE_HOME\fsm\scripts
ATGPF_ORACLE_HOME is located under the fusionapps Oracle Fusion Middleware home directory (FA_MW_HOME).
Enter fsmConfigurationPackageExport.sh (for UNIX) or fsmConfigurationPackageExport.cmd (for Windows), using the following syntax:
fsmConfigurationPackageExport
commonDomainInternalUrl=http://host.domain:port
jdbcUrl=jdbc:oracle:thin:@DB_host_name.domain/sid
fusionRuntimeSchema=fusion_runtime
fusionRuntimeSchemaPasswordFile=USER_HOME/fusionRuntimeSchemaPassword.txt
fsmUsername=user
fsmPasswordFile=USER_HOME/fusionRuntimeSchemaPassword.txt
implementationProjectCode=IMPLEMENTATION_PROJECT_CODE_TO_EXPORT
configurationPackageFile=USER_HOME/cp.zip
logFile=USER_HOME/log_file
jpsConfig=COMMON_DOMAIN_HOME/config/fmwconfig/jps-config-jse.xml
mwHomeLoc=MW_HOME
atgpfHomeLoc=ATGPF_ORACLE_HOME
[pollingInterval=interval]
[pollingLimit=limit]
The following example shows how to export the configuration package from the source instance for an implementation project named FINANCIALS_IMPLEMENTATION:
fsmConfigurationPackageExport.sh commonDomainInternalUrl=http://fusionsystemtest-w-internal-fs.example.com:7011
jdbcUrl=jdbc:oracle:thin:@db.example.com:1528:proddb
fusionRuntimeSchema=fusion_runtime
fusionRuntimeSchemaPasswordFile=USER_HOME/fusionRuntimeSchemaPassword.txt
fsmUsername=FUSION
fsmPasswordFile=USER_HOME/fusionRuntimeSchemaPassword.txt
implementationProjectCode=FINANCIALS_IMPLEMENTATION
configurationPackageFile=USER_HOME/cp.zip
logFile=USER_HOME/cpExport.log
jpsConfig=COMMON_DOMAIN_HOME/config/fmwconfig/jps-config-jse.xml
mwHomeLoc=/net/mount1/appbase/fusionapps
atgpfHomeLoc=/net/mount1/appbase/atgpf
A description of the options for the fsmConfigurationPackageExport command follow:
| Option | Description | Optional or Mandatory? |
|---|---|---|
|
|
The To obtain the URL, use Oracle Fusion Functional Setup Manager:
|
Mandatory |
|
|
The JDBC URL in the format of |
Mandatory |
|
|
The Oracle database schema name (user name) to log in to the source database. This value should always be |
Mandatory |
|
|
The absolute path to the password file, which contains the schema password to log in to the source database. |
Mandatory |
|
|
User name to log in to Oracle Fusion Functional Setup Manager that has Application Implementation Consultant job role. |
Mandatory |
|
|
The absolute path to the password file, which contains password to log in to Functional Setup Manager. |
Mandatory |
|
|
The implementation project code that must be exported from the source instance. |
Mandatory |
|
|
The absolute path to the configuration package ZIP file to save exported data. |
Mandatory |
|
|
The absolute path to the source log file. |
Mandatory |
|
|
The absolute path to the |
Mandatory |
|
|
The absolute location of the source Oracle Fusion Applications Middleware Home ( |
Mandatory |
|
|
The absolute location of the source Applications Core Oracle Home ( |
Mandatory |
|
|
The Web Service Client Policy to be used to invoke the Oracle Enterprise Scheduler Web service to submit the export process. The default is |
Optional |
|
|
The polling interval to be used to periodically check if export process is complete. The default is 5 seconds. |
Optional |
|
|
The polling limit to be used until reached to check if the export process is complete. The default is 3600 seconds. |
Optional |
config.xml File on the Common /CRM/SCM DomainsThe coherence host and port entries in this file are pointing to the source configuration and must be edited to point to the destination, as follows
Navigate to the config.xml file at <Domain_HOME>/config/config.xml
Edit these parameters: update *.coherence.localhost, *.coherence.localport, *.coherence.wka1 and *.coherence.wka1.port
Below is an example from CommonDomain/config/config.xml .You would replace the source coherence host and port, if necessary, with destination information.
<arguments>-DUCS.coherence.localhost=sourcehost.oracle.com -DUCS.coherence.localport=7061 -DUCS.coherence.wka1.port=7061 -DUCS.coherence.wka1=sourcehost.oracle.com -DJDBCProgramName=DS/CommonDomain/w lcs_server1 -Dserver.group=WLCSCluster</arguments>
Similarly, you need to update in CRMDomain/config/config.xml and SCMDomain/config/config.xml.
The fsmConfigurationPackageImport script moves the setup data for an implementation to a target instance.
To import the data on the target:
For either UNIX or Windows, at an operating system command prompt on the target, navigate to the location of the fsmConfigurationPackageImport executable:
(UNIX) ATGPF_ORACLE_HOME/fsm/scripts (Windows) ATGPF_ORACLE_HOME\fsm\scripts
ATGPF_ORACLE_HOME is located under the fusionapps Oracle Fusion Middleware home directory (FA_MW_HOME).
Enter fsmConfigurationPackageImport.sh (for UNIX) or fsmConfigurationPackageImport.cmd (for Windows), using the following syntax:
fsmConfigurationPackageImport
commonDomainInternalUrl=http://host.domain:port
jdbcUrl=jdbc:oracle:thin:@DB_host_name.domain/sid
fusionRuntimeSchema=fusion_runtime
fusionRuntimeSchemaPasswordFile=USER_HOME/fusionRuntimeSchemaPassword.txt
fsmUsername=FUSION
fsmPasswordFile=USER_HOME/fusionRuntimeSchemaPassword.txt
configurationPackageFile=USER_HOME/cp.zip
logFile=USER_HOME/cpImport.log
jpsConfig=COMMON_DOMAIN_HOME/config/fmwconfig/jps-config-jse.xml
mwHomeLoc=MW_HOME
atgpfHomeLoc=ATGPF_ORACLE_HOME
The following example shows how to import the configuration package from the source instance:
fsmConfigurationPackageImport.sh
commonDomainInternalUrl=http://fusionsystemtest-w-internal-fs.example.com:7011
jdbcUrl=jdbc:oracle:thin:@db.example.com:1528:proddb
fusionRuntimeSchema=fusion_runtime
fusionRuntimeSchemaPasswordFile=USER_HOME/fusionRuntimeSchemaPassword.txt
fsmUsername=FUSION
fsmPasswordFile=USER_HOME/fusionRuntimeSchemaPassword.txt
configurationPackageFile=USER_HOME/cp.zip
logFile=USER_HOME/cpImport.log
jpsConfig=COMMON_DOMAIN_HOME/config/fmwconfig/jps-config-jse.xml
mwHomeLoc=/net/mount1/appbase/fusionapps
atgpfHomeLoc=/net/mount1/appbase/atgpf
The description of the options for the fsmConfigurationPackageImport command follows:
| Option | Description | Optional or Mandatory? |
|---|---|---|
|
|
The To obtain the URL, use Oracle Fusion Functional Setup Manager:
|
Mandatory |
|
|
The JDBC URL in the format of |
Mandatory |
|
|
The Oracle database schema name (user name) to log in to the target database. This value should always be |
Mandatory |
|
|
The absolute path to the password file, which contains the schema password to log in to the target database. |
Mandatory |
|
|
User name to log in to Oracle Fusion Functional Setup Manager that has Application Implementation Consultant job role. |
Mandatory |
|
|
The absolute path to the password file, which contains password to log in to Functional Setup Manager. |
Mandatory |
|
|
The absolute path to the password file, which contains password to log in to Functional Setup Manager. |
Mandatory |
|
|
The absolute path to the configuration package ZIP file to save exported data. |
Mandatory |
|
|
The absolute path to the target log file. |
Mandatory |
|
|
The absolute path to the |
Mandatory |
|
|
The absolute location of the target Oracle Fusion Applications Middleware Home ( |
Mandatory |
|
|
The absolute location of the target Applications Core Oracle Home ( |
Mandatory |
|
|
The Web Service Client Policy to be used to invoke the Oracle Enterprise Scheduler Web service to submit the import process. The default is |
Optional |
|
|
The polling interval to be used to periodically check if import process is complete. The default is 5 seconds. |
Optional |
|
|
The polling limit to be used until reached to check if the import process is complete. The default is 3600 seconds. |
Optional |
After you move the Oracle Fusion Applications components across environments, you must perform final configuration tasks, which differ between distributed and non-distributed environments. Each is described in this section:
Section 20.4.5.1, "Completing Post-Movement Tasks for a Target Distributed Environment"
Section 20.4.5.2, "Completing Post-Movement Tasks on a Target Non-Distributed Environment"
NOTE: For both distributed and non-distributed environments, it is necessary to edit the crawlerlauncher script so that the APPTOP path points to the destination, rather than the source environment. To do so:
Locate the script in APPTOP/fusionapps/ses/bin.
The file is named crawlerlauncher.sh (UNIX) or crawlerlauncher.cmd (Windows)
(UNIX and Linux): Find the line $ORACLE_HOME/bin/clexecutor.sh "$1" <APPTOP>/instance/ess/search/log APPTOP/fusionapps APPTOP/fusionapps/wlserver_10.3 $ORACLE_HOME APPTOP/fusionapps/jdk6 Modify the first <APPTOP> location to point to the destination APPTOP.
(Windows): Modify set LOG_DIR=C:\AT\instance/ess/search/log to the correct destination folder.
In a distributed environment, after you move the Oracle Fusion Applications components across environments, you must:
Reconcile GUIDs security policies.
Because GUIDs are not preserved during movement to a target environment, you must reconcile the GUIDs in the security policies. See Section 6.4.3.
Apply any necessary topology changes, such as scaling up or scaling out the topology. For information, see Section 19.5.
Start the Managed Servers as needed. See Section 4.4.3.1.
Start a full index on all index schedules. See Section 9.4.2.7.
In a non-distributed environment, after you move the Oracle Fusion Applications components across environments, you must:
Reconcile GUIDs security policies.
Stop the Administration Server and Node Manager.
Restart the Administration Server and Node Manager.
To complete the post-movement tasks, first set APPTOP. Then:
For either UNIX or Windows, at an operating system command prompt, navigate to the following locations on the target:
(UNIX) FA_ORACLE_HOME/lcm/t2p/bin (Windows) FA_ORACLE_HOME\lcm\t2p\bin
FA_ORACLE_HOME is a directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home.
Find the postmovementsetup.properties file and enter the appropriate values for all the properties. Note that postmovementsetup.properties calls a second properties file (named postmovementsetup_password_prompts.properties). You need to enter the path to that password_prompts file as a value for password.keys.file.
Both properties files are copied below, so you can see the structure.
Once the properties files have been edited, use the following command to perform post-movement tasks on the target environment:
java -classpath T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain -task PostMovement -hostfqdn host -props postmovementsetup.properties -workdir working_dir
Note:
On Windows, separate classpath elements with a semicolon (;).
A description of the options for the PostMovement command follow:
| Option | Description |
|---|---|
|
|
The dependent library files containing classes required to run the command. Use the following value for the T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain |
|
|
The command to execute. Enter |
|
|
The current host name where this operation runs. |
|
|
Absolute path to the postmovementsetup.properties file. |
|
|
Absolute path to the working directory. |
The postmovementsetup.properties file has the following structure:
#Properties file for T2P post movement setup parameters #Script location, must be the absolute path to scripts folder, inclusive. scripts-folder=/scratch/work/t2p/scripts #Node manager information NMUser=bootstrap_admin NMPort=5556 #Process id of node manager process, required on unix/linux NMPid=<pid> #Service name of nodemanager, required on windows NMSvcName=<Node Manager Service> #Optional if set as environment variable. WLST_PROPERTIES=-Dweblogic.security.SSL.trustedCAKeyStore=$APPLTOP/fusionapps/wlserver_10.3/server/lib/fusion_trust.jks #Optional, if not specified defaults to PLAIN NMConnectionType=PLAIN #Path to domain from which to use the jps-config-jse.xml reconcile-guid-domain-path=$APPTOP/instance/domains/example.oracle.com/CommonDomain #Database info to run reconcile GUID dburl=jdbc:oracle:thin:@dbhostname:5593:DB5593 dbuser=fusion #If following 2 props are set, then it is assumed user name and passwords are the same for all domains. AdminUser=FAAdmin #Domain admin user credentials, if the above is not set CommonDomainAdminUser=FAAdmin #Put all other domain user name and password below, if needed. # Bug 13837127 #RUP4 properties password.keys.file=<absolute path to the postmovementsetup_password_prompts.properties file.> #If following property is set to true, then SSL setup won't be done. Default is to run SSL setup. run-reconcile-guid-only=false #If following property is set to true, then only cleanup operation will run. SSL setup and GUID reconcilation are ignored. #Default is run SSL setup along with clean up. run-cleanup-only=false
The postmovementsetup_password_prompts.properties file has the following structure:
#Following key value pairs represent the key names for various passwords and #values for corresponding prompt text to be asked when inputting password #from console. # Nodemanager password key name and password prompt NMPassword=Enter password for Node manager admin user #Database password to run reconcile GUID dbpassword=Enter password for database to reconcile GUID #Domain admin user password key AdminPassword=Enter password for admin user #Domain admin user credentials, if the above is not set CommonDomainAdminPassword=Enter password for CommonDomain admin user #Put all other domain password keys and prompts below, if needed, corresponding to names in postmovementsetup.properties.
|
 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|