Jdev Install.html

[Nga Sagastume]

NoteThe remainder of this document uses to represent the directory location in which JDeveloper was installed. For example, if JDeveloper was unzipped in c:\jdev9i, the would be c:\jdev9i.

Set the variable SetJavaHome in the file \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.

If you are using JDeveloper on a Windows platform, and you want to use CodeCoach or Profiler, you will need to install ojvm, the specialized Oracle Java Virtual Machine for JDeveloper. The ojvm will also make the JDeveloper debugger run more quickly. See Installing ojvm on Windows to Run CodeCoach and Profiler, and to Improve Debugger Performance in this installation guide.

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.

The complete installation of JDeveloper is configured to use JDK 1.3.1_02 for Windows platforms. If you install JDeveloper on another platform, perform the following steps to configure JDeveloper to use the appropriate JDK. Also, you must specify the VM that you are using in jdev.conf.

You can use either a local JDK or a JDK on a mounted drive. Also, see the previous section, Installing JDeveloper from jdev9032_base.zip for information on specifying the use of other Java Virtual Machines.

To use CodeCoach and Profiler, you need to install ojvm, the specialized Oracle Java Virtual Machine for JDeveloper.The ojvm will also make the JDeveloper debugger run faster. If you performed the complete installation using jdev9032.zip, ojvm was installed automatically. If you performed the base installation using jdev9032_base.zip, you will need to manually install ojvm into your JDK. 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.

To install the documentation set, download jdev9032_doc.zip from /products/jdev. You can install the documentation into JDeveloper, without any configuration, by extracting the files into . The \jdev\doc\ohj directory will be created as well as the \jdev\tutorials directory.

If you installed jdev9032_base.zip, JDeveloper is pre-configured to use documentation hosted on OTN. Please note that the first launch of the hosted help system may take several minutes to initialize if you are on a low-bandwith or high-latency connection.

You can set up your own web server for hosting documentation. This is especially useful if you want to add information to the JDeveloper documentation. For information on extending the JDeveloper documentation, refer to the Oracle Help for Java (OHJ) documentation, which is included with JDeveloper.

Uncompress each JAR file located in \jdev\doc\ohj into its own directory on your Web server. If you installed jdev9032_base.zip, you will need to download the documentation ( jdev9032_doc.zip) from /products/jdev.

Modify the file jdeveloper.hs to point to the correct URL for each of the .hs files on your server. Look at the file jdeveloper-hosted-example.xml in the \jdev\doc\ohj\jdeveloper.jar for an example of how to edit this file.

Note: You can also select Help Check for Updates...> from the JDeveloper main menu. This menu option lists extensions that you don't have, lists newer versions of ones you have, and installs them for you.

Your user settings from the production release of JDeveloper 9.0.2 can be migrated to this release of JDeveloper. Oracle does not support direct migration from 3.2.3 to 9.0.3. For information about migration issues, see the topic Ways to Migrate to Oracle9i JDeveloper 9.0.3 in the Getting Started with JDeveloper book in the Online Help.

Note: It is not necessary to use this flag if you are running a newly installed version of JDeveloper for the first time. On subsequent runs of JDeveloper, use this flag to open the Migrate User Settings dialog.

/jdev/system where is the root directory of the installation of JDeveloper you are migrating from. For UNIX users, any previous releases that are discovered will already be included in the dropdown list of the dialog.

when starting JDeveloper on a UNIX computer, your JDK isn't set up to use the font that is generating the error. 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.

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

You can install JDeveloper in Microsoft Terminal Server, Citrix MetaFrame and MetaFrame XP (for Windows), and MetaFrame 1.1 for Unix environments, 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.

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

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

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.

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 not have to make any modifications to your configuration.

If you performed the base installation of JDeveloper, OC4J will not run, and you will not be able to deploy or run your applications until you install the full JDK into . You must also modify jdev.conf to point to this JDK home and specify a VM if you are not using ojvm. See Installing JDeveloper from jdev9032_base.zip for more information.

You can start and stop the OC4J server in stand-alone mode using the provided start_oc4j and stop_oc4j batch files and shell scripts located in \jdev\bin\ , or run the following commands from the \j2ee\home\ directory.

Please refer to the following information to set up a screen reader and Java Access Bridge. These steps 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.

Download Java Access Bridge 1.0.2. The file you will download is accessbridge-1_0_2.zip. It is available from www.oracle.com/java/technologies/javase/javase-tech-access-bridge.html. Refer to the Java Access Bridge documentation available from this web site for more information about installation and the Java Access Bridge.

Confirm that two jar files: access-bridge.jar and jaccess-1_3.jar were added to the folder \jdk\jre\lib\ext during the install. If necessary, copy them from \installer\installerFiles to \jdk\jre\lib\ext .

For deploying to OC4J and Oracle9iAS, see the Oracle9i JDeveloper Version 9.0.3 Release Notes. For specific information about deploying to other J2EE servers such as Apache Tomcat, WebLogic, and JBoss, please refer to the Help topic "Ways to Deploy J2EE Applications" in the "Packaging and Deploying" book, which you can access by selecting Help Help Topics> from the JDeveloper main menu.

To install a version of JDeveloper pre-configured for SOA Suite or Business Process Management Suite applications, see "Introducing the Quick Start Distributions" in Installing SOA Suite and Business Process Management Suite Quick Start for Developers.

You should have obtained the appropriate installer for your operating system as described in Section 1.6. Depending on what distribution and installer you are using, you should take note of the following JDK prerequisites.

To streamline your installation process, the JDK you wish to use with the product should be the one you use to start the installer program. In that case, be sure the desired JDK is the first one in your system PATH, or reference it explicitly on the command line.

Be sure the user account you use for installing Oracle JDeveloper has the required privileges. For more information, see "Selecting an Installation User" in Planning an Installation of Oracle Fusion Middleware.

Ensure that a certified JDK exists on the system on which you are about to install Oracle JDeveloper. If you checked the prerequisites for generic installers as described in Section 2.1, you should have already obtained and installed a certified JDK on your system.

3a8082e126