Deploying the ADF Application - Oracle ADF 11gR2 Development Beginner's Guide - page 232

ADF application deployment
The ADF web applicaion iles are packaged into archives and deployed to the server for
user access and interacion. Normally, in a development environment, JDeveloper 11 g R2
comes with an integrated WebLogic server to test the applicaion. The ADF applicaion can
be deployed to different servers such as WebLogic and WebSphere which are provided
with the ADF runime libraries, and the shared libraries related to the web applicaion are
available for the server. Using JDeveloper, the user can deploy the current applicaion and
test it with the use of the integrated WebLogic server.
Overview
Deploying an applicaion is as important as developing the applicaion. The WebLogic
server 10.3.5.0 is integrated with JDeveloper 11.2.2.0. There is an opion for us to deploy
the applicaion to a diferent applicaion server provided that the server contains all runime
libraries to support the ADF applicaion. The ADF runime libraries, which are called Java
Resource Files ( JRF ), are provided by default for the WebLogic server, WebSphere, and
GlassFish. The ADF applicaion is deployed to the server as a packaged enterprise archive
which contains the required web content and related resource files. All the deployment
library properies are conigured from the Deployment opion in the Project properies and
Applicaion properies opions. The diferent archives that are helpful at diferent stages of
the ADF web applicaion deployments are as follows:
Java Archive (JAR) : Java archive is a Java specific archive that is used to package all
the Java class iles related to the project. For example, we can bundle all the uility
class files as a Java archive file and then use it in any other project. JAR files are used
as libraries in the Model and Viewcontroller projects. The file structure includes
a class file and a META-INF folder that contains the MANIFEST.MF file.
ADF library (JAR) : The ADF library is an archive that is specific to the ADF framework.
The ADF library is different from a Java archive file because the ADF library will
pull all related libraries referenced by the files and add it to the manifest file. The
dependent libraries are pulled by JDeveloper and added as a secondary import. The
ADF library will expose the ADF task flows and other ADF-specific metadata files that
are not exposed by a normal Java archive file. ADF libraries may contain task flows
but are also used for declaraive components and page templates. Using the ADF
library, we can drag-and-drop the task flow onto the page as a region. The structure
includes the META-INF folder containing the manifest file along with the jar-
connection.xml and jar-adf-config.xml files specific to the ADF library.
The ADF library can contain coniguraion iles for the ADF applicaion.