Skip Headers
Oracle® Fusion Middleware Installation Guide for Oracle JDeveloper
11g Release 1 (11.1.1)

Part Number E13666-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
View PDF

Oracle® Fusion Middleware

Installation Guide for Oracle JDeveloper

11g Release 1 (11.1.1)

E13666-03

March 2009

This document provides information on:

1 Oracle JDeveloper System Requirements

This release of Oracle JDeveloper is tested and supported on the specific versions Windows, Linux, and Mac OS X, as listed in Section 1.1, "Recommended CPU, Memory, Display, and Hard Drive Configurations". In addition, it is supported on any operating system that supports Sun Java SE Development Kit (JDK) 6 Update 5 or later.

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

The following tables list the recommended CPU, memory, display, and hard drive requirements for the different operating systems:

The following table lists the recommended CPU, memory, display, and hard drive requirements for the Windows operating system:

Table 1 Recommended CPU, Memory, Display, and Hard Drive Requirements for Windows

Resource Recommended

Operating System

Windows Vista

Windows Server 2003 R2

Windows XP-Service Pack 2

CPU Type and Speed

Pentium IV 2 GHz or faster

Memory

Studio Edition: 2 GB RAM

Display

65536 colors, set to at least 1024 X 768 resolution

Hard Drive Space

Studio Edition: 2.25 GB

Java Edition: 103 MB

JDK

JDK 6.0 Update 7 for Windows, available at: http://java.sun.com/javase/downloads/index.jsp.


The following table lists the recommended CPU, memory, display, and hard drive requirements for the Linux operating system:

Table 2 Recommended CPU, Memory, Display, and Hard Drive Requirements for Linux

Resource Recommended

Distribution

Red Hat Enterprise Linux 5.0

Red Hat Enterprise Linux 4.0

Oracle Enterprise Linux 5.0

Oracle Enterprise Linux 4.0

SUSE Linux Enterprise Server 10

CPU Type and Speed

Pentium IV 2 GHz or faster

Memory

Studio Edition: 2 GB RAM

Java Edition: 103 MB

Display

65536 colors, set to at least 1024 X 768 resolution

Hard Drive Space

Studio Edition: 2.25 GB

Java Edition: 103 MB

JDK

JDK 6.0 Update 7 for Linux, available at: http://java.sun.com/javase/downloads/index.jsp.


The following table lists the recommended CPU, memory, display, and hard drive requirements for the Mac OS X operating system:

Table 3 Recommended CPU, Memory, Display, and Hard Drive Requirements for MAC OS X

Resource Recommended

Operating System

Apple Mac OS X Version 10.5.2 or later

CPU Type and Speed

64-bit Intel processors

Memory

Studio Edition: 2 GB RAM

Display

65536 colors, set to at least 1024 X 768 resolution

Hard Drive Space

Studio Edition: 2.25 GB

Java Edition: 103 MB

JDK

Sun Java SE 6 for Mac OS X 10.5, available at: http://www.apple.com/support/downloads/javaformacosx105update1.html.


1.2 Support for Team Based Development Tools

Oracle JDeveloper provides integrated support for the following team based development tools:

  • CVS version 1.11.x

  • CVSNT 2.5.x

  • Subversion 1.4.x

  • ClearCase SCM 7.0

  • Dimensions 10.1.2

  • Perforce 2007

  • Microsoft Team System 2008

2 Installing the Oracle JDeveloper Studio Edition

Oracle Installer can be used to install Oracle JDeveloper Studio, the ADF Runtime, and WebLogic Server 10g Release 3 (10.3) on your system.

Oracle Installer is available in the following forms:

You can download Oracle Installer from the Oracle Technology Network (OTN) web site: http://www.oracle.com/technology/software/products/jdev/index.html.

For more information about installing the ADF Runtime, see the "Deploying Fusion Web Applications" chapter in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

For more information about using the WebLogic Server in Oracle JDeveloper, see Section 11, "Using WebLogic Server with Oracle JDeveloper".

2.1 Before You Begin

Before you run the generic installer, ensure that the following prerequisites are satisfied:

  • You must have JDK 6.0 Update 5 or later installed on your system. If you don't have JDK 6.0 Update 5 installed, you can obtain it from: http://java.sun.com/javase/downloads/index.jsp.

  • To streamline your installation process, the JDK you wish to use with the product should be the one you use to start the installer program. In that case, be sure the desired JDK is the first one in your system PATH, or reference it explicitly on the command line.

  • If the JDK you use to launch the installer doesn't meet the minimum product requirements, you will be given the opportunity to browse for one during the installation process.

2.2 Launching the Installer

Depending on the type of installer you are using, you can begin the installation process in one of the following ways:

  • To launch the platform-independent installer, enter: java -jar jdevstudio11110install.jar.

  • To launch the Windows installer, double-click the jdevstudio11110install.exe file.

  • To launch the Linux installer, follow these steps:

    1. Ensure that the jdevstudio11110install.bin file is executable: chmod +x jdevstudio11110install.bin.

    2. Execute the file: ./jdevstudio11110install.bin.

You can also launch the installer in silent mode, to ensure that no configuration options are displayed during the installation process. For more information, see Section 16.1, "Installing Oracle JDeveloper Studio in Silent Mode".

2.3 Installer Screens

The installer provides several screens that allow you to specify various parameters for the installation:

  1. Welcome

    Click Next to begin the installation process.

  2. Choose Middleware Home Directory

    You can create a new Middleware Home directory, or select one from a list of existing Middleware Home directories. If you choose a directory that already has components installed on it, you are directly taken to the Choose Products and Components screen to select additional components to install.

    If you choose to create a new Middleware Home directory, the default provided is C:\Oracle\Middleware\ for Windows, and $HOME/Oracle/Middleware/ for Unix platforms.

    Caution:

    Ensure that you choose a directory that does not contain spaces. For example, do not use C:\Program Files as the Middleware Home.

    Note:

    For the remainder of this document, in the context of the Studio Edition, <install_dir> has been used to represent the Middleware Home directory that you have chosen. For example, if you selected C:\mw_home\ as your Middleware Home directory, then <install_dir> would refer to C:\mw_home\.
  3. Choose Install Type

    Select either Complete Install or Custom Install. The Complete Installation will install Oracle JDeveloper Studio, the ADF Runtime, and WebLogic Server on your system. Selecting Custom Installation takes you to the Choose Products and Components screen, where you can select the components you want to install.

  4. Choose Products and Components (Custom Install only)

    Select the components you wish to install. If you deselect a component that is needed by other components, those are deselected as well.

    Note:

    If some components are already installed on your Middleware Home directory, they will appear grayed out on this screen.
  5. JDK Selection (Generic Installer only)

    If you did not launch the generic installer with the JDK you wish to use for the product, or the one you launched it with does not meet the minimum requirements, you may select the location of your desired JDK now. Navigate to your JDK directory that contains the child folder bin, which in turn contains java.exe. For example, if the path for your java.exe is C:\JDK\jdk1.6.0_05\bin\java.exe, you should select C:\JDK\jdk1.6.0_05.

  6. Confirm Product Installation Directories

    View the directories that the components will be installed in. To make changes, click Back and navigate to the desired screen, or click Next to continue with the installation.

    Note:

    In addition to the disk space required by the components you have chosen to install, the installer needs 684MB of temporary work space. If there is insufficient disk space on your system, a dialog will appear informing you about it. You can then either free up space in your desired location, or click Previous and choose an alternate location on the Choose Middleware Home Directory screen.
  7. Install Windows Service (Windows systems only)

    Select to install the Node Manager Service. Node Manager is used to monitor, start, and stop server instances in a domain. For more information, refer to the Oracle WebLogic Server Installation Guide, located at: http://download.oracle.com/docs/cd/E12839_01/common/docs103/install/index.html.

    Note:

    Oracle JDeveloper and ADF do not require the use of the Node Manager Service.
  8. Choose Shortcut Location (Windows systems only)

    Select the Start Menu folder where you want to place your shortcuts. You can select one of the following options:

    • "All Users" Start Menu folder

      Select this option to provide all users registered on this machine with access to installed software. Only users with Administrator privileges can create shortcuts in the All Users folder.

    • Local user's Start Menu folder

      Select this option to ensure that other users registered on this machine will not have access to the Start menu entries for this installation.

  9. Installation Summary

    Displays the components that will be installed and total disk space that will be utilized.

  10. Installation status

    Displays the progress of the installation.

  11. Installation Complete

    Select Run Quickstart to open the Quickstart window once the installation process has ended. Quickstart enables you to easily launch installed components and access online documentation.

    Click Done to end the installation process.

2.4 Verifying Your Installation

To view information about which products and components were installed, open the registry.xml file, located at: <install_dir>/registry.xml.

3 Installing the Java Edition

The Oracle JDeveloper Java Edition does not require an installer. To install Oracle JDeveloper Java, you will need an unzip tool. You can download a free, cross-platform unzip tool, Info-Zip, available at: http://www.info-zip.org/.

Caution:

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

Caution:

Ensure that you install Oracle JDeveloper into a directory that does not contain spaces. For example, do not use C:\Program Files as the installation directory.

To install Oracle JDeveloper from jdevjavabase11110.zip:

  1. If you don't have JDK 6.0 Update 5 or later installed, you can obtain it from: http://java.sun.com/javase/downloads/index.jsp.

  2. Unzip jdevjavabase11110.zip to the target directory.

    Note:

    For the remainder of this document, in the context of the Java Edition, <install_dir> is used to represent the directory of the installation. For example, if you unzipped jdevjavabase11110.zip into C:\jdev_install\, then <install_dir> refers to C:\jdev_install.
  3. Specify the location of your JDK installation in the dialog that appears when you start Oracle JDeveloper for the first time. You will need to enter the path to java.exe.

4 Using Oracle JDeveloper on Windows

Once the installation is complete, you can begin using Oracle JDeveloper on Windows systems.

4.1 Starting Oracle JDeveloper

To start Oracle JDeveloper Studio on Windows, use any of the following methods:

  • From your Start Menu, select All Programs, then select Oracle Fusion Middleware 11.1.1.x.x, and then select Oracle JDeveloper Studio 11.1.1.x.x.

  • You can also start Oracle JDeveloper from the command line by running one of the following commands:

    • <install_dir>\jdeveloper\jdeveloper.exe

    • <install_dir>\jdeveloper\jdev\bin\jdevw.exe

    • <install_dir>\jdeveloper\jdev\bin\jdev.exe (to display a console window for internal diagnostic information)

4.2 Specifying the JDK location

Note:

This section is not applicable to the Studio edition.

Specify the location of your JDK installation in the dialog that appears when you start Oracle JDeveloper for the first time. You will need to enter the path to java.exe.

4.3 Changing the JDK location

To change a JDK location that you have previously specified, set the variable SetJavaHome in the file <install_dir>\jdeveloper\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 is in a directory called jdk1.6.0_05 on your D: drive, your entry in jdev.conf would look like:

SetJavaHome d:\jdk1.6.0_05

4.4 User Directories

The following lists the new default directory structure for user-specific content in Oracle JDeveloper for Windows:

  • The default location for the system subdirectory is now <install_dir>\jdeveloper\system\systemXX.XX.XX.XX, where XX.XX.XX.XX is the unique number of the product build.

  • The default location for user-generated content (previously stored in <install_dir>\jdev\mywork) is now C:\JDeveloper\mywork.

For more information on user directories and how to set the value for the home environment variable, see Section 9, "Setting the User Home Directory".

5 Using Oracle JDeveloper on Linux and UNIX Systems

Once the installation is complete, you can begin working with Oracle JDeveloper on Linux and UNIX systems.

5.1 Changing System Cursors

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 Oracle JDeveloper provides a set of cursors to replace the default set. You must have write access to the JDK in order to replace the cursors.

To replace the cursors:

  1. Make a backup copy of the default cursors located in the JDK directory at:

    <jdk_install>/jre/lib/images/cursors

  2. Extract the replacement cursors from the tar file at:

    <install_dir>/jdeveloper/jdev/bin/clear_cursors.tar

5.2 Starting Oracle JDeveloper

To start Oracle JDeveloper on Linux and UNIX, run the file <install_dir>/jdeveloper/jdev/bin/jdev.

5.3 Specifying the JDK location

Note:

This section is not applicable to the Studio edition.

When you start Oracle JDeveloper for the first time, the jdev script prompts you to provide the location of your JDK installation if it cannot locate it. You will need to enter the path to java.exe.

5.4 Changing the JDK location

To change a JDK location that you have previously specified, set the variable SetJavaHome in the file <install_dir>/jdeveloper/jdev/bin/jdev.conf to the location of your Java installation.

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

SetJavaHome /usr/local/java

6 Using Oracle JDeveloper on Mac OS X Platforms

Once the installation is complete, you can begin using Oracle JDeveloper on Mac OS X platforms.

Note:

TIn addition to the steps outlined in this document, this release requires additional workarounds to successfully use Oracle JDeveloper on Mac OS X platforms. Please refer to the Release Notes for more information.

6.1 Starting Oracle JDeveloper

To start Oracle JDeveloper, run the file <install_dir>/jdeveloper/jdev/bin/jdev.

6.2 Specifying the JDK location

Note:

This section is not applicable to the Studio edition.

When you start Oracle JDeveloper for the first time, the jdev script prompts you to provide the location of your JDK installation if it cannot locate it. You will need to enter the path to java.exe.

6.3 Changing the JDK location

To change a JDK location that you have previously specified, set the variable SetJavaHome in the file <install_dir>/jdeveloper/jdev/bin/jdev.conf to the location of your Java installation.

For example, in a Mac OS X environment, if the location of your JDK is in a directory called /usr/local/java, your entry in jdev.conf would look like:

SetJavaHome /usr/local/java

7 Migrating from a Previous Version

This version of Oracle JDeveloper supports migration from Oracle JDeveloper 10.1.3.4 and Oracle JDeveloper 11.1.1.0.x only. Oracle recommends migrating to Oracle JDeveloper 10.1.3.4 from all other earlier versions before migrating to this release of Oracle JDeveloper.

7.1 Migrating User Settings

When you start Oracle JDeveloper for the first time (and each time after adding a new extension), Oracle JDeveloper will prompt to ask whether to migrate your settings from a previous installation. Click Yes on this dialog to browse to the system directory of your previous installation. This will copy relevant user preferences and settings from the prior release to Oracle JDeveloper 11g.

To force Oracle JDeveloper to display the migration dialog after the initial start, use the -migrate flag, for example, jdev -migrate.

7.2 Migrating Projects

When you open an application or project that was created in a prior release, Oracle JDeveloper will prompt to migrate the project to Oracle JDeveloper 11g. Depending on the content of the projects, Oracle JDeveloper may display additional prompts to migrate some specific source files as well. Oracle recommends that you make a backup copy of your projects before migrating. See the Oracle JDeveloper page on OTN for more information about migrating specific types of projects to 11g.

8 Enabling Oracle JDeveloper Extensions

Before you can use an extension in Oracle JDeveloper, you first need to download the extension from OTN. An example of an available Oracle JDeveloper Extension is JUnit.

To automatically download and install a Oracle JDeveloper extension:

To manually download a Oracle JDeveloper Extension:

  1. Go to http://www.oracle.com/technology/products/jdev/101/update/exchange.xml.

  2. Select a Oracle JDeveloper Extension.

  3. Follow the instructions to download the zip file.

To manually install a Oracle JDeveloper Extension:

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

  2. From the Help menu, select Check for Updates.

  3. On Step 1 of the wizard, select Install from a Local File and navigate to the ZIP file.

  4. Finish the wizard and restart Oracle JDeveloper. After you restart Oracle JDeveloper, you will be able to use the extension.

For additional information, see the "Extending Oracle JDeveloper" topics in the online documentation, which you can access by selecting Table of Contents in the Help menu.

9 Setting the User Home Directory

This section provides instructions on how to define a user home environment variable and set its value for each user in order for Oracle JDeveloper to identify user home directories correctly.

The user home directory contains the user's preferences for Oracle JDeveloper (in the system subdirectory). It is also the default location for new projects (in the \JDeveloper\mywork\ directory) as well as other configuration files that are specific to a given user.

Caution:

Ensure that you choose a Home directory that does not contain spaces. For example, do not use C:\My Home as your home directory.

To define the name of the user home environment variable:

  1. Open the file <install_dir>\jdeveloper\jdev\bin\jdev.boot in a text editor. Use an editor that recognizes UNIX end-of-line characters, such as WordPad.

  2. Find the entry:

    ide.user.dir.var = JDEV_USER_HOME, JDEV_USER_DIR

    This is the default variable that Oracle JDeveloper will look for at startup. You can define or add any environment variable that Oracle JDeveloper should use. As the terminal server administrator, you may change the name of this variable to follow your system's naming conventions.

    Note:

    You can explicitly set the home environment variable by adding the following line in the jdev.boot file: ide.user.dir = <Path to preferred user directory>

    The output should look something like this: ide.user.dir = D:/users/jdoe

  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.

The user home directory can also be specified from the command line using this command:

jdev.exe -J-Dide.user.dir=<Path>

Example: jdev.exe -J-Dide.user.dir=D:/users/joe

9.1 Setting the Home Environment Variable on Windows

To set the home environment variable on a Windows systems, including individual users of Oracle JDeveloper on a multiuser system, use the following steps:

Caution:

Do not set the home environment variable to a directory that contains spaces. For example, do not specify C:\My Projects as the home directory.
  1. From the Windows Start menu, select Control Panel, and then select 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 ide.user.dir.var, as a user variable.

  5. Set the value of this variable to your home directory (for example, 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. From the Help menu, select About to verify that the value of ide.user.dir is set to your user home directory.

9.2 Setting the Home Environment Variable on Linux and UNIX

Use the following steps to set the environment variable on Linux and UNIX systems. The examples and syntax provided refer to the C Shell.

Caution:

Do not set the home environment variable to a directory that contains spaces. For example, do not specify home/jdoe/my projects as the home directory.
  1. In your startup configuration file (for example, .cshrc), set the environment variable to your preferred directory:

    setenv JDEV_USER_DIR $HOME/mydocs/jdevfiles

  2. Source the file to make your changes take effect:

    source .cshrc

  3. Display the environment variable to confirm the change:

    echo $JDEV_USER_DIR

    You should see output similar to the following:

    /home/jdoe/mydocs/jdevfiles

  4. Launch Oracle JDeveloper.

  5. From the Help menu, select About to verify that the value of ide.user.dir is set to your user home directory.

By default, the user home directory on Linux and UNIX is $HOME/jdevhome.

9.3 Setting the Home Environment Variable on Mac OS X

Use the following steps to set the environment variable on Mac OS X systems. The examples and syntax provided refer to the BASH shell.

Caution:

Do not set the home environment variable to a directory that contains spaces. For example, do not specify home/jdoe/my projects as the home directory.
  1. In your startup configuration file (for example, .bashrc), set the environment variable to your preferred directory:

    JDEV_USER_DIR=$HOME/mydocs/jdevfiles

  2. Export the new value of the environment variable:

    export JDEV_USER_DIR

  3. Source the file to make your changes take effect:

    . .profile

  4. Display the environment variable to confirm the change:

    echo $JDEV_USER_DIR

    You should see output similar to the following:

    /Users/jdoe/mydocs/jdevfiles

  5. Launch Oracle JDeveloper.

  6. From the Help menu, select About to verify that the value of ide.user.dir is set to your user home directory.

By default, the user home directory on Mac OS X is $HOME/jdeveloper.

10 Using Oracle JDeveloper in a Multiuser Environment

You can install Oracle 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 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 resource planning, such as number of users and power of the server to deliver optimal performance for Oracle JDeveloper and your users.

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

  2. Define the user home directory environment variable as instructed in Section 10.2, "Configuring User Home Directories in a Multiuser Environment" and in Section 10.3, "Configuring Terminal Server Clients for Running Oracle JDeveloper".

10.2 Configuring User Home Directories in a Multiuser Environment

Before you run Oracle JDeveloper in a terminal server environment, you may want to 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 <install_dir>\JDeveloper\system\ directory for each user for storing system settings, and C:\JDeveloper\mywork as the default user source directory for all users. See Section 9, "Setting the User Home Directory" for instructions on how to configure user home directory environment variables.

10.3 Configuring Terminal Server Clients for Running Oracle JDeveloper

This section assumes 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 Java JDK 6.0.

  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, as described in Section 9.1, "Setting the Home Environment Variable on Windows".

  5. Launch Oracle JDeveloper.

  6. Oracle JDeveloper will ask if you would like your user home directory to be created. Click Yes.

  7. From the Help menu, select 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 <install_dir>\jdeveloper\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 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, each user must modify the default project to apply this setting. To specify this value in the default project settings:

  1. From the Tools menu, select Default Project Properties.

  2. In the Default Project Properties dialog, click Run/Debug/Profile, and then click Edit.

  3. Click the Launch Settings node.

  4. On the Launch Settings page, enter -Xheapbase100000000 in the Java Options field.

11 Using WebLogic Server with Oracle JDeveloper

Note:

This section is not applicable to the Java edition.

Installing Oracle JDeveloper Studio 11g Release 1 (11.1.1) also automatically installs Oracle WebLogic Server 10g Release 3 (10.3). Oracle JDeveloper uses this preconfigured installation as the Integrated WLS, a Oracle JDeveloper-managed server for testing and debugging your applications from within the IDE. After installing Oracle JDeveloper, everything you need to begin developing, testing and debugging web applications is installed and configured for you; no additional configuration steps are necessary for development purposes.

For additional information on using a standalone WLS with Oracle JDeveloper, please refer to the Help topic "Connecting and Deploying to Oracle WebLogic Server" in the Oracle JDeveloper online documentation.

11.1 Configuring WebLogic Server for ADF

The WLS domain that is created for you during installation, DefaultDomain, is not intended for use outside of the IDE. To deploy ADF applications to a standalone WLS server, the server must be configured to run ADF applications.

To prepare WLS for running ADF applications:

  1. Install WebLogic Server 10g Release 3 (10.3). Use Oracle Installer to install at least the WebLogic Server Core Application Server and Configuration Wizard and Upgrade Framework components. You can install WLS 10g Release 3 using any of the Oracle distribution media.

    For more information about installing WLS, refer to the following WebLogic Server documentation:

  2. Add ADF runtime libraries to the WebLogic Server environment. If you did not install the Application Development Framework Runtime component during installation of WebLogic Server, you can do so by running Oracle Installer as described in Section 2.2, "Launching the Installer". Perform a custom installation, and install the ADF Runtime component into the existing WLS home. This step provides the necessary patches to WLS for ADF, and copies the ADF runtime jar files and domain templates to the server environment.

    For more information about adding the ADF runtime libraries to a stand-alone WLS, see the "Installing the ADF Runtime to the WebLogic Installation" section in see the "Deploying Fusion Web Applications" chapter in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

  3. Configure a new or existing domain for ADF runtime. Before deploying an ADF application to WLS, you must configure a domain for ADF runtime. Use the WebLogic Configuration wizard to create a new domain configured automatically to support Application Development Framework runtime or to extend an existing domain with the ADF runtime domain templates.

    For more information about configuring WLS domains and preparing a domain for running ADF applications, refer to the following documentation:

12 Application Servers Supported by Oracle JDeveloper

Note:

This section is not applicable to the Java edition.

A matrix associating Oracle 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/htdocs/11/.

For additional information, see the "Deploying Applications" topics in the JDeveloper online documentation, which you can access by Table of Contents from the Help menu.

13 Database Certification for Oracle JDeveloper

Note:

This section is not applicable to the Java edition.

A matrix associating Oracle and non-Oracle databases with Oracle JDeveloper features they are certified against is available on Oracle Technology Network (OTN) at: http://www.oracle.com/technology/products/jdev/htdocs/11/.

14 Web Browsers Supported by Oracle JDeveloper

Oracle JDeveloper supports the following web browsers:

15 Mobile Browsers Supported by Oracle JDeveloper

Oracle JDeveloper supports the following mobile browsers:

16 Oracle JDeveloper Accessibility Information

The following sections provide information on how to use accessibility features in Oracle JDeveloper, including how to perform a silent installation.

16.1 Installing Oracle JDeveloper Studio in Silent Mode

Silent-mode installation is a way of setting installation configurations only once to ensure that no configuration options are displayed during the installation process. During installation in silent mode, the installation program reads the settings for your configuration from an XML file that you create before beginning the installation.

To install in silent mode:

  1. Create a silent.xml file that defines the configuration settings that will be used for the installation. See Section Section 16.1.1, "Creating the silent.xml file" for more information.

  2. Start the silent installation by using the following command:

    java -jar jdevstudio11110install.jar -mode=silent -log=log.txt

    The -log=log.txt argument maintains a log of the installation in the log.txt file. Information contained in the log file helps you investigate installation failures.

    Note:

    To use a silent.xml file in a location other than the directory in which Oracle Installer resides, also use the additional argument -silent_xml=<your_location>\silent.xml.

16.1.1 Creating the silent.xml file

The silent.xml file contains several parameters that you can provide values for to indicate your configuration preferences.

The parameters and their descriptions are listed in the Table 4, "silent.xml file Parameters":

Table 4 silent.xml file Parameters

Resource Recommended

BEAHOME

The full path for the Oracle Middleware Home directory of your choice, for example, C:\Oracle\Middleware\.

In a silent install, specifying a value for this parameter in silent.xml is mandatory.

COMPONENT_PATHS

Specify the components and subcomponents to be installed. If this parameter is not mentioned in silent.xml, all components are installed by default.

Guidelines for component selection:

  • If you specify a component to be installed, all its subcomponents are automatically installed. For example, if you specify the value Oracle JDeveloper and ADF for this parameter, both its subcomponents, Oracle JDeveloper Studio and Application Development Framework Runtime are automatically installed.

  • To install multiple components, separate the components with a bar (|). To install subcomponents, specify a component/subcomponent combination. For example, to install Application Development Framework Runtime, use the value JDeveloper and ADF/Application Development Framework Runtime.

  • If components you specify have dependencies on other components that have not been specified, those components also get installed.

INSTALL_SHORTCUT_IN_ALL_USERS_FOLDER

Possible values:

  • yes/true: The shortcuts are created in All Users folder (default).

  • false/no: The shortcuts are created in the local user's folder.

You must have Administrator privileges to install the shortcuts in the All Users folder.

LOCAL_JVMS

Specify the location of your Java directory. This parameter need not be specified if you launched Oracle Installer with the desired JDK.


16.1.2 Sample silent.xml file

For example, you may want to specify a silent installation with the following configuration options:

  • Middleware Home Directory: C:\Oracle\Middleware\.

  • Components to Install: Oracle JDeveloper Studio and Application Development Framework Runtime.

  • Java Location: C:\jdk\jdk1.6.0_07\.

  • Shortcuts created in the local user's Start Menu folder.

To achieve this configuration, your silent.xml file should be coded like this:

<?xml version="1.0" encoding="UTF-8"?>
<bea-installer>
    <input-fields>
        <data-value name="BEAHOME" value="C:\Oracle\Middleware"/>
        <data-value name="COMPONENT_PATHS" value="JDeveloper and ADF/JDeveloper Studio|JDeveloper and ADF/Application Development Framework Runtime"/>
        <data-value name="LOCAL_JVMS" value="C:\jdk\jdk1.6.0_07\"/>
        <data-value name="INSTALL_SHORTCUT_IN_ALL_USERS_FOLDER" value="false"/>
    </input-fields>
</bea-installer>

For more information about silent-mode installation for WebLogic Server, please see the WebLogic Server Installation Guide at: http://download.oracle.com/docs/cd/E12839_01/common/docs103/install/index.html.

16.2 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 minimum technology stack:

  • Windows NT 4.0 (with Service Pack 6), Windows 2000, or Windows XP

  • Java Sun J2SE 1.5.0_05

  • Sun Java Access Bridge 2.0.1

  • JAWS 7.0+

  • Microsoft Internet Explorer 5.5 or higher

Please refer to the following procedures to set up a screen reader and Java Access Bridge. If you are using JAWS 7.00.135U, see also Section 16.3, "Configuring JAWS 7.0 and Access Bridge with Oracle JDeveloper" for additional configuration information.

  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.

    For information about performing a silent installation, see Section 16.1, "Installing Oracle JDeveloper Studio in Silent Mode".

  3. Download Java Access Bridge for Windows version 2.0.1. The file you will download is accessbridge-2_0_1.zip. It is available from: http://java.sun.com/products/accessbridge.

    Refer to the Java Access Bridge documentation available from this web site for more information about installation and the Java Access Bridge.

  4. 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 JDK 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 Oracle JDeveloper build and the JDK 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 JDK or Oracle 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.

  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 Oracle 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 <install_dir>\jdk\jre\lib\ext directory, or copy them from <accessbridge_home>\installer\installerFiles:

    access-bridge.jar
    jaccess-1_4.jar
    
  11. Confirm that the file accessibility.properties has been installed in the <jdev_home>\jdk\jre\lib directory, or copy it from \installer\installerFiles.

  12. Start your screen reader.

  13. Start Oracle JDeveloper by running the file jdev.exe located in the folder <install_dir>\jdeveloper\jdev\bin.

The steps above assume you are running Windows and using a Windows-based screen reader. A console window that contains error information (if any) will open first and then the main Oracle JDeveloper window will appear, once Oracle JDeveloper has started. Any messages that appear will not affect the functionality of Oracle JDeveloper.

16.3 Configuring JAWS 7.0 and Access Bridge with Oracle JDeveloper

The following combinations of Access Bridge file versions are necessary to achieve optimal functionality with JAWS 7.0. Also required in the system32 directory is a copy of the latest version of the Access Bridge jar file.

16.3.1 Access Bridge v. 2.0.1 Configuration for Oracle JDeveloper

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

access-bridge.jar
jaccess-1_4.jar

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

accessibility.properties

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

JavaAccessBridge.dll
JAWTAccessBridge.dll
WindowsAccessBridge.dll 

16.4 Finding 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 Oracle JDeveloper Accessibility Information node under Oracle JDeveloper Basics in the online help table of contents.

17 Uninstalling Oracle JDeveloper

To uninstall Oracle JDeveloper Studio, run the uninstaller which is located at:

Note:

The uninstaller removes only those files that were created at the time of installation and were not modified post installation. Therefore, any files that were created or modified after the installation are left as is. A message about the files and folders that have not been removed is displayed at the end of the process. You can delete these files if you wish to.

To uninstall Oracle JDeveloper Java Edition:

18 Oracle on the Web

Oracle provides a number of resources on the Web. Some sites you may find helpful are listed in Table 5, "Oracle on the Web":

Table 5 Oracle on the Web

Description URL

JDeveloper Home Pages

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

Oracle JDeveloper Discussion Forum

http://forums.oracle.com/forums/forum.jspa?forumID=83

Corporate Site

http://www.oracle.com/

Oracle Technology Network

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

Oracle Accessibility Site

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


19 Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

TTY Access to Oracle Support Services

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, 7 days a week. For TTY support, call 800.446.2398. Outside the United States, call +1.407.458.2479.


Oracle® Fusion Middleware Installation Guide for Oracle JDeveloper, 11g Release 1 (11.1.1)

E13666-03

Copyright © 1997, 2009, Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.