3 What is New in the Installation

This chapter contains information about new installation features for Oracle Application Server 10g Forms and Reports Services in the following sections:

• Section 3.1, "Custom Port Numbers"

• Section 3.2, "Configuration Assistant Enhancements"

3.1 Custom Port Numbers

In Oracle Application Server 10g Forms and Reports Services 10g, you can specify custom port numbers for components, instead of having the Oracle Universal Installer (OUI) assign default port numbers. The term for this feature is "static ports". To use static ports, set up a file with component names and desired port numbers. The OUI then uses the values from the file instead of the default port numbers.

See Also: For more details, see Section 3.1.3, "Using Custom Port Numbers (the "Static Ports" Feature)".

3.1.1 Ports

Many Oracle Application Server 10g Forms and Reports Services components, such as Oracle HTTP Server and OracleAS Web Cache, use ports. You can have OUI assign default port numbers, or use port numbers that you specify. The information in the following sections provide more information on the usage and customizing of ports.

• Section 3.1.2, "Using Default Port Numbers"

• Section 3.1.3, "Using Custom Port Numbers (the "Static Ports" Feature)"

3.1.2 Using Default Port Numbers

If you want to use the default port numbers assigned to the installed components, you do not have to do anything. See Table 3–1, " Default Port Numbers and Ranges (Arranged by Component)" for a list of default port numbers that OUI will assign to components.

Tip: The OUI will not assign port numbers that are specified in the /etc/services file. If you do not want OUI to assign a specific port number, add the port number to the /etc/services file. For example, if you want to reserve port 7777 for an application, you can add something like the following line to the /etc/services file: myApplication 7777/tcp The OUI will not assign port 7777 to any component if this line exists in the /etc/services file.

Note: In the default configuration for hp-ux PA-RISC (64-bit) and Linux x86 operating system, the /etc/services file includes ports 389 and 636 (for LDAP and LDAP/SSL). These are the default ports for Oracle Internet Directory. This means that if you want to use these port numbers for Oracle Internet Directory, you must either delete or comment out these lines in the /etc/services file. To comment out a line, add a # at the beginning of the line, as follows: # ldap 389/tcp # Lightweight Directory Access Protocol # ldap 389/udp # Lightweight Directory Access Protocol # ldaps 636/tcp # LDAP protocol over TLS/SSL (was sldap) # ldaps 636/udp # LDAP protocol over TLS/SSL (was sldap) If you do not comment out or remove the lines from the /etc/services file, then OUI will not assign ports 389 and 636 for Oracle Internet Directory (OID). Instead, it assigns a number from the default port number range for OID. See Table 3–1, " Default Port Numbers and Ranges (Arranged by Component)" for a list of default port numbers.

3.1.3 Using Custom Port Numbers (the "Static Ports" Feature)

To instruct OUI to assign custom port numbers for components:

1. Create a file containing the component names and port numbers. See below for file format. This file is typically called the staticports.ini file, but you can name it anything you want.

2. When you start up OUI, you can include the file name in the command line.

The staticports.ini file has the following format (replace the port_num variable with the port number that you want to use for the component).

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
Oracle HTTP Server Jserv port = port_num
Java Object Cache port = port_num
DCM Java Object Cache 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
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
Reports Services SQL*Net port = port_num
Oracle Certificate Authority SSL Server Authentication port = port_num
Oracle Certificate Authority SSL Mutual Authentication port = port_num
Log Loader port = port_num

The easiest way to create the file is to use the staticports.ini file on the Disk 1 CD-ROM as a template:

1. Copy the staticports.ini file from the Disk 1 CD-ROM to your hard drive.

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

   You only provide port numbers for components that require them. You do not need to provide port numbers for all the components in this file. Remove the lines for the components for which you want to use default port numbers.

   
   

   Usage Notes: Port numbers cannot be greater than 65536. If you use a port number lower than 1024 for a component, you must run the component as the root user. If you use a port number lower than 1024 for a component, OUI will not be able to 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. You still have to comment out ports 389 and 636 in the /etc/services file if you want to use these port numbers for OID. See the Note on page 3-2 for details. If you plan to set port numbers for Oracle HTTP Server and OracleAS Web Cache, read Section 3.1.3.1, "Ports for Oracle HTTP Server and OracleAS Web Cache".

   
   

   The following example sets the Application Server Control port and some ports for OracleAS Web Cache. For components not specified, OUI 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
   
   

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 10g Forms and Reports Services installation. If you have installed Oracle Application Server 10g Forms and Reports Services 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.

3.1.3.1 Ports for Oracle HTTP Server and OracleAS Web Cache

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.

Configuring OracleAS Web Cache and Oracle HTTP Server

Use the following procedure to configure OracleAS Web Cache and Oracle HTTP Server:

1. Set the port for OracleAS Web Cache.

   OracleAS Web Cache uses the port specified by the Port directive (Figure 3–1). To set this port, add the following line in the staticports.ini file:

   Web Cache HTTP Listen port = port_number
   
   

   To configure the SSL port for OracleAS Web Cache, add 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 the 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, if you have the following lines in staticports.ini, the Port directive would be set to 7979:

   Web Cache HTTP Listen port = 7979
   Oracle HTTP Server port = 8080
   
   

2. Set the port for Oracle HTTP Server.

   Oracle HTTP Server uses the port specified by the Listen directive. To set this port, add the following line in the staticports.ini file:

   Oracle HTTP Server Listen port = port_number
   
   

   To configure the SSL Listen port, add the following line:

   Oracle HTTP Server Listen (SSL) port = port_number
   
   

Figure 3-1 Configuring both OracleAS Web Cache and Oracle HTTP Server

Description of the illustration ports_wc.gif

Configuring Oracle HTTP Server Only

If you are configuring Oracle HTTP Server only, then Oracle HTTP Server uses both Port and Listen directives. In this case, 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 the staticports.ini file, they will be ignored because you are not configuring OracleAS Web Cache.

3.1.3.2 Examples

This section describes some common scenarios for using the staticports.ini file.

• Section 3.1.3.2.1, "Configuring Oracle HTTP Server to Use Ports 80 and 443 With OracleAS Web Cache as the Front-End"

• Section 3.1.3.2.2, "Configuring Oracle HTTP Server to Use Ports 80 and 443 Without OracleAS Web Cache"

3.1.3.2.1 Configuring Oracle HTTP Server to Use Ports 80 and 443 With OracleAS Web Cache as the Front-End

In this scenario, create a staticports.ini file that includes the following lines:

Web Cache HTTP Listen port = 80
Oracle HTTP Server Listen port = 81     See below.
Web Cache HTTP Listen (SSL) port = 443
Oracle HTTP Server Listen (SSL) port = 444     See below.

The ports for Oracle HTTP Server Listen and SSL Listen can be any available port. The example uses ports 81 and 444. These port numbers do not have to be less than 1024. If you select port numbers less than 1024, you have to start up Oracle HTTP Server and OracleAS Web Cache as the root user.

Note: Because you are using ports lower than 1024, you have to configure Oracle HTTP Server and OracleAS Web Cache to run as the root user. You do this configuration after installation. For more details, see Oracle HTTP Server Administrator's Guide and Oracle Application Server Web Cache Administrator's Guide.

3.1.3.2.2 Configuring Oracle HTTP Server to Use Ports 80 and 443 Without OracleAS Web Cache

In this scenario, create a staticports.ini file that includes the following lines:

Oracle HTTP Server port = 80
Oracle HTTP Server Listen port = 80
Oracle HTTP Server SSL port = 443
Oracle HTTP Server Listen (SSL) port = 443

Note: Because you are using ports lower than 1024, you have to configure Oracle HTTP Server to run as the root user. Do this configuration after installation. For details, see Oracle HTTP Server Administrator's Guide.

3.1.3.3 Notes on Using the staticports.ini File

• You do not need to specify port numbers for all components in the staticports.ini file. If you remove the line for a component from the file, OUI uses the default port number for the component.

• Names of components in the file are case sensitive.

• OUI 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 OUI detects that a specified port is not available, it displays an alert. The OUI will not assign a port that is not available. To fix this:

  1. Edit the staticports.ini file to specify a different port, or shut down the application that is using the port.

  2. Click Retry. The OUI rereads the staticports.ini file and verifies the entries in the file again.

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

3.1.4 Default Port Numbers

Table 3–1 lists the default port numbers for components. The last column, Name in staticports.ini, specifies the component name as it appears in the staticports.ini file, which enables you to override the default port numbers. See Section 3.1.3, "Using Custom Port Numbers (the "Static Ports" Feature)" for details.

Table 3-1 Default Port Numbers and Ranges (Arranged by Component)

Component	Default Port	Port Number Range	Name in staticports.ini
Oracle Process Management and Notification (OPMN)
Oracle Notification Server Request Port	6003	6003 - 6099	Oracle Notification Server Request port
Oracle Notification Server Local Port	6100	6100 - 6199	Oracle Notification Server Local port
Oracle Notification Server Remote Port	6200	6200 - 6299	Oracle Notification Server Remote port
Oracle Application Server Containers for J2EE (OC4J)
OC4J AJP	3301	3301 - 3400	Not settable
OC4J RMI	3201	3201 - 3300	Not settable
JMS	3701	3701 - 3800	Not settable
IIOP	3401	3401 - 3500	Not settable
IIOPS1	3501	3501 - 3600	Not settable
IIOPS2	3601	3601 - 3700	Not settable
OracleAS Forms Services
OracleAS Forms Services	Uses the same port as Oracle HTTP Server
Oracle HTTP Server
Oracle HTTP Server Listener (OracleAS Web Cache not configured)	7777	7777 - 7877	Oracle HTTP Server Listen port
Oracle HTTP Server Listener (SSL)	4443	4443 - 4543	Oracle HTTP Server Listen (SSL) port
Oracle HTTP Server Listener (non-SSL, OracleAS Web Cache configured)	7778	7777 - 7877	Oracle HTTP Server port
Oracle HTTP Server Listener (SSL, OracleAS Web Cache configured)	4444	4443 - 4543	Oracle HTTP Server SSL port
JServ servlet engine	8007	8007 - 8107	Oracle HTTP Server Jserv port
Java Object Cache	7000	7000 - 7099	Java Object Cache port
DCM Java Object Cache	7100	7100 - 7199	DCM Java Object Cache port
SOAP server	9998	9998 - 9999	Not settable
Port Tunneling	7501	7501 - 7599	Not settable
Oracle HTTP Server Diagnostic port	7200	7200 - 7299	Oracle HTTP Server Diagnostic port
OracleAS Reports Services
SQL*Net (for 6i backwards compatibility only)	1950	1950 - 1960	Reports Services SQL*Net port
OracleAS Reports Services Visigenics CORBA	14000	14000 - 14010	Not settable
OracleAS Web Cache
OracleAS Web Cache - HTTP Listener	7777	7777 - 7877	Web Cache HTTP Listen port
OracleAS Web Cache - HTTP Listener (SSL)	4443	4443 - 4543	Web Cache HTTP Listen (SSL) port
OracleAS Web Cache Administration	4000	4000 - 4300	Web Cache Administration port
OracleAS Web Cache Invalidation	4001	4000 - 4300	Web Cache Invalidation port
OracleAS Web Cache Statistics	4002	4000 - 4300	Web Cache Statistics port
Oracle Enterprise Manager Application Server Control
Application Server Control	1810	1810 - 1829	Application Server Control port
Application Server Control - RMI	1850	1850 - 1869	Application Server Control RMI port
Application Server Control - SSL	4888	4888 - 4899	Not settable
Log Loader	44000	44000 - 44099	Log Loader port
Oracle Enterprise Manager 10g Grid Control
Grid Control	Uses the same port as Oracle HTTP Server
Oracle Management Agent	1830	1830 - 1849	Oracle Management Agent port
Oracle Management Service	7770	7770 - 7776
OracleAS Certificate Authority
Server Authentication Virtual Host	4400	4400 - 4419	Oracle Certificate Authority SSL Server Authentication port
Mutual Authentication Virtual Host	4401	4400 - 4419	Oracle Certificate Authority SSL Mutual Authentication port

3.2 Configuration Assistant Enhancements

In Oracle Application Server 10g Forms and Reports Services, configuration assistants are enhanced with these features:

• The configuration assistants write log files in a central location.

• The configuration assistants write more understandable error messages in the log files.

• You can rerun configuration assistants that have failed.