Oracle Fusion Applications 11.1.2.9 Installation Part 2

Oracle Fusion Applications 11.1.2.9 Installation Part 2 Preparing for an Installation

2.1 Mounting the Shared Storage

Mount the shared storage on each server according to the information defined in the Oracle Fusion Applications Installation Workbook - Storage tab -> Shared Storage table.

Ensure that the file system is mounted as read-write.

If you are using different shared storage for Oracle Identity Management and Oracle Fusion Applications, follow these steps to mount each shared drive:

■ The Oracle Identity Management shared storage should be mounted on the servers running Oracle Identity Management components (see the Topology tab in the Oracle Fusion Applications Installation Workbook).

■ The Oracle Fusion Applications shared storage should be mounted on the servers running Oracle Fusion Applications components (see the Topology tab in the Oracle Fusion Applications Installation Workbook).

Verifying the /etc/oraInst.loc File

2.2 Preparing Servers

Preparing the Oracle Identity Management Server (IDM01)

Ensure Software Install Location is 45 Characters or Fewer

When planning the Oracle Identity Management deployment, ensure that the Software Installation Location directory path is 45 characters or fewer in length. You specify this directory on the Installation and Configuration page when you create the provisioning profile. A longer pathname can cause errors during Oracle Identity Management provisioning.

Configure Kernel Parameters

UNIX: The kernel parameter and shell limit values shown below are recommended values only. For production database systems, Oracle recommends that you tune these values to optimize the performance of the system. See your operating system documentation for more information about tuning kernel parameters. Kernel parameters must be set to a minimum of those below on all nodes in the cluster. The values in the following table are the current Linux recommendations. For more information, refer to Oracle Fusion Middleware System Requirements and Specifications. If you are deploying a database onto the host, you might need to modify additional kernel parameters. Refer to the 11g Release 2 Oracle Grid Infrastructure Installation Guide for your platform.

Linux:

To set these parameters:

1. Log in as root and add or amend the entries in /etc/sysctl.conf.

2. Save the file.

3. Activate the changes by issuing the command:

/sbin/sysctl –p

Set the Open File Limit

On all UNIX operating systems, the minimum Open File Limit should be 150000.

To change the shell limits, login as root and edit the /etc/security/limits.conf file.

Add the following lines:

* soft nofile 150000

* hard nofile 150000

* soft nproc 16384

* hard nproc 16384

If you are installing on Oracle Linux Server release 6, edit /etc/security/limits.d/90-nproc.conf to make sure it has the following line:

* soft nproc 16384

After editing the file, reboot the machine.

Synchronize Time Between Nodes

Synchronize the time on the individual Oracle Internet Directory nodes using Greenwich Mean Time so that there is a discrepancy of no more than 250 seconds between them.

Preparing the Oracle Fusion Applications Server(FA01)

Increase the Open Files Limit

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

For Linux x86-64:

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

■ FUSION_USER_ACCOUNT soft nofile 327679

■ FUSION_USER_ACCOUNT hard nofile 327679

Edit /etc/ssh/sshd_config as follows:

1. Set UsePAM to Yes.

2. Restart sshd.

3. Logout (or reboot) and log in again.

Increase the maximum open files limit.

Edit /proc/sys/fs/file-max and set it to 6553600. The change becomes effective immediately but does not persist after a reboot. To make the change permanent edit /etc/sysctl.conf and set fs.file-max = 6553600. This change will not be effective until the sysctl command is run or the server is rebooted.

Increase the Max User Processes

For all platforms, typically, you would have max user processes set to 16384:

$ulimit -u

16384

Increase the maximum user process to 16384 or higher.

Linux:

To check the max user processes:

$ulimit -u

16384

To change the max user processes:

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

FUSION_USER_ACCOUNT soft nproc 16384

FUSION_USER_ACCOUNT hard nproc 16384

Preparing the Oracle Fusion Applications Server(DBNODE01)

Set the Kernel Parameter Value

Before you install the Oracle Database using the Provisioning Wizard, ensure that the

value of the kernel parameter shmmax on the database host is greater than the value of

the System Global Area (SGA) Memory.

The value of SGA Memory (sga_target) is 9 GB in the default Database Configuration

Assistant (DBCA) template for the Starter database. If you are running DBCA using

the production DBCA template packaged with Oracle Fusion Applications

Provisioning, the value of the SGA Memory is 18 GB. Ensure that shmmax > (shmall *

shmmni) > SGA Memory, where shmmax, shmall, shmmni are kernel parameters.

Linux:

For example, to retrieve the values of these kernel parameters, use the following

command:

user@host> /sbin/sysctl -a | grep shm

kernel.shmmni = 4096

kernel.shmall = 3145728

kernel.shmmax = 12884901888

To set the value of a kernel parameter:

user@host> /sbin/sysctl -w sys.kernel.shmmax=value

2.3 Create the hwrrepo directory

If you are provisioning the Oracle Fusion Human Capital Management (Oracle Fusion

HCM) application offerings, namely Workforce Development and Workforce

Deployment, and planning to use the Workforce Reputation Management feature, you

need to perform the following tasks after provisioning is complete:

1. Create a directory named /mnt/hwrrepo (Windows: C:\mnt\hwrrepo) for the

provisioning hosts.

2. Mount a shared disk as needed by the Workforce Reputation (HWR) application.

Windows: net share hwrrepo=C:\mnt\hwrrepo /unlimited

/GRANT:userdomain\username,FULL

3. Grant directory permission to the user/group who owns the Oracle Fusion

Applications WLS domain(s).This user can start or shut down the Oracle Fusion

Applications environment.

UNIX: Run this shell command as root and replace <user id>:<group id> with

appropriate user and group identifiers:

chown <user id>:<group id> /mnt/hwrrepo

Windows: icacls C:\mnt\hwrrepo /grant:r userdomain\username:(F)

4. Change read/write permission for the directory /mnt/hwrrepo to be globally

readable/writable.

UNIX: Run this shell command as root:

chmod 750 /mnt/hwrrepo

You will see a warning message in the provisioning log during the preverify phase

when you select the Workforce Development and Workforce Deployment offerings for

provisioning if the directory is not setup. The warning message is a reminder. You can

proceed with provisioning the environment and mount the shared disk after

provisioning is complete and before you start using the Workforce Reputation

application.

2.4 Edit Host Names (UNIX)

For UNIX platforms, confirm that the host names are correctly formatted in

/etc/hosts, for each host that is participating in provisioning. Review /etc/hosts for

each participating host and edit any host entries that do not meet the following

recommendations:

1. The format for each host entry should follow this format:

IP_address canonical_hostname [aliases]

The canonical_hostname should be the same as the fully qualified host name.

Errors can occur if a short version, or alias, of the host name is specified first in

/etc/hosts. The usage of aliases is optional and can be left empty. Examples of

correct and incorrect entries follow:

(Correct) 141.80.151.100 myMachine.company.com myMachine

(Incorrect) 141.80.151.100 myMachine myMachine.company.com

2.5 Verify Required Operating System Packages and Libraries

Oracle Fusion Applications require specific operating system packages and libraries in

the hosts where the software is installed.

For Database Host

1. Navigate to REPOSITORY_LOCATION/installer/database/Disk1.

2. Run the command:

UNIX: ./runInstaller -executePrereqs -silent

Windows: setup.exe -executePrereqs -silent -jreLoc REPOSITORY_

LOCATION\jdk6

3. Review the output located at:

oraInventory/logs/installAction<timestamp>.log. For example,

oraInventory/logs/installActionyyyy-mm-dd_hh-mm-ssPM.log.

Other Oracle Fusion Applications Hosts

1. Navigate to REPOSITORY_LOCATION/installer/<product>/Disk1, where

<product> represents:

■ atgpf

■ biappsshiphome

■ bishiphome

■ dbclient

■ ecm_bucket2

■ fusionapps

■ odi

■ soa

■ wc

■ webgate

■ webtier

Optionally, you can also include the following products:

■ bhd

■ gop

2. Run the command:

UNIX:

./runInstaller -sv -jreLoc REPOSITORY_LOCATION\jdk6

3. Review the output located at: oraInventory/logs/install<timestamp>.out. For

example, oraInventory/logs/installyyyy-mm-dd_hh-mm-ssAM.out.

4. Repeat Step 1 to Step 3 for all products listed in Step 1.

If you want to Install the following production you need to install true type fonts

Appears only if you have selected Oracle Sales, Oracle Marketing, or Oracle Financials offerings. Enter the directory where the TrueType fonts are installed. The location varies on different operating systems, but is typically found here:

How to install Microsoft TrueType Fonts in OEL 6.7

Download the Microsoft core fonts rpm package.

[root@fa01]# wget https://www.itzgeek.com/msttcore-fonts-2.0-3.noarch.rpm

Install rpm package.

[root@geeksite~/[# rpm -Uvh msttcore-fonts-2.0-3.noarch.rpm

Microsoft True Type core fonts successfully installed on OEL 6.7.

Continue: Oracle Fusion Applications 11.1.2.9 Installation Part 3