Oracle Fusion Applications 11.1.2.9 Installation Part 5

Part 5 Provisioning Oracle Identity Management

The Oracle Identity Management Provisioning Wizard and related tools were developed to automate Oracle Identity Management Provisioning and reduce the time required to configure Oracle Identity Management for Oracle Fusion Applications.

5.1 Creating an Oracle Identity Management Provisioning Profile

Before you can perform provisioning, you must provide information about your topology to the Oracle Identity Management Provisioning Wizard. Once you have provided all the necessary input, the wizard will create a provisioning file called provisioning.rsp that you use to perform the provisioning operation.

5.2 Creating a Provisioning Profile

Before running the provisioning tool, set the following environment variables:

• Set JAVA_HOME to: /u02/jdk6
• On UNIX systems, set the DISPLAY environment variable to an active and authorized display.

To start the Oracle Identity Management Provisioning Wizard, execute the following commands from: IDMLCM_HOME/provisioning/bin, where IDMLCM_HOME is the place where you installed the Oracle Home Directory for Oracle Identity Management, using the installation script for the Oracle Identity Management Provisioning Wizard and Oracle Identity Management Patching Tools

Login to host idm01 with applmgr user

cd /u01/app/idmlcm/Oracle_IDMLCM1/provisioning/bin

./idmProvisioningWizard.sh

The Welcome page provides a brief overview of the wizard and lists some requirements that must be met.

Click Next to continue.

Select Create a New Identity Management Environment Provisioning Response File if you are creating a response file for the first time.

Click Next to continue.

The checkbox should be unchecked, as this feature is not supported.

Click Next to continue.

The Product List page is purely informational. It displays the list of products that are installed and configured by the Oracle Identity Management Provisioning Wizard.

Click Next to continue.

Specify descriptive information to identify this response file. This description is not associated in any way with the executable plan file, or the summary file, that you save at the end of the response file creation process.

• Response File Name: The Oracle Identity Management Provisioning Wizard provides the default title Oracle Identity Management Provisioning Response File. You can change this.
• Response File Version: The Oracle Identity Management Provisioning Wizard provides a default value, which you can change. You can use this to keep track of different file versions.
• Created By: Defaults to the operating system user who invoked the Provisioning Wizard. Set when the response file is initially created and cannot be modified for the current response file.
• Created Date: Defaults to the date that the response file was initially created. Set when the response file was initially created and cannot be modified for the current response file.
• Response File Description: Provide a description of this response file. This is an optional field.

Click Next to continue. 

Use the Install Location Configuration page to supply the location of the various directories required for installation and configuration actions.

Installation and Configuration

• Software Repository Location: Specify the location of the software repository, either by typing it in the field or by clicking the Browse button, navigating to the desired location, and selecting it. This location must contain a folder named installers, which contains the software to install.

• Software Installation Location: Specify the location on shared storage where you want the Middleware Homes to be placed, either by typing it in the field or by clicking the Browse button, navigating to the desired location, and selecting it. In a multinode scenario, this folder must be shared across all machines.

• Shared Configuration Location: Specify the shared configuration location, either by typing it in the field or by clicking the Browse button, navigating to the desired location, and selecting it.

• Enable Local Configuration Location: Select this option only when provisioning the Enterprise topology.

Tip:

This value is available in the Oracle Fusion Applications Installation Workbook - Storage tab -> Temporary Shared Storage -> Provisioning Repository Location.

Ensure that this directory path is 45 characters or fewer in length. A longer path name can cause errors during Oracle Identity Management provisioning.

Tip:

This value is available in the Oracle Fusion Applications Installation Workbook - Storage tab -> Install Directories -> IDM Software Installation Location.

In a single host environment, the shared configuration location is not actually shared.

For the Enterprise topology, this is where the artifacts to be shared across all hosts, such as keystores, scripts to start/stop services, and life cycle management information, will be created. In a multi-node scenario, this folder must be shared across all machines.

Tip:

This value is available in the Oracle Fusion Applications Installation Workbook - Storage tab -> Install Directories -> IDM Shared Configuration Location.

Depending on the decision made during the planning phase this option will be available in the Oracle Fusion Applications Installation Workbook - Storage tab -> Install Directories -> IDM Local Configuration Location. If the value is not specified in the Oracle Fusion Applications Installation Workbook, clear this checkbox.

o    Local Configuration Location: Specify the location for the local domain directory that you want to set up, either by typing it in the field or by clicking the Browse button, navigating to the desired location, and selecting it. This field is required if you selected Enable Local Applications Configuration. The specified directory must initially be empty. This folder should not be shared across hosts.

Tip:

This value is available in the Oracle Fusion Applications Installation Workbook - Storage tab -> Install Directories -> IDM Local Configuration Location.

Click Next to continue.

Use the Node Topology Configuration page to select configuration options and provide information about hosts and products.

Tip:This value is available in the Oracle Fusion Applications Installation Workbook - Environment tab -> Environment Info -> IDM Topology Type.

• Single Host: Select to provision a simple, single host topology. This topology is recommended only for test and development environments.

o    Host Name: Specify the host where you want to provision Oracle Identity Management, as a fully-qualified host name.

• EDG Topology: Select to provision a multiple host topology.

o    Product(s): This field cannot be edited. It specifies the tier that will be installed and configured on the host.

o    Host Name: Specify each host where you want to provision the corresponding product tier, as a fully-qualified host name. To install Oracle Identity Management on a single host, specify the same host name for all products.

• Configure second application instances: Select to configure second instances of the applications you specified under EDG Topology. Selecting this option will provision a highly-available environment.

o    Application(s) - Second Instance: This field cannot be edited and specifies the tier that will be installed and configured on the host.

o    Host Name: Specify the host where you want to provision the second instance of these applications, as a fully-qualified host name. To install all second instances of all products on a single host, specify the same host name for all products.

Tip:

This value is available in the Oracle Fusion Applications Installation Workbook - Topology tab:

§  Abstract Hostname (or real Hostname if no Abstract) from Topology table row that matches the following components:

§  IDM Directory

§  IDM Identity and Access

§  IDM WebTier

• Install WebTier in DMZ: Do not select this option for a Single Host topology or when the Web Tier is installed on the same host as other products.

Tip:

This value is available in the Oracle Fusion Applications Installation Workbook - Topology tab -> Topology -> DMZ (Yes/No) - for the node that corresponds to the component IDM WebTier.

Click Next to continue.
  

Use the Virtual Hosts Configuration page to select virtual host configuration options. If you selected Single Host, the Virtual Hosts Configuration page cannot be edited.

Click Next to continue.

Use the Common Passwords page to select a common password.

• Common Identity Management Password: Specify a password to be used for all administrative users in the Oracle Identity Management Suite and for keystores. The password must be at least eight characters long and must contain at least one uppercase letter and at least one number.
• Confirm Common Identity Management Password: Reenter the password.

 Click Next to continue.

Use the OID Configuration page to select configuration options for Oracle Internet Directory.

Oracle Internet Directory Configuration Parameters

• Identity Store Realm DN: Specify the Distinguished Name of the Oracle Internet Directory realm, for example: dc=mycompany,dc=com.

Tip:

This value is available in the Oracle Fusion Applications Installation Workbook - Identity Management tab -> LDAP -> Identity Store Realm DN.

• Policy Store Realm DN: This field cannot be edited. The Policy Store and Identity Store will always be the same.

Authentication Directory Type

Select one of the following authentication directories:

• Oracle Internet Directory
• Oracle Virtual Directory

 Click Next to continue.

Use the ODSM Configuration page to select configuration options for Oracle Directory Services Manager (ODSM). For Single Host, the Virtual Hosts Configuration page cannot be edited.

·         ODSM Host: This field is purely informational. The value is determined by the host entered in the Topology

·         Port: Specify the port to be used by the first ODSM instance.

Tip:This value is available in the Oracle Fusion Applications Installation Workbook - Network - Ports tab -> Identity Management Port Numbers -> IDMDomain ODSM.

Click Next to continue.

Use the OHS Configuration page to change the installation ports used for Oracle HTTP Server (OHS). 

Oracle HTTP Server for Identity Management Configuration Parameters

·         Host: This field is purely informational. The value is determined by the host entered in the Topology

·         Port: Specify the non-SSL port number to be used for the first instance of the Oracle HTTP Server.

Tip:

This value is available in the Oracle Fusion Applications Installation Workbook - Network - Ports tab -> Identity Management Port Numbers -> IDM Oracle HTTP Server.

·         SSL Port: Specify the SSL port number to be used for the first instance of the Oracle HTTP Server.

Tip:

This value is available in the Oracle Fusion Applications Installation Workbook - Network - Ports tab -> Identity Management Port Numbers -> IDM Oracle HTTP Server SSL.

·         Instance Name: This field is purely informational. It displays the instance name of the first Oracle HTTP Server.

Click Next to continue.

Use the OIM Configuration page to modify the ports used by Oracle Identity Manager and, optionally, to configure an email server.

Oracle Identity Manager Configuration Parameters

·         OIM Host: This field is purely informational. The value is determined by the host entered in the Topology

·         Port: Specify the port to be used by the Oracle Identity Manager managed servers.

Tip:

This value is available in the Oracle Fusion Applications Installation Workbook - Network - Ports tab -> Identity Management Port Numbers -> IDMDomain OIM.

Click Next to continue.

Use the OAM Configuration page to select installation options for Oracle Access Manager.

Oracle Access Manager Configuration Parameters

·                     OAM Host: This field is purely informational. The value is determined by the host entered in the Node Topology Configuration Page.

·                     OAM Port: Specify the port number of the first instance.

Tip:

This value is available in the Oracle Fusion Applications Installation Workbook - Network - Ports tab ->

• OAM Transfer Mode: Specify the transfer mode to be used by Oracle Access manager. This must be Open on AIX and Simple on other platforms.
• Cookie Domain: Specify the cookie domain. For example: .mycompany.com

Tip:

This value is available in the Oracle Fusion Applications Installation Workbook - Environment tab -> Environment Info -> Domain name.

Click Next to continue. 

Use the SOA Configuration page to enter the ports to be used by the Oracle SOA Suite Managed servers.

SOA Configuration Parameters

·                     SOA Host: This field is purely informational

·                     Port: This field specifies the port for the first Oracle SOA Suite instance. You can change this.

Tip:

This value is available in the Oracle Fusion Applications Installation Workbook - Network - Ports tab -> Identity Management Port Numbers -> IDMDomain SOA.

Click Next to continue.

Use the OID Identity Store DB Configuration page to enter the database connection details for your Oracle Internet Directory Database.

OID Identity Store DB Configuration Parameters

Tip:

These values are available in the Oracle Fusion Applications Installation Workbook - Database tab -> IDM Database or OID Database (optional).

Depending on the topology decisions made during the planning phase (Section 4.4.2.5, "Oracle Identity Management Split Database Configuration") you may have one (IDMDB) or two (OIDDB and IDMDB) Oracle Identity Management database(s). If you have an OIDDB, which is specific for OID, specify the details here. Otherwise use the information for the single IDMDB.

·         Schema User Name: This field specifies the name of the Oracle Internet Directory schema user, ODS. You cannot change this name.

·         Service Name: Specify the service name of the database service, for example: idmdb.mycompany.com

·         Schema Password: Specify the password you used when creating the Oracle Internet Directory schema using the Oracle Fusion Middleware Repository Creation Utility (Oracle Fusion Middleware RCU) when creating the FA_OIM schema.

·         Single DB: Select if you are using a single Oracle Database.

o    Host VIP Name: Specify the host name of the Oracle Database.

o    Listener Port: Specify the database listener port.

Click Next to continue.

The OID Policy Store DB Configuration page cannot be edited. 

Click Next to continue.  

Use the OIM DB Configuration page to enter information about the database that contains the schemas for Oracle Identity Manager, Oracle SOA Suite, Oracle Access Manager, and Oracle Identity Federation.

OIM DB Configuration Page

• Schema User Name: This field specifies the name of the schema user, FA_OIM. You cannot change this name.
• Service Name: Specify the service name of the database service, for example: idmdb.mycompany.com

Tip:

This value is available in the Oracle Fusion Applications Installation Workbook - Database tab -> IDM Database -> IDM DB Service Name.

• Schema Password: For creating the FA_OIM schema, specify the password you used when creating the Oracle Internet Directory schema using the Oracle Fusion Middleware RCU.
• Single DB: Select if you are using a single Oracle Database.

o    Host VIP Name: Specify the host name of the Oracle Database.

o    Listener Port: Specify the database listener port.

 Click Next to continue.

The OAM DB Configuration page cannot be edited. 

Click Next to continue.

The Load Balancer page is editable only if you have selected the EDG topology option.

Click Next to continue.

Use the Summary page to view a summary of your selections and enter additional information.

• Response File Name: Provide the name of the response file to be created.
• Provisioning Summary: Provide the name of the provisioning summary file to be created.
• Directory: Specify the directory where you want to save the Provisioning Response File.

 Click Finish to save and close.

5.3 Introduction to Performing Oracle Identity Management Provisioning

After you create the provisioning response file, you use it to provision an Oracle Identity Management environment.

There are eight stages to provisioning. These stages must be run in the following order:

1. Preverify - This checks that each of the servers being used in the topology satisfies the minimum requirements of the software being installed and configured.
2. Install - This installs all of the software and related patches present in Provisioning Repository.
3. Preconfigure - This does the following:

o    Creates OID and seeds it with Users/Groups.

o    Creates OVD

o    Configures ODSM

o    Creates the WebLogic Domain

o    Creates OHS instance

4. Configure - This does the following:

o    Associates the Policy Store to OID

o    Starts managed servers as necessary

o    Associates OAM with OID

o    Configure OIM

5. Configure-Secondary - This does the following:

o    Integrates Weblogic Domain with Web Tier

o    Register Web Tier with domain

o    Integrate OAM and OIM

6. Postconfigure - This does the following:

o    Register OID with Weblogic Domain

o    SSL Enable OID and OVD

o    Tune OID

o    Run OIM Reconciliation

o    Configure UMS Mail Server

o    Generate OAM Keystore

o    Configure OIF

o    Configure WebGate

7. Startup - This starts up all components in the topology
8. Validate - This performs a number of checks on the built topology to ensure that everything is working as it should be.

You specify the stage using the -target option to the runIDMProvisioning.sh. Each stage must be completed before the next stage can begin. Failure of a stage will necessitate a cleanup and restart.

Provisioning is accomplished by using either the command line or the Oracle Identity Management Provisioning Wizard.

5.4 Performing Oracle Identity Management Provisioning

To use the command line, you must run the command runIDMProvisioning.sh or runIDMProvisioning.bat a number of times, specifying the provisioning stage with the -target option. You MUST complete each command, in order, before running the next command.

Before running the provisioning tool, set the following environment variables:

• Set JAVA_HOME to: REPOSITORY_LOCATION/jdk6
• Check whether the TNS_ADMIN environment variable is set on your Oracle Internet Directory hosts.
•  If TNS_ADMIN is set, unset it unset TNS_ADMIN

The command syntax for the provisioning tool:

runIDMProvisioning.sh -responseFile RESPONSE_FILE -target STAGE

Where:

RESPONSE_FILE is the provisioning response file. You specified the file name and directory on the Summary page when you ran the wizard to create the file. The default value is IDMLCM_HOME/provisioning/bin/provisioning.rsp on UNIX 

STAGE is one of the stages mentioned in 5.3

5.5 Identity Management Installation Options

Select Provision an Identity Management Environment to use an existing provisioning response file to provision the environment.

If your Oracle Identity Management topology spans multiple hosts, you must make the provisioning response file accessible to all hosts (preferrably by including it on shared storage) and run the provisioning tool on each host other than the primordial host, where the Oracle Identity Management Provisioning Wizard is running.

Preverify- During this stage, the Oracle Identity Management Provisioning Wizard checks for the basic prerequisites, such as free disk space, port availability, and Database connections.

Login to host idm01 with applmgr user

./runIDMProvisioning.sh -responseFile /u01/app/idmlcm/Oracle_IDMLCM1/provisioning/bin/IDMProvisioning.rsp -target preverify

Upon Successful, Continue with next command

Install- During this stage, installs the Oracle Fusion Middleware products. The host is marked with a Home symbol in the Host column. The Domains column lists the domains deployed in the new environment.

./runIDMProvisioning.sh -responseFile /u01/app/idmlcm/Oracle_IDMLCM1/provisioning/bin/IDMProvisioning.rsp -target install

BUILD SUCCESSFUL

Total time: 92 minutes 27 seconds

Successfully finished install.

Proceed with preconfigure.

Upon Successful, Continue with next command

Preconfigure- During this stage, the Oracle Identity Management Provisioning Wizard configures Oracle Internet Directory, Oracle Virtual Directory, and Oracle Directory Services Manager. It also creates the domain and extends it for all the necessary components.

./runIDMProvisioning.sh -responseFile /u01/app/idmlcm/Oracle_IDMLCM1/provisioning/bin/IDMProvisioning.rsp -target preconfigure

BUILD SUCCESSFUL

Total time: 45 minutes 47 seconds

Successfully finished preconfigure.

Proceed with configure.

Upon Successful, Continue with next command

Configure- During this stage, the Oracle Identity Management Provisioning Wizard performs OIM configuration.

./runIDMProvisioning.sh -responseFile /u01/app/idmlcm/Oracle_IDMLCM1/provisioning/bin/IDMProvisioning.rsp -target configure

BUILD SUCCESSFUL

Total time: 4 minutes 47 seconds

Successfully finished configure-secondary.

Proceed with configure-secondary.

Upon Successful, Continue with next command

Configure-secondary- During this stage, the Oracle Identity Management Provisioning Wizard performs Oracle Identity Manager-Oracle Access Manager integration.

./runIDMProvisioning.sh -responseFile /u01/app/idmlcm/Oracle_IDMLCM1/provisioning/bin/IDMProvisioning.rsp -target configure-secondary

BUILD SUCCESSFUL

Total time: 4 minutes 47 seconds

Successfully finished configure-secondary.

Proceed with postconfigure.

Upon Successful, Continue with next command

Postconfigure- During this stage, the Oracle Identity Management Provisioning Wizard performs tuning and enables the environment for SSL communication. Oracle Identity Federation is configured in this stage.

./runIDMProvisioning.sh -responseFile /u01/app/idmlcm/Oracle_IDMLCM1/provisioning/bin/IDMProvisioning.rsp -target postconfigure

BUILD SUCCESSFUL

Total time: 34 minutes 55 seconds

Successfully finished postconfigure.

Proceed with startup.

Upon Successful, Continue with next command

During this stage, the Oracle Identity Management Provisioning Wizard starts or restarts all the services except for Oracle Identity Federation.

./runIDMProvisioning.sh -responseFile /u01/app/idmlcm/Oracle_IDMLCM1/provisioning/bin/IDMProvisioning.rsp -target startup

BUILD SUCCESSFUL

Total time: 23 minutes 48 seconds

Successfully finished startup.

Proceed with validate.

Upon Successful, Continue with next command

During this stage, the Oracle Identity Management Provisioning Wizard performs the basic validations, such as server status and Oracle Internet Directory connectivity.

./runIDMProvisioning.sh -responseFile /u01/app/idmlcm/Oracle_IDMLCM1/provisioning/bin/IDMProvisioning.rsp -target validate

BUILD SUCCESSFUL

Total time: 1 minute 55 seconds

Successfully finished validate. 

5.6 Validating the Administration Server

http://idm01.mycompany.com/console and logging in as the user weblogic_idm

Verify that all managed servers are showing a status of Running.

Verify that you can access Oracle Enterprise Manager Fusion Middleware Control by accessing the URL:

http://idm01.mycompany.com/em and logging in as the user weblogic_idm

5.7 Validating the Oracle Access Manager Configuration

To validate that this has completed correctly.

1. Access the OAM console at: http://idm01.mycompany.com/oamconsole
2. Log in as the Oracle Access Manager user.
3. Click the System Configuration tab
4. Expand Access Manager Settings - SSO Agents - OAM Agents.
5. Click the open folder icon, then click Search.
6. You should see the WebGate agents Webgate_IDM, Webgate_IDM_11g and IAMSuiteAgent.

5.8 Validating Oracle Directory Services Manager (ODSM)Validating Browser Connection to ODSM Site

Follow these steps to validate that you can connect the Oracle Directory Services Manager site in a browser:

 In a web browser, verify that you can connect to Oracle Directory Services Manager (ODSM) at:

 http://idm01.mycompany.com:port/odsm

For example, on IDMHOST1, enter this URL, where 7005 is ODSM_PORT

http://idm01.mycompany.com:7005/odsm

In a web browser, verify that you can access ODSM through the load balancer address:

http://idm01.mycompany.com/odsm

5.9 Validating ODSM Connections to Oracle Internet Directory

Validate that Oracle Directory Services Manager can create connections to Oracle Internet Directory.

Create a connection to the Oracle Internet Directory on each ODSM instance separately. Even though ODSM is clustered, the connection details are local to each node. Proceed as follows:

Launch Oracle Directory Services Manager from IDMHOST1:

http://idm01.mycompany.com:7005/odsm

Create a connection to the Oracle Internet Directory virtual host by providing the following information in ODSM:

o    Server: OIDSTORE.mycompany.com

o    Port: 636 (LDAP_LBR_SSL_PORT)

o    Enable the SSL option

o    User: cn=orcladmin

o    Password: ldap-password

Create a connection to the Oracle Internet Directory virtual host by providing the corresponding information in ODSM

5.10 Validating Oracle Identity ManagerValidating the Oracle Internet Directory Instances

To validate the Oracle Internet Directory instances, ensure that you can connect to each Oracle Internet Directory instance and the load balancing router using these commands:

Note:

Ensure that the following environment variables are set before using ldapbind:

·         ORACLE_HOME (set to IDM_BASE/products/dir/idm)

·         OID_ORACLE_INSTANCE

·         PATH - The following directory locations should be in your PATH:

ORACLE_HOME/bin

ORACLE_HOME/ldap/bin

ORACLE_HOME/ldap/admin

ldapbind -h idm01.mycompany.com -p 3060 -D "cn=orcladmin" -q

ldapbind -h idm01.mycompany.com -p 3131-D "cn=orcladmin" -q -U 1

Note:

The -q option prompts the user for a password. LDAP Tools have been modified to disable the options -w password and -P password when the environment variable LDAP_PASSWORD_PROMPTONLY is set to TRUE or 1. Use this feature whenever possible.

Validating SSL Connectivity

This section is applicable only for UNIX.

You can manually verify that the SSL connection has been set up correctly by generating a wallet and then using that wallet to access Oracle Internet Directory. Proceed as follows:

Execute the command

cd IDM_BASE/products/dir/oracle_common/bin

./SSLClientConfig.sh -component cacert

providing the following inputs:

·         LDAP host name: Name of the Oracle Internet Directory server containing the Domain Certificate

·         LDAP port: Port used to access Oracle Internet Directory (OID_LDAP_PORT), for example: 3060

·         LDAP User: Oracle Internet Directory admin user, for example: cn=orcladmin

·         Password: Oracle Internet Directory admin user password

·         SSL Domain for CA: This is IDMDomain.

·         Password for truststore: This is the password you want to assign to your wallet.

When the command executes, it generates wallets in the directory IDM_BASE/products/dir/idm/rootCA/keystores/common



Now that you have a wallet, you can test that authentication is working by executing the command:

ldapbind -h LDAPHOST1.mycompany.com -p 3131 -U 2 -D cn=orcladmin -q -W "file:IDM_BASE/products/dir/idm/rootCA/keystores/common" -Q

You will be prompted for your Oracle Internet Directory password and for the wallet password. If the bind is successful, the SSL connection has been set up correctly.

Validating Oracle Identity Manager

Validate the Oracle Identity Manager Server Instance by bringing up the Oracle Identity Manager Console in a web browser. at:

http://idm01.mycompany.com:14000/oim/

Log in using the xelsysadm username and password.

Validating Oracle SOA Suite Instance from the Web Tier

Validate Oracle SOA Suite by accessing the URL:

http://idm01.mycompany.com:8001/soa-infra

and logging in using the xelsysadm username and password.

5.11 Starting All Servers and Stopping All Servers

Provisioning created a file called startall.sh and stopall.sh to start/stop everything in the correct order on host IDM01

If you want to start the services on a single host, execute the command on that host.

Before invoking this script, set JAVA_HOME to JAVA_HOME.

During exectution you will be prompted to enter the Weblogic and Node Manager administrator passwords.

The script starts the servers in the following order:

1.       Node Manager1

2.       AdminServer

3.       wls_ods1

4.       wls_soa1

5.       wls_oim1

6.       wls_oam1

7.       wls_oif1

8.       ohs1

9.       oid1

The script to stop all servers is stopall.sh .

Before invoking this script, set JAVA_HOME to JAVA_HOME.

During execution you will be prompted to enter the Weblogic and Node Manager administrator passwords.

5.12 Performing Backups of Installation and Configuration

It is an Oracle best practices recommendation to create a backup after successfully completing the installation and configuration of each tier, or at another logical point. Create a backup after verifying that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems or failures occurs in later steps. You can discard this backup when the enterprise deployment setup is complete. After the enterprise deployment setup is complete, you can initiate the regular deployment-specific Backup and Recovery process.

Following are the main components for backup

a.    Backing Up Middleware Home

b.   Backing up Oracle Internet Directory

c.    Backing Up the Database

d.   Backing Up the WebLogic Domain

e.   Backing Up the Web Tier

Continue: Part 6 Provisioning Oracle Fusion Applications