2 Preparing for an Installation

2.1.1 System Requirements

Review the Oracle Fusion Applications requirements for hardware and software, minimum disk space and memory requirements, required system libraries, packages, or patches, and minimum database requirements on the Oracle Technology Network (OTN).

2.1.2 Supported Platforms

Oracle Fusion Applications is supported on the following platforms:

• Linux x86-64 (64 bit)

• Oracle Solaris SPARC (64 bit)

• Oracle Solaris x86-64 (64 bit)

• IBM AIX on POWER Systems (64 bit)

• Microsoft Windows x64 (64 bit)

Refer to the certification matrix available on the Oracle Technology Network (OTN).

2.1.3 Installing Oracle Database

Oracle Fusion Applications requires Oracle Database (11.2.0.2 or later) for storing transactional data. You can install either a single-instance Oracle Enterprise Edition Database or Oracle Real Application Clusters Database. See Chapter 3, "Installing a Transaction Database" for details.

2.1.4 Installing Oracle Identity Management Components

Before you create a provisioning plan, you must install and configure the Oracle Identity Management components necessary to manage system security. This book contains information about installing Oracle Identity Management components in these sections:

• Required Components

• Creating a Properties File

• Installation Actions for Identity Management Components

2.2.1 Tune Socket Buffer Size (AIX only)

Run the following commands as the root user:

no -o rfc1323=1

no -o sb_max = 4194304

2.2.2 Set SKIP_SLIBCLEAN Variable (AIX only)

The provisioning install phase installs the Oracle Database client and a database patch update. To prepare your environment for this action, set the SKIP_SLIBCLEAN environment variable as follows:

SKIP_SLIBCLEAN = TRUE;export SKIP_SLIBCLEAN;export SKIP_SSLIBCLEAN

Run /usr/sbin/slibclean as root.

2.2.3 Check for Required Solaris Patch

For provisioning on Solaris servers, ensure that Solaris Operating System patch 144540-01 is installed. Do this for both SPARC and x86-64-based servers.

2.2.4 Increase Open Files Limit

Increase the limit of open files to 16384 or higher for the operating system.

For Linux x64:

• Modify /etc/security/limits.conf to read as follows:

  • FUSION_USER_ACCOUNT soft nofile 32767

  • FUSION_USER_ACCOUNT hard nofile 327679

• Modify /etc/init.d as root to read as follows:

  • ulimit -Hn 32767

  • ulimit -Sn 327679

• Place the libstdc++.so.5 and libgcc_s.so.1 libraries on the server/machine chosen as the HTTP host in a single directory with at least read-only privileges for the user that will run provisioning.

For Solaris SPARC:

Edit /etc/system and set as follows:

set rlim_fd_cur=32767

set rlim_fd_max=327679

For AIX:

Modify etc/security/limits defaults to read as follows:

fsize = -1

core = 2097151

cpu = -1

data = 1024000

rss = 512000

stack = -1

stack hard = -1

nofiles = 32767

nofiles hard = 327679

2.2.5 Set Up Server and Shared Area Permissions (Windows x64)

For each host in the provisioned environment, complete these steps:

1. Create a domain\user that is part of the Administrators group.

2. Log in as the user you created.

3. Run secpol.msc (security policy) and add the domain\user you created to "Log on as service" under Local Policies > User Rights Assignment.

4. Create a fusionapps folder on a shared disk that is accessible to all hosts in the provisioned environment.

5. Create a symbolic link to the fusionapps folder you created in Step 4. Perform this step on all hosts to be provisioned. For example, at the MS-DOS prompt, type the following:

   C:\>mklink /d C:\fusionapps \\netfiler1\fusionapps

   The name of the fusionapps folder must not exceed eight characters in length.

6. Confirm that a file or folder can be created through the C:\fusionapps symbolic link from all hosts in the provisioned environment.

2.2.6 Set Up Local Port Ranges

You must define your local port range to ensure that it doesn't overlap with the ports used by the Java Virtual Machines (JVM) and other servers. This action avoids port conflicts during server startup. To view and modify localRange:

(Linux)

To view:

$cat /proc/sys/net/ipv4/ip_local_port_range

To modify:

$echo "16202 65535" > /proc/sys/net/ipv4/ip_local_port_range

(Solaris)

To view:

#/usr/sbin/ndd /dev/tcp tcp_smallest_anon_port tcp_largest_anon_port

To Modify:

#/usr/sbin/ndd -set /dev/tcp tcp_smallest_anon_port 16202

#/usr/sbin/ndd -set /dev/tcp tcp_largest_anon_port 65535

(AIX)

To view:

#/usr/sbin/no -a | fgrep ephemeral

To modify:

#/usr/sbin/no -o tcp_ephemeral_low=16202 -o tcp_ephemeral_high=65535

For more information about setting port values, see "Viewing and Changing Ports for Components" in the Oracle Fusion Applications Administrator's Guide.

2.2.7 Synchronize System Clocks

All engine and data tier servers (including SIP) must accurately synchronize their system clocks to a common time source, to within one or two milliseconds. Large differences in system clocks can cause severe problems.

2.2.8 Install Unzip Program (Windows)

You must have installed the unzip program and it must be present in your PATH.

2.2.9 Support for File Locking (UNIX)

The shared drive (NFS or CIFS) must support file locking. For NFS version 3, the advisory locking must be configured for the NFS mount. This applies to all UNIX platforms.

2.3.1 Where Do I Get the Software?

Once you have completed the necessary software licensing agreements, you can obtain the Oracle Fusion Applications software using one of these two methods:

• Oracle E-Delivery - download the Product Media Pack from the E-Delivery web site. This method provides you with a readme document that helps determine which media you need to fulfill the license you have purchased. You download only the media you need. This method of delivery is the default.

• Oracle Fusion Applications Store - obtain the Product Media Pack from the Oracle Fusion Applications Store. This method provides a complete set of the software in DVD format. You use only the DVDs that are covered by your license agreement.

Both the software delivery methods include the following components:

• Oracle Fusion Applications Installation Directory Utility (IDU)

• Oracle Fusion Applications Provisioning installer

• Oracle Database Server installer

• Oracle Database Client installer

• Oracle Fusion Applications installer

• Oracle Fusion Middleware technology stack installers

• One or more patch sets

• Electronic documentation files

2.3.2 Software Delivery Methods

A Product Media Pack refers to the groupings. Each media pack may also include a .zip file containing electronic documentation files or "Quick Install" files, which facilitate the initial installation of the software.

2.3.3 Staging the Software

The Oracle Fusion Applications Installation Directory Utility (IDU) is a standalone utility that creates the provisioning repository installation directory and stages the software components required by provisioning, including the Oracle Fusion Applications Provisioning installer. The IDU is delivered as a separate component, and is complete with everything it needs to run (bootstrap) itself.

The IDU is platform-specific and includes platform-specific JDK, ANT, and a shell or batch file to invoke the class that will do the staging. You specify the version that corresponds to your platform:

• Generic

• Linux64

• AIX

• Solaris64

• Solaris_Sparc64

• Windows64

See Section 1.1.1, "Terms and Definitions" for general descriptions of the Oracle Fusion Applications Installation Directory Utility and the Oracle Fusion Applications Provisioning framework installation.

2.4.1 Using IDU Command Line Arguments

When you run the Installation Directory Utility, you can tailor its actions by adding arguments to the start command. Valid arguments are as follows. Note that the directory creation process relies primarily on the input for the -mode and -medium arguments.

2.4.2 Running the Installation Directory Utility

The IDU creates an installation directory for the provisioning repository, using the top-level directory name and location you specify. Note that the top-level directory must be on a network or hard drive that is shared so that it is accessible to all the hosts you want to associate with the new environment.

If you want to break the directory creation process into several sessions, you stop the process with Ctrl-C and resume it later by re-starting the IDU with the -stage parameter. The utility checks to see which installers have already been copied and skips the ones that have been created. The installers skipped are reported in a system message.

If an installer is only partially added, you must re-copy that DVD from the beginning. You can also start the utility in update mode to re-stage an installer that you have already successfully staged.

Note that you must have previously installed the unzip program before you can download or copy software files. The program must be present in your PATH. Before you begin, verify that you have the program with this command:

(UNIX) which unzip

(Windows) unzip

If you get a message to the effect that "unzip is not recognized as an internal or external command, operable program or batch file," set this path:

setting>control panel>system properties>advanced tab>environment variables>system variables>location_of_unzip.

2.4.3 Installation Directory Structure

The IDU creates a provisioning repository directory structure and stages all the installers included in the software bill of materials (BOM), except for its own installer, which is included on the "StartDVD." The installers are staged in the repository_name/installers directory.

Some of the installers staged are not required by provisioning. For example, the IDU stages installers associated with Oracle Identity Management components. These components are prerequisites for provisioning an Oracle Fusion Applications environment. You install and configure them separately, as described in Section 2.1.4, "Installing Oracle Identity Management Components."

Table 2-1 lists the middleware and database installers staged by the IDU. Installers marked with "Yes" in the "Required by Provisioning" column will be installed with the provisioning framework. Installers marked with "No" or as prerequisites are not.

Table 2-2 lists the installers associated with Oracle Fusion Applications components. Installers marked with "Yes" in the "Required by Provisioning" column will be installed with the provisioning framework. Installers marked with "No" are not.

2.5.1 Run the Provisioning Installer

Run the installer from the directory where you created the provisioning repository. For example: repository_name/installers/faprov/Disk1. Use this command:

(UNIX) runInstaller

(Windows) setup.exe

The installer creates and populates the repository_name/provisioning directory.

2.5.2 Provisioning Installer Screens and Instructions

Table 2-3 lists the steps for running the provisioning framework installer. For examples of the interview screens, see Appendix A, "Provisioning Framework Screens."

2.5.3 Contents of the Provisioning Directory

Table 2-4 shows the contents of the repository_name/provisioning directory.

2.5.4 Add largepages Option for all jvms/clusters

If your environment has large pages, you can update fusionapps_start_params.properties file by appending -XlargePages:exitOnFailure=true to the operating system entry for your platform. Complete these steps to add support for Java Virtual Machine (JVM) large pages:

1. After you have created a provisioning repository, open provisioning/provisioning-plan/fusionapps_start_params.properties.

2. Append the JVM argument to the appropriate entry:

   • fusion.default.Linux-x86_64.memoryargs=-Xms512m -Xmx2048m -Xgc:genpar

   • fusion.default.SunOS-sparc.memoryargs=-Xms512m -Xmx2048m -XX:PermSize=256m -XX:MaxPermSize=512m -XX:+UseParallelGC

   • fusion.default.AIX-powerpc.memoryargs=-Xms512m -Xmx2048m -XX:PermSize=256m -XX:MaxPermSize=512m -Xgcpolicdy:optavgpause

   • fusion.default.Windows_NT.memoryargs=-Xms512m -Xmx2048m -Xgc:genpar

3. Run provisioning as usual.

2.7.1 Run the Provisioning Deinstaller

To start the deinstaller, navigate to the (UNIX) PROV_FRMWK_HOME/oui/bin or (Windows) PROV_FRMWK_HOME\oui\bin. and start the deinstaller with this command:

(UNIX)

./runInstaller.sh -deinstall

(Windows)

setup.exe -deinstall

On Windows operating systems, you can also start the deinstaller from the Start menu by selecting Programs>Oracle Fusion Applications Provisioning 11g-Home1>Uninstall.

2.7.2 Deinstaller Screens and Instructions

Table 2-5 contains instructions for deinstalling the provisioning framework. If you need additional help with any of the interview screens, refer to Appendix A, "Provisioning Framework Screens" or click Help on any interview screen.