Oracle JDeveloper 11g Technology Preview 4

Installation Guide

April 2008

Before you install JDeveloper, please review the content of this guide.

Table of Content

• 1.0 JDeveloper System Requirements
  • 1.1 Recommended CPU, Memory, Display, and Hard Drive Configurations
  • 1.2 Support for Team Based Development Tools
• 2.0 Installing and Starting JDeveloper on Windows
  • 2.1 Installing the Complete Version
  • 2.2 Installing JDeveloper Base
  • 2.3 Starting JDeveloper on Windows
  • 2.4 Specifying the JDK location on Windows
  • 2.5 User Directories on Windows
• 3.0 Installing and Starting JDeveloper on Linux and UNIX Platforms
  • 3.1 Configuring the JDK in JDeveloper
  • 3.2 Modifying Permissions on Linux and UNIX Platforms
  • 3.3 Cursor Problems
  • 3.4 Starting JDeveloper on Linux and UNIX Systems
  • 3.5 Specifying the JDK location on Linux and UNIX Systems
• 4.0 Installing and Starting JDeveloper on Mac OS X Platforms
  • 4.1 Configuring the JDK in JDeveloper
  • 4.2 Modifying Permissions on Mac OS X Platforms
• 5.0 Migrating User Settings
• 6.0 Enabling JDeveloper Extensions
• 7.0 Setting the User Home Directory
  • 7.1 Setting the Home Environment Variable on Windows
  • 7.2 Setting the Home Environment Variable on Linux and UNIX
  • 7.3 Setting the Home Environment Variable on Mac OS X
• 8.0 Using JDeveloper in a Multiuser Environment
  • 8.1 Installing JDeveloper on a Citrix MetaFrame Server or a Microsoft Terminal Server
  • 8.2 Configuring User Home Directories in a Multiuser Environment
  • 8.3 Configuring Terminal Server Clients for Running JDeveloper
• 9.0 Using OC4J with JDeveloper
• 10.0 Application Servers Supported by JDeveloper
• 11.0 Database Certification for JDeveloper
• 12.0 Web Browsers Supported by JDeveloper
• 13.0 Finding JDeveloper Accessibility Information
• 14.0 Using a Screen Reader and Java Access Bridge with JDeveloper
  • 14.1 Configuring JAWS 7.0 and Access Bridge with JDeveloper
• 15.0 Uninstalling JDeveloper
• 16.0 Oracle on the Web

1.0 JDeveloper System Requirements

This release of JDeveloper is tested and supported on the specific versions Windows, Linux, and Mac OS X, as listed in Section 1.1 below. In addition, it is supported on any operating system that supports Sun Java SE Development Kit (JDK) 5.0.

1.1 Recommended CPU, Memory, Display, and Hard Drive Configurations

Windows

Resource	Recommended
Operating System	Windows 2000-Service Pack 4 Windows Server 2003 R2 Windows XP-Service Pack 2
CPU Type and Speed	Pentium IV 2 GHz or faster
Memory	Studio Edition: 2 GB RAM
Display	65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space (for Base Installation)	Studio Edition: 725 MB
JDK	JDK 5.0 Update 6 or later for Windows, available at: http://java.sun.com/javase/downloads/index_jdk5.jsp. (Included in the Complete Installation.)

Linux

Resource	Recommended
Distribution	Red Hat Enterprise Linux 3.0 Red Hat Enterprise Linux 4.0
CPU Type and Speed	Pentium IV 2 GHz or faster
Memory	Studio Edition: 2 GB RAM
Display	65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space	Base Installation: 725 MB
JDK	JDK 5.0 Update 6 or later for Linux, available at: http://java.sun.com/javase/downloads/index_jdk5.jsp.

MAC OS X

Resource	Recommended
Operating System	Apple Mac OS X Version 10.4.x
CPU Type and Speed	Dual 1.25 GHz G4/G5 (1 GHz G4 minimum)
Memory	2 GB RAM
Display	"Thousands" of colors
Hard Drive Space	Base Installation: 725 MB
JDK	Sun J2SE 1.5 release 4 available at the following locations: http://www.apple.com/support/downloads/j2se50release4ppc.html (Power PC) http://www.apple.com/support/downloads/j2se50release4intel.html (Intel)

1.2 Support for Team Based Development Tools

JDeveloper provides integrated support for Concurrent Version System (CVS) and Subversion:

• CVS version 1.11.x
• CVSNT 2.5.02 & 2.5.03
• Subversion 1.4.3

Back to TOC

2.0 Installing and Starting JDeveloper on Windows

JDeveloper does not require an installer. To install JDeveloper, you will need an unzip tool. You can download a free, cross-platform unzip tool, Info-Zip, available at: http://www.info-zip.org/.

2.1 Installing the Complete Version

The complete installation (jdev<edition>1111.zip) includes the Windows version of JDK 5.0 and the JDeveloper documentation.

To install the complete version, unzip jdev<edition>1111.zip in the directory you want to install JDeveloper.

2.2 Installing JDeveloper Base

For quicker download times, you can download the base installation (jdev<edition>base1111.zip). The base installation requires that you already have JDK 5.0 on your machine because the JDK is not included.

To install JDeveloper from jdev<edition>base1111.zip:

1. If you don't have JDK 5.0 installed, you can obtain it from: http://java.sun.com/javase/downloads/index_jdk5.jsp.
2. Unzip jdev<edition>base1111.zip to the target directory.
3. Specify the location of your JDK installation in the dialog that appears when you start JDeveloper for the first time. You will need to enter the path to java.exe.
   

2.3 Starting JDeveloper on Windows

To start JDeveloper on Windows, run any of the following files:

• <jdev_home>\jdeveloper.exe
• <jdev_home>\jdev\bin\jdevw.exe
• <jdev_home>\jdev\bin\jdev.exe (to display a console window for internal diagnostic information)

2.4 Specifying the JDK location on Windows Systems

Specify the location of your JDK installation in the dialog that appears when you start JDeveloper for the first time. You will need to enter the path to java.exe.

To change a JDK location that you have previously specified, set the variable SetJavaHome in the file <jdev_home>\jdev\bin\jdev.conf to the location of your JDK installation. Use an editor that recognizes UNIX end-of-line characters, such as WordPad. When you save the file, WordPad will warn you that it is about to save the file in text-only format. You can ignore this warning.

For example, in a Windows environment, if the location of your JDK 5.0 is in a directory called jdk1.5.0_14 on your D: drive, your entry in jdev.conf would look like:

SetJavaHome d:\jdk1.5.0_14

2.5 User Directories on Windows

The new default directory structure for user-specific content in JDeveloper for Windows is provided below:

• The default location for the system subdirectory is now %APPDATA%\JDeveloper\systemXX.XX.XX.XX, where:
  • %APPDATA% is the Windows Application Data directory for the user (usually C:\Documents and Settings\<user>\Application Data)
  • XX.XX.XX.XX is a unique number of the product build, for example, system11.1.1.0.22.47.89
• The default location for user-generated content (previously stored in <jdev_home>\jdev\mywork) is now C:\JDeveloper\mywork.

For more information on user directories and how to set the value for the home environment variable, see Setting the User Home Directory.

3.0 Installing and Starting JDeveloper on Linux and UNIX Platforms

This section provides additional instructions specific to installing JDeveloper on Linux and UNIX systems.

JDeveloper does not require an installer. To install JDeveloper, you will need an unzip tool. You can download a free, cross-platform unzip tool, Info-Zip, available at: http://www.info-zip.org/.

To install JDeveloper on Linux and UNIX platforms, unzip jdev<edition>base1111.zip in the directory you want to install JDeveloper.

3.1 Configuring the JDK in JDeveloper

The base installation (jdev<edition>base1111.zip) does not contain the JDK for running JDeveloper and creating projects. If you install JDeveloper on Linux or UNIX, perform the following steps to configure JDeveloper to use the appropriate JDK.

1. If you don't have JDK 5.0 installed, install it. You can get a copy for many operating systems from http://java.sun.com/javase/downloads/index_jdk5.jsp, or ask your OS vendor for a copy.
2. When you start JDeveloper for the first time, the jdev script prompts you to provide the location of your JDK installation if it cannot locate it. You will need to enter the path to java.exe.

3.2 Modifying Permissions on Linux and UNIX Platforms

All JDeveloper files must have read permissions which can be set by issuing:

chmod -R g+r <jdev_home>

Users (or groups) must have write permissions for the following files (required for deployment):

• <jdev_home>/j2ee/home/application-deployments
• <jdev_home>/j2ee/home/applications
• <jdev_home>/j2ee/home/config

3.3 Cursor Problems

On UNIX or Linux platforms, the Java cursors may display large and opaque, creating difficulties when used for drag and drop operations. To address this problem JDeveloper provides a set of cursors to replace the default set. You must have write access to the JDK in order to replace the cursors.

To replace the cursors:

1. Make a back-up copy of the default cursors located in the JDK directory at:

   <jdk_install>/jre/lib/images/cursors

2. Extract the replacement cursors from the tar file at:

   <jdev_home>/jdev/bin/clear_cursors.tar

3.4 Starting JDeveloper on Linux and UNIX Systems

To start JDeveloper on Linux and UNIX, run the file <jdev_home>/jdev/bin/jdev.

Back to TOC

3.5 Specifying the JDK location on Linux and UNIX Systems

When you start JDeveloper for the first time, the jdev script prompts you to provide the location of your JDK installation if it cannot locate it. You will need to enter the path to java.exe.

To change a JDK location that you have previously specified, set the variable SetJavaHome in the file <jdev_home>/jdev/bin/jdev.conf to the location of your Java installation.

For example, in a UNIX environment, if the location of your JDK is in a directory called /usr/local/java, your entry in jdev.conf would look like:

SetJavaHome /usr/local/java

4.0 Installing and Starting JDeveloper on Mac OS X Platforms

JDeveloper does not require an installer. To install JDeveloper, you will need an unzip tool. You can download a free, cross-platform unzip tool, Info-Zip, available at: http://www.info-zip.org/.

To install this version of JDeveloper on Mac OS X platforms, unzip jdev<edition>base1111.zip in the directory you want to install JDeveloper.

4.1 Configuring the JDK in JDeveloper

The base installation (jdev<edition>base1111.zip) does not contain the JDK for running JDeveloper and creating projects. If you install JDeveloper on Mac OS X, perform the following steps to configure JDeveloper to use the appropriate JDK.

1. You must update your Mac OS X JDK to Java Sun version 1.5 release 4 or later for use with JDeveloper. Use Mac OS X Software Update or download from http://www.apple.com/support/downloads/j2se50release4ppc.html (Power PC) or http://www.apple.com/support/downloads/j2se50release4ppc.html (Intel).
2. Specify the path to java.exe in the
3. Set the variable SetJavaHome in the file <jdev_home>/jdev/bin/jdev.conf to the location of your Java installation. For example, if the location of your JDK is in a directory called /usr/local/java, your entry in jdev.conf would look like:
   
   SetJavaHome /usr/local/java

4.2 Modifying Permissions on Mac OS X Platforms

All JDeveloper files must have read permissions which can be set by issuing:

chmod -R g+r <jdev_home>

Users (or groups) must have write permissions for the following files (required for deployment):

• <jdev_home>/j2ee/home/application-deployments
• <jdev_home>/j2ee/home/applications
• <jdev_home>/j2ee/home/config

5.0 Migrating User Settings

Migration to this JDeveloper 11g Technology Preview 4 release from a previous release, and from this release to the final production release of JDeveloper 11.1.1.0.0 is not supported.

6.0 Enabling JDeveloper Extensions

Before you can use an extension in JDeveloper, you first need to download the extension from OTN. An example of available JDeveloper Extensions is JUnit.

To automatically download and install a JDeveloper extension:

• From the JDeveloper main menu, select Help | Check for Updates.
  This menu option lists extensions that you don't have, lists newer versions of ones you have, and downloads them after you select them. After you restart JDeveloper, you will be able to use the extension.

To manually download a JDeveloper Extension:

1. Go to http://www.oracle.com/technology/products/jdev/htdocs/partners/addins/exchange/index.html.
2. Select a JDeveloper Extension.
3. Follow the instructions to download the zip file.

To manually install a JDeveloper extension:

1. Verify if there are additional installation instructions in the extension archive.
2. From the JDeveloper main menu, select Help | Check for Updates.
3. On Step 1 of the wizard, select Install from a Local File and navigate to the ZIP file.
4. Finish the wizard and restart JDeveloper. After you restart JDeveloper, you will be able to use the extension.

For additional information, see the "Extending JDeveloper" topics in the online documentation, which you can access by choosing Help | Table of Contents from the JDeveloper main menu.

7.0 Setting the User Home Directory

This section provides instructions on how to define a user home environment variable and set its value for each user in order for JDeveloper to identify user home directories correctly.

The user home directory contains the user's preferences for JDeveloper (in the system subdirectory). It is also the default location for new projects (in the C:\JDeveloper\mywork\ directory) as well as other configuration files that are specific to a given user.

To define the name of the user home environment variable:

1. Open the file <jdev_home>\jdev\bin\jdev.boot in a text editor. Use an editor that recognizes UNIX end-of-line characters, such as WordPad.
   
2. Find the entry:

ide.user.dir.var = JDEV_USER_HOME, JDEV_USER_DIR
   
   This is the default variable that JDeveloper will look for at startup. You can define or add any environment variable that JDeveloper should use. As the terminal server administrator, you may change the name of this variable to follow your system's naming conventions.
   
   

   Note: You can explicitly set the home environment variable by adding the following line in the jdev.boot file: ide.user.dir = <Path to preferred user directory> The output should look something like this: ide.user.dir = D:/users/jdoe

   
   
3. Save the file. If you are using WordPad, it will warn you that it is about to save the file in text-only format. You can ignore this warning.

The user home directory can also specified from the command line using this command:

jdev.exe -J-Dide.user.dir=<Path>

Example: jdev.exe -J-Dide.user.dir=D:/users/joe

7.1 Setting the Home Environment Variable on Windows

To set the home environment variable on Windows systems:

1. From the Windows Start menu, choose Control Panel | System.
2. Select the Advanced tab, then click Environment Variables.
3. In the User Variables section, click New.
4. Add JDEV_USER_DIR, or the name you chose for ide.user.dir.var, as a user variable.
5. Set the value of this variable to your home directory (e.g., N:\users\jdoe), and click OK.
6. To check your variable setting, open a command shell and enter:

   set

   You should see output similar to the following:

   JDEV_USER_DIR=N:\users\jdoe

7. Launch JDeveloper.
8. Choose Help | About to verify that the value of ide.user.dir is set to your user home directory.

For information on the new default directory structure for Windows in this release of JDeveloper, see User Directories on Windows.

7.2 Setting the Home Environment Variable on Linux and UNIX

Follow the steps below to set the environment variable on Linux and UNIX systems. The examples and syntax provided refer to the C Shell.

1. In your startup configuration file (for example, .cshrc), set the environment variable to your preferred directory:

   setenv JDEV_USER_DIR $HOME/mydocs/jdevfiles

2. Source the file to make your changes take effect:

   source .cshrc

3. Display the environment variable to confirm the change:

   echo $JDEV_USER_DIR

   You should see output similar to the following:

   /home/jdoe/mydocs/jdevfiles

4. Launch JDeveloper.
5. Choose Help | About to confirm that the value of ide.user.dir is set to your user home directory.

By default, the user home directory on Linux and UNIX is $HOME/jdevhome.

7.3 Setting the Home Environment Variable on Mac OS X

Follow the steps below to set the environment variable on Mac OS X systems. The examples and syntax provided refer to the BASH shell.

1. In your startup configuration file (for example, .bashrc), set the environment variable to your preferred directory:

   JDEV_USER_DIR=$HOME/mydocs/jdevfiles

2. Export the new value of the environment variable:

   export JDEV_USER_DIR

3. Source the file to make your changes take effect:

   . .profile

4. Display the environment variable to confirm the change:

   echo $JDEV_USER_DIR

   You should see output similar to the following:

   /Users/jdoe/mydocs/jdevfiles

5. Launch JDeveloper.
6. Choose Help | About to confirm that the value of ide.user.dir is set to your user home directory.

By default, the user home directory on Mac OS X is $HOME/jdevhome.

Back to TOC

8.0 Using JDeveloper in a Multiuser Environment

If you are using JDeveloper on Linux or UNIX, you will have to set permissions on directories and files. See Modifying Permissions on Linux and UNIX Platforms for more information.

You can install JDeveloper in Microsoft Terminal Server, Citrix MetaFrame and MetaFrame XP (for Windows), and MetaFrame 1.1 for UNIX environments. These environments allow many clients to access one installation of JDeveloper. In all cases, users can save their projects locally.

When installing and configuring JDeveloper for a multiuser environment, you'll need to account for resource planning, such as number of users and power of the server to deliver optimal performance for JDeveloper and your users.

8.1 Installing JDeveloper on a Citrix MetaFrame Server or a Microsoft Terminal Server

You need to have administrative privileges to install JDeveloper.

To Install JDeveloper on a Citrix MetaFrame or Microsoft Terminal Server:

1. Install JDeveloper as described in Installing and Starting JDeveloper on Windows.
2. Define the user home directory environment variable (see below).

8.2 Configuring User Home Directories in a Multiuser Environment

Before you run JDeveloper in a terminal server environment, you may want to define the user home environment variable and set its value for each user, in order for JDeveloper to identify user home directories correctly. If the variable is not defined and set, JDeveloper uses the %APPDATA%\.jdeveloper directory for each user for storing system settings, and C:\JDeveloper\mywork as the default user source directory for all users. See Setting the User Home Directory for instructions specific to configuring user home directory environment variables.

8.3 Configuring Terminal Server Clients for Running JDeveloper

These topics assume that you have already installed a Citrix MetaFrame or Microsoft Terminal Server client locally and that JDeveloper has been installed and configured by the system administrator.

1. Verify that the color resolution of the terminal server client has been set to a minimum of 256 colors. This minimum resolution is required by Java JDK 5.0.
2. Log on to your terminal server.
3. Verify that the user home environment variable has been defined: Ask your system administrator for the naming convention that is used on your system. The default variable is JDEV_USER_DIR.
4. Set the user home environment variable, as described in Setting the Home Environment Variable on Windows.
5. Launch JDeveloper.
6. JDeveloper will ask if you would like your user home directory to be created. Select Yes.
7. Choose Help | About to verify that the value of ide.user.dir is set to your user home directory.

If you run JDeveloper in a multiuser environment and you see the error

The system DLL ole32.dll was relocated in memory. The application will not run properly. The relocation occurred because the DLL Dynamically Allocated Memory occupied an address range reserved for Windows NT system DLL's. The vendor supplying the DLL should be contacted for a new DLL.

you'll need to update the <jdev_home>\jdev\bin\jdev.conf file by uncommenting the line:

AddVMOption -Xheapbase100000000

Use an editor that recognizes UNIX end-of-line characters, such as WordPad. You may have to change the number upward or downward if you still get the error when starting JDeveloper. When you save the file, WordPad will warn you that it is about to save the file in text-only format. You can ignore this warning.

In addition, each user must modify the default project to apply this setting. To specify this value in the default project settings:

1. Select Tools | Default Project Properties.
2. In the Default Project Properties dialog, click Run/Debug/Profile, and then click Edit.
3. Click the Launch Settings node.
4. On the Launch Settings page, enter -Xheapbase100000000 in the Java Options field.

Back to TOC

9.0 Using OC4J with JDeveloper

JDeveloper is pre-packaged with Oracle Containers for J2EE (OC4J), which you can use for testing your Java EE applications. In this technical preview release, the pre-packaged OC4J can be used in one of 4 modes, depending on your requirement.

For an explanation of the different modes, please refer to the Release Notes. For additional information on using OC4J with JDeveloper, please refer to the Help topic "Connecting and Deploying to OC4J Application Servers" in the online documentation.

Back to TOC

10.0 Application Servers Supported by JDeveloper

This technical preview release of JDeveloper has been tested only with the following:

• Integrated OC4J
• The embedded OC4J server within JDeveloper
• Standalone OC4J Technology Preview 4

Back to TOC

11.0 Database Certification for JDeveloper

This technical preview release of JDeveloper has been tested only with the following:

• Oracle Database 10g Express Edition
• Oracle Database 10g Enterprise Edition
• Oracle Database 11g Enterprise Edition

Back to TOC

12.0 Web Browsers Supported by JDeveloper

JDeveloper supports the following web browsers:

• IE 6.0
• IE 7.0
• Firefox 1.5
• Firefox 2.0
• Safari 2.x (Mac-Specific)

Back to TOC

13.0 Finding JDeveloper Accessibility Information

For the latest configuration information or for information on addressing accessibility and assistive technology issues, see the Oracle Accessibility FAQ at http://www.oracle.com/accessibility/faq.html. Also, see the help topics available by selecting the JDeveloper Accessibility Information node under Getting Started with Oracle JDeveloper in the online help table of contents.

Back to TOC

14.0 Using a Screen Reader and Java Access Bridge with JDeveloper

To make the best use of our accessibility features, Oracle Corporation recommends the following minimum technology stack:

• Windows NT 4.0 (with Service Pack 6), Windows 2000, or Windows XP
• Java Sun J2SE 1.5.0_05
• Sun Java Access Bridge 2.0.1
• JAWS 7.0+
• Microsoft Internet Explorer 5.5 or higher

Please refer to the following information to set up a screen reader and Java Access Bridge. If you are using JAWS 7.00.135U, please refer to the additional configuration information provided below the procedure.

1. Install the screen reader, if it is not already installed.

   Refer to the documentation for your screen reader for more information about installation.

2. Install JDeveloper.

   Refer to the Installation Guide for more information about installing JDeveloper.

3. Download Java Access Bridge for Windows version 2.0.1. The file you will download is accessbridge-2_0_1.zip. It is available from:
   http://java.sun.com/products/accessbridge.

   Refer to the Java Access Bridge documentation available from this web site for more information about installation and the Java Access Bridge.

4. After downloading the file, extract (unzip) the contents to a folder, for example, accessbridge_home.
5. Install Java Access Bridge by running Install.exe from the <accessbridge_home>\installer folder.

   The installer first checks the JDK version for compatibility, then the Available Java virtual machines dialog displays.

6. Click Search disks. Then select to search only the drive that contains the JDeveloper build and the JDK version in the program files directory (if it exists).

   The search process can take a long time on a large disk with many instances of JDK or JDeveloper, or when searching multiple disks. However, unless you complete an exhaustive search of your disk, Access Bridge will not be optimally configured, and will not be correctly installed to all of the Java VMs on your system. After selecting the disk to search, click Search.

7. Confirm that you want to install the Java Access Bridge into each of the Java virtual machines displayed in the dialog, by clicking Install in All.
8. Click OK when you see the Installation Completed message.
9. Confirm that the following files have been installed in the Winnt\System32 directory (or the equivalent Windows 2000 or XP directory), or copy them from <accessbridge_home>\installer\installerFiles as they must be in the system path in order to work with JDeveloper:

   JavaAccessBridge.dll
JAWTAccessBridge.dll
WindowsAccessBridge.dll

   Note that the system directory is required in the PATH system variable.

10. Confirm that the following files have been installed in the <jdev_home>\jdk\jre\lib\ext directory, or copy them from <accessbridge_home>\installer\installerFiles:

    access-bridge.jar
jaccess-1_4.jar

11. Confirm that the file accessibility.properties has been installed in the <jdev_home>\jdk\jre\lib directory, or copy it from <accessbridge_home>\installer\installerFiles. Confirm that the file accessibility.properties includes the following three lines:

    assistive_technologies=com.sun.java.accessibility.AccessBridge
AWT.EventQueueClass=com.sun.java.accessibility.util.EventQueueMonitor
AWT.assistive_technologies=com.sun.java.accessibility.AccessBridge

12. Start your screen reader.
13. Start JDeveloper by running the file jdev.exe located in the folder <jdev_home>\jdev\bin.

The steps above assume you are running Windows and using a Windows-based screen reader. A console window that contains error information (if any) will open first and then the main JDeveloper window will appear, once JDeveloper has started. Any messages that appear will not affect the functionality of JDeveloper.

14.1 Configuring JAWS 7.0 and Access Bridge with JDeveloper

The following combinations of Access Bridge file versions are necessary to achieve optimal functionality with JAWS 7.0. Also required in the system32 directory is a copy of the latest version of the Access Bridge jar file.

Access Bridge v. 2.0.1 Configuration for JDeveloper

Place the following files in the JDeveloper directory [\jdk\jre\lib\ext]:

Place the following file in the JDeveloper directory [\jdk\jre\lib]:

Place the following files in the Windows system32 directory [\winnt\system32]:

Back to TOC

15.0 Uninstalling JDeveloper

To uninstall JDeveloper, remove the entire JDeveloper installation directory. No other action is necessary.

Back to TOC

16.0 Oracle on the Web

Oracle provides a number of resources on the Web. These are some sites you may find helpful:

Back to TOC