| Oracle® Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1.1) for Windows Part Number B12239-01 |
|
|
View PDF |
| Oracle® Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1.1) for Windows Part Number B12239-01 |
|
|
View PDF |
This chapter describes how to plan each Oracle Collaboration Suite installation.
This chapter contains these topics:
Table 2-1 describes the minimum hardware requirements for each installation of Oracle Collaboration Suite.
Table 2-1 Oracle Collaboration Suite Hardware RequirementsFoot 1
| Requirement | Value |
|---|---|
| CPU |
|
| Monitor | 256 color viewing capability |
| Memory (minimum requirement) |
|
TMP or TEMP directory |
Oracle9iAS infrastructure and Oracle Collaboration Suite middle tier require at least 300 MB of free space |
| Disk Space |
|
Oracle Web Conferencing offers document and voice conversion services. Document conversion services convert Microsoft Office documents into HTML for viewing in Document Presentation mode. Voice conversion services allow for voice streaming and for capturing and recording of the audio portion of a conference.
Document conversion is provided through the Document Conversion Server, which must reside on a separate computer from the middle tier. The computer must have Microsoft Windows 2000. The Voice Conversion Server must also reside on a separate computer from the middle tier, and this computer must have Microsoft Windows 2000. In addition, the Voice Conversion Server must have an Intel Dialogic card. Depending on your sizing requirements, you can install both servers on a single computer.
|
See Also: Oracle Web Conferencing Sizing Guide for specific information on sizing requirements for your system |
Table 2-2 describes the operating system requirements for each installation of Oracle Collaboration Suite.
Table 2-2 Operating System Requirements for Oracle Collaboration Suite
| Requirement | Value |
|---|---|
| Operating System | Oracle9iAS infrastructure and Oracle Collaboration Suite middle tier:
Oracle Collaboration Suite information storage:
|
| Virtual Memory | Oracle9iAS infrastructure:
Oracle Collaboration Suite information storage:
Oracle Collaboration Suite middle tier:
See Also: "Changing the Size of the Virtual Memory Paging File" |
Oracle Web Conferencing voice conversion services and document conversion services require additional hardware and software. Voice conversion services are enabled with the Oracle Web Conferencing Voice Conversion server and document conversion services are enabled with the Oracle Web Conferencing Voice Conversion server. For a description of these servers and their hardware requirements, see "Additional Hardware Requirements for Oracle Web Conferencing".
The computer or computers on which Oracle Web Conferencing voice and document conversion services reside must have the Microsoft Windows 2000 operating system. The computer with the Voice Conversion Server must also have the Intel Dialogic software. The computer with the Document Conversion Server must have Microsoft Office 2000. Depending on your sizing requirements, both servers can be installed on a single computer, but all hardware and software requirements must be met.
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-3 lists the requirements for viewing Oracle Collaboration Suite online documentation.
Table 2-3 Online Documentation Requirements
|
See Also: Oracle Collaboration Suite Documentation Roadmap |
Following installation, the 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.
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
This section contains these topics:
When installing the Oracle9iAS infrastructure or the Oracle Collaboration Suite middle tier, ensure that the TMP or TEMP directory has 300 MB, or more, of free space.
|
Important: TheORACLE_HOME environment variable is automatically set in the registry. Do not set this variable as a System Environment variable, as it prevents installation. |
To change the TMP or TEMP directory path on Windows NT:
Select Start > Settings > Control Panel > System.
Select the Environment tab.
Select the TMP or TEMP variable from the User Variables for username list box.
Change the Value field to a directory with 300 MB, or more, of free space.
Click Set.
Click OK.
To change the TMP or TEMP directory path on Windows 2000:
Select Start > Settings > Control Panel > System.
Select the Advanced tab.
Click Environment Variables.
Select the TMP or TEMP variable from the User Variables for username list box.
Click Edit.
Change the Variable Value field to a directory with 300 MB, or more, of free space.
Click OK until you exit System Properties.
To change the amount of virtual memory on Windows NT:
Select Start > Settings > Control Panel > System.
Select the Performance tab.
Click Change.
Select the appropriate drive and enter the new value in the Initial size (MB) field.
Click Set.
Click OK until you exit System Properties.
To change the amount of virtual memory on Windows 2000:
Select Start > Settings > Control Panel > System.
Select the Advanced tab.
Click Performance Options.
Click Change.
Select the appropriate drive and enter the new value in the Initial size (MB) field.
Click Set.
Click OK until you exit System Properties.
Perform the following preinstallation steps to install Real Application Clusters. This information is also described in the Oracle Cluster Setup Wizard online help.
|
See Also: Oracle9i Real Application Clusters Setup and Configuration for more information on preinstallation steps for Real Application Clusters. This manual is available on Oracle Technology Network athttp://otn.oracle.com/ |
This section contains these topics:
Each instance shares a set of unformatted devices on a shared disk subsystem for data files. The number and type of raw devices required depends on several factors.
If you plan to use one of the General Purpose, Transaction Processing, or Data Warehouse database configuration types, you must create specific tablespaces using the minimum sizes listed in Table 2-4. When considering size requirements for your disks, remember to account for the initial signature of 1 or 2 MB on each disk that cannot be used for extended partitions. These requirements are the same for both the vendor-supplied clusterware layer and the Oracle-supplied clusterware layer.
If you do not create the database with the database configuration assistant, the number of logical drives you create depends on the number of data files, redo log files, and control files you plan to create. However, you must still create a logical drive of 100 MB for the Voting disk.
Table 2-4 Logical Drive Disk Sizes for Database Configuration Assistant
| Create a Partition for... | File Size |
|---|---|
SYSTEM tablespace |
420 MB |
| server parameter file | 5 MB |
USERS tablespace |
120 MB |
TEMP tablespace |
120 MB |
UNDOTBS tablespace |
320 MB |
EXAMPLE tablespace |
160 MB |
CWMLITE tablespace |
100 MB |
XDB tablespace |
50 MB |
ODM tablespace |
280 MB |
INDX tablespace |
70 MB |
TOOLS tablespace |
12 MB |
DRSYS tablespace |
250 MB |
| First control file | 110 MB |
| Second control file | 110 MB |
| Two redo log files for each instance | 120 MB |
srvcfg (Voting disk for clusterware) |
100 MB |
By default, the database configuration assistant uses automatic undo management. Create one Undo tablespace for each instance. Logical drive for the Undo tablespace for all preconfigured database templates must be at least 320 MB. If you use manual undo management, make the RBS logical drive at least 625 MB in size.
|
See Also: Oracle9i Real Application Clusters Setup and Configuration for more information on planning your raw device creation strategy and DBCA database configuration options |
Perform the following tasks on your Windows NT or Windows 2000 computer to prepare a set of nodes for cluster software installation:
To configure unformatted logical drives, create an extended partition and multiple logical drives.
From one node in the cluster, run Windows NT Disk Administrator or Disk Management to create an extended partition and multiple logical drives. Each computer must be a member of the same domain or within a trusted domain.
|
See Also: Your Windows Disk Administrator or Disk Management online help for more information about creating and managing extended partitions and logical drives |
This section contains instructions for:
Run Windows NT Disk Administrator from one node to create an extended partition and configure logical drives on the shared disk for the entire cluster. You can use more than one disk to accommodate all the partitions, depending on your shared disk array's configuration. Each computer must be a member of the same domain or within a trusted domain.
To create an extended partition:
Log in as member of the Administrators Group.
Choose Start > Programs > Administrative Tools > Disk Administrator to display the Disk Administrator window.
Right-click an unpartitioned disk, or an area of free space on a disk that does not contain an extended partition.
Select Create Extended. The Disk Administrator displays the maximum sizes for the extended partition.
Enter the size of the partition of the extended partition, then click OK.
To create a logical drive:
|
Note: When storing Oracle files on raw devices, Oracle Corporation recommends that you do not create more than 120 logical drives within an extended partition. Doing so can significantly increase the time needed to restart your computer and start the disk administration tools. |
Select an area of free space in the extended partition.
Click Partition > Create.
The Disk Administrator window displays the minimum and maximum sizes for the logical drive.
Enter the size of the logical drive that you want to create. Create the logical drives with file sizes shown in Table 2-4.
Click OK.
Select the logical drive.
Click Tools > Assign Drive Letter.
Select the Do not assign a drive letter option.
Click OK.
|
Note: Optionally, run theLetterDelete utility after creating all logical drives to remove all drive letter assignments with a single command. |
Repeat steps 1-5 until all required logical drives are created.
Click Partition > Commit Changes Now.
A confirmation dialog displays, informing you that changes have been made to the disk.
Click Yes to acknowledge the message.
A dialog box displays, informing you the disks have been updated successfully.
Click OK.
Click Partition > Exit.
Changes should be visible on all nodes.
The Disk Administrator window shown in Figure 2-1 illustrates an example of a disk configuration. The logical partitions are sized to allow the database configuration assistant to create a cluster database.
| Disk | Contains |
|---|---|
| Disk 0 | A primary partition |
| Disk 1 | An extended partition with 36 logical partitions and an area of free space |
Run Windows 2000 Disk Management from one node to create an extended partition and configure logical drives on the shared disk for the entire cluster. You can use more than one disk to accommodate all the partitions, depending on your shared disk array's configuration. Each computer must be a member of the same domain or within a trusted domain.
You must create primary partitions, an extended partition, and logical drives on basic disks. Dynamic disks are not supported. A basic disk uses the same partitions as earlier versions of Windows and can contain up to four primary partitions, or three primary partitions and one extended partition.
To create an extended partition and logical drives:
Click Settings > Control Panel.
Double-click Administrative Tools.
Click the + next to Storage, then select Disk Management.
The Computer Management window displays. View the status of a disk or volume in the Status column. Figure 2-2 shows the status of Healthy for volumes, and Online for disks.
Right-click an unallocated region of a basic disk, and click Create Partition. Or, right-click free space in an extended partition, and click Create Logical Drive.
Click Next > Extended Partition > Next, or Logical Drive > Next. Set the appropriate logical drive size for each tablespace data file listed in Table 2-4.
Click Next.
Select the Do not assign a drive letter or drive path option.
Click Next.
Select the Do not format this partition option.
Click Next.
Click Finish.
|
Note: If the Disk Management window is open during any disk management modifications, such as creating symbolic links or adding logical partitions, you need to close and open the window to view any changes you applied. |
Use one of the following methods to assign symbolic link names:
The Oracle Cluster Setup Wizard assists with cluster creation and the addition of nodes to an existing cluster. It also enables you to assign symbolic link names to logical drives. Refer to "Task 3: Creating a Cluster" to create symbolic link names and create a cluster using Oracle Cluster Setup Wizard.
Object Link Manager is a graphical user interface (GUI) tool that assigns symbolic link names or renames existing symbolic link names.
|
See Also: "Installing the Raw Devices Management Utilities Manually" to install Oracle Object Link Manager |
Select c:\temp\GUIOracleOBJManager.exe, where temp is the temporary directory defined in step 2 of the "Installing the Raw Devices Management Utilities Manually" section.
The Oracle Object Manager window displays.
Select the row to update and click any point within the highlighted row.
An edit window, with an active blinking cursor, opens in the New Link Name column.
Enter the new link name and click Enter.
Repeat steps 2 and 3 to create additional symbolic link names.
|
Note: Do not proceed to step 5 if the edit window is active. Changes will not apply. |
Select Options > Commit.
The ImportSYMLinks utility is a command line tool that assigns symbolic link names or renames existing symbolic link names.
|
See Also: "Installing the Raw Devices Management Utilities Manually" to install theImportSYMLinks utility |
Create a TBL file.
| Task | Procedure |
|---|---|
| Modify an existing symbolic link name | Export existing links to a TBL file using the following command:
ExportSYMLinks.exe /f:filename If |
Create a TBL file |
A sample ASCII file is located in the following directory on the first component CD-ROM:Foot 1
\preinstall_rac\olm\sample.tbl
|
Use the following command to import symbolic link mappings:
ImportSYMLinks.exe /f:filename
For example,
ImportSYMLinks.exe \f:c:\temp\mysymlinks.tbl
where temp is the temporary directory defined in step 2 of the "Installing the Raw Devices Management Utilities Manually" section and filename is the full path and filename of the valid TBL file.
If you intend to use Oracle9i operating system dependent clusterware, use the Oracle Cluster Setup Wizard to install the clusterware, assign symbolic links, and create a cluster. If you intend to use vendor operating system dependent clusterware, refer to your vendor documentation.
If you intend to use vendor operating system dependent clusterware instead of Oracle9i operating system dependent clusterware, you do not need to run the Oracle Cluster Setup Wizard. However, the raw device management utilities are required to configure a raw device before the Oracle Universal Installer is invoked. You must temporarily install the raw device management utilities.
Run the Oracle Cluster Setup Wizard on a node that is to become a node in the cluster. Running the wizard from a node that will not become a node in the cluster is not supported. To add a node to an existing cluster, run the Oracle Cluster Setup Wizard from the CD-ROM at any time.
|
See Also: Oracle9i Real Application Clusters Administration for more information about adding a node at the clusterware layer on a Windows platform |
Ensure all the nodes to be part of the cluster are up and can communicate with each other in a TCP/IP environment
Ensure you have 2 MB available on each node to install the Oracle operating system dependent clusterware and Object Link Manager
Stop the vendor operating system dependent clusterware. This only applies if you plan to install the Oracle operating system dependent clusterware, and have a version of your vendor operating system dependent clusterware running.
|
Note: Oracle Corporation recommends using the same username and password on each node in a cluster, or a domain username. You must have administrative privileges and each node must be in the same domain. |
To verify administrative privileges, from the node on which the Oracle Cluster Setup Wizard runs, enter the following for each node in the cluster:
NET USE \\host_name\C$
where host_name is the public network name for the other node.
For example, if you run the Oracle Cluster Setup Wizard on node1 and plan to create a four-node cluster with node1, node2, node3, and node4, enter the following commands on node1:
NET USE \\node2\C$ NET USE \\node3\C$ NET USE \\node4\C$
When the command completes successfully, you have administrative privileges on each node.
To create a cluster:
Insert the first component CD-ROM on one node of the cluster, and go to the \preinstall_rac\clustersetup directory.
Select clustersetup.exe to launch the Oracle Cluster Setup Wizard.
Click Next.
Choose to Create a cluster, then click Next to display the Disk Configuration screen.
Optionally, perform one of the ftasks listed in Table 2-5 to rename or add a symbolic link:
Table 2-5 Symbolic Link Tasks
| Task | Procedure |
|---|---|
| Rename a symbolic link |
|
| Create a symbolic link |
|
Assign a Voting disk, labeled as srvcfg, by highlighting the corresponding row.
Click Next.
Choose Create a cluster and click Next, to display the Network Selection window.
Select Use private network for interconnect if the nodes are connected by a high speed private network. Otherwise, select Use public network for interconnect and click Next to display the Network Configuration window.
Enter the names of the nodes and click Next.
Enter the public and private names for the nodes if private network was chosen in step 9 of this section
Enter the public names if public network was chosen in step 9 of this section
The VIA Detection window displays if VIA is detected on the local node. Go to step 11. Otherwise, go to step 12.
Chose whether or not to use VIA for the clusterware interconnect. After making your selection, click Next to display the Install Location window.
Choose an installation location and click Next.
A progress window displays the various actions performed by Oracle Cluster Setup Wizard.
|
See Also: Oracle Cluster Setup Wizard online Help |
Additional disk management utilities, listed in Table 2-6, are installed by the Oracle Cluster Setup Wizard on all nodes. These utilities are not installed if you do not run Oracle Cluster Setup Wizard.
Table 2-6 Raw Devices Disk Management Utilities
| Utility | Task |
|---|---|
| Object Link Manager | A graphical user interface (GUI) tool that creates or modifies symbolic links to logical drives. This utility can be used as part of the Oracle Cluster Setup Wizard, or separately. |
DeleteDisk |
Reformats an entire disk and deletes its contents. |
LetterDelete |
Removes all drive letters from Oracle raw partitions and updates the disk key registry to disable mappings when you restart your computer. |
LogPartFormat |
Initializes all space in a logical partition to zero and removes the symbolic link name. |
crlogdr |
Creates and deletes logical drives and their associated symbolic names on a disk that does not have a primary partition and one extended partition. Use this tool to review the disk layout. |
ExportSYMLinks |
Reads persistent symbolic links from their respective disk drives and generates a TBL file of the list (named by default symmap.tbl). |
ImportSYMLinks |
Reads a TBL file and creates persistent symbolic links on the disks and on all nodes in the cluster. |
|
See Also:
|
If you did not install Oracle9i operating system dependent clusterware using the Oracle Cluster Setup Wizard, manually install the raw device management utilities.
To manually install the disk management utilities, perform the following tasks on each node of the cluster:
Create a temporary directory.
Copy the contents of the \preinstall_rac\olm directory from the first component CD-ROM to the temporary directory you created.
Install Oracle Object Service by entering the following command from the temporary directory you created:
C:\temp> OracleOBJService \INSTALL
|
Note: The Oracle Cluster Setup Wizard automatically creates and starts this service. |
Set the Oracle Object Service service on each node in the cluster to automatic. Refer to your Microsoft online help for more information about configuring, starting, and stopping services.
