| Oracle® Collaboration Suite Preinstallation Requirements Release 2 (9.0.4) Part Number B15607-01 |
|
|
View PDF |
| Oracle® Collaboration Suite Preinstallation Requirements Release 2 (9.0.4) Part Number B15607-01 |
|
|
View PDF |
This chapter discusses Oracle Collaboration Suite Release 2 (9.0.4.1) preinstallation requirements for hp Tru64 UNIX.
This chapter contains these topics:
Additional Hardware Requirements for Oracle Web Conferencing
Additional Software Requirements for Oracle Web Conferencing
Table 2-1 describes the minimum hardware requirements for each installation of Oracle Collaboration Suite.
Table 2-1 Oracle Collaboration Suite Hardware Requirements Foot 1
|
Note: Disk space must be available on a single disk. Oracle Collaboration Suite does not support spanning the installation over multiple disks. |
|
Note: If you are performing an upgrade, the Oracle Collaboration Suite upgrade assistant creates four new tablespaces for Oracle Email. See Chapter 3 of the Oracle Collaboration Suite Installation and Configuration Guide for Solaris for information about space requirements for these additional tablespaces. |
Use the following command to determine the amount of random access memory installed on hp Tru64 UNIX:
$ /bin/vmstat -P | grep " Total Physical Memory"
There are several hardware sizing considerations for Oracle Web Conferencing. The Oracle Web Conferencing Sizing Guide has complete information about these considerations. This section provides information about required hardware for the Voice Conversion Server used by Oracle Web Conferencing to support streaming voice data during conferences or playback of recorded conferences with voice data.
The Voice Conversion server must be installed on a computer with Microsoft Windows 2000 Server SP4 or above, with the following basic configuration:
2.4 GHz Intel Processor
512 MB SDRAM
20 GB disk
In addition, you need specialized telephony hardware. You need a T1 or E1 trunk, and a media processing board from Intel / Dialogic to support the trunk. The T1/E1 protocol supported by Oracle Web Conferencing is robbed-bit /CAS (Channel Associated Signaling). The following tables list hardware and sizing recommendations depending on the number of concurrent voice conferences, the type of and number of trunk lines, and the number of Voice Conversion Servers.
Table 2-2 Sizing Recommendations for Voice Conversion Using T1
| Concurrent Voice Conferences | T1 Lines | Voice Servers | Dialogic Hardware Needed per Voice Server |
|---|---|---|---|
| 12 | 1 | 1 | D/240JCT-T1 |
| 24 | 1 | 1 | D/480JCT-T1 |
| 48 | 2 | 1 | 2 x D/480JCT-T1 |
| 96 | 4 | 2 | 2 x D/480JCT-T1 |
| 192 | 8 | 4 | 2 x D/480JCT-T1 |
Table 2-3 Sizing Recommendations for Voice Conversion Using E1
| Concurrent Voice Conferences | T1 Lines | Voice Servers | Dialogic Hardware Needed per Voice Server |
|---|---|---|---|
| 15 | 1 | 1 | D/300JCT-E1 |
| 30 | 1 | 1 | D/300JCT-E1 |
| 60 | 2 | 1 | 2 x D/600JCT-E1 |
| 120 | 4 | 2 | 2 x D/600JCT-E1 |
| 240 | 8 | 4 | 2 x D/600JCT-E1 |
|
See Also: Oracle Web Conferencing Sizing Guide for specific information on sizing requirements for your system |
The following are the operating system requirements for hp Tru64 UNIX:
hp Tru64 UNIX 5.1B. Use the following command to determine the current operating system version:
sizer -v
JDK 1.3.1-5
X Windows must be installed on the system from where the installer is run. Use any HP-supported X Windows server with support for Motif, such as dtwm, twm, and mwm. Character mode installations are not supported for Oracle9iAS.
The X environments, Basic X-environments (OSF11), and X Servers (OSFSER) are required to run graphical products.
The following executables must be present in the /usr/ccs/bin directory:
make
ar
ld
nm
Your operating system can require the installation of patches and packages. Several of the patches listed in the following tables have dependency patches that must also be installed. See the readme files included with the patches and packages for additional information. When downloading a specific patch or package, verify dependencies and download the dependency patches or packages, if required.
|
Note: Your operating system must include thesendmail program. |
This section contains these topics:
Table 2-4 lists the patches required for Oracle Collaboration Suite:
Table 2-4 Required Patches for Oracle Collaboration Suite
| Installation | Patch |
|---|---|
| Operating system packages
These subsets are part of the hp Tru64 UNIX distribution |
|
| Operating system patches |
|
| Oracle9iAS Infrastructure and Oracle Collaboration Suite |
|
| Information Storage |
|
| Oracle Real Application Clusters |
|
Use the following command to determine if a specific patch is installed on the system:
$ /usr/sbin/dupatch -track -type kit
Use the following URL to download the operating system patches:
Table 2-5 lists additional software required for all platforms:
Table 2-5 Additional Required Operating System Requirements
| Software | Requirement |
|---|---|
| X Server and Window Manager | Use any X Server and window manager supported by your UNIX operating system.
For Hummingbird Exceed, use a native window manager. For WRQ Reflections, allow a remote window manager. To determine if your X Window System is working properly on your local system, enter the following command:
The X clock should appear on your monitor. |
| Required executables | The following executables must be present: make, ar, ld, and nm. |
Oracle Web Conferencing uses a Document Conversion Server to convert Microsoft Office documents into HTML or other compatible formats for sharing during conferences. The server must reside on a separate computer from the middle tier, and it must have Microsoft Windows NT and Microsoft Office 2000 or Microsoft Office XP.
Oracle Web Conferencing also uses a Voice Conversion Server to support streaming voice data during conferences or playback of recorded conferences with voice data. The server requires Microsoft Windows 2000 Server SP4 or above, and Intel Dialogic System Software 5.1.1 SP1 or above.
|
See Also: Oracle Web Conferencing Sizing Guide for more details about required hardware and software |
|
See Also: "Additional Hardware Requirements for Oracle Web Conferencing" for voice conversion server hardware requirements |
The Oracle Collaboration Suite user interface is available in the following languages: Arabic, Brazilian Portuguese, Danish, Dutch, English, Finnish, French, German, Greek, Italian, Japanese, Korean, Norwegian, Portuguese, Simplified Chinese, Spanish, Swedish, Traditional Chinese, and Turkish.
Oracle Calendar server administration tools have an English interface but support entering data in all Oracle Collaboration Suite supported languages.
The Oracle Calendar clients are available only in English with the following exceptions:
Oracle Connector for Outlook: All Oracle Collaboration Suite supported languages, except Arabic
Oracle Calendar Web client: All Oracle Collaboration Suite supported languages, except Arabic
Oracle Calendar desktop client for Windows: English, French, German, and Japanese
Oracle Calendar Sync for Palm for Windows: English, French, German, and Japanese
Oracle Calendar Sync for Pocket PC for Windows: English, French, German, and Japanese
You can view Oracle Collaboration Suite documentation online using a Web browser or Portable Document Format (PDF) Viewer.
Table 2-6 lists the requirements for viewing Oracle Collaboration Suite online documentation.
Table 2-6 Online Documentation Requirements
|
See Also: Oracle Collaboration Suite Documentation Roadmap |
Following installation, Oracle Universal Installer creates a file named portlist.ini showing the ports assigned during the installation of Oracle Collaboration Suite components. The installation process automatically detects any port conflicts and selects an alternate port in the range allocated for that component. The file is located at:
$ORACLE_HOME/install/portlist.ini
Many Oracle Collaboration Suite components require a Web browser. All Oracle Collaboration Suite installations require an Oracle9iAS Infrastructure and Oracle9i database. A complete list of certified software, including certified Oracle9iAS Infrastructure releases, database releases, and Web browsers for Oracle Collaboration Suite is located at OracleMetaLink:
http://metalink.oracle.com
Before installing Oracle Collaboration Suite, Oracle Corporation recommends that you read Oracle Collaboration Suite Release Notes, available in the doc directory of each Oracle Collaboration Suite installation CD-ROM and on Oracle Technology Network. See Oracle Collaboration Suite Documentation Roadmap for more information about Oracle Collaboration Suite documentation. Although this document is accurate at the time of publication, you can access the latest information and documentation on Oracle Technology Network:
http://otn.oracle.com/
This section contains these topics:
Real Application Clusters for Oracle Collaboration Suite Information Storage Installation
Configuring Kernel Parameters for Oracle Collaboration Suite
Table 2-7 explains how to set and unset environment variables.
Table 2-7 Setting and Unsetting Environment Variables
| To... | C shell | Bourne/Korn shell |
|---|---|---|
| Set an environment variable |
prompt> setenv VARIABLE value
|
prompt> VARIABLE=value;export VARIABLE
|
| Unset an environment variable |
prompt> unsetenv VARIABLE |
prompt> unset VARIABLE |
|
Note: You do not need to set the environment variablesLD_LIBRARY_PATH, ORACLE_HOME, TMP, TMPDIR, and TNS_ADMIN. |
Before starting Oracle Universal Installer, set the DISPLAY environment variable to refer to the X Server that displays Oracle Universal Installer. The format of the DISPLAY environment variable is:
hostname:display_number.screen_number
Oracle Collaboration Suite requires a running X Server to properly create graphics for Oracle Universal Installer, Web applications, and management tools. The frame buffer X Server installed with your operating system requires that you remain logged in and have the frame buffer running at all times. If you do not want to do this, then you must use a virtual frame buffer, such as X Virtual Frame Buffer (XVFB) or Virtual Network Computing (VNC).
Oracle Universal Installer configures this instance to use the same X Server from the installation process for applications and management tools. This X Server must either always be running or you must reconfigure Oracle Collaboration Suite to use another X Server that is always running after the installation completes.
|
See Also:
|
Installing From a Remote Computer
Setting the DISPLAY environment variable enables you to run Oracle Universal Installer remotely from another workstation. On the system where you launch Oracle Universal Installer, set DISPLAY to the system name or IP address of your local workstation.
|
Note: You can use a PC X emulator to run the install if it supports a PseudoColor color model or PseudoColor visual. Set the PC X emulator to use a PseudoColor visual, and then start Oracle Universal Installer. See the X emulator documentation for instructions on how to change the color model or visual settings. |
If you get an Xlib error similar to "Failed to connect to server", "Connection refused by server," or "Can't open display" when starting Oracle Universal Installer, then run the commands on your local workstations as listed in Table 2-8.
Table 2-8 DISPLAY Environment Variable Commands
Oracle Universal Installer requires that the fully-qualified hostname information appear in the configuration files for your computer. A fully-qualified hostname includes both the name of the system and its domain.
Failure to properly configure the hostname information in the listed files may result in runtime errors during Oracle Collaboration Suite installation.
Verify that /etc/hosts has the following format:
ip_address fully_qualified_hostname short_hostname aliases
The following example shows a properly configured /etc/hosts file:
148.87.9.44 oasdocs.us.oracle.com oasdocs oracleinstall
The installation process requires a special UNIX account and several special groups. See the following subsections for more information:
UNIX Group Name for the Oracle Universal Installer Inventory
UNIX Group Names for Privileged Groups
|
Note: You must use the same operating system user account when adding additional Oracle Collaboration Suite installations on the same host. |
Use the admintool or groupadd utility to create a group name such as oinstall. The oinstall group owns the Oracle Universal Installer oraInventory directory. The oracle user account that runs the installation must have the oinstall group as its primary group.
|
Note: The UNIX group name must not exceed 8 characters, otherwise the Oracle Calendar configuration assistant will fail. |
For more information about these utilities, see your operating system documentation.
The oracle account is the UNIX account that owns Oracle software for your system. You must run Oracle Universal Installer from this account.
Create an oracle account with the properties listed in Table 2-9.
Table 2-9 Oracle Account Properties
| Variable | Property |
|---|---|
| Login Name | Select any name to access the account. This document refers to the name as the oracle account. |
| Group Identifier | The oinstall group is used in this document. |
| Home Directory | Select a home directory consistent with other user home directories. |
| Login Shell | The default shell can be either the C, Bourne, or Korn shell. |
|
Note: Use theoracle account only for installing and maintaining Oracle software. Never use it for purposes unrelated to Oracle Universal Installer. Do not use root as the oracle account. |
Two privileged groups are required for Oracle9iAS Infrastructure installation and Oracle Collaboration Suite information storage installation:
These privileged groups are not required for Oracle Collaboration Suite installation.
Oracle documentation refers to these groups as OSOPER and OSDBA, respectively. Databases use these groups for operating system authentication. This is necessary in situations where the database is shut down and database authentication is unavailable.
The privileges of these groups are given to either a single UNIX group or two corresponding UNIX groups. There are two ways to choose which groups get the privileges:
If the oracle account is a member of the dba group before starting Oracle Universal Installer, then dba is given the privileges of both OSOPER and OSDBA.
If the oracle account is not a member of the dba group, then Oracle Universal Installer prompts you for the group names that get these privileges.
Table 2-10 lists the privileges for the OSOPER and OSDBA groups.
Table 2-10 Privileges for the OSOPER and OSDBA Groups
| Group | Privileges |
|---|---|
OSOPER |
Permits the user to perform STARTUP, SHUTDOWN, ALTER DATABASE OPEN/MOUNT, ALTER DATABASE BACKUP, ARCHIVE LOG, and RECOVER, and includes the RESTRICTED SESSION privilege. |
OSDBA |
Contains all system privileges with ADMIN OPTION, and the OSOPER role; permits CREATE DATABASE and time-based recover. |
Perform the following preinstallation steps to install Real Application Clusters.
|
See Also: Oracle9i Real Application Clusters Setup and Configuration for more information about preinstallation steps for Real Application Clusters. This manual is available on Oracle Technology Network athttp://otn.oracle.com/ |
Perform the following steps as the root user:
Log in as the root user.
Ensure that you have the OSDBA group defined in the /etc/group file on all nodes in the cluster. The OSDBA group name and number, and OSOPER group if you plan to designate one, must be identical for all nodes of a UNIX cluster accessing a single database. The default UNIX group name for the OSDBA group is dba.
Create the oracle account on each node of the cluster so that the account:
Has the ORAINVENTORY group as the primary group
Has the dba group as the secondary group
Is used only to install and update Oracle software
Has write permissions on remote directories
Create a mount point directory on each node to serve as the top of the Oracle software directory structure so that:
The name of the mount point on each node is identical to that on the initial node
The oracle account has read, write, and execute privileges
Set up user equivalence by adding entries for all nodes in the cluster on the node from which to run Oracle Universal Installer, including the local node, to either the .rhosts file of the oracle account or the /etc/hosts.equiv file.
Check user equivalence by executing a remote command on every node as the oracle user using the following command:
prompt> rsh another_host pwd
Check RCP equivalence by copying a small file from every node to every node. For example, enter:
prompt> rcp /tmp/dummy_file another_host:/tmp/dummy_file
This is required for Oracle Universal Installer to install Oracle software on all selected nodes of the cluster.
Perform the following steps as the oracle user:
Log in as the oracle account.
Verify that the Cluster Membership Monitor is running using the following command:
$ /usr/sbin/clu_get_info
Verify that the correct number of cluster members are configured. Member state for all nodes should be "up".
Check for user equivalence of the oracle account by performing a remote login (rlogin) to each node in the cluster.
If you are prompted for a password, the oracle account does not have user equivalence. Ensure that you gave the same attributes to the oracle user on all the nodes in the cluster. Oracle Universal Installer cannot use the rcp command to copy Oracle products to the remote directories without user equivalence.
If you have not set up user equivalence, you must perform Step 6 in "Steps to Perform as the root User for Real Application Clusters Installation".
Create at least one shared configuration file as an information repository for the database server configuration. If your platform supports the Cluster File System, skip this step.
Create a shared raw device of at least 100 MB for the Server Management (SRVM) configuration. Oracle Universal Installer prompts you for the name of this shared file on the Shared Configuration File Name Page. Alternatively, set the environment variable SRVM_SHARED_CONFIG to the absolute path name of the shared raw device from which Oracle Universal Installer can retrieve the configuration file.
|
See Also: Oracle9i Real Application Clusters Setup and Configuration for more information about setting up a shared configuration file |
The Oracle9iAS Metadata Repository installation requires you to configure your system kernel parameters. Compliance with this requirement is especially important for production environments. Review your kernel parameter settings to ensure that they meet Oracle9iAS Metadata Repository and Oracle Internet Directory requirements. You may experience errors during installation or operational errors after installation if this is not completed.
If you change the kernel settings, you must restart your system in order for kernel changes to take effect.
The parameters in the Table 2-11 are the recommended values for Oracle9iAS Infrastructure on hp Tru64 UNIX:
Table 2-11 Kernel Parameter Settings for hp Tru64 UNIX for Oracle9iAS Infrastructure
| Kernel Parameter | Setting | Purpose |
|---|---|---|
| MAX_PROC_PER USER | 2566 | Defines the maximum processors per user |
| MSG_MNB | 360000 | Defines the maximum bytes in a message queue |
| MSG_MNI | 2800 | Defines the maximum message queues system-wide |
| MSG_TQL | 2540 | Defines the maximum messages system-wide |
| SEM_MNI | 52 | Defines the maximum semaphores system-wide |
| SEM_MSL | 25 | Defines the maximum semaphores system-wide |
| SEM_OPM | 12 | Defines the maximum operations per semop call |
| SEM_UME | 42 | Defines the maximum semaphore undo per semaphore |
| SHM_MAX | 4278190080 (4 GB less 16 MB) | Defines the maximum allowable size of the shared memory. The SHM_MAX parameter does not affect how much shared memory is used or needed by Oracle9i, the operating system, or the operating system kernel. |
| SHM_MNI | 274 | Defines the maximum number of shared memory segments in the entire system. |
| SHM_SEG | 128 | Defines the maximum number of shared memory segments one process can attach. |
The Oracle Collaboration Suite installation requires you to configure your system kernel parameters. Compliance with this requirement is especially important for production environments. Review your kernel parameter settings to ensure that they meet Oracle Collaboration Suite requirements. You may experience errors during installation or operational errors after installation if this is not completed.
If you change the kernel parameter settings, you must restart your system in order for kernel changes to take effect.
The parameters in the Table 2-12 are the recommended values for Oracle Collaboration Suite on hp Tru64 UNIX:
Table 2-12 Kernel Parameter Settings for hp Tru64 UNIX for Oracle Collaboration Suite
| Kernel Parameter | Setting | Purpose |
|---|---|---|
| MAX_PROC_PER USER | 2566 | Defines the maximum processors per user |
| MSG_MNB | 360000 | Defines the maximum bytes in a message queue |
| MSG_MNI | 2800 | Defines the maximum message queues system-wide |
| MSG_TQL | 2540 | Defines the maximum messages system-wide |
| SEM_MNI | 52 | Defines the maximum semaphores system-wide |
| SEM_MSL | 25 | Defines the maximum semaphores system-wide |
| SEM_OPM | 12 | Defines the maximum operations per semop call |
| SEM_UME | 42 | Defines the maximum semaphore undo per semaphore |
| SHM_MAX | 4278190080 (4 GB less 16 MB) | Defines the maximum allowable size of the shared memory. The SHM_MAX parameter does not affect how much shared memory is used or needed by Oracle9i, the operating system, or the operating system kernel. |
| SHM_MNI | 274 | Defines the maximum number of shared memory segments in the entire system. |
| SHM_SEG | 128 | Defines the maximum number of shared memory segments one process can attach. |
Oracle Collaboration Suite information storage uses UNIX resources such as shared memory, swap memory, and semaphore extensively for interprocess communication. If your parameter settings are insufficient for Oracle Collaboration Suite information storage, then you experience problems during installation and instance startup.The greater the amount of data you can store in memory, the faster your database operates. In addition, by maintaining data in memory, the UNIX kernel reduces disk I/O activity.
Review your kernel parameter settings to ensure that they meet Oracle Collaboration Suite information storage requirements. If you do not do this, you may experience errors during installation, or operational errors after installation. These are the recommended kernel parameter requirements for a typical Oracle Collaboration Suite information storage environment.If you have previously tuned your kernel parameters to levels that meet your application needs, then continue to use these values. A system restart is necessary if you change the kernel settings for the kernel changes to take effect.
For hp Tru64 UNIX, use a text editor such as vi to change the kernel parameter settings in the /etc/sysconfigtab file after making a backup copy. If you have previously changed your kernel for another program to levels equal to or higher than the levels that Oracle9i requires, then do not touch the settings. If the levels are too low, then change them to at least as high as those in the table. If you change the settings, then save the /etc/sysconfigtab file and restart the system. For example, if you need to change your SHM_MAX, SHM_MNI, SHM_SEG, PER_PROC_STACK_SIZE, and PER_PROC_DATA_SIZE parameter settings, then add the following lines to the /etc/sysconfigtab file:
ipc: shm_max = 4278190080 shm_mni = 256 shm_seg = 128 proc: per_proc_stack_size = 33554432 per_proc_data_size = 201326592
Refer to the following table to determine if your system-shared memory and semaphore kernel parameters are set high enough for Oracle9i.
To determine the current kernel parameter settings, use the following command:
# /sbin/sysconfig -q ipc
The parameters in the Table 2-13 are the recommended values to run Oracle9i with a single database instance on hp Tru64 UNIX:
Table 2-13 Kernel Parameter Settings for hp Tru64 UNIX for Oracle Collaboration Suite Information Storage
| Kernel Parameter | Setting | Purpose |
|---|---|---|
| MAX_PER_PROC_STACK_SIZE | 33554432 (32 MB) | Defines the processor stack size. The default size is sufficient for Oracle9i software. If an application that shares the system with Oracle9i requires a higher per process stack size, do not set this parameter higher than 512 MB. |
| PER_PROC_STACK_SIZE | 33554432 (32 MB) | Defines the processor stack size. The default size is sufficient for Oracle9i software. If an application that shares the system with Oracle9i requires a higher per process stack size, do not set this parameter higher than 512 MB. |
| PER_PROC_DATA_SIZE | 201326592 (192 MB) | Defines the minimum per process data segment size. |
| SHM_MAX | 4278190080 (4 GB less 16 MB) | Defines the maximum allowable size of the shared memory. The SHM_MAX parameter does not affect how much shared memory is used or needed by Oracle9i, the operating system, or the operating system kernel. |
| SHM_MIN | 1 | Defines the minimum allowable size of a single shared memory segment. |
| SHM_MNI | 256 | Defines the maximum number of shared memory segments in the entire system. |
| SHMSEG | 128 | Defines the maximum number of shared memory segments one process can attach. |
Although Oracle recommends that you install the Oracle9iAS Infrastructure, Oracle Collaboration Suite information storage database, and Oracle Collaboration Suite middle tier on separate computers for better performance, you can install Oracle Collaboration Suite on one computer. A single-computer installation DVD is provided in the CD pack for Linux and Windows platforms. For other platforms, you can perform a single-computer installation using the CD-ROM sets in the CD pack.
|
See Also: http://otn.oracle.com/software/products/cs/files/README.html for information about single-computer installations on Windows and http://otn.oracle.com/software/products/cs/files/readme _linux.html for information about single-computer installations on Linux |
|
Note: The Oracle Web Conferencing document conversion server and voice conversion server must be installed on a separate computer from the Oracle Collaboration Suite middle tier. Additionally, Oracle recommends that you install the Oracle Web Conferencing document conversion server and voice conversion server on separate computers. Both the Oracle Web Conferencing document conversion server and voice conversion server must be installed on Windows platforms. |
|
See Also: The Oracle Web Conferencing Administrator's Guide for more information about the Oracle Web Conferencing document and voice conversion servers |
