| Oracle® Collaboration Suite Installation Guide 10g Release 1 (10.1.2) for Microsoft Windows Part Number B25463-03 |
|
|
View PDF |
| Oracle® Collaboration Suite Installation Guide 10g Release 1 (10.1.2) for Microsoft Windows Part Number B25463-03 |
|
|
View PDF |
Before installing Oracle Collaboration Suite, ensure that your computer meets the requirements described in this chapter.
This chapter contains the following sections:
Section 2.9, "Prerequisite Checks Performed by the Installer"
|
Note: To view updated certification information or to download a required patch, refer to the OracleMetaLink site atIf you have a support contract with Oracle, then the steps to download a patch from the OracleMetaLink site are:
|
This section lists the hardware configurations required to install Oracle Collaboration Suite.
Table 2-1 lists the system requirements for running Oracle Collaboration Suite.
Table 2-1 Hardware Requirements for Windows Systems
| Item | Minimum Requirement | Checked by Installer |
|---|---|---|
| Processor Speed | 300 MHz or higher Intel Pentium processor recommended.
To determine the processor speed, right-click the My Computer icon on the Desktop and select Properties. Select General, if required. |
No |
| Network | You can install Oracle Collaboration Suite on a computer that is connected to a network, or on a standalone computer that is not connected to the network.
If you are installing Oracle Collaboration Suite on a standalone computer, you can connect the computer to a network after installation. You must perform some configuration tasks when you connect it to the network; refer to the Oracle Collaboration Suite Administrator's Guide for details. |
No |
| IP | The IP address of a computer can either be static or dynamic (DHCP-based).
Note: It is recommended that you install Oracle Collaboration Suite Identity Management, Oracle Collaboration Suite Database, and Application tiers on systems with static IP addresses. If you are installing on DHCP computers, refer to Section 2.8.1 for additional requirements. If you are installing on static IP computers and you want to be able to run Oracle Collaboration Suite on or off the network, refer to Section 2.8.5 for additional requirements. |
No |
| Host name | Ensure that your host names are not longer than 255 characters. | No |
| Memory | The installer checks the amount of memory on your computer and will not let you proceed if your computer does not meet the following minimum memory requirements:
Oracle Collaboration Suite 10g Infrastructure: 1 gigabyte (GB) Oracle Collaboration Suite 10g Applications: 1 GB Oracle Collaboration Suite 10g Database: 1 GB Note: For Oracle Collaboration Suite Infrastructure and Applications installation on a single computer installation, 2 GB or more is recommended. If warning messages and popup windows appear after the single-computer installation is completed, then refer to Section K.4.18 for more information on how to resolve this problem. These values assume you are running only one Oracle Collaboration Suite instance for each computer. The memory requirements provided for the various installation types represents enough physical memory to install and run Oracle Collaboration Suite. However, for most production sites, you should configure at least 3 GB of physical memory. For sites with substantial traffic, increasing the amount of memory further may improve your performance. To determine the optimal amount of memory for your installation, you should load test your site. Resource requirements can vary substantially for different applications and different usage patterns. In addition, some operating system utilities for monitoring memory can overstate memory usage (partially because of the representation of shared memory). The preferred method for determining memory requirements is to monitor the improvement in performance resulting from the addition of physical memory in the load test. Refer to your platform vendor documentation for information on how to configure memory and processor resources for testing purposes. |
Yes |
| Disk space | The installer may display inaccurate disk space requirement figures. The disk space requirements are:
Oracle Collaboration Suite 10g Infrastructure: 8 GB Oracle Collaboration Suite 10g Applications: 5 GB Oracle Collaboration Suite 10g Database: 5.4 GB |
No |
Space in TEMP directory |
256 MB
If the |
Yes |
| Monitor | 256-color display | Yes |
| Total Pagefile size (Virtual Memory) | These values are estimates. You should use the values recommended by Windows based on the amount of memory on your computer.
If you plan to use Clusters, Oracle recommends a minimum of 1 GB. In a production environment, Oracle recommends a minimum of 1 GB. To view and change the total pagefile size (virtual memory): Windows 2000:
Windows 2003:
|
Yes |
| File system type | NTFS is recommended over FAT32 or FAT file system types because NTFS includes security features such as enforcing permission restrictions on files. | No |
The Oracle Real-Time Collaboration components perform load balancing as they handle communications between clients and servers. The Redirector determines which multiplexer or communication manager processes are available as it routes requests from clients. The multiplexer determines which Web Conferencing Server processes are available as it routes communications from and to the Web Conferencing clients.
You may also choose to use a Load Balancer to manage processes handled by your Oracle middle-tier servers. If so, then keep these considerations in mind:
All systems behind the load balancer should have intranet-routable IP addresses and must be directly accessible from the Internet at least on the standard HTTP and HTTPS ports (80 and 443).
If you use geographic load balancers – that is, load balancers to separate loads between geographic locations – then you must create Oracle Real-Time Collaboration clusters to partition the system based on geographical distribution.
|
Note: Oracle Messenger also uses ports 5222 and 5223 which in some cases must be open to the Internet. |
To reduce memory consumption:
Configure only the components that you need.
After installation, start only the components that you need. Refer to the Oracle Collaboration Suite Administrator's Guide for details.
Choose the smallest Applications tier type that contains the components that you need.
Run Application Server Control only when you need to administer an instance. In most cases, you do not need Application Server Control running all the time.
If you are running multiple Oracle Collaboration Suite Infrastructure instances on one computer, each Application Server Control can consume a lot of memory. Running Application Server Control only when you need it can free up memory for other components.
Configure Application Server Control so that it can manage multiple instances. Refer to the Oracle Collaboration Suite Administrator's Guide for details.
You must keep the following hardware requirements in mind while installing Oracle Real-Time Collaboration:
There are a number of hardware sizing considerations for Oracle Real-Time Collaboration. Refer to the Oracle Collaboration Suite Concepts and Deployment Guide for detailed information about these considerations.
This section provides information about the hardware required for the Voice Conversion Server used by Oracle Real-Time Collaboration 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 Service Pack 4 (SP4) or later, with the following basic configuration:
2.4 Gigahertz (GHz) Intel Processor
512 Megabyte (MB) Synchronous Dynamic Random Access Memory (SDRAM)
20 Gigabyte (GB) disk
You also need specialized telephony hardware to install Oracle Real-Time Collaboration. You need a T1 or E1 trunk, and a media processing board from Intel or Dialogic to support the trunk. The T1/E1 protocol supported by Oracle Real-Time Collaboration is robbed-bit /CAS (Channel Associated Signaling).
Table 2-2 and Table 2-3 list the 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 for each 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 | E1 Lines | Voice Servers | Dialogic Hardware Needed for each 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 Collaboration Suite Concepts and Deployment Guide for specific information on sizing requirements for your system |
The Oracle Real-Time Collaboration components perform load balancing as they handle communications between clients and servers. The Redirector determines which multiplexer or communication manager processes are available as it routes requests from clients. On the other hand, the multiplexer determines which Web Conferencing Server processes are available as it routes communications from and to the Web Conferencing clients.
You might also use a Load Balancer to manage processes handled by your Oracle Applications tier servers. If so, then keep the following considerations in mind:
All systems behind the load balancer should have intranet-routable Internet protocol (IP) addresses and must be directly accessible from the Internet at least on the standard HTTP and HTTPS ports (80 and 443).
If you use geographic load balancers, the load balancers for separating loads between geographic locations, then you must create Oracle Real-Time Collaboration clusters to partition the system based on geographical distribution.
|
Note: Oracle Messenger also uses ports 5222 and 5223, which in some cases must be open to the Internet. |
The typical hardware required for installing Oracle Voicemail & Fax is as follows:
Dell PowerEdge 2850 or similar with the following:
Dual Central Processing Unit (CPU)
4 GB or more of RAM
Microsoft Windows 2000 Server with Service Pack 4 (SP4)
|
Note: Except for Microsoft Windows 2000 Server, no other operating system version is supported for Oracle Voicemail & Fax. |
Telephony card that works with NetMerge CCS software from Intel
|
Note: In place of a telephony card, you can also use the Intel NetStructure HMP software with NetMerge CCS.For more information about Intel NetStructure HMP and NetMerge CCS, refer to |
The installer also checks that your computer contains the required operating system patches. If it determines that some required patches are missing, it displays an error.
Microsoft Windows 2000 requires Service Pack 3 or later.
Microsoft Windows Server 2003 (32-bit) with Service Pack
|
Note: The 32-bit version of Oracle Collaboration Suite for Windows runs on Intel x86, AMD64, and Intel EM64T processors. For additional information, visit OracleMetaLink at:The following 64-bit operating systems are supported:
|
In addition to the software requirements for the computer, you must have a compatible browser.
The following browsers are supported:
Microsoft Internet Explorer 5.5, 6.0 and later
Netscape 7.1, 7.2 and later
Mozilla 1.5 and later. You can download Mozilla from
Note that Firefox, the standalone Mozilla browser, is not certified at the time of publication.
Safari 1.2 on Apple Macintosh computers
|
Note: For the most current list of supported operating system-specific software, operating system version, and certified browsers, check OracleMetaLink at |
|
Note: Oracle Collaboration Suite Infrastructure is not supported on Windows operating systems that include Terminal Services (for example, Windows 2000 with Terminal Services is not supported). |
Oracle Real-Time Collaboration uses a Document Conversion Server to convert Microsoft Office documents into HTML or other compatible formats for sharing during conferences. The server must either Microsoft Windows NT or Microsoft Office 2000 installed on it.
Oracle Real-Time Collaboration also uses a Voice Conversion Server to support streaming of voice data during conferences or playback of recorded conferences with voice data. The server requires Microsoft Windows 2000 Server SP4 or later, and Intel Dialogic System Software 5.1.1 SP1 or later.
Table 2-4 describes the software requirements for installing Oracle Voicemail & Fax.
Table 2-4 Software Requirements for Oracle Voicemail & Fax
| Requirement | Description |
|---|---|
| Oracle Management Agent | Ensure that the Oracle Management Agent is properly configured and running before you start the installation.
Refer to Oracle Enterprise Manager Advanced Configuration Guide for more information. |
| NetMerge CSS | NetMerge CCS is third-party software from Intel.
You might want to refer to Administrator's Guide for Intel NetMerge CCS 3.0. installed in the For more information, contact the reseller from whom you purchased the software. Note: When you install NetMerge CCS, you must set the locale to English because NetMerge is only supported in English. After NetMerge CCS is installed, the system administrator can change the locale setting on the computer, if you want the text on the Oracle Voicemail & Fax installation screens to appear in a different language. |
| Oracle Mail | An instance of Oracle Mail must be configured and registered against the instance of Oracle Internet Directory that you want to associate with the current installation. This instance of Oracle Mail may or may not be configured on the same computer. |
|
Important: In addition to the requirements mentioned, both Oracle Real-Time Collaboration and Oracle Voicemail & Fax require that an instance of Oracle Collaboration Suite Infrastructure be installed before starting the installation. The Infrastructure must have an associated Oracle Internet Directory. |
|
Note: Perform this procedure only if prompted by the installer. |
Oracle Collaboration Suite requires minimum versions of some system files in the Windows system directory (typically Drive_Letter:\Windows\system32 or Drive_Letter:\Winnt\system32).When you enter the installer to install Oracle Collaboration Suite, the installer checks the Windows system files on your computer. If it finds that these files that are not up-to-date, it prompts you to exit the installer and run wsf.exe to install the latest Windows system files. You can find wsf.exe in the same directory as the installer.
To run wsf.exe:
Start wsf.exe, which starts up Oracle Universal Installer to install the Windows system files.
DVD-ROM (assumes E: is the DVD-ROM drive):
E:\> cd collaboration_suite E:\> wsf.exe
Follow the screens in the installer:
Table 2-5 Screens for Installing Windows System Files
| Screen | Action |
|---|---|
| Welcome | Click Next. |
| Specify File Locations | Destination Name: Enter a name for the Oracle home for wsf.
Destination Path: Enter any full path. The installer installs the files in the proper system directories, regardless of the value you enter in this field. Click Next. |
| Warning: System Reboot Required | If you refer to this screen, you must restart your computer after installing Windows system files. If you do not refer to this screen, you do not must restart your computer.
Click Next. |
| Summary | Click Next to start installing the Windows system files. |
| End of Install | Click Exit to exit the installer. |
If the installer displayed the "Warning: System Reboot Required" screen, restart your computer.
Components of Oracle Collaboration Suite Infrastructure (such as Oracle HTTP Server, OracleAS Web Cache, and Oracle Enterprise Manager) and Oracle Collaboration Suite Applications use ports. You can have the installer assign default port numbers, or use port numbers that you specify, including the port numbers under 1024.
This section contains the following topics:
Section 2.4.4, "Using Custom Port Numbers (the "Static Ports" File)"
Section 2.4.5, "Ports for Oracle HTTP Server and OracleAS Web Cache"
An ephemeral port is a port number that an operating system can temporarily assign to a service or process. Some services or processes have conventionally assigned permanent port numbers. In other cases, an ephemeral port number is assigned temporarily (for the duration of the request and its completion) from a range of assigned port numbers.
Problem: Components Cannot Start Because of Conflicts with Ephemeral Ports
On rare occasions, Oracle Collaboration Suite processes are unable to start because required ports are not available. Processes may fail to start or report that they are unable to bind to ports. The behavior may be transient in that if you try to restart the affected process later, it does start successfully.
The cause of this problem is that by default, Oracle Collaboration Suite uses a number of ports that fall in to the range of ephemeral ports. Ephemeral ports are usually used on the client ends of client/server TCP/IP connections. Because client processes usually are unconcerned with which port value is used on the client side of the connection, all TCP/IP implementations enable clients to defer to the operating system the choice of which port value to use for the client side. The operating system selects a port from the ephemeral port range for each client connection of this type.
On the other hand, server processes (for example, Oracle Collaboration Suite processes) cannot use ephemeral ports. They must use fixed port values so that clients can always connect to the same server port to communicate with the server.
Port conflicts with ephemeral ports arise when an Oracle Collaboration Suite process is configured to use a port in the ephemeral port range. The Oracle Collaboration Suite process tries to start, but discovers that the port that it needs is already in use by a client process (the client received the ephemeral port assignment from the operating system). This client can be any process on the computer capable of communicating through TCP/IP. The Oracle Collaboration Suite process fails to start when the port that it needs is unavailable.
This problem occurs relatively more frequently on Microsoft Windows than on other operating systems because by default Windows uses a small range of ports for ephemeral client connections.
Ephemeral Port Range
The ephemeral port range on Microsoft Windows is ports 1024 through 5000, inclusive.
Only the upper end of this range is adjustable in Windows. In most other operating systems, the ephemeral range by default is much larger, and the lower and upper bounds of the range are adjustable.
Several Oracle Collaboration Suite processes, including Oracle HTTP Server, OracleAS Web Cache, Oracle Enterprise Manager Application Server Control, and OC4J, use ports in the ephemeral port range. These processes cannot start if the ports that they need are already in use by clients.
How to Avoid Conflicts with Ephemeral Ports
To avoid conflicts with ephemeral ports, you have these options:
Install Oracle Collaboration Suite using staticports.ini so that Oracle Collaboration Suite components do not use ports within the ephemeral range. In the staticports.ini file, use port numbers below 1024 or above 5000.
Refer to Section 2.4.4 for details.
If you have already installed Oracle Collaboration Suite, you can reconfigure the components to use ports below 1024 or above 5000. Refer to the Oracle Collaboration Suite Administrator's Guide to learn how to change the current ports used by Application Server processes.
This option can be done postinstallation. Modify the ephemeral port range on your computer. Use this option only if you cannot use any of the alternatives mentioned earlier. This option is the least preferred because it makes changes to the Windows registry, and it affects all products that you run on your computer.
This option moves the ephemeral port range to a new location. Before making the change, you must verify that none of the products you are using (Oracle or non-Oracle) on your computer use nonephemeral ports within the ephemeral port range. If any products do so, you must relocate them to the new ReservedPorts range, above the new ephemeral range, or below port 1024.
To implement this option, perform these steps:
Raise the upper bound of the ephemeral port range to expand the size of the range.
Set the MaxUserPort value in the registry to at least 13000, but no later than 65534. MaxUserPort is the upper bound of the ephemeral port range.
For steps, refer to Microsoft Knowledge Base article 196271: http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;196271.
Reserve a portion of the newly expanded ephemeral port range for use by Oracle Collaboration Suite.
Set the ReservedPorts value in the registry so that ports 1024 through 8000 are reserved for Oracle Collaboration Suite. The reserved range incorporates the range of ports normally used by Oracle Collaboration Suite.
For steps, refer to Microsoft Knowledge Base article 812873: http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;812873.
Restart your computer for the changes to take effect.
After performing the steps, you end up with the following: ports from 1024 through 8000 are reserved for Oracle Collaboration Suite, and ports 8001 through 13000 are the new ephemeral port range (assuming you set the MaxUserPort to 13000). The reserved range incorporates the range of ports normally used by Oracle Collaboration Suite, and the ephemeral range has the same size as the original.
To check if a port is being used, you can enter the netstat command to show the used port as follows:
Drive_Letter:\> netstat -an | find "port_num"
In the preceding syntax, port_num refers to the port number you want to check.
Note that you need double-quotes around the port number.
To use the default port numbers for components such as Oracle HTTP Server, OracleAS Web Cache, and Oracle Enterprise Manager, you do not have to do anything. Refer to Appendix I for a list of default port numbers that the installer will assign to components.
Note the following points:
The installer assigns the default ports to components only if the ports are not in use by other applications. If the default port is in use, the installer tries other ports in the port number range for the component. For example, the default non-SSL port for Oracle HTTP Server for the Applications tier is port 80. If this port is in use by another application, the installer assigns a port in the 7777 - 7877 range.
The default ports for Oracle HTTP Server depend on the installation type (Table 2-6).
In Table 2-6, the values in parenthesis indicate the ports that the installer will try to assign to Oracle HTTP Server if the default port is already in use.
The installer no longer checks the services file to determine if a port is in use. In earlier releases, the installer would not assign a port number if the port number is listed in the file.
The services file is located in the Drive_Letter:\%SystemRoot%\system32\drivers\etc directory, where %SystemRoot% is winnt on Windows 2000, and windows on Windows 2003.
If You Plan to Install Oracle Collaboration Suite Infrastructure and Oracle Collaboration Suite Applications on the Same Computer
If you plan to install multiple instances (such as an Oracle Collaboration Suite Infrastructure and an Applications tier, or multiple Applications tiers) on the same computer, only the first instance that you install on the computer will use the default ports. When you install additional instances, the installer will detect that the default ports are already in use by the first instance, and it will assign other ports to the additional instances.
The components where this is most visible are Oracle HTTP Server and OracleAS Web Cache, as shown in the following scenarios:
Table 2-7 Oracle HTTP Server Ports in Different Scenarios
| Scenario | Non-SSL Port | SSL Port |
|---|---|---|
| Oracle Collaboration Suite Infrastructure and a Applications tier installed on the same computer. | Oracle HTTP Server on the Oracle Collaboration Suite Infrastructure: 7777
Oracle HTTP Server on the Applications tier: 80 |
Oracle HTTP Server on the Oracle Collaboration Suite Infrastructure: 4443
Oracle HTTP Server on the Applications tier: 443 |
| Two Applications tiers installed on the same computer. | Oracle HTTP Server on the first Applications tier: 80
Oracle HTTP Server on the second Applications tier: 7777 |
Oracle HTTP Server on the first Applications tier: 443
Oracle HTTP Server on the second Applications tier: 4443 |
Instead of using default ports, you can assign custom port numbers for Oracle Collaboration Suite Applications components during the installation. For this, you must create a file containing the component names and port numbers. Section 2.4.4.1 describes the file format. This file is typically called the staticports.ini file, but you can name it anything you want.
|
Note: The default listener port 1521 cannot be changed to any custom port. |
To instruct the installer to assign custom port numbers for Applications tier components, you must specify the path to staticports.ini as a parameter to the setup.exe command as follows:
setup.exe oracle.ocs.midtier:s_staticPorts=path_to_your_ini_file (for installing Oracle Collaboration Suite 10g Applications) setup.exe oracle.ocs.onebox:s_staticPorts=path_to_your_ini_file (for installing Oracle Collaboration Suite 10g Applications and Infrastructure)
If you do not specify the full path to the file, the installer cannot find the file. The installer will then assign default ports for all the components, and it will do this without displaying any warning.
|
Note: If you specify custom port numbers using thestaticports.ini file, then the installer will not show the Specify Ports Configuration Options screen.
In this case, the installer attempts to use the ports that you specified in the It is recommended that you always check the |
The staticports.ini file has the following format. Replace port_num with the port number that you want to use for the component.
# staticports.ini Template File # This file is a template for specifying port numbers at installation time. # To specify a port number, uncomment the appropriate line (remove #) and # replace "port_num" with the desired port number. # You can then launch Oracle Universal Installer with special options to use this # file. # Please refer to Oracle Collaboration Suite 10.1.2 Installation Guide for # instructions. # Ports common to Infrastructure and Applications install # Oracle HTTP Server port = port_num # Oracle HTTP Server Listen port = port_num # Oracle HTTP Server SSL port = port_num # Oracle HTTP Server Listen (SSL) port = port_num # Oracle HTTP Server Diagnostic port = port_num # ASG port = port_num # Application Server Control port = port_num # Application Server Control RMI port = port_num # Java Object Cache port = port_num # Log Loader port = port_num # DCM Discovery port = port_num # Oracle Notification Server Request port = port_num # Oracle Notification Server Local port = port_num # Oracle Notification Server Remote port = port_num # Oracle Management Agent port = port_num # Ports specific to Infrastructure install # Oracle Internet Directory port = port_num # Oracle Internet Directory (SSL) port = port_num # Enterprise Manager Console HTTP port = port_num # Enterprise Manager Agent port = port_num # Ports specific to Applications install # Web Cache HTTP Listen port = port_num # Web Cache HTTP Listen (SSL) port = port_num # Web Cache HTTP Administration port = port_num # Web Cache Invalidation port = port_num # Web Cache Statistics port = port_num # Oracle Net Listener = port_num # Oracle Mail IMAP4 port = port_num # Oracle Mail IMAP4 Secure port = port_num # Oracle Mail POP3 port = port_num # Oracle Mail POP3 Secure port = port_num # Oracle Mail SMTP port = port_num # Oracle Mail NNTP port = port_num # Oracle Mail NNTP Secure port = port_num # Oracle Calendar server = port_num # Oracle Calendar server manager (CSM) = port_num # Wireless PIM Notification Dispatcher = port_num # Wireless PIMAP UDC Dispatcher = port_num # RTC Redirector Server port= port_num # RTC Redirector MX port= port_num # RTC Redirector XMPP port= port_num # RTC Redirector Secure XMPP port= port_num # RTC process monitor port = port_num # RTC messenger director server first port = port_num # RTC messenger director server second port = port_num # RTC messenger multiuser chat port = port_num # RTC messenger connection manager port = port_num # RTC messenger statistics collection port = port_num # RTC messenger server to server connection port = port_num # RTC messenger group service port = port_num # RTC messenger voice proxy port = port_num
|
Note: If you plan to install Oracle Collaboration Suite Infrastructure and Oracle Collaboration Suite Applications on a single computer, then you must use thestaticports.ini.onebox template. |
The easiest way to create the file is to use the staticports.ini file on the DVD as a template:
Copy the staticports.ini file from the DVD to your hard disk.
Table 2-8 specifies the location of the staticports.ini file on DVD.
Edit the local copy (the file on the hard disk) to include the desired port numbers.
You do not specify port numbers for all components in the staticports.ini file. If a component is not listed in the file, then the installer uses the default port number for that component.
You cannot change the port used by the Infrastructure Database listener (port 1521) during installation, but you can do so after installation.
The following example sets the Application Server Control port and some ports for the Web Cache. For components not specified, the installer will assign the default port numbers.
Application Server Control port = 2000 Web Cache Administration port = 2001 Web Cache Invalidation port = 2002 Web Cache Statistics port = 2003
When installation is complete, you can check the ORACLE_HOME\install\portlist.ini file to refer to the assigned ports.
|
Notes on Choosing Port Numbers:
|
The installer verifies that the ports specified in the file are available by checking memory. This means that it can only detect ports that are being used by running processes. It does not look in configuration files to determine which ports an application is using.
If the installer detects that a specified port is not available, it displays an alert. The installer will not assign a port that is not available. To fix this:
Edit the staticports.ini file to specify a different port, or shut down the application that is using the port.
Click Retry. The installer rereads the staticports.ini file and verifies the entries in the file again.
|
Tip: Thestaticports.ini file uses the same format as the ORACLE_HOME\install\portlist.ini file, which is created after an Oracle Collaboration Suite installation. If you have installed Oracle Collaboration Suite and you want to use the same port numbers in another installation, you can use the portlist.ini file from the first installation as the staticports.ini file for subsequent installations. |
Check your staticports.ini file carefully, because a mistake can cause the installer to use default ports without displaying any warning. Here are some things that you should check:
If you specify the same port for more than one component, the installer will use the specified port for the first component, but for the other components, it will use the default ports of the components. The installer does not warn you if you have specified the same port for multiple components.
If you specify different ports for one component on multiple lines, the installer assigns the default port for the component. The installer does not warn you if you have specified different ports for one component.
If you have syntax errors in the staticports.ini file (for example, if you omitted the = character for a line), the installer ignores the line. For the components specified on such lines, the installer assigns the default ports. The installer does not display a warning for lines with syntax errors.
If you misspell a component name, the installer assigns the default port for the component. Names of components in the file are case-sensitive. The installer does not display a warning for lines with unrecognized names.
If you specify a nonnumeric value for the port number, the installer ignores the line and assigns the default port number for the component. It does this without displaying any warning.
If you misspell the parameter on the command line, the installer does not display a warning. It continues and assigns default ports to all components.
If you specify a relative path to the staticports.ini file (for example, .\staticports.ini or just staticports.ini) on the command line, the installer will not find the file. The installer continues without displaying a warning and it will assign default ports to all components. You must specify a full path to the staticports.ini file.
If the parameter you specify on the command line does not match the type of installation that you are performing (for example, if you specify the parameter for Applications but you are installing the Infrastructure), the installer does not give a warning. It continues and assigns default ports to all components.
Be sure you understand the following when setting ports for these components.
In the httpd.conf file for Oracle HTTP Server, the Port and the Listen directives specify the ports used by OracleAS Web Cache and Oracle HTTP Server. The correct lines in the staticports.ini file for setting these ports depend on which components you are configuring.
If You Are Configuring OracleAS Web Cache and Oracle HTTP Server
If You Are Configuring OracleAS Web Cache and Oracle HTTP Server, as shown in Figure 2-1, then you must perform the following tasks:
Set the port for OracleAS Web Cache.
OracleAS Web Cache uses the port specified by the Port directive. To set this port, use this line in the staticports.ini file:
Web Cache HTTP Listen port = port_number
To configure the SSL port for OracleAS Web Cache, use the following line:
Web Cache HTTP Listen (SSL) port = port_number
You cannot set the port number using the Oracle HTTP Server port line in this case. If your staticports.ini file contains both Oracle HTTP Server port and Web Cache HTTP Listen port, the Oracle HTTP Server port line is ignored. For example, the Port directive would be set to 7979, if you had the following lines in staticports.ini:
Web Cache HTTP Listen port = 7979 Oracle HTTP Server port = 8080
Set the port for Oracle HTTP Server.
Oracle HTTP Server uses the port specified by the Listen directive. To set this port, use this line in the staticports.ini file:
Oracle HTTP Server Listen port = port_number
To configure the SSL Listen port, use the following line:
Oracle HTTP Server Listen (SSL) port = port_number
Figure 2-1 Configuring Both OracleAS Web Cache and Oracle HTTP Server
If You Are Configuring Oracle HTTP Server Only (no OracleAS Web Cache)
If you are configuring Oracle HTTP Server only, then Oracle HTTP Server uses both Port and Listen directives, as shown in Figure 2-2, then you must set both directives to use the same port number.
To set these ports, use the "Oracle HTTP Server port" and "Oracle HTTP Server Listen port" lines in the staticports.ini file. For example:
Oracle HTTP Server port = 8080 Oracle HTTP Server Listen port = 8080
To set the SSL version of these ports, use the following lines. As in the non-SSL version, the port numbers must be the same.
Oracle HTTP Server SSL port = 443 Oracle HTTP Server Listen (SSL) port = 443
If you also specify the Web Cache lines in staticports.ini, they will be ignored because you are not configuring OracleAS Web Cache.
If port 1521 on your computer is already in use by an existing application, such as Oracle Database 10g listener or some other application, you might have to take some action before running the installer. Refer to the following sections for details:
If you are installing a new database for the Oracle Collaboration Suite Infrastructure on a computer that is already running an Oracle Database, ensure that the listeners for both databases do not conflict.
You might be able to use the same listener for both the existing Oracle Database and the Oracle Collaboration Suite Database. Consider the version of the existing listener as well as the port number. Table 2-9 shows the various scenarios and the respective outcomes.
You can change the Infrastructure listener to use a different port after installation. Refer to the Oracle Collaboration Suite Administrator's Guide for details.
Table 2-9 Scenarios and Outcomes While Installing Infrastructure on a Computer Already Having a Database
| Version of the Existing Listener | Existing Listener Uses Port 1521 | Existing Listener Uses a Port Other Than 1521 |
|---|---|---|
| Earlier than 10.1.0.2 | You need two listeners: one for the existing Database and one for the Oracle Collaboration Suite Infrastructure.
Refer to "Scenario 1: Existing Listener Uses Port 1521 and Listener Version Is Earlier Than 10.1.0.2". |
You need two listeners: one for the existing Database and one for the Oracle Collaboration Suite Infrastructure.
Refer to "Scenario 3: Existing Listener Uses a Port Other Than 1521" . |
| 10.1.0.2 or later | The existing listener supports both the existing Database and the Oracle Collaboration Suite Infrastructure.
Refer to "Scenario 2: Existing Listener Uses Port 1521 and Listener Version Is 10.1.0.2 or Later" . |
You need two listeners: one for the existing database and one for the Oracle Collaboration Suite Infrastructure.
Refer to "Scenario 3: Existing Listener Uses a Port Other Than 1521" Part . |
To check the listener version, enter the following command:
Drive_Letter:\> cd %ORACLE_HOME%\bin
Drive_Letter:\> lsnrctl version
In this command, ORACLE_HOME is the home directory for your database.
You can also use the same command to check the listener port.
C:\OraHome_1\BIN>lsnrctl VERSION LSNRCTL for 32-Bit Windows: Version 10.1.0.4.2 - Production on 18-AUG-2005 18:42:10 Copyright (c) 1991, 2004, Oracle. All rights reserved. Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=as-pc.oracle.com)(PORT=1521))) TNSLSNR for 32-Bit Windows: Version 10.1.0.4.2 - Production TNS for 32-Bit Windows: Version 10.1.0.4.2 - Production Oracle Bequeath NT Protocol Adapter for 32-Bit Windows: Version 10.1.0.4.2 - Production Windows NT Named Pipes NT Protocol Adapter for 32-Bit Windows: Version 10.1.0.4.2 - Production Windows NT TCP/IP NT Protocol Adapter for 32-Bit Windows: Version 10.1.0.4.2 - Production,, The command completed successfully
Scenario 1: Existing Listener Uses Port 1521 and Listener Version Is Earlier Than 10.1.0.2
Listeners earlier than version 10.1.0.2 are not compatible with the Infrastructure from this Oracle Collaboration Suite release (10.1.2). What you can do is to install Infrastructure, which installs a version 10.1.0.3 listener, and use this new listener for both databases.
Stop the existing listener before you install Infrastructure.
Drive_Letter:\> cd %ORACLE_HOME%\bin Drive_Letter:\> lsnrctl stop
ORACLE_HOME is the home directory for your existing database.
If you do not stop the existing listener, the installation will fail.
Install Infrastructure.
Update the configuration file of the new listener, as necessary. The name of the listener configuration file is listener.ora, located in the /network/admin%ORACLE_HOME%\network\admin directory.
Check network address entries in the configuration file of the existing listener.
Does the configuration file contain only the following network addresses?
TCP Port 1521
IPC key EXTPROC
If so, you do not have to edit the configuration file of the Infrastructure listener for network addresses.
If the configuration file contains other network addresses, you must add them to the configuration file of the Infrastructure listener.
|
Note: If your computer has a listener that uses theIPC protocol with the EXTPROC key, you should change the key to have someother value. This is because the OracleAS Metadata Repository listener requires access to the EXTPROC key. |
Check SID_DESC entries in the configuration file of the existing listener.
If the configuration file of the existing listener contains SID_DESC entries for the existing database, you must add these entries to the configuration file of the Infrastructure listener.
Do not start the existing listener (version earlier than 10.1.0.2). The new listener supports both databases, so you do not must run the existing listener.
|
Note: Step c in the preceding section is very important. You only must run one listener (the new listener) to support both databases. |
Scenario 2: Existing Listener Uses Port 1521 and Listener Version Is 10.1.0.2 or Later
The existing listener will support both the existing database and the Infrastructure. The installer will perform this configuration automatically. You do not have to do anything.
The existing listener must be stopped during installation.
Scenario 3: Existing Listener Uses a Port Other Than 1521
You will end up running two listeners: one for the existing database and one for the Infrastructure, regardless of the version of the existing listener.
The existing listener can be running during installation, because it is not using port 1521.
If another application is listening on port 1521, you must reconfigure it to listen on a different port. If that is not possible, shut it down while you install Oracle Collaboration Suite Database. After installation, you can reconfigure Oracle Collaboration Suite Database to use a port other than 1521. Refer to the Oracle Collaboration Suite Administrator's Guide for instructions.
The operating system user performing the installation must belong to the Administrators group. Perform the following steps to check if you belong to the Administrators group:
Display the Computer Management dialog box.
On Windows 2000: Right-click My Computer on the desktop and select Manage.
On the left side, expand Local Users and Groups, and select Users.
On the right side, right-click the user and select Properties. This displays the Properties dialog box.
In the Properties dialog box, select the Member Of tab.
If you are not a member of the Administrators group, get an administrator to add you to the group or log in as a user who is a member of the Administrators group.
The operating system user who installs Oracle Collaboration Suite must set or unset certain environment variables.
Table 2-10 summarizes whether you set or unset an environment variable.
Table 2-10 Environment Variables Summary
| Environment Variable | Set or Unset |
|---|---|
| ORACLE_HOME and ORACLE_SID |
Must not be set. |
| PATH |
Must not be longer than 1023 characters. |
| TEMP |
Optional. If unset, defaults to C:\temp. |
| TNS_ADMIN |
Must not be set. |
This section describes how to set environment variables in Windows:
Display the System control panel.
On Windows 2000: Select Start. Select Settings. Select Control Panel, and then select System.
Select the Advanced tab.
Click Environment Variables.
To change the value of a variable, select the variable and click Edit.
The PATH environment variable cannot be longer than 1023 characters. During the installation, Oracle Universal Installer checks the size of this variable and displays an error if it determines that (as a result of adding the Oracle Collaboration Suite path statements to) the existing PATH will cross this threshold.
When the installation process displays the error, you must modify the PATH statement and then restart the installation. Otherwise, the installation may fail.
Ensure that the TNS_ADMIN environment variable is not set when you enter the installer. If set, it can cause errors related to failure of Database Configuration Assistant (DBCA) during installation.
The installer uses a temporary directory for swap space. The installer checks for the TEMP environment variable to locate the temporary directory. By default, the installer uses the C:\temp directory.
If you want the installer to use a directory other than C:\temp, set TEMP to the full path of an alternate directory. The directory must meet the requirements listed in Section 2.1.
If you do not set this environment variable, and the default directory does not have enough space, then the installer displays an error message that says the environment variable is not set. You can either set the environment variable to point to a different directory or free up enough space in the default directory. In either case, you must restart the installation.
The contents of the %WINDIR%\system32\drivers\etc\hosts file affect the following:
The installer provides alternative methods for you to enter the values that you want without editing the hosts file as explained in Section 2.7.1 and Section 2.7.2.
|
Note: The host name specified in the hosts file may or may not be fully qualified. However, host names that are not fully qualified may not be usable outside the domain.For example, if the fully-qualified domain name for a server is |
%WINDIR% specifies the Windows operating system directory. Typically, it is C:\WINNT for Windows 2000.
C:\WINDOWS for Windows 2003
The installer reads the hosts file to construct the location of the default Identity Management realm. It displays this location in the "Specify Namespace in Internet Directory" screen.
The hosts file should use the following format:
ip_address fully_qualified_hostname short_hostname
Example:
123.45.67.89 primaryHost.mydomain.com primaryHost
In the preceding example, the location of the default Identity Management realm would display as "dc=mydomain,dc=com".
If the file uses a different format, the installer displays an incorrect value in the screen. For example, suppose the hosts file contains the following line:
123.45.67.89 primaryHost primaryHost.mydomain.com <--- incorrect format
Then the installer would display "dc=primaryHost,dc=com" as the default Identity Management realm. This is probably not the value that you want for the default Identity Management realm.
|
Note: If you need thehosts file to use a different format, you can edit the file to use the required format, perform the installation, then revert the file back to its original format after installation.
If you are unable, or unwilling, to edit the |
If you are installing Oracle Application Server Single Sign-On and your hosts file contains only the host name of your computer (without the domain name), then you will only be able to sign on to the OracleAS Single Sign-On server using the host name by itself (without the domain name).
To require a domain name when connecting to the OracleAS Single Sign-On server, you can edit the hosts file to include the domain name. If you do not want to edit the file, you can use the OUI_HOSTNAME command-line parameter to the installer to override the value in hosts. For example:
Drive_Letter:\> setup.exe OUI_HOSTNAME=myserver.mydomain.com
Typically, the computer on which you want to install Oracle Collaboration Suite is connected to the network, has local storage to contain the Oracle Collaboration Suite installation, has a display monitor, and has an appropriate disk drive.
This section describes how to install Oracle Collaboration Suite on computers that do not meet the typical scenario. It covers the following cases:
Section 2.8.1, "Installing Oracle Collaboration Suite on DHCP Computers"
Section 2.8.2, "Installing Oracle Collaboration Suite on Multihomed Computers"
Section 2.8.3, "Installing Oracle Collaboration Suite on Computers with Multiple Aliases"
Section 2.8.4, "Installing Oracle Collaboration Suite on Non-Networked Computers"
Section 2.8.7, "Copying the DVD to a Hard Drive and Installing from the Hard Drive"
Section 2.8.8, "Installing Oracle Collaboration Suite from a Remote DVD-ROM Drive"
Section 2.8.9, "Installing Oracle Collaboration Suite on Remote Computers"
Note this limitation when running Oracle Collaboration Suite on DHCP computers: Oracle Collaboration Suite instances on DHCP computers cannot communicate with other instances running on other computers. For example, you cannot have Infrastructure on one computer and an Applications tier on another computer if any one of those computers uses DHCP. All the instances that must communicate with each other must run on the same computer. There are no limitations on clients: clients from other computers can access the instances running on the DHCP computer, as long as the client computer can resolve the DHCP computer on the network.
Before installing Oracle Collaboration Suite on a DHCP computer, perform these steps:
Install a loopback adapter on the DHCP computer.
When you install a loopback adapter, the loopback adapter assigns a local IP for your computer. Having a loopback adapter and a local IP address means that you do not have to run the chgiphost script after installation each time the IP address changes (because of the use of DHCP).
Which Is the Primary Network Adapter?
Windows considers loopback adapters as a type of network adapter. After installing a loopback adapter on your computer, you have at least two network adapters on your computer: your network adapter and the loopback adapter.
You want Windows to use the loopback adapter as the primary adapter. The primary adapter is determined by the order in which you installed the adapters:
On Windows 2000, the primary adapter is the last adapter installed. You can just install the loopback adapter. However, if you install additional network adapters after you install the loopback adapter, you must deinstall the loopback adapter and reinstall it.
To install a loopback adapter on the different Windows platforms, refer to Section 2.8.6, "Installing a Loopback Adapter".
Ping each computer where you plan to install Oracle Collaboration Suite.
Ping the computer from itself, using the host name.
For example, if you installed a loopback adapter on a computer called mycomputer, check the following:
prompt> ping mycomputer Ping itself using just the hostname. Reply from 10.10.10.10 Returns loopback adapter IP.
Ping the computer from other computers on the network, using the host name.
In this case, the ping command returns the network IP of the computer.
prompt> ping mycomputer Ping using the hostname. Reply from 139.185.140.166 Returns network IP.
If ping fails, then consult your network administrator.
A multihomed computer is associated with multiple IP addresses. This is typically achieved by multiple network cards on the computer. Each IP address is associated with a host name; additionally you can set up aliases for the host name.
By default, Oracle Universal Installer uses the ORACLE_HOSTNAME environment variable setting to find the host name. If ORACLE_HOSTNAME is not set and you are installing on a computer that has multiple network cards, Oracle Universal Installer determines the host name by using the first name in the hosts file (typically located in DRIVE_ LETTER:\WINDOWS\system32\drivers\etc).
When you install Oracle Collaboration Suite on a multihomed computer, the installer configures Oracle Collaboration Suite to use the host name/IP address on the primary network adapter.Clients must be able to access the computer using this host name (or aliases for this host name). To check, ping the host name from the client computers using the short name (host name only) and the full name (hostname.domainname). Both must work.
To use a network adapter that is not the primary adapter, start up the installer with the OUI_HOSTNAME command-line parameter. Specify the host name that you want to use in the parameter. For example:
DVD (assumes E: is the DVD drive):E:\> setup.exe OUI_HOSTNAME=myserver.mydomain.com
A computer with multiple aliases refers to a computer registered with the naming service under a single IP but with multiple aliases. The naming service resolves any of those aliases to the same computer.
Before installing Oracle Collaboration Suite on such computers, you must:
Install a loopback adapter on the computer.
Ensure the loopback adapter is the primary network adapter.
The loopback adapter ensures that when Oracle Collaboration Suite queries for the host name, it always gets the same name (because the queries are done locally). Without the loopback adapter, the queries can return any of the aliases for the computer (because the queries get the response from the naming service).
To learn how Windows determines which adapter is the primary adapter, refer to "Which Is the Primary Network Adapter?".
For steps on how to install a loopback adapter, refer to Section 2.8.6.
You can install Oracle Collaboration Suite on a non-networked computer, such as a laptop. Because a non-networked computer has no access to other computers, you have to install all the components that you need on the computer. For instance:
|
Note: If you install an Applications tier that requires infrastructure services, you need to install both Oracle Collaboration Suite Infrastructure and Applications tier on the computer. Ensure your computer has enough resources to run both instances. See Section 2.1.2, "Tips for Reducing Memory Usage". |
Note that to install Oracle Collaboration Suite on a non-networked computer, the computer must have networking capabilities. Non-networked means that the computer is not connected to a network.
If you want to install Oracle Collaboration Suite on a non-networked computer, and you never want to connect the computer to a network after installation, ever, then you can just go ahead and install Oracle Collaboration Suite on your non-networked computer.
However, if you plan to connect the computer to a network after installation, perform these steps before you install Oracle Collaboration Suite on the non-networked computer.
Install a loopback adapter on the computer. See Section 2.8.6, "Installing a Loopback Adapter".
The loopback adapter and local IP address simulate a networked computer. If you connect the computer to the network, Oracle Collaboration Suite still uses the local IP and host name.
Ping the computer from itself, using only the host name and using the fully qualified name.
For example, if you installed a loopback adapter on a computer called mycomputer, check the following:
prompt> ping mycomputer Ping itself using just the hostname. Reply from 10.10.10.10 Returns loopback adapter IP. prompt> ping mycomputer.mydomain.com Ping using a fully qualified name. Reply from 10.10.10.10 Returns loopback adapter IP.
|
Note: When you ping a computer from itself, theping command should return the IP of the loopback adapter. |
If ping fails, then you need to talk with your network administrator.
Connecting the Computer to the Network After Installation
If you connect the computer to a network after installation, your Oracle Collaboration Suite instance on your computer can work with other instances on the network. Recall that you must have installed a loopback adapter on your computer. Your computer can use a static IP or DHCP, depending on the network to which you are connected.
If you plan to install Oracle Collaboration Suite on a networked computer with static IP and you want to be able to run Oracle Collaboration Suite when you disconnect the computer from the network, you must perform the following steps before installing Oracle Collaboration Suite:
Install a loopback adapter on your computer. Refer to Section 2.8.6 for details.
Without a loopback adapter, Oracle Collaboration Suite cannot function correctly when you disconnect the computer from the network because the static IP is no longer available.
Make sure the loopback adapter is the primary network adapter. Refer to "Which Is the Primary Network Adapter?". To check, ping the computer from itself using the host name.
For example, if you installed a loopback adapter on a computer called mycomputer, you can run these commands:
prompt> ping mycomputer Ping itself using just the hostname. Reply from 10.10.10.10 Returns loopback adapter IP. prompt> ping mycomputer.mydomain.com Ping using a fully qualified name. Reply from 10.10.10.10 Returns loopback adapter IP.
When you ping a computer from itself, the ping command should return the IP of the loopback adapter. It should not return the network IP of the computer.
These steps are required regardless of whether the computer is using static IP or DHCP. If this is a DHCP computer, you already know you need a loopback adapter; refer to Section 2.8.6.
When you disconnect the computer from the network, the computer has no access to any network resources. Make sure you have all the instances (for example, Infrastructure and Applications tier) you need on your computer.
A loopback adapter is required if you are installing Oracle Collaboration Suite on:
A DHCP computer (refer to Section 2.8.1)
A non-networked computer that might be connected to the network after the installation (refer to Section 2.8.4)
A computer with multiple aliases (refer to Section 2.8.3)
A networked computer (with static IP or DHCP), on which you want to be able to run Oracle Collaboration Suite when you take the computer off the network
The procedure for installing a loopback adapter depends on the version of Windows:
Section 2.8.6.1, "Checking If a Loopback Adapter Is Installed on Your Computer"
Section 2.8.6.2, "Installing a Loopback Adapter on Windows 2000"
Section 2.8.6.3, "Installing a Loopback Adapter on Windows 2003"
Section 2.8.6.5, "Removing a Loopback Adapter on Windows 2000 or Windows 2003"
To check if a loopback adapter is installed on your computer, run the "ipconfig /all" command:
prompt> ipconfig /all
If a loopback adapter is installed, a section that lists the values for the loopback adapter will be displayed. For example:
Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Loopback Adapter Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Autoconfiguration IP Address. . . : 169.254.25.129 Subnet Mask . . . . . . . . . . . : 255.255.0.0
Windows 2000 reports on the last network adapter installed. This means that if you install additional network adapters after you install the loopback adapter, you must remove and reinstall the loopback adapter. The loopback adapter must be the last network adapter installed on the computer.
To install a loopback adapter on Windows 2000:
Select Start. Select Settings. Select Control Panel.
Double-click Add/Remove Hardware. This starts up the Add/Remove Hardware Wizard.
On the Welcome page: Click Next.
On the Choose a Hardware Task page: Select Add/Troubleshoot a device, and click Next.
On the Choose a Hardware Device page: Select Add a new device, and click Next.
On the Find New Hardware page: Select No, I want to select the hardware from a list, and click Next.
On the Hardware Type page: Select Network adapters, and click Next.
On the Select Network Adapter page
Manufacturers: select Microsoft.
Network Adapter: select Microsoft Loopback Adapter.
Click Next.
On the Start Hardware Installation page: Click Next.
On the Completing the Add/Remove Hardware Wizard page: Click Finish.
Right-click My Network Places on the desktop and choose Properties. This displays the Network and Dial-up Connections control panel.
Right-click the connection that was just created. This is usually "Local Area Connection 2". Choose Properties.
On the General tab, select Internet Protocol (TCP/IP), and click Properties.
In the Properties dialog, enter the following values:
IP Address: Enter a nonroutable IP for the loopback adapter. The following nonroutable addresses are recommended:
192.168.x.x (x is any value between 1 and 255)
10.10.10.10
Subnet mask: Enter 255.255.255.0.
Leave all other fields empty.
Click OK.
Click OK in the Local Area Connection 2 Properties dialog.
Restart the computer.
Add a line to the C:\winnt\system32\drivers\etc\hosts file with the following format:
IP_address hostname.domainname hostname
This line should come after the localhost line in the file.
Replace IP_address with the nonroutable IP address you entered in Step 14.
Replace hostname and domainname with the appropriate values.
Example:
10.10.10.10 mycomputer.mydomain.com mycomputer
Check the network configuration:
Open the System control panel, and select the Network Identification tab. In Full computer name, make sure you refer to the host name and the domain name.
Click Properties. In Computer name, you should refer to the host name, and in Full computer name, you should refer to the host name and domain name.
Click More. In Primary DNS suffix of this computer, you should refer to the domain name.
Exit the System Control Panel.
To install a loopback adapter on Windows 2003:
From the Start menu, select Control Panel.
Double-click Add Hardware. This starts up the Add Hardware Wizard.
On the Welcome window, click Next.
On the Is the hardware connected? window, select Yes, I have already connected the hardware, and click Next.
On the The following hardware is already installed on your computer wincow, select Add a new hardware device, and click Next.
On the The wizard can help you install other hardware, select Install the hardware that I manually select from a list, and click Next.
On the From the list below, select the type of hardware you are installing window, select Network adapters, and click Next.
On the Select Network Adapter window, select the following:
Manufacturer: select Microsoft.
Network Adapter: select Microsoft Loopback Adapter.
Click Next.
On the The wizard is ready to install your hardware window, click Next.
On the Completing the Add Hardware Wizard window, click Finish.
If you are using Windows 2003, Restart your computer.
Right-click My Network Places on the desktop and choose Properties. This displays the Network Connections control panel.
Right-click the connection that was just created. This is usually called Local Area Connection 2. Choose Properties.
On the General tab, select Internet Protocol (TCP/IP), and click Properties.
In the Properties dialog, enter the following values:
IP Address: Enter a nonroutable IP for the loopback adapter. The following nonroutable addresses are recommended:
192.168.x.x (x is any value between 1 and 255)
10.10.10.10
Subnet mask: Enter 255.255.255.0.
Leave all other fields empty.
Click OK.
Click OK in the Local Area Connection 2 Properties dialog box.
Restart the computer.
Add a line to the C:\windows\system32\drivers\etc\hosts file with the following format:
IP_address hostname.domainname hostname
This line should come after the localhost line in the file.
Replace IP_address with the nonroutable IP address you entered in Step 15.
Replace hostname and domainname with the appropriate values.
Example:
10.10.10.10 mycomputer.mydomain.com mycomputer
Check the network configuration:
Open the System control panel, and select the Computer Name tab. In Full computer name, make sure you refer to the host name and the domain name.
Click Change. In Computer name, you should refer to the host name, and in Full computer name, you should refer to the host name and domain name.
Click More. In Primary DNS suffix of this computer, you should refer to the domain name.
If your DHCP server also assigns the host name for your computer (in addition to assigning an IP address), the installer might use this host name instead of the host name you defined locally.
To ensure that the installer uses the local host name, you have two options:
Option 1: Start up the installer with the OUI_HOSTNAME parameter. This parameter specifies the host name that you want to use.
prompt> setup.exe OUI_HOSTNAME=myhostname.mydomain.com
Option 2: Before running the installer, add a line to the C:\winnt\system32\drivers\etc\hosts file with the following format:
IP_address hostname.domainname hostname
This line should come after the localhost line in the file.
Replace IP_address with the loopback adapter's IP address. This should be a nonroutable IP address.
Replace hostname and domainname with the appropriate values.
Example:
10.10.10.10 mycomputer.mydomain.com mycomputer
If you have already installed Oracle Collaboration Suite, you can change the host name after installation using the change IP/host name procedures documented in the Oracle Collaboration Suite Administrator's Guide.
To remove a loopback adapter:
Display the System control panel.
Windows 2000: From the Start menu, select Settings, Control Panel, then double-click System.
Windows 2003: From the Start menu, select Control Panel, and then System.
In the Hardware tab, click Device Manager.
In the Device Manager window, expand Network adapters. You should refer to Microsoft Loopback Adapter.
Right-click Microsoft Loopback Adapter and select Uninstall.
Click OK.
Instead of installing from the Oracle Collaboration Suite DVD, you can copy the contents of the DVD to a hard drive and install the product from there. This provides for an easier solution if you plan to install many instances of Oracle Collaboration Suite on your network, or if the computers where you want to install Oracle Collaboration Suite do not have DVD-ROM drive.You can also install Oracle Collaboration Suite from remote DVD-ROM drives. Refer to Section 2.8.8 for more information.
Accessing the Hard Drive from Other Computers
To install Oracle Collaboration Suite on remote computers from the hard drive where you copied the contents of the DVD, perform the following steps:
On the local computer, share the hard drive.
On the computers where you want to install Oracle Collaboration Suite, map to the shared hard drive.
Run the installer from the remote computers where you want to install Oracle Collaboration Suite.
|
Note: Note that you must use the drive letter for the mapped drive to access the installer (for example,H:\setup.exe).
You cannot use the universal naming convention (UNC) syntax (\\hostname\sharename) to access the installer. |
Checking the Space Requirement
Ensure that the hard drive contains enough space to hold the contents of the Oracle Collaboration Suite DVD.
If the computer where you want to install Oracle Collaboration Suite does not have a CD-ROM or DVD-ROM drive, you can perform the installation from a remote CD-ROM or DVD-ROM drive. Check that you have performed these steps:
Share the DVD-ROM Drive on the Remote Computer
The remote DVD-ROM drive that you want to use must allow shared access. To set this up, perform these steps on the remote computer (that has the DVD-ROM drive):
Log in to the remote computer as an Administrator user.
Start up Windows Explorer.
Right-click the DVD-ROM drive letter and choose Sharing (Windows 2000).
or Sharing and Security (Windows 2003).
In the Sharing tab:
Select Share this folder.
Share name: Give it a share name such as dvd. You will use this name when you map the DVD-ROM drive on the local computer. Refer to Step d.
Click Permissions. You need at least read permission for the user who will be accessing it to install Oracle Collaboration Suite.
Click OK when done.
Insert the Oracle Collaboration Suite DVD-ROM in to the DVD-ROM drive.
Map the DVD-ROM Drive on the Local Computer
Perform these steps on the local computer to map the DVD-ROM drive and to run the installer:
Map the remote DVD-ROM drive.
Start up Windows Explorer on the local computer.
Select Tools. Select Map Network Drive. This displays the Map Network Drive dialog.
Select a drive letter to use for the remote DVD-ROM drive.
In Folder, enter the location of the remote DVD-ROM drive using the following format:
\\remote_hostname\share_name
Replace remote_hostname with the name of the remote computer with the DVD-ROM drive.
Replace share_name with the share name that you entered in Step 4.
Example: \\computer2\dvdrom
To connect to the remote computer as a different user:
Click different user name, and enter the user name.
Click Finish.
Run the installer from the mapped DVD-ROM drive.
To install and run Oracle Collaboration Suite on a remote computer (that is, the remote computer has the hard drive and will run Oracle Collaboration Suite components), but you do not have physical access to the computer, you can still perform the installation on the remote computer if it is running remote control software such as VNC or Symantec pcAnywhere. You also need the remote control software running on your local computer.
You can install Oracle Collaboration Suite on the remote computer in one of two ways:
If you have copied the contents of the Oracle Collaboration Suite DVD-ROM to a hard drive, you can install from the hard drive.
You can insert the DVD-ROM into a drive on your local computer, and install the product from the DVD-ROM.
Installing from a Hard Drive
If you have copied the contents of the Oracle Collaboration Suite DVD-ROM to a hard drive, you can install from the hard drive.
The steps that you must perform are as follows:
Ensure that the remote control software is installed and running on the remote and local computers.
Share the hard drive that contains the Oracle Collaboration Suite DVD-ROM.
On the remote computer, map a drive letter to the shared hard drive. You would use the remote control software to do this on the remote computer.
Through the remote control software, run the installer on the remote computer. You access the installer from the shared hard drive.
Installing from a Remote DVD-ROM Drive
You can insert the DVD-ROM into a drive on your local computer, and install from it. This is similar to the scenario described in Section 2.8.8.
The steps that you must perform are:
Ensure that the remote control software is installed and running on the remote and local computers.
On the local computer, share the DVD-ROM drive.
On the remote computer, map a drive letter to the shared DVD-ROM drive. You would use the remote control software to do this on the remote computer.
These steps are described in Section 2.8.8.
Through the remote control software, run the installer on the remote computer. You access the installer from the shared DVD-ROM drive.
Table 2-11 lists the checks performed by the installer.
Table 2-11 Prerequisite Checks Performed by the Installer
| Item | Description |
|---|---|
| Operating system version | Refer to Section 2.2 for supported versions. |
| User | The installer checks that the user has administrative privileges. |
| Monitor | Refer to Section 2.1 for monitor requirements. |
| Windows Service Packs | Refer to Section 2.2 for a list of required packs. |
| Memory | Refer to Section 2.1 for recommended values. |
| Total pagefile (virtual memory) size | Refer to Section 2.1 for recommended values. |
| TEMP space | Refer to Section 2.1 for recommended values. |
| Instance name | The installer checks that the computer on which you are installing Oracle Collaboration Suite does not already have an instance of the same name. |
| Oracle home directory name | The installer checks that the Oracle home directory name does not contain any spaces. |
| Path to the Oracle home directory | The installer checks that the path to the Oracle home directory is not longer than 127 characters. |
| Oracle home directory contents | The installer checks that the Oracle home directory does not contain any files that might interfere with the installation. |
| Oracle home directory
<<Are these assumptions correct?>> |
Always install Oracle Collaboration Suite in a new directory, unless you are expanding an Oracle Collaboration Suite Applications tier. Refer to Section 6.7. Here are some examples of installations that are not allowed:
|
| Port 1521 | The installer displays a warning if port 1521 is in use by any application, including database listeners of any version. You must stop the application that is using port 1521, then click Retry in the warning dialog.
If a database listener is using port 1521, you might be able to use it for Oracle Collaboration Suite Database. Refer to Section 2.4.6 for details. If it is another application that is using port 1521, you must stop it or configure it to use a different port. Alternatively, you can change the database listener to use a port other than 1521, but you can do this only after installation. Refer to the Oracle Collaboration Suite Administrator's Guide for details. |
| Static port conflicts | The installer checks the ports listed in the staticports.ini file, if specified. Refer to Section 2.4. |
DBCA_RAW_CONFIG environment variable |
If you are installing the Infrastructure in an Oracle Real Application Clusters environment, you must set this environment variable to point to a file that describes the locations of your raw partitions. |
TNS_ADMIN environment variable |
The TNS_ADMIN environment variable must not be set. |
| Cluster file system | The installer checks that you are not installing Oracle Collaboration Suite in a cluster file system (CFS). |
| Oracle Enterprise Manager directories are writable | The installer runs this check only if you are expanding Oracle Collaboration Suite 10g Applications or if you are reinstalling Oracle Collaboration Suite in the same Oracle home. The installer checks that these directories are writable by the operating system user running the installer:
|
| Oracle Enterprise Manager files exist | The installer runs this check only if you are expanding Oracle Collaboration Suite 10g Applications or if you are reinstalling Oracle Collaboration Suite in the same Oracle home. The installer checks that these files exist:
|
