G Assigning Custom Ports

You can specify custom port numbers for components, instead of having the installer assign default port numbers. This feature is called the static ports feature. To use static ports, you set up a file with component names and desired port numbers. The installer uses the values from the file instead of the default port numbers.

This file is typically called the staticports.ini file, but you can name it anything you wish. The AppendixG, "Formats for the Staticports.ini File" section describes the file format.

See Also:

For more information on assigning custom port numbers for installation components, refer to the Oracle Application Server 10g Installation Guide for your operating system located at:

http://otn.oracle.com/documentation/appserver10g.html

When you start the installer, specify the appropriate parameter and the full path to the staticports.ini file on the command line. Make sure that you use the correct parameter for the installation type that you are using. If you use the incorrect parameter, the installer assigns default ports to all components.

For example, to install an additional Management Agent, in the DVD directory, type the following command at the command line:

/runInstaller -staticPortsIniFile <staticport.ini file name>

Note:

If you do not specify the full path to the staticports.ini file, the installer changes the current directory to a different one from the directory from which you started the installer, and the installer will not be able to find the file. In this event, the installer assigns default ports for all components, and it does this without displaying any warning.

Copy the staticports.ini file from the DVD-ROM to your hard disk. The file is located at:

<DVD>/response/staticports.ini

Edit the local copy (the file on the hard disk) to include the desired port numbers.

You do not need to specify port numbers for all components in the staticports.ini file. If a component is not listed in the file, the installer uses the default port number for that component.

When installation is complete, you can check the ORACLE_HOME/install/portlist.ini file to view the assigned ports.

Notes:

When choosing port numbers, consider the following:

Port numbers cannot be greater than 65536.
If you use a port number less than 1024 for a component, you must run the component as the root user.
If you use a port number less than 1024 for a component, the installer cannot start up the component at the end of installation. You may need to configure the component first before you can start it up. See the appropriate component documentation for details.

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 does 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 re-reads thestaticports.ini file and verifies the entries in the file again.

Tip:

The staticports.ini file uses the same format as the ORACLE_HOME/install/portlist.ini file, which is created after an Oracle Application Server installation. If you have installed Oracle Application Server 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.

Formats for the Staticports.ini File

The staticports.ini file has the following format. Replace port num with the port number that you want to use for the component.

# Enterprise Manager#Enterprise Manager Central Agent Port=port_num#Enterprise Manager Central Console Port=port_num#Enterprise Manager Central Console Secure Port=port_num# J2EE and Web Cache#Oracle HTTP Server Listen port=port_num#Oracle HTTP Server Listen (SSL) port=port_num#Oracle HTTP Server Diagnostic port=port_num#Web Cache HTTP Listen port=port_num#Web Cache HTTP Listen (SSL) port=port_num#Web Cache Administration port=port_num#Web Cache Invalidation port=port_num#Web Cache Statistics port=port_num#Oracle Notification Server Request port=port_num#Oracle Notification Server Local port=port_num#Oracle Notification Server Remote port=port_num#Application Server Control port=port_num#Application Server Control RMI port=port_num#Oracle Management Agent port=port_num#Log Loader port=port_num

Note:

After having specified appropriate port values, ensure you remove the comment (#) for those properties before saving the file. The values are not considered otherwise.

Error Conditions that Cause the Installer to Resort to Default Ports

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 a port is already being used by a component or any other application, do not specify that port (used port) in the staticports.ini file.
If you have specified the same port for more that one component, the installation will display an error after the prerequisite checks phase. You must rectify this error before proceeding with the installation.
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 non-numeric 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) on the command line, the installer does not find the file. The installer continues without displaying a warning and it assigns 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 installation type that you are performing (for example, if you specify the parameter for the middle tier but you are installing the infrastructure), the installer does not give a warning. It continues and assigns default ports to all components.