Oracle® JDeveloper 10g

Installation Guide

Version 9.0.5.1

March 2004

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 Team Based Development Tools Support
• 2.0 Installing JDeveloper Full Version
• 3.0 Installing JDeveloper Base
  • 3.1 Installing OJVM with a Base Installation on Windows
  • 3.2 Adding Local Documentation to a Base Installation
• 4.0 Installing JDeveloper on Non-Windows Platforms
  • 4.1 Modifying Permissions on Non-Windows
  • 4.2 Configuring the Java SDK in JDeveloper on Non-Windows Platforms
  • 4.3 Font Problems in UNIX
  • 4.4 Cursor Problems on Non-Windows Platforms
  • 4.5 Reusing Mozilla Profile Instance
• 5.0 Configuring JDeveloper to Use Hosted Documentation
• 6.0 Starting JDeveloper
• 7.0 Enabling JDeveloper Extensions
• 8.0 Migrating User Settings from Previous Releases
• 9.0 Required Component Versions for E-Business Integration
  • 9.1 Deploying Activity Modeler Generated Artifacts
• 10.0 Using JDeveloper in a Multi-user Environment
  • 10.1 Installing JDeveloper on a Citrix MetaFrame Server or a Microsoft Terminal Server
  • 10.2 Configuring User Home Directories in a Multi-user Environment
  • 10.3 Configuring Terminal Server Clients for Running JDeveloper
• 11.0 Using OC4J with JDeveloper
• 12.0 Application Servers Supported by JDeveloper
• 13.0 Finding JDeveloper Accessibility Information
• 14.0 Using a Screen Reader and Java Access Bridge with JDeveloper
• 15.0 Uninstalling JDeveloper
• 16.0 JDeveloper Documentation
• 17.0 Oracle on the Web

1.0 JDeveloper System Requirements

This release of JDeveloper is supported on Windows NT, Windows 2000, Windows XP, Linux, Solaris, and HP-UX.

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

Windows

Resource	Recommended
Operating System	Windows 2000-Service Pack 4, Windows NT-Service Pack 6a, Windows XP-Service Pack 1
CPU Type and Speed	Pentium III 866 MHz or faster
Memory	512 MB RAM
Display	65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space	Base Install: 230 MB Complete Install: 375 MB
Java SDK	Sun J2SE 1.4.2_03 for Windows, available at: http://www.javasoft.com.

Linux

Resource	Recommended
Distribution	Red Hat Enterprise Linux 2.1 Red Hat Enterprise Linux 3.0 Red Hat Linux 9.0 SuSE SLES8
CPU Type and Speed	Pentium III 866 MHz or faster
Memory	512 MB RAM
Display	65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space	Base Install: 231 MB Complete Install: 390 MB
Java SDK	Sun J2SE 1.4.2_03 for Linux, available at: http://www.javasoft.com.

Solaris

Resource	Recommended
Operating System	Solaris 2.8, or 2.9 using the CDE window manager
CPU Type and Speed	Sparc 500 MHz or faster
Memory	512 MB RAM
Display	65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space	Base Install: 231 MB Complete Install: 390 MB
Java SDK	Sun J2SE 1.4.2_03 for Solaris (32-bit), available at: http://www.javasoft.com.

HP-UX

Resource	Recommended
Operating System	HPUX 11.0 and 11i
CPU Type and Speed	HP PA-RISC 500 MHz or faster
Memory	512 MB RAM
Display	65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space	Base Install: 231 MB Complete Install: 390 MB
Java SDK	HP J2SE 1.4.2.02 for PA-RISC, available at http://www.hp.com/products1/unix/java/index.html.

1.2 Team Based Development Tools Support

JDeveloper provides integrated support for the following source control systems:

ClearCase

• ClearCase 4.x
• ClearCase 5.x (including ClearCase 2002)

Oracle SCM

• Oracle 9i SCM
• Oracle SCM 10g (9.0.4)

Concurrent Version Support (CVS)

• CVS versions 1.10 to 1.11.14
• CVSNT versions 2.0.26 to 2.0.34

2.0 Installing JDeveloper Full Version

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

The full installation ( jdev9051.zip) includes the Windows version of Sun J2SE 1.4.2_03 and the JDeveloper documentation.

To install JDeveloper from jdev9051.zip:

• Unzip jdev9051.zip in the directory you want to install JDeveloper.
• If you install jdev9051.zip on a UNIX or Linux system, you have to modify jdev.conf to specify the SDK. See Configuring the Java SDK in JDeveloper on Non-Windows Platforms for more information.

Back to TOC

3.0 Installing JDeveloper Base

For quicker download times, you can download the base install ( jdev9051_base.zip):

• The base install requires that you already have 1.4..2_03 of the Sun J2SE on your machine, as the SDK is not included in the base install.
• The base install, by default, does not include JDeveloper documentation. Instead, the base install requires a Web connection to access the documentation or you may separately install the documentation. See Adding Local Documentation to a Base Installation for details.

To install JDeveloper from jdev9051_base.zip:

1. If you don't have Java� 2 Platform, Standard Edition, version 1.4.2_03 installed, you can obtain it from: http://www.javasoft.com.
2. Unzip jdev9051_base.zip in the directory you want to install JDeveloper.
3. Set the variable SetJavaHome in the file <jdev_install>\jdev\bin\jdev.conf to the location of your SDK 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 Sun J2SE 1.4.2_03 is in a directory called j2sdk1.4.2_03 on your D: drive, your entry in jdev.conf would look like:
   
   SetJavaHome d:\j2sdk1.4.2_03

4. In order to use the Profilers and CodeCoach, you will need to install OJVM, the specialized Oracle Java Virtual Machine for JDeveloper. The OJVM will also make the JDeveloper debugger run more quickly. See Installing OJVM on Windows in the next section.
   
   

   Note: The JDeveloper installation includes OJVM, and OJVM can be installed for use with JDeveloper, but this configuration is not supported by Oracle. For information about OJVM on Linux please refer to the JDeveloper Release Notes at: <jdev_install>/jdev/readme.html .

5. If you want to use local documentation with JDeveloper, see Adding Local Documentation to a Base Installation.

3.1 Installing OJVM with a Base Installation on Windows

To use CodeCoach and the Profilers with a base installation you need to install OJVM, the specialized Oracle Java Virtual Machine for JDeveloper. OJVM will also increase the speed of the JDeveloper debugger, and provide automatic deadlock detection and memory debugging features. If you performed the complete installation using jdev9051.zip, OJVM was installed automatically. If you performed the base installation using jdev9051_base.zip, you will need to manually install OJVM into your SDK. The batch file InstallOJVM.bat (provided with JDeveloper) will copy OJVM files into the specified SDK and update the configuration of that SDK. The files are copied into a separate OJVM directory and will not overwrite any of the existing files in the SDK.

To install OJVM with a base installation:

• In <jdev_install>\jdev\bin\ execute the command
  

  InstallOJVM.bat d:\j2sdk1.4.2_03


  where d:\j2sdk1.4.2_03 is the location of your SDK.

3.2 Adding Local Documentation to a Base Installation

To install the documentation set, download jdev9051_doc.zip from http://otn.oracle.com/products/jdev. You can install the documentation into JDeveloper, without any configuration, by extracting the files into <jdev_install> . The <jdev_install>\jdev\doc\ohj directory will be created as well as the <jdev_install>\jdev\tutorials directory.

If you install the documentation into any other local directory, you will need to configure the location in JDeveloper:

1. Start JDeveloper.
2. Select T ools | Preferences from the JDeveloper main menu.
3. In the preferences tree, navigate to Documentation.
4. Select the Use Local Documentation radio button.
5. Set the full path to where the local documentation is installed, which by default is <jdev_install>\jdev\doc\ohj .

4.0 Installing JDeveloper on Non-Windows Platforms

This section provides additional instructions specific to installing JDeveloper on a non-Windows platform. Review these sections of the Installation Guide for general information:

• Installing JDeveloper Full Version
• Installing JDeveloper Base

OJVM, the specialized Oracle Java Virtual Machine enables CodeCoach and Profilers, increases the speed of the JDeveloper debugger, and provides automatic deadlock detection and memory debugging features.. The JDeveloper installation includes OJVM, and OJVM can be installed for use with JDeveloper, but this configuration is not supported by Oracle. For information about OJVM on Linux please refer to the JDeveloper Release Notes at: <jdev_install>/jdev/readme.html .

4.1 Modifying Permissions on a Non-Windows System

All JDeveloper files must have read permissions:

chmod -R g+r <jdev_install>

Users (or groups) must have write and execute permissions for the following files:

• chmod +x <jdev_install>/jdev/bin/jdev
• chmod +x <jdev_install>/jdev/bin/ojc
• chmod +x <jdev_install>/jdev/BC4J/bin/bc4joc4j
• chmod +x <jdev_install>/jdev/bin/start_oc4j
• chmod +x <jdev_install>/jdev/bin/stop_oc4j


In addition, users (or groups) must have write permissions for the following (required for deployment):

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

4.2 Configuring the Java SDK in JDeveloper on Non-Windows Platforms

The complete installation of JDeveloper is configured to use Java Sun J2SE 1.4.2_03 for Windows platforms. If you install JDeveloper on another platform, perform the following steps to configure JDeveloper to use the appropriate SDK.

1. If you don't have Java� 2SE, version 1.4.2_03 installed, install it. You can get a copy for many operating systems from http://www./javasoft.com, or check with your OS vendor where to obtain a copy.
2. Set the variable SetJavaHome in the file <jdev_install>/jdev/bin/jdev.conf to the location of your Java installation.
   

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

4.3 Font Problems in UNIX

If you see an error similar to:

Font specified in font.properties not found [--symbol-medium-r-normal--*-%d-*-*-p-*-adobe-fontspecific]

when starting  JDeveloper in a UNIX, your SDK isn't set up to use the font that is generating the error. JDeveloper, by default, uses the information in the file font.properties included with each SDK. If this file references fonts not available on your computer, you will see the above error (or one like it). To fix this error, you'll either need to install a new font, or change your font.properties file. For information on installing new fonts on your computer, contact your vendor.

4.4 Cursor Problems on Non-Windows Platforms

On UNIX or Linux platforms, the Java cursors 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 Java SDK in order to replace the cursors.

To replace the cursors:

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

   <jdk_install>/jre/lib/images/cursors

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

   <jdev_install>/jdev/bin/clear_cursors.tar

4.5 Reusing Mozilla Profile Instance

When using Mozilla on a non-Windows system, you will need to close the browser each time before running your web application again. You can avoid this problem and reuse your Mozilla profile instance by setting the browser command line with a -remote option.

To reuse a Mozilla profile instance:

1. From the main menu of JDeveloper select Tools | Preferences | Web Browser and Proxy.
2. In the Browser Command Line enter:

   /opt/mozilla/mozilla -remote openURL(${URL}) || /opt/mozilla/mozilla ${URL}

3. Click OK.

5.0 Configuring JDeveloper to Use Hosted Documentation

If you installed jdev9051_base.zip, JDeveloper is pre-configured to use documentation hosted on OTN. Please note that the first launch of the hosted help system may take several minutes to initialize if you are on a low bandwith or high-latency connection.

If you installed jdev9051.zip, JDeveloper is pre-configured to use local documentation. However, you can configure JDeveloper to use the documentation hosted on OTN.

To configure JDeveloper to use documentation hosted on OTN:

1. From the JDeveloper main menu, select Tools | Preferences .
2. Navigate to Documentation.
3. Select the Use Hos ted Documentation on Oracle Technology Network radio button.

6.0 Starting JDeveloper

• To start JDeveloper on Windows, run the file <jdev_install>\jdev\bin\jdevw.exe . You can also run jdev.exe (which is in the same directory) if you want to see a console window for displaying internal diagnostic information.
• To start JDeveloper on other platforms, run the file <jdev_install>/jdev/bin/jdev .

7.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 installs them for you.

To manually download a JDeveloper Extension:

1. Go to http://otn.oracle.com/software/products/jdev/content.html and select JDeveloper Extensions.
2. Select a JDeveloper Extension.
3. Follow the instructions to download the zip file.

To manually install a JDeveloper extension:

1. Shut down any instances of JDeveloper that are running on your machine.
2. Verify if there are additional installation instructions in the extension archive.
3. Unzip the downloaded archive into your <jdev_install>\jdev\lib\ext directory.
4. Restart JDeveloper. After you restart JDeveloper, you will be able to use the extension.

8.0 Migrating User Settings from Previous Releases

Your user settings (system settings, libraries, connections, and projects) from the production release of JDeveloper 9.0.2 can be migrated to this release of JDeveloper. Oracle does not support direct migration from 3.2.3 to 9.0.5.1. If you are running a newly installed version of JDeveloper for the first time you will be prompted with a Migrate User Settings dialog. You can use the dialog migrate your user settings by selecting Yes. If you select No, any settings that you set on the first and subsequent runs will be overwritten if you later run JDeveloper with the -migrate flag provided to open the Migrate User Settings dialog. For information about migration issues, see the topic Migrating to JDeveloper 10g , which you can access by selecting Help | Help Topics | Getting Started with JDeveloper from the JDeveloper main menu.

To migrate user settings from previous installations of JDeveloper:

1. Start JDeveloper at a command line or shell prompt with the -migrate flag:

   jdev -migrate

2. When the Migrate User Settings dialog appears, select a version of JDeveloper to migrate. If the Version dropdown list is empty, click Browse.
3. Browse for the location of the system directory of the source installation of JDeveloper, for example:
   <previous_jdev_install>/jdev/system9.0.3.0.1354 where <previous_jdev_install> is the root directory and 9.0.3.0.1354 represents the previous build version of the installation of JDeveloper you are migrating from. For UNIX users, any previous releases that are discovered will already be included in the dropdown list of the dialog.
4. Select the settings and customizations you want to migrate. Oracle recommends that you select all available options.
5. Click OK. Your user settings are migrated to your latest version of JDeveloper.

9.0 Required Component Versions for E-Business Integration

The versions of components required for E-Business integration are:

• Oracle8i Database (8.1.7)
• Oracle9i Database (9.0.1 or 9.2)
• Oracle Workflow Server 2.6.0 if the hub is an Oracle8i (8.1.7) database
• Oracle 10g Database

• Oracle Workflow Server 2.6.1 if the hub is an Oracle9i (9.0.1) database

• Oracle Workflow Server 2.6.2 if the hub is an Oracle9i (9.2) database
• Oracle Workflow Client 2.6.0 or above

9.1 Deploying Activity Modeler Generated Artifacts

The queue definitions that the E-Business Integration Generator in the Activity Modeler generates for the Oracle Workflow Business Event System are 8.1 compatible queues. If the COMPATIBLE parameter in a database init.ora file is set to a value lower than 8.1, the generated queues cannot be deployed to that database.

10.0 Using JDeveloper in a Multi-user Environment

If you are using JDeveloper in a non-Windows environment, you will have to set permissions on directories and files. See Modifying Permission on a non-Windows System 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, allowing many clients to access one installation of JDeveloper. In all cases, users can save their projects locally.

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

10.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 JDeveloper Full Version.
2. Define the user home directory environment variable (see below).

10.2 Configuring User Home Directories in a multi-user Environment

Before you run JDeveloper in a terminal server environment, you must 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 <jdev_install>/jdev as the home directory for all users. Using this directory may cause unstable behavior in JDeveloper with multiple users.

To define the name of the user home environment variable:

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

SetUserHomeVariable JDEV_USER_DIR
   
   This is the default variable that JDeveloper will look for at startup. As the terminal server's administrator, you may change the name of this variable to follow your system's naming conventions.
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.

To set the environment variable:

1. From the Windows Start menu, select 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 the SetUserHomeVariable, 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. JDeveloper will ask if you would like your user home directory to be created. Select Yes.
9. Choose Help | About to verify that the value of ide.user.dir is set to your user home directory.

10.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 Sun's SDK.
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: from the Windows Start menu, select Control Panel | System.
   1. Select the Advanced tab, then click Environment Variables.
   2. In the User Variables section, click New.
   3. Add the variable to User Variables and click OK.
      For example, you can define JDEV_USER_DIR as the variable containing the path to the user's home directory.
   4. To check the correct variable settings, open a command shell and enter:
      

      set

      You should see output similar to the following:
      
      JDEV_USER_DIR=n:\users\jdoe
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 multi-user 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_install>\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, you will need to set the same option with the same value in Project | D efault Project Settings | Runner | Java options.

To make this setting available to all users, the administrator should perform this change, exit JDeveloper and then copy the file:

<userhome>\system\DefaultWorkspace\Project1.jpr.

<jdev_install>\jdev\multi\system\DefaultWorkspace\Project1.jpr .

11.0 Using OC4J with JDeveloper

Included with JDeveloper is a fully functioning version of Oracle Application Server 10g (9.0.4) Containers for J2EE (OC4J). If you are using JDeveloper to test your applications, you will not have to make any modifications to your configuration.

If you performed the base installation of JDeveloper and wish to deploy your application to OC4J in standalone mode, you must set the JAVA_HOME variable to point to the full SDK. You must also modify jdev.conf to point to this SDK home. See Installing JDeveloper Base for more information.

You can start and stop the OC4J server in stand-alone mode using the provided start_oc4j.bat and stop_oc4j.bat files and shell scripts located in <jdev_install>\jdev\bin\. The start_oc4j batch file can be run either from Windows Explorer or the command line since no arguments are required; however the stop_oc4j batch file requires <admin> and <admin-password> on the command line. You can also run the following commands from the <jdev_install>\j2ee\home\ directory:

To configure the OC4J server for stand-alone mode:

1. Execute the following command:
   
   java -jar $j2ee_home/oc4j.jar -install
   
2. Enter and confirm the administrator password.

To start the OC4J server for use in stand-alone mode:

• Execute the following command:
  
  java -jar $j2ee_home/oc4j.jar

To stop OC4J:

• Execute the following command:
  
  java -jar $j2ee_home/admin.jar ormi://localhost/ <admin> <admin-password> -shutdown

For more information on fine tuning your OC4J server instance, see the OC4J documentation.

Back to TOC

12.0 Application Servers Supported by JDeveloper

This matrix associates JDeveloper versions with the application servers they support for deployment. For specific deployment instructions, see the JDeveloper online documentation.

Notes

1. For BC4J applications, you must install the BC4J runtime libraries on the server. Installers are provided for Windows and Solaris platforms.

2. For BC4J applications, you must install the BC4J runtime libraries on the server, using the BC4J Installer.

3. This combination will not work for applications with J2EE 1.3-specific features or for UIX applications.

4. For UIX applications, make a standalone web application that does not rely on the version of UIX installed on the application server:

1. Ensure that your UIX application has local copies of the UIX installables for the version of UIX that you developed against. UIX XML applications created with JDeveloper already have local installables. Some UIX JSP applications do not. If your application does not already have local UIX installables, unzip the <jdev_install>/jdev/redist/uix2-install.zip file into the application's public_html directory.

2. Select the UIX Runtime library for local deployment in your project's deployment profile. This will ensure that the version of UIX runtime you developed against is automatically included in the WEB-INF/lib of your application.

3. Add an orion-web.xml deployment descriptor to your application. Add the following line:

   <web-app-class-loader search-local-classes-first="true"/>

   This will instruct OC4J to use the version of the UIX runtime library in WEB-INF/lib of your application instead of the version installed globally on the application server.

5. For all applications, you must upgrade to J2SE version 1.4 (Do this upgrade before installing the BC4J or ADF runtime libraries):

1. Upgrade your iAS installation to use J2SE version 1.4. See the instructions in the iAS 9.0.3 release notes, chapter 4, "Configuration".

2. Configure your JDeveloper project to use J2SE 1.4. See the instructions in the JDeveloper online documentation.

6. For ADF applications, you must install the ADF runtime libraries on the server, using the ADF Runtime Installer. See the instructions in the JDeveloper online documentation.

7. Deploy to standalone OC4J. Alternatively, run the embedded OC4J that ships with JDeveloper as a standalone OC4J, and use it as a deployment target for BC4J or ADF applications.

8. These combinations are not supported, but these howto documents describe deployment of BC4J and non-BC4J applications to various versions of JBoss.

9. These combinations are not supported for BC4J or ADF applications; however, this howto document describes the deployment of BC4J applications to WebLogic 7.

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 online help topics available by selecting Help | Help Topics | Getting Started with JDeveloper | JDeveloper Accessibility Information from the JDeveloper main menu.

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 Pace 6), Windows 2000, or Windows XP
• Sun Java Access Bridge 1.0.3 or higher
• JAWS 3.70.87 or 5.0
• Microsoft Internet Explorer 5.5 or higher
• JDK 1.3.1 or higher

Please refer to the following information to set up a screen reader and Java Access Bridge. These steps 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.

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 JDeveloper installation.

3. Download Java Access Bridge 1.0.3. The file you will download is accessbridge-1_0_3.zip.

   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 the contents to a folder; for example, accessbridge_home.
5. Install Java Access Bridge by running Install.exe from the <accessbridge_home>\installer folder.
6. Confirm that you want to install the Java Access Bridge into each of the Java virtual machines displayed in the dialog. Click OK when you see the Installation Completed message.
7. Copy the following two jar files and three DLL files from <accessbridge_home>\installer\installerFiles to <oracle_home>\jdk\jre\lib\ext:

   access-bridge.jar
jaccess-1_4.jar
JavaAccessBridge.dll
JAWTAccessBridge.dll
WindowsAccessBridge.dll

8. Add the DLL files listed above, JavaAccessBridge.dll, JAWTAccessBridge.dll and WindowsAccessBridge.dll, to the Winnt\System32 directory, as they must be in the system path in order to work with JDeveloper.
9. Confirm that the PATH environment variable has been updated to include the directory where the DLL files were installed, <oracle_home>\jdk\jre\lib\ext.
10. Confirm that the file <oracle_home>\jdk\jre\lib\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

    If necessary, copy the file accessibility.properties from <accessbridge_home>\installer\installerFiles to <oracle_home>\jdk\jre\lib.

11. Modify the file jdev.conf located in the folder <jdev_install>\jdev\bin to uncomment the AddVMOption line as shown below:

    #
# Prepend patches to the bootclasspath. Currently, rtpatch.jar contains a
# patch that fixes the javax.swing.JTree accessibility problems.
# Uncomment the line below if you need to run JDeveloper under JAWS.
#
AddVMOption -Xbootclasspath/p:../../jdk/jre/lib/patches/rtpatch.jar

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

15.0 Uninstalling JDeveloper

Before you uninstall JDeveloper, you may want to backup your projects and files. By default, these files are in <jdev_install>\jdev\mywork .

To uninstall JDeveloper, remove the entire JDeveloper installation directory. No other actions are necessary.

16.0 JDeveloper Documentation

Depending on your installation and configuration, JDeveloper online help is installed locally or on a Web host. You can access it from the JDeveloper Help menu.

Back to TOC

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