| Oracle® Fusion Applications Administrator's Guide 11g Release 1 (11.1.4) Part Number E14496-06 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Administrator's Guide 11g Release 1 (11.1.4) Part Number E14496-06 |
|
|
PDF · Mobi · ePub |
This chapter describes how to move Oracle Fusion Applications components from one environment to another.
This chapter contains the following topics:
Moving the Oracle Identity Management Domain Component Artifacts
Moving Binary and Configuration Files to a Non-Distributed Target Environment
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. This process requires a combination of reinstallation (of the transaction Oracle Database and the Oracle Identity Management components) with a copy/paste 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. 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 17.4)
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 17.5)
Moving the Oracle Fusion Application binary files and configuration files. In the standard distributed installations, this is a two-part movement, described in Section 17.6 and Section 17.7.
In non-distributed QA environments, this movement is simplified (Section 17.8).
Moving the Functional Setup Data, required in both distributed and non-distributed scenarios (Section 17.9),
Completing post-movement tasks, required in both distributed and non-distributed scenarios (Section 17.10).
This section gives an overview of what components are moved, what is not moved, and what must be configured before you begin component movement.
The following artifacts are copied from the source to the destination environments, using the various movement scripts and tools:
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
Configuration 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 moved to the target environment:
Transactional data (assumed to be test transactions)
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 17.7.7.5 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
Moving your Oracle Fusion Applications components and configurations successfully requires that your source and destination topologies be configured correctly.
To prepare, perform the following steps:
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 Applications Information Technology Management, Implement Applications 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 theOracle 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.
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 "Enabling Node Manager to Run in SSL Mode for 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.
This section describes the procedures needed to move the Oracle transaction database schemas and seed data from the source to the destination environment:
You must go through the first two steps of installing a second transaction Oracle Database on a 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, you will run the Database Movement scripts described below. The scripts copy the database schemas and seed data from the source to the destination database, and perform any necessary configurations to create a matching system.
Note that test transactional data is not moved.
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 16.4 for tips on handling movement completion if the RAC installations differ between source and target.
Once the file structure and database have been installed on the destination server, use the database utility script to export the schemas and seed data from the source and import them to the destination environment.
To move these database artifacts,:
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 SID 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 |
Run the T2PDataUtil script on the target. 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 /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 SID 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. |
Oracle Identity Management handles users— their information, authentication, and access policies. Such data is required by various Oracle Fusion Applications products in order to function; therefore, the Oracle Identity Management system must be configured before the rest of the components can be moved.
This document assumes either of two possible use cases regarding the Oracle Identity Management system. In scenario 1, the entire Oracle Fusion Applications environment, including the Oracle Identity Management suite, was installed and configured on the test system and will be re-created on a fresh production system.
In scenario 2, the majority of the Oracle Fusion Applications components were installed on the test system, but the enterprise already had a production version of Oracle Identity Management that has not yet been "wired" for Oracle Fusion Applications. In this case, Oracle Identity Management movement tasks will create the Oracle Fusion Applications-related artifacts on the existing system and configure them. In this case, there will be a few extra steps noted within the tasks below. These steps ensure that the Oracle Fusion Applications-related components are installed and wired on the Oracle Identity Management system, but that necessary pre-existing users, groups, and policies are not overwritten.
In both cases, a working version of Oracle Identity Management must be installed on the destination server(s). You will then complete the multi-part process in this section to move artifacts and configurations from the source to the target Oracle Identity Management.
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 the procedures needed to move Oracle Identity Management artifacts from a source to a destination environment:
Move the security artifacts in the identity store (Section 17.5.1).
Move the policy and credential store by seeding the Oracle ADF credentials (Section 17.5.2).
Modify the Credential Store Framework (CSF) entries in the target environment (Section 17.5.3).
Move Oracle Access Manager artifacts (Section 17.5.4).
Configure Oracle Identity Manager for Oracle Fusion Applications (Section 17.5.5).
Move Oracle Identity Federation artifacts (Section 17.5.6).
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 17.9 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 Applications Information Technology Management, Implement Applications Guide for information about moving setup data
In scenario 1, you are moving from one Oracle Fusion Applications edition of Oracle Identity Management to another. In scenario 2, you are upgrading an existing Oracle Identity Management system on your production environment to work with Oracle Fusion Applications.
In both cases, you first create the Fusion Applications-specific system IDs on the destination, then move various security artifacts from the test to the production environment. Movement of the security artifacts in the identity store from the source to target environment is based on the following assumptions:
The source and target Lightweight Directory Access Protocol (LDAP) instances are based on the same product, such as Oracle Internet Directory or Active Directory.
The schemas related to LDAP in the target environment are compatible with those of the source environment. Using the same version of the directory server guarantees schema compatibility between the source and destination directory instances.
Oracle Fusion Applications and the Oracle Identity Management system have certain baseline system administrators and groups that are required for basic software functionality. Only these users, roles, and groups are moved to the target LDAP server. All other enterprise users (employees, contacts, etc.). and temporary enterprise groups are not moved.
To move the security artifacts in the identity store from the source to the destination environment, follow the procedures in the following tasks and execute them in the Oracle Identity Management domain:
Create all the required system identities (systemid) at the target LDAP,. The minimal list of users required for configuring the Oracle Fusion Applications domain includes the following:
Oracle WebLogic Server administration user
Note:
The user ID of the Oracle WebLogic Server administration user in the target environment must be the same as the user ID of the Oracle WebLogic Server administration user in the source environment. However, the passwords can be different.
Oracle Access Manager administration user
Oracle Identity Manager administration user and administration group
Other users for configuring the authentication providers in Oracle WebLogic Server
If the users were created using idmConfigTool in the source environment, you can use the tool with the same parameters in the target environment. For information, see the "Integrating Oracle Access Manager 11g with Oracle Identity Manager 11g" section in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management (Oracle Fusion Applications Edition).
Running the command creates the following complete set of artifacts:
The following groups, along with their Access Control Information:
Group with read privileges to the Users Container (orclFAUserReadPrivilegeGroup)
Group with read and write privileges to the Users Container (orclFAUserWritePrivilegeGroup)
Group with read privileges to the Groups Container (orclFAGroupReadPrivilegeGroup)
Group with write privileges to the Groups Container (orclFAGroupWritePrivilegeGroup)
Group with write privileges to a partial set of attributes (orclFAUserWritePrefsPrivilegeGroup)
Note:
In scenario 2, where an existing Oracle Identity Management system is being rewired to work with Oracle Fusion Applications, the destination identity store already exists, and its Users and Groups containers are likely already protected with Access Control Policies. Therefore, the script cannot automatically assign Access Control Information to the new Fusion Applications-related users and groups. In this case, you must manually modify the policies to provide the privileges. For information, see the "Managing Directory Access Control" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.
The user specified by the IDSTORE_READONLYUSER parameter. (This user is configured as the proxy user in the Authenticator configuration of Oracle WebLogic Server, so should be the same as the user in the source environment.) At creation, this user is assigned to the orclFAWritePrefsPrivilegeGroup and orclFAGroupReadPrivilegeGroup groups.
The user specified by the IDSTORE_READWRITEUSER parameter. At creation, this user is assigned to the orclFAUserWritePrivilegeGroup and orclFAGroupWritePrivilegeGroup groups.
The user specified by SUPER_USER. (This is the Oracle WebLogic Server administration user and must be the same as the user configured in the source environment.) At creation, this user is assigned to the orclFAUserReadPrivilegeGroup group.
The System ID container
Oracle Access Manager users
The Oracle Identity Management user. Running the command also sets the corresponding Access Control Information.
App IDs are stored under cn=appidUsers,cn=users,dc=mycompany,dc=com in the Users Container. To move these entries, use the following Lightweight Directory Interchange Format (LDIF) export and import procedure:
Dump the contents of the source App ID container to a file.
ldapsearch -h oid_hostname -p ldap_port -D "binddn" -w password -b 'cn=appidUsers,cn=users,dc=mycompany,dc=com' -L -s sub 'objectclass=*' cn sn uid givenname displayname objectclass >& appidUsersDump.ldif
Search for the naming context and replace it with the new naming context.
perl -pi -e 's/oldnamingcontext/newnamingcontext/g' appidUsersDump.ldif
Upload the LDIF file to the target environment.
ldapadd -h oid_hostname -p ldap_port -D "binddn" -w password -a -c -f appidUsersDump.ldif
App ID groups are stored under cn=appIDGroups,cn=groups,dc=mycompany,dc=com in the Groups Container.
To move these entries, use the following LDIF export and import procedure:
Dump the source entries to a file.
ldapsearch -h oid_hostname -p ldap_port -D "binddn" -w password -b 'cn=appidGroups,cn=users,dc=mycompany,dc=com' -L -s sub 'objectclass=*' "*" orclguid >& appidGroupsDump.ldif
Search for the naming context and replace it with the new naming context.
perl -pi -e 's/oldnamingcontext/newnamingcontext/g' appidGroupsDump.ldif
Upload the LDIF file to the target environment.
ldapmodify -h oid_hostname -p ldap_port -D "binddn" -w password -a -f appidGroupsDump.ldif
Enterprise roles are stored under cn=fusionGroups,cn=groups,dc=mycompany,dc=com in the LDAP directory. The enterprise roles can be associated with App ID users, App ID groups, and other enterprise users. Because the enterprise users in the source environment are not moved from the source directory to the target directory, the memberships are not moved between the source and target directories. To move these entries, use the following LDIF export, clean up, and import procedure:
Dump the source entries to a file.
ldapsearch -h oid_hostname -p ldap_port -D "binddn" -w password -b 'cn=fusionGroups,cn=users,dc=mycompany,dc=com' -L -s sub 'objectclas=*' dn cn objectclass orclguid >fusionGroupsDump.ldif
Search for the naming context and replace it with the new naming context.
perl -pi -e 's/oldnamingcontext/newnamingcontext/g' fusiongroupsDump.ldif
Upload the LDIF file to the target environment.
ldapadd -h oid_hostname -p ldap_port -D "binddn" -w password -a -c -f fusiongroupsDump.ldif
The steps differ slightly depending on whether your enterprise has the scenario 1 test case, or scenario 2.
In scenario 1, you must create the Administrators, Monitors, and Operators roles at the target identity store, then assign the required users to these roles.
Move the Administrators group from the source environment.
ldapsearch -h oid_hostname -p ldap_port -D "binddn" -w password -b 'cn=Administrators,cn=groups,dc=mycompany,dc=com >& administrators.ldif
Remove any source environment users that should not be in the group.
perl -pi -e 's/oldnamingcontext/newnamingcontext/g' administrators.ldif
Upload the LDIF file to the target environment.
ldapadd -h oid_hostname -p ldap_port -D "binddn" -w password -a -c -f administrators.ldif
Move the Monitors group from the source environment.
ldapsearch -h oid_hostname -p ldap_port -D "binddn" -w password -b 'cn=Monitors,cn=groups,dc=mycompany,dc=com >& monitors.ldif
Remove any source environment users that should not be in the group.
perl -pi -e 's/oldnamingcontext/newnamingcontext/g' monitors.ldif
Upload the LDIF file to the target environment.
ldapadd -h oid_hostname -p ldap_port -D "binddn" -w password -a -c -f monitors.ldif
Move the Operators group from the source environment.
ldapsearch -h oid_hostname -p ldap_port -D "binddn" -w password -b 'cn=Operators,cn=groups,dc=mycompany,dc=com >& operators.ldif
Remove any source environment users that should not be in the group.
perl -pi -e 's/oldnamingcontext/newnamingcontext/g' operators.ldif
Upload the LDIF file to the target environment.
ldapadd -h oid_hostname -p ldap_port -D "binddn" -w password -a -c -f operators.ldif
In scenario 2, where these groups already exist, the Identity Domain Administrator performs the following operation.
Run the command:
ORACLE_HOME=/u01/oid/oid_home export ORACLE_HOME $ORACLE_HOME/ldap/bin/oidcmprec source=SOURCE_IDM_SERVER:3060/fusionapps1 \ destination=TARGET_IDM_SERVER:3060/fusionapps1 \ base= ' "cn=groupname,cn=groups,dc=mycompany,dc=com" "cn=groups,dc=mycompany,dc=com" ' \ operation=compare \ filename=prod_dev_compare \ exclattr="orclguid userpassword authpassword authpassword;* pwdchangedtime obpassword* pwdreset" \ entod=log \ atrod=log \ mvatrdif=merge \ threads=6 \ dnthreads=4 scope=sub for groupnames 'administrators', 'operators' and 'monitors'.
This command generates a resulting LDIF file that shows the differences between the source and destination environments.
Two policy domains are created in the Oracle Fusion Applications deployments, one for Oracle Identity Management domain components and one for Oracle Fusion Applications components. To move the policy store that is related to Oracle Fusion Applications from the source environment to the target environment, follow these procedures:
To move the policy and credential store artifacts, you must first identify the policy domain created for Oracle Fusion applications. The policy domain is an LDAP container that is seeded by the Oracle Fusion Applications provisioning in the source environment. It is very important that the policy store container name is the same in both the source and target environments. Then, move the entire content of the policy store from the source environment to the target environment. For information, see the "Migrating Large Volume Policy and Credential Stores" section in the Oracle Fusion Middleware Application Security Guide.
Because there is one map for all the domains, you only need to seed the Oracle ADF credentials from one domain. The credentials are then automatically propagated to the others. For example, you perform this procedure from the CommonDomain domain.
To seed the Oracle ADF credentials:
At an operating system command prompt, navigate to the location of the WLST script:
(UNIX) FA_MW_HOME/oracle_common/common/bin (Windows) FA_MW_HOME\oracle_common\common\bin
FA_MW_HOME is named fusionapps and located under the APPLICATIONS_BASE.
Run the wlst script:
(UNIX) wlst.sh (Windows) wlst.cmd
Connect to Oracle WebLogic Server with the following WLST command:
connect([options])
See the "connect" section in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
Obtain the password for a credential in the domain credential store with the following WLST command:
listCred(map="oracle.apps.security", key="appidname-KEY")
where appidname is one of the following values:
FUSION_APPS_PRJ_ADF_APPID FUSION_APPS_ATK_BI_APPID FUSION_APPS_CRM_BI_APPID FUSION_APPS_FIN_BI_APPID FUSION_APPS_HCM_BI_APPID FUSION_APPS_IC_BI_APPID FUSION_APPS_PRC_BI_APPID FUSION_APPS_PRJ_BI_APPID FUSION_APPS_SCM_BI_APPID
See the "listCred" section in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
These credentials are automatically populated with values from the source environment in Fusion Applications Control. In Step 5 you modify these values to reflect the target environment.
Update the credentials with Fusion Applications Control using the same map and key values as used with the listCred command in Step 4:
From the navigation pane, expand the farm, WebLogic Domain, and select the domain.
From the WebLogic Domain menu, choose Security > Credentials.
The Credentials page is displayed.
In the Credential Store Provider section, expand ADF.
These credentials are automatically populated with values from the source environment.
Select a credential and click Edit.
The Edit Key dialog is displayed.
View and modify the values for a key in the following Property Name fields:
- un: This value is set to the appidname for the key. You should not have to edit this value. This property is not available for the PRJ_EssbaseProvider key.
- pw: Enter the password provided by the listCred command from Step 4. This property is not available for the PRJ_EssbaseProvider key.
- password: Enter the password provided by the listCred command from Step 4 for FUSION_APPS_PRJ_ADF_APPID.
Click OK.
Perform substeps d through f for each of the remaining keys.
You must review the credentials in the credential store and update them for the target environment. The credentials are described in Table 17-1.
Table 17-1 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 to 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 HRMS application web service SOAP interaction. The user credentials correspond to the PeopleSoft HRMS application user with access privileges to invoke the PeopleSoft 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 |
To modify the CSF entries:
For either UNIX or Windows, at an operating system command prompt, navigate to the following directories 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.
Use the following command to update the CSF entries in the target environment:
java -classpath T2PAutomation.jar:cloningclient.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain -task MoveIDM -props -props property_file -workdir working_dir
A description of the options for the MoveIDM 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 command to execute. Enter |
|
|
The absolute path to the properties file name. The properties file must have following properties: #Mandatory properties. Connection info for IDM domain. AdminUser=admin_server_user_name AdminPassword=admin_server_password AdminURL=t3://hostname:port #Script location, must be the absolute path to scripts folder, inclusive. scripts-folder=/scratch/aime/work/t2p/scripts #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 Change the sample values for your target environment. The
|
|
|
The directory used for log files and any other temporary files generated by the automation framework. The log files are located in the |
Moving the Oracle Access Manager requires three parts: moving the Oracle Access Manager Server, moving the Oracle Access Manager Webgate binary files, and moving the Oracle Access Manager Webgate configuration files.
Follow the steps in the task "Move Oracle Access Manager 11g to a New Target Environment" in the Oracle Fusion Middleware Administrator's Guide, to move Oracle Access Manager Server artifacts.
Oracle Access Manager Webgate binary files are moved as part of the webtier Oracle Middleware home binary movement. The Webgate configuration artifacts, along with the rest of the Webgate components, are moved automatically during the copyConfig or paste Config step of the OHS instance.
The component of the Oracle Identity Management suite knows as the "Oracle Identity Manager"must also be configured for Oracle Fusion Applications, as described in the following tasks:
Note:
The Administration Server, the Oracle Identity Manager, and the SOA Managed Servers must be running when you perform these tasks.
The CallbackConfiguration.xml file is an Oracle Metadata Services (MDS) document that contains information about the web services that must be invoked for completion and postprocessing callbacks. For information, see the "MDS Utilities and User Modifiable Metadata Files" chapter in the Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager.
To move CallbackConfiguration.xml from the source to the target environment:
In the source environment, use the weblogicExportMetadata.sh utility, located in IDENTITY_MANAGER_HOME/bin/, to export CallbackConfiguration.xml, located in /metadata/iam-features-callbacks/sample_data/.
Edit the CallbackConfiguration.xml file to specify the host and port of the target environment in the web service URLs.
In the target environment, import the CallbackConfiguration.xml file into MDS using the weblogicImportMetadata.sh utility located in IDENTITY_MANAGER_HOME/bin/.
To seed the Oracle Fusion Applications artifacts:
Note:
Use JConsole to invoke the managed beans (MBean), and use the Oracle WebLogic Server domain administrator credentials for performing all MBean operations.
For more information, see the Oracle Fusion Middleware Oracle WebLogic Server MBean Reference.
Invoke the MLSLanguageSeedingMBean.seedAllLanguages method to seed all the multi-language support (MLS) and multi-representation (MR) languages in the target system. This MBean method does not take any parameters.
Invoke the APPIDSeedingMBean.seedFusionAPPID method once for each App ID to create the App IDs for Oracle Fusion Applications in Oracle Identity Manager. (You can get the App IDs from the source environment where they are already seeded.) This MBean method takes a single parameter that is the actual App ID and will seed this App ID in the Oracle Identity Manager data store. For information about App IDs, see Table 3-4.
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
Oracle Identity Federation artifacts are moved from the source environment to the target environment when you move Oracle Identity Management components across environments. Therefore, Oracle Identity Federation has already been moved to the target environment.
If you want more information, see the "Moving Identity Management to an Existing Production Environment" section in the Oracle Fusion Middleware Administrator's Guide.
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 17.2 and Section 17.8.
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 17-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 17.6.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 17.6.2.
Manually move the Oracle Database installation from the source environment to the target environment. See Section 17.6.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.
Table 17-2 describes the options for the copyBinary script.
Table 17-2 Options for the copyBinary Script
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit (JDK). |
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. Use this option if the inventory location is not in the default location, so that the operation can read the Oracle homes present in the inventory. You must have write permission to the inventory location. The default location is |
Available on UNIX only. Optional, if the inventory is in the default location. Otherwise, it is mandatory. |
|
|
|
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
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
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.
Table 17-3 describes the options for the pasteBinary script.
Table 17-3 Options for the pasteBinary Script
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit |
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 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. Use this option if the inventory location is not in the default location, so that the operation can read the Oracle homes present in the inventory. You must have write permission to the inventory location. The default location is |
Available on UNIX only. Optional, if the inventory is in the default location. Otherwise, it is mandatory. |
|
|
|
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:
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 command, 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.
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 17.7.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 17.2 and Section 17.8.
Note:
On Windows, before you move the configurations to the target environment, you must set a JVM System Variable. See Section 17.7.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 17.7.3.
Extract the move plan by running the extractMovePlan script on the list of configuration archive locations, which are separated by commas. See Section 17.7.4.
Modify the move plan to specify properties for the target environment. See Section 17.7.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 17.7.6.
Complete the component-specific configuration move by performing additional movement tasks on the Oracle Fusion Middleware components. See Section 17.7.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 17.7.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 17-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:
export USER_MEM_ARGS="-Xms512m -Xmx1536m -XX:CompileThreshold=8000 -XX:PermSize=512m -XX:MaxPermSize=1024m"
For systems running JRockit:
export 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.
This section covers the following topics:
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:
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.
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 [-additionalParams search.encrypt.key=pwdfile] [-logDirLoc existing_log_directory_location] [-silent {true | false}]
The following example copies the configuration of the FinancialDomain domain:
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
The following example copies the configuration of the CommonDomain domain. Notice the use of the -additionalParams option for Oracle SES.
configConfig.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 17-4 describes the options for the copyConfig script for Oracle WebLogic Server Java EE components.
Table 17-4 Options for the copyConfig Script for Oracle WebLogic Server Java EE Components
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute location of the Java Development Kit |
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. For example, 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 |
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.
Table 17-5 describes the options for the copyConfig script for system components.
Table 17-5 Options for the copyConfig Script for System Components
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute location of the Java Development Kit |
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/abcdef03/scratch/work/mw2903/wlserver_10.3/common/nodemanager/abcdef04.us.example.com (with a folder corresponding to each Node Manager) into an archive file:
copyConfig.sh -javaHome USER_HOME/jrockit_160_17_R28.0.0-679/
-archiveLoc /FIN_T2P/node_manager_abcdef04.jar
-sourceNMHomeLoc /net/mount1/appbase/fusionapps/wlserver_10.3/common/nodemanager/abcdef04.us.example.com
-silent true
Table 17-6 describes the options for the copyConfig script for Node Manager.
Table 17-6 Options for the copyConfig Script for Node Manager
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute location of the Java Development Kit |
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/
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/welcome1.txt
-silent true
Table 17-7 describes the options for the copyConfig script for Oracle BI Enterprise Edition.
Table 17-7 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 |
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.
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
Table 17-8 describes the options for the copyConfig script for Oracle Global Order Promising Server.
Table 17-8 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 |
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 the configuration plan 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.
Use the following syntax to run the extractMovePlan script:
extractMovePlan -javaHome absolute_location_of_JDK -archiveLoc archive_location [,archive_location...] -planDirLoc move_plan_directory [-optimizationHints fusionApps,sameSchemaNameSinglePassword] [-logDirLoc existing_log_directory_location]
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
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 17-9 describes the options for the extractMovePlan script:
Table 17-9 Options for the extractMovePlan Script
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute location of the Java Development Kit |
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. In those cases, you may not see all the properties in the move plan. If the framework does not find a matching value, it does not derive the property. In those cases, you will see the 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 17-10 provides pointers to the appropriate list of properties for each component. Some of the references link to tables in the "Move Plans 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 17-10 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" |
|
Oracle WebCenter Content: Imaging |
Section 17.7.5.12, "Editing Oracle WebCenter Content: Imaging Properties" |
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 17-11 describes the FusionAppsTopology properties to edit in the move plan, if they are present.
Table 17-11 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 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 |
|
|
|
|
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 17-12 describes the move plan properties that you can change for the patching framework.
Table 17-12 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. |
adc6170361.us.oracle.com:7001 |
|
Oracle Access Manager-related properties |
The following properties are defined in |
|
|
|
Host name for Oracle Access Manager |
adc6260031.us.oracle.com |
|
|
Port for Oracle Access Manager connection |
3060 |
|
|
Host for the Administration Server on the Oracle Access Manager |
adc6260031.us.oracle.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 17-13 describes the Oracle Fusion Applications properties.
Table 17-13 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 17-14 shows the move plan properties that you can change for Oracle BI Enterprise Edition.
Table 17-14 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 17-15 describes the move plan properties that you can change for Oracle Business Intelligence Data Warehouse Administration Console (DAC).
Table 17-15 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 17-16 describes the move plan properties that you can change for Oracle Essbase.
Table 17-16 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 17-17 describes the move plan properties that you can change for the EPM Registry.
Table 17-17 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 17-18 describes the move plan properties that you can change for Oracle BI Action Framework.
Table 17-18 Oracle BI Action Framework
| Properties | Description | Sample Value |
|---|---|---|
|
Property in the location-alias configGroup: |
Action Framework configuration |
|
|
|
The URL corresponding to the action name Note that there may be more than one name/value pair. |
http://adc10001.us.oracle.com:9704/analytics |
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 17-19 describes the Oracle Data Integrator properties. Edit the values of each property.
Table 17-19 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 17-20 describes the ECSF properties. Edit the values of the ECSF properties in the move plan.
Table 17-20 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 17-21 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 17-21 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 17-22 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 17-23 describes the Oracle Governance, Risk and Compliance Controls properties. Edit the values of each property.
You must modify entries in the move plan to change the writable attributes of configuration properties (configProperty) such as server names, user names, and passwords for the target environment before you apply the copied configurations from the source environment to the target environment.
Table 17-24 describes the Oracle SES properties. Edit the values of these properties in the move plan.
Note:
Oracle SES is dependent on the SEARCH_TOP property of the ESS-EXT component. You must modify the value of the SEARCH_TOP property. For information, see Section 17.7.5.
Table 17-24 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 17-25 describes the Oracle Topology Manager properties. Edit the property values to specify the desired destination information.
Table 17-25 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 17-26 describes the Imaging properties. Edit the value of each property.
Table 17-26 Oracle WebCenter Content: Imaging Properties
| Configuration Group | Property | Description | Sample Value |
|---|---|---|---|
|
|
Administrative user ID used during the |
|
|
|
|
|
A comma- separated list of directories where input sources look for work |
|
|
|
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.
This section covers the following topics:
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 17-27 describes the options for the pasteConfig script for Oracle WebLogic Server Java EE components.
Table 17-27 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 |
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 17-28 describes the options for the pasteConfig script for system components.
Table 17-28 Options for the pasteConfig Script for System Components
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit |
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/xyz456.us.example.com
-targetMWHomeLoc /net/mount1/appbase/fusionapps/
-movePlanLoc /FIN_T2P/moveplan.xml
-silent true
Table 17-29 describes the options for the pasteConfig script for Node Manager.
Table 17-29 Options for the pasteConfig Script for Node Manager
| Option | Shortcut | Description | Mandatory or Optional? |
|---|---|---|---|
|
|
None |
The absolute path of the Java Development Kit |
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 [-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/welcome1.txt -silent true
Table 17-30 describes the options for the pasteConfig script for Oracle BI Enterprise Edition.
Table 17-30 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 |
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 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. |
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 -movePlanLoc move plan_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 17-31 describes the options for the pasteConfig script for Oracle Global Order Promising Server.
Table 17-31 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 |
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 modified move plan in the target environment. |
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 |
|
Domain-Detail Options |
|||
|
|
|
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.
Oracle BI EE. See Section 17.7.7.1.
Oracle BI Applications. See Section 17.7.7.2.
Oracle SES. See Section 17.7.7.3.
Oracle WebLogic Communication Services. See Section 17.7.7.4.
Oracle WebCenter Portal: Discussions (Optional) See Section 17.7.7.5.
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. Execute the following Execute following listCred commands to retrieve passwords for FUSION_APPS_PROV_PATCH_APPID, FUSION_APPS_PRC_BI_APPID, and FUSION_APPS_BI_APPID .
At an operating system command prompt, navigate to the location of the WLST script:
(UNIX) FA_MW_HOME/oracle_common/common/bin (Windows) FA_MW_HOME\oracle_common\common\bin
FA_MW_HOME is named fusionapps and located under the APPLICATIONS_BASE.
Run the wlst script:
(UNIX) wlst.sh (Windows) wlst.cmd
Connect to Oracle WebLogic Server with the following WLST command:
connect([options])
See the "connect" section in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
Use the following WLST commands from the fusionapps Middleware directory:
listCred(map="oracle.patching", key="FUSION_APPS_PATCH_WLS_ADMIN-KEY") listCred(map="oracle.apps.security", key="FUSION_APPS_PRC_BI_APPID-KEY") listCred(map="oracle.apps.security", key="FUSION_APPS_BI_APPID-KEY")
See the "listCred" section in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
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 target 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, see the "Moving Oracle BI Applications Using the Full-Movement Scenario" section in the Oracle Fusion Middleware Reference Guide for Oracle Business Intelligence Applications.
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 8.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 the Administration Server is using the shared storage, and the other Managed Servers on the Administration Server machine are using the local storage, then you must run the pack and unpack commands once even on the Admin Server machine to create the domain directory on the local storage.
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 17.6 and Section 17.7. 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
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. Use this option to specify the location for 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. The 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 -workdir working_dir
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 |
|
|
The directory used for log files and any other temporary files generated by the automation framework. The log files are located at |
Extract the move plan by running the extractMovePlan script on the list of configuration archive locations, separated by comma. See Section 17.7.4.
Modify the move plan to specify properties for the target environment. See Section 17.7.5.
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
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
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 |
Validate the domain, Managed Servers, Oracle HTTP Server, and Node Manager server status by running the Validate command:
java -classpath T2PAutomation.jar:cloningclient.jar:$APPTOP/fusionapps/wlserver_10.3/server/lib/weblogic.jar:obfuscatepassword.jar:ojmisc.jar oracle.t2p.automation.T2PAutomationMain -task Validate -props property_file -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 |
|
|
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 T2P post movement setup parameters #Script location, must be the absolute path to scripts folder, inclusive. scripts-folder=/scratch/aime/work/t2p/scripts #Node manager information NMUser=bootstrap_admin NMPassword=welcome1 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 #With the following true, reconcile GUID operation is run on this host. For other hosts set this to false. run-reconcile-guid=true #Path to domain from which to use the jps-config-jse.xml reconcile-guid-domain-path=/scratch/aime/work/APPTOP/instance/domains/adcdat10.us.oracle.com/CommonDomain #Database info to run reconcile GUID dburl=jdbc:oracle:thin:@jdbc:oracle:thin:@//DB_host_name.domain/sid dbuser=db_user dbpassword=db_password #If following 2 props are set, then it is assumed use name and passwords are the same for all domains. AdminUser=admin_server_user_name AdminPassword=admin_server_password #Domain admin user credentials, if the preceding is not set CommonDomainAdminUser=admin_server_user_name CommonDomainAdminPassword=admin_server_password #Put all other domain user name and password below, if needed. |
|
|
The current host name where this operation runs. |
|
|
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 17.7.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 17.7.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 3.3.3.1.4.
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 |
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:
Completing Post-Movement Tasks for a Target Distributed Environment
Completing Post-Movement Tasks on a Target Non-Distributed Environment
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 4.4.3.
Apply any necessary topology changes, such as scaling up or scaling out the topology. For information, see Section 16.5.
Start the Managed Servers as needed. See Section 3.3.3.1.
Start a full index on all index schedules. See Section 7.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:
For either UNIX or Windows, at an operating system command prompt, navigate 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.
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 properties_file -workdir working_dir
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. |
This command also deletes unnecessary files from the following directories:
(UNIX) DOMAIN_HOME/compositeConfigPlans (Windows) DOMAIN_HOME\compositeConfigPlans
This section provides a case study of moving Oracle Fusion Supply Chain Management components from a source environment to a target distributed environment, whereby the Administration Servers of the Oracle WebLogic Server domains and all the system component instances run on the multiple hosts.
In this case study, the Oracle Fusion Supply Chain Management topology, shown in Table 17-32, represents a sample topology in the source environment. It does not include a comprehensive list of applications.
Table 17-32 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 |
|
This case study describes the following steps for moving the Oracle Fusion Supply Chain Management components from a source environment to a target environment:
Task 3, "Move Oracle Identity Management Domain Component Artifacts"
Task 8, "Apply the Configurations to the Target Environment"
Task 9, "Complete the Component-Specific Configuration Move"
Before performing the full-movement tasks, performTask 1, "Ensure Source Environment is Correctly Configured"
Before performing the full-movement tasks perform Task 2, "Ensure Source and Destination Environments Fulfil Requirements".
Move the Oracle Fusion Applications-related artifacts for Oracle Identity Management from the source Oracle Identity Management domains to the target Oracle Identity Management domains. For information, see Section 17.5.
You must move the binary files of each Middleware home (fusionapps and webtier_mwhome) from the source environment to the target environment.
To move the binary files:
Using the copyBinary script, create a separate copy of each source Middleware home by copying the installed binary files and patches into an archive file. For more information, see Section 17.6.1.
Using the pasteBinary script, apply the archive containing the binary files of the source Middleware home to the target environment. For more information, see Section 17.6.2.
Move the Oracle Database client installation. For information, see Section 17.6.3.
Creating a configuration archive copies the source Oracle WebLogic Server domain home, OHS instance home, and Node Manager configuration files into an archive file. You must create a separate configuration archive for each Oracle WebLogic Server domain and each OHS instance in the source environment.
To create the configuration archives, run the copyConfig script for the OHS instances, Node Managers, and Oracle BI EE components, and each of the following Oracle WebLogic Server domains:
CRMDomain
CommonDomain
BIDomain
HCMDomain
FinancialDomain
ProcurementDomain
ProjectsDomain
SCMDomain
For information about running copyConfig for Oracle WebLogic Server domains, see Section 17.7.3.1.
For information about running copyConfig for OHS instances, see Section 17.7.3.2.
You must also run copyConfig for Node Manager on each machine within the topology of the source environment. For information, see Section 17.7.3.3.
Extracting the move plan consolidates into a single XML file the configuration settings of the source environment from the configuration archives, as well as from other configuration files specific to components, such as SOA composite plans and adapter plans.
To extract the move plan, run the extractMovePlan script on the list of configuration archive locations, separated by comma.
In this case study, a total of eighteen configuration archives were created; each of the Oracle WebLogic Server domains (eight archives for eight domains), each of Node Manager (eight archived for eight Node Managers), Oracle BI EE, and OHS instances.You must extract the configuration information from all eighteen configuration archives into a single move plan:
extractMovePlan.sh -javaHome USER_HOME/jrockit_160_20_D1.0.1-1705
-archiveLoc /FSCM_T2P/FSCM_WebTier.jar,/FSCM_T2P/FSCM_CRMDomain.jar,/FSCM_T2P/FSCM_CommonDomain.jar,/FSCM_T2P/FSCM_BIDomain.jar,/FSCM_T2P/HCMDomain.jar,/FSCM_T2P/FSCM_FinancialDomain.jar,/FSCM_T2P/FSCM_ProcurementDomain.jar,/FSCM_T2P/FSCM_ProjectsDomain.jar,/FSCM_T2P/FSCM_SCMDomain.jar,/FSCM_T2P/CRMDomain_NodeManager.jar,/FSCM_T2P/CommonDomain_NodeManager.jar,/FSCM_T2P/BIDomain_NodeManager.jar,/FSCM_T2P/HCMDomain_NodeManager.jar,/FSCM_T2P/FinancialDomain_NodeManager.jar,/FSCM_T2P/ProcurementDomain_NodeManager.jar,/FSCM_T2P/ProjectsDomain_NodeManager.jar,/FSCM_T2P/SCMDomain_NodeManager.jar,/FSCM_T2P/FSCM_BIComponents.jar
-planDirLoc /FSCM_T2P/move_plan
-logDirLoc /FSCM_T2P/logs
-optimizationHints fusionApps,sameSchemaNameSinglePassword
The eighteen configuration archive locations, which are separated by commas, are specified to create a single move plan called moveplan.xml or multiple archive move plans in /FSCM_T2P/move_plan.
For more information about extracting move plans, see Section 17.7.4.
You must modify the move plan to specify 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. For more information, see Section 17.7.5.
Apply the copied configurations from the source environment to the target environment by running the pasteConfig script for each of the following Oracle WebLogic Server domains, OHS instances, and Oracle BI EE components separately, using the same move plan (moveplan.xml):
CRMDomain
CommonDomain
BIDomain
HCMDomain
FinancialDomain
ProcurementDomain
ProjectsDomain
SCMDomain
You must also run pasteConfig for Node Manager on each machine within the topology in the target environment. For more information, see Section 17.7.6.3.
You must move the component-specific configurations of the Oracle Fusion Middleware components.
For more information, see Section 17.7.7.
Moving the functional setup data applies the setup configuration data of the source environment to the target environment. Move the functional setup data for all the offerings. For information, see Section 17.9.
After you move the Oracle Fusion Applications components across environments, you must complete various post-movement tasks. For information, see Section 17.10.
|
 Copyright © 2011, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|