This release of JDeveloper is tested and supported on the specific versions Windows, Linux, and Mac OS X, as listed in Section 1.1 below. In addition, it is supported on any operating system that supports Sun J2SE 1.5.0_05.
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 2
CPU Type and Speed
Pentium IV 2 GHz or faster
Memory
1 GB RAM
Display
65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space
Base Installation: 375 MB
Complete Installation: 500 MB
JDeveloper provides integrated support for Concurrent Version Support (CVS):
CVS versions 1.10 to 1.11.14
CVSNT versions 2.5
Download extensions to integrate other source control systems in JDeveloper using the Check for Updates wizard. From the main menu choose Help | Check for Updates to launch the wizard. JDeveloper provides extensions for the following:
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 ORACLE_HOME.
You will not be able to uninstall it using Oracle Universal Installer.
The full installation (jdevstudio1013.zip) includes the Windows version
of Sun J2SE 1.5.0_05 and the JDeveloper documentation.
To install JDeveloper from jdevstudio1013.zip:
Unzip jdevstudio1013.zip in the directory you want to install JDeveloper.
Note: Do not install JDeveloper in a location with spaces in the directory name. For example, use the directory c:\jdev_10g instead of c:\jdev 10g.
Note: The remainder of this document uses <jdev_install>
to represent the directory location in which JDeveloper was installed.
For example, if JDeveloper was unzipped in c:\jdev10g, the
<jdev_install> would be c:\jdev10g.
For quicker download times, you can download the base installation (jdevstudiobase1013.zip):
The base installation requires that you already have 1.5.0_05 of the Sun J2SE
on your machine because the SDK is not included.
The base installation, by default, does not include JDeveloper documentation.
To install JDeveloper from jdevstudiobase1013.zip:
If you don't have Java™ 2 Platform, Standard Edition, version 1.5.0_05
installed, you can obtain it from: http://www.javasoft.com.
Unzip jdevstudiobase1013.zip to the target directory.
Note: Do not install JDeveloper in a location with spaces in the directory name. For example, use the directory c:\jdev_10g instead of c:\jdev 10g.
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.5.0_05
is in a directory called jdk1.5.0_05 on your D: drive, your entry in jdev.conf
would look like:
SetJavaHome d:\jdk1.5.0_05
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: 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.
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 jdev1013.zip, OJVM was installed
automatically.
If you perform the base installation using jdevstudioabase1013.zip,
you are prompted to install OJVM into your SDK. JDeveloper copies OJVM
files into the specified SDK and updates 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. You can install or update OJVM later if you decline the installation at startup.
To install or update OJVM with a base installation:
From the main menu select Tools | Manage Libraries.
Click the J2SE Definitions tab.
In the Definitions list select the SDK into which OJVM is to be installed.
In the right pane, OJVM Successfully Installed/Updated indicates whether or not OJVM is currently installed or updated with the most recent version. If it is not, the Install or Update button is active. Click to install or update OJVM.
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:
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 permissions for the following
files (required for deployment):
Note:<jdev_install>/j2ee/home/application-deploymentsis not available until you run java -jar oc4j.jar -install
<jdev_install>/j2ee/home/application-deployments
<jdev_install>/j2ee/home/applications
<jdev_install>/j2ee/home/config
4.2 Configuring Java SDK in JDeveloper on Non-Windows
Platforms
The complete installation of JDeveloper is configured to use Java Sun J2SE 1.5.0_05
for Windows platforms. If you install JDeveloper on another platform, perform
the following steps to configure JDeveloper to use the appropriate SDK.
If you don't have Java™ 2SE, version 1.5.0_05 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.
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 Cursor Problems on Non-Windows Platforms
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:
Make a back-up copy of the default cursors located in the SDK directory
at:
<jdk_install>/jre/lib/images/cursors
Extract the replacement cursors from the tar file at:
7.0 Migrating User Settings from Previous Releases
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.3.
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
| Table of Contents | 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
When the Migrate User Settings dialog appears, select a version of JDeveloper
to migrate. If the Version dropdown list is empty,
click Browse.
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.
Select the settings and customizations you want to migrate. Oracle recommends
that you select all available options.
Click OK. Your user settings are migrated to
your latest version of JDeveloper.
Before you can use an extension in JDeveloper, you first
need to download the extension from OTN. An example of available JDeveloper
Extensions is JUnit.
To automatically download and install a JDeveloper
extension:
From the JDeveloper main menu, select Help | Check
for Updates.
This menu option lists extensions that you don't have, lists newer versions
of ones you have, and downloads them after you select them. After you restart JDeveloper, you will be able to use the extension.
Shut down any instances of JDeveloper that are running on your machine.
Verify if there are additional installation instructions in the extension
archive.
From the JDeveloper main menu, select Help | Check for Updates.
On Step 1 of the wizard, select Install from a Local File and navigate to the ZIP file.
Finish the wizard and restart JDeveloper. After you restart JDeveloper, you will be able to use the extension.
For additional information, see the "Extending JDeveloper" topics in the online documentation, which you can access by choosing Help | Table of Contents from the JDeveloper main menu.
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.
9.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:
Define the user home directory environment variable (see below).
9.2 Configuring User Home Directories in a Multiuser
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:
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.
Find the entry:
SetUserHomeVariable JDEV_USER_DIR
This is
the default variable that JDeveloper will look for at startup. As the terminal
server administrator, you may change the name of this variable to follow
your system's naming conventions.
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:
Note: Each user of JDeveloper on a multiuser system must
follow these procedures.
From the Windows Start menu, choose Control Panel |
System.
Select the Advanced tab, then click Environment
Variables.
In the User Variables section, click New.
Add JDEV_USER_DIR, or the name you chose for the SetUserHomeVariable,
as a user variable.
Set the value of this variable to your home directory (e.g., N:\users\jdoe),
and click OK.
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
Launch JDeveloper.
JDeveloper will ask if you would like your user home directory to be created.
Select Yes.
Choose Help | About to verify
that the value of ide.user.dir is set to your user home directory.
9.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.
To configure a terminal server client for running JDeveloper:
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 Sun J2SE 1.5.0_05.
Log on to your terminal server.
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.
Set the user home environment variable: from the Windows Start menu, choose Control Panel | System.
Select the Advanced tab, then click
Environment Variables.
In the User Variables section, click New.
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.
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
Launch JDeveloper.
JDeveloper will ask if you would like your user home directory to be created.
Select Yes.
Choose Help | About to verify
that the value of ide.user.dir is set to your user home directory.
If you run JDeveloper in a multiuser environment and you see the error
The system DLL ole32.dll was relocated in memory. The application will
not run properly. The relocation occurred because the DLL Dynamically Allocated
Memory occupied an address range reserved for Windows NT system DLL's. The
vendor supplying the DLL should be contacted for a new DLL.
you'll need to update the <jdev_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:
Included with JDeveloper is a fully functioning version of Oracle Application
Server 10g Release 2 (10.1.3) Containers for J2EE (OC4J). The embedded server resides in the following location in the JDeveloper installation:
If 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 start the OC4J server for use in standalone mode:
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:
If your machine lacks sufficient free memory to run OC4J with a larger maximum heap size, shut down the Java process that runs OC4J and restart it with the -Doracle.j2ee.dont.use.memory.archive=true flag to turn off class preloading, for example:
If your machine has at least 512 MB of free memory, OC4J will run more quickly if you leave preloading enabled, but startup time will increase considerably. Shut down the Java process that runs OC4J, and restart it with a larger maximum heap size using the -mx flag, for example:
Java -mx512M -jar oc4j.jar
For more information on fine tuning your OC4J server instance, see the OC4J documentation.
For additional information, see the "Deploying JDeveloper" topics in the online documentation, which you can access by choosing Help | Table of Contents from the JDeveloper main menu.
This matrix associates Oracle and non-Oracle databases with the JDeveloper
features they are certified against. As well as the native drivers for the databases listed below, DataDirect 3.5 Service
Pack 2 drivers are supported for DB2 (8.1), SQL Server (2000), Sybase ASE (12.5), and Informix Dynamic Server (10.0).
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.
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.
15.0 Using a Screen Reader and Java Access Bridge
with JDeveloper
To make the best use of our accessibility features, Oracle Corporation recommends the following minimum technology stack:
Windows NT 4.0 (with Service Pack 6), Windows 2000, or
Windows XP
Java Sun J2SE 1.5.0_05
Sun Java Access Bridge 1.2 or higher
JAWS 3.70.87 or 5.0.0.844+
Microsoft Internet Explorer 5.5 or higher
Please refer to the following information to set up a screen reader and
Java Access Bridge. If you are using JAWS 3.70.87, please refer to the additional configuration information provided below the procedure.
Install the screen reader, if it is not already installed.
Refer to the documentation for your screen reader for more
information about installation.
Install JDeveloper.
Refer to the Installation Guide for more information about
installing JDeveloper.
Download Java Access Bridge for Windows version 1.2. The file you will download is
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.
After downloading the file, extract (unzip) the contents to a folder, for
example, accessbridge_home.
Install Java Access Bridge by running 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.
Click Search disks. Then select to search only the
drive that contains the JDeveloper build and the SDK 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
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.
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.
Click
OK
when you see the Installation Completed message.
Confirm that the following files have been installed in the Winnt\System32 directory
(or the equivalent Windows 2000 or XP directory),
or copy them from <accessbridge_home>\installer\installerFiles
as they must be in the system path in order to work with JDeveloper:
Note that the system directory is required in the PATH system variable.
Confirm that the following files have been installed in the <jdev_install>\jdk\jre\lib\ext directory, or copy them from
<accessbridge_home>\installer\installerFiles:
Confirm that the file 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:
Only if you are using JAWS version 3.7, do the following: 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
Start your screen reader.
Start JDeveloper by running the file 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 and then the main JDeveloper window will appear, once
JDeveloper has started.
Any messages that appear will not affect the functionality of JDeveloper.
15.1 Configuring JAWS 3.70 and Access Bridge with JDeveloper
The following combinations of Access Bridge file versions are necessary to achieve optimal functionality with JAWS 3.70 since this version of the screen reader uses older Java technology than is used in JDeveloper 10.1.3. 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. Also required in the system32 directory is a copy of the latest version of the Access Bridge jar file.
Access Bridge v. 1.0.3 Configuration for JDeveloper 10.1.3
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: 28672
version: AccessBridge-1.0.3
jaccess-1_3.jar
size: 43584
version: AccessBridge-1.0.3
jaccess-1_4.jar
size: 46597
version: AccessBridge-1.0.3
JavaAccessBridge.dll
size: 139264
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: 353
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
Access Bridge v. 1.0.4 Configuration for JDeveloper 10.1.3
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]:
Bookmark
