2 What's New in the Installation

This chapter describes new features in the Oracle Universal Installer. To see a list of new features in the product itself, visit the Oracle Technology Network site at:

http://www.oracle.com/technology

Contents:

Section 2.1, "OracleAS Metadata Repository Uses Oracle Database 10g"
Section 2.2, "Support for More High Availability Environments"
Section 2.3, "Support for Oracle Internet Directory Replication"
Section 2.4, "New Screen for Specifying the staticports.ini File"
Section 2.5, "Additional Tool for Deinstallation"
Section 2.6, "Changed Option Name in Select Configuration Options Screen for J2EE and Web Cache"
Section 2.7, "Recording Feature for Silent Installations"
Section 2.8, "Generating Installation Statistics"
Section 2.9, "Change in the Default Port Range"
Section 2.10, "New Element for Specifying Port Numbers for CORBA Communication"
Section 2.11, "Cloning OracleAS Forms and Reports Services Instances"

2.1 OracleAS Metadata Repository Uses Oracle Database 10g

In 10g (9.0.4), the installer created an Oracle9i Release 1 (9.0.1.5) database and loaded the OracleAS Metadata Repository in that database.

In this release, the installer creates an Oracle Database 10g (10.1.0.4.2) for the OracleAS Metadata Repository.

To configure this database during installation, the installer displays these new screens:

Specify Database Configuration Options
Specify Database Schema Passwords

For details, see Section 6.29, "Install Fragment: Database Screens".

2.2 Support for More High Availability Environments

In this release, Oracle Application Server supports the following high availability environments:

OracleAS Cold Failover Cluster
OracleAS Cluster (Identity Management)
OracleAS Disaster Recovery

In addition, for each environment, you can distribute the OracleAS Metadata Repository and Oracle Identity Management components over several computers. In earlier releases, you had to install all the components on the same computer.

There are also new screens related to high availability.

For details, see:

2.3 Support for Oracle Internet Directory Replication

In this release, you can install the master Oracle Internet Directory, as well as Oracle Internet Directory replicas using the installer.

During installation, you select the type of replication that you want:

Fan-out Replication (which is also called LDAP Replication)
Multimaster Replication (which is also called Advanced Replication)

For details, see Chapter 9, "Installing Oracle Internet Directory in Replicated Mode".

2.4 New Screen for Specifying the staticports.ini File

In 10g (9.0.4), if you wanted components to use custom ports, you created a staticports.ini file to map components and port numbers, and when you started the installer, you used a command-line option to specify the file.

In this release, you specify the staticports.ini file in the new "Select Port Configuration Options" screen in the installer. You do not use the command-line options to specify the file.

For details, see Section 4.5.3, "Using Custom Port Numbers (the "Static Ports" Feature)".

2.5 Additional Tool for Deinstallation

In this release, there is a new tool called the Deconfig tool which removes entries from Oracle Internet Directory and the OracleAS Metadata Repository. You run this tool before you deinstall an Oracle Application Server instance using the installer.

For details, see Section E.1, "New Tool: Deconfig Tool".

2.6 Changed Option Name in Select Configuration Options Screen for J2EE and Web Cache

In 10g (9.0.4), the Select Configuration Options screen contained these options:

OracleAS File-Based Cluster
OracleAS Database-Based Cluster

In this release, these options have been replaced by the "OracleAS Farm Repository" option because the installer does not create a cluster for the instance. The installer places the instance in a farm, but does not place it in a cluster. If you want, you can cluster it after installation.

For details, see Section 7.4, "Configuration Options for the J2EE and Web Cache Middle Tier".

2.7 Recording Feature for Silent Installations

The installer has a record mode, in which it saves your inputs to a response file. You can then use the generated response file to install Oracle Application Server on different computers using the same values.

For details, see Section B.5.2, "Creating Response Files by Using the Record Mode in the Installer".

2.8 Generating Installation Statistics

The installer provides command line options for monitoring resources used for installation. The following options are supported:

Table 2-1 Installer Options for Generating Installation Statistics

Option Description

Option	Description
`-printtime`	Use this option to get information on the time taken for the installation. The installer writes the information in the following file: `oraInventory/logs/timetimestamp.log` oraInventory specifies the location of your `oraInventory` directory. You can look in the `/etc/oraInst.loc` file to find out where this directory is on your computer.
`-printmemory`	Use this option to get information on the memory used for the installation. The installer writes the information in the following file: `oraInventory/logs/memorytimestamp.log` oraInventory specifies the location of your oraInventory directory. You can look in the `/etc/oraInst.loc` file to find out where this directory is on your computer.
`-printdiskusage`	Use this option to get information on the disk space used for the installation. The installer writes the information in the following file: `oraInventory/logs/diskusagetimestamp.log` oraInventory specifies the location of your oraInventory directory. You can look in the /`etc/oraInst.loc` file to find out where this directory is on your computer.

-printtime

Use this option to get information on the time taken for the installation. The installer writes the information in the following file:

oraInventory/logs/timetimestamp.log

oraInventory specifies the location of your oraInventory directory. You can look in the /etc/oraInst.loc file to find out where this directory is on your computer.

-printmemory

Use this option to get information on the memory used for the installation. The installer writes the information in the following file:

oraInventory/logs/memorytimestamp.log

oraInventory specifies the location of your oraInventory directory. You can look in the /etc/oraInst.loc file to find out where this directory is on your computer.

-printdiskusage

Use this option to get information on the disk space used for the installation. The installer writes the information in the following file:

oraInventory/logs/diskusagetimestamp.log

oraInventory specifies the location of your oraInventory directory. You can look in the /etc/oraInst.loc file to find out where this directory is on your computer.

For example, the following command provides information about all three items:

runInstaller -printtime -printmemory -printdiskusage

2.9 Change in the Default Port Range

The default port ranges for the following components have changed:

Oracle Internet Directory
OracleAS Certificate Authority
Oracle Application Server Containers for J2EE
Oracle Enterprise Manager 10g Application Server Control Console
Oracle Application Server Web Cache

For details, see Appendix C, "Default Port Numbers".

2.10 New Element for Specifying Port Numbers for CORBA Communication

Oracle Reports 10g Release 2 (10.1.2) introduces the ORBPorts element in the server configuration file to allow you to explicitly specify the port numbers used by Reports Server and engines for communication through CORBA. You can specify either a range of ports or individual ports separated by commas. For example:

<ORBPorts value="15000-15010"/>     (Range of values)
<ORBPorts value="15000,16000,17000,18000"/>    (Comma-separated values)

Note:

The ORBPorts element should be defined only if the TCP port filtering has been enabled on the server where Reports Server is running. If port filtering is enabled, and a few ports can be opened for Reports Server, then use ORBPorts to specify them in the server configuration file for Reports Server and engine communication. If any of the ports are not available, Reports Server or engines may fail to start and an error displays.

By default, the ORBPorts element is not present in the server configuration file. If this element is missing, Reports Server chooses a random port for CORBA communication. For more information about the ORBPorts element, see the chapter "Configuring OracleAS Reports Services" in the Oracle Application Server Reports Services Publishing Reports to the Web manual.

2.11 Cloning OracleAS Forms and Reports Services Instances

Cloning is the process of copying an existing installation to a different location while preserving its configuration. In this release, cloning an installation of OracleAS Forms and Reports Services instance is possible. For more information about cloning, refer to Oracle Application Server Administrator's Guide.