Oracle® Fusion Middleware Identity Management Provisioning Guide (Oracle Fusion Applications Edition) 11g Release 7 (11.1.7) Part Number E41444-02 |
|
|
PDF · Mobi · ePub |
This chapter describes tasks you must perform before running the Identity Management Provisioning Wizard. Many of these tasks are platform-specific.
This chapter contains the following sections:
When planning the 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 Identity Management provisioning. See Section 7.2.2, "Null Error Occurs When WebLogic Patches Are Applied."
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.
Table 3-1 UNIX Kernel Parameters
Parameter | Value |
---|---|
kernel.sem |
256 32000 100 142 |
kernel.shmmax |
4294967295 |
To set these parameters:
Log in as root
and add or amend the entries in the file /etc/sysctl.conf
.
Save the file.
Activate the changes by issuing the command:
/sbin/sysctl -p
You must set the following AIX Kernel parameters before starting Identity Management Provisioning:
no -o tcp_recvspace=262144 no -o tcp_sendspace=262144 no -o udp_recvspace=262144 no -o udp_sendspace=262144 no -o rfc1323=1 no -o sb_max=4194304 /usr/sbin/no -o tcp_timewait=1
On all UNIX operating systems, the minimum Open File Limit should be 150000.
Note:
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.
C shell:
limit descriptors
Bash:
ulimit -n
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, also edit the /etc/security/limits.d/90-nproc.conf file, and ensure it has the following line:
* soft nproc 16384
After editing the files, reboot the machine.
See the Oracle Fusion Middleware System Requirements and Specifications for the latest suggested value.
Proceed as follows:
Create a domain\user
that is part of the Administrators group.
Log in as the user that you created.
Run secpol.msc
(security policy). To do this, click Start > Run, type secpol.msc
, and press Enter. Add the domain\user
that you created to Log on as service under the Local Policies, User Rights Assignment option.
Reboot the machine.
Ensure that IPV4 is enabled and IPV6 is disabled, as follows:
To enable the IPV4 address, execute the command:
netsh interface ipv4 install
To disable the IPV6 address, execute the command:
netsh interface ipv6 uninstall
A method for completely disabling IPV6 on a Windows host is documented at:
http://support.microsoft.com/kb/929852
To list all the IP addresses for verification, execute the command:
netsh interface ipv4 show ipaddresses netsh interface ipv6 show ipaddresses
The openssl
command is not available by default on Microsoft Windows.
You must install OpenSSL on the Windows machine. See: http://www.openssl.org
The directory containing the binary openssl
must be in the PATH
environment variable.
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 LANG
and 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.