This chapter describes how to prepare the servers for an enterprise deployment.
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 optional fashion. Specifically, you must ensure that:
The compute nodes are running a Linux 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.
Note:
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 minimum Open File Limit is 4096.
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.
C shell:
limit descriptors
Bash:
ulimit -n
To change the shell limits, login as root and edit the /etc/security/limits.conf file.
Verify that the following values, at a minimum, are met:
* soft nofile 4096 * hard nofile 65536 * soft nproc 2047 * hard nproc 16384
After editing the file, reboot the compute node.
By default huge pages are enabled in Exalogic compute nodes, verify the existing allocation by running.
grep Huge /proc/meminfo
Set the recommended Huge Page allocation to 25000.
To set the Huge Page allocation, run the following command as root in the compute node:
# echo 25000 > /proc/sys/vm/nr_hugepages
Before you begin the installation of the Oracle software, ensure that all your local /ect/hosts file is formatted like the following:
### Compute Node Private Interface details (IPoIB) 192.168.10.1 webhost1-priv.mycompany.com webhost1-priv 192.168.10.2 webhost2-priv.mycompany.com webhost2-priv 192.168.10.3 soahost1-priv.mycompany.com soahost1-priv 192.168.10.6 soahost2-priv.mycompany.com soahost2-priv ### SOA EDG external VIP (EoIB) 10.242.6.239 otdadmin.mycompany.com otdadmin 10.242.6.240 adminvhn.mycompany.com adminvhn 10.242.6.245 webhost1VHN1.mycompany.com webhost1VHN1 10.242.6.246 webhost2VHN1.mycompany.com webhost2VHN1 10.242.6.241 soahost1VHN1.mycompany.com soahost1VHN1 10.242.6.243 soahost1VHN2.mycompany.com soahost1VHN2 10.242.6.242 soahost2VHN1.mycompany.com soahost2VHN1 10.242.6.244 soahost2VHN2.mycompany.com soahost2VHN2 ### SOA EDG private VIP (IPoIB) 192.168.30.11 webhost1-priv-V1.mycompany.com webhost1-priv-V1 192.168.30.21 webhost2-priv-V1.mycompany.com webhost2-priv-V1 192.168.20.11 soahost1-priv-V1.mycompany.com soahost1-priv-V1 192.168.20.12 soahost1-priv-V2.mycompany.com soahost1-priv-V2. 192.168.20.21 soahost2-priv-V1.mycompany.com soahost2-priv-V1 192.168.20.22 soahost2-priv-V2.mycompany.com soahost2-priv-V2
Note:
If soainternal.mycompany.com and osbinternal.mycompany.com have DNS entries, you do not need to add to the /etc/hosts.
Oracle SOA uses Quartz to maintain its jobs and schedules in the database. Synchronize the system clocks for the SOA WebLogic cluster to enable proper functioning of jobs and adapters.
You can use the NTP service to keep clocks in sync. Refer to your network administrator for the appropriate NTP server configuration.
Your operating system configuration can influence the behavior of characters supported by Oracle Fusion Middleware products.
Oracle highly recommends that you enable Unicode support by setting the LANG and LC_ALL environment variables to a locale with the UTF-8 character set. This enables processing of any character in Unicode. Oracle SOA Suite technologies, for example, are based on Unicode.
Groups
You must create the following groups on each node.
oinstall
dba
Users
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 dba group.
Notes:
The group oinstall must have write privileges to all the file systems on shared and private 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.
The user and group should exists at the NIS server due to the NFSv4 mount requirement.
Define storage locations on the Sun ZFS Storage 7320 appliance for WEBHOST1 and WEBHOST2.
Note:
This section is based on the assumption that you have set up NFS V4 properly for the corresponding permissions and mounts to work properly. See Configuring NFS Version 4 (NFSv4) on Exalogic in the Oracle Fusion Middleware Exalogic Machine Owner's Guide for more information.
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 /u02/private/oracle/products mkdir -p /u02/private/oracle/config
Mount the shares:
mount -t nfs4 -o rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp zfsHost-priv:/export/soaedg/webhost1products /u02/private/oracle/products mount -t nfs4 zfsHost-priv:/export/soaedg/webhost1config /u02/private/oracle/config
Log in to WEBHOST2 and create the following directories as the root user.
sudo root mkdir -p /u02/private/oracle/products mkdir -p /u02/private/oracle/config
Change the ownership of the mount points on WEBHOST1 and WEBHOST2 using the following Commands:
chown oracle:oinstall /u02/private/oracle/products chown oracle:oinstall /u02/private/oracle/config
Mount the shares:
mount -t nfs4 -o rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp zfsHost-priv:/export/soaedg/webhost2products /u02/private/oracle/products mount -t nfs4 zfsHost-priv:/export/soaedg/webhost2config /u02/private/oracle/config
You can now use these mount points as you install and configure your Oracle Traffic Director software in the directories.
Validating the Shared Storage Configuration
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.
For example:
$ cd newly mounted directory
$ touch testfile
Verify that the owner and permissions are correct:
$ ls -l testfile
Then remove the file:
$ rm testfile
Define storage locations on the Sun ZFS Storage 7320 appliance for WEBHOST1 and WEBHOST2.
To define storage locations:
Log in to SOAHOST1 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/config
Mount the shares:
mount -t nfs4 -o rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp zfsHost-priv:/export/soaedg/products /u01/oracle/products mount -t nfs4 -o rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp zfsHost-priv:/export/soaedg/config /u01/oracle/config mount -t nfs4 zfsHost-priv:/export/soaedg/soahost1config /u02/private/oracle/config
Log in to SOAHOST2 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/config
Change the ownership of the mount points using the following commands:
chown oracle:oinstall /u01/oracle/products chown oracle:oinstall /u01/oracle/config chown oracle:oinstall /u02/private/oracle/config
Mount the shares:
mount -t nfs4 -o rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp zfsHost-priv:/export/soaedg/products /u01/oracle/products mount -t nfs4 -o rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp zfsHost-priv:/export/soaedg/config /u01/oracle/products mount -t nfs4 -o rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp zfsHost-priv:/export/soaedg/soahost2config /u02/private/oracle/config
You can now use these mount points as you install and configure your SOA/OSB software in the directories.
Validating the Shared Storage Configuration
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.
For example:
$ cd newly mounted directory
$ touch testfile
Verify that the owner and permissions are correct:
$ ls -l testfile
Then remove the file:
$ rm testfile