Installation Guide
Version 10.1.2
October 2004
Before you install JDeveloper, please review the contents of this guide. Before using JDeveloper, you should read the JDeveloper 10g Release Notes.
This release of JDeveloper is supported on Windows NT, Windows 2000, Windows XP, Linux, Solaris, Mac OS X, and HP-UX.
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 Installation: 230 MB
Complete Installation: 375 MBJava SDK Sun J2SE 1.4.2_04 for Windows, available at: http://www.javasoft.com.
Resource Recommended
Distribution
Red Hat Enterprise Linux 2.1
Red Hat Enterprise Linux 3.0
Red Hat Linux 9.0
SuSE SLES8CPU 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 Installation: 231 MB
Complete Installation: 390 MBJava SDK
Sun J2SE 1.4.2_04 for Linux, available at: http://www.javasoft.com.
|
Note: If you want to use JDeveloper in a multiuser
UNIX environment, Oracle recommends a minimum of 512 MB RAM and 1 GB of
swap space. |
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 Installation: 231 MB
Complete Installation: 390 MBJava SDK
Sun J2SE 1.4.2_04 for Solaris (32-bit), available at: http://www.javasoft.com.
Resource Recommended
Operating System
Apple Mac OS X Version 10.3
CPU Type and Speed
Dual 1.25 GHz G4/G5 (1 GHz G4 minimum)
Memory
1 GB RAM (512 MB minimum)
Display
"Thousands" of colors
Hard Drive Space
Base Installation: 231 MB
Complete Installation: 390 MBJava SDK
Sun J2SE 1.4.2 Update 2 available at: http://developer.apple.com/java/download/ or from Mac OS X Software Update.
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 Installation: 390 MBJava SDK
HP J2SE 1.4.2.02 for PA-RISC, available at http://www.hp.com/products1/unix/java/index.html.
JDeveloper provides integrated support for the following source control systems:
|
Note: JDeveloper does not support ClearCase UCM. |
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/.
|
Alert: Do not install this
JDeveloper release into any existing |
The full installation (jdev1012.zip) includes the Windows version
of Sun J2SE 1.4.2_04 and the JDeveloper documentation.
To install JDeveloper from jdev1012.zip:
jdev1012.zip in the directory you want to install JDeveloper.
jdev1012.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.|
Note: The remainder of this document uses |
For quicker download times, you can download the base installation (jdev1012_base.zip):
To install JDeveloper from jdev1012_base.zip:
jdev1012_base.zip to the target directory.
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.jdev.conf
would look like:SetJavaHome d:\j2sdk1.4.2_04|
Note: JDeveloper provides OJVM,
and OJVM can be installed for use with JDeveloper, but this configuration is only supported for JDeveloper projects, not the JDeveloper IDE. For information about OJVM on Linux please
refer to the JDeveloper Release Notes at: |
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 jdev1012.zip, OJVM was installed
automatically. If you performed the base installation using jdev1012_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:
<jdev_install>\jdev\bin\ execute the command:InstallOJVM.bat d:\j2sdk1.4.2_04d:\j2sdk1.4.2_04 is the location of your SDK.To install the documentation set, download jdev1012_doc.zip from
http://www.oracle.com/technology/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:
<jdev_install>\jdev\doc\ohj.This section provides additional instructions specific to installing JDeveloper on a non-Windows platform. Review these sections of the Installation Guide for general information:
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. JDeveloper provides OJVM,
and OJVM can be installed for use with JDeveloper, but this configuration is only supported for JDeveloper projects, not the JDeveloper IDE. For information about OJVM on Linux
please refer to the JDeveloper Release Notes at: <jdev_install>/jdev/readme.html.
All JDeveloper files must have read permissions which can be set by issuing:
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>/BC4J/bin/bc4j2oc4j
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):
|
Note: |
<jdev_install>/j2ee/home/application-deployments
<jdev_install>/j2ee/home/applications
<jdev_install>/j2ee/home/configThe complete installation of JDeveloper is configured to use Java Sun J2SE 1.4.2_04 for Windows platforms. If you install JDeveloper on another platform, perform the following steps to configure JDeveloper to use the appropriate SDK.
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
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 UNIX, your SDK isn't set up to use the
font that is specified in the error. JDeveloper, by default, uses the information
in the file font.properties included with each SDK. 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. For information on updating
the font.properties file, see Sun's Font
Overview documentation or your SDK vendor's documentation.
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 Java SDK in order to replace the cursors.
To replace the cursors:
<jdk_install>/jre/lib/images/cursors
<jdev_install>/jdev/bin/clear_cursors.tar
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:
/opt/mozilla/mozilla -remote openURL(${URL}) || /opt/mozilla/mozilla
${URL}
JDeveloper is provided as a self-contained application bundle. An installer is not required.
You must update your Mac OS X SDK to Java Sun version 1.4.2 Update 2 or later for use with JDeveloper. Use Mac OS X Software Update or download from http://developer.apple.com/java/download/.
To install JDeveloper from jdev1012.dmg:
Note that by default JDeveloper files are stored under /Users/<username>/jdevhome.
If you installed jdev1012_base.zip, JDeveloper is preconfigured
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 jdev1012.zip, JDeveloper is preconfigured 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:
<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.
<jdev_install>/jdev/bin/jdev.User settings such as 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 10.1.2.
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 this dialog
to 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. For information about
migration issues, see the " Migrating to JDeveloper
10g " topics in the online documentation, which you can access by choosing Help
| Help Topics | Getting Started with JDeveloper from the JDeveloper main menu.
To migrate user settings from previous installations of JDeveloper:
Start JDeveloper at a command line or shell prompt with the -migrate
flag:
jdev -migrate
<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.
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:
To manually download a JDeveloper Extension:
To manually install a JDeveloper extension:
<jdev_install>\jdev\lib\ext
directory.
For additional information, see the "Extending JDeveloper" topics in the online documentation, which you can access by choosing Help | Help Topics from the JDeveloper main menu.
Back to TOCThe versions of components required for E-Business integration are:
|
Note: Oracle Workflow Server 2.6.0 can be downloaded from http://www.oracle.com/technology/software/products/integration/content.html |
|
Note: Before using Oracle Workflow Server 2.6.1 with an Oracle9i (9.0.1) database, patch 2026582 must be downloaded from http://metalink.oracle.com/ and applied to your database. |
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.
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. These environments allow many clients to access one installation of JDeveloper. In all cases, users can save their projects locally.
When installing and configuring JDeveloper for a multiuser environment, you'll need to account for resource planning, such as number of users and power of the server to deliver optimal performance for JDeveloper and your users.
You need to have administrative privileges to install JDeveloper.
To Install JDeveloper on a Citrix MetaFrame or Microsoft Terminal Server:
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:
<jdev_install>\jdev\bin\jdev.conf in
a text editor. Use an editor that recognizes UNIX end-of-line characters,
such as WordPad.
SetUserHomeVariable JDEV_USER_DIRTo set the environment variable:
|
Note: Each user of JDeveloper on a multiuser system must
follow these procedures. |
JDEV_USER_DIR, or the name you chose for the SetUserHomeVariable,
as a user variable.
N:\users\jdoe),
and click OK.
setJDEV_USER_DIR=N:\users\jdoe ide.user.dir is set to your user home directory.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.
To configure a terminal server client for running JDeveloper:JDEV_USER_DIR.
JDEV_USER_DIR as the variable containing the
path to the user's home directory.
set
JDEV_USER_DIR=n:\users\jdoe ide.user.dir is set to your user home directory.If you run JDeveloper in a multiuser environment and you see the error
The system DLL ole32.dll was relocated in memory. The application will not run properly. The relocation occurred because the DLL Dynamically Allocated Memory occupied an address range reserved for Windows NT system DLL's. The vendor supplying the DLL should be contacted for a new DLL.
you'll need to update the <jdev_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
| Default 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.
to: <jdev_install>\jdev\multi\system\DefaultWorkspace\Project1.jpr.
Back to TOC
Included with JDeveloper is a fully functioning version of Oracle Application Server 10g Release 2 (10.1.2) Containers for J2EE (OC4J). The embedded server resides in the following location in the JDeveloper installation:
<jdev_install>/jdev/system####/oc4j-config
<jdev_install>/system####/oc4j-configIf you are using JDeveloper to test your J2EE applications before deploying to a target application server, 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, JDeveloper includes a copy of OC4J in <jdev_install>/j2ee/home/config. To run 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.
If you deploy your applications to standalone OC4J, make sure that you use the remote admin.jar file that was shipped with the remote OC4J. If you are using an admin.jar that doesn't match the version of OC4J to which you are deploying, deployment may fail. You can configure deployment to use the correct admin.jar for the OC4J standalone instance when you set up your connection using the JDeveloper Application Server Connection Wizard. To identify the standalone OC4J version that you are using, enter java -jar oc4j.jar -version from your OC4J installation directory.
You can start and stop the OC4J server in standalone 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 standalone mode:
java -jar $j2ee_home/oc4j.jar -install
To start the OC4J server for use in standalone mode:
java -jar $j2ee_home/oc4j.jarTo stop OC4J:
java -jar $j2ee_home/admin.jar ormi://localhost/ <admin> <admin-password>
-shutdown
|
Note: The server must be running when you deploy projects
to it. |
By default, OC4J preloads a large number of classes to improve performance. Because of this, you may get a java.lang.OutOfMemoryError when you attempt to deploy to OC4J or run an application after deploying.
If you get a java.lang.OutOfMemoryError, you have two options:
-Doracle.j2ee.dont.use.memory.archive=true flag to turn off class preloading, for example:
Java -Doracle.j2ee.dont.use.memory.archive=true -jar oc4j.jar
-mx flag, for example:
Java -mx512M -jar oc4j.jar
For more information on fine tuning your OC4J server instance, see the OC4J documentation.
A matrix associating JDeveloper versions with the application servers they support for deployment is available on Oracle Technology Network (OTN) at: http://www.oracle.com/technology/products/jdev/collateral/papers/10g/as_supportmatrix.html.
For additional information, see the "Deploying JDeveloper" topics in the online documentation, which you can access by choosing Help | Help Topics from the JDeveloper main menu.
This matrix associates Oracle and non-Oracle databases with the JDeveloper features they are certified against.
Supported means that Oracle will address customer issues,
but the features are not necessarily tested. Certified means
that the feature is supported on that database, and has passed testing by JDeveloper
QA. The databases shown are all supported, even if not certified or working
in this release.
| Database | JDeveloper Feature | |||||
|---|---|---|---|---|---|---|
| Database | Certification Status | Database Features | SQL Worksheet | PL/SQL | Oracle ADF Business Components Design Time | Oracle ADF Business Components Run Time |
Oracle 8i1 (8.1.7.4.12) |
Full Certification | Certified | Certified | Certified | Certified | Certified |
| Oracle9i1 9.2.4.0) | Full Certification | Certified | Certified | Certified | Certified | Certified |
| Oracle Database 10g1 | Full Certification | Certified | Certified | Certified | Certified | Certified |
| Oracle Lite (4.0.3) | Partial Certification | Certified2 | Certified | Not Working | Certified3 | Certified4 |
| DB2 (7 release 2) | Partial Certification | Certified5 | Certified | Not Working | Certified3 | Certified4 |
| SQL Server (2000) | Partial Certification | Certified5 | Certified | Not Working | Certified3 | Certified4 |
| MySQL (4.0.14b) | Not Certified | Working6 | Working | Not Working | Working7 | Working8 |
For the latest configuration information or for information on addressing accessibility and assistive technology issues, see the Oracle Accessibility FAQ at http://www.oracle.com/accessibility/faq.html. Also, see the help topics available by selecting the JDeveloper Accessibility Information node under Getting Started with Oracle JDeveloper in the online help table of contents.
To make the best use of our accessibility features, Oracle Corporation recommends the following minimum technology stack:
Please refer to the following information to set up a screen reader and Java Access Bridge. If you are using JAWS 3.70.87, please refer to the additional configuration information provided below the procedure.
Refer to the documentation for your screen reader for more information about installation.
Refer to the Installation Guide for more information about installing JDeveloper.
accessbridge-1_2.zip. It is available from:
http://java.sun.com/products/accessbridge.
Refer to the Java Access Bridge documentation available from this web site for more information about installation and the Java Access Bridge.
accessbridge_home.
Install.exe from
the <accessbridge_home>\installer folder.
The installer first checks the SDK version for compatibility, then the Available Java virtual machines dialog displays.
The search process can take a long time on a large disk with many instances of SDK 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.
Winnt\System32 directory
(or the equivalent Windows 2000 or XP directory),
or copy them from <accessbridge_home>\installer\installerFiles
as they must be in the system path in order to work with JDeveloper:
JavaAccessBridge.dll
JAWTAccessBridge.dll
WindowsAccessBridge.dll
Note that the system directory is required in the PATH system variable.
<jdev_install>\jdk\jre\lib\ext directory, or copy them from
<accessbridge_home>\installer\installerFiles:
access-bridge.jar
jaccess-1_3.jar
jaccess-1_4.jar
JavaAccessBridge.dll
JAWTAccessBridge.dll
WindowsAccessBridge.dll
accessibility.properties has been installed in the <jdev_install>\jdk\jre\lib directory, or copy it from <accessbridge_home>\installer\installerFiles. Confirm that the file
accessibility.properties
includes the following three lines:
assistive_technologies=com.sun.java.accessibility.AccessBridge
AWT.EventQueueClass=com.sun.java.accessibility.util.EventQueueMonitor
AWT.assistive_technologies=com.sun.java.accessibility.AccessBridge
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
jdev.exe located in
the folder <jdev_install>\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. Then the main JDeveloper window will appear once JDeveloper has started. Any message that appears will not affect the functionality of JDeveloper.
JDeveloper is designed to be accessible with screenreader software. JDeveloper 10.1.2 has been tested with JAWS 5.0 and JAWS 3.70. Although our testing of JDeveloper 10.1.2 and JAWS 5.0 was completed using Access Bridge 1.1_GA, Access Bridge version 1.2_GA works with JDeveloper 10.1.2 and JAWS 5.0. You do not need to use rtpatch.jar when using JAWS 5.0.
Access Bridge version requirements for each version of JAWS are listed below. Please see the JDeveloper 10g Release Notes regarding issues with the different configurations.
Place the following files in the JDeveloper directory [\jdk\jre\lib\ext]:
| access-bridge.jar | size: 33184 | version: AccessBridge_1_2_GA |
| JAWTAccessBridge.dll | size: 32768 | version: AccessBridge_1_2_GA |
| jaccess-1_3.jar | size: 43642 | version: AccessBridge_1_2_GA |
| jaccess-1_4.jar | size: 46276 | version: AccessBridge_1_2_GA |
| JavaAccessBridge.dll | size: 155648 | version: AccessBridge_1_2_GA |
| WindowsAccessBridge.dll | size: 81920 | version: AccessBridge_1_2_GA |
Place the following file in the JDeveloper directory [\jdk\jre\lib]:
| accessibility.properties | size: 153 | version: AccessBridge_1_2_GA |
Place the following files in the Windows system32 directory [\winnt\system32]:
| JavaAccessBridge.dll | size: 155648 | version: AccessBridge_1_2_GA |
| WindowsAccessBridge.dll | size: 81920 | version: AccessBridge_1_2_GA |
| JAWTAccessBridge.dll | size: 32768 | version: AccessBridge_1_2_GA |
Access Bridge v. 1.1_GA Configuration for JDeveloper 10.1.2 with JAWS 5.0
Place the following files in the JDeveloper directory [\jdk\jre\lib\ext]:
| access-bridge.jar | size: 33136 | version: AccessBridge_1_1_GA |
| JAWTAccessBridge.dll | size: 32768 | version: AccessBridge_1_1_GA |
| jaccess-1_3.jar | size: 43584 | version: AccessBridge_1_1_GA |
| jaccess-1_4.jar | size: 46619 | version: AccessBridge_1_1_GA |
| JavaAccessBridge.dll | size: 155648 | version: AccessBridge_1_1_GA |
| WindowsAccessBridge.dll | size: 81920 | version: AccessBridge_1_1_GA |
Place the following file in the JDeveloper directory [\jdk\jre\lib]:
| accessibility.properties | size: 153 | version: AccessBridge_1_1_GA |
Place the following files in the Windows system32 directory [\winnt\system32]:
| JavaAccessBridge.dll | size: 155648 | version: AccessBridge_1_1_GA |
| WindowsAccessBridge.dll | size: 81920 | version: AccessBridge_1_1_GA |
| JAWTAccessBridge.dll | size: 32768 | version: AccessBridge_1_1_GA |
The use of JDeveloper 10.1.2, JAWS 3.70, and AccessBridge1.1_GA is not a recommended configuration. You may encounter JVM conflict exceptions when you attempt to launch JDeveloper 10.1.2. The latest version of Access Bridge, version 1.2_GA, does not require extensive configuration to work with JDeveloper 10.1.2 and JAWS 3.70.
To use earlier versions of Access Bridge with JDeveloper 10.1.2 and JAWS 3.70, the following combinations of Access Bridge file versions are necessary to achieve optimal functionality since this version of the screen reader uses older Java technology than is used in JDeveloper 10.1.2. There are two stacks of software technology listed below for those who want to use either version 1.0.3 or 1.0.4 of the Access Bridge. Note that the latest version of the Access Bridge Jar file is required in the system32 directory.
Place the following files in the JDeveloper directory [\jdk\jre\lib\ext]:
| access-bridge.jar | size: 33184 | version: AccessBridge_1_2_GA |
| JAWTAccessBridge.dll | size: 32768 | version: AccessBridge_1_2_GA |
| jaccess-1_3.jar | size: 43642 | version: AccessBridge_1_2_GA |
| jaccess-1_4.jar | size: 46276 | version: AccessBridge_1_2_GA |
| JavaAccessBridge.dll | size: 155648 | version: AccessBridge_1_2_GA |
| WindowsAccessBridge.dll | size: 81920 | version: AccessBridge_1_2_GA |
Place the following file in the JDeveloper directory [\jdk\jre\lib]:
| accessibility.properties | size: 153 | version: AccessBridge_1_2_GA |
Place the following files in the Windows system32 directory [\winnt\system32]:
| JavaAccessBridge.dll | size: 155648 | version: AccessBridge_1_2_GA |
| WindowsAccessBridge.dll | size: 81920 | version: AccessBridge_1_2_GA |
| JAWTAccessBridge.dll | size: 32768 | version: AccessBridge_1_2_GA |
Place the following files in the JDeveloper directory [\jdk\jre\lib\ext]:
| access-bridge.jar | size: 27295 | version: access-bridge-1.0.4 |
| JAWTAccessBridge.dll | size: 32768 | version: AccessBridge-1.0.4 |
| jaccess-1_4.jar | size: 46573 | version: AccessBridge-1.0.4 |
| JavaAccessBridge.dll | size: 139264 | version: AccessBridge-1.0.4 |
| WindowsAccessBridge.dll | size: 77824 | version: AccessBridge-1.0.4 |
Place the following file in the JDeveloper directory [\jdk\jre\lib]:
| accessibility.properties | size: 153 | version: AccessBridge-1.0.4 |
Place the following files in the Windows system32 directory [\winnt\system32]:
| JavaAccessBridge.dll | size: 155648 | version: AccessBridge_1_1_GA |
| WindowsAccessBridge.dll | size: 77824 | version: AccessBridge-1.0.3 |
| JAWTAccessBridge.dll | size: 28672 | version: AccessBridge-1.0.3 |
Place the following files in the JDeveloper directory [\jdk\jre\lib\ext]:
| access-bridge.jar | size: 33184 | version: access-bridge-1.0.4 |
| JAWTAccessBridge.dll | size: 32768 | version: AccessBridge-1.0.3 |
| jaccess-1_3.jar | size: 43642 | version: AccessBridge-1.0.3 |
| jaccess-1_4.jar | size: 46276 | version: AccessBridge-1.0.3 |
| JavaAccessBridge.dll | size: 155648 | version: AccessBridge-1.0.3 |
| WindowsAccessBridge.dll | size: 77824 | version: AccessBridge-1.0.3 |
Place the following file in the JDeveloper directory [\jdk\jre\lib]:
| accessibility.properties | size: 153 | version: AccessBridge-1.0.3 |
Place the following files in the Windows system32 directory [\winnt\system32]:
| JavaAccessBridge.dll | size: 155648 | version: AccessBridge_1_1_GA |
| WindowsAccessBridge.dll | size: 77824 | version: AccessBridge-1.0.3 |
| JAWTAccessBridge.dll | size: 28672 | version: AccessBridge-1.0.3 |
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 action is necessary.
Back to TOCDepending 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.
Oracle provides a number of resources on the Web. These are some sites you may find helpful:
| Description | URL |
|---|---|
|
JDeveloper Home Page |
|
|
JDeveloper Discussion Forum |
|
|
Corporate Site |
|
|
Oracle Developer Suite-JDeveloper |
|
|
Oracle Technology Network |
|
|
Worldwide Customer Support |
|
| Oracle Accessibility Site | http://www.oracle.com/accessibility/ |