1 Installing Application Developer

This chapter describes how to install Application Developer.

The following topics are covered in this chapter:

1.1 Preparing to Install

Make sure you have read"Before you Begin" in Oracle Fusion Middleware Installation Planning Guide before you install Oracle Application Developer.

1.1.1 Creating Database Schemas

Oracle Application Developer includes Oracle WSM Policy Manager and Oracle WSM-PM Extension. These components require that the MDS schema exists in your database prior to installation. You must run Repository Creation Utility (RCU) to create the MDS schema in your database. Follow the instructions in "Creating Schemas" in Oracle Fusion Middleware Repository Creation Utility User's Guide to do so.

1.1.2 Installing Oracle WebLogic Server

Oracle Application Server requires Oracle WebLogic Server:

  1. To download the latest Oracle WebLogic Server, see "Product Distribution" in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

  2. For installation instructions, see "Running the Installation Program in Graphical Mode" in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

1.2 Installation Instructions

When you run the installer, Application Developer is installed onto your system. After the product is installed, you must run the Fusion Middleware Configuration Wizard to configure Application Developer.

This section contains the following topics:

1.2.1 Starting the Installer

The installer requires the location of a Java Runtime Environment (JRE) on your system. When you installed Oracle WebLogic Server, a JRE was installed on your system. You can use this location (the location of the jre directory) to start the installer. The default location for the JRE is MW_HOME/jdk160_18 (on UNIX systems) or MW_HOME\jdk160_18 (on Windows systems), where MW_HOME is the Middleware Home directory.

On 64-bit platforms, the JRE location is the JAVA_HOME you used to install Oracle WebLogic Server.

Note:

Starting the installer as root user is not supported.

On UNIX operating systems:

./runInstaller -jreLoc JRE_LOCATION

On Windows operating systems:

setup.exe -jreLoc JRE_LOCATION

You must specify the absolute path to your JRE_LOCATION; relative paths are not supported.

Note:

You must also specify the JRE_LOCATION in the same manner if you are installing Oracle Application Developer on a 64-bit UNIX or Windows operating system with a 32-bit JDK.

If no JRE location is specified, you will be prompted to provide the location of your JRE before the installer is started. For example, on a UNIX operating system:

[> ./runInstaller 
Starting Oracle Universal Installer...
 
Checking if CPU speed is above 300 MHz.    Actual 2999 MHz    Passed
Checking Temp space: must be greater than 150 MB.   Actual 66070 MB    Passed
Checking swap space: must be greater than 512 MB.   Actual 4047 MB    Passed
Checking monitor: must be configured to display at least 256 colors.    Actual 256    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2010-02-23_10-57-58AM. Please wait ...
Please specify JRE/JDK location ( Ex. /home/jre ), <location>/bin/java should exist :

Specify the absolute path to the JRE on your system before you continue.

1.2.2 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log (on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windows operating systems) directory. Refer to Section D.2.1, "Installation Log Files" for more information about the log files and their contents.

1.2.3 Inventory Screens (UNIX Only)

If you are installing on a UNIX system, and if this is the first time any Oracle product is being installed on your system with the Oracle Universal Installer, you will be asked to provide the location of an inventory directory. This is where the installer will set up subdirectories and maintain inventory data for each Oracle product that is installed on this system.

Follow the instructions in Table 1-1 to configure the inventory directory information. For more help, click on the screen name in the table below, or click the Help button in the GUI.

Table 1-1 Inventory Directory and Group Screens

No. Screen Description and Action Required

1

Specify Inventory Directory Screen (UNIX Only)

Specify the Oracle inventory directory and group permissions for that directory. The group must have write permissions to the Oracle inventory directory.

Click OK to continue.

2

Inventory Location Confirmation Screen (UNIX Only)

Run the createCentralInventory.sh script as root.

Click OK to continue.


1.2.4 Installation Screens and Instructions

Follow the instructions in Table 1-2 to install the Application Developer software.

Note:

Running the installer as root user is not supported.

If you need additional help with any of the installation screens, refer to Appendix A, "Application Developer Installation Screens" or click Help to access the online help.

Table 1-2 Installation Flow for Install and Configure Option (Common Screens)

No. Screen Description and Action Required

1

Welcome Screen

Click Next to continue.

2

Prerequisite Checks Screen

Click Next to continue.

3

Specify Installation Location Screen

Specify the Middleware home location. The Oracle Common home (oracle_common) will automatically be created inside the Middleware home.

Click Next to continue.

4

Installation Summary Screen

Verify the installation about to be performed.

Click Install to continue.

5

Installation Progress Screen

This screen shows the progress of the installation.

When the process is 100% complete, click Next to continue.

6

Installation Complete Screen

Click Finish to dismiss the screen.


1.3 Patching Your Application Developer Installation

Next, you must use the Patch Set Installer for Application Developer to update your software to the latest version.

For instructions, refer to "Applying the Latest Oracle Fusion Middleware Patch Set with the Patch Set Installers" in Oracle Fusion Middleware Patching Guide.

After the installation and patching is complete, you must configure your products before you can begin using them. Go to Chapter 2, "Configuring Application Developer".