Oracle JDeveloper 10g  J2EE Developer Preview

Before you install JDeveloper, please review the contents of this guide. Before using JDeveloper, you should read the JDeveloper 10g Release Notes.

Table of Contents

1. JDeveloper System Requirements
   1.1  Recommended CPU, Memory, Display, and Hard Drive Configurations
   1.2  Support for Team Based Development Tools
2. Installing JDeveloper Full Version
3. Installing JDeveloper Base
   3.1  Installing OJVM with a Base Installation on Windows
4. 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. Installing and Starting JDeveloper on Mac OS X Platforms
6. Configuring JDeveloper to Use Hosted Documentation
7. Starting JDeveloper
8. Migrating User Settings from Previous Releases
9. Enabling JDeveloper Extensions
10. Required Component Versions for E-Business Integration
    10.1  Deploying Activity Modeler Generated Artifacts
11. Using JDeveloper in a Multiuser Environment
    11.1  Installing JDeveloper on a Citrix MetaFrame Server or a Microsoft Terminal Server
    11.2  Configuring User Home Directories in a Multiuser Environment
    11.3 Configuring Terminal Server Clients for Running JDeveloper
12. Using OC4J with JDeveloper
    12.1  OC4J Memory Requirements
13. Application Servers Supported by JDeveloper
14. Database Certification for JDeveloper
15. Finding JDeveloper Accessibility Information
16. Uninstalling JDeveloper
17. JDeveloper Documentation
18. Oracle on the Web

1. JDeveloper System Requirements

This release of JDeveloper is supported on Windows NT, Windows 2000, Windows XP, Linux, and Mac OS X.

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

Windows

Linux

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.

MAC OS X

1.2 Support for Team Based Development Tools

JDeveloper provides integrated support for the following source control systems:

ClearCase

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

Note: JDeveloper does not support ClearCase UCM.

Concurrent Version Support (CVS)

• CVS versions 1.11 or greater
• CVSNT versions 2.0.58 or greater

Note: CVSNT is supported on all platforms and is recommended.

2. 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://infozip.sourceforge.net .

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 ( jdevj2ee1013.zip ) includes the Windows version of Sun J2SE 1.4.2_04 and the JDeveloper documentation.

To install JDeveloper from jdevj2ee1013.zip:

• Unzip  jdevj2ee1013.zip  in the directory you want to install JDeveloper.
• If you install  jdevj2ee1013.zip  on a UNIX or Linux system, you may 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  <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 .

3. Installing JDeveloper Base

For quicker download times, you can download the base installation ( jdevj2eebase1013.zip ):

• The base installation requires that you already have 1.4.2_04 of the Sun J2SE on your machine because the SDK is not included.

To install JDeveloper from jdevj2eebase1013.zip:

1. If you don't have Java 2 Platform, Standard Edition, version 1.4.2_04 installed, you can obtain it from: http://www.oracle.com/ .
2. Unzip  jdevj2eebase1013.zip  to the target directory.
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_04 is in a directory called j2sdk1.4.2_04 on your D: drive, your entry in  jdev.conf  would look like:

   SetJavaHome d:\j2sdk1.4.2_04

4. If you do not set the variable SetJavaHome you will be asked at the first start of JDev to provide the path to the location of your SDK installation.
5. 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. For information about OJVM on Linux please refer to the JDeveloper Release Notes at:  <jdev_install>/jdev/readme.html .

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  jdevjava1013.zip, OJVM installed automatically. If you performed the base installation using  jdevjavabase1013.zip, upon the first start of JDeveloper you will be asked if you want to install OJVM into your SDK. If accepted JDev 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.

If you declined this option you can do it later by selecting Tools | Manage Libraries from the main menu. Select J2SE Definition and then the SDK to which you wish to add the OJVM. The Install button is enabled if OJVM has not been installed.

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

4.1 Modifying Permissions on a Non-Windows System

All JDeveloper files must have read permissions which can be set by issuing:

chmod -R g+r  <jdev_install>

Users (or groups) must have 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/bin/start_oc4j                                 
chmod +x  <jdev_install>/jdev/bin/stop_oc4j                                 
chmod +x  <jdev_install>/jdev/bin/ojaudit                                 
chmod +x  <jdev_install>/jdev/bin/addjdevtodesktop                                 

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

Note:  <jdev_install>/j2ee/home/application-deployments  is 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.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.

1. If you don't have Java 2SE, version 1.4.2_04 installed, install it. You can get a copy for many operating systems from http://www.oracle.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 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 ew 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.

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

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 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 choose  Tools | Preferences | Web Browser and Proxy .
2. In the  B rowser Command Line  enter:

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

3. Click  OK .

5. Installing and Starting JDeveloper on Mac OS X Platforms

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 jdevj2ee1013.dmg:

1. Mount the JDeveloper Disk Image by double-clicking the .dmg file.
2. Drag the JDeveloper application to a location on your hard drive; for example, Applications.
3. Start JDeveloper by double-clicking the JDeveloper application.
4. If starting JDeveloper for the first time answer:
5. • Yes to create a JDeveloper user home.
   • No to migrate from a previous version.

   Note that by default JDeveloper files are stored under /Users/ <username>/jdevhome .

6. Configuring JDeveloper to Use Hosted Documentation

JDeveloper is preconfigured to use local documentation. However, you can configure JDeveloper to use the 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.

To configure JDeveloper to use documentation hosted on OTN:

1. From the JDeveloper main menu, choose  T ools | P references | Documentation .
2. Select  Use Hos t ed Documentation on Oracle Technology Network .
3. Click  OK .

7. Starting JDeveloper

• To start JDeveloper on Windows, run the file  <jdev_install>\jdeveloper.exe . You can also run  <jdev_install>\jdev\bin\jdev.exe 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 .

8. Migrating User Settings from Previous Releases

Your user settings (system settings, connections, workspaces and projects) from previous production releases of JDeveloper 9.0.3 and higher can be migrated to this J2EE Developer Preview of JDeveloper. Oracle does not support direct migration from 3.2.3 to 10.1.3.0.2, and you must first migrate to 9.0.2. Oracle does not support direct migration from 9.0.2 to 10.1.3.0.2. The recommended path is 9.0.2 > 9.0.4.x > 10.1.3.0.2.

JDeveloper J2EE Developer Preview provides support for J2EE technologies, Ant, Database, EJB, Java, JavaBeans, HTML, JSP, JSF, UIX, UML, Struts, Swing/AWT, TopLink, Web Services, and XML technologies. Workspaces and projects containing technologies not supported by the Developer Preview release will be migrated, but design and runtime features will not be available for the unsupported technologies. The migration process backs up the original workspace and project files to  .bak files.

Important: Back up your work completely before migrating. Once workspace or project files have been migrated they cannot be opened using previous versions of JDeveloper. To recover the original files, copy the backed up files to their original file names.

To migrate your user settings:

1. Initiate the Migrate User Settings dialog in one of two ways:
2. • Run a newly installed version of JDeveloper for the first time, or
   • Start JDeveloper at a command line or shell prompt with the  -migrate flag (e.g.,  jdev -migrate) which overwrites any existing settings.
3. Enter the location of the system directory of the source installation of JDeveloper to migrate, or click Browse to navigate to the directory. 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 from which you are migrating.
4. Click  OK. Your user settings, including any workspaces and projects, are migrated to your latest version of JDeveloper. Click Cancel to abort the migration process and make no changes to your user settings.

For more information about migration issues, see the "Migrating to JDeveloper 10g" topic in the online documentation, which you can access by choosing  Help | Help Topics | Getting Started with JDeveloper  from the JDeveloper main menu.

9. 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 after you select them.

To manually download a JDeveloper Extension:

1. Go to http://www.oracle.com/tools/downloads/Jdeveloper-12c-downloads.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/extensions directory.
4. 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 | Help Topics from the JDeveloper main menu.

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

Note: Before using Oracle Workflow Server 2.6.1 with an Oracle9i  (9.0.1) database, patch 2026582 must be downloaded from http://support.oracle.com/portal/ and applied to your database.

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

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

11. Using JDeveloper in a Multiuser 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. 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.

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

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

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

Note:  Each user of JDeveloper on a multiuser system must follow these procedures.

1. From the Windows Start menu, choose  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  H elp |  A bout | Properties  to verify that the value of  ide.user.dir  is set to your user home directory.

11.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 Java Sun J2SE 1.4.2_04.
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, choose  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  H elp |  A bout | Properties  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   P roject | D e fault Project Settings| Runner| J ava  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

12. Using OC4J with JDeveloper

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:

• On Windows installations: <jdev_install> /jdev/system####/oc4j-config
• On non-Windows and multiuser installations: <jdev_install> /system####/oc4j-config

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 configure the OC4J server for standalone 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 standalone 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

Note:  The server must be running when you deploy projects to it.

12.1 OC4J Memory Requirements

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:

  java -Doracle.j2ee.dont.use.memory.archive=true -jar oc4j.jar

• 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  -Xmx flag, for example:

  java -Xmx512M -jar oc4j.jar

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

13. Application Servers Supported by JDeveloper

A matrix associating JDeveloper versions with the application servers they support for deployment is available on Oracle Technology Network (OTN).

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.

14. Database Certification for JDeveloper

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.

Notes

1. JDeveloper is fully certified against Oracle 8i , Oracle9i  and Oracle Database 10g .
2. Certified for browsing tables, views, synonyms and sequences.

   Not certified for creating database objects, or offline importing of objects.

3. Certified for browsing tables and views.

   Not certified for creating database objects, or offline importing of objects.

4. Browsing tables works, however MySQL does not support views.

   Also, creating database objects, and offline import of tables do not work.

15. Finding JDeveloper Accessibility Information

For the latest configuration information or for information on addressing accessibility and assistive technology issues. 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.

16. 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 action is necessary.

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

18. Oracle on the Web

Oracle provides a number of resources on the Web. These are some sites you may find helpful: