Fusion Application Installation - Oracle Fusion Applications Administration Essentials - page 22

• Configure : This creates the Managed Server in which the applications will be

deployed. This phase configures the primordial host and the primary hosts.

• Configure-secondary : This configures the secondary hosts (if any).

• Postconfigure : This configures Oracle SOA Suite and the web tier. It in-

cludes the application of security policies.

• Startup : This starts all the Admin and Managed servers. During this phase,

the Globally Unique Identifier ( GUID ) is set up.

• Validate : This starts the Managed Server and checks the deployment.

To install the provisioning framework, go to $PROVISIONING_REPOSITORY/in-
stallers/faprov/disk1 and run the binary ./runInstallers file.

Before starting the installation

It is important to ensure that prechecks and dependencies have been addressed be-
fore starting the install. Restarting an install is troublesome and time consuming. It
is better to have all the requirements in place and checked out before initiating the
installation process. The following are good areas to check prior to initiating the in-
stallation:

• Check all OS prerequisites. Ensure that the entropy value is set correctly.

• Review the latest release notes and ensure that patches for OIM and the

database have been evaluated.

• Refrain from using generic hostnames, such as dev and prod. These will

cause issues when cloning the environment in the future.

• During the creation of response files, do not select Local Storage options for

the domain.

Installing the database

The Oracle Fusion Application Database can be installed in two modes:

• Manual : This allows the database to be created manually. Explicit configura-

tion variables will need to be provided as part of the installation process. This
approach is useful for production installations.

This approach is also required when a database in a Real Application
Cluster ( RAC ) mode is to be installed. During Manual process, you have