Oracle JDeveloper 10g

Installation Guide
Version 10.1.2
November 2005

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

    3.2 Adding Local Documentation to a Base Installation
  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
  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. Using a Screen Reader and Java Access Bridge with JDeveloper

    16.1 Configuring JAWS 5.0 and Access Bridge with JDeveloper

    16.2 Configuring JAWS 3.70 and Access Bridge with JDeveloper
  17. Uninstalling JDeveloper
  18. JDeveloper Documentation
  19. Oracle on the Web

 

1. JDeveloper System Requirements

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

Note: These requirements are specific to JDeveloper and may differ from Oracle 10g Developer Suite.


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

Windows

 

Resource

Recommended

Operating System

Windows XP-Service Pack 2
Windows 2000-Service Pack 4
Windows NT-Service Pack 6a

CPU Type and Speed 

Pentium III 866 MHz or faster

Memory

512 MB RAM

Display 

65536 colors, set to at least 1024 X 768 resolution

Hard Drive Space

Base Installation: 230 MB
Complete Installation: 375 MB

Java SDK Sun J2SE 1.4.2_06 for Windows, available at: http://www.javasoft.com.

Linux

 

Resource

Recommended

Distribution

Red Hat Enterprise Linux 2.1
Red Hat Enterprise Linux 3.0
Red Hat Linux 9.0
SuSE SLES8

CPU Type and Speed 

Pentium III 866 MHz or faster

Memory

512 MB RAM

Display 

65536 colors, set to at least 1024 X 768 resolution

Hard Drive Space

Base Installation: 231 MB
Complete Installation: 390 MB

Java SDK

Sun J2SE 1.4.2_06 for Linux, available at: http://www.javasoft.com.

Note: If you want to use JDeveloper in a multiuser UNIX environment, Oracle recommends a minimum of 512 MB RAM and 1 GB of swap space.

Solaris

 

Resource

Recommended

Operating System

Solaris 2.8, or 2.9 using the CDE window manager

CPU Type and Speed 

Sparc 500 MHz or faster

Memory

512 MB RAM

Display 

65536 colors, set to at least 1024 X 768 resolution

Hard Drive Space

Base Installation: 231 MB
Complete Installation: 390 MB

Java SDK

Sun J2SE 1.4.2_06 for Solaris (32-bit), available at: http://www.javasoft.com.

MAC OS X

Resource

Recommended

Operating System

Apple Mac OS X Version 10.3

CPU Type and Speed 

Dual 1.25 GHz G4/G5 (1 GHz G4 minimum)

Memory

1 GB RAM (512 MB minimum)

Display 

"Thousands" of colors

Hard Drive Space

Base Installation: 231 MB
Complete Installation: 390 MB

Java SDK

Sun J2SE 1.4.2 Update 2 available at: http://developer.apple.com/java/download/ or from Mac OS X Software Update.

HP-UX

 

Resource

Recommended

Operating System

HPUX 11.0 and 11i

CPU Type and Speed 

HP PA-RISC 500 MHz or faster

Memory

512 MB RAM

Display 

65536 colors, set to at least 1024 X 768 resolution

Hard Drive Space

Base Install: 231 MB
Complete Installation: 390 MB

Java SDK

HP J2SE 1.4.2.02 for PA-RISC


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.

Oracle SCM

  • Oracle 9i SCM
  • Oracle SCM 10g (9.0.4)

Concurrent Version Support (CVS)

  • CVS versions 1.10 to 1.11.14
  • CVSNT versions 2.0.26 to 2.0.34

Back to TOC

 

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://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 ( jdev1012.zip) includes the Windows version of Sun J2SE 1.4.2_06 and the JDeveloper documentation.

To install JDeveloper from jdev1012.zip:


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.

Back to TOC

 

3. Installing JDeveloper Base

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

  • The base installation requires that you already have 1.4.2_06 of the Sun J2SE on your machine because the SDK is not included.
  • The base installation, by default, does not include JDeveloper documentation. Instead, the base installation requires a Web connection to access the documentation or you may separately install the documentation. See Adding Local Documentation to a Base Installation for details.

To install JDeveloper from jdev1012_base.zip:

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

    SetJavaHome d:\j2sdk1.4.2_06

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

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


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 jdev1012.zip, OJVM was installed automatically. If you performed the base installation using jdev1012_base.zip, you will need to manually install OJVM into your SDK. The batch file InstallOJVM.bat (provided with JDeveloper) will copy OJVM files into the specified SDK and update the configuration of that SDK. The files are copied into a separate OJVM directory and will not overwrite any of the existing files in the SDK.

To install OJVM with a base installation:

  • In <jdev_install>\jdev\bin\ execute the command:
    InstallOJVM.bat d:\j2sdk1.4.2_06
    where d:\j2sdk1.4.2_06 is the location of your SDK.


3.2 Adding Local Documentation to a Base Installation

To install the documentation set, download jdev1012_doc.zip from http://www.oracle.com/technology/products/jdev. You can install the documentation into JDeveloper, without any configuration, by extracting the files into <jdev_install> . The <jdev_install>\jdev\doc\ohj directory will be created.

If you install the documentation into any other local directory, you will need to configure the location in JDeveloper:

  1. Start JDeveloper.
  2. Choose T ools | Preferences | Documentation from the JDeveloper main menu.
  3. Select the Use Local Documentation radio button.
  4. Set the full path to where the local documentation is installed, which by default is <jdev_install>\jdev\doc\ohj .
  5. Click OK.

Back to TOC

 

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:


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 write and execute permissions for the following files:

  • chmod +x <jdev_install>/jdev/bin/jdev
  • chmod +x <jdev_install>/jdev/bin/ojc
  • chmod +x <jdev_install>/BC4J/bin/bc4j2oc4j
  • chmod +x <jdev_install>/jdev/bin/start_oc4j
  • chmod +x <jdev_install>/jdev/bin/stop_oc4j

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

Note: < jdev_install>/j2ee/home/application-deployments 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_06 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_06 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.
  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 a new font, or change your font.properties file. For information on installing new fonts on your computer, contact your vendor. For information on updating the font.properties file, see Sun's Font Overview documentation or your SDK vendor's documentation.


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


Back to TOC

 

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

  1. Mount the JDeveloper 10.1.2 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:
    • 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

If you installed jdev1012_base.zip, JDeveloper is preconfigured to use documentation hosted on OTN. Please note that the first launch of the hosted help system may take several minutes to initialize if you are on a low bandwith or high-latency connection.

If you installed jdev1012.zip, JDeveloper is preconfigured to use local documentation. However, you can configure JDeveloper to use the documentation hosted on OTN.

To configure JDeveloper to use documentation hosted on OTN:

  1. From the JDeveloper main menu, choose Tools | Preferences | Documentation .
  2. Select Use Hos ted Documentation on Oracle Technology Network .
  3. Click OK.

Back to TOC

 

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

Back to TOC

 

8. 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.2. If you are running a newly installed version of JDeveloper for the first time you will be prompted with a Migrate User Settings dialog. You can use this dialog to migrate your user settings by selecting Yes. If you select No, any settings that you set on the first and subsequent runs will be overwritten if you later run JDeveloper with the -migrate flag. For information about migration issues, see the " Migrating to JDeveloper 10g " topics in the online documentation, which you can access by choosing Help | Help Topics | Getting Started with JDeveloper from the JDeveloper main menu.

To migrate user settings from previous installations of JDeveloper:

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

    jdev -migrate

  2. When the Migrate User Settings dialog appears, select a version of 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 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.
  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 JDeveloper.

Back to TOC

 

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/technology/software/products/jdev/content.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\lib\ext 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.

Back to TOC

 

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

Note: Oracle Workflow Server 2.6.0 can be downloaded from http://www.oracle.com/technology/software/products/integration/content.html

  • 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://metalink.oracle.com/ 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.

Back to TOC

 

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 Help | About 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.

To configure a terminal server client for running 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 Java Sun J2SE 1.4.2_06.
  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 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 | 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.
to:
<jdev_install>\jdev\multi\system\DefaultWorkspace\Project1.jpr .
Back to TOC

 

12. Using OC4J with JDeveloper

Included with JDeveloper is a fully functioning version of Oracle Application Server 10g Release 2 (10.1.2) Containers for J2EE (OC4J). The embedded server resides in the following location in the JDeveloper installation:

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

Back to TOC


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

    Java -mx512M -jar oc4j.jar


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

Back to TOC

 

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) at: http://www.oracle.com/technology/products/jdev/collateral/papers/10g/as_supportmatrix.html.

For additional information, see the "Deploying JDeveloper" topics in the online documentation, which you can access by choosing Help | Help Topics from the JDeveloper main menu.

Back to TOC

 

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.

Database JDeveloper Feature
Database Certification Status Database Features SQL Worksheet PL/SQL

Oracle 8i 1 (8.1.7.4.12)

Full Certification Certified Certified Certified
Oracle9i 1 9.2.4.0) Full Certification Certified Certified Certified
Oracle Database 10g 1 Full Certification Certified Certified Certified
Oracle Lite (4.0.3) Partial Certification Certified 2 Certified Not Working
DB2 (7 release 2) Partial Certification Certified 3 Certified Not Working
SQL Server (2000) Partial Certification Certified 3 Certified Not Working
MySQL (4.0.14b) Not Certified Working 4 Working Not Working

 

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.

Back to TOC

 

15. Finding 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 help topics available by selecting the JDeveloper Accessibility Information node under Getting Started with Oracle JDeveloper in the online help table of contents.

Back to TOC

 

16. 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 XP, Service Pack 2
  • Java Sun J2SE 1.4.2_03 or higher
  • Sun Java Access Bridge 1.2 or higher
  • JAWS 5.0 (5.10.383 preferred)
  • 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.

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

    Refer to the Installation Guide for more information about installing JDeveloper.

  3. Download Java Access Bridge for Windows version 1.2. The file you will download is accessbridge-1_2.zip. It is available from:
    http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-java-client-419417.html.

    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 (unzip) the contents to a folder, for example, accessbridge_home.
  5. 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.

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

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

    During the installation of the Access Bridge 1.2 files, the installation may appear to be stalled.  If this occurs, the installation process will not proceed because it is attempting to test each JVM instance for proper configuration and has encountered a problem with this JVM.  Since the installation will not recover or continue if this occurs, note the file location of the JVM instance in the install dialog, then cancel the installation process.  Either repair the configuration problem with the JVM instance or remove the java.exe instance from that drive and restart the Access Bridge 1.2 installation. Details about this installation problem can be found in the Access Bridge 1.2 notes.txt file located in the <accessbridge_home> folder.
  8. Click OK when you see the Installation Completed message.
  9. 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:

    JavaAccessBridge.dll
    JAWTAccessBridge.dll
    WindowsAccessBridge.dll

    Note that the system directory is required in the PATH system variable.

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

    access-bridge.jar
    jaccess-1_3.jar
    jaccess-1_4.jar
    JavaAccessBridge.dll
    JAWTAccessBridge.dll
    WindowsAccessBridge.dll

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

    assistive_technologies=com.sun.java.accessibility.AccessBridge
    AWT.EventQueueClass=com.sun.java.accessibility.util.EventQueueMonitor
    AWT.assistive_technologies=com.sun.java.accessibility.AccessBridge

  12. Only if you are using JAWS version 3.70, 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

  13. Start your screen reader.
  14. 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. Then the main JDeveloper window will appear once JDeveloper has started. Any message that appears will not affect the functionality of JDeveloper.


16.1 Configuring JAWS 5.0 and Access Bridge with JDeveloper

JDeveloper is designed to be accessible with screenreader software. JDeveloper 10.1.2 has been tested with JAWS 5.0 and JAWS 3.70. Although our testing of JDeveloper 10.1.2 and JAWS 5.0 was completed using Access Bridge 1.1_GA, Access Bridge version 1.2_GA works with JDeveloper 10.1.2 and JAWS 5.0. You do not need to use rtpatch.jar when using JAWS 5.0.

Access Bridge version requirements for each version of JAWS are listed below. Please see the JDeveloper 10g Release Notes regarding issues with the different configurations.

Access Bridge v. 1.2_GA Configuration for JDeveloper 10.1.2 with JAWS 5.0

Place the following files in the JDeveloper directory [ \jdk\jre\lib\ext]:

access-bridge.jar size: 33184 version: AccessBridge_1_2_GA
JAWTAccessBridge.dll size: 32768 version: AccessBridge_1_2_GA
jaccess-1_3.jar size: 43642 version: AccessBridge_1_2_GA
jaccess-1_4.jar size: 46276 version: AccessBridge_1_2_GA
JavaAccessBridge.dll size: 155648 version: AccessBridge_1_2_GA
WindowsAccessBridge.dll size: 81920 version: AccessBridge_1_2_GA

Place the following file in the JDeveloper directory [ \jdk\jre\lib]:

accessibility.properties size: 153 version: AccessBridge_1_2_GA

Place the following files in the Windows system32 directory [\winnt\system32]:

JavaAccessBridge.dll size: 155648 version: AccessBridge_1_2_GA
WindowsAccessBridge.dll size: 81920 version: AccessBridge_1_2_GA
JAWTAccessBridge.dll size: 32768 version: AccessBridge_1_2_GA

Access Bridge v. 1.1_GA Configuration for JDeveloper 10.1.2 with JAWS 5.0

Place the following files in the JDeveloper directory [ \jdk\jre\lib\ext]:

access-bridge.jar size: 33136 version: AccessBridge_1_1_GA
JAWTAccessBridge.dll size: 32768 version: AccessBridge_1_1_GA
jaccess-1_3.jar size: 43584 version: AccessBridge_1_1_GA
jaccess-1_4.jar size: 46619 version: AccessBridge_1_1_GA
JavaAccessBridge.dll size: 155648 version: AccessBridge_1_1_GA
WindowsAccessBridge.dll size: 81920 version: AccessBridge_1_1_GA

Place the following file in the JDeveloper directory [ \jdk\jre\lib]:

accessibility.properties size: 153 version: AccessBridge_1_1_GA

Place the following files in the Windows system32 directory [\winnt\system32]:

JavaAccessBridge.dll size: 155648 version: AccessBridge_1_1_GA
WindowsAccessBridge.dll size: 81920 version: AccessBridge_1_1_GA
JAWTAccessBridge.dll size: 32768 version: AccessBridge_1_1_GA

16.2 Configuring JAWS 3.70 and Access Bridge with JDeveloper

The use of JDeveloper 10.1.2, JAWS 3.70, and AccessBridge1.1_GA is not a recommended configuration.  You may encounter JVM conflict exceptions when you attempt to launch JDeveloper 10.1.2. The latest version of Access Bridge, version 1.2_GA, does not require extensive configuration to work with JDeveloper 10.1.2 and JAWS 3.70.

To use earlier versions of Access Bridge with JDeveloper 10.1.2 and JAWS 3.70, the following combinations of Access Bridge file versions are necessary to achieve optimal functionality since this version of the screen reader uses older Java technology than is used in JDeveloper 10.1.2. There are two stacks of software technology listed below for those who want to use either version 1.0.3 or 1.0.4 of the Access Bridge. Note that the latest version of the Access Bridge Jar file is required in the system32 directory.

AccessBridge v. 1.2_GA Configuration for JDeveloper 10.1.2

Place the following files in the JDeveloper directory [ \jdk\jre\lib\ext]:

access-bridge.jar size: 33184 version: AccessBridge_1_2_GA
JAWTAccessBridge.dll size: 32768 version: AccessBridge_1_2_GA
jaccess-1_3.jar size: 43642 version: AccessBridge_1_2_GA
jaccess-1_4.jar size: 46276 version: AccessBridge_1_2_GA
JavaAccessBridge.dll size: 155648 version: AccessBridge_1_2_GA
WindowsAccessBridge.dll size: 81920 version: AccessBridge_1_2_GA

Place the following file in the JDeveloper directory [ \jdk\jre\lib]:

accessibility.properties size: 153 version: AccessBridge_1_2_GA

Place the following files in the Windows system32 directory [\winnt\system32]:

JavaAccessBridge.dll size: 155648 version: AccessBridge_1_2_GA
WindowsAccessBridge.dll size: 81920 version: AccessBridge_1_2_GA
JAWTAccessBridge.dll size: 32768 version: AccessBridge_1_2_GA

Access Bridge v. 1.0.4 Configuration for JDeveloper 10.1.2

Place the following files in the JDeveloper directory [ \jdk\jre\lib\ext]:

access-bridge.jar size: 27295 version: access-bridge-1.0.4
JAWTAccessBridge.dll size: 32768 version: AccessBridge-1.0.4
jaccess-1_4.jar size: 46573 version: AccessBridge-1.0.4
JavaAccessBridge.dll size: 139264 version: AccessBridge-1.0.4
WindowsAccessBridge.dll size: 77824 version: AccessBridge-1.0.4

Place the following file in the JDeveloper directory [ \jdk\jre\lib]:

accessibility.properties size: 153 version: AccessBridge-1.0.4

Place the following files in the Windows system32 directory [ \winnt\system32]:

JavaAccessBridge.dll size: 155648 version: AccessBridge_1_1_GA
WindowsAccessBridge.dll size: 77824 version: AccessBridge-1.0.3
JAWTAccessBridge.dll size: 28672 version: AccessBridge-1.0.3

Access Bridge v. 1.0.3 Configuration for JDeveloper 10.1.2

Place the following files in the JDeveloper directory [ \jdk\jre\lib\ext]:

access-bridge.jar size: 33184 version: access-bridge-1.0.4
JAWTAccessBridge.dll size: 32768 version: AccessBridge-1.0.3
jaccess-1_3.jar size: 43642 version: AccessBridge-1.0.3
jaccess-1_4.jar size: 46276 version: AccessBridge-1.0.3
JavaAccessBridge.dll size: 155648 version: AccessBridge-1.0.3
WindowsAccessBridge.dll size: 77824 version: AccessBridge-1.0.3

Place the following file in the JDeveloper directory [ \jdk\jre\lib]:

accessibility.properties size: 153 version: AccessBridge-1.0.3

Place the following files in the Windows system32 directory [\winnt\system32]:

JavaAccessBridge.dll size: 155648 version: AccessBridge_1_1_GA
WindowsAccessBridge.dll size: 77824 version: AccessBridge-1.0.3
JAWTAccessBridge.dll size: 28672 version: AccessBridge-1.0.3

Back to TOC

 

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

Back to TOC

 

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

Back to TOC

 

19. Oracle on the Web

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

Description  URL 

JDeveloper Home Page  

http://www.oracle.com/technology/products/jdev/ 

JDeveloper Discussion Forum

http://www.oracle.com/technology/discussionforums/jdev.html 

Corporate Site 

http://www.oracle.com/

Oracle Developer Suite-JDeveloper

http://www.oracle.com/tools/index.html

Oracle Technology Network 

http://www.oracle.com/technology/

Worldwide Customer Support 

http://www.oracle.com/support/ 

Oracle Accessibility Site http://www.oracle.com/accessibility/

Back to TOC

Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065, USA
http://www.oracle.com

Worldwide Inquiries:
1-800-ORACLE1
Fax 650.506.7200

Copyright © 2005, Oracle Corporation. All Rights Reserved.

false ,,,,,,,,,,,,,,,