Installing Oracle9i JDeveloper Version 9.0.3.2

• JDeveloper System Requirements
• Installing JDeveloper
• Configuring the JDK in JDeveloper on Non-Windows Platforms
• Starting JDeveloper
• Installing ojvm on Windows to Run CodeCoach and Profiler, and to Improve Debugger Performance
• Upgrade the BC4J Runtime Libraries in iAS
• Adding Local Documentation to a Base Installation
• Hosted Documentation
• Enabling JDeveloper Extensions
• Migrating User Settings from Previous Releases
• Font Problems in UNIX
• Required Component Versions for E-Business Integration
• Using JDeveloper in a Multiuser Environment
• Using OC4J with JDeveloper
• JDeveloper Accessibility Information
• Supported Deployment Environments
• Uninstalling JDeveloper
• JDeveloper Documentation

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

JDeveloper System Requirements

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

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

Windows

Linux

Solaris

Resource	Recommended
Operating System	Solaris 2.6, 2.7, or 2.8 using the CDE window manager
CPU Type and Speed	Sparc 333 MHz
Memory	256 MB RAM
Display	65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space	Base Install: 160 MB Complete Install: 275 MB
JDK	Sun JDK 1.3.1_02, available here.

HP-UX

Resource	Recommended
Operating System	HPUX 11.0 using the CDE or VUE window managers
CPU Type and Speed	HP PA-RISC 200 MHz
Memory	256 MB RAM
Display	65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space	Base Install: 160 MB Complete Install: 275 MB
JDK	HP JDK 1.3.1_02, available at https://www8.hp.com/in/en/home.html

Installing JDeveloper

Note: Do not install this JDeveloper release into any ORACLE_HOME. You will not be able to uninstall it using Oracle Universal Installer.

Note: Do not install this JDeveloper release over any previous version of JDeveloper. Install this version of JDeveloper into a new directory.

Note: To install JDeveloper, you will need an unzip tool. You can download a free, cross-platform unzip tool, Info-Zip, available at http://www.info-zip.org.

The full installation ( jdev9032.zip) includes the Windows version of JDK1.3.1_02 and the JDeveloper documentation.

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

• The base install requires that you already have JDK 1.3.1_02 on your machine, as the JDK is not included in the base install.
• The base install, by default, does not include JDeveloper documentation. Instead, the base install requires a Web connection to access the documentation.

Installing JDeveloper from jdev9032.zip

• Unzip jdev9032.zip in the directory you want to install JDeveloper.
• If you install jdev9032.zip on a Unix or Linux system, you have to modify jdev.conf to specify the JDK and VM. See the next two sections 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:\jdev9i, the <jdev_install> would be c:\jdev9i.

Installing JDeveloper from jdev9032_base.zip

If you don't have Java™ 2, version 1.3.1_02 installed, you can obtain it.

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

Unzip jdev9032_base.zip in the directory you want to install JDeveloper.

Set the variable SetJavaHome in the file <jdev_install>\jdev\bin\jdev.conf to the location of your JDK 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 JDK 1.3.1_02 is in a directory called jdk1.3 on your D drive, your entry in jdev.conf would look like:

SetJavaHome d:\jdk1.3

In a UNIX environment, if the location of your JDK is in a directory called /local/java/jdk, your entry in jdev.conf would look like:

SetJavaHome /local/java/jdk

You can use either a local JDK or a JDK on a mounted drive.

If you are using 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 JDeveloper. The ojvm will also make the JDeveloper debugger run more quickly. See Installing ojvm on Windows to Run CodeCoach and Profiler, and to Improve Debugger Performance in this installation guide.

If you are using 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.

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

Configuring the JDK in JDeveloper on Non-Windows Platforms

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

If you don't have Java™ 2, version 1.3.1_02 installed, install it. You can get a copy for many operating systems from here, 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 JDK 1.3.1_02 is in a directory called /local/java/jdk, your entry in jdev.conf would look like:

SetJavaHome /local/java/jdk

You can use either a local JDK or a JDK on a mounted drive. Also, see the previous section, Installing JDeveloper from jdev9032_base.zip for information on specifying the use of other Java Virtual Machines.

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.

You'll also need to set permissions on directories and files. See Modifying Permission on a non-Windows Multiuser System for more information.

Starting JDeveloper

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

Installing ojvm on Windows to Run CodeCoach and Profiler, and to Improve Debugger Performance

Note: You can only perform this procedure on a Windows platform using OJVM. CodeCoach and Profiler are not available on non-Windows platforms.

To use CodeCoach and Profiler, you need to install ojvm, the specialized Oracle Java Virtual Machine for JDeveloper.The ojvm will also make the JDeveloper debugger run faster. If you performed the complete installation using jdev9032.zip, ojvm was installed automatically. If you performed the base installation using jdev9032_base.zip, you will need to manually install ojvm into your JDK. The batch file InstallOJVM.bat (provided with JDeveloper) will copy ojvm files into the specified JDK and update the configuration of that JDK. The files are copied into a separate ojvm directory and will not overwrite any of the existing files in the JDK.

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

InstallOJVM.bat c:\jdk

where c:\jdk is the location of your JDK.

If you later install a different JDK, you will have to copy the ojvm files into the new JDK by running the command

<jdev_install>\jdev\bin\InstallOJVM.bat c:\newjdk

where c:\newjdk is the location of your new JDK.

Upgrade the BC4J Runtime Libraries in iAS

To take advantage of the BC4J runtime bug fixes with iAS, you'll have to update the libraries on your iAS server.

Upgrading the BC4J Runtime Libraries on an iAS Server

Using Enterprise Manager, shutdown iAS.

Backup your current runtime libraries by copying %IAS_HOME%\BC4J to %IAS_HOME%\BC4J_old.

Copy the following files from %JDev_HOME%\BC4J\jlib to %IAS_HOME%\BC4J\jlib

bc4jctvb.jar                                   
    bc4jdomgnrc.jar                                   
    bc4jmtvb.jar                                   
    bc4jui.jar

Copy the following files from %JDev_HOME%\BC4J\lib to %IAS_HOME%\BC4J\lib

bc4j_jclient_common.jar                            
    bc4jct.jar                      
    bc4jctejb.jar                
    bc4jdomorcl.jar        
    bc4jhtml.jar         
    bc4jimdomains.jar       
    bc4jmt.jar             
    bc4jmtejb.jar      
    bc4juixtags.jar       
    collections.jar      
    datatags.jar

Copy the following file from %JDev_HOME%\BC4J\redist to %IAS_HOME%\BC4J\redist

bc4j.ear

Backup %IAS_HOME%\j2ee\home\applications\BC4J.ear by renaming it to BC4J.ear.old

Copy %IAS_HOME%\BC4J\redist\bc4j.ear to %IAS_HOME%\j2ee\home\applications\BC4J.ear

Delete %IAS_HOME%\j2ee\home\applications\BC4J

Restart iAS using Enterprise Manager.

Adding Local Documentation to a Base Installation

To install the documentation set, download jdev9032_doc.zip from /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:

Start JDeveloper.

Select T> ools | Preferences > from the JDeveloper main menu.

In the preferences tree, navigate to Documentation.

Select the Use Local Documentation radio button.

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 jdev9032_base.zip, JDeveloper is pre-configured to use documentation hosted on OTN. Please note that the first launch of the hosted help system may take several minutes to initialize if you are on a low-bandwith or high-latency connection.

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

Configuring JDeveloper to Use Documentation Hosted on OTN

From the JDeveloper main menu, select Tools | Preferences >.

Navigate to Documentation>.

Select the Use Hos ted Documentation on Oracle Technology Network > radio button.

Hosting 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 JDeveloper documentation. For information on extending the JDeveloper documentation, refer to the Oracle Help for Java (OHJ) documentation, which is included with JDeveloper.

To set up JDeveloper documentation on your Web server:

Uncompress each JAR file located in <jdev_install>\jdev\doc\ohj into its own directory on your Web server. If you installed jdev9032_base.zip, you will need to download the documentation ( jdev9032_doc.zip) from /products/jdev.

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 JDeveloper to use the documentation on your server:

From the JDeveloper main menu, select Tools | Preferences ,

Navigate to Documentation>.

Select the U se Hosted Documentation radio button.

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

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

• JUnit
• WebDAV
• iSQL*Plus

To download a JDeveloper Extension:

Go to http://www.oracle.com/tools/downloads/Jdeveloper-12c-downloads.html, Oracle9i JDeveloper Extensions>.

Select a JDeveloper Extension.

Follow the instructions to download the zip file.

To install a JDeveloper extension:

Shut down any instances of Oracle9i JDeveloper that are running on your machine.

Verify if there are additional installation instructions in the extension archive.

Unzip the downloaded archive into your <jdev_install>\jdev\lib\ext directory.

Restart JDeveloper. After you restart 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.3. For information about migration issues, see the topic Ways to Migrate to Oracle9i JDeveloper 9.0.3 in the Getting Started with JDeveloper book in the Online Help.

To migrate user settings (system settings, libraries, and connections) from previous installations of Oracle9i 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/system where <previous_jdev_install> is the root directory 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.

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 on a UNIX computer, your JDK isn't set up to use the font that is generating the error. JDeveloper, by default, uses the information in the file font.properties included with each JDK. 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 JDeveloper in a Multiuser Environment

If you are using JDeveloper in a multiple user, non-Windows environment, you will have to modify some permissions.

You can install JDeveloper in Microsoft Terminal Server, Citrix MetaFrame and MetaFrame XP (for Windows), and MetaFrame 1.1 for Unix environments, allowing many clients to access one installation of JDeveloper. In all cases, users can save their projects locally.

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

Modifying Permissions on a non-Windows Multiuser System

All JDeveloper files must have read permissions:

chmod -R g+r <jdev_install>

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

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

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:

Install JDeveloper as above.

Define the user home directory environment variable (see below).

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

From the Windows Start menu, select 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 in the previous procedure, 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.

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 Sun's JDK.

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, select 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 -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 JDeveloper. When you save the file, WordPad will warn you that it is about to save the file in text-only format. You can ignore this warning.

In addition, you will need to set the same option with the same value in Project | D efault Project Settings | Runner | Java > options.

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

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

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

Using OC4J with JDeveloper

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

If you performed the base installation of JDeveloper, OC4J will not run, and you will not be able to deploy or run your applications until you install the full JDK into <jdev_install> . You must also modify jdev.conf to point to this JDK home and specify a VM if you are not using ojvm. See Installing JDeveloper from jdev9032_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:

Execute the following command:

java -jar oc4j.jar -install

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

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.

JDeveloper Accessibility Information

For the latest configuration information or for information on addressing accessibility and assistive technology issues

Using a Screen Reader and Java Access Bridge with 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
• Sun Java Access Bridge 1.0.2
• JAWS 3.70.87
• Microsoft Internet Explorer 5.5
• JDK 1.3.1

Please refer to the following information to set up a screen reader and Java Access Bridge. These steps assume you are running Windows and using a Windows-based screen reader. A console window that contains error information (if any) will open first and then the main JDeveloper window will appear, once JDeveloper has started.

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 previous sections in this document for more information about JDeveloper installation.

Download Java Access Bridge 1.0.2. The file you will download is accessbridge-1_0_2.zip. It is available from www.oracle.com/java/technologies/javase/javase-tech-access-bridge.html. 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 the contents to a folder; for example, accessbridge_home.

Install Java Access Bridge by running Install.exe from the <accessbridge_home>\installer folder.

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.

Confirm that two jar files: access-bridge.jar and jaccess-1_3.jar were added to the folder <jdev_install>\jdk\jre\lib\ext during the install. If necessary, copy them from <accessbridge_home>\installer\installerFiles to <jdev_install>\jdk\jre\lib\ext.

Confirm that two DLL files, JavaAccessBridge.dll and WindowsAccessBridge.dll were added to the folder <jdev_install>\jdk\jre\lib\ext. If necessary, copy them from <accessbridge_home>\installer\installerFiles to <jdev_install>\jdk\jre\lib\ext.

Add the files listed above, JavaAccessBridge.dll and WindowsAccessBridge.dll, to the Winnt\System32 directory, as they must be in the system path in order to work with JDeveloper.

Confirm that the PATH environment variable has been updated to include the directory where the DLL files were installed, <jdev_install>\jdk\jre\lib\ext.

Confirm that the file <jdev_install>\jdk\jre\lib\accessibility.properties includes the following line:

assistive_technologies=com.sun.java.accessibility.AccessBridge

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

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

It is also necessary to use Hotspot instead of OJVM to run JDeveloper. To do this, set the SetJavaVM line in the jdev.conf file as follows:

SetJavaVM hotspot

Start your screen reader.

Start JDeveloper by running the file jdev.exe located in the folder <jdev_install>\jdev\bin.

Supported Deployment Environments

For deploying to OC4J and Oracle9iAS, see the Oracle9i JDeveloper Version 9.0.3 Release Notes. For specific information about 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 JDeveloper main menu.

Uninstalling JDeveloper

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

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

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.

Oracle on the Web

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