Oracle� JDeveloper 10g  Java Developer Preview

Installation Guide
Version 10.1.3.0.1
November 2004

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

Table of Contents

  1. JDeveloper System Requirements
    1.1  Recommended CPU, Memory, Display, and Hard Drive Configurations
    1.2  Support for Team Based Development Tools
  2. Installing JDeveloper Full Version
  3. Installing JDeveloper Base
    3.1  Installing OJVM with a Base Installation on Windows
  4. Installing JDeveloper on Non-Windows Platforms
    4.1  Modifying Permissions on Non-Windows
    4.2  Configuring the Java SDK in JDeveloper on Non-Windows Platforms
    4.3  Font Problems in UNIX
    4.4  Cursor Problems on Non-Windows Platforms
    4.5  Reusing Mozilla Profile Instance
  5. Installing and Starting JDeveloper on Mac OS X Platforms
  6. Configuring JDeveloper to Use Hosted Documentation
  7. Starting JDeveloper
  8. Migrating User Settings from Previous Releases
  9. Enabling JDeveloper Extensions
  10. Using JDeveloper in a Multiuser Environment
    10.1  Installing JDeveloper on a Citrix MetaFrame Server or a Microsoft Terminal Server
    10.2  Configuring User Home Directories in a Multiuser Environment
    10.3  Configuring Terminal Server Clients for Running JDeveloper
  11. Finding JDeveloper Accessibility Information
  12. Uninstalling JDeveloper
  13. JDeveloper Documentation
  14. Oracle on the Web

1. JDeveloper System Requirements

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

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

Windows

 

Resource

Recommended

Operating System

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

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: 47 MB
Complete Installation: 123 MB

Java SDK Sun J2SE 1.4.2_04 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: 50 MB
Complete Installation: 133 MB

Java SDK

Sun J2SE 1.4.2_04 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.

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: 49 MB
Complete Installation: 132 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.

1.2 Support for Team Based Development Tools

JDeveloper provides integrated support for the following source control systems:

ClearCase

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

Note: JDeveloper does not support ClearCase UCM.

Concurrent Version Support (CVS)

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

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


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

To install JDeveloper from jdevjava1013.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 ( jdevjavabase1013.zip ):

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

To install JDeveloper from jdevjavabase1013.zip:

  1. If you don't have Java� 2 Platform, Standard Edition, version 1.4.2_04 installed, you can obtain it from: http://www.javasoft.com .
  2. Unzip  jdevjavabase1013.zip  to the target directory.
  3. Set the variable  SetJavaHome  in the file  <jdev_install> \jdev\bin\jdev.conf  to the location of your SDK installation. Use an editor that recognizes UNIX end-of-line characters, such as WordPad. When you save the file, WordPad will warn you that it is about to save the file in text-only format. You can ignore this warning.

    For example, in a Windows environment, if the location of your Sun J2SE 1.4.2_04 is in a directory called j2sdk1.4.2_04 on your D: drive, your entry in  jdev.conf  would look like:

     

    SetJavaHome d:\j2sdk1.4.2_04

     

  4. If you do not set the variable SetJavaHome you will be asked at the first start of JDev to provide the path to the location of your SDK installation.
  5. In order to use the Profilers and CodeCoach, you will need to install OJVM, the specialized Oracle Java Virtual Machine for JDeveloper. The OJVM will also make the JDeveloper debugger run more quickly. See  Installing OJVM on Windows  in the next section.

    Note:  JDeveloper provides OJVM, and OJVM can be installed for use with JDeveloper, but this configuration is only supported for JDeveloper projects, not the JDeveloper IDE. For information about OJVM on Linux please refer to the JDeveloper Release Notes at:  <jdev_install>/jdev/readme.html .

3.1 Installing OJVM with a Base Installation on Windows

To use CodeCoach and the Profilers with a base installation you need to install OJVM, the specialized Oracle Java Virtual Machine for JDeveloper. OJVM will also increase the speed of the JDeveloper debugger, and provide automatic deadlock detection and memory debugging features. If you performed the complete installation using  jdevjava1013.zip, OJVM installed automatically. If you performed the base installation using  jdevjavabase1013.zip, upon the first start of JDeveloper you will be asked if you want to install OJVM into your SDK. If accepted JDev will copy OJVM files into the specified SDK and update the configuration of that SDK. The files are copied into a separate OJVM directory and will not overwrite any of the existing files in the SDK.

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

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

  • chmod +x  <jdev_install> /jdev/bin/jdev
  • chmod +x  <jdev_install> /jdev/bin/ojc
  • chmod +x  <jdev_install> /jdev/bin/ojaudit
  • chmod +x  <jdev_install> /jdev/bin/addjdevtodesktop

4.2 Configuring Java SDK in JDeveloper on Non-Windows Platforms

The complete installation of JDeveloper is configured to use Java Sun J2SE 1.4.2_04 for Windows platforms. If you install JDeveloper on another platform, perform the following steps to configure JDeveloper to use the appropriate SDK.

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

4.5 Reusing Mozilla Profile Instance

When using Mozilla on a non-Windows system, you will need to close the browser each time before running your web application again. You can avoid this problem and reuse your Mozilla profile instance by setting the browser command line with a -remote option.

To reuse a Mozilla profile instance:

  1. From the main menu of JDeveloper choose  Tools | Preferences | Web Browser and Proxy .
  2. In the  B rowser Command Line  enter:

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

  3. Click  OK .
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 jdevjava1013.dmg:

  1. Mount the JDeveloper Disk Image by double-clicking the .dmg file.
  2. Drag the JDeveloper application to a location on your hard drive; for example, Applications.
  3. Start JDeveloper by double-clicking the JDeveloper application.
  4. If starting JDeveloper for the first time answer:
    • 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 .

Back to TOC

6. Configuring JDeveloper to Use Hosted Documentation

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

To configure JDeveloper to use documentation hosted on OTN:

  1. From the JDeveloper main menu, choose  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>\jdeveloper.exe . You can also run  <jdev_install>\jdev\bin\jdev.exe if you want to see a console window for displaying internal diagnostic information.
  • To start JDeveloper on other platforms, run the file  <jdev_install> /jdev/bin/jdev .
Back to TOC

8. Migrating User Settings from Previous Releases

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

JDeveloper Java Developer Preview provides support for Java, XML and JavaBeans technologies. Workspaces and projects containing technologies not supported by the developer preview will be migrated, but design and runtime features will not be available for the unsupported technologies. The migration process backs up the original workspace and project files to  .bak files.

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

To migrate your user settings:

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

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

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/extensions  directory.
  4. Restart JDeveloper. After you restart JDeveloper, you will be able to use the extension.

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

Back to TOC

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

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

10.2 Configuring User Home Directories in a Multiuser Environment

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

To define the name of the user home environment variable:

  1. Open the file  <jdev_install>\jdev\bin\jdev.conf  in a text editor. Use an editor that recognizes UNIX end-of-line characters, such as WordPad.
  2. Find the entry:
    SetUserHomeVariable JDEV_USER_DIR
    This is the default variable that JDeveloper will look for at startup. As the terminal server administrator, you may change the name of this variable to follow your system's naming conventions.
  3. Save the file. If you are using WordPad, it will warn you that it is about to save the file in text-only format. You can ignore this warning.

To set the environment variable:

Note:  Each user of JDeveloper on a multiuser system must follow these procedures.
  1. From the Windows Start menu, choose  Control Panel | System .
  2. Select the  Advanced  tab, then click  Environment Variables .
  3. In the  User Variables  section, click  New .
  4. Add  JDEV_USER_DIR , or the name you chose for the  SetUserHomeVariable , as a user variable.
  5. Set the value of this variable to your home directory (e.g.,  N:\users\jdoe ), and click  OK .
  6. To check your variable setting, open a command shell and enter:

    set

    You should see output similar to the following:

    JDEV_USER_DIR=N:\users\jdoe

  7. Launch JDeveloper.
  8. JDeveloper will ask if you would like your user home directory to be created. Select  Yes .
  9. Choose  H elp |  A bout | Properties  to verify that the value of  ide.user.dir  is set to your user home directory.

10.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_04.
  2. Log on to your terminal server.
  3. Verify that the user home environment variable has been defined: Ask your system administrator for the naming convention that is used on your system. The default variable is  JDEV_USER_DIR .
  4. Set the user home environment variable: from the Windows Start menu, choose  Control Panel | System .
    1. Select the   Advanced  tab, then click  Environment Variables .
    2. In the  User Variables  section, click  New .
    3. Add the variable to User Variables and click  OK.
      For example, you can define  JDEV_USER_DIR  as the variable containing the path to the user's home directory.
    4. To check the correct variable settings, open a command shell and enter:

      set

      You should see output similar to the following:

      JDEV_USER_DIR=n:\users\jdoe

  5. Launch JDeveloper.
  6. JDeveloper will ask if you would like your user home directory to be created. Select  Yes .
  7. Choose  H elp |  A bout | Properties  to verify that the value of  ide.user.dir  is set to your user home directory.

If you run JDeveloper in a multiuser environment and you see the error

The system DLL ole32.dll was relocated in memory. The application will not run properly. The relocation occurred because the DLL Dynamically Allocated Memory occupied an address range reserved for Windows NT system DLL's. The vendor supplying the DLL should be contacted for a new DLL.

you'll need to update the  <jdev_install>\jdev\bin\jdev.conf  file by uncommenting the line:

AddVMOption -Xheapbase100000000

Use an editor that recognizes UNIX end-of-line characters, such as WordPad. You may have to change the number upward or downward if you still get the error when starting JDeveloper. When you save the file, WordPad will warn you that it is about to save the file in text-only format. You can ignore this warning.

In addition, you will need to set the same option with the same value in   P roject | D e fault Project Settings�| Runner�| J ava  options.
To make this setting available to all users, the administrator should perform this change, exit JDeveloper and then copy the file:

 

<userhome>\system\DefaultWorkspace\Project1.jpr


to:

 

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


Back to TOC

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

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

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

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

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