Fusion Middleware Documentation
Advanced Search


Installing Oracle JDeveloper
Close Window

Table of Contents

Show All | Collapse

3 Next Steps After Installing Oracle JDeveloper Studio

This chapter describes the steps that you need to follow after installing Oracle JDeveloper.

This chapter contains the following sections:

3.1 Preparing to Launch Oracle JDeveloper

This section describes tasks that you may want to perform after installing Oracle JDeveloper. This section describes the tasks for Linux, Windows, and multiuser environments.

The section is divided into the following topics:

3.1.1 Optimizing Oracle JDeveloper on Linux, UNIX, and Mac OS X

This section describes tasks that you may want to perform after installing Oracle JDeveloper on Linux, UNIX, or Mac OS X.

It contains the following topics:

3.1.1.1 Setting the System Resource Limit

The minimum recommended system resource limit for Oracle JDeveloper on Linux systems is 4096.

To determine the resource limit configuration for your system, enter the following command:

/bin/sh -c 'ulimit -n'

If the value returned is less than 4096, set the system resource limit by following these steps:

  1. Open the limits.conf file, which is located at /etc/security/.

  2. Find the following parameters:

    soft nofile value_of_the_parameter
    hard nofile value_of_the_parameter
    
  3. Change the value of these parameters to 4096:

    soft nofile 4096
    hard nofile 4096
    

    Note:

    If the parameters listed in Step 2 do not exist, add the parameters with their values as listed in Step 3 to the limits.conf file.

3.1.1.2 Setting the User Home Directory on Linux, UNIX, and Mac OS X

This section describes how to permanently redefine the location of your user home directory using the home environment variable in a Linux, UNIX, or Mac OS X environment.

When you define the user home directory, it will contain a system subdirectory that stores the user's preferences for JDeveloper, also known as the domain home. The user home directory will also contain a separate subdirectory for user-generated content and other configuration files that are specific to a given user, also known as the application home.

If you do not define a user home directory, these subdirectories will be located in different parts of your computer.

  • The default location for the system subdirectory is $HOME/.jdeveloper/system12.1.3.XX.XX.XX, where XX.XX.XX is the unique number of the product build.

  • The default location for user-generated content is $HOME/jdeveloper/mywork.

There are two ways to set your user home directory if you do not want your JDeveloper files to be stored at $HOME. Both methods will set the user home directory for all instances of JDeveloper on your system.

You only need to use one of the following methods to set the user home directory:

Editing product.conf

Starting in 12c (12.1.3), many JDeveloper settings, including the location of your JDK, are stored in product.conf. This file is created by JDeveloper on first startup unless the file already exists from a previous installation. JDeveloper will use the settings stored in product.conf even if they are from a previous installation.

Note:

In previous versions of JDeveloper, product.conf was named jdev.conf.

  1. Find the product.conf file. It should be located at $HOME/.jdeveloper/12.1.3.0.0.

  2. Open product.conf in an editor. Add a line to set AddVMOption -Dide.user.dir to your preferred directory path.

    For example, if your preferred directory is $HOME/mydocs/jdevfiles, your definition should look like this:

    AddVMOption -Dide.user.dir=$HOME/mydocs/jdevfiles
    

    Caution:

    Do not set the home environment variable to a directory that contains spaces. For example, do not specify $HOME/my projects as the home directory.

  3. Save your changes. The changes should take effect immediately when you start JDeveloper. The changes made to product.conf will also override any environment variable you have defined.

    When you launch Oracle JDeveloper for the first time, you can verify that the user home directory has been set to your preferred directory by accessing the Help menu, selecting About from the drop-down menu, toggling the Properties tab, and finding the definition for ide.user.dir.

Setting environment variable JDEV_USER_DIR

This is another way of setting the user home directory. You can set the environment variable JDEV_USER_DIR to your preferred directory path. The examples and syntax provided below are for the bash shell on Linux systems.

  1. Open your startup configuration file with an editor. For the bash shell, this file is named .bashrc. The configuration file should be located in your home directory. If the appropriate file for your shell does not exist at this location, create a new file.

  2. Set the environment variable JDEV_USER_DIR to your preferred directory.

    For example, if your preferred directory is $HOME/mydocs/jdevfiles, your definition may look like this:

    export JDEV_USER_DIR=$HOME/mydocs/jdevfiles
    

    Caution:

    Do not set the home environment variable to a directory that contains spaces. For example, do not specify $HOME/my project folder as the home directory.

  3. Save your file and exit the editor. Start a new terminal session.

  4. In the command line, use the following command to display the environment variable to confirm the change:

    echo $JDEV_USER_DIR
    

    This should output the directory you specified. For this example, the command will output the following:

    $HOME/mydocs/jdevfiles
    

When you launch Oracle JDeveloper for the first time, you can verify that the user home directory has been set to your preferred directory by accessing the Help menu, selecting About from the drop-down menu, toggling the Properties tab, and finding the definition for ide.user.dir.

3.1.1.3 Changing the JDK Location in Linux, UNIX, and Mac OS X

This section describes how to permanently change the location of your JDK if it has changed since the first time you launched JDeveloper.

To change a JDK location, do the following steps:

  1. Find the product.conf file. It should be located at $HOME/.jdeveloper/12.1.3.0.0.

  2. Open product.conf in an editor. Find the line that reads like the following:

    SetJavaHome /path/jdk
    

    Uncomment this line. Replace /path/jdk with the path to your JDK directory.

    For example, if the location of your JDK is /usr/local/java, your definition will look like this:

    SetJavaHome /usr/local/java
    

This will set the JDK path for all installations of JDeveloper on your system.

If you deinstall JDeveloper but do not delete the product.conf file, all settings stored in this file, including the JDK path, will be preserved for future installations. If you re-install JDeveloper with the same numerical version as your previous installation, your new installation will automatically read that JDK location again.

3.1.1.4 Changing System Cursors on Linux, UNIX, and Mac OS X

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

To replace the cursors:

  1. Create a backup 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 by following these steps:

    1. Navigate to the following location on your system:

      JDEV_HOME/jdeveloper/jdev/bin/clear_cursors.tar
      
    2. Run the following command to extract the replacement cursors from the tar file:

      tar -xvf clear_cursors.tar
      

3.1.2 Optimizing Oracle JDeveloper on Windows

This section describes tasks that you may want to perform after installing Oracle JDeveloper.

It contains the following topics:

3.1.2.1 Setting the User Home Directory on Windows

This section describes how to permanently redefine the location of your user home directory using the home environment variable in a Windows environment.

When you define a user home directory for JDeveloper, it will contain a system subdirectory that stores the user's preferences for JDeveloper. It will also contain a separate subdirectory for user-generated content and other configuration files that are specific to a given user.

If you do not define a user home directory, these subdirectories will be located in different parts of your computer

  • The default location for the system subdirectory, or domain home, is:

    • %USERPROFILE%\AppData\Roaming\JDeveloper\system12.1.3.XX.XX.XX on Windows 7 systems. XX.XX.XX is the unique number of the product build.

    • %USERPROFILE%\Application Data\JDeveloper\system12.1.3.XX.XX.XX on all other Windows platforms. XX.XX.XX is the unique number of the product build.

  • The default location of the user-generated content, or application home, is:

    • C:\JDeveloper\mywork on Windows 7 systems.

    • C:\Documents and Settings\My Documents\JDeveloper\mywork on all other Windows platforms.

There are two ways to set your user home directory if you do not want your JDeveloper files to be stored at the default location. Both methods will set the user home directory for all instances of JDeveloper on your system.

You only need to use one of the following methods to set the user home directory:

Editing product.conf

Starting in 12c (12.1.3), many JDeveloper settings, including the location of your JDK, are stored in product.conf. This file is created by JDeveloper on first startup unless the file already exists from a previous installation. JDeveloper will use the settings stored in product.conf even if they are from a previous installation.

Note:

In previous versions of JDeveloper, product.conf was named jdev.conf.

  1. Find the product.conf file. It should be located at %USERPROFILE%\AppData\Roaming\JDeveloper\12.1.3.

  2. Open product.conf in an editor. Add a line to set AddVMOption -Dide.user.dir to your preferred directory path.

    For example, if your preferred directory is N:\users\jdoe, your definition should look like this:

    AddVMOption -Dide.user.dir=N:\users\jdoe
    

    Caution:

    Do not set the home environment variable to a directory that contains spaces. For example, do not specify C:\My Projects as the home directory.

  3. Save your changes. The changes should take effect immediately when you start JDeveloper. The changes made to product.conf will also override any environment variable you have defined.

    When you launch Oracle JDeveloper for the first time, you can verify that the user home directory has been set to your preferred directory by accessing the Help menu, selecting About from the drop-down menu, toggling the Properties tab, and finding the definition for ide.user.dir.

Setting the environment variable JDEV_USER_DIR

This is another way of setting the user home directory. To set the home environment variable on a Windows systems, including individual users of Oracle JDeveloper on a multiuser system, you need to edit the value of JDEV_USER_DIR.

Do the following:

  1. From the Windows Start menu, select Control Panel, and then select System.

  2. Click Advanced system settings, then click Environment Variables.

  3. In the User Variables section, click New.

  4. Add JDEV_USER_DIR as a user variable.

  5. Set the value of this variable to your home directory (for example, N:\users\jdoe), and click OK.

    Caution:

    Do not set the home environment variable to a directory that contains spaces. For example, do not specify C:\My Projects as the home directory.

  6. To check your variable setting, open a command shell and enter the following command:

    set

    This will list all of your defined variables. Find and verify that your newly defined variable appears similar to the following:

    JDEV_USER_DIR=N:\users\jdoe

When you launch Oracle JDeveloper for the first time, you can verify that the user home directory has been set to your preferred directory by accessing the Help menu, selecting About from the drop-down menu, toggling the Properties tab, and finding the definition for ide.user.dir.

3.1.2.2 Changing the JDK location on Windows

This section describes how to permanently change the location of your JDK if it has changed since the first time you launched JDeveloper.

Starting in 12c (12.1.3), most JDeveloper settings, including the location of your JDK, are stored in product.conf. This file is created by JDeveloper on first startup unless the file already exists from a previous installation. Your new installation of JDeveloper will use the settings stored in product.conf even if they are from a previous installation.

Note:

In previous versions of JDeveloper, product.conf was named jdev.conf.

To change a JDK location, do the following steps:

  1. Find the product.conf file. It should be located at %USERPROFILE%\AppData\Roaming\JDeveloper\12.1.3.0.0.

  2. Open product.conf in an editor. Find the line that reads like the following:

    SetJavaHome \path\jdk
    

    Uncomment this line. Replace \path\jdk with the path to your JDK directory.

    For example, if the location of your JDK is jdk1.7.0_15 on your D: drive, your definition will look like this:

    SetJavaHome D:\jdk1.7.0_15
    

If you deinstall JDeveloper but do not delete the product.conf file, all settings stored in this file, including the JDK path, will be preserved. If you re-install JDeveloper with the same numerical version as your previous installation, your new installation will automatically read that JDK location again.

3.1.3 Optimizing Oracle JDeveloper in a Multiuser Environment

This section contains information about how 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 Oracle JDeveloper. In all cases, users can save their projects locally.

When installing and configuring Oracle JDeveloper for a multiuser environment, you will 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.

This section contains the following sections:

3.1.3.1 Installing Oracle JDeveloper on a Citrix MetaFrame Server or a Microsoft Terminal Server

You need to have administrative privileges to install Oracle JDeveloper on a Citrix Metaframe Server or a Microsoft Terminal Server.

Run the Oracle JDeveloper installer on your Citrix MetaFrame or Microsoft Terminal Server as detailed in Chapter 2. Do not launch Oracle JDeveloper at the end of installation, as you should configure the user home directories and terminal server clients as described in the following sections.

3.1.3.2 Configuring Terminal Server Clients for Running Oracle JDeveloper

This section assumes 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.

To configure a terminal server client for running Oracle JDeveloper, do the following:

  1. Verify that the color resolution of the terminal server client has been set to a minimum of 256 colors. This minimum resolution is a prerequisite for installing Java JDK 7.0.

  2. Log in to your terminal server.

  3. Verify that the user home environment variable has been defined. Confirm the naming convention that is used on your system. The default variable is JDEV_USER_DIR.

  4. Launch Oracle JDeveloper.

  5. Oracle JDeveloper prompts you to confirm if the user home directory needs to be created. Click Yes.

  6. Verify that the user home directory has been set to your preferred directory by accessing the Help menu, selecting About from the drop-down menu, toggling the Properties tab, and finding the definition for ide.user.dir.

3.1.3.3 Troubleshooting system DLL ole32.dll Memory Error

If you run Oracle JDeveloper in a multiuser environment, you might encounter the following 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.

If you see this error, update the HOME/.jdeveloper/12.1.3.0.0/product.conf file by uncommenting the following parameter:

AddVMOption -Xheapbase100000000

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

  1. From the Application menu, select 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.

3.2 Launching Oracle JDeveloper

To start Oracle JDeveloper, do the following:

On Linux, UNIX, and Mac OS X:

  1. Navigate to the following location on your system:

    JDEV_HOME/jdeveloper/jdev/bin/
    
  2. Run the following command:

    ./jdev
    

On Windows:

From your Start Menu, select All Programs, then select Oracle Fusion Middleware 12.1.3, and then select JDeveloper Studio 12.1.3.

You can also start Oracle JDeveloper from the command line by running one of the following commands:

  • JDEV_HOME\jdeveloper\jdeveloper.exe

  • JDEV_HOME\jdeveloper\jdev\bin\jdevw.exe

  • JDEV_HOME\jdeveloper\jdev\bin\jdev.exe (to display a console window for internal diagnostic information)

3.3 Migrating to Oracle JDeveloper 12.1.3 From a Previous Version

Oracle JDeveloper 12c (12.1.3) supports migration from Oracle JDeveloper 11.1.1.7.0 or 11.1.2.4.0. Oracle recommends migrating to Oracle JDeveloper 11.1.1.7.0 or 11.1.2.4.0 from all other earlier versions before migrating to this release of Oracle JDeveloper.

This section provides more information about migrating from a previous version to Oracle JDeveloper 12c (12.1.3). It contains the following topics:

3.3.1 Migrating User Settings

When you start Oracle JDeveloper for the first time (and each time you add a new extension or upgrade to a newer version), JDeveloper displays the Confirm Import Preferences dialog to confirm whether to import your preferences and settings from a previous installation.

When the Confirm Import Preferences dialog is displayed, click Show All Installations to view a list of all the previous installations. From this list, choose the installation that you want to import preferences and settings from. When you hover the mouse over an item in list, the path to the installation is displayed as a tooltip.

Alternatively, you can click Find a previous installation manually (with the image of a magnifying glass) on the top right of the installation list to browse for an installation manually. Clicking Yes on the Confirm Import Preferences dialog imports user preferences and the state of the IDE from the previous installation.

To force Oracle JDeveloper to display the Confirm Import Preferences dialog upon subsequent startups, use the -migrate flag when starting Oracle JDeveloper from the command line, for example, jdev -migrate.

Note:

If you migrate to 12c (12.1.3)from another version of Oracle JDeveloper, you will need to reinstall the extensions that you want to use. Some extensions for older versions may no longer exist.

For more information on installing extensions, see Section 3.4, "Enabling Oracle JDeveloper Extensions".

3.3.2 Migrating Projects

When you open an application or project that was created in a previous release, Oracle JDeveloper prompts you to migrate the project to Oracle JDeveloper 12c. Depending on the content of the projects, Oracle JDeveloper might display additional prompts to migrate some specific source files as well.

Oracle recommends that you create a backup copy of your projects before migrating them. Accepting the initial prompts to migrate your projects means that JDeveloper will update the format for crucial XML files, but migration does not rewrite or update specific project code. After migration, you should re-test your applications to completely verify that they work.

See the Oracle JDeveloper page on OTN for more information about migrating specific types of projects to 12c.

3.3.2.1 Migrating JSF and JSTL Projects

This version of JDeveloper requires that all projects with JavaServer Faces and JSTL be migrated to the latest versions of the technologies (version 2.0 and 1.2 respectively). Additionally, any web.xml deployment descriptors will be migrated to version 2.5.

For the most current information on migration, see the Oracle JDeveloper documentation page on OTN: http://www.oracle.com/technetwork/developer-tools/jdev/documentation/1212-cert-1964670.html#Abrams-SupportInformation-MigrationSupport.

3.4 Enabling Oracle JDeveloper Extensions

Before you can use an extension in Oracle JDeveloper, you first need to download the extension from the Oracle Technology Network (OTN). An example of an available Oracle JDeveloper Extension is JUnit.

You can find and install extensions from inside Oracle JDeveloper. To do so, follow these steps:

  1. Launch JDeveloper.

  2. Click on Help in the ribbon menu. Choose Check for Updates from the drop-down menu. This will launch an Update wizard.

  3. The first screen of the Update wizard allows you to select sources to check for extensions. Oracle Fusion Middleware Products and Official Oracle Extensions and Updates are selected by default. You can check the other two boxes if you want more options.

    Note:

    Starting in 12c (12.1.3), you can no longer download SOA extensions. You need to use a Quick Start distribution to obtain a version of JDeveloper pre-configured for either SOA Suite or Business Process Management Suite. See "Introducing the Quick Start Distributions" in Installing SOA Suite and Business Process Management Suite Quick Start for Developers for more information.

    Press Next when you have identified and selected your sources.

  4. The Updates screen allows you to select specific extensions, such as JUnit. Check the extensions that you want to install and press Next.

  5. On the License Agreements screen, you need to agree to the license terms for the extensions you selected on the previous screen. Press Next to begin the download.

  6. When the extensions have finished downloading, the wizard will display a summary of the installations or upgrades that you installed. Click Finish to exit the wizard.

  7. You will usually need to restart JDeveloper to finish installing updates. A dialogue box will pop up after you exit the wizard that gives you this option. If you have unsaved work, press No before restarting JDeveloper.

Alternatively, you can manually download and install an Oracle JDeveloper extension from OTN. To do so, follow these steps:

  1. Go to the following link: http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/131167.xml.

  2. Select an Oracle JDeveloper Extension. Make sure that you are selecting extensions for 12c (12.1.3), as there may be different versions of each extension for different versions of JDeveloper.

  3. Follow the instructions to download the zip file.

  4. Verify if there are additional installation instructions in the extension archive.

  5. From the Help menu, select Check for Updates.

  6. In Step 1 of the wizard, select Install from a Local File and navigate to the ZIP file on your system.

  7. Finish the wizard and restart Oracle JDeveloper. After you restart Oracle JDeveloper, you will be able to use the extension.

3.5 Using Oracle WebLogic Server with Oracle JDeveloper

Note:

This section is not applicable to the Java edition of Oracle JDeveloper.

Installing Oracle JDeveloper Studio 12c (12.1.3) also automatically installs Oracle WebLogic Server (12.1.2). Oracle JDeveloper uses this preconfigured installation as the Integrated Oracle WebLogic Server and JDeveloper managed server for testing and debugging your applications from within the IDE. After installing Oracle JDeveloper, all the applications that you need to begin developing, testing and debugging are installed and configured.

For additional information about using a standalone Oracle WebLogic Server instance with JDeveloper, see the Deploying Applications chapter in the Oracle Fusion Middleware User's Guide for Oracle JDeveloper.

3.5.1 Using the Integrated Oracle WebLogic Server

Oracle JDeveloper is bundled with an integrated application server called Integrated WebLogic Server, and a default instance called IntegratedWebLogicServer is defined for it.

All applications are bound, by default, to IntegratedWebLogicServer. Oracle JDeveloper manages the Integrated WebLogic Server lifecycle for testing your application. The first time Integrated WebLogic Server is needed, Oracle JDeveloper creates the DefaultDomain and prompts you to provide the administrative username and password. The location of configuration files for the default domain is the DefaultDomain directory located in the Oracle JDeveloper system directory.

Note:

The Oracle WebLogic Server domain that is created for you during installation, DefaultDomain, is not intended for use outside of the IDE. To deploy ADF applications to a standalone Oracle WebLogic Server, the server must be configured to run ADF applications.

For more information, see "Preparing the Standalone Application Server for Deployment" in Administering Oracle ADF Applications.

The IntegratedWebLogicServer's DefaultDomain uses Java DB. If the IntegratedWebLogicServer fails to create the DefaultDomain, you should search for any preexisting instances of Java DB or Derby Client running in the background and stop them.

3.6 Understanding Oracle JDeveloper Accessibility Information

This section contains the following topics:

3.6.1 Using a Screen Reader and Java Access Bridge with Oracle JDeveloper

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

  • Windows XP, Windows Vista

  • Java J2SE 1.7.0_15

  • Java Access Bridge 2.0.1

  • JAWS 12.0.522

  • Microsoft Internet Explorer 7.0 or higher

  • Mozilla Firefox 3.5 or higher

To set up a screen reader and Java Access Bridge, follow these steps:

Note:

  • These steps apply to machines that have the Windows operating system.

  • You must use a screen reader that is compatible with Windows.

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

    For more information about installation, refer to the documentation for your screen reader.

  2. Install Oracle JDeveloper.

    For information about performing a silent installation, see Section A.1, "Installing Oracle JDeveloper Studio in Silent Mode".

  3. Download Java Access Bridge for Windows version 2.0.1. The latest version of the file is available at the following location: http://www.oracle.com/technetwork/java/javase/tech/index-jsp-136191.html.

    For more information about Java Access Bridge, refer to the Java Access Bridge documentation available on the web site.

  4. Extract the contents of the zip file to a folder, accessbridge_home.

  5. Install Java Access Bridge by running the install.exe file 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 customize your search for only the drive that contain the Oracle JDeveloper build and the JDK version in the program files directory (if it exists).

    The search process can take a long time if the disk that has many instances of JDK or Oracle JDeveloper, or when searching multiple disks. However, unless you complete an exhaustive search of your disk, Access Bridge will not be configured optimally, and will not be correctly installed to all of the Java virtual machines 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 XP or Vista directory), or copy them from accessbridge_home\installerfiles, as they must be in the system path to work with Oracle 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\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 \installerfiles.

  12. Start your screen reader.

  13. Start Oracle JDeveloper by running the file jdev.exe located in the folder JDEV_HOME\jdeveloper\jdev\bin.

A console window that contains error information (if any) is displayed first . The Oracle JDeveloper window appears when Oracle JDeveloper starts up. Any error or warning messages that appear do not affect the functionality of Oracle JDeveloper.

3.6.2 Finding Accessibility Information

For the latest configuration information or for information about addressing accessibility and assistive technology issues, see the Oracle Accessibility FAQ at http://www.oracle.com/us/corporate/accessibility/faqs/index.htm. Also, see the Oracle JDeveloper Accessibility Information chapter in the Oracle Fusion Middleware User's Guide for Oracle JDeveloper.

3.7 Oracle on the Web

Oracle provides a number of resources on the Web. Some sites you might find helpful are listed in Table 3-1, "Oracle on the Web":

Table 3-1 Oracle on the Web

Description URL

Oracle JDeveloper Home Pages

http://www.oracle.com/technetwork/developer-tools/jdev/overview/index.html

Oracle JDeveloper Discussion Forum

http://forums.oracle.com/forums/forum.jspa?forumID=83

Corporate Site

http://www.oracle.com/

Oracle Technology Network

http://www.oracle.com/technetwork/index.html

Oracle Accessibility Site

http://www.oracle.com/us/corporate/accessibility/index.html