# Installation and Upgrade Guide

# Pre-Installation Procedures

This section describes the following pre-installation steps that ensure successful installation:

1. Download the most up-to-date documentation from http://www.oracle.com/technology/documentation/index.html.
2. Read the product release notes for information on compatibility issues, known problems, and workarounds that might affect how you proceed with your deployment. Release notes are located at the top-level directory of the product package.
3. Provision host computers for your deployment and install prerequisite software. For details, see Ensuring Component Version Compatibility.
4. Install the Documentum DFC Runtime Environment. For details, see Configuring the Documentum DFC Runtime Environment.
5. For installation on UNIX and Linux hosts, create the installation directory and the ALUI user and group. For details, see Setting Up User and Group Accounts (UNIX and Linux).

## Ensuring Component Version Compatibility

Note: | For the most up-to-date list of supported software for your deployment, refer to the Interoperability page in the AquaLogic User Interaction Support Center.

The following table summarizes hardware and software requirements for the components you deploy with this product.

Caution: | IPv6 is not supported. You should verify that IPv6 is not enabled prior to installing this product.
Table 2-1 Hardware and Software Requirements
Component | Requirement
--- | ---
Documentum CS Host Computer | Hardware 512 MB RAM 128 MB disk space Operating System AIX 5.3, on POWER3, POWER4, POWER5 Red Hat Enterprise Linux 4 Update 3, on x86 Microsoft Windows 2003 Server SP1 or R2, on x86 Solaris 8, 9, and 10, on SPARC SUSE Enterprise Linux 9, on x86
Documentum Content Server | Documentum Content Server 5.2.5, 5.3
Network | You must be able to configure communication between the Remote Server, the portal, and Documentum Content Server. If the Documentum Content Server is located on a computer outside of the portal and remote server domain, you must configure trust relations between domains.
Portal Software | AquaLogic Interaction 6.1
Client Browser | Firefox 1.0, 1.5, 2.0 Internet Explorer 6.0, 7.0 Netscape 7.2, 8.0 Safari 1.3, 2.0

## Configuring the Documentum DFC Runtime Environment

Before you install Documentum CS software on the Remote Server host computer, 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 Documentum CS content Web services (1 connection per user per content Web service) but comfortably within this machine'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 Documentum CS 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.

## Setting Up User and Group Accounts (UNIX and Linux)

If you are installing an AquaLogic User Interaction product on a UNIX or Linux host computer for the first time, set up an ALI user group and account on the Remote Server host.

For local authentication, perform the following steps on the Remote Server host; for network authentication, perform these steps in LDAP or NIS:

1. Verify there is sufficient disk space for the application to install.
2. Create the local ALI group (ALI_GROUP), the local ALI user (ALI_USER), and its home directory (PT_HOME).
3. Type `chown -R $PT_USER:$PT_GROUP $PT_HOME`.
4. Type `chmod -R 770 $PT_HOME`.
5. Log in to the host as root and type the following:

    mkdir -p /etc/plumtree
    chgrp $ALI_GROUP /etc/plumtree
    chmod -R 770 /etc/plumtree
    mkdir -p /tmp/plumtree
    chmod -R 777 /tmp/plumtree

6. If the file /etc/plumtree/ptreg.xml exists, type the following:

    chmod 660 /etc/plumtree/ptreg.xml
    chgrp $ALI_GROUP /etc/plumtree/ptreg.xml