Oracle® Fusion Middleware

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

The following tables list the recommended CPU, memory, display, and hard drive requirements for the different operating systems:

• Table 1, "Recommended CPU, Memory, Display, and Hard Drive Requirements for Windows"

• Table 2, "Recommended CPU, Memory, Display, and Hard Drive Requirements for Linux"

• Table 3, "Recommended CPU, Memory, Display, and Hard Drive Requirements for MAC OS X"

The following table lists the recommended CPU, memory, display, and hard drive requirements for the Windows operating system:

The following table lists the recommended CPU, memory, display, and hard drive requirements for the Linux operating system:

The following table lists the recommended CPU, memory, display, and hard drive requirements for the Mac OS X operating system:

3.1 Before You Begin

Before you run the generic installer, ensure that the following prerequisites are satisfied:

• You must have JDK 6.0 Update 24 or later installed on your system. If you don't have JDK 6.0 Update 24 installed, you can obtain it from: http://www.oracle.com/technetwork/java/javase/downloads/index.html.

• To streamline your installation process, the JDK you wish to use with the product should be the one you use to start the installer program. In that case, be sure the desired JDK is the first one in your system PATH, or reference it explicitly on the command line.

• If the JDK you use to launch the installer doesn't meet the minimum product requirements, you will be given the opportunity to browse for one during the installation process.

3.2 Launching the Installer

Depending on the type of installer you are using, you can begin the installation process in one of the following ways:

• To launch the platform-independent installer, enter: java -jar jdevstudio11120install.jar.

• To launch the Windows installer, double-click the jdevstudio11120install.exe file.

• To launch the Linux installer, follow these steps:

  1. Ensure that the jdevstudio11120install.bin file is executable: chmod +x jdevstudio11120install.bin.

  2. Execute the file: ./jdevstudio11120install.bin.

You can also launch the installer in silent mode, to ensure that no configuration options are displayed during the installation process. For more information, see Section 13.1, "Installing Oracle JDeveloper Studio in Silent Mode".

3.3 Installer Screens

The installer provides several screens that allow you to specify various parameters for the installation:

1. Welcome

   Click Next to begin the installation process.

2. Choose Middleware Home Directory

   You can create a new Middleware Home directory, or select one from a list of existing Middleware Home directories. If you choose a directory that already has Oracle JDeveloper and Oracle WebLogic Server components installed on it, you are taken directly to the Choose Products and Components screen to select additional components to install.

   If you choose to create a new Middleware Home directory, the default provided is C:\Oracle\Middleware\ for Windows, and $HOME/Oracle/Middleware/ for Linux and Unix platforms.

   Caution:

   Ensure that you choose a directory that does not contain spaces. For example, do not use C:\Program Files as the Middleware Home.

   Notes:

   • The JDeveloper component should always be installed in new Middleware Home. The only component in the Oracle installer that can be installed into an existing Middleware Home is the Application Development Framework, and that should not be done if ADF has already been installed on the system by other Oracle Fusion Middleware products.

   • For the remainder of this document, in the context of the Studio Edition, MW_HOME has been used to represent the Middleware Home directory that you have chosen. For example, if you selected C:\Oracle\ as your Middleware Home directory, then MW_HOME would refer to C:\Oracle\.

3. Choose Install Type

   Select either Complete or Custom depending on the type of installation you want to perform. Selecting Complete will install Oracle JDeveloper Studio, Application Development Framework Runtime, and Oracle WebLogic Server on your system. For more information about the Oracle WebLogic Server components that are installed in the complete installation, see the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

   Selecting Custom takes you to the Choose Products and Components screen, where you can select the components you want to install.

4. Choose Products and Components (Custom Install only)

   Select the components you wish to install. If you deselect a component that is needed by other components, those are deselected as well. For more information about Oracle WebLogic Server components, see Oracle Fusion Middleware Getting Started With Installation for Oracle WebLogic Server.

   Notes:

   • If you choose to not install the Application Development Framework Runtime component, you can still run ADF applications by installing Oracle Application Developer, which provides the ability to configure standalone ADF applications on Oracle WebLogic Server in an environment managed by Oracle Enterprise Manager. For more information, see Section 12.2, "Configuring Oracle WebLogic Server for ADF".

   • If some components are already installed in your Middleware Home directory, they will appear grayed out on this screen.

5. JDK Selection (Generic Installer only)

   If you did not launch the generic installer with the JDK you wish to use for the product, or the one you launched it with does not meet the minimum requirements, you may select the location of your desired JDK now. Navigate to your JDK directory that contains the child folder bin, which in turn contains java.exe. For example, if the path for your java.exe is C:\JDK\jdk1.6.0_24\bin\java.exe, you should select C:\JDK\jdk1.6.0_24.

6. Confirm Product Installation Directories

   View the directories that the components will be installed in. To make changes, click Back and navigate to the desired screen, or click Next to continue with the installation.

   Note:

   In addition to the disk space required by the components you have chosen to install, the installer needs 684MB of temporary work space. If there is insufficient disk space on your system, a dialog will appear informing you about it. You can then either free up space in your desired location, or click Previous and choose an alternate location on the Choose Middleware Home Directory screen.

7. Install Windows Service (Windows systems only)

   Select to install the Node Manager Service. Node Manager is used to monitor, start, and stop server instances in a domain. For more information, see the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

   Note:

   JDeveloper and ADF do not require the use of the Node Manager Service.

8. Choose Shortcut Location (Windows systems only)

   Select the Start Menu folder where you want to place your shortcuts. You can select one of the following options:

   • "All Users" Start Menu folder

     Select this option to provide all users registered on this machine with access to installed software. Only users with Administrator privileges can create shortcuts in the All Users folder.

   • Local user's Start Menu folder

     Select this option to ensure that other users registered on this machine will not have access to the Start menu entries for this installation.

9. Installation Summary

   Displays the components that will be installed and total disk space that will be utilized.

10. Installation status

    Displays the progress of the installation.

11. Installation Complete

    Select Run Quickstart to open the Quickstart window once the installation process has ended. Quickstart enables you to easily launch installed components and access online documentation.

    Click Done to end the installation process.

    Note:

    Should the installation process be interrupted prior to completion, the result is likely an incomplete and non-functional partial installation. If this occurs, the recommended approach is to attempt to uninstall the previous installation. If that is successful, you can re-install normally, otherwise you should re-install into a new middleware home.

3.4 Verifying Your Installation

To view information about which products and components were installed, open the registry.xml file, located at: MW_HOME/registry.xml.

5.1 Starting JDeveloper

To start Oracle JDeveloper Studio on Windows, use any of the following methods:

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

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

  • MW_HOME\jdeveloper\jdeveloper.exe

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

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

5.2 Specifying the JDK location

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 the Java executable, for example D:\jdk1.6.0_24\bin.

5.3 Changing the JDK location

To change a JDK location that you have previously specified, set the variable SetJavaHome in the file MW_HOME\jdeveloper\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 is in a directory called jdk1.6.0_24 on your D: drive, your entry in jdev.conf would look like:

SetJavaHome d:\jdk1.6.0_24

5.4 User Directories

The following list describes the default directory structure within JDeveloper on Windows:

• The default location for the system subdirectory is %APPDATA%\JDeveloper\system11.1.2.0.XX.XX.XX, where XX.XX.XX is the unique number of the product build.

• The default location for user-generated content is:

  • C:\Users\user\Documents\JDeveloper\mywork on Windows 7 systems.

  • C:\JDeveloper\mywork on all other Windows platforms.

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

6.1 Changing System Cursors

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 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 at:

   MW_HOME/jdeveloper/jdev/bin/clear_cursors.tar

6.2 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:

• /bin/sh -c 'ulimit -n'

If the value returned is less than 4096, you set the system resource limit:

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

2. Look for the following lines:

   *      soft nofile <value>
   *      hard nofile <value>
   

3. In the lines, change the value to 4096. The lines will then read:

   *      soft nofile 4096
   *      hard nofile 4096
   

   Note:

   In case the lines listed in Step 2 do not exist, add the lines listed in Step 3 to the limits.conf file.

6.3 Starting JDeveloper

To start JDeveloper on Linux and UNIX, run the file MW_HOME/jdeveloper/jdev/bin/jdev.

6.4 Specifying the JDK location

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 the Java executable, for example /usr/local/java/bin/java.

6.5 Changing the JDK location

To change a JDK location that you have previously specified, set the variable SetJavaHome in the file MW_HOME/jdeveloper/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

7.1 Starting JDeveloper

To start JDeveloper, run the file MW_HOME/jdeveloper/jdev/bin/jdev.

7.2 Specifying the JDK location

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 the Java executable, for example /usr/local/java/bin/java.

7.3 Changing the JDK location

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

For example, in a Mac OS X 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

8.1 Migrating User Settings

When you start JDeveloper for the first time (and each time after adding a new extension or making an upgrade), JDeveloper will display the Confirm Import Preferences dialog to ask whether to import your preferences and settings from a previous installation.

On the Confirm Import Preferences dialog, click Show All Installations to view a list of all previous installations. From this list, choose the installation that you want to import preferences and settings from. Hovering over a particular installation displays the path to the installation as a tooltip. Alternatively, you can click the Find a previous installation manually button (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 JDeveloper to display the Confirm Import Preferences dialog, use the -migrate flag when starting Oracle JDeveloper from the command line, for example, jdev -migrate.

8.2 Migrating Projects

When you open an application or project that was created in a prior release, JDeveloper will prompt to migrate the project to JDeveloper 11g. Depending on the content of the projects, JDeveloper may display additional prompts to migrate some specific source files as well. Oracle recommends that you make a backup copy of your projects before migrating. See the Oracle JDeveloper page on OTN for more information about migrating specific types of projects to 11g.

10.1 Setting the Home Environment Variable on Windows

To set the home environment variable on a Windows systems, including individual users of JDeveloper on a multiuser system, use the following steps:

1. From the Windows Start menu, select Control Panel, and then select 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 (for example, 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. From the Help menu, select About to verify that the value of ide.user.dir is set to your user home directory.

10.2 Setting the Home Environment Variable on Linux and UNIX

Use the following steps 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. From the Help menu, select About to verify 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.

10.3 Setting the Home Environment Variable on Mac OS X

Use the following steps 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. From the Help menu, select About to verify 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/jdeveloper.

11.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.

2. Define the user home directory environment variable as instructed in Section 11.2, "Configuring User Home Directories in a Multiuser Environment" and in Section 11.3, "Configuring Terminal Server Clients for Running JDeveloper".

11.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 MW_HOME\JDeveloper\system\ directory for each user for storing system settings, and C:\JDeveloper\mywork as the default user source directory for all users. See Section 10, "Setting the User Home Directory" for instructions on how to configure user home directory environment variables.

11.3 Configuring Terminal Server Clients for Running 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 JDeveloper:

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 6.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 Section 10.1, "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. Click Yes.

7. From the Help menu, select 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 will need to update the MW_HOME\jdeveloper\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. 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.

12.1 Using the Integrated Oracle WebLogic Server

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. JDeveloper manages the Integrated WebLogic Server lifecycle for testing your application. The first time Integrated WebLogic Server is needed, 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 JDeveloper system directory.

12.2 Configuring Oracle WebLogic Server for ADF

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.

To prepare Oracle WebLogic Server for running ADF applications:

1. Install Oracle WebLogic Server 11g Release 1 (10.3.5). Use Oracle Installer to install at least the Oracle WebLogic Server Core Application Server and Configuration Wizard and Upgrade Framework components. You can install Oracle WebLogic Server 11g Release 1 (10.3.5) using any Oracle distribution media.

   For more information about installing Oracle WebLogic Server, see the following documentation:

   • Oracle Fusion Middleware Getting Started With Installation for Oracle WebLogic Server.

   • Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

2. Add ADF runtime libraries to the Oracle WebLogic Server environment. This step provides the necessary patches to Oracle WebLogic Server for ADF, and copies the ADF runtime jar files and domain templates to the server environment. Add the ADF Runtime in one of the two following ways:

   • If you did not install the Application Development Framework Runtime component during installation of Oracle WebLogic Server, you can do so by running Oracle Installer as described in Section 3.2, "Launching the Installer". Perform a custom installation, and install the ADF Runtime component into the existing Oracle WebLogic Server home.

   • Run the Oracle Fusion Middleware 11g Application Developer Installer, which is available through any of the Oracle Fusion Middleware distribution media, and install the ADF runtime to the existing Oracle WebLogic Server home. Oracle Application Developer provides the ability to run standalone ADF applications in a server environment managed by Oracle Enterprise Manager. For more information about the Oracle Fusion Middleware 11g Application Developer Installer, see the Oracle Fusion Middleware Installation Guide for Application Developer.

   For more information about adding the ADF runtime libraries to a stand-alone Oracle WebLogic Server, see the "Installing the ADF Runtime to the WebLogic Installation" section in the "Deploying Fusion Web Applications" chapter in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

3. Configure a new or existing domain for ADF runtime. Before deploying an ADF application to Oracle WebLogic Server, you must configure a domain for ADF runtime. Use the WebLogic Configuration wizard to create a new domain configured automatically to support Application Development Framework Runtime or to extend an existing domain with the ADF runtime domain templates.

   For more information about configuring Oracle WebLogic Server domains and preparing a domain for running ADF applications, see the following documentation:

   • Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

   • The "Creating and Extending WebLogic Domains" section in the "Deploying Fusion Web Applications" chapter in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

13.1 Installing Oracle JDeveloper Studio in Silent Mode

Silent-mode installation is a way of setting installation configurations only once to ensure that no configuration options are displayed during the installation process. During installation in silent mode, the installation program reads the settings for your configuration from an XML file that you create before beginning the installation.

To install in silent mode:

1. Create a silent.xml file that defines the configuration settings that will be used for the installation. See Section Section 13.1.1, "Creating the silent.xml file" for more information.

2. Start the silent installation by using the following command:

   java -jar jdevstudio11120install.jar -mode=silent -log=install.log

   The -log=install.log argument maintains a log of the installation in the install.log file. Information contained in the log file helps you investigate installation failures.

   Note:

   To use a silent.xml file in a location other than the directory in which Oracle Installer resides, also use the additional argument -silent_xml=<your_location>\silent.xml.

<?xml version="1.0" encoding="UTF-8"?>
<bea-installer>
    <input-fields>
        <data-value name="BEAHOME" value="C:\Oracle\Middleware"/>
        <data-value name="COMPONENT_PATHS" value="JDeveloper and ADF/JDeveloper Studio|JDeveloper and ADF/Application Development Framework Runtime"/>
        <data-value name="LOCAL_JVMS" value="C:\jdk\jdk1.6.0_24\"/>
        <data-value name="INSTALL_SHORTCUT_IN_ALL_USERS_FOLDER" value="false"/>
    </input-fields>
</bea-installer>

13.2 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 configuration:

• Windows XP, Windows Vista

• Java J2SE 1.6.0_24

• Java Access Bridge 2.0.1

• JAWS 12.0.522

• Microsoft Internet Explorer 7.0 or later

• Mozilla Firefox 3.5 or later

Please refer to the following procedures to set up a screen reader and Java Access Bridge.

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.

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

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://www.oracle.com/technetwork/java/javase/tech/index-jsp-136191.html.

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

4. 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 XP or Vista directory), or copy them from <accessbridge_home>\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 MW_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 JDeveloper by running the file jdev.exe located in the folder MW_HOME\jdeveloper\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.

13.3 Finding 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/us/corporate/accessibility/faqs/index.html. Also, see the Oracle JDeveloper Accessibility Information chapter in the Oracle Fusion Middleware User's Guide for Oracle JDeveloper.