Installs an extension zip on a JDeveloper instance.
Environment/Instance Properties
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| JDeveloper Install Home |
| Yes | The JDeveloper installation directory. You can control Build instance associated with your project, which effectively controls which version of JDeveloper is used for build operations. |
| Use OJWebUpdate64 | FDJDEV_EXT_USE_64 | Yes | Whether or not to use the 64-bit version of the OJWebUpdate executable. Default is true. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
| Zip File Path |
| Yes | The path to the extension zip to install. Relative paths are assumed to be in FD_ARTIFACTS_DIR or FD_TEMP_DIR. |
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation consumes a zip file containing extension info for the JDeveloper instance.
Endpoint Selection
This operation will select all available endpoints associated to the environment instance.
You must create an instance for JDeveloper and associate the endpoints where you have JDeveloper installed. You can create more than one instance if you are supporting multiple JDeveloper versions in your environment. For example, JDeveloper 11.1.1.8, JDeveloper 12.1.3 etc. Projects can select a specific JDeveloper instance on the Project Configuration Screen as per what version of JDeveloper each project is using for development.
Endpoint Execution
This operation will randomly execute on one of the endpoints identified during selection.
Special Considerations
The JDeveloper 11g download page does not have specific installer for 64bit Linux or Windows. It is advisable to use Generic Installer if you are setting up a 64-bit Windows or Linux environment.
For JDeveloper 12c, you can use 64-bit Windows installer or choose to use Generic Installer.
In a nutshell, if the download is not very clear, Generic Installer is your best choice.
When using Generic Installer, make sure to use proper JDK (32-bit or 64-bit depending on operating system and specific Java version either JDK 1.6 or JDK 1.7). You will launch generic installer using
{path to java}-jar{installer jar file}. The version of Java used to launch the installer will be used when you launch JDeveloper or run Plugin operations.JDK to use for specific version of JDeveloper
JDeveloper 11g – JDK 1.6.x
JDeveloper 12c – JDK 1.7.x / 1.8.x
It is very critical to select the proper JDK version, as generated applications will most likely be deployed to WebLogic, and WebLogic also runs with specific version of JDK. You do not have to be very specific with patch numbers, just make sure the major and minor version of JDK matches with the target runtime environment.
Install JDeveloper in version specific folder, as you will most likely have more than one version to support. For example,
/oracle/middleware/product/jdev11117, /oracle/middleware/product/jdev121300,etc.If you are building WebCenter applications, you must install various JDeveloper extensions necessary to compile WebCenter applications.
You must do the same for other extensions including any custom extensions that you may have on Developer workstations. For example, the JUnit extension.
As JDeveloper on remote host is being used to perform builds, developers must make sure to not reference JAR files using absolute path. If there is need to use third-party or open-source JAR files, you can reference them by creating a Project-scoped JDeveloper library.