Installation and Upgrade Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Completing 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 additional 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, seeHardware and Software Requirements.
  4. Set the PT_HOME environment variable. For details, see Setting the PT_HOME Environment Variable.
  5. Configure the Documentum DFC Runtime Environment. For details, see Configuring the Documentum DFC Runtime Environment.

 


Hardware and Software Requirements

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.
Component
Requirement
Remote Server Host Computer
  • Disk: 128 MB available
  • Memory: 512 MB RAM
  • Operating System: Microsoft Windows 2003 Server SP1
  • Application Server: BEA WebLogic 8.1 SP2, SP4, SP5, and 9.1
  • Documentum DFC Runtime Environment 5.2.5 SP2
Portal Software
  • AquaLogic Interaction 6.1
  • Plumtree Foundation 6.0.x
  • Plumtree Corporate Portal 5.0.x
Documentum Content Server
  • Documentum Content Server 5.1, 5.2
  • Documentum eContent Server 4.2
Network
  • You must be able to configure communication between the Documentum Portlets host computer, the portal, and Documentum Content Server.
  • If the Documentum Content Server is located on a computer outside of the portal and Documentum Portlets host computer domain, you must configure trust relations between domains.
Client Browser
  • Internet Explorer 5.x and 6.x
  • Netscape Navigator 4.08, 7.2, and 8.x (Windows)
  • Netscape Navigator 4.8 (UNIX)
  • Netscape Communicator 4.79
  • Firefox 1.0 and 1.5

 


Setting the PT_HOME System Variable for the Documentum Portlets Host Computer

If you are installing AquaLogic User Interaction products on the remote server the first time, set the PT_HOME system variable to enable communication among component products.

 


Setting the PT_HOME Environment Variable

Before proceeding with installation, you must set the PT_HOME environment variable. To set the PT_HOME environment variable:

  1. On the Desktop, right click My Computer and choose Properties.
  2. Click the Advanced tab.
  3. Click Environment Variables.
  4. In the System Variables group, click the New button.
  5. In the New System Variable dialog box, specify PT_HOME for Variable Name and C:\bea\alui for Variable Value.
  6. Click OK to close the New System Variable dialog box.
  7. Click OK to close the Environment Variables dialog box.
  8. Click OK to close the System Properties dialog box.
Note: We strongly recommend you set PT_HOME to C:\bea\alui. If you set this to a different location, be sure to specify your custom location instead of C:\bea\alui when you complete the installation and configuration steps provided in this guide.

 


Configuring the Documentum DFC Runtime Environment

This section describes how to configure the Documentum components to support integration with the portlet suite. To configure the Documentum DFC Runtime Environment:

  1. Install the DFC Runtime Environment as described in Documentum documentation.
  2. In the DFC Runtime Environment dmcl.ini configuration file (this file is usually located in the c:\documents and settings\<username>\windows folder), modify/add the DMAPI_CONFIGURATION section as follows:
  3. [DMAPI_CONFIGURATION]
    cache_queries=T
    connect_pooling_enabled=T
    client_locale=en
    connect_recycle_interval=100
    max_session_count=1000
  4. In the Documentum Content Server server.ini configuration file, set the concurrent_sessions variable to a minimum of 1000 to support the max_session_count setting in the dmcl.ini file.

  Back to Top       Previous  Next