Oracle provides documentation for performing this deployment but it assumes you’re deploying the application to an EAR file constructed using Oracle JDeveloper.  Since that never happens in the real world (because we all use things like build management systems which swap property files in and out and automatically setup datasources), here are some things that might be good to know, especially if you’re doing this as part of an upgrade from a previous version (like


You’ll need to install the ADF runtime to the WLS 10.3.2 instance you’re deploying to.  There are literally dozens of documents and blogs describing those so I won’t go into detail here.

EAR Structure

Generally, when we talk about ADF we’re discussing a web application module and maybe a couple of EJBs.  For a web application, you’ll want to make sure the following lines are contained in your weblogic.xml file:


Also, be sure to include the following in your weblogic-application.xml file:


These two stanzas will allow your application access to the shared libraries you installed as part of the prerequisite step.  In doing so, you shouldn’t need to package any of the ADF JAR files directly in your EAR.  If you do so, WebLogic will complain and your log file will start to look very busy.

Startup Classpath

You’ll also need to make sure your managed server’s startup classpath looks something like this:


Where $WLS is your WebLogic installation.  The big one here is jrf.jar.  This is a JAR file with zero classes in it.  Basically it just contains a JAR manifest (MANIFEST.MF) that has Class-Path entries for all the ADF dependencies.

Apache Commons Logging

Unfortunately, jrf.jar introduces a dependency on commons logging 1.0.4 which contains the memory leak problem and lacks the diagnostic tools contained in JCL 1.1.1.  The end result is that this will cause problems if you try to package commons logging with your enterprise application.


WebLogic 10.3.2 Documentation

Commons Logging Documentation

Oracle ADF Documentation

As an aside, I’ve found the best thing to do is open Oracle JDeveloper and use the help with the IDE to link out to other documentation.  Often times it can be impossible to Google for Oracle  software documentation because any results don’t contain enough information about which version they refer to.  Using the embedded help to click out seems to be the best way to get accurate information.