2 Deployment Requirements

This chapter provides preinstallation requirements for Oracle Collaboration Suite Certified Configuration (Oracle Collaboration Suite CC).

This chapter contains the following sections:

System Requirements
Partitioning Requirements
Operating System Users and Groups
Additional System Setup
Validation

System Requirements

Note:

Check the following URL for the latest updates for Oracle Collaboration Suite CC:

http://pleias.us.oracle.com/repo/OCS_CC9.0.3_221/Shiphomes/Collaboration%20Suite%209_0_3_1%20Certified%20Configuration%20Release%202_2_1%20Announcement.htm

Ensure that your system meets the following requirements:

Hardware Requirements

Table 2-1, "Hardware Requirements for Oracle Collaboration Suite CC" lists hardware requirements for Oracle Collaboration Suite CC.

Table 2-1 Hardware Requirements for Oracle Collaboration Suite CC

Hardware Component	Requirement
Minimum number of CPUs	2
Minimum CPU clock speed	450 MHz
Minimum CPU power factor	1400
Minimum physical memory	2 GB
Minimum number of NICs	2
Disk space	See "Partitioning Requirements".

Note:

If you have a CPU with a lower frequency, then you will need more CPUs to meet the total system power factor.

Software Requirements

Table 2-2, "Software Requirements" lists software requirements for a typical Oracle Collaboration Suite CC software installation and for creating a simple prototype database.

Table 2-2 Software Requirements

Software Component	Requirement
Operating System	Red Hat Advanced Server 2.1, with the following: Enterprise kernel, Errata 12 or higher glibc 2.2.4-26 or higher During installation, in the Package Group Selection page, always select Software Development.
Operating System Patches	`binutils-2.11.90.0.8-13` This patch is not required if you install from the gold image. It is only required when you install from the Product CD-ROMs. Oracle Corporation has assigned bug number 2414946 to track this patch. You can obtain the patch by accessing the Oracle Automated Release Updates (ARU) Web site (`http://aru.us.oracle.com`), and searching for ARU# 1843755. Follow the instructions in the patch README file to install the patch. Oracle Corporation recommends that you remove this patch after configuring Oracle Collaboration Suite CC.
C Compiler	`gcc-2.96-108.1`
X Server and Window Manager	`Xfree86` To determine if your X Window System is working properly on your local system, enter the following command: $ xclock The X clock should appear on your monitor.
Korn shell (`ksh`)	`pdksh-5.2.14-13` (Available on the RedHat AS 2.1 CD. Retrieve the patch from the OS CD-ROM and install it onto your system.)
BC numeric processing language	`bc-1.06-5` (Available on the RedHat AS 2.1 CD. Retrieve the patch from the OS CD-ROM and install it onto your system.)
Procinfo	`procinfo-18-2` (Available on the RedHat AS 2.1 CD. Retrieve the patch from the OS CD-ROM and install it onto your system.)

Kernel Parameter Settings

Table 2-3, "Kernel Configuration Settings" shows the minimum values required to run Oracle Collaboration Suite Infostore with a single-database instance.

Table 2-3 Kernel Configuration Settings

Kernel Parameter	Minimum Setting	Definition
SEMMNI	100	Defines the maximum number of semaphore sets in the entire system.
SEMMNS	256	Defines the maximum number of semaphores on the system. This setting is a minimum recommended value, for initial installation only. The SEMMNS parameter should be set to the sum of the `initsid.ora` `PROCESSES` parameter for each Oracle database, adding the largest one twice, and then adding an additional 10 for each database.
SEMOPM	100	Defines the maximum number of operations for each `semop` call.
SEMMSL	100	Defines the minimum recommended value, for initial installation only.
SHMMAX	2147483648	Defines the maximum allowable size of one shared memory segment. 2 GB for SMP kernel. The recommended size is half the RAM size. Note: SHMMAX cannot be greater than the physical memory on the machine.
SHMMNI	100	Defines the maximum number of shared memory segments in the entire system.
`fs` `file_max`	256000	Defines the maximum number of open files on this system.
Local `IP` port range	1024 - 65000	Defines the local port range used by TCP and UDP traffic to choose the local port.
Process limit	16384	Defines the maximum number of processes a user can start. Set by using `ulimit -u`.
threads_max	6000	Defines the maximum number of threads on this system.
MSGMNI	6000	Defines the maximum number of message queue IDs.
MSGMNB	6000	Defines the maximum size of the message queue.

Partitioning Requirements

Ensure you meet the following partitioning requirements before you install Oracle Collaboration Suite CC.

Partitions for Local Disk

The following table lists the partitions that must be created on the local disk for a successful installation of Oracle Collaboration Suite CC.

Table 2-4 Partition Requirements

Mount Point	Minimum Size (GB)	Description
`/`	9 GB	Besides `root`, this partition also contains the `/usr`, `/opt`, `/var` and `/tmp` directories.
`/boot`	128 MB	Operating system kernel
`/oem`	1 GB	Oracle Enterprise Manager installation
`Swap`	4 GB	The recommended swap space size is 2 times the size of RAM.
`/admin`	4 GB (minimum or rest of the disk)	Top-level directory for certified configuration scripts, tooling, and so on.

Partitions for Oracle Software

This section describes the file system layout for two-tier (preferred model) and single-tier deployments of Oracle Collaboration Suite CC. Although you can create these partitions on a local disk, Oracle Corporation recommends that you create these partitions on an off-host storage.

The XYYYY naming convention that are used in the following tables is described as follows:

X is a one-letter instance ID (‘t’ for test and ‘p’ for production)
YYYY is the four-letter customer ID

For example, a test instance deployment with a customer ID of ‘orcl’ would replace XYYYY with ‘torcl’.

Partitions for Two-Tier Deployment: Partitions on a Database-Tier System

Note:

If you are deploying Infostores on Real Application Clusters CC, refer to Real Application Clusters CC documentation for partition requirements for Email and Files. Do not use the following partitions for Email and Files Infostores on Real Application Clusters CC.

The following table lists the partitions on a database-tier system.

Table 2-5 Partitions for a Two-Tier Deployment: Partitions on a Database-Tier System

Product	Mount Point	Size	Description
Oracle9i Release 2 (9.2.0.2) database for Email Infostore (This is only required if you are deploying Email.)	`/XYYYYu/oracle`	4 GB	This will be the `ORACLE_BASE`. The Oracle home for Email Infostore will be `$ORACLE_BASE/product/920`.
	`/XYYYYu/oradata`^Foot 1	8 GB	All database-related files will be distributed in the following directories as per Outsourcing standards: `/XYYYYu/oradata/data01` `/XYYYYu/oradata/data02` `/XYYYYu/oradata/data03`
	`/XYYYYu/arch`	4 GB	Archive logs for Infostore Email database.
Oracle9i Release 2 (9.2.0.2) database for Files Infostore (This is only required if you are deploying Files.)	`/XYYYYf/oracle`	4 GB	This will be the `ORACLE_BASE`. The Oracle home for Files Infostore will be `$ORACLE_BASE/product/920`.
	`/XYYYYf/oradata`^Foot 2	8 GB	All database-related files will be distributed in the following directories as per Outsourcing standards: `/XYYYYf/oradata/data01` `/XYYYYf/oradata/data02` `/XYYYYf/oradata/data03`
	`/XYYYYf/arch`	4 GB	Archive logs for Infostore Files database.
Oracle9iAS Infrastructure release 9.0.2.1 database (Infrastructure database)	`/XYYYYs/oracle`	4 GB	This will be the `ORACLE_BASE`. The Oracle home for the Oracle9iAS Infrastructure database will be `$ORACLE_BASE/product/infra_902`.
	`/XYYYYs/oradata`	8 GB	All 9iAS Infrastructure database related files will be distributed in the following directories as per Outsourcing standards: `/XYYYYs/oradata/data01` `/XYYYYs/oradata/data02` `/XYYYYs/oradata/data03`
	`/XYYYYs/arch`	4 GB	Archive logs for Infrastructure database.
Oracle Collaboration Suite release 9.0.3.1 middle-tier for Calendar Server (This is only required if you are deploying Calendar.)	`/XYYYYc/collab`	4 GB	This will be the `ORACLE_BASE`. The Oracle home for Calendar Server will be `$ORACLE_BASE/product/ocsmt_903`.
	`/XYYYYc/calendardb`	2 GB	Calendar Server, a non-Oracle file system-based database.

^Footnote 1The size of oradata partitions for Email depends on the number of named users for the application and the quota for each named user.
^Footnote 2The size of oradata partitions for Files depends on the number of named users for the application the quota for each named user.

The ORACLE_BASE partition will also contain following few important directories besides ORACLE_HOME:

$ORACLE_BASE/oraInventory - A top-level inventory
$ORACLE_BASE/jre - A top-level directory containing JRE required for OUI
$ORACLE_BASE/oui - A top-level directory containing Oracle Universal Installer
$ORACLE_BASE/admin - A top-level directory containing administrative file for ORACLE_HOME like udump, bdump, and so on.

Partitions for a Two-Tier Deployment: Partitions on a Middle-Tier System

The following table lists the partitions for a middle-tier deployment.

Table 2-6 Partitions for a Two-Tier Deployment: Partitions on a Middle-Tier System

Product Mount Point Size Description

Oracle9iAS Infrastructure release 9.0.2.1 (OID and SSO servers) (Infrastructure mid-tier) /XYYYYs/idm 8 GB This will be the ORACLE_BASE. The Oracle home for Oracle9iAS Infrastructure mid-tier running OID and SSO servers is $ORACLE_BASE/product/infra_902.

Oracle Collaboration Suite release 9.0.3.1 middle-tier components (Email and Files only)

Product	Mount Point	Size	Description
Oracle9iAS Infrastructure release 9.0.2.1 (OID and SSO servers) (Infrastructure mid-tier)	`/XYYYYs/idm`	8 GB	This will be the `ORACLE_BASE`. The Oracle home for Oracle9iAS Infrastructure mid-tier running OID and SSO servers is `$ORACLE_BASE/product/infra_902`.
Oracle Collaboration Suite release 9.0.3.1 middle-tier components (Email and Files only)	`/XYYYYc/collab` Note: The letter `‘c’` in `/XYYYYc` should be replaced by the following letters for customer deployments: `‘u’` if deploying Email or Email and Files `‘f’` if deploying Files only	8 GB	This will be the `ORACLE_BASE`. The Oracle home for Oracle Collaboration Suite middle-tier components will be `$ORACLE_BASE/product/ocsmt_903`. This Oracle home is for all middle-tier applications except Calendar (Email and Files only). The OID and SSO servers will use the Infrastructure database on the database-tier.

/XYYYYc/collab

Note: The letter ‘c’ in /XYYYYc should be replaced by the following letters for customer deployments:

‘u’ if deploying Email or Email and Files
‘f’ if deploying Files only

8 GB

This will be the ORACLE_BASE. The Oracle home for Oracle Collaboration Suite middle-tier components will be $ORACLE_BASE/product/ocsmt_903. This Oracle home is for all middle-tier applications except Calendar (Email and Files only). The OID and SSO servers will use the Infrastructure database on the database-tier.

Partitions for a Single-Tier Deployment

The following table lists the partitions for a single-tier deployment.

Table 2-7 Partitions for a Single-Tier Deployment

Product	Mount Point	Size	Description
Oracle9i Release 2 (9.2.0.2) database for Email Infostore (This is only required if you are deploying Email.)	`/XYYYYu/oracle`	8 GB	This will be the `ORACLE_BASE`. The Oracle home for Email Infostore will be `$ORACLE_BASE/product/920`.
	`/XYYYYu/oradata`^Foot 1	8 GB	All database-related files will be distributed in the following directories as per Outsourcing standards: `/XYYYYu/oradata/data01` `/XYYYYu/oradata/data02` `/XYYYYu/oradata/data03`
	`/XYYYYu/arch`	4 GB	Archive logs for Infostore Email database.
Oracle9i Release 2 (9.2.0.2) database for Files Infostore (This is only required if you are deploying Files.)	/XYYYYf/oracle	8 GB	This will be the `ORACLE_BASE`. The Oracle home for Files Infostore will be `$ORACLE_BASE/product/920`.
	`/XYYYYf/oradata`^Foot 2	8 GB	All database-related files will be distributed in the following directories as per Outsourcing standards: `/XYYYYf/oradata/data01` `/XYYYYf/oradata/data02` `/XYYYYf/oradata/data03`
	`/XYYYYf/arch`	4 GB	Archive logs for Infostore Files database.
Oracle9iAS Infrastructure release 9.0.2.1 database, and OID and SSO servers	`/XYYYYs/oracle`	8 GB	This will be the `ORACLE_BASE`. The Oracle home for Oracle9iAS Infrastructure database, and OID and SSO servers will be `$ORACLE_BASE/product/infra_902`.
	`/XYYYYs/oradata`	8 GB	All Infrastructure database-related files will be distributed in following directories as per standards: `/XYYYYs/oradata/data01` `/XYYYYs/oradata/data02` `/XYYYYs/oradata/data03`
	`/XYYYYs/arch`	4 GB	Archive logs for Infrastructure database.
Oracle Collaboration Suite release 9.0.3.1 middle-tier components (Email, Files, and Calendar)	`/XYYYYu/collab` Note: The letter `‘c’` of `/XYYYYc` should be replaced by the following letters for customer deployments: `‘u’` if deploying Email or Email and Files. `‘f’` if deploying Files only	8 GB	This will be the `ORACLE_BASE`. The Oracle home for Oracle Collaboration Suite middle-tier applications will be `$ORACLE_BASE/product/ocsmt_903`. The Oracle Collaboration Suite middle-tier applications are Calendar, Email, Files, Portal, Ultra Search, and Wireless.
	`/XYYYYc/calendardb`	2 GB	Calendar Server, a non-Oracle file system-based database.

^Footnote 1The size of oradata partitions for Email depends on the number of named users for the applications the quota for each named user.
^Footnote 2The size of oradata partitions for Files depends on the number of named users for the applications the quota for each named user.

Disk Storage Requirement

A quick method for sizing the raw disk requirements for an Oracle Collaboration Suite implementation on a NetApps Storage device looks like the following:

Raw disk = (number of named users) x (user quota) x 1.2 (metadata overhead) x 1.2 (snapshot overhead) x 1.4 (RAID 4 file system overhead)

So, a 10,000 user implementation with a 100 MB quota would require roughly 2 terabytes of storage.

Operating System Users and Groups

The Oracle Collaboration Suite CC does not require you to create specific users. The Oracle Collaboration Suite CC installations will create operating system users and groups based on the instance type (X) and customer ID (YYYY).

The following tables describes the list of users and groups that will be created during the installation of Oracle Collaboration Suite CC. All the users and groups are created with lowercase letters.

Note:

During installation, these passwords are set to unknown strings, therefore, you must set the password for these users after installation.

Table 2-8 Two-Tier Deployment: Users and Groups on Database-Tier

ORACLE_HOME	OS User	OS Group
Oracle9i Release 2 (9.2.0.2) database for Email Infostore	`orXYYYYu`	`dbXYYYYu`
Oracle9i Release 2 (9.2.0.2) database for Files Infostore	`orXYYYYf`	`dbXYYYYf`
Oracle9iAS Infrastructure release 9.0.2.1 database	`orXYYYYs`	`dbXYYYYs`
Oracle Collaboration Suite release 9.0.3.1 middle-tier for Calendar Server only	`iaXYYYYc` `unison`	`iaXYYYYc` `dxoffice`

Table 2-9 Two-Tier Deployment: Users and Groups on Middle-Tier System

Product	OS User	OS Group
Oracle9iAS Infrastructure database release 9.0.2.1 for OID and SSO servers	`i`aXYYYYu	`iaXYYYYu`
Oracle Collaboration Suite release 9.0.3.1 middle-tier for Email and Files	`iaXYYYYu`	`iaXYYYYu`

Table 2-10 Single-Tier Deployment: Users and Group

Product	OS User	OS Group
Oracle9i Release 2 (9.2.0.2) database for Email Infostore	`orXYYYYu`	`dbXYYYYu`
Oracle9i Release 2 (9.2.0.2) database for Files Infostore	`orXYYYYf`	`dbXYYYYf`
Oracle9iAS Infrastructure release 9.0.2.1 database, and OID and SSO servers	`iaXYYYYu`	`iaXYYYYu`
Oracle Collaboration Suite release 9.0.3.1 middle-tier components for Email, Files, and Calendar	`iaXYYYYu`	`iaXYYYYu`

Configuring Hostnames

The /etc/hosts file must contain the fully qualified hostname information for your computer. A fully qualified hostname includes both the name of the host system and its domain. Verify that the /etc/hosts file has the following format:

ip_address fully_qual_hostname short_hostname_aliases

where:

the variable ip_address represents the numeric value IP address for the host
the variable fully_qual_hostname represents the fully qualified host name
the variable short_hostname_aliases represents the alias by which the host can be accessed.

The following example shows a properly configured /etc/hosts file for iascc01 host:

127.0.0.1 localhost

148.87.9.44 iascc01.us.oracle.com iascc01

Network Setup Requirements

For a two-tier deployment with a firewall between the database-tier and the middle-tier systems, you must open a few firewall ports for Oracle Collaboration Suite CC installation and configuration. The following ports must be open on the firewall to allow traffic from the middle-tier to the database-tier:

Net listener port for Infrastructure Infostore (1521)
Net listener port for Email Infostore (1621)
Net listener port for Files database (1721)
Calendar Server ports (5730, 5731)

The ports in parentheses are the default ports when you install Oracle Collaboration Suite CC out-of-the-box.

Additionally, you must open the following ports to allow traffic from the database-tier to the middle-tier:

OID port (4032)
OID SSL port (4031)
Web Cache invalidation port (4001)
Web Cache listening port (7778)

Additional System Setup

Complete the following additional operating system setup tasks.

Removing IBM JDK and JRE 1.3.x

By default, Red Hat Advanced Server version 2.1 installs the IBM JDK and JRE. However, the IBM JDK and JRE are not compatible with Oracle Collaboration Suite. Oracle Corporation recommends that you remove the IBM JDK and JRE from your operating system. Oracle Corporation ships the required JDK and JRE with Oracle Collaboration Suite software.

As the root user, use the following commands to remove the IBM JRE and JDK from your system:

# rpm -e IBMJava2-SDK IBMJava2-JRE

Creating Symlink for fuser Executable

As the root user, create the symbolic link for fuser with the following command:

# ln -s /sbin/fuser /bin/fuser

Validation

To ensure that your system meets minimum specified requirements, Oracle Collaboration Suite CC checks to ensure that all the requirements listed in the preceding sections are met. Validated requirements include system requirements, partitioning requirements, and other previously mentioned requirements including kernel parameters. Validation occurs before installing and configuring Oracle Collaboration Suite CC.

If your system does not meet the minimum-specified requirements, then the installation or configuration will not proceed.

(Optional) You can use the following procedure to confirm that you meet the minimum-specified requirements before installing or configuring Oracle Collaboration Suite CC:

Log in as the root user.
Use ftp to obtain the Oracle Collaboration Suite CC CD-Zero tar file (ocs9031cc_cdzero.tar.gz) and extract it into a temporary directory.
Perform system checks to ensure that your system meets certified configuration requirements using the following command:
```
# <directory where cdzero is extracted/validation/ocheck -product ocs -system -relaxed
```
If you have a system where Oracle Collaboration Suite release 9.0.3.1 CD-Zero is installed, use the following command to verify your system setup.
```
# /admin/$ORACLE_CC_ROOT/ocs/9.0.3/validation/bin/ocheck -product ocs -system -relaxed
```
The Validation Report appears. If the report Status column lists "fail" for any item, then installation or configuration cannot proceed until the cause of the failure is fixed. If the report Status column lists "warn" for any item, then the item deviates from the specified minimum requirements. However, installation or configuration may still run to completion. Oracle Corporation recommends that you meet the minimum specified requirements.

If you receive a fail or warn message during validation, then compare the Expected column with the Value column, which lists your system hardware, software, and accounts and groups status. Make the necessary changes on your system to bring it up to the minimum required specifications for Oracle Collaboration Suite CC.