2 Deployment Requirements

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

This chapter contains the following sections:

System Requirements
Partitioning Requirements
Disk Storage Requirement
Operating System Users and Groups
Network Setup Requirements
Removing IBM JDK and JRE 1.3.x
Validation
Prerequisites for Installation and Configuration

System Requirements

Note:

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

http://ptd.us.oracle.com/pmo/ocs.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 clock speed, 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 25 or higher `glibc` 2.2.4-32 or higher During installation, on 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. 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-118`
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. Obtain the patch from the operating system CD-ROM and install it onto your system.)
BC numeric processing language	`bc-1.06-5` (Available on the RedHat AS 2.1 CD. Obtain the patch from the operating system CD-ROM and install it onto your system.)
Procinfo	`procinfo-18-2` (Available on the RedHat AS 2.1 CD. Obtain the patch from the operating system CD-ROM and install it onto your system.)
Expect	`expect-5.32.2-65` (Available on the RedHat AS 2.1 CD. Obtain the patch from the operating system 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 Infostores with a single-database instance.

Table 2-3 Kernel Configuration Settings

Kernel Parameter	Minimum Setting	Definition
SEMMNI	142	Defines the maximum number of semaphore sets in the entire system.
SEMMNS	32000	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	250	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	4096	Defines the maximum number of shared memory segments in the entire system.
`fs.file_max`	270336	Defines the maximum number of open files on this system.
Local `IP` port range	10000 - 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	2766	Defines the maximum number of message queue IDs.
MSGMNB	65536	Defines the maximum size of the message queue.
MSGMAX	8192	Defines the maximum packet size in the message queue.
SHMALL	3282294	Defines the system wide maximum of shared memory pages.

Partitioning Requirements

Ensure that your system meets 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 allocate the 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 Infostores. 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.3) database for Email Infostore (These partitions are 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 Email Infostore database.
Oracle9i Release 2 (9.2.0.3) database for Files Infostore (These partitions are 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 Files Infostore database.
Oracle9i Release 2 (9.2.0.3) database for Real-Time Collaboration Infostore (These partitions are only required if you are deploying Real-Time Collaboration.)	`/XYYYYr/oracle`	4 GB	This will be the `ORACLE_BASE`. The Oracle home for Real-Time Collaboration Infostore will be `$ORACLE_BASE/product/920`.
	`/XYYYYr/oradata`^Foot 3	8 GB	All database-related files will be distributed in the following directories as per Outsourcing standards: `/XYYYYr/oradata/data01` `/XYYYYr/oradata/data02` `/XYYYYr/oradata/data03`
	`/XYYYYr/arch`	4 GB	Archive logs for Real-Time Collaboration Infostore database.
Oracle9iAS Infrastructure release 9.0.2.3 (Infrastructure database 9.0.1.4)	`/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/oracle_logs`	1 GB	Major log files for 9iAS Infrastructure.
	`/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.4 middle-tier for Calendar Server (These partitions are 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_904`.
	`/XYYYYc/collab_logs`	1 GB	Major log files for Oracle Collaboration Suite Calendar Server.
	`/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 and the quota for each named user.
^Footnote 3The size of oradata partitions for Real-Time Collaboration depends on the number of named users for the application and the quota for each named user.

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

$ORACLE_BASE/oraInventory - A top-level inventory directory
$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 files 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.3, OID and SSO servers (Infrastructure mid-tier)	`/XYYYYs/idm`	4 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`.
	`/XYYYYs/idm_logs`	2 GB	Partition for the major log files of Oracle9iAS Infrastructure, OID and SSO servers.
Oracle Collaboration Suite release 9.0.4 middle-tier components	`/XYYYYu/collab`	4 GB	This will be the `ORACLE_BASE`. The Oracle home for Oracle Collaboration Suite middle-tier components will be `$ORACLE_BASE/product/ocsmt_904`. This Oracle home is for all middle-tier applications except Calendar. The OID and SSO servers will use the Infrastructure database on the database-tier.
	`/XYYYYu/collab_logs`	2 GB	Partition for the major log files or Oracle Collaboration Suite middle-tier components.

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.3) database for Email, Files, and Real-Time Collaboration Infostore	`/XYYYYa/oracle`	4 GB	This will be the `ORACLE_BASE`. The Oracle home for Email, Files, and Real-Time Collaboration Infostores will be `$ORACLE_BASE/product/920`.
	`/XYYYYa/oradata`^Foot 1	8 GB	All database-related files will be distributed in the following directories as per Outsourcing standards: `/XYYYYa/oradata/data01` `/XYYYYa/oradata/data02` `/XYYYYa/oradata/data03`
	`/XYYYYa/arch`	4 GB	Archive logs for Email, Files, and Real-Time Collaboration Infostores databases.
Oracle9iAS Infrastructure release 9.0.2.3, and OID and SSO servers	`/XYYYYs/oracle`	4 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/oracle_logs`	2 GB	Parition for the major log files of Oracle9iAS Infrastructure, OID and SSO servers.
	`/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.4 middle-tier components	`/XYYYYu/collab`	4 GB	This will be the `ORACLE_BASE`. The Oracle home for Oracle Collaboration Suite middle-tier applications will be `$ORACLE_BASE/product/ocsmt_904`. The Oracle Collaboration Suite middle-tier applications are Calendar, Email, Files, Portal, Real-Time Collaboration, Ultra Search, and Wireless.
	`/XYYYYu/collab_logs`	2 GB	Parition for the major log files of Oracle Collaboration Suite middle-tier components
	`/XYYYYu/calendardb`	2 GB	Calendar Server, a non-Oracle file system-based database.

^Footnote 1The size of oradata partitions for Email, Files, and Real-Time Collaboration 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

Oracle Collaboration Suite CC does not require you to create specific users. 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.

If the system uses NIS(YP) to manage users and groups, Oracle Collaboration Suite CC might not create the required users and groups correctly. You must create the users and groups before 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.3) database for Email Infostore	`orXYYYYu`	`dbXYYYYu`
Oracle9i Release 2 (9.2.0.3) database for Files Infostore	`orXYYYYf`	`dbXYYYYf`
Oracle9i Release 2 (9.2.0.3) database for Real-Time Collaboration Infostore	`orXYYYYr`	`dbXYYYYr`
Oracle9i Release 2 (9.2.0.3) database for Single Infostore	`orXYYYYa`	`dbXYYYYa`
Oracle9iAS Infrastructure release 9.0.2.3 database	`orXYYYYs`	`dbXYYYYs`
Oracle Collaboration Suite release 9.0.4 middle-tier for Calendar Server only	`iaXYYYYc`	`iaXYYYYc`

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.3 for OID and SSO servers	`iaXYYYYu`	`iaXYYYYu`
Oracle Collaboration Suite release 9.0.4 middle-tier for Email, Files, and Real-Time Collaboration	`iaXYYYYu`	`iaXYYYYu`

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

Product	OS User	OS Group
Oracle9i Release 2 (9.2.0.3) database for Single Infostore	`orXYYYYa`	`dbXYYYYa`
Oracle9iAS Infrastructure release 9.0.2.3 database, and OID and SSO servers	`iaXYYYYu`	`iaXYYYYu`
Oracle Collaboration Suite release 9.0.4 middle-tier components for Email, Files, Real-Time Collaboration, 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 to install and configure Oracle Collaboration Suite CC. 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 database (1521)
Net listener port for Email Infostore (1621)
Net listener port for Files Infostore (1721)
Net listener port for Real-Time Collaboration Infostore (1821)
Calendar Server ports (5730, 5731)

The ports in parentheses are the default ports for an "out-of-the-box" installation of Oracle Collaboration Suite CC.

You must also open the following ports to allow traffic from the database-tier to the middle-tier:

OID port (4032)
OID SSL port (4031)
HTTP (7778)
Web Cache Invalidation (4001)
Web Cache Administration (4000)

Removing IBM JDK and JRE 1.3.x

By default, Red Hat Advanced Server 2.1 installs the IBM JDK and JRE. However, the IBM JDK and JRE installed with Red Hat Advanced Server 2.1 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

Validation

To ensure that your system meets minimum specified requirements, Oracle Collaboration Suite CC checks that all the requirements listed in the preceding sections are met. 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 Utility Pack tar file (ocs904cc_utilpack.tar.gz) from http://ptd.us.oracle.com/pmo/ocs.htm 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 utilpack is extracted/validation/ocheck -product ocs -system -relaxed
```
If you have a system where Oracle Collaboration Suite release 9.0.4.1 Utility Pack is installed, use the following command to verify your system setup.
```
# /admin/mwcc/ocs/904/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.

Prerequisites for Installation and Configuration

You will need the following information before installing and configuring Oracle Collaboration Suite CC:

4-letter customer ID
instance type (test, development, or production)
install type (singletier, midtier, or dbtier)

Note:

You are asked to log in as the root user to start installation, configuration, or cloning. However, internally, all the operations are done as a normal operating system user (not the root user) who owns or will own the Oracle software except when it is mandatory to perform operations as the root user.

After you complete the installation and configuration of Oracle Collaboration Suite CC, you must perform maintenance and management operations using a normal operating system user who is the owner of a particular Oracle home, unless otherwise required by the base product itself.

See Also:

Appendix A, " Input Parameters for config.sh" for all input parameters that you need during installation and configuration.