Cxoracle-11g free download. SQLTools for Oracle SQLTools is a spin-off of the original SQLTools for Oracle. Like the original SQLTools SQLTools. Grouping and Descriptive Categories (14). This is an Oracle Jdeveloper 11g plugin for using findbugs. The Studio Edition for Windows is the most popular download of Oracle JDeveloper. It contains all the features of the product - including ADF, J2EE, UML, Database, Java, and XML. This download includes JDK 6 and is supported on Windows Vista, XP, 2003 and 2000.
Installation Guide
Version 10.1.2 October 2004
Before you install JDeveloper, please review the contents of this guide. Before using JDeveloper, you should read the JDeveloper 10g Release Notes.
Table of Contents
1. JDeveloper System Requirements
This release of JDeveloper is supported on Windows NT, Windows 2000, Windows XP, Linux, Solaris, Mac OS X, and HP-UX.
1.1 Recommended CPU, Memory, Display, and Hard Drive ConfigurationsWindows
Linux
Solaris
MAC OS X
HP-UX
1.2 Support for Team Based Development Tools
JDeveloper provides integrated support for the following source control systems:
ClearCase
Oracle SCM
Concurrent Version Support (CVS)
2. Installing JDeveloper Full Version
JDeveloper does not require an installer. To install JDeveloper, you will need an unzip tool. You can download a free, cross-platform unzip tool, Info-Zip, available at: http://www.info-zip.org/.
The full installation (
jdev1012.zip ) includes the Windows version of Sun J2SE 1.4.2_04 and the JDeveloper documentation.
To install JDeveloper from jdev1012.zip:
3. Installing JDeveloper Base
For quicker download times, you can download the base installation (
jdev1012_base.zip ):
To install JDeveloper from jdev1012_base.zip:
3.1 Installing OJVM with a Base Installation on Windows
To use CodeCoach and the Profilers with a base installation you need to install OJVM, the specialized Oracle Java Virtual Machine for JDeveloper. OJVM will also increase the speed of the JDeveloper debugger, and provide automatic deadlock detection and memory debugging features. If you performed the complete installation using
jdev1012.zip , OJVM was installed automatically. If you performed the base installation using jdev1012_base.zip , you will need to manually install OJVM into your SDK. The batch file InstallOJVM.bat (provided with JDeveloper) will copy OJVM files into the specified SDK and update the configuration of that SDK. The files are copied into a separate OJVM directory and will not overwrite any of the existing files in the SDK.
To install OJVM with a base installation:
3.2 Adding Local Documentation to a Base Installation
To install the documentation set, download
jdev1012_doc.zip from http://www.oracle.com/technology/products/jdev. You can install the documentation into JDeveloper, without any configuration, by extracting the files into <jdev_install> . The <jdev_install>jdevdocohj directory will be created as well as the <jdev_install>jdevtutorials directory.
If you install the documentation into any other local directory, you will need to configure the location in JDeveloper:
4. Installing JDeveloper on Non-Windows Platforms
This section provides additional instructions specific to installing JDeveloper on a non-Windows platform. Review these sections of the Installation Guide for general information:
OJVM, the specialized Oracle Java Virtual Machine enables CodeCoach and Profilers, increases the speed of the JDeveloper debugger, and provides automatic deadlock detection and memory debugging features. JDeveloper provides OJVM, and OJVM can be installed for use with JDeveloper, but this configuration is only supported for JDeveloper projects, not the JDeveloper IDE. For information about OJVM on Linux please refer to the JDeveloper Release Notes at:
<jdev_install>/jdev/readme.html .
4.1 Modifying Permissions on a Non-Windows System
All JDeveloper files must have read permissions which can be set by issuing:
chmod -R g+r <jdev_install>
Users (or groups) must have write and execute permissions for the following files:
In addition, users (or groups) must have write permissions for the following (required for deployment):
4.2 Configuring Java SDK in JDeveloper on Non-Windows Platforms
The complete installation of JDeveloper is configured to use Java Sun J2SE 1.4.2_04 for Windows platforms. If you install JDeveloper on another platform, perform the following steps to configure JDeveloper to use the appropriate SDK.
4.3 Font Problems in UNIX
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 in UNIX, your SDK isn't set up to use the font that is specified in the error. JDeveloper, by default, uses the information in the file
font.properties included with each SDK. 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. For information on updating the font.properties Adobe acrobat 9.5 download. file, see Sun's Font Overview documentation or your SDK vendor's documentation.
4.4 Cursor Problems on Non-Windows Platforms
On UNIX or Linux platforms, the Java cursors may display large and opaque, creating difficulties when used for drag and drop operations. To address this problem JDeveloper provides a set of cursors to replace the default set. You must have write access to the Java SDK in order to replace the cursors.
To replace the cursors:
4.5 Reusing Mozilla Profile Instance
When using Mozilla on a non-Windows system, you will need to close the browser each time before running your web application again. You can avoid this problem and reuse your Mozilla profile instance by setting the browser command line with a
-remote option.
To reuse a Mozilla profile instance:
5. Installing and Starting JDeveloper on Mac OS X Platforms
JDeveloper is provided as a self-contained application bundle. An installer is not required.
You must update your Mac OS X SDK to Java Sun version 1.4.2 Update 2 or later for use with JDeveloper. Use Mac OS X Software Update or download from http://developer.apple.com/java/download/.
To install JDeveloper from jdev1012.dmg:
6. Configuring JDeveloper to Use Hosted Documentation
If you installed
jdev1012_base.zip , JDeveloper is preconfigured 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.
If you installed
jdev1012.zip , JDeveloper is preconfigured to use local documentation. However, you can configure JDeveloper to use the documentation hosted on OTN.
To configure JDeveloper to use documentation hosted on OTN:
7. Starting JDeveloper
8. Migrating User Settings from Previous Releases
User settings such as system settings, libraries, connections, and projects 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 10.1.2. If you are running a newly installed version of JDeveloper for the first time you will be prompted with a Migrate User Settings dialog. You can use this dialog to migrate your user settings by selecting Yes. If you select No, any settings that you set on the first and subsequent runs will be overwritten if you later run JDeveloper with the
-migrate flag. For information about migration issues, see the ' Migrating to JDeveloper 10g ' topics in the online documentation, which you can access by choosing Help | Help Topics | Getting Started with JDeveloper from the JDeveloper main menu.
To migrate user settings from previous installations of JDeveloper:
9. Enabling JDeveloper Extensions
Before you can use an extension in JDeveloper, you first need to download the extension from OTN. An example of available JDeveloper Extensions is JUnit.
To automatically download and install a JDeveloper extension:
To manually download a JDeveloper Extension:
To manually install a JDeveloper extension:
For additional information, see the 'Extending JDeveloper' topics in the online documentation, which you can access by choosing Help | Help Topics from the JDeveloper main menu.
Back to TOC
10. Required Component Versions for E-Business Integration
The versions of components required for E-Business integration are:
10.1 Deploying Activity Modeler Generated Artifacts
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 Back to TOC
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.
11. Using JDeveloper in a Multiuser Environment
If you are using JDeveloper in a non-Windows environment, you will have to set permissions on directories and files. See Modifying Permission on a non-Windows System for more information.
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 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 resource planning, such as number of users and power of the server to deliver optimal performance for JDeveloper and your users.
11.1 Installing JDeveloper on a Citrix MetaFrame Server or a Microsoft Terminal Server
You need to have administrative privileges to install JDeveloper.
To Install JDeveloper on a Citrix MetaFrame or Microsoft Terminal Server:
11.2 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
<jdev_install>/jdev 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:
To set the environment variable:
11.3 Configuring Terminal Server Clients for Running JDeveloper
These topics assume 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 JDeveloper:
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
<jdev_install>jdevbinjdev.conf file by uncommenting the line:
AddVMOption -Xheapbase100000000
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 to all users, the administrator should perform this change, exit JDeveloper and then copy the file:
to:
Back to TOC
12. Using OC4J with JDeveloper
Included with JDeveloper is a fully functioning version of Oracle Application Server 10g Release 2 (10.1.2) Containers for J2EE (OC4J). The embedded server resides in the following location in the JDeveloper installation:
If you are using JDeveloper to test your J2EE applications before deploying to a target application server, you will not have to make any modifications to your configuration.
If you performed the base installation of JDeveloper and wish to deploy your application to OC4J in standalone mode, JDeveloper includes a copy of OC4J in
<jdev_install>/j2ee/home/config . To run OC4J in standalone mode you must set the JAVA_HOME variable to point to the full SDK. You must also modify jdev.conf to point to this SDK home. See Installing JDeveloper Base for more information.
If you deploy your applications to standalone OC4J, make sure that you use the remote
admin.jar file that was shipped with the remote OC4J. If you are using an admin.jar that doesn't match the version of OC4J to which you are deploying, deployment may fail. You can configure deployment to use the correct admin.jar for the OC4J standalone instance when you set up your connection using the JDeveloper Application Server Connection Wizard. To identify the standalone OC4J version that you are using, enter java -jar oc4j.jar -version from your OC4J installation directory.
You can start and stop the OC4J server in standalone mode using the provided
start_oc4j.bat and stop_oc4j.bat files and shell scripts located in <jdev_install>jdevbin. The start_oc4j batch file can be run either from Windows Explorer or the command line since no arguments are required; however the stop_oc4j batch file requires <admin> and <admin-password> on the command line. You can also run the following commands from the <jdev_install>j2eehome directory:
To configure the OC4J server for standalone mode:
To start the OC4J server for use in standalone mode:
To stop OC4J:
12.1 OC4J Memory Requirements
By default, OC4J preloads a large number of classes to improve performance. Because of this, you may get a
java.lang.OutOfMemoryError when you attempt to deploy to OC4J or run an application after deploying.
If you get a
java.lang.OutOfMemoryError , you have two options:
For more information on fine tuning your OC4J server instance, see the OC4J documentation.
13. Application Servers Supported by JDeveloper
A matrix associating JDeveloper versions with the application servers they support for deployment is available on Oracle Technology Network (OTN) at: http://www.oracle.com/technology/products/jdev/collateral/papers/10g/as_supportmatrix.html.
For additional information, see the 'Deploying JDeveloper' topics in the online documentation, which you can access by choosing Help | Help Topics from the JDeveloper main menu.
14. Database Certification for JDeveloper
This matrix associates Oracle and non-Oracle databases with the JDeveloper features they are certified against.
Supported means that Oracle will address customer issues, but the features are not necessarily tested. Certified means that the feature is supported on that database, and has passed testing by JDeveloper QA. The databases shown are all supported, even if not certified or working in this release.
Notes
15. Finding JDeveloper Accessibility Information
For the latest configuration information or for information on addressing accessibility and assistive technology issues, see the Oracle Accessibility FAQ at http://www.oracle.com/accessibility/faq.html. Also, see the help topics available by selecting the JDeveloper Accessibility Information node under Getting Started with Oracle JDeveloper in the online help table of contents.
16. Using a Screen Reader and Java Access Bridge with JDeveloper
To make the best use of our accessibility features, Oracle Corporation recommends the following minimum technology stack:
Please refer to the following information to set up a screen reader and Java Access Bridge. If you are using JAWS 3.70.87, please refer to the additional configuration information provided below the procedure.
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. Then the main JDeveloper window will appear once JDeveloper has started. Any message that appears will not affect the functionality of JDeveloper.
16.1 Configuring JAWS 5.0 and Access Bridge with JDeveloper
JDeveloper is designed to be accessible with screenreader software. JDeveloper 10.1.2 has been tested with JAWS 5.0 and JAWS 3.70. Although our testing of JDeveloper 10.1.2 and JAWS 5.0 was completed using Access Bridge 1.1_GA, Access Bridge version 1.2_GA works with JDeveloper 10.1.2 and JAWS 5.0. You do not need to use rtpatch.jar when using JAWS 5.0.
Access Bridge version requirements for each version of JAWS are listed below. Please see the JDeveloper 10g Release Notes regarding issues with the different configurations.
Access Bridge v. 1.2_GA Configuration for JDeveloper 10.1.2 with JAWS 5.0
Place the following files in the JDeveloper directory [
jdkjrelibext ]:
Place the following file in the JDeveloper directory [
jdkjrelib ]:
Place the following files in the Windows system32 directory
[winntsystem32 ]:
Access Bridge v. 1.1_GA Configuration for JDeveloper 10.1.2 with JAWS 5.0
Place the following files in the JDeveloper directory [
jdkjrelibext ]:
Place the following file in the JDeveloper directory [
jdkjrelib ]:
Place the following files in the Windows system32 directory
[winntsystem32 ]:
16.2 Configuring JAWS 3.70 and Access Bridge with JDeveloper
The use of JDeveloper 10.1.2, JAWS 3.70, and AccessBridge1.1_GA is not a recommended configuration. You may encounter JVM conflict exceptions when you attempt to launch JDeveloper 10.1.2. The latest version of Access Bridge, version 1.2_GA, does not require extensive configuration to work with JDeveloper 10.1.2 and JAWS 3.70.
To use earlier versions of Access Bridge with JDeveloper 10.1.2 and JAWS 3.70, the following combinations of Access Bridge file versions are necessary to achieve optimal functionality since this version of the screen reader uses older Java technology than is used in JDeveloper 10.1.2. There are two stacks of software technology listed below for those who want to use either version 1.0.3 or 1.0.4 of the Access Bridge. Note that the latest version of the Access Bridge Jar file is required in the system32 directory. AccessBridge v. 1.2_GA Configuration for JDeveloper 10.1.2
Place the following files in the JDeveloper directory [
jdkjrelibext ]:
Place the following file in the JDeveloper directory [
jdkjrelib ]:
Place the following files in the Windows system32 directory
[winntsystem32 ]:
Access Bridge v. 1.0.4 Configuration for JDeveloper 10.1.2
Place the following files in the JDeveloper directory [
jdkjrelibext ]:
Place the following file in the JDeveloper directory [
jdkjrelib ]:
Place the following files in the Windows system32 directory [
winntsystem32 ]:
Access Bridge v. 1.0.3 Configuration for JDeveloper 10.1.2
Place the following files in the JDeveloper directory [
jdkjrelibext ]:
Place the following file in the JDeveloper directory [
jdkjrelib ]:
Place the following files in the Windows system32 directory
[winntsystem32 ]:
Oracle Jdeveloper 11g Download For Mac Installer17. Uninstalling JDeveloper
Before you uninstall JDeveloper, you may want to backup your projects and files. By default, these files are in
<jdev_install>jdevmywork .
To uninstall JDeveloper, remove the entire JDeveloper installation directory. No other action is necessary.
Back to TOC
18. JDeveloper Documentation
Depending on your installation and configuration, JDeveloper online help is installed locally or on a Web host. You can access it from the JDeveloper Help menu.
19. Oracle on the WebOracle provides a number of resources on the Web. These are some sites you may find helpful:
Oracle Jdeveloper 11g Download For Mac 64-bit
The installation steps depend on the Oracle JDeveloper distribution and installer you are using.
Note:
The installation types described here do not support SOA extensions. To install a version of JDeveloper preconfigured for SOA Suite or Business Process Management Suite applications, see Introducing the Quick Start Distributions in Oracle Fusion Middleware Installing Oracle SOA Suite and Business Process Management Suite Quick Start for Developers.
You must obtain the appropriate installer for your operating system as described in Understanding and Obtaining the Oracle JDeveloper Distributions. Depending on the distribution and installer you are using, the type of installation you perform differs:
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |