# Installation and Upgrade Guide

# Introduction

This chapter provides an overview of Collaboration and lists the minimum hardware and software requirements.

## Collaboration Overview

This section provides a general overview of Collaboration and its components. It also describes how these components are shared and interact with the portal.

### Collaboration Components

This section provides an overview of Collaboration components. For more information on Collaboration and how it is used within the context of the portal, see the Administrator Guide for BEA AquaLogic Interaction Collaboration.

Collaboration contains the following components:

Table 2-1 Collaboration Components

Component | Description
Portal | Serves end user portal pages and content. The portal allows end users to access portal content via MyPages, Community Pages, the Knowledge Directory, and Search. The portal also enables administrative actions, such as setting preferences on portlets or managing communities.
Collaboration | Collaboration expands the functionality of the portal. Collaboration allows multiple users to collaborate on projects and tasks. It also controls access based on access rights assigned to each user.
Image Service | Serves static content used or created by portal components. The Image Service serves images and other static content for use by the system.
Notification Service | Generates and sends e-mail notifications from projects to project users, and functions as a job server for Collaboration. These jobs are distinct from portal jobs, which run using the Automation Service. Jobs include, but are not limited to: summary notification, community role synchronization, and recycle bin management. All jobs run daily, and are managed in a queue; each time a job is completed, it is re-added to the queue.
Note: | The Notification Service is not required for users to employ the E-mail a Project feature. However, if the Notification Service is not running, the E-mail a Project feature is less useful. For more information about E-mail a Project, see Administrator's Guide for BEA AquaLogic Interaction Collaboration.
Search Service | Returns indexed content stored in the portal. Search Service returns content that is indexed in the system from the portal, Collaboration, and Publisher. Content that is indexed in the system includes documents, portlets, communities, and users as well as many other portal objects.
Automation Service | Runs jobs and other automated portal tasks. The Automation Service runs jobs that perform tasks such as crawling documents into the Knowledge Directory, synchronizing groups and users with external authentication sources, and maintaining the search collection.
Document Repository Service | The Document Repository Service stores content uploaded into the portal.
Collaboration Web Services API | This component allows developers to create, modify, and delete objects within Collaboration in response to events triggered by remote portlets and other enterprise applications. To use the Collaboration Web Services API, you must install the AquaLogic Interaction Development Kit (IDK). For detailed information on the IDK, including documentation and sample code, see the Developer Center.

### Recommended Configuration

The exact hardware configuration depends upon the size of your implementation among other factors. However, even in the smallest production environment, we strongly recommend that you install additional AquaLogic Interaction components, including Collaboration, on a separate machine from the portal and Image Service.

The following table shows a typical configuration:

Table 2-2 Recommended Configuration

Machine | Component
--- | ---
1: Portal Web Application Components | Portal Image Service API Service
2: Additional Web Application Components | Collaboration Publisher Studio Portlets
3: Search and Indexing Components | Automation Service Search Service
4: Persistent Storage Components | Document Repository Service Portal Database Collaboration Database

For more information on recommended configurations based on the size of your implementation, see the Deployment Guide for BEA AquaLogic User Interaction (Plumtree Application Suite).

## Hardware and Software Requirements

The following table lists the software requirements for Collaboration. For hardware requirements, consult the Deployment Guide for BEA AquaLogic User Interaction (Plumtree Application Suite). For the most current platform support information, refer to the Interoperability Matrix which can be found by logging in to: http://portal.plumtree.com. Then navigate to the Product Center and click Interoperability.

Caution: | IPv6 is not supported. You should verify that IPv6 is not enabled prior to installing this product.
Table 2-3 Hardware and Software Requirements
Component | Requirement
--- | ---
AquaLogic User Interaction Host Computer | Microsoft Windows 2000 SP4, Microsoft Windows 2003 SP1 Red Hat Enterprise Linux 3 Update 3 (ES & AS), on x86 SUSE Enterprise Linux 9, on x86 AIX 5.3, on POWER3, POWER4, POWER5 Solaris 8 and 9, on SPARC
Database Server Host Computer | Microsoft SQL Server 2000 SP3 (Windows only) Oracle 9i (9.2.0.4) in default or Oracle RAC configuration Oracle 10g (10.1.0.3) in default or Oracle RAC configuration
Portal | Plumtree Foundation 6.0, Plumtree Foundation 6.0 SP1 Plumtree Corporate Portal 5.0.4, 5.0.4J, 5.0.5, 5.0.5J
Note: | References in this documentation to Plumtree Corporate Portal 5.0.x apply to Plumtree Corporate Portal 5.0.4/5.0.5/5.0.4J/5.0.5J.
Browser | Microsoft Internet Explorer, versions 5.5 and 6.x Netscape 7.2 Safari 1.2 (Mac) Firefox 1.0 (and higher)
Groupware Servers | Microsoft Exchange 2000 SP3 (and higher) Microsoft Exchange 2003 Lotus Notes 5.0.11
Required Software for Exchange Integration | Microsoft.NET Microsoft Web Services Enhancement
Microsoft Project | Microsoft Project 2000 Microsoft Project 2003

Note: | Collaboration 4.1 contains a significant change in the deployment configuration for the product. Instead of installing the product, installing a separate application server, and deploying a WAR file to the application server, Collaboration 4.1 is self-contained. It includes the runtime components needed for HTTP/HTTPS processing, and it no longer requires a separate application server. This change facilitates the product installation and maintenance.