Oracle® Fusion Applications Cloning and Content Movement Administrator's Guide 11g Release 5 Refresh 8 (11.1.5) Part Number E38322-12 |
|
|
PDF · Mobi · ePub |
The procedures in this Appendix contain recommended steps for creating a Fusion Applications environment with the goal of making the cloning process as simple as possible. Some of the recommendations include:
Use generic host names and URLs. Refrain from using environment-specific descriptors, such as "test," "dev," "prod," etc., as these descriptors will get copied to the destination environment. Pay attention to this fact when creating domain names, host names, SIDs/service names, and directory structures.
Install without using the local domain/storage option. That is, use only shared storage, and do not put environment-specific labels in your directory structures or mount points.
This section gives recommendations for the following aspects of Fusion Applications installation:
For demonstration purposes, the sample environment contains all product families, and uses four servers, total: two for Identity Management, and two for Fusion Applications, with web tier and midtier sharing the same host. You can modify the principles of this recommendation to fit your own host and product requirements.
When cloning, remember that the destination topology is only as flexible as the source topology.
Recommended component allocation is as follows:
Component | Abstract Host Name |
---|---|
Identity Management Database(s) |
idmdb.mycompany.com |
Identity Management MidTier |
idmmidtier.mycompany.com |
Identity Management WebTier |
idmwebtier.mycompany.com |
Fusion Applications Database |
fusiondb.mycompany.com |
Fusion Applications WebTier |
fusionapps.mycompany.com |
CommonDomain |
fusionapps.mycompany.com |
BIDomain |
fusionapps.mycompany.com |
CRMDomain |
fusionapps.mycompany.com |
ICDomain |
fusionapps.mycompany.com |
SCMDomain |
fusionapps.mycompany.com |
HCMDomain |
fusionapps.mycompany.com |
FinancialDomain |
fusionapps.mycompany.com |
ProjectsDomain |
fusionapps.mycompany.com |
ProcurementDomain |
fusionapps.mycompany.com |
It is highly recommended that all hosts use the same operating system and install user/group (with same IDs). The entries in the table are examples only. To ensure a successful install, follow the minimum hardware and software requirements in the installation documentation
Abstract Host Name | Real Host Name | OS Group |
---|---|---|
idmdb.mycompany.com |
HOST1 |
oinstall |
idmmidtier.mycompany.com |
HOST2 |
oinstall |
fusiondb.mycompany.com |
HOST3 |
oinstall |
fusionapps.mycompany.com |
HOST4 |
oinstall |
To simplify for cloning, do not use local storage. Do not use environment labels, such as "production" or "test," in your mount points. Do not use soft links to install any of the components. The examples in the table use /u01
as a shared directory among all the hosts in this setup.
Storage Mount | Cloned to Target? | Local or Shared (Source) | Local or Shared (Target) | Mount Point | Directory |
---|---|---|---|---|---|
Fusion Applications Shared |
Yes |
Shared |
Shared |
/u01 |
fa |
Fusion Applications Database |
Yes |
Shared |
Shared or Local |
/u01 |
fusiondb |
Identity Management MidTier/WebTier |
Yes |
Shared |
Shared or Local |
/u01 |
idm |
Identity Management Database(s) |
Yes |
Shared |
Shared or Local |
/u01 |
idmdb |
JDK |
Yes |
Shared |
Shared or Local |
/u01 |
jdk6 |
Repository/Staging (includes Provisioning) |
Optional |
Shared |
Shared |
/u01 |
repository |
Response Files |
No |
Shared |
- |
/u01 |
response_files |
Temporary Backup |
No |
Shared |
- |
/u01 |
backup |
These are preparatory steps before the main installation.
Preparation Point | Instructions |
---|---|
Prepare the OS |
For each host:
|
Before installing the Provisioning Framework |
Complete the following tasks:
|
Install the JDK |
Unzip the |
Install the Provisioning Framework |
Follow the documentation normally:
|
There are separate instructions for installing the database and installing the core components of Identity Management.
For cloning, use special steps to assign abstract host names. This is done in several stages, as described below, and is repeated for every Identity Management tier.
Preparation Point | Instructions |
---|---|
Before installing the Identity Management database(s) on the Identity Management Database Host |
Complete the following tasks to create an abstract host name for the Identity Management database host. Because the Provisioning Framework uses the given host name information in subsequent configurations, use a temporary name to simplify for cloning.
|
Run the database installer and create the database and listener |
Follow the documentation normally, with special attention to the following:
|
After completing the Identity Management database install |
Complete the following tasks:
|
Subsequently |
Complete the following tasks:
|
Preparation Point | Instructions |
---|---|
Before installing the Identity Management web tier and mid tier |
Complete the following tasks to create an abstract host name for the Identity Management web and mid tier host. Because the Provisioning Framework uses the given host name information in subsequent configurations, use a temporary name to simplify for cloning.
|
Install/configure Identity Management web and mid tiers |
Follow the documentation normally, with special attention to the following:
|
After installing/configuring Identity Management web and mid tiers |
Complete the following tasks:
|
Subsequently |
Complete the following tasks:
|
There are separate instructions for installing the database and installing the core components of Fusion Applications.
For cloning, use special steps to assign abstract host names. This is done in several stages, as described below, and is repeated for every Fusion Applications tier.
Preparation Point | Instructions |
---|---|
Before installing the Fusion Applications database(s) on the Fusion Applications database Host |
Complete the following tasks to create an abstract host name for the Fusion Applications database host. Because the Provisioning Framework uses the given host name information in subsequent configurations, use a temporary name to simplify for cloning.
|
Run the database installer and create the database and listener |
Follow the documentation normally, with special attention to the following:
|
After completing the Fusion Applications database install |
Complete the following tasks:
|
Subsequently |
Complete the following tasks:
|
For cloning, use special steps to assign abstract host names.
Preparation Point | Instructions |
---|---|
Before Provisioning |
On each Oracle Fusion Applications Host:
|
Run Provisioning |
Follow the documentation normally, with special attention to the following:
|
After Provisioning |
Complete the following tasks:
|
Subsequently |
Complete the following tasks:
|