Skip Headers
Oracle® Fusion Applications Cloning and Content Movement Administrator's Guide
11g Release 8 Refresh 8 (11.1.8)

Part Number E38322-19
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

B Best Practices: Install with Cloning in Mind

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:

This section gives recommendations for the following aspects of Fusion Applications installation:

B.1 Planning the Environment

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.

B.1.1 Component Allocation

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


B.1.2 Host Recommendations

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


B.1.3 Storage Mount Points and Directories

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


B.2 OS, Provisioning Framework, and JDK Recommendations

These are preparatory steps before the main installation.

Preparation Point Instructions

Prepare the OS

For each host:

  • Make sure the OS user specified in the Host table above exists, can log in and has access to a graphical interface (X-forwarding works but is extremely slow, VNC is recommended)

  • Make sure the OS Group specified in the Host table above exists and is the primary group of the OS User

  • Make sure there is no oraInst.loc file in the /etc directory

  • Set the JAVA_HOME environment variable to /u01/jdk6 and the PATH to include it

    export JAVA_HOME=/u01/jdk6 export PATH=$JAVA_HOME/bin:$PATH

Before installing the Provisioning Framework

Complete the following tasks:

  1. Download the zip files from E-Delivery

  2. Create directory /u01/repository

  3. Extract the installer files from E-Delivery into /u01/repository

  4. Create directory /u01/backup

  5. Create directory /u01/response_files

Install the JDK

Unzip the jdk6.zip file located at /u01/repository/installers/jdk to /u01, which creates the directory /u01/jdk6

Install the Provisioning Framework

Follow the documentation normally:

  • Install the Provisioning Framework to /u1/faprov

  • Make sure there is no /etc/oraInst.loc file and choose the option to use a local inventory and choose to create the oraInventory directory under /u01 (this will be the same oraInventory that will be used later when provisioning)

  • Save response and summary files to /u01/response_files


B.3 Identity Management Installation Recommendations

There are separate instructions for installing the database and installing the core components of Identity Management.

B.3.1 Installing Identity Management Databases

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.

  1. Edit the /etc/hosts file and add an entry for idmdb.mycompany.com at the top.

  2. Temporarily change the host name to idmdb.mycompany.com:

    hostname idmdb.mycompany.com

  3. Start a new session (logout and log back in). if using VNC, kill the current VNC session and start a new one so the new host name is properly picked up.

Run the database installer and create the database and listener

Follow the documentation normally, with special attention to the following:

  • Make sure there is no /etc/oraInst.loc file and choose the option to use a local inventory and choose to create the oraInventory directory under /u01/idmdb

  • When providing the host name, always use the abstract host name idmdb.mycompany.com

  • Use a port different from 1521 for the listener (e.g. 1522) as 1521 will be used for the Oracle Fusion Applications Database. Also use a different listener name e.g. LISTENER_IDMDB. This will enable target environments to have both Identity Management and Fusion Applications databases share a single host if needed

  • Make sure everything gets installed under /u01/idmdb, including the directories for data files. This will simplify cloning later.

After completing the Identity Management database install

Complete the following tasks:

  1. Stop all database processes (instance, listener, database control, etc.).

  2. Change the host name back to the original one.

  3. Start a new session (logout and log back in). if using VNC, kill the current VNC session and start a new one so the new host name is properly picked up.

  4. Start the database instance and listener.

  5. Verify that everything is working:

Subsequently

Complete the following tasks:

  1. Complete the remaining steps for the database e.g. RCU

  2. Stop all database processes (instance, listener, database control, etc.)

  3. Take a full cold backup of the idmdb directory using this command:

    tar -czvpf <version>idmdb_afterRCU.tgz /u01/idmdb


B.3.2 Installing Identity Management Web- and Mid Tiers

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.

  1. Edit the /etc/hosts file and add the following entries pointing to the server itself):

    idmmidtier.mycompany.com (at the top)

    idmwebtier.mycompany.com

    oididstore.mycompany.com

    policystore.mycompany.com

    idstore.mycompany.com

    idminternal.mycompany.com

    sso.mycompany.com

  2. Add an entry for idmdb.mycompany.com if it's not already there (pointing to the Identity Management database server).

  3. Temporarily change the host name to idmmidtier.mycompany.com:

    hostname idmmidtier.mycompany.com

  4. Start a new session (logout and log back in). If using VNC, kill the current VNC session and start a new one so the new host name is properly picked up.

Install/configure Identity Management web and mid tiers

Follow the documentation normally, with special attention to the following:

  • Make sure there is no /etc/oraInst.loc file and choose the option to use a local inventory. Choose to create the oraInventory directory under /u01/idm.

  • Manually create a file called oraInst.loc under /u01 with the following text:

    inventory_loc=/u01/idm/oraInventory inst_group=oinstall

  • When running config.sh, post-patching instructions, idmconfigtool and LDAPSync post-install:

    Use the alias idmmidtier.mycompany.com when referring to the host name for the Identity Management mid-tier components

    Use idmdb.mycompany.com when referring to the host name for Identity Management databases

    Use idstore.mycompany.com when referring to the host name for OVD

    Use policystore.mycompany.com when referring to the host name for OID during policy store configuration

    Use oididstore.mycompany.com when referring to the host name for OID during identity store configuration

    Use the virtual host sso.mycompany.com when referring to the HTTP URLs (web tier) for OAM and OIM

  • When creating domains and instances, make sure they are all located in a directory that is under /u01/idm (for example, /u01/idm/instance).

  • When choosing port numbers, use ports outside of the ranges that may conflict with the default ports used by Oracle Fusion Applications (in cases where Identity Management and Oracle Fusion Applications are cloned to the same server):

    For the WebLogic Administration Server, use port 17001 (or something outside the 7XXX range which is used by the Oracle Fusion Applications CommonDomain)

    For Node Manager, use port 5566 (or something other than 5556 which is the default port for the Oracle Fusion Applications Node Managers)

    For ODSM use port 17006 (or something outside the 7XXX range which is used by the Oracle Fusion Applications CommonDomain)

After installing/configuring Identity Management web and mid tiers

Complete the following tasks:

  1. Stop all processes for mid tier and web tier components (IDMDomain, nodemanager, Oracle Internet Directory (OID), OHS, ODSM, etc.)

  2. Change the host name back to the original one.

  3. Start a new session (logout and log back in). If using VNC, kill the current VNC session and start a new one so the new host name is properly picked up.

  4. Start the components and verify they are all working by using the browser to connect to:

    WLS Console, Enterprise Manager and OAM Console

    ODSM (and verifying access to the Identity and Policy stores)

    OIM Console (via HTTP Server)

Subsequently

Complete the following tasks:

  1. Stop all processes including the Identity Management databases

  2. Take a full cold backup of the idmdb and idm directories (the config process has written to the database as well, so both have to be in sync) using this command:

    tar -czvpf <version>idmdb_starter.tgz /u01/idmdbtar -czvpf <version>idm_starter.tgz /u01idm /u01/jdk6


B.4 Fusion Applications Installation Recommendations

There are separate instructions for installing the database and installing the core components of Fusion Applications.

B.4.1 Installing Fusion Applications Database

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.

  1. Edit the /etc/hosts file and add an entry for fusiondb.mycompany.com at the top.

  2. Temporarily change the host name to fusiondb.mycompany.com:

    hostname fusiondb.mycompany.com

  3. Start a new session (logout and log back in). if using VNC, kill the current VNC session and start a new one so the new host name is properly picked up.

Run the database installer and create the database and listener

Follow the documentation normally, with special attention to the following:

  • Make sure there is no /etc/oraInst.loc file and choose the option to use a local inventory and choose to create the oraInventory directory under /u01/fusiondb

  • When providing the host name, always use the alias fusiondb.mycompany.com

  • You may use regular port 1521 for the listener as conflicts have already been avoided by using 1522 for the Identity Management database listener

  • Make sure everything gets installed under /u01/fusiondb, including the directories for datafiles. This will simplify cloning later

After completing the Fusion Applications database install

Complete the following tasks:

  1. Stop all database processes (instance, listener, database control, etc.).

  2. Change the host name back to the original one.

  3. Start a new session (logout and log back in). if using VNC, kill the current VNC session and start a new one so the new host name is properly picked up.

  4. Start the database instance and listener. Verify that everything is functioning normally by connecting remotely with SQL*Plus.

Subsequently

Complete the following tasks:

  1. Complete the remaining steps for the database e.g. RCU.

  2. Stop all Fusion Applications database processes.

  3. Take a full cold backup of the fusiondb directory using this command:

    tar -czvpf <version>fusiondb_afterRCU.tgz /u01/fusiondb


B.4.2 Provisioning Fusion Applications

For cloning, use special steps to assign abstract host names.

Preparation Point Instructions

Before Provisioning

On each Oracle Fusion Applications Host:

  1. Edit the /etc/hosts file and add an entry for fusionappsX.mycompany.com at the top (where X is a number depending on how many Oracle Fusion Applications hosts you plan to have; if you have only one then make that entry fusionapps.mycompany.com).

  2. Add entries for the internal and external virtual hosts as well:

    fainternal.mycompany.com

    o faexternal.mycompany.com

  3. Temporarily change the host name to fusionappsX.mycompany.com (where X is a number depending on how many Oracle Fusion Applications hosts you plan to have; if you have only one then make that fusionapps.mycompany.com):

    hostname fusionapps.mycompany.com

  4. Start a new session (logout and log back in). if using VNC, kill the current VNC session and start a new one so the new host name is properly picked up.

Run Provisioning

Follow the documentation normally, with special attention to the following:

  • Run the Provisioning Framework from the primordial host (the one with the CommonDomain Administration Server).

  • Add the invPtrLoc option when invoking provisioningWizard.sh and runProvisioning.sh. Point it at the oraInst.loc file at /u01/faprov.

  • Install Oracle Fusion Applications to /u01/fa.

  • When providing the hostname, always use the alias fusionappsX.mycompany.com (where X is a number depending on how many Oracle Fusion Applications hosts you plan to have; if you have only one then make that fusionapps.mycompany.com).

  • In the Virtual Hosts screen, select IP-based and provide the following for host names:

    Internal: fainternal.mycompany.com

    External: faexternal.mycompany.com

  • In the LBR screen, leave un-selected (you can add a LBR later by changing the /etc/hosts entries for fainternal and faexternal)

After Provisioning

Complete the following tasks:

  1. Stop all Oracle Fusion Applications processes (you may leave the database running).

  2. Change the host name of each Oracle Fusion Applications host back to the original one.

  3. Start a new session (logout and log back in). if using VNC, kill the current VNC session and start a new one so the new host name is properly picked up.

  4. Start Oracle Fusion Applications again and verify that it is functioning correctly.

  5. Run the Post-Install steps from the documentation.

Subsequently

Complete the following tasks:

  1. Stop all processes including Oracle Fusion Applications, the Oracle Fusion Applications Database, Identity Management, and Identity Management databases

  2. Take a full cold backup of the entire environment using this command:

    tar -czvpf <version>_idmdb_complete.tgz /u01/idmdbtar -czvpf <version>idm_complete.tgz /u01/idm /u01/jdk6tar -czvpf <version>fusiondb_complete.tgz /u01/fusiondbtar -czvpf <version>fa_complete.tgz /u01/faprov /u01/fa /u01/oraInventory /u01/jdk6