|Oracle® Exalogic Elastic Cloud Enterprise Deployment Guide for Oracle Identity Management
Release EL X2-2 and EL X3-2
Part Number E35832-01
|PDF · Mobi · ePub|
It contains the following sections:
Before you deploy Oracle Fusion Middleware on new hardware, you must set up the compute nodes you plan to use so that the Oracle Software can work in an optimum fashion. Specifically, you must ensure that:
The compute nodes are running a certified operating system with the required software patches installed.
You have configured the UNIX Kernel correctly.
You have created Users and Groups to own the Oracle software.
The settings described in this chapter are only a guide. After using your Oracle software, you should use operating system utilities to tune the configuration to ensure that you are maximizing the potential of your servers.
Before starting your operating provisioning you must install a certified operating system.
Be sure to verify you have obtained all required patches. For more info, see Section 2.5.3, "Applying Patches and Workarounds."
This section includes the following topics:
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 Table 5-1 are the current UNIX recommendations. For the latest recommendations for UNIX and other operating systems, see the Oracle Fusion Middleware System Requirements and Specifications at the following URL:
256 32000 100 142
To set these parameters:
Log in as
root and add or amend the entries in the file
Save the file.
Activate the changes by issuing the command:
On all UNIX operating systems, the minimum Open File Limit should be 4096.
The following examples are for Linux operating systems. Consult your operating system documentation to determine the commands to be used on your system.
You can see how many files are open with the following command:
/usr/sbin/lsof | wc -l
To check your open file limits, use the commands below.
To change the shell limits, login as
root and edit the
Add the following lines:
* soft nofile 4096 * hard nofile 65536 * soft nproc 2047 * hard nproc 16384
After editing the file, reboot the machine.
Before you begin the installation of the Oracle software, ensure that all your local
/ect/hosts file is formatted like the following:
oudinternal.mycompany.com VIP address idminternal.mycompany.com VIP address ADMINVHN VIP address SOAHOST1VHN VIP address SOAHOST2VHN VIP address OIMHOST1VHN VIP address OIMHOST2VHN VIP address
idminternal.mycompany.com have DNS entries, you do not need to add to the /etc/hosts.
Your operating system configuration can influence the behavior of characters supported by Oracle Fusion Middleware products.
On UNIX operating systems, Oracle highly recommends that you enable Unicode support by setting the
LC_ALL environment variables to a locale with the UTF-8 character set. This enables the operating system to process any character in Unicode. Oracle SOA Suite technologies, for example, are based on Unicode.
If the operating system is configured to use a non-UTF-8 encoding, Oracle SOA Suite components may function in an unexpected way. For example, a non-ASCII file name might make the file inaccessible and cause an error. Oracle does not support problems caused by operating system constraints.
You must create the following groups on each node.
You must create the following users on each node.
oracle–The group that owns the Oracle software. You may use a different name. The primary group for this account must be
oinstall. The account must also be in the
oinstall must have write privileges to all the file systems on shared and local storage that are used by the Oracle software.
Each group must have the same Group ID on every node.
Each user must have the same User ID on every node.
This procedure ensures that the user account that was used to configure Oracle Traffic Director has access to the Storage Appliance.
To ensure user account has the correct permissions:
Log in to the ZFS server as root.
Run the following commands:
ZFS-SharedStorage > shares ZFS-SharedStorage > select <share-used-for-OTD> ZFS-SharedStorage > get sharenfs ZFS-SharedStorage > set sharenfs="sec=sys,rw=@bond0-ip-address-of-OTD-compute-node1,root=@bond0-ip-address-of-OTD-compute-node2" ZFS-SharedStorage > commit
Define storage locations on the Sun ZFS Storage 7320 appliance for WEBHOST1 and WEBHOST2.
To define storage locations:
Log in to WEBHOST1 and mount the following shares as the root user.
These directories are used as mount points for the shared and private directories required by the enterprise topology:
mkdir -p /u01/oracle/products mkdir -p /u01/oracle/config mkdir -p /u02/private/oracle/products mkdir -p /u02/private/oracle/config
Mount the shares:
mount -t nfs4 zfsHost:/export/IDM/products /u01/oracle/products mount -t nfs4 zfsHost:/export/IDM/config /u01/oracle/products mount -t nfs4 zfsHost:/export/IDM/WEBHOST1/products /u02/private/oracle/products mount -t nfs4 zfsHost:/export/IDM/WEBHOST1/config /u02/private/oracle/config
Log in to WEBHOST2 and create the following directories as the root user.
sudo root mkdir -p /u01/oracle/products mkdir -p /u01/oracle/config mkdir -p /u02/private/oracle/products mkdir -p /u02/private/oracle/config
Mount the shares:
mount -t nfs4 zfsHost:/export/IDM/products /u01/oracle/products mount -t nfs4 zfsHost:/export/IDM/config /u01/oracle/products mount -t nfs4 zfsHost:/export/IDM/WEBHOST2/products /u02/private/oracle/products mount -t nfs4 zfsHost:/export/IDM/WEBHOST2/config /u02/private/oracle/config
You can now use these mount points as you install and configure your Oracle Traffic Director software in the directories.
Ensure that you can read and write files to the newly mounted directories by creating a test file in the shared storage location you just configured.
$ cd newly mounted directory $ touch testfile
Verify that the owner and permissions are correct:
$ ls -l testfile
Then remove the file:
$ rm testfile