Installing Oracle9i JDeveloper Version 9.0.4

September 2003

Before you install Oracle JDeveloper, please review the contents of this guide.

• Oracle JDeveloper System Requirements
• Installing Oracle JDeveloper
• Configuring the Java SDK in Oracle JDeveloper on Non-Windows Platforms
• Starting Oracle JDeveloper
• Installing ojvm with a Base Installation on Windows
• Adding Local Documentation to a Base Installation
• Hosted Documentation
• Enabling Oracle JDeveloper Extensions
• Migrating User Settings from Previous Releases
• Font Problems in UNIX
• Required Component Versions for E-Business Integration
• Using Oracle JDeveloper in a Multiuser Environment
• Using OC4J with Oracle JDeveloper
• Oracle JDeveloper Accessibility Information
• Supported Deployment Environments
• Uninstalling Oracle JDeveloper
• Oracle JDeveloper Documentation

Oracle JDeveloper System Requirements

This release of Oracle JDeveloper is supported on Solaris and HP-UX.

Recommended CPU, Memory, Display, and Hard Drive Configurations for Supported Systems

Windows

Resource	Recommended
Operating System	Windows 2000 SP3, Windows NT 4.0 SP6a, Windows XP SP1
CPU Type and Speed	Pentium III 500 MHz
Memory	512 MB RAM
Display	65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space	Base Install: 160 MB Complete Install: 400 MB

Linux

Resource	Recommended
Distribution	Red Hat Enterprise Linus AS 2.1 Red Hat Enterprise Linux ES 2.1 Red Hat 9.0 United Linux 1.0
CPU Type and Speed	Pentium III 500 MHz
Memory	512 MB RAM
Display	65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space	Base Install: 160 MB Complete Install: 400 MB
Java 2 Standard Edition	Sun SDK 1.4.2_02 for Linux

Solaris

Resource	Recommended
Operating System	Solaris 2.7 or 2.8 using the CDE window manager
CPU Type and Speed	Sparc 333 MHz
Memory	512 MB RAM
Display	65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space	Base Install: 160 MB Complete Install: 400 MB
Java 2 Standard Edition	Sun SDK 1.4.1_05 for Solaris

HP-UX

Resource	Recommended
Operating System	HPUX 11.0 and 11.11 using the CDE or VUE window managers
CPU Type and Speed	HP-UX PA-RISC 200 MHz
Memory	512 MB RAM
Display	65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space	Base Install: 160 MB Complete Install: 400 MB
Java 2 Standard Edition	HP SDK 1.4.1.05 for HP-UX PA-RISC, available at http://www.hp.com/products1/unix/java/

Installing Oracle JDeveloper

The full installation ( jdev904.zip) includes the Windows version of SDK 1.4.1_05 and the Oracle JDeveloper documentation.

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

• The base install requires that you already have SDK 1.4.1_05 (1.4.2_02 for Linux) on your machine, as the SDK is not included in the base install.
• The base install, by default, does not include Oracle JDeveloper documentation. Instead, the base install requires a Web connection to access the documentation.

Installing Oracle JDeveloper from jdev904.zip

• Unzip jdev904.zip in the directory you want to install Oracle JDeveloper.
• If you install jdev904.zip on a UNIX or Linux system, you have to modify jdev.conf to specify the SDK and VM. See the next two sections for more information.

Installing Oracle JDeveloper from jdev904_base.zip

1. If you don't have Java™ 2, version 1.4.1_05 (1.4.2_02 for Linux) installed, you can obtain it from http://www.hp.com/products1/unix/java/ for the HP-UX PA-RISC version.
   
   

   Note: For the base install, you must install the SDK into the <jdev_install> for OC4J to work properly if you plan to deploy and run your applications.

2. Unzip jdev904_base.zip in the directory you want to install Oracle 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 SDK 1.4.1_05 is in a directory called j2sdk1.4.1_05 on your D drive, your entry in jdev.conf would look like:
   
   SetJavaHome d:\j2sdk1.4.1_05

4. In a UNIX environment, if the location of your SDK is in a directory called /local/java/sdk, your entry in jdev.conf would look like:
   
   SetJavaHome /local/java/sdk
   
   You can use either a local SDK or a SDK on a mounted drive.

4. If you are using Oracle JDeveloper on a Windows platform, and you want to use CodeCoach or Profiler, you will need to install ojvm, the specialized Oracle Java Virtual Machine for Oracle JDeveloper. The ojvm will also make the Oracle JDeveloper debugger run more quickly. See Installing ojvm on Windows to Run CodeCoach and Profiler, and to Improve Debugger Performance in this installation guide.
5. If you are using Oracle JDeveloper on a Windows platform, but want to use a VM other than ojvm, edit <jdev_install>\jdev\bin\jdev.conf and find the line:
   
   # SetJavaVM ojvm
   
   Right below this line, add a line containing the name of the Java Virtual Machine you want to use ("Hotspot" is an example):
   
   SetJavaVM hotspot
   
   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.
   
   

   Note: If you do not install ojvm, you will not be able to use CodeCoach or Profiler, and the debugger will not run as quickly.

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

Modifying Permissions on a non-Windows System

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

• <jdev_install>/jdev/bin/jdev
• <jdev_install>/jdev/bin/ojc
• <jdev_install>/jdev/bin/bc4j2oc4j
• <jdev_install>/jdev/bin/start_oc4j
• <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

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

The complete installation of Oracle JDeveloper is configured to use Java SDK 1.4.1_05 for Windows platforms. If you install Oracle JDeveloper on another platform, perform the following steps to configure Oracle JDeveloper to use the appropriate SDK. Also, you must specify the VM that you are using in jdev.conf.

1. If you don't have Java™ 2, version 1.4.1_05 (1.4.2_02 for Linux) installed, install it.
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 SDK 1.4.1_05 is in a directory called /local/java/sdk, your entry in jdev.conf would look like:
   
   SetJavaHome /local/java/sdk
   
   You can use either a local SDK or a SDK on a mounted drive. Also, see the previous section, Installing Oracle JDeveloper from jdev904_base.zip for information on specifying the use of other Java Virtual Machines.

3. Edit <jdev_install>/jdev/bin/jdev.conf to select another VM. Find the line:
   
   # SetJavaVM ojvm
   
   Right below this line, add a line containing the name of the Java Virtual Machine you want to use ("Hotspot" is an example):
   
   SetJavaVM hotspot
   
   

   Note: Because ojvm does not run on non-Windows platforms, you will not be able to use CodeCoach or Profiler, and the debugger will not run as quickly.

Starting Oracle JDeveloper

• To start Oracle 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 Oracle JDeveloper on other platforms, run the file <jdev_install>/jdev/bin/jdev .

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.The 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 jdev905.zip, ojvm was installed automatically. If you performed the base installation using jdev905_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.

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

  InstallOJVM.bat c:\j2sdk1.4.1_05


  where c:\ j2sdk1.4.1_05 is the location of your SDK.

Adding Local Documentation to a Base Installation

To install the documentation set, download jdev904_doc.zip from http://otn.oracle.com/products/jdev. You can install the documentation into Oracle 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 Oracle JDeveloper:

1. Start Oracle JDeveloper.
2. Select T ools | Preferences from the Oracle 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 .

Hosted Documentation

If you installed jdev904_base.zip, Oracle 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 jdev904.zip, Oracle JDeveloper is pre-configured to use local documentation. However, you can configure Oracle JDeveloper to use the documentation hosted on OTN.

Configuring Oracle JDeveloper to Use Documentation Hosted on OTN

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

Hosting Oracle JDeveloper Documentation on Your Own Web Server

You can set up your own web server for hosting documentation. This is especially useful if you want to add information to the Oracle JDeveloper documentation. For information on extending the Oracle JDeveloper documentation, refer to the Oracle Help for Java (OHJ) documentation, which is included with Oracle JDeveloper.

To set up Oracle JDeveloper documentation on your Web server:

1. Uncompress each JAR file located in <jdev_install>\jdev\doc\ohj into its own directory on your Web server. If you installed jdev904_base.zip, you will need to download the documentation ( jdev904_doc.zip) from http://otn.oracle.com/products/jdev.
2. Modify the file jdeveloper.hs to point to the correct URL for each of the .hs files on your server. Look at the file jdeveloper-hosted-example.xml in the <jdev_install>\jdev\doc\ohj \jdeveloper.jar for an example of how to edit this file.

Once you have installed the documentation to be hosted, your users will have to configure their copy of Oracle JDeveloper to use the documentation on your server:

1. From the Oracle JDeveloper main menu, select Tools | Preferences ,
2. Navigate to Documentation.
3. Select the U se Hosted Documentation radio button.
4. Provide the URL to the jdeveloper.hs file on your server. This URL should include the port number, even if you are using the default port (80).

Enabling Oracle JDeveloper Extensions

Before you can use an extension in Oracle9i JDeveloper (9.0.4), you first need to download the extension from OTN. The following are examples of Oracle9i JDeveloper (9.0.4) Extensions that are available:

• JUnit
• WebDAV
• iSQL*Plus

To automatically download and install an Oracle JDeveloper extension:

• From the Oracle 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 an Oracle JDeveloper Extension:

1. Go to http://otn.oracle.com/software/products/jdev/content.html, Oracle9i JDeveloper (9.0.4) Extensions .
2. Select a Oracle JDeveloper Extension.
3. Follow the instructions to download the zip file.

To manually install an Oracle JDeveloper extension:

1. Shut down any instances of Oracle 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 Oracle JDeveloper. After you restart Oracle JDeveloper, you will be able to use the extension.

Migrating User Settings from Previous Releases

Your user settings 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.4. For information about migration issues, see the topic Ways to Migrate to Oracle9i JDeveloper (9.0.4) in the Getting Started with JDeveloper book in the Online Help.

To migrate user settings (system settings, libraries, and connections) from previous installations of Oracle JDeveloper:

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

   jdev -migrate


   Note: It is not necessary to use this flag if you are running a newly installed version of Oracle JDeveloper for the first time and you do not want to migrate user settings from another installation of Oracle JDeveloper. Otherwise, any settings that you set on the first and subsequent runs will be clobbered when you later run Oracle JDeveloper with the -migrate flag. On subsequent runs of Oracle JDeveloper, use this flag to open the Migrate User Settings dialog.

2. When the Migrate User Settings dialog appears, select a version of Oracle 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 Oracle JDeveloper, for example:
   <previous_jdev_install>/jdev/system where <previous_jdev_install> is the root directory of the installation of Oracle 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 Oracle JDeveloper.

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  Oracle JDeveloper in a UNIX, your SDK isn't set up to use the font that is generating the error. Oracle 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.

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

Deploying Activity Modeler Generated Artifacts Requires 8.1 Database With 8.1 Queues

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.

Using Oracle JDeveloper in a Multiuser Environment

If you are using Oracle 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 Oracle 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 Oracle JDeveloper. In all cases, users can save their projects locally.

When installing and configuring Oracle JDeveloper for a multiuser 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 Oracle JDeveloper and your users.

Installing Oracle JDeveloper on a Citrix MetaFrame Server or a Microsoft Terminal Server

You need to have administrative privileges to install Oracle JDeveloper.

To Install Oracle JDeveloper on a Citrix MetaFrame or Microsoft Terminal Server:

1. Install Oracle JDeveloper as above.
2. Define the user home directory environment variable (see below).

Configuring User Home Directories in a Multiuser Environment

Before you run Oracle JDeveloper in a terminal server environment, you must define the user home environment variable and set its value for each user in order for Oracle JDeveloper to identify user home directories correctly. If the variable is not defined and set, Oracle JDeveloper uses the <jdev_install>/jdev as the home directory for all users. Using this directory may cause unstable behavior in Oracle 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 Oracle 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 in the previous procedure, 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 Oracle JDeveloper.
8. Oracle 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.

Configuring Terminal Server Clients for Running Oracle JDeveloper

These topics assume that you have already installed a Citrix MetaFrame or Microsoft Terminal Server client locally and that Oracle JDeveloper has been installed and configured by the System Administrator.

To configure a terminal server client for running Oracle JDeveloper:

1. Verify that the color resolution of the terminal server client has been set to a minimum of 256 colors. This minimum resolution is required by 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 Oracle JDeveloper.
6. Oracle 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 Oracle 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 -Xheapbase10000000

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 Oracle 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 Oracle JDeveloper and then copy the file:

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

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

Using OC4J with Oracle JDeveloper

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

If you performed the base installation of Oracle JDeveloper, OC4J will not run, and you will not be able to deploy or run your applications until you install the full SDK into <jdev_install> . You must also modify jdev.conf to point to this SDK home and specify a VM if you are not using ojvm. See Installing Oracle JDeveloper from jdev904_base.zip for more information.

You can start and stop the OC4J server in stand-alone mode using the provided start_oc4j and stop_oc4j batch files and shell scripts located in <jdev_install>\jdev\bin\ , or 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 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 oc4j.jar

  For HP-UX, use the alternate command:

java -XdoCloseWithReadPending -jar 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.

Oracle 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 at Getting Started with Oracle JDeveloper | Oracle JDeveloper Accessibility Information.

Using a Screen Reader and Java Access Bridge with Oracle JDeveloper

To make the best use of our accessibility features, Oracle Corporation recommends the following software configuration:

• Windows NT 4.0 (with Service Pack 6) or Windows 2000 (with Service Pack 3)
• Sun Java Access Bridge 1.0.3
• JAWS 3.70.87
• Microsoft Internet Explorer 5.5
• Java 2 SDK 1.4.1_05

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 Oracle JDeveloper window will appear, once Oracle 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 Oracle JDeveloper.

   Refer to the Installation Guide for more information about Oracle JDeveloper installation.

3. Download Java Access Bridge 1.0.3.

   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 Oracle 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 Oracle JDeveloper by running the file jdev.exe located in the folder <jdev_install>\jdev\bin .

Supported Deployment Environments

For deploying to OC4J and Oracle9iAS, as well as deploying to other J2EE servers such as Apache Tomcat, WebLogic, and JBoss, please refer to the Help topic "Ways to Deploy J2EE Applications" in the "Packaging and Deploying" book, which you can access by selecting Help | Help Topics from the Oracle JDeveloper main menu.

Uninstalling Oracle JDeveloper

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

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

Oracle JDeveloper Documentation

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

Oracle on the Web

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