Terminal User Guide

We set Java home and Java path variables, let’s check is it really work. Double-click on Start menu – Run – cmd. We can check Java home variable by typing echo% JAVAHOME%. And we can verify the version of Java as well java-version. If everything is OK your output should be more or less the same as mine. Open terminal on mac, change path to the root cd vi.bashprofile (This opens the bashprofile file) Click I to insert text and use the following text to set JAVAHOME and PATH. You definitely need to install to a path which is accessible from all users. /opt/YOURCONDADISTRIBNAME is a good candidate. However you also have to add conda path which automatically happens when you add the following shell script to other users'.bashrc files. You can find the shell script in the root user's.bashrc file. For the record, I bring it here. Update your path. You can update your PATH variable for the current session at the command line, as shown in Get the Flutter SDK. You’ll probably want to update this variable permanently, so you can run flutter commands in any terminal session. The steps for modifying this variable permanently for all terminal sessions are machine-specific.

The shell uses environment variables to store information, such as the name of the current user, the name of the host computer, and the default paths to any commands. Environment variables are inherited by all commands executed in the shell’s context, and some commands depend on environment variables.

You can create environment variables and use them to control the behavior of a command without modifying the command itself. For example, you can use an environment variable to have a command print debug information to the console.

To set the value of an environment variable, use the appropriate shell command to associate a variable name with a value. For example, to set the variable PATH to the value /bin:/sbin:/user/bin:/user/sbin:/system/Library/, you would enter the following command in a Terminal window:

A leading-edge research firm focused on digital transformation. Good Subscriber Account active since President Donald Trump announced early Friday that he and Melania Trump had tested positive for.

To view all environment variables, enter:

When you launch an app from a shell, the app inherits much of the shell’s environment, including exported environment variables. This form of inheritance can be a useful way to configure the app dynamically. For example, your app can check for the presence (or value) of an environment variable and change its behavior accordingly.

Different shells support different semantics for exporting environment variables. For information, see your preferred shell’s man page.

Add Directory To Path Mac

Although child processes of a shell inherit the environment of that shell, shells are separate execution contexts that don’t share environment information with each other. Variables you set in one Terminal window aren’t set in other Terminal windows.

After you close a Terminal window, variables you set in that window are no longer available. If you want the value of a variable to persist across sessions and in all Terminal windows, you must set it in a shell startup script. For information about modifying your zsh shell startup script to keep variables and other settings across multiple sessions, see the “Invocation” section of the zsh man page.

This chapter describes the steps that you need to follow after installing Oracle JDeveloper Studio.

This chapter contains the following sections:

3.1 Using Oracle JDeveloper on Linux and UNIX Systems

This section describes tasks that you might want to perform after installing Oracle JDeveloper.

It contains the following sections:

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:

1. Create 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 by following these steps:

   1. Navigate to the following location on your system:

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

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:

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

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

2. Find the following parameters:

3. Change the value of these parameters to 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:

1. Navigate to the following location on your system:

2. Run the following command:

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.

It contains the following topics:

3.2.1 Starting Oracle JDeveloper on Windows

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

• Method 1

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

• Method 2

  Start Oracle JDeveloper from the command line by running one of the following commands:

  • JDEV_HOMEjdeveloperjdeveloper.exe

  • JDEV_HOMEjdeveloperjdevbinjdevw.exe

  • JDEV_HOMEjdeveloperjdevbinjdev.exe (to display a console window for internal diagnostic information)

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_10bin

3.2.3 Changing the JDK location on Windows

To change a JDK location on Windows, set the variable SetJavaHome in the file JDEV_HOMEjdeveloperjdevbinjdev.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%JDevelopersystem12.1.2.0.XX.XX.XX, where XX.XX.XX is the unique number of the product build.

• The default location of the user-generated content is:

  • C:UsersuserDocumentsJDevelopermywork on Windows 7 systems.

  • C:JDevelopermywork on all other Windows platforms.

For more information about user directories and how to set the value for the home environment variable, see Section 3.6, 'Setting the User Home Directory'.

3.3 Using Oracle JDeveloper on Mac OS X Platforms

This section discusses how you can begin using Oracle JDeveloper on Mac OS X platforms.

It contains the following topics:

3.3.1 Starting Oracle JDeveloper on Mac OS X Platforms

To start JDeveloper on Mac OS X platforms, follow these tasks:

1. Navigate to the following directory on your system:

2. Run the following command:

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.

It contains the following topics:

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.

For the most current information on migration, see the Oracle JDeveloper documentation page on OTN: http://www.oracle.com/technetwork/developer-tools/jdev/documentation/index.html.

3.5 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 an Oracle JDeveloper extension:

• From the Help menu, select Check for Updates.

  On the Source page of the Check for Updates wizard, you can specify the update center to download the extension from, or specify a local file to install the extension from.

  You can search the following update centers:

  • Oracle Fusion Middleware Products

  • Official Oracle Extensions and Updates

  • Open Source and Partners Extensions

  • Internal Automatic Updates

To manually download an Oracle JDeveloper extension, follow these steps:

1. Go to the following link: http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/131167.xml.

2. Select an Oracle JDeveloper Extension.

3. Follow the instructions to download the zip file.

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

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

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

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

4. 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 JDevelopermywork 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:

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

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

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

Examples:

• jdev.exe -J-Dide.user.dir=D:usersjdoe (on Windows).

• jdev.exe -J-Dide.user.dir=/home/users/jdoe (on Linux and UNIX).

3.7 Setting the Home Environment Variable

This section contains information about setting up the HOME environment variable on Linux and Windows platforms.

It contains the following topics:

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

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

3. Display the environment variable to confirm the change:

   You should see an output similar to the following:

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.

3.7.2 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. Do the following:

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. Click Advanced, 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:usersjdoe), and click OK.

6. To check your variable setting, open a command shell and enter the following command:

   set

   You should see output similar to the following:

   JDEV_USER_DIR=N:usersjdoe

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.

3.7.3 Setting the Home Environment Variable on MacOS X System

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.

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.

This section contains the following sections:

3.8.1 Installing Oracle JDeveloper on a Citrix MetaFrame Server or a Microsoft Terminal Server

You need to have administrative privileges to install Oracle JDeveloper on a Citrix Metaframe Server or a Microsoft Terminal Server.

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 3.8.2, 'Configuring User Home Directories in a Multiuser Environment' and in Section 3.8.3, 'Configuring Terminal Server Clients for Running Oracle JDeveloper'.

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_HOMEJDevelopersystem directory for each user for storing system settings, and C:JDevelopermywork 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.

3.8.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 JDeveloper has been installed and configured by the system administrator.

To configure a terminal server client for running Oracle JDeveloper, do the following:

1. Verify that the color resolution of the terminal server client has been set to a minimum of 256 colors. This minimum resolution is a prerequisite for installing Java JDK 7.0.

2. Log in to your terminal server.

3. Verify that the user home environment variable has been defined. Confirm 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 3.7.2, 'Setting the Home Environment Variable on Windows'.

5. Launch Oracle JDeveloper.

6. Oracle JDeveloper prompts you to confirm is the user home directory needs 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, 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_HOMEjdeveloperjdevbinjdev.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:

1. From the Application 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.

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, see 'Preparing the Standalone Application Server for Deployment' in Administering Oracle ADF Applications.

3.10 Understanding Oracle JDeveloper Accessibility Information

This section contains the following topics:

3.10.1 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 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, follow these steps:

Note:

• These steps apply to machines that have the Windows operating system.

• You must use a screen reader that is compatable with Windows.

1. Install the screen reader if it is not already installed.

   For more information about installation, refer to the documentation for your screen reader.

2. Install Oracle JDeveloper.

   For information about performing a silent installation, see Section A.1, 'Installing Oracle JDeveloper Studio in Silent Mode'.

3. Download Java Access Bridge for Windows version 2.0.1. The latest version of the file is available at the following location: http://www.oracle.com/technetwork/java/javase/tech/index-jsp-136191.html.

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

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

5. Install Java Access Bridge by running the install.exe file from the accessbridge_homeinstaller folder.

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

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

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 WinntSystem32 directory (or the equivalent Windows XP or Vista directory), or copy them from accessbridge_homeinstallerfiles, as they must be in the system path to work with Oracle JDeveloper:

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

10. Confirm that the following files have been installed in the JDEV_HOMEjdkjrelibext directory, or copy them from accessbridge_homeinstallerfiles:

11. Confirm that the file accessibility.properties has been installed in the jdev_homejdkjrelib directory, or copy it from installerfiles.

12. Start your screen reader.

13. Start Oracle JDeveloper by running the file jdev.exe located in the folder JDEV_HOMEjdeveloperjdevbin.

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.

3.10.2 Finding Accessibility Information

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. Also, see the Oracle JDeveloper Accessibility Information chapter in the Oracle Fusion Middleware User's Guide for Oracle JDeveloper.

3.11 Oracle on the Web

Oracle provides a number of resources on the Web. Some sites you might find helpful are listed in Table 3-1, 'Oracle on the Web':

Mac Os Path

Table 3-1 Oracle on the Web