Installing Oracle9i JDeveloper

Updated May 14, 2002

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

• JDeveloper System Requirements
• Installing JDeveloper
• Configuring the JDK in JDeveloper on Non-Windows Platforms
• Starting JDeveloper
• Adding CodeCoach and the Profiler, and Improving Debugger Performance, in a Base Installation
• Adding Local Documentation to a Base Installation
• Enabling WebDAV Support in JDeveloper
• Migrating to JDeveloper from Earlier Releases
• Hosted Documentation
• Font Problems on Unix Computers
• Required Component Versions for E-Business Integration
• Multiuser Support
• Using OC4J with JDeveloper
• Configuring OC4J 2.1 to work with BC4J
• Using a Screen Reader and Java Access Bridge with JDeveloper
• Supported Deployment Environments
• Uninstalling JDeveloper
• JDeveloper Documentation

JDeveloper System Requirements

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

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

Windows

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

Linux

Resource	Recommended
Distribution	SuSE LINUX SLES7 (Kernel 2.4.7, GlibC 2.2.2-55) or Redhat LINUX 7.1 (Kernel 2.4.2-2, GlibC 2.2.2-10) using the GNOME window manager
CPU Type and Speed	Pentium III 500 MHz
Memory	256 MB RAM
Display	65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space	Base Install: 110MB Complete Install: 400MB
JDK	Sun JDK 1.3.1 for Linux

Solaris

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

HP-UX

Resource	Recommended
Operating System	HPUX 11.0 using the CDE or VUE window managers
CPU Type and Speed	HP PA-RISC 200 MHz
Memory	256 MB RAM
Display	65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space	Base Install: 110MB Complete Install: 400MB
JDK	HP JDK 1.3.1.02, available at http://www.hp.com

Installing JDeveloper

Installing JDeveloper from jdev9i_902.zip

• Unzip jdev9i_902.zip in the directory you want to install JDeveloper.

Installing JDeveloper from jdev9i_902_base.zip

1. If you don't have Java™ 2, version 1.3.1_02 installed, install it.
2. Unzip jdev9i_902_base.zip in the directory you want to install JDeveloper.
3. Set the variable SetJavaHome in the file <jdeveloper_root>\jdev\bin\jdev.conf to the location of your Java installation. Use an editor that recognizes UNIX end-of-line characters, such as WordPad. When you save the file, WordPad will warn you that it is about to save the file in text-only format. You can ignore this warning.
   
   For example, in a Windows environment, if the location of your jdk 1.3.1 is in a directory called jdk1.3 on your D drive, your entry in jdev.conf would like:

   SetJavaHome d:\jdk1.3

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

4. If you are using JDeveloper on a Windows platform, and you want to use CodeCoach or the Profiler, you will need to install ojvm, JDeveloper's specialized Java Virtual Machine. ojvm will also make JDeveloper's debugger run more quickly. See Adding CodeCoach and the Profiler, and Improving Debugger Performance, in a Base Installation.
5. If you are using JDeveloper on a Windows platform but do not want to install ojvm, edit <jdeveloper_root>/jdev/bin/jdev.conf and find the line:
   
   #SetJavaVM ojvm
   
   Right below this line, add the line
   
   SetJavaVM hotspot
   
   Use an editor that recognizes UNIX end-of-line characters, such as WordPad. When you save the file, WordPad will warn you that it is about to save the file in text-only format. You can ignore this warning.
   
   Note: If you do not install ojvm, you will not be able to use CodeCoach or the Profiler, and the debugger will not run as quickly.
6. If you want to use Local Documentation with JDeveloper, see Adding Local Documentation to a Base Installation

Configuring the JDK in JDeveloper on Non-Windows Platforms

The complete installation of JDeveloper is configured to use JDK 1.3.1 for Windows platforms. If you install JDeveloper on another
platform, perform the following steps to configure JDeveloper to use the appropriate JDK.

1. If you don't have Java™ 2, version 1.3.1 installed, install it.
2. Set the variable SetJavaHome <developer_root>\jdev\bin\jdev.conf to the location of your Java installation.
   

   For example, in a UNIX environment, if the location of your JDK 1.3.1 is in a directory called /local/java/jdk, your entry in jdev.conf would look like:
   
   SetJavaHome /local/java/jdk
   
   You can use either a local JDK or a JDK on a mounted drive.

Starting JDeveloper

• To start JDeveloper on Windows, run the file <jdeveloper_root>/jdev/bin/jdevw.exe
• To start JDeveloper on other platforms, run the file <jdeveloper_root>/jdev/bin/jdev

Adding CodeCoach and the Profiler, and Improving Debugger Performance, in a Base Installation

To use CodeCoach and the Profiler, you need to install ojvm, JDeveloper's specialized Java Virtual Machine. ojvm will also make JDeveloper's debugger run more quickly. If you performed the complete installation, this was done for you automatically. If you performed the base installation, you will need to manually install ojvm into the JDK you installed during step 1 of Installing JDeveloper from jdev9i_902_base.zip. The batch file InstallOJVM.bat (provided with JDeveloper) will copy ojvm files into the specified JDK and update the configuration of that JDK. The files are copied into a separate ojvm directory and will not overwrite any of the existing files in the JDK.

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

  InstallOJVM.bat c:\jdk


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

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

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

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

Adding Local Documentation to a Base Installation

To install the documentation set, download jdev9i_902_doc.zip from /products/jdev . You can install it into JDeveloper directly without any configuration by extracting the files into <jdeveloper_root>.

If you install the documentation into any other location locally, you will need to configure it.

1. In the Tools menu and choose Preferences.
2. In the preferences tree navigate to Documentation.
3. Select the Use Local Documentation radio button.
4. Set the full path to the jdeveloper.hs file.

Enabling WebDAV Support in JDeveloper

Before you can use WebDAV support in Oracle9i JDeveloper, you first need to download the WebDAV addin for JDeveloper from OTN. The WebDAV addin download includes IBM's DAV4J driver.

To download the WebDAV Addin for JDeveloper:

1. Go to /software/products/jdev/index.html.
2. Click the WebDAV Addin for JDeveloper link in the section on Oracle9i JDeveloper Downloads .
3. Follow the remaining instructions and click jdev9iWebDAV.zip.

1. Shutdown any instances of Oracle9i JDeveloper that are currently running on your machine.
2. Unzip the downloaded jdev9iWebDAV.zip file to a temporary directory.
3. Locate the directory in which JDeveloper is installed.
4. Copy dav4j.jar, dav4j_license.htm, jdwebdav.jar and xml4j.jar into the <jdeveloper root>\lib\ext directory.

When you next start JDeveloper, you will be able to create and use WebDAV connections.

For information about using WebDAV support in JDeveloper, see Oracle9i JDeveloper Online Help.

Migrating Your Project from Earlier Releases

For information about migration issues, see Ways to Migrate Projects to Oracle9i JDeveloper in the Welcome to Oracle9i JDeveloper book in the on-line help system.

Hosted Documentation

If you have installed the base install, or have set the IDE option to use hosted documentation, JDeveloper is pre-configured to use documentation hosted on OTN. The URL to the documentation set on OTN is :80/hosted_doc/jdev/jdeveloper/jdeveloper.hs

Please note that the first launch of the hosted help system may take several minutes to initialize.

In addition to this site, you can set up your own host for serving hosted documentation. You may want to do this if you are behind a firewall, or you find network access times slow, or if you want to add information to the JDeveloper documentation. If you want to extend the JDeveloper documentation, refer to the Oracle Help for Java (OHJ) documentation, which is included with JDeveloper.

Hosting JDeveloper Documentation

1. Uncompress the jar files located in the <jdeveloper_root>/doc/ohj onto your web server. If you have the base install, you will have to download the documentation from OTN. Each jar should be uncompressed into it's own directory.
2. Modify the file jdeveloper.hs file to point to the correct URL for each of the subhelpsets on your server. Look at the file jdeveloper-hosted-example.xml in the <jdeveloper_root>/jdev/doc/ohj/jdeveloper.jar for an example of how to configure this file.

Once you have done that, your users will have to set their copy of JDeveloper to use your new server. In the IDE Settings dialog, navigate to "Documentation". Ensure that "Use Hosted Documentation" radio button is selected. Provide the URL to the jdeveloper.hs file on your server. This URL should include the port number, even if you are using the default port (80).

Font Problems on UNIX Computers

If you see an error similar to

Font specified in font.properties not found [--symbol-medium-r-normal--*-%d-*-*-p-*-adobe-fontspecific]

when starting  JDeveloper on a UNIX computer, your JDK isn't set up to use the the mentioned font. JDeveloper, by default, uses the information in the file font.properties included with each JDK. If this file references fonts not available on your computer, you will see the above error (or one like it). To fix this error, you'll either need to install a new font, or change your font.properties file. For information on installing new fonts on your computer, contact your vendor.

Required Component Versions for E-Business Integration

The versions of components required for e-business integration are:

• Oracle server version 8.1.6, 8.1.7 or 9.0.1 (8.1.7 or 9.0.1 are recommended)
• Oracle Workflow server 2.6.0 or 2.6.1 if the hub is an 8.1.6 or 8.1.7 database
• Oracle Workflow server 2.6.2 if the hub is a 9.0.1 database
• Oracle Workflow client 2.6.0 or above

Deploying Activity Modeler Generated Artifacts Requires 8.1 Database With 8.1 Queues

The queue definitions that the eBusiness 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's init.ora file is set to a value lower than 8.1, the generated queues cannot be deployed to that database.

Using JDeveloper in a Multiuser Environment

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

You can install JDeveloper in Microsoft Terminal Server or Citrix WinFrame environment, allowing many clients to access one installation of JDeveloper. In all cases, users can save their projects locally.

When installing and configuring JDeveloper for a multiuser environment, you'll need to account for the resource planning, such as number of users and power of the server, to deliver optimal performance for JDeveloper and your users.

Modifying Permission on a non-Windows Multiuser System

Users (or groups) must have write and execute permissions for the following directories (recursively)

• <jdeveloper_root>/j2ee
• <jdeveloper_root>/BC4J/redist
• <jdeveloper_root>/SOAP/webapps

For example, you could use the command

chmod -R g+wx <grp name> j2ee


In addition, users (or groups) must have execute permissions for the following:

• <jdeveloper_root>/jdev/bin/jdev
• <jdeveloper_root>/jdev/bin/jdev.conf
• <jdeveloper_root>/jdev/bin/ojc
• <jdeveloper_root>/BC4J/bin/create_jclient.ear.sh
• <jdeveloper_root>/BC4J/bin/dac2jclient.sh
• <jdeveloper_root>/BC4J/bin/StartCORBA

Installing JDeveloper on a Citrix WinFrame Server or a Microsoft Terminal Server

You need to have administrative privileges to install JDeveloper.

To Install JDeveloper on a Citrix or Microsoft Server

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

Configuring User Home Directories in a Multiuser Environment

Before you run JDeveloper in a terminal server environment, you must define the user home environment variable and set its value for each user in order for JDeveloper to identify user home directories correctly. If the variable is not defined and set, JDeveloper uses the <jdeveloper_root> 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 <jdeveloper_root>\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's administrator, you may change the name of this variable to follow your system's naming conventions.
3. Save the file. If you are using WordPad, it will warn you that it is about to save the file in text-only format. You can ignore this warning.

To set the environment variable:

1. From the Windows Start menu, select Control Panel | System.
2. Select the Environment tab.
3. Add JDEV_USER_DIR, or the name you chose in the previous procedure, as a User Variable.
4. Set the value of this variable to your home directory (e.g., N:\users\jdoe) and click OK.
5. To check your variable setting, open a command shell and enter
   
   set j
   
   You should see output similar to the following:
   
   JDEV_USER_DIR=N:\users\jdoe
6. Launch JDeveloper.
7. JDeveloper will ask if you would like your user home directory to be created. Select Yes.
8. Choose Help | About to verify that the value of ide.user.dir is set to your user home directory.

Configuring Terminal Server Clients for Running JDeveloper

These topics assume that you have already installed a Citrix WinFrame 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 Sun's JDK.
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:
   1. From the Windows Start menu, select Control Panel | System
   2. Click the Environment tab.
   3. Add the variable to your 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 <jdeveloper_root>\bin\jdev.conf file by adding the line

AddVMOption -Xheapbase10000000

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

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

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

<userhome>\system\DefaultWorkspace\Project1.jpr

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

Using OC4J with JDeveloper

Included with JDeveloper is a fully functioning version of Oracle9i Application Server Containers for J2EE (OC4J). If you are using JDeveloper to test your applications, you will be using the embedded version of OC4J and you will not have to make any modifications to your configuration. If you would like to use the same configuration for your server, you can use the version included with JDeveloper.

To configure the OC4J server for non-embedded mode

1. At the command line, in <jdeveloper_root>/j2ee/home run the command

    

   java -jar oc4j.jar -install

   The server will auto-unpack several jars. You will then be prompted to enter an admin password.

2. Enter an admin password and press enter.

   You will be prompted to confirm the password.

3. Confirm the password by typing it again and press enter.

Installation will be complete.

You can now start the server.

To start the OC4J server for use in non-embedded mode

• At the command line, in <jdeveloper_root>/j2ee/home run the command

   

  java -jar oc4j.jar

  Several jar files will be auto-deployed and you will the server will output

   

  Oracle9iAS (2.0.0.0) Containers for J2EE initialized

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

Note: The server must be running when you deploy projects to it.

Using the included server will have no impact on using JDeveloper for testing and running your projects.

Configuring OC4J 2.1 to work with BC4J

OC4J 2.1 is not, by default, configured to work with BC4J. A script to configure OC4J 2.1 to work with BC4J is available on the Oracle Technology Network (OTN) at /products/jdev/.

Using a Screen Reader and Java Access Bridge with JDeveloper

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

• Windows NT 4.0 (with Service Pack 6) or Windows 2000
• Sun Java Access Bridge 1.0.2
• JAWS 3.70.87
• Microsoft Internet Explorer 5.5
• JDK 1.3.1

Please refer to the following information to set up a screen reader and Java Access Bridge.

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

3. Download Java Access Bridge 1.0.2. The file you will download is accessbridge-1_0_2.zip.
4. After downloading the file, extract the contents to a folder; for example, accessbridge_home.
5. Install Java Access Bridge by running Install.exe from the <accessbridge_home>\installer folder.
6. Confirm that you want to install the Java Access Bridge into each of the Java virtual machines displayed in the dialog. Click OK when you see the Installation Completed message.
7. Confirm that two jar files: access-bridge.jar and jaccess-1_3.jar were added to the folder <oracle_home>\jdk\jre\lib\ext during the install. If necessary, copy them from <accessbridge_home>\installer\installerFiles to
8. <oracle_home>\jdk\jre\lib\ext.
9. Confirm that two DLL files: JavaAccessBridge.dll and WindowsAccessBridge.dll were added to the folder <oracle_home>\jdk\jre\lib\ext. If necessary, copy them from <accessbridge_home>\installer\installerFiles to <oracle_home>\jdk\jre\lib\ext.
10. Add the files listed above, JavaAccessBridge.dll and WindowsAccessBridge.dll, to the Winnt\System32 directory, as they must be in the system path in order to work with JDeveloper.
11. Confirm that the PATH environment variable has been updated to include the directory where the DLL files were installed, <oracle_home>\jdk\jre\lib\ext.
12. Confirm that the file <oracle_home>\jdk\jre\lib\accessibility.properties includes the following line:

    assistive_technologies=com.sun.java.accessibility.AccessBridge

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

13. Modify the file jdev.conf located in the folder <JDeveloper Install directory>\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

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

    SetJavaVM hotspot

15. Start your screen reader.
16. Start JDeveloper by running the file jdev.exe located in the folder <JDeveloper Install directory>\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 JDeveloper window will appear, once JDeveloper has started.

Supported Deployment Environments

Oracle9i JDeveloper can be used to deploy applications in a variety of environments. JDeveloper is based on the Sun JDK 1.3.1, and the applications or components that you create may be deployed on any J2EE certified platform running that JDK version.

Although JDeveloper and clients developed with JDeveloper may work in other environments, this version of JDeveloper has been specifically certified for the following environments:

The version of the Java VM included in both Netscape Navigator and Microsoft Internet Explorer is older than the Java VM 1.3.1 used in Oracle JDeveloper. Therefore, user's browsers may require a Java VM Plug-in to be installed.

Uninstalling JDeveloper

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

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

JDeveloper Documentation

Depending on your installation and configuration, JDeveloper documentation is either installed locally or on a web host. It can be accessed from the JDeveloper Help menu.

Oracle on the Web

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