You can launch Oracle JDeveloper on Linux, UNIX, Mac OS X, Windows, and multiuser environments.
Before launching Oracle JDeveloper, you can specify settings for Linux, UNIX, and Mac OS X environments.
4096.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 as follows:
You can permanently redefine the location of your user home directory in a Linux, UNIX, or Mac OS X environment.
When you define the user home directory, it will contain a system subdirectory that stores the user's preferences for JDeveloper, also known as the domain home. The user home directory will also contain a separate subdirectory for user-generated content and other configuration files that are specific to a given user, also known as the application home.
If you do not define a user home directory, these subdirectories will be located in different areas on your computer.
The default location for the system subdirectory is $HOME/.jdeveloper/system12.2.1.2.XX.XX.XX, where XX.XX.XX is the unique number of the product build.
The default location for user-generated content is $HOME/jdeveloper/mywork.
There are two ways to set your user home directory if you do not want your JDeveloper files to be stored at $HOME. Both methods set the user home directory for all instances of JDeveloper on your system.
Use either of the following methods to set the user home directory:
Setting environment variable JDEV_USER_DIR, which will require you to restart your terminal session
Editing product.conf
With 12c (12.2.1.1), many JDeveloper settings, including the location of your JDK, are stored in product.conf. This file is created by JDeveloper on first startup unless the file already exists from a previous installation. JDeveloper will use the settings stored in product.conf even if they are from a previous installation.
Note:
In earlier versions of JDeveloper, product.conf was named jdev.conf.
Find the product.conf file. It should be located at $HOME/.jdeveloper/12.2.1.2.0.
Open product.conf in an editor. Add a line to set AddVMOption -Dide.user.dir to your preferred directory path.
For example, if your preferred directory is $HOME/mydocs/jdevfiles, your definition should look like this:
AddVMOption -Dide.user.dir=$HOME/mydocs/jdevfiles
Caution:
Do not use a directory that contains spaces as the home directory. For example, do not specify $HOME/my projects as the home directory.
Save your changes. The changes should take effect immediately when you start JDeveloper. The changes made to product.conf will also override any environment variable you have defined.
When you launch Oracle JDeveloper for the first time, you can verify that the user home directory has been set to your preferred directory by accessing the Help menu, selecting About from the drop-down menu, toggling the Properties tab, and finding the definition for ide.user.dir.
Setting environment variable JDEV_USER_DIR
You can set the environment variable JDEV_USER_DIR to your preferred home directory path. The examples and syntax provided below are for the bash shell on Linux systems.
When you launch Oracle JDeveloper for the first time, you can verify that the user home directory has been set to your preferred directory by accessing the Help menu, selecting About from the drop-down menu, toggling the Properties tab, and finding the definition for ide.user.dir.
You can permanently change the location of your JDK if it has changed since the first time you launched JDeveloper.
To change a JDK location:
This will set the JDK path for all installations of JDeveloper on your system.
If you deinstall JDeveloper but do not delete the product.conf file, all settings stored in this file, including the JDK path, will be preserved for future installations. If you re-install JDeveloper with the same numerical version as your previous installation, your new installation will automatically read that JDK location again.
On 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 as follows:
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
Before launching Oracle JDeveloper, you can specify settings for a Windows environment.
You can permanently redefine the location of your user home directory in a Windows environment.
When you define a user home directory, it will contain a system subdirectory that stores the user's preferences for JDeveloper, also known as the domain home. The user home directory will also contain a separate subdirectory for user-generated content and other configuration files that are specific to a given user, also known as the application home.
If you do not define a user home directory, these subdirectories will be located in different areas on your computer
The default location for the system subdirectory is:
%USERPROFILE%\AppData\Roaming\JDeveloper\system12.2.1.2.XX.XX.XX on Windows 7 systems.
%USERPROFILE%\Application Data\JDeveloper\system12.2.1.2.XX.XX.XX on all other Windows platforms. .
where XX.XX.XX is the unique number of the product build
The default location of the user-generated content is:
C:\JDeveloper\mywork on Windows 7 systems.
C:\Documents and Settings\My Documents\JDeveloper\mywork on all other Windows platforms.
There are two ways to set your user home directory if you do not want your JDeveloper files to be stored at the default location. Both methods set the user home directory for all instances of JDeveloper on your system.
Use either of the following methods to set the user home directory:
Editing product.conf
With 12c (12.2.1.1), many JDeveloper settings, including the location of your JDK, are stored in product.conf. This file is created by JDeveloper on first startup unless the file already exists from a previous installation. JDeveloper will use the settings stored in product.conf even if they are from a previous installation.
Note:
In earlier versions of JDeveloper, product.conf was named jdev.conf.
Find the product.conf file. It should be located at %USERPROFILE%\AppData\Roaming\JDeveloper\system12.2.1.2.XX.XX.XX.
Open product.conf in an editor. Add a line to set AddVMOption -Dide.user.dir to your preferred directory path.
For example, if your preferred directory is N:\users\jdoe, your definition should look like this:
AddVMOption -Dide.user.dir=N:\users\jdoe
Caution:
Do not use a directory that contains spaces as the home directory. For example, do not specify C:\My Projects as the home directory.
Save your changes. The changes should take effect immediately when you start JDeveloper. The changes made to product.conf will also override any environment variable you have defined.
When you launch Oracle JDeveloper for the first time, you can verify that the user home directory has been set to your preferred directory by accessing the Help menu, selecting About from the drop-down menu, toggling the Properties tab, and finding the definition for ide.user.dir.
Setting the environment variable JDEV_USER_DIR
You can set the environment variable JDEV_USER_DIRto your preferred home directory path on a Windows system, including individual users of Oracle JDeveloper on a multiuser system.
When you launch Oracle JDeveloper for the first time, you can verify that the user home directory has been set to your preferred directory by accessing the Help menu, selecting About from the drop-down menu, toggling the Properties tab, and finding the definition for ide.user.dir.
You can permanently change the location of your JDK if it has changed since the first time you launched JDeveloper.
To change a JDK location:
This will set the JDK path for all installations of JDeveloper on your system.
If you deinstall JDeveloper but do not delete the product.conf file, all settings stored in this file, including the JDK path, will be preserved. If you re-install JDeveloper with the same numerical version as your previous installation, your new installation will automatically read that JDK location again.
When installing and configuring Oracle JDeveloper for a multiuser environment (such as Microsoft Terminal Server, Citrix MetaFrame and MetaFrame XP (for Windows), and MetaFrame 1.1 for UNIX), you will 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.
These environments allow many clients to access one installation of Oracle JDeveloper. In all cases, users can save their projects locally.
With administrative privileges, you can install Oracle JDeveloper on a Citrix Metaframe Server or a Microsoft Terminal Server.
Run the Oracle JDeveloper installer on your Citrix MetaFrame or Microsoft Terminal Server as detailed in Installing Oracle JDeveloper. Do not launch Oracle JDeveloper at the end of installation, as you must first configure the user home directories and terminal server clients as described in the following sections.
After installing a Citrix MetaFrame or Microsoft Terminal Server client locally, and JDeveloper installed and configured, you can configure a terminal server client for running Oracle JDeveloper.
To configure a terminal server client for running Oracle JDeveloper:
You may encounter this error when you run Oracle JDeveloper in a multiuser environment.
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 product.conf file in $HOME/.jdeveloper/12.2.1.2.0 file by uncommenting the following parameter:
AddVMOption -Xheapbase100000000
In addition, each user must modify the default project to apply this setting. To specify this value in the default project settings:
-Xheapbase100000000 in the Java Options field.To start Oracle JDeveloper, follow the steps for the operating system you are using, or launch it from the command line.
On Windows operating systems:
From the Start Menu, select All Programs, then select Oracle Fusion Middleware 12.2.1.1, then select JDeveloper Studio 12.2.1.1.
On the command line, enter one of the following commands:
JDEV_HOME\jdeveloper\jdeveloper.exe
JDEV_HOME\jdeveloper\jdev\bin\jdevw.exe
JDEV_HOME\jdeveloper\jdev\bin\jdev.exe (to display a console window for internal diagnostic information)
Oracle JDeveloper 12c (12.2.1.1) supports migration from Oracle JDeveloper 11.1.1.9.0 or 11.1.2.3.0.
Oracle recommends migrating to Oracle JDeveloper 11.1.1.9.0 or 11.1.2.3.0 from all other earlier versions before migrating to this release of Oracle JDeveloper.
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 confirm 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 upon subsequent startups, use the -migrate flag when starting Oracle JDeveloper from the command line, for example, jdev -migrate.
Note:
If you migrate to 12c (12.2.1.1) from another version of Oracle JDeveloper, you will need to reinstall the extensions that you want to use. Some extensions for older versions may no longer exist.
For more information on installing extensions, see Enabling Oracle JDeveloper Extensions.
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 them. Accepting the initial prompts to migrate your projects means that JDeveloper will update the format for crucial XML files, but migration does not rewrite or update specific project code. After migration, you should re-test your applications to completely verify that they work.
See the Oracle JDeveloper page on OTN for more information about migrating specific types of projects to 12c.
This release of Oracle 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.
For the most current information on migration, see the Oracle JDeveloper documentation page on OTN: http://www.oracle.com/technetwork/developer-tools/jdev/documentation/1212-cert-1964670.html#Abrams-SupportInformation-MigrationSupport.
You can also migrate files silently from the command line using the headless migration tool. This tool can be found at jdeveloper/jdev/bin/ojmigrate.
The command to use ojmigrate uses the following structure:
ojmigrate [option]... file...|@file
Specifying a value for the option parameter is optional. The file or the @file parameter value is required.
Using the option Parameter
You can use the following flags for the option parameter:
-ade to connect to the current ADE view-dry to initiate a dry run and skip calling migrators-failFast to stop the migration after the first failure-generateDefaults to let migrator helpers generate a migration.prperties file, alongside the .jws file, that contains the defaults for migration options.You can view these valid values and their use cases by invoking the help file for ojmigrate in the command line.
Using the file Parameter
If you want to migrate one application, specify the path to the .jws file you want to migrate as the value for file.
For example, if you are trying to migrate example.jws with no option flag, your command would be structured like the following:
ojmigrate example.jws
If you want to migrate more than one application, you should use the @file parameter described in the next section.
Using the @file Parameter
If you want to migrate more than one application at a time, you can create a file containing all the paths to applications you want to migrate and use the @file parameter to point to this file.
You can autogenerate this file by using a script like the following:
find . -name "*.jws" -printf "%P\n" > workspaces.txt
Once this file is generated, you should check it to make sure all the applications you want migrated are included. You can also create the file manually.
Once you have created and saved this file, specify the path to this file as the value for @file in the example command structure. The @ symbol must be appended to your filename when specifying this parameter.
For example, if you have listed the location of multiple .jws files in example.txt, your command would be structured like the following:
ojmigrate @example.txt
If you encounter errors during migration, you can try to troubleshoot them with the strategies listed in this section. To isolate the cause of your errors, run ojmigrate with the -failFast flag. This will cause ojmigrate to stop after its first unsuccessful migration and analyze the issue.
Migrating Applications With -ade
If you see errors about being unable to check out read-only files, you should migrate these applications in ADE.
Make sure you are in ADE view and have a transaction started. Because the ADE extension is not part of the JDeveloper non-debug builds, you should use either a JDeveloper debug build or you should manually install the ADE extension.
Once you are in ADE view, invoke ojmigrate with the -ade flag.
The commands for this section should resemble the following:
ade useview VIEW_NAME ade begintrans TXN_NAME ojmigrate -ade @workspaces.txt
Using a Two-Pass Migration
Migration could have failed because some migrators require extra data normally provided in the migration wizard, or the defaults that the migrators are using are not suitable for your application. In these cases, you should do a two-pass migration.
For the first pass, run the ojmigrate command with the -generateDefaults flag. Your command may look like this:
ojmigrate -genarateDefaults @workspaces.txt
This command generates a properties file containing a list of defaults formatted as name/value pairs with comments. The key/value pair is per application and per NodeMigratorHelper, meaning that there is one set of key pairs for every application, and the key is prefixed with the class name of the corresponding NodeMigratorHelper.
The properties file is generated beside the .jws application you are trying to migrate. Its title will be formatted as workspacename.migration.properties.
If the file is generated, open it, change the appropriate values, and save your changes. If you ran the command and do not see a file like this, no migrators generated defaults.
On the second pass, run the command without the -generateDefaults flag.
ojmigrate @workspaces.txt
If you still encounter errors, then some migrators may not be headless friendly. A developer should prepare your migrator for headless migration before attempting the two-pass migration again.
Preparing a NodeMigratorHelper for Headless Migration
If you need data from the user before performing a migration, you should do the following:
Oracle JDeveloper extensions (such as JUnit) are available through JDeveloper or by downloading from OTN.
To locate and install extensions using Oracle JDeveloper:
Launch JDeveloper.
Click Help, then select Check for Updates to launch an Update wizard.
On the first screen of the Update wizard, Oracle Fusion Middleware Products and Official Oracle Extensions and Updates are selected by default. Select the other two boxes if you want more options.
Note:
Starting in 12c (12.1.3), you can no longer download SOA extensions. You need to use a Quick Start distribution to obtain a version of JDeveloper pre-configured for either SOA Suite or Business Process Management Suite. See Introducing the Quick Start Distributions in Oracle Fusion Middleware Installing SOA Suite and Business Process Management Suite Quick Start for Developers for more information.
Click Next when you have identified and selected your sources.
On the Updatesscreen, select the extensions that you want to install and click Next.
On the License Agreements screen, you need to agree to the license terms for the extensions you selected on the previous screen. Click Next to begin the download.
When the extensions have finished downloading, the wizard displays a summary of the installations or upgrades that you installed. Click Finish to exit the wizard.
In the dialog box that appears, respond to the prompt to restart JDeveloper to finish installing updates.
Alternatively, you can manually download and install an Oracle JDeveloper extension from OTN as follows:
http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/131167.xml.You can use a screen reader with Oracle JDeveloper, and become familiar with assistive technologies in Oracle products and Oracle JDeveloper.
To make the best use of accessibility features, Oracle Corporation recommends the following minimum configuration:
Windows XP, Windows Vista
Java J2SE 1.7.0_15
Java Access Bridge 2.0.1
JAWS 12.0.522
Microsoft Internet Explorer 7.0 or higher
Mozilla Firefox 3.5 or higher
To set up a screen reader and Java Access Bridge:
Note:
These steps apply to machines that have the Windows operating system.
You must use a screen reader that is compatible with Windows.
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.
For the latest configuration information or for information about addressing accessibility and assistive technology issues, see the Oracle Accessibility FAQ at http://www.oracle.com/us/corporate/accessibility/faqs/index.htm. See also Oracle JDeveloper Accessibility Information in Oracle Fusion Middleware Developing Applications with Oracle JDeveloper
Installing Oracle JDeveloper Studio 12c (12.2.1.1) also automatically installs Oracle WebLogic Server 12c (12.2.1.1).
Note:
The information in this section is not applicable to the Java edition of Oracle JDeveloper.
Oracle JDeveloper uses the preconfigured Oracle WebLogic Server 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 Deploying Applications in Oracle Fusion Middleware Developing Applications with Oracle JDeveloper.
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, see Preparing the Standalone Application Server for Deployment in Oracle Fusion Middleware Administering Oracle ADF Applications.
The IntegratedWebLogicServer's DefaultDomain uses Java DB. If the IntegratedWebLogicServer fails to create the DefaultDomain, you should search for any preexisting instances of Java DB or Derby Client running in the background and stop them.
Useful Oracle resources related to Oracle JDeveloper are available on the Web.
The following table lists some sites you may find helpful.
Table 3-1 Oracle Resources on the Web
| Description | URL |
|---|---|
|
Oracle JDeveloper Home Pages |
|
|
Oracle JDeveloper Discussion Forum |
|
|
Corporate Site |
|
|
Oracle Technology Network |
|
|
Oracle Accessibility Site |