After you procure the required hardware for the enterprise deployment, it is important to ensure that each host computer meets the minimum system requirements.

You can review the typical Linux operating system settings for an enterprise deployment in this section.

• Setting Linux Kernel Parameters
  
• Setting the Open File Limit and Number of Processes Settings on UNIX Systems
  
• Verifying IP Addresses and Host Names in DNS or Hosts File
  

The users and groups to be defined on each of the computers that host the enterprise deployment are listed in this section.

It is recommended to enable Unicode support in your operating system so as to allow processing of characters in Unicode.

You should create the groups and users either locally or in your NIS or LDAP server. This user is the Oracle software owner.

groupadd groupname

groupadd -g 500 oinstall
groupadd -g 501 dba

useradd -g primary group -G optional groups -u userid username

useradd -g oinstall -G dba -u 500 oracle

All servers in the deployment must have the same time. The best way to achieve this is to use an NTP server.

1. Determine the name of the NTP servers you wish to use. For security reasons, ensure that these are inside your organization.
2. Log into the host as the root user.
3. Edit the file /etc/chrony.conf to include a list of the time servers. After editing, the file appears as follows:

   server ntphost1.example.com
   server ntphost2.example.com

4. Use the following systemctl command to check the status the Chrony daemon, chronyd:

   systemctl status chronyd

5. Use the following systemctl command to start or restart chronyd:

   systemctl restart chronyd

6. Run the following chronyc -n tracking command to check chrony tracking:

   chronyc -n tracking

7. Ensure the time is set correctly using the date command.
8. To ensure that the server always uses the NTP server to synchronize the time, set the client to start on reboot by using the following command:

   systemctl enable chronyd

1. Login to the host as root.
2. Edit the /etc/idmapd.conf configuration file:

   vi /etc/idmapd.conf

   Set the domain value, as in the following example:

   Domain = example.com
   

3. Restart the rpcidmapd service:

   service rpcidmapd restart

4. Update the /etc/yp.conf configuration file, and set the correct domain value, as in the following example:

   vi /etc/yp.conf

   Add the following line:

   domain example.com server NIS_Server_hostname_or_IP

   Where example.com is the example domain and NIS_Server_hostname_or_IP is the host name or IP address of the NIS host. You must replace these sample values with values appropriate for your environment.

5. Set NIS domain name on the command line:

   domainname NIS_DOMAIN_NAME

   For example:

   domainname nisdomain.example.com

6. Edit the /etc/nsswitch.conf configuration file:

   vi /etc/nsswitch.conf

   Add nis to each of the following entries:

   Note:

   The first value may be compat or files depending on your OS and enterprise requirements.

   passwd:     files nis
    shadow:     files nis
    group:      files nis
    automount:  files nis nisplus
    aliases:    files nis nisplus
   

7. Restart the rpcidmapd service:

   service rpcidmapd restart

8. Restart the ypbind service by running the following command:

   service ypbind restart

9. Check the yp service by running this command:

   ypwhich

10. Verify if you can access Oracle user accounts:

    ypcat passwd

11. Add ypbind to your boot sequence, so that it starts automatically after rebooting.

    chkconfig ypbind on

To prepare for the enterprise deployment, you must enable the virtual IP (VIP) address required by the WebLogic Administration Server in the node where it will run by default.

1. Determine the CIDR notation of the netmask. Each Netmask has a CIDR notation. For example, 255.255.240.0 has a CIDR of 20.
   If the netmask you are adding is the same as the interface, the fastest way to determine this is to examine the existing IP address that are assigned to the network card. You can do this by using the following command:

   ip addr show dev eth0

   Sample output:

   2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
   link/ether 00:21:f6:03:85:9f brd ff:ff:ff:ff:ff:ff
   int 192.168.20.1/20 brd 10.248.11.255 scope global eth0

   In this example, the CIDR value is the value after the forward slash (/), which is, 20. If you are unsure of the CIDR value, contact your network administrator.
2. Configure the additional IP address on the appropriate network interface card with an appropriately suffixed label using the following command:

   ip addr add VIP/CIDR dev nic# label nic#:n

   Note:

   For each VIP that you need to add, increment the :n suffix starting with :1

   Example: For VIP IP of 192.168.20.3, netmask: 255.255.240.0 (CIDR: 20), and the eth0 NIC:

   ip addr add 192.168.20.3/20 dev eth0 label eth0:1

3. For each of the virtual IP addresses that you define, update the ARP caches by using the following command:

   arping -b -A -c 3 -I eth0 192.168.20.3