This document associates JDeveloper versions with the application
servers they support for deployment. For specific deployment instructions, please
see the JDeveloper online documentation and the chapter Deploying ADF Applications
in the ADF
Developer's Guide.
Application Servers Supported by JDeveloper
10g (10.1.3.x)
This matrix shows application servers supported by JDeveloper
10g (10.1.3), for deploying J2EE and ADF applications. The matrix also shows
any additional restrictions that apply or extra tasks that are required.
Note: Please check the Deployment
Issues section of the JDeveloper 10.1.3.1
or 10.1.3.0
release notes for other issues related to deploying applications to Oracle Application
Server and other application servers.
A. If your JDeveloper and Oracle Application
Server do not have matching version numbers (for example if one is 10.1.3.0
and the other is 10.1.3.1), the following notes apply:
For ADF applications developed in JDeveloper 10.1.3.1 and deployed to Oracle
Application Server 10.1.3.0, you need to install the ADF runtime libraries
in your application server, using the ADF Installer. You can run the installer
from within JDeveloper (select Tools | ADF Runtime installer) or use the standalone
version.
Oracle Application Server 10.1.3.1 is not supported with JDeveloper 10.1.3.0.
B. For all applications, you need to reconfigure
your applications to use J2SE 1.4.2 and J2EE 1.3. See the JDeveloper documentation
for complete instructions.
C. For ADF applications only, you need to
install the ADF runtime libraries, using the ADF Installer. You can run the
installer from within JDeveloper (select Tools | ADF Runtime installer) or use
the standalone
version.
D. JDeveloper 10.1.3.1 is certified only
with Oracle Application Server 10g (10.1.3.1). If you are using JDeveloper 10.1.3.0,
then you must use Oracle Application Server 10g (10.1.3.0). Note the specific
point release numbers.
E. Some ADF features are not supported with
WebLogic 9:
The ADF BC deployment profile wizard does not support creating WebLogic
9 connections; a workaround is to create a WebLogic 8 connection and use that
to connect to your WebLogic 9 instance.
ADF applications with JSP/Struts or model 1 JSP clients do not render correctly
in WebLogic 9.
F. For ADF applications, see the section Deploying to WebSphere
in the JDeveloper documentation.
G. For all applications, you need to reconfigure
your applications to use J2SE 1.4. See the JDeveloper documentation for complete
instructions.
Application Servers Supported by JDeveloper 10g (10.1.2)
and Earlier Versions
This matrix shows application servers supported by JDeveloper
10.1.2 and earlier. To use this matrix:
Find the cell corresponding to version of
JDeveloper you are working with and the application server version you
want to deploy your application to.
The contents of the cell tell you whether this combination is supported, and what, if anything, you need to do to make it work.
1. This configuration is supported for UIX applications only.
For complete instructions on how to deploy UIX applications from JDeveloper
10.1.2 to Oracle Application Server 10g (10.1.3), please see the document Deploying
a 10.1.2 UIX Application to a 10.1.3.x OC4J Instance.
2. For ADF applications only, you need
to install the ADF runtime libraries, using the ADF Runtime Installer. To start
the Installer, select Tools | ADF Runtime Installer from the main menu in JDeveloper.
Instructions for running the installer are in the JDeveloper online documentation,
or click Help in the Installer.
3. For BC4J or ADF applications that use
interMedia Domain objects, the application must run with JDBC 10.1.0 driver
(thin). It can be configured just on the OC4J instance where your ADF application
is deployed. Note that the 10.1.0 JDBC driver must be used specifically with
Oracle Application Server 10g (9.0.4.1), and not version 9.0.4. Further details
can be found at the MetaLink document Oracle
Application Server - Oracle JDBC Drivers Support (you will be required to
create an account to log into MetaLink).
4. JDeveloper 9.0.4 is certified only with
Oracle Application Server 10g (9.0.4). If you are using JDeveloper 9.0.4.1,
then you must use Oracle Application Server 10g (9.0.4.1). Note the specific
point release numbers.
5. If you are deploying a BC4J application
from JDeveloper 9.0.4 Windows version to Oracle Application Server 10g (9.0.4)
Solaris or Linux version, you should install the BC4J runtime libraries, using
the BC4J
Installer. This step is recommended only for this combination of versions,
because JDeveloper 9.0.4 for Windows contains a later build of the BC4J runtime
than Oracle Application Server 9.0.4 for Solaris or Linux.
6. For UIX, you need to follow these steps
to make a standalone web application that does not rely on the version of UIX
installed on the application server:
Ensure that your UIX application has local copies of the
UIX installables for the version of UIX that you developed against. UIX XML
applications created with JDeveloper already have local installables. Some
UIX JSP applications do not. If your application does not already have local
UIX installables, unzip the uix2-install.zip file (found in the redist directory
in JDeveloper) into your public_html directory.
Select the UIX Runtime library for local deployment in
your project's deployment profile. This will ensure that the version of UIX
runtime you developed against is automatically included in the WEB-INF/lib
of your application.
Create an orion-web.xml file in your JDeveloper project
(in the Deployment Descriptors category in the File->New dialog). Add the
following line:
This will instruct OC4J to use the version of the UIX runtime library in WEB-INF/lib
of your application instead of the version of UIX installed globally on the
application server.
7. For BC4J applications
only, you need to install the BC4J runtime libraries, using the BC4J
Installer.
8. Not supported for ADF applications.
9. Not supported for BC4J applications; however
this howto
document describes the steps for deploying BC4J applications to WebLogic
7.
10. The ADF runtime installer does not support
installing the ADF runtime to WebSphere; you need to copy the runtime libraries
by hand. ADF applications are not supported in release 10.1.2.0.1.
Bookmark
