3.1.1 Changing System Cursors on Linux and UNIX Systems

On UNIX or Linux platforms, the Java cursors might display as 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 to replace the cursors.

To replace the cursors:

Create a backup copy of the default cursors located in the JDK directory at:

jdk_install/jre/lib/images/cursors

Extract the replacement cursors from the .tar file by following these steps:

Navigate to the following location on your system:

JDEV_HOME/jdeveloper/jdev/bin/clear_cursors.tar

Run the following command to extract the replacement cursors from the tar file:

tar -xvf clear_cursors.tar

3.1.2 Setting the System Resource Limit on Linux and UNIX Systems

The minimum recommended system resource limit for Oracle JDeveloper on Linux systems is 4096.

To determine the resource limit configuration for your system, enter the following command:

/bin/sh -c 'ulimit -n'

If the value returned is less than 4096, set the system resource limit by following these steps:

Open the limits.conf file, which is located at /etc/security/.

Find the following parameters:

soft nofile value_of_the_parameter
hard nofile value_of_the_parameter

Change the value of these parameters to 4096:

soft nofile 4096
hard nofile 4096

Note:

If the parameters listed in Step 2 do not exist, add the parameters with their values, as listed in Step 3, to the limits.conf file.

3.1.3 Starting Oracle JDeveloper on Linux and UNIX Systems

To start Oracle JDeveloper on Linux and UNIX, do the following:

Navigate to the following location on your system:

JDEV_HOME/jdeveloper/jdev/bin/

Run the following command:

./jdev

3.1.4 Specifying the JDK Location on Linux and UNIX Systems

Note:

This section is not applicable to the Studio edition of Oracle JDeveloper.

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. When prompted, enter the path to the Java executable file, for example /usr/local/java/bin/java.

3.1.5 Changing the JDK Location in Linux and UNIX Systems

To change a JDK location that you have previously specified, set the variable SetJavaHome in the file JDEV_HOME/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

3.2 Using Oracle JDeveloper on Windows

This section discusses how you begin working with Oracle JDeveloper on Windows.

3.2.2 Specifying the JDK location on Windows

Note:

This section is not applicable to the Studio edition of Oracle JDeveloper.

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 the Java executable file, for example D:\jdk1.7.0_10\bin

3.2.3 Changing the JDK location on Windows

To change a JDK location on Windows, set the variable SetJavaHome in the file JDEV_HOME\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.7.0_10 on your D: drive, your entry in jdev.conf shows as follows:

SetJavaHome d:\jdk1.7.0_10

3.2.4 User Directories Structure

The following list describes the default directory structure within Oracle JDeveloper, on Windows:

The default location for the system subdirectory is %APPDATA%\JDeveloper\system12.1.2.0.XX.XX.XX, where XX.XX.XX is the unique number of the product build.

3.3.1 Starting Oracle JDeveloper on Mac OS X Platforms

3.3.2 Specifying JDK Location on Mac OS X Platforms

Note:

This section is not applicable to the Studio edition of Oracle JDeveloper.

When you start 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 the Java executable, for example /usr/local/java/bin/java.

3.3.3 Changing the JDK Location on Mac OS X Platforms

To change a JDK location, set the variable SetJavaHome in the file JDEV_HOME/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

3.4 Migrating From a Previous Version to Oracle JDeveloper 12.1.2

Oracle JDeveloper version 12.1.2.0 supports migration from Oracle JDeveloper 11.1.1.1.0 or higher only. Oracle recommends migrating to Oracle JDeveloper 11.1.1.1.0 from all other earlier versions before migrating to this release of Oracle JDeveloper. This section provides more information about migrating from a previous version to Oracle JDeveloper 12.1.2.0.

3.4.1 Migrating User Settings

When you start Oracle JDeveloper for the first time (and each time you add a new extension or upgrade to a newer version), JDeveloper displays the Confirm Import Preferences dialog to cofirm whether to import your preferences and settings from a previous installation.

When the Confirm Import Preferences dialog is displayed, click Show All Installations to view a list of all the previous installations. From this list, choose the installation that you want to import preferences and settings from. When you hover the mouse over an item in list, the path to the installation is displayed as a tooltip. Alternatively, you can click Find a previous installation manually (with the image of a magnifying glass) on the top right of the installation list to browse for an installation manually. Clicking Yes on the Confirm Import Preferences dialog imports user preferences and the state of the IDE from the previous installation.

To force Oracle JDeveloper to display the Confirm Import Preferences dialog, use the -migrate flag when starting Oracle JDeveloper from the command line, for example, jdev -migrate.

Note:

If you migrate to another version of Oracle JDeveloper, you will need to reinstall the extensions that you want to use.

3.4.2 Migrating Projects

When you open an application or project that was created in a previous release, Oracle JDeveloper prompts you to migrate the project to Oracle JDeveloper 12c. Depending on the content of the projects, Oracle JDeveloper might display additional prompts to migrate some specific source files as well. Oracle recommends that you create 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 12c.

3.4.2.1 Migrating JSF and JSTL Projects

This version of JDeveloper requires that all projects with JavaServer Faces and JSTL be migrated to the latest versions of the technologies (version 2.0 and 1.2 respectively). Additionally, any web.xml deployment descriptors will be migrated to version 2.5.

To manually install an Oracle JDeveloper Extension, follow these steps:

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

From the Help menu, select Check for Updates.

In Step 1 of the wizard, select Install from a Local File and navigate to the ZIP file on your system.

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

3.6 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, for Oracle JDeveloper to identify user home directories correctly.

The user home directory contains the user's preferences for 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, follow these steps:

Open the file JDEV_HOME/jdeveloper/jdev/bin/jdev.boot in a text editor. Use an editor that recognizes UNIX end-of-line characters, such as WordPad.

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

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.

3.8 Using Oracle JDeveloper in a Multiuser Environment

This section contains information about how 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 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 JDeveloper and your users.

3.8.2 Configuring User Home Directories in a Multiuser Environment

Before you run Oracle JDeveloper in a terminal server environment, you might want to define the user home environment variable and set its value for each user, for Oracle JDeveloper to identify user home directories correctly. If the variable is not defined and set, Oracle JDeveloper uses the JDEV_HOME\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 3.6, "Setting the User Home Directory" for instructions on how to configure user home directory environment variables.

Oracle JDeveloper prompts you to confirm is the user home directory needs to be created. Click Yes.

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, you might encounter the following 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.

If you see this error, update the JDEV_HOME\jdeveloper\jdev\bin\jdev.conf file by uncommenting the following parameter:

AddVMOption -Xheapbase100000000

Use an editor that recognizes UNIX end-of-line characters, such as WordPad. You might have to change the number upward or downward if you still get the error when starting Oracle JDeveloper. When you save the file, WordPad warns 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, follow these steps:

From the Application menu, select Default Project Properties.

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

Click the Launch Settings node.

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

3.9 Using Oracle WebLogic Server with Oracle JDeveloper

Note:

This section is not applicable to the Java edition of Oracle JDeveloper.

Installing Oracle JDeveloper Studio 12c (12.1.2) also automatically installs Oracle WebLogic Server (12.1.2). Oracle JDeveloper uses this preconfigured installation as the Integrated Oracle WebLogic Server and JDeveloper managed server for testing and debugging your applications from within the IDE. After installing Oracle JDeveloper, all the applications that you need to begin developing, testing and debugging are installed and configured.

For additional information about using a standalone Oracle WebLogic Server instance with JDeveloper, see the Deploying Applications chapter in the Oracle Fusion Middleware User's Guide for Oracle JDeveloper.

3.9.1 Using the Integrated Oracle WebLogic Server

Oracle JDeveloper is bundled with an integrated application server called Integrated WebLogic Server, and a default instance called IntegratedWebLogicServer is defined for it.

All applications are bound, by default, to IntegratedWebLogicServer. Oracle JDeveloper manages the Integrated WebLogic Server lifecycle for testing your application. The first time Integrated WebLogic Server is needed, Oracle JDeveloper creates the DefaultDomain and prompts you to provide the administrative username and password. The location of configuration files for the default domain is the DefaultDomain directory located in the Oracle JDeveloper system directory.

Note:

The Oracle WebLogic Server 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 Oracle WebLogic Server, the server must be configured to run ADF applications.

For more information about Java Access Bridge, refer to the Java Access Bridge documentation available on the web site.

Extract the contents of the zip file to a folder, accessbridge_home.

Install Java Access Bridge by running the install.exe file from the accessbridge_home\installer folder.

The installer first checks the JDK version for compatibility. Then, the Available Java virtual machines dialog displays.

Click Search Disks. Then customize your search for only the drive that contain the Oracle JDeveloper build and the JDK version in the program files directory (if it exists).

The search process can take a long time if the disk that has 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 configured optimally, and will not be correctly installed to all of the Java virtual machines on your system. After selecting the disk to search, click Search.

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.

Click OK when you see the Installation Completed message.

Confirm that the following files have been installed in the Winnt\System32 directory (or the equivalent Windows XP or Vista directory), or copy them from accessbridge_home\installerfiles, as they must be in the system path to work with Oracle JDeveloper:

JavaAccessBridge.dll
JAWTAccessBridge.dll
WindowsAccessBridge.dll

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

Confirm that the following files have been installed in the JDEV_HOME\jdk\jre\lib\ext directory, or copy them from accessbridge_home\installerfiles:

access-bridge.jar
jaccess-1_4.jar

Confirm that the file accessibility.properties has been installed in the jdev_home\jdk\jre\lib directory, or copy it from \installerfiles.

Start your screen reader.

Start Oracle JDeveloper by running the file jdev.exe located in the folder JDEV_HOME\jdeveloper\jdev\bin.

A console window that contains error information (if any) is displayed first . The Oracle JDeveloper window appears when Oracle JDeveloper starts up. Any error or warning messages that appear do not affect the functionality of Oracle JDeveloper.