2 What’s New in the Installation

2.1 Option of Installing OracleAS Metadata Repository in an Existing Database

In Release 2 (9.0.2), the installer automatically created a new Oracle9i database and populated it with the OracleAS Metadata Repository. It was not possible to install the OracleAS Metadata Repository in an existing database.

In 10g (9.0.4), the installer can install a new database seeded with the OracleAS Metadata Repository or it can use an existing Oracle9i database (you need to provide the connect information for the database). If you want to use an existing database, you need to run the new Oracle Application Server Repository Creation Assistant tool, available on the "OracleAS RepCA and Utilities" CD-ROM, to populate the existing database with the OracleAS Metadata Repository. You would do this before running the installer to install other Oracle Application Server components.

See Chapter 10, " Installing the OracleAS Metadata Repository in an Existing Database" for details, including database requirements.

2.2 Custom Port Numbers

In 10g (9.0.4), 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.

See Section 4.4.2, "Using Custom Port Numbers (the "Static Ports" Feature)" for details.

2.3 One ias_admin User Per Oracle Application Server Instance

In Release 2 (9.0.2), if you install Oracle Application Server on a computer that already has an Oracle Application Server instance (using the same operating system user to perform the installations), you would need to enter the password of the existing ias_admin user during installation, because the instances share the same ias_admin user.

In 10g (9.0.4), each instance of Oracle Application Server has its own ias_admin user. Even if you install multiple Oracle Application Server instances on the same computer using the same operating system user, you would need to provide new passwords for each ias_admin user.

2.4 emtab File No Longer Created or Used

Oracle Application Server 10g (9.0.4) does not create or use the emtab file because each Oracle Application Server instance has its own Oracle Enterprise Manager Application Server Control (or Application Server Control, for short).

In 10g (9.0.4), the Application Server Control does not have the concept of "primary installation".

If you installed Release 2 (9.0.2) on your computer, you might have the emtab file from that release.

2.5 New Operating System Patches Required

Release 2 (9.0.2) required JDK 1.3.1. This release, 10g (9.0.4), ships with JDK 1.4.2 for Linux and requires JDK 1.4.1.05 or higher for HP-UX. On HP-UX, JDK 1.4.1.05 requires additional system patches. You must check if your computer has the updated patches. See Section 4.2, "Check the Software Requirements" for a list of patches.

2.6 Space in /var/tmp No Longer Required During Installation

In 10g (9.0.4), the installer does not require any disk space in the /var/tmp directory. However, some components may write to /var/tmp during runtime.

2.7 /etc/hosts File Does Not Need to Be in a Specific Format (in Most Cases)

In Release 2 (9.0.2), you had to ensure the content in the /etc/hosts file followed a specific format.

In 10g (9.0.4), this is no longer required. However, the installer still uses this file for a few items. See Section 4.8, "The /etc/hosts File" for details.

2.8 Support for High Availability Configurations

In 10g (9.0.4), the installer can detect hardware clusters and install Oracle Application Server on clustered nodes. A new screen in the installer displays all the nodes in a cluster, and you select the nodes where you want the installer to install Oracle Application Server.

Oracle Application Server can run in OracleAS Active Failover Cluster, OracleAS Cold Failover Cluster, and OracleAS Disaster Recovery environments. See Chapter 9, " Installing in High Availability Environments" for details.

Oracle Application Server can also run in a Real Application Clusters environment. See Section 10.8, "Installing OracleAS Metadata Repository in a Real Application Clusters Database" for details.

2.9 Support for Selecting OracleAS Cluster Type During Installation

In 10g (9.0.4), when you install the J2EE and Web Cache middle tier type, the "Select Configuration Options" screen prompts you to select either file-based clustering or database-based clustering. See Section 7.4, "Configuration Options for the J2EE and Web Cache Middle Tier" for details.

2.10 Support for Secure Installations

In 10g (9.0.4), you can specify that Oracle Application Server components connect to Oracle Internet Directory using SSL only. See Section 5.13, "Connecting to Oracle Internet Directory Through SSL Connections" for details.

2.11 Support for IP Address and Hostname Changes After Installation

Oracle Application Server supports IP address changes after installation for all installation types except for the OracleAS Developer Kits 10g installation type.

For hostname changes, this is supported only for computers running Oracle Application Server middle tiers. It is not supported for computers running OracleAS Infrastructure 10g or OracleAS Developer Kits 10g.

If you change the hostname or IP address after installation (using operating system commands or editing operating system configuration files), you need to use Application Server Control to update the information in Oracle Application Server configuration files. See the Oracle Application Server 10g Administrator's Guide for details.

2.12 Changed Terminology

Table 2-1 lists terms updated in 10g (9.0.4). The 10g (9.0.4) documentation set uses the new terms.

2.13 Configuration Assistant Enhancements

In 10g (9.0.4), configuration assistants now have these features:

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

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

• You can now rerun configuration assistants that have failed.

For details, see Appendix B, " Troubleshooting".

2.14 More Prerequisite Checks

In 10g (9.0.4), the installer performs more prerequisite checks to ensure that your computer meets the minimum requirements. See Section 4.10, "Prerequisite Checks Performed by the Installer" for a list of checks.

2.15 Removed Restrictions

The following restrictions that were in Release 2 (9.0.2) are now removed:

• NFS installations are now supported.

• When you install a middle tier on a computer that already has other middle tiers, you need to select which farm the middle tier should belong to. The installer no longer automatically assigns middle tiers to existing farms.

• Silent installations no longer require X windows, but interactive installations still require it.

2.16 Support for Generating Installation Statistics

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

• -printtime prints the time taken for installation.

• -printmemory prints the memory used for installation.

• -printdiskusage prints the disk space used for installation.

Example: the following command prints information for all three items:

runInstaller -printtime -printmemory -printdiskusage

2.17 Support for Off Network and DHCP Installations on Linux

You can install Oracle Application Server 10g (9.0.4) on a Linux system that is not on a network and you can install Oracle Application Server 10g (9.0.4) on a Linux system that is configured to use DHCP.