4 Configuration

This chapter discusses Oracle9i Application Server configuration topics. It covers the following topics:

Section 4.1, "Common Configurations"
Section 4.2, "Configuration Limitations"
Section 4.3, "Configuration Tasks and Issues"
Section 4.4, "Using Oracle9iAS with J2SE Version 1.4"

4.1 Common Configurations

Oracle certifies the following common configurations with Oracle9iAS Release 2 (9.0.3):

Supported Configuration	Reference	Possible Deployments	Restrictions
Changing CPU on an installed machine.	None.	NA	None.
Using Oracle9iAS with J2SE Version 1.4.		NA	None.
Using an Oracle9i Database with Oracle Real Application Clusters 9.2 as the customer database.	None.	NA	Oracle9iAS Clickstream Intelligence is not supported to use this customer database.

4.2 Configuration Limitations

Oracle9iAS Release 2 (9.0.3) does not support the following:

Changing the domain name of a host that contains an Oracle9iAS Release 2 (9.0.3) installation.
Changing the IP address for a host that is part of a farm or cluster.
Cloning an Oracle9iAS Release 2 (9.0.3) instance.
Using Network File System (NFS) for accessing shared files.
Backing up of a configured environment and restoring it, either to a different machine or to the same machine.
Using Oracle Data Guard on Oracle9iAS infrastructure.
Using Oracle Real Application Clusters database on Oracle9iAS infrastructure.
Deassociating or reassociating an Oracle9iAS Release 2 (9.0.3) installation with an infrastructure.
Transitioning your installation from a development or test environment to a production environment.

4.3 Configuration Tasks and Issues

This section covers the following configuration issues and tasks:

Section 4.3.1, "Attributes Containing Paths Break Cluster Model"

4.3.1 Attributes Containing Paths Break Cluster Model

In attributes that specify paths, make sure that the paths are relative to ORACLE_HOME directory. Otherwise, your cluster members may not run properly.

4.4 Using Oracle9iAS with J2SE Version 1.4

Oracle9iAS Release 2 (9.0.3) ships with Java 2 Platform, Standard Edition (J2SE) version 1.3.1, which is installed in the ORACLE_HOME/jdk directory. Oracle9iAS Release 2 (9.0.3) also supports J2SE version 1.4. If you have applications that use J2SE 1.4 features, you need to use J2SE version 1.4.

This section covers the following issues:

Section 4.4.1, "Installing J2SE Version 1.4 for Oracle9iAS"

4.4.1 Installing J2SE Version 1.4 for Oracle9iAS

This section describes how to run Oracle9iAS with J2SE version 1.4. The general idea is to rename the current jdk directory to something else (such as jdk13), and install J2SE version 1.4 in the jdk directory. This makes it simple for you so that you do not have to modify any paths or scripts that reference the jdk directory.

To run Oracle9iAS with J2SE version 1.4, use the following procedures:

Stop all Oracle9iAS processes.
Rename ORACLE_HOME/jdk to something else. For example, you can rename it to jdk13.
Download J2SE version 1.4 from http://java.sun.com

Download notes:
- Download the SDK version, not the JRE version.
Install J2SE version 1.4 according to the instructions provided by Sun Microsystems, but with the additional requirement that you need to install it in the ORACLE_HOME/jdk directory.

Note:
You have to install J2SE in the ORACLE_HOME/jdk directory.

Add the following lines to JDK_1.4_HOME/jre/lib/security/java.security:

# Oracle-specific definitions
auth.policy.provider=oracle.security.jazn.spi.PolicyProvider
login.configuration.provider=oracle.security.jazn.spi.LoginConfigProvider

Note:

The login.configuration.provider line already exists in the java.security file. Comment out the existing line by prefixing a # character at the beginning of the line and add the line with the Oracle-specific value.

Start all Oracle9iAS processes and services.