2 Prerequisites

This chapter provides software requirements, as well as environmental and third-party software prerequisites. You must read this chapter and meet the prerequisites before proceeding with the upgrade.

Complete the following basic steps to prepare your network and host computers for deployment:

Ensure you are running Oracle WebCenter Interaction 10.3 or 10.3.0.1.

You can upgrade only from versions 10.3 or 10.3.0.1. If you run an older version, you must first upgrade to 10.3 before following the instructions in this guide. For instructions on upgrading to 10.3, see documentation available in the Oracle WebCenter Interaction 10g Release 3 (10.3) documentation set.
Download the most up-to-date documentation from the Oracle Technology Network in the Oracle WebCenter Interaction 10g Release 4 (10.3.3.0.0) documentation set.
Read the product release notes for information on compatibility issues, known problems, and workarounds that might affect how you proceed with your deployment.
Provision host computers for your deployment and install prerequisite software. For details, see Software Requirements.
Back up configuration.xml. The installer will merge new settings into this file, and might, in the process, overwrite customizations you have made.
Ensure that you have the users and groups required to install Oracle WebCenter Interaction. For details, see User and Group Requirements.
Grant user and group access rights to Oracle Inventory directories. For details, see Granting User and Group Access Rights to Oracle Inventory Directories.
If you are installing on AIX, adjust your file size limit and temp directory to accommodate the Oracle WebCenter Interaction installer. For details, see Adjusting AIX File Size Limit and Temp Directory.
If you are using Oracle Database in your deployment, set the Oracle environment variables. For details, see Setting Oracle Environment Variables.
If you are using Oracle WebLogic Server in your deployment, disable Basic Authentication. For details, see Preparing Oracle WebLogic Server for Oracle WebCenter Interaction.
If you are installing Oracle WebCenter Interaction Content Service for Documentum for the first time, you must first install the Documentum DFC Runtime Environment. For details, see Configuring the Documentum DFC Runtime Environment.
If you are upgrading Oracle WebCenter Interaction Content Service for Documentum:
1. If you have customized the config.xml and dql.xml configuration files, copy these files to a temporary location outside of the installation target path so that they are not overwritten by the installer.
2. Uninstall the previous version of Oracle WebCenter Interaction Content Service for Documentum.
Caution:

If Professional Consulting Services (PCS) has made specialized customizations to the Oracle WebCenter Interaction Content Service for Documentum, do not upgrade on your own. Your customizations might not be included in the new version. Contact PCS to perform the upgrade.
If you are upgrading Oracle WebCenter Interaction Identity Service for LDAP, uninstall the previous version of Oracle WebCenter Interaction Identity Service for LDAP.

Software Requirements

For the latest information on supported operating systems, application servers, databases, and browsers, see the Oracle WebCenter Interaction page at http://www.oracle.com/technetwork/middleware/webcenter-interaction/index.html, open the Oracle WebCenter Interaction 10g Release 4 Certification Matrix spreadsheet, and refer to the WebCenter Interaction 10.3.3 worksheet.

For more information on recommended configurations based on the size of your implementation, see the section about provisioning computers in the Oracle Fusion Middleware Deployment Planning Guide for Oracle WebCenter Interaction.

User and Group Requirements

This section describes the user and group requirements for Oracle WebCenter products on UNIX and Linux platforms.

We recommend that you create a user and group that will own the portal installation. The following table lists recommended values for a user, a group, and Oracle WebCenter directories.

Pre-install Setting	Standard Value	Notes
ALI Group Name	ali	Local group with a fixed ID
ALI User	ali	Local group with a fixed ID
PT_HOME	/opt/oracle/middleware/wci	Owned by ALI user and group

Important Information

The same values for these users, groups, and directories should be used across all computers hosting portal components. Local users and groups with fixed IDs are recommended. Secure deployments should avoid NIS users for computer security. Using the same local user and group for all Oracle WebCenter services allows an administrator to lock down host computers and audit activity.

For convenience, preinstall.sh, a script to create users, groups and directories, is provided with the distribution. For details on running the pre-install script, see Running the UNIX Pre-Install Script.

You must also grant this user and group access rights to the Oracle Inventory directories. For details, see Granting User and Group Access Rights to Oracle Inventory Directories.

Running the UNIX Pre-Install Script

This section describes how to use the pre-install script to create users and groups for Oracle WebCenter Interaction on UNIX and Linux.

The preinstall.sh script creates a user, a group and directories with permissions appropriate for a Oracle WebCenter Interaction installation on UNIX. The script is interactive, asking you a series of questions about the values to be configured.

Review the preinstall.sh script.
Log in as root to become superuser.
Make a temporary directory for the files and allow all users to access these files by typing:

# mkdir /tmp/plumtree

# chmod 777 /tmp/plumtree
Copy the preinstall file by typing:

# cd /tmp/plumtree

# cp /install_dir/scripts/preinstall.sh .
Run the preinstall.sh script by typing:

# ./preinstall.sh

Be sure to carefully review any output from the script.
Change the of the newly created user by typing:

# passwd ali
Enter the login.
Log out as superuser.

Granting User and Group Access Rights to Oracle Inventory Directories

Oracle Inventory includes files that provide the Oracle Universal Installer with the locations of the ORACLE_HOME directories on a particular computer. For Oracle Inventory to function properly, the user that installs Oracle WebCenter Interaction must have access rights to the directories that contain Oracle Inventory's files. You can set the user and group access rights for these directories by running the ouais.sh shell script.

Log in to the remote server host computer as the root user.
Copy the ouais.sh script to the computer onto which you will be installing Oracle WebCenter Interaction.

This script is located in the same location as the Oracle WebCenter Interaction installer file.
Change the current directory (cd) to be the directory to which you copied the ouais.sh script.
Run the ouais.sh shell script.

As arguments to the script, specify the ALI user and group you created that will run the Oracle WebCenter Interaction installer. For details, see User and Group Requirements. For example, you would use the following command to run the ouais.sh script from the root shell:
```
./ouais.sh -u <oracleuser> -g <oraclegroup>
```
The ouais.sh script creates the Oracle Inventory directory if it did not exist before you ran the script. Additionally, the script grants user and group ownership to the directories that contain the files that are used by Oracle Inventory.

Adjusting AIX File Size Limit and Temp Directory

If you are installing on AIX, adjust your file size limit and temp directory to accommodate the Oracle WebCenter Interaction installer.

View your local default values, using the following command:
```
$ulimit -a
```
By default, AIX limits the maximum size of files to 1GB. The default value is set to 2097151 in the /etc/security/limits file, but the value is in 512byte blocks, so it might look like the limit is 2GB when it is really only 1GB.
If your limit is less than 2GB (approximately 4194304 in 512btye blocks), adjust the limit as root (only root can adjust limits upward):
```
$ulimit -f 4194304
```
For the change to take effect, you must log out and log back in.
The default temp location (/tmp) will not accommodate the space needed for the Oracle WebCenter Interaction installer extraction process, so you must define a different location for the extracted files by setting the following variable, pointing to a new temp directory:
```
export IATEMPDIR="new_temp_directory"
```

Setting Oracle Environment Variables

This table describes the Oracle Environment variables that must be set when installing Oracle WebCenter products to instances of Oracle9i or Oracle Database 10g.

Environment Variable	Description	Example Values
ORACLE_BASE	Must be set to the root directory of your Oracle installation.	/opt/oracle
ORACLE_HOME	Must be set to the home directory of your Oracle installation.	/opt/oracle/ora92
ORACLE_SID	Must be set to the system ID (SID) of the portal database instance.	(Oracle9i) PLUM (Oracle Database 11g) PLUM11 Note: PLUM or PLUM10 are expected by the SQL scripts. If you set your SID to a value other than these example values, you must edit the SQL scripts to reflect this change.

Environment Variable

Description

Example Values

ORACLE_BASE

Must be set to the root directory of your Oracle installation.

/opt/oracle

ORACLE_HOME

Must be set to the home directory of your Oracle installation.

/opt/oracle/ora92

ORACLE_SID

Must be set to the system ID (SID) of the portal database instance.

(Oracle9i) PLUM
(Oracle Database 11g) PLUM11

Note: PLUM or PLUM10 are expected by the SQL scripts. If you set your SID to a value other than these example values, you must edit the SQL scripts to reflect this change.

Preparing Oracle WebLogic Server for Oracle WebCenter Interaction

This section describes how to configure Oracle WebLogic Server for use with the Oracle WebCenter Interaction portal application.

WebLogic Basic Authentication must be disabled for the Oracle WebCenter Interaction portal application on Oracle WebLogic Server. To do this, in the Oracle WebLogic Server config.xml for the Oracle WebCenter Interaction portal, set <enforce-valid-basic-auth-credentials> to false.

Disable WebLogic Basic Authentication for the Oracle WebCenter Interaction portal application.
1. Open WebLogic_home/user_projects/domains/domain/config/config.xml in a text editor, where WebLogic_home is your Oracle WebLogic installation directory.
2. In the <security-configuration> section, set <enforce-valid-basic-auth-credentials> to false.
  
  If <enforce-valid-basic-auth-credentials> is already defined in this section, change its value to false.
  
  If <enforce-valid-basic-auth-credentials> does not exist in this section, add the following line before the </security-configuration> line as shown below:
```
<security-configuration>
...
    <enforce-valid-basic-auth-credentials>
    false
    </enforce-valid-basic-auth-credentials>
</security-configuration>
```
On Oracle Enterprise Linux, AIX, HP-UX, and Solaris, verify that your Oracle WebLogic Server domain is configured to use a valid 64–bit Java SDK.
On Oracle Enterprise Linux, AIX, HP-UX, and Solaris, add -d64 to your domain's JAVA_OPTIONS.

To do this, edit the setDomainEnv.sh script for your domain. Find where JAVA_OPTIONS is set, near the end of the file, and add the -d64 flag.

For example:
```
#JAVA_OPTIONS="${JAVA_OPTIONS}"
JAVA_OPTIONS="-d64 ${JAVA_OPTIONS}"
export JAVA_OPTIONS
```
Increase the JVM's MaxPermSize.

A MaxPermSize of 256m is recommended. If MaxPermSize is set too low, you will see java.lang.OutOfMemoryError: PermGen space when attempting to start the portal.To increase MaxPermSize, edit the setDomainEnv.sh script for your domain. Find where MaxPermSize is being set for your JAVA_VENDOR, and set it to 256m.

For example:
```
if [ "${JAVA_VENDOR}" = "HP" ] ; then
    #MEM_ARGS="${MEM_ARGS} -XX:MaxPermSize=128m"
    MEM_ARGS="${MEM_ARGS} -XX:MaxPermSize=256m"
    export MEM_ARGS
fi
```

Configuring the Documentum DFC Runtime Environment

If you are installing Oracle WebCenter Interaction Content Service for Documentum, you must first install the Documentum DFC Runtime Environment. For details on installation of Documentum products, refer to Documentum documentation.

After you install the Documentum Desktop Client on the Remote Server host computer, configure the dmcl.ini file for the client as follows:

Set the host to the docbroker that will be used by all users of this Remote Server. To allow more than one docbroker, you must install a Remote Server for each docbroker.
```
[DOCBROKER_PRIMARY]
host = YOURDOCBROKER
```
Set your max session count to a value comfortably above the number of sessions you expect to be opened by the Oracle WebCenter Interaction Content Service for Documentum content Web services (1 connection per user per content Web service) but comfortably within this computer's performance limitations and well below the maximum number of concurrent sessions allowed by your Documentum server. For more information, refer to Advanced Configuration: Tuning Documentum Server.
```
[DMAPI_CONFIGURATION]
cache_query = T
connect_pooling_enabled=T 
connect_recycle_interval=100 
max_session_count=
Docbroker_search_order=RANDOM
```

Additional Step for UNIX and Linux Hosts

Ensure you have set environment variables for any user who uses this DFC instance by adding them to the Java application server startup file:

DOCUMENTUM: refer to the DFC Installation Guide.
DOCUMENT_SHARED: refer to the DFC Installation Guide.

CLASSPATH: include full path to dfc.jar, dctm.jar, and $DOCUMENTUM_SHARED/config. For example:

export CLASSPATH=$CLASSPATH:/user/DFC/dfc.jar:$DOCUMENTUM_SHARED/dctm.jar:$DOCUMENTUM_SHARED/config

LD_LIBRARY_PATH (Solaris and Linux): include the full path to the dfc directory under the Documentum DFC program root. Add the full path to the dfc directory to LD_LIBRARY_PATH. For example
```
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/documentum_dfc_program_root/dfc
```
LIBPATH (AIX): include the full path to the dfc directory under the Documentum DFC program root. Add the full path to the dfc directory to LIBPATH. For example:
```
export LIBPATH=$LIBPATH:/documentum_dfc_program_root/dfc
```
PATH: enter the full path to the installation directory.
DMCL_CONFIG: enter the path to a dmcl.ini file. For example:
```
export DMCL_CONFIG=/user/DFC/dmcl.ini
```
Note:

We strongly recommend that you set the DMCL_CONFIG system variable on the Remote Server to ensure that the Oracle WebCenter Interaction Content Service for Documentum can communicate with the Documentum server. The DMCL_CONFIG value should be the path to the dmcl.ini file. See the installation guide for Documentum DFC Runtime Environment for additional details.