2
Requirements

This chapter provides information about system hardware and software requirements. It also describes how to prepare your system with the necessary Oracle software. Topics in this chapter include:

• Hardware Requirements

• Operating System Requirements

• Oracle Database Requirements and Recommendations

• Oracle Software Requirements

• Upgrade Requirements and Process Overview

For additional information about any of the requirements or pre-installation steps involving Oracle Application Server, or components such as Oracle Internet Directory, see the appropriate guide from those listed under "Related Documents" in the Preface.

See Appendix A, "Planning Your Oracle CM SDK Deployment" for information about Oracle CM SDK deployment options.

Hardware Requirements

The requirements described in Table 2-1 and Table 2-2 are based on using the Oracle Application Server, A. J2EE and Web Cache installation type from the Oracle Application Server 10g (9.0.4) CD.

Table 2-1  Minimum Hardware Requirements for Single-Computer Deployment

Description	Requirement
Number of computers	1
Oracle CM SDK users supported	2 concurrent connected users
Number of CPUs	1 (add 1 CPU if Oracle Text is being used for indexing)
Minimum processor type	AIX CPU: All AIX compatible processors HP CPU: HP 9000 Series HP-UX processor for HP-UX 11.0 (64-bit) Linux CPU: 1-Ghz Pentium III Tru64 CPU: Alpha Processor Solaris: Ultra 60
RAM	1 gigabyte
Hard-disk drive space and swap space	8.5 gigabytes minimum total free hard-disk drive space required, which includes 6 gigabytes of space required by the Oracle database and Oracle Application Server Middle-Tier Install, and 2 gigabytes of swap space

Table 2-2  Minimum Hardware Requirements for Multiple-Computer Deployment

Description	Requirements
Number of computers	2
Oracle CM SDK users supported	50 concurrent connected users
Minimum processor type	AIX CPU: All AIX compatible processors HP CPU: HP 9000 Series HP-UX processor for HP-UX 11.0 (64-bit) Linux CPU: 1-Ghz Pentium III Tru64 CPU: Alpha Processor Solaris: Ultra 60
Computer 1:
Number of CPUs	1
RAM	1.5 gigabytes
Hard disk drive space and swap space	4 gigabytes minimum total free hard-disk drive space required, which includes 2 gigabytes of space required by Oracle Application Server Middle-Tier Install, and 2 gigabytes of swap space
Computer 2:
Number of CPUs	2 (includes 1 CPU for Oracle Text indexing)
RAM, disk, and swap space	See Oracle9i Database Server Installation Guide and Release Notes for requirements for the database computer.

The hardware requirements for multiple-computer deployment support a workgroup of about 50 Oracle CM SDK concurrent connected users accessing all protocols moderately (a concurrent connected user is a user who is authenticated and has performed an operation in the previous hour). The hardware requirements for single-computer deployment can support approximately two Oracle CM SDK concurrent connected users accessing two protocols moderately.

Table 2-1 and Table 2-2 do not include requirements for Oracle Internet Directory. If you want to use Oracle Internet Directory for Oracle CM SDK credential management, Oracle recommends that you install, configure, and run it on a separate computer. However, if your computer is powerful enough, it is possible to run Oracle CM SDK in an Oracle Application Server middle tier Oracle home and Oracle Internet Directory in an Oracle Application Server infrastructure Oracle home on the same computer. See Appendix A, "Planning Your Oracle CM SDK Deployment" for more information.

Operating System Requirements

For AIX, HP-UX, Compaq Tru64, and Linux operating system requirements, see Oracle Application Server 10g Installation Guide for configuration requirements. Also see the Oracle Content Management SDK Release Notes (platform-specific) for additional configuration requirements and caveats, in addition to the "Linux Requirements" noted in this section.

For Sun SPARC Solaris systems, Oracle CM SDK requires Sun SPARC Solaris 2.8 and Solaris 2.9 with the specific patches required by Oracle Application Server and any Solaris patches required for the JDK. See the Oracle Application Server 10g Installation Guide for Solaris patch requirements. You can download the patches from the Sun support web site (http://sunsolve.sun.com).

In addition, the Solaris system parameters must meet the requirements listed in the "Sun SPARC Solaris Kernel Parameters".

Linux Requirements

In addition to any issues in the Release Notes, the following requirements apply to Linux:

• If the Oracle database supporting Oracle CM SDK is running on Linux, you must patch the database due to Oracle Text bug 2037255 prior to installing, or the configuration will fail.

• The K desktop environment (KDE) does not support Oracle CM SDK installation on SuSE Linux 7.x (KDE2). Use fvwm or wmaker as the X Window manager when installing and configuring on Linux.

Sun SPARC Solaris Kernel Parameters

For Sun SPARC Solaris systems, if you create a database instance on a computer, you must make sure the kernel parameters for shared memory match the settings in the Oracle9i Database Installation Guide (excerpted as Table 2-3). However, note that the default settings typically meet or exceed these minimum values.

• If you make changes to the /etc/system file, be sure to reboot the computer so that the kernel settings can take effect.

  Table 2-3  Minimum Values for a Single Oracle9i Database Instance

  Kernel Parameter	Setting	Purpose
  SEMMNI	100	Defines the maximum number of semaphore sets in the entire system.
  SEMMNS	256	Defines the maximum 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 PROCESSES parameter for each Oracle database, adding the largest one twice, and then adding an additional 10 for each database.
  SEMMSL	256	Defines the minimum recommended value, for initial installation only.
  SHMMAX	4294967295	Defines the maximum allowable size of one shared memory segment, in bytes (4294967295 bytes = 4 GB).
  SHMMIN	1	Defines the minimum allowable size of a single shared memory segment.
  SHMMNI	100	Defines the maximum number of shared memory segments in the entire system.
  SHMSEG	10	Defines the maximum number of shared memory segments one process can attach.

See your hardware platform's documentation for more information about kernel parameters.

Oracle Database Requirements and Recommendations

To use an Oracle9i Database Server, Release 1 (9.2.0.3) database with Oracle CM SDK 10g (9.0.4), Oracle recommends that you create a separate Oracle home for Oracle Application Server (Oracle Application Server A, B, or C) on a different computer, and install and configure Oracle CM SDK in this Oracle home (see Chapter 1, Concepts, in the Oracle Content Management SDK Administrator's Guide for information about integrating with Oracle Application Server). See "Multiple-Computer Deployment" for details.

If you have an existing Oracle production database that you want to use as the database tier for Oracle CM SDK, be sure that it meets the following requirements:

• Oracle9i Database Server, Release 1 (9.2.0.3 or later); Enterprise or Standard Edition.

• Oracle JVM 9.2.0.3 (or above). Required; included as part of Enterprise or Standard Edition Oracle database server. See "Oracle JVM Option (JServer) Requirement" for information about how to confirm that this option exists in an existing database.

• Oracle Text 9.2.0.3 (or above). Required; Included as part of Enterprise or Standard Edition. Required for full-text search and retrieval.

• Oracle JDBC/OCI Driver for JDK 1.4. In addition, the thin driver is required by the Oracle CM SDK Configuration Assistant.

• Initialization parameter values that meet the Initialization Parameter Requirements.

• Free space of at least 450 MB in the USERS tablespace (if you plan to use the USERS tablespace to store Oracle CM SDK objects) or enough free space in the custom tablespaces to accommodate the tables and indexes created during configuration. (See Appendix B, "Creating an Oracle Database" for information about minimum free space in each custom tablespace.)

  Note: Oracle CM SDK also supports release 9.0.1.4 of Oracle9i Database Server.

Initialization Parameter Requirements

Configure Oracle9i Database Server using the parameters shown in Table 2-4. These parameters affect Oracle CM SDK installation and performance.

Table 2-4  Oracle9i Initialization Parameters

Parameter	Minimum Setting or Space Available
aq_tm_processes	1
java_pool_size	30 MB
job_queue_processes	4
open_cursors	300
processes	100
session_max_open_files	50
shared_pool_size	50 MB (52428800 bytes)

To check the value of the parameters, connect to the database using SQL*Plus and run the following query of the v$parameter view:

SELECT name, value FROM v$parameter WHERE name = 'processes';

SQL*Plus returns the value of the processes parameter. Repeat the command above, replacing the word processes with the appropriate parameter name to check the other parameter values as listed in Table 2-4.

If you need to change any parameters, be aware that initialization parameter settings are managed differently in Oracle9i than in prior releases. See the Oracle9i Database Administrator's Guide for your release for specific instructions before changing any settings.

Oracle JVM Option (JServer) Requirement

The Oracle CM SDK configuration fails if the Oracle JVM option (also known as JServer) is not installed and running in the database. The easiest way to verify that the Oracle JVM option exists is to connect to the database instance as SYS 'AS SYSDBA' using SQL*Plus and run the following query:

SELECT dbms_registry.status('JAVAVM') FROM dual;

If the result is VALID, then Oracle JVM is installed.

See the Oracle9i Installation Guide for information about installing the database with this option.

Oracle Software Requirements

Oracle CM SDK requires an Oracle home, based on Oracle Application Server 10g (9.0.4).

Oracle Home Requirement

Oracle CM SDK requires an Oracle home based on Oracle Application Server 10g (9.0.4) software, using one of the following installation types:

• A. J2EE and Web Cache

• B. Portal and Wireless

• C. Business Intelligence and Forms

Oracle recommends using the Oracle Application Server, A. J2EE and Web Cache installation option to support the middle tier, because it requires less RAM and hard-disk drive space than the other install types. Unlike the other installation options (B and C), the Oracle Application Server, A. J2EE and Web Cache installation type does not require Oracle Application Server, Infrastructure.

Installation option A allows you to use either Oracle CM SDK or Oracle Internet Directory for credential management. The other installation options (B and C) allow you to use either Oracle CM SDK or Oracle Internet Directory for credential management, but require you to install Oracle Internet Directory for use with other components.

To use Oracle Internet Directory for credential management, you must install and configure Oracle Application Server, Infrastructure. To improve performance, Oracle recommends that you install Oracle Application Server, Infrastructure on a separate computer.

Oracle Application Server, Infrastructure includes a restricted-use Enterprise Edition installation of the Oracle9i Database Server. During installation and configuration of Oracle Application Server Infrastructure, a database instance is created for the Oracle Application Server Metadata repository, and for Oracle Internet Directory. This should not be used for storing the Oracle CM SDK schema. Install Oracle Application Server, Infrastructure before installing Oracle CM SDK.

See Appendix A, "Planning Your Oracle CM SDK Deployment" for detailed deployment recommendations.

Upgrade Requirements and Process Overview

The process for upgrading an existing Oracle Internet File System or Oracle CM SDK to the current version of Oracle CM SDK depends on the release you are upgrading from, and on the release number of the Oracle database. Oracle CM SDK requires:

• Oracle9i Database Server release 9.0.1.4 or 9.2.0.3 (or later)

• Oracle Application Server 10g (9.0.4)

Each product must be in its own Oracle home. In addition, because of the respective resource requirements of each of these platforms, Oracle CM SDK typically requires multiple-computer deployment for production environments. Table 2-5 summarizes the process for several Oracle Internet File System and Oracle CM SDK releases.

Table 2-5  Overview of Steps for Various Upgrade Paths

Release Number	Process Summary
Oracle Internet File System 1.1.x	In order to install Oracle CM SDK 10g (9.0.4), you must first upgrade to Oracle Internet File System 9.0.1, and then upgrade to Oracle Internet File System 9.0.2. For instructions, see the installation documentation for Oracle Internet File System 9.0.1 and 9.0.2.
Oracle Internet File System 9.0.1	In order to install Oracle CM SDK 10g (9.0.4), you must first upgrade to Oracle Internet File System 9.0.2. For instructions, see the installation documentation for Oracle Internet File System 9.0.2.
Oracle Internet File System 9.0.2 and Oracle CM SDK 9.0.3	Install Oracle CM SDK into the Oracle Application Server-based (10g) Oracle home. Copy all custom classes from your old Oracle Internet File System or Oracle CM SDK installation to the following directory: $ORACLE_HOME/ifs/cmsdk/custom_classes Note: If you have a custom class named LINK, you must rename the class before installing Oracle CM SDK 10g (9.0.4). Upgrade your database to Oracle9i Database Server release 9.0.1.4 or 9.2.0.3 (or later) Use the Oracle CM SDK Configuration Assistant to upgrade to Oracle CM SDK 10g (9.0.4).

To use an existing Oracle database instance, see the "Oracle Database Requirements and Recommendations" to ensure that your instance meets all requirements.