Details about Configuration files as well as other xml files used in Oracle ADF 12C Application?

1. PageDef.xml :-

• For each page one page definition file is created.
• Page definition file consist of following sections :-

          parameters  :-  These are page level parameters that are stored locally to web page, and it is accessed by using an expression language.

          executables :-  This section contains the definition of Binding Container, access the iterators present data control, accessor iterator, method iterator etc.

It is also contains the entry of task flow binding.

          bindings  :-  It contains the entry of method action , attributes etc which refers to an entry in executable section.

2.   DataBindings.cpx :-

• This is a Data Binding Registry file. Jdeveloper creates this file, when first time an          accessable entry from data control binds to an UI Component.
• This file contains the following section:-

                Page Mappings :- It contains the path/location of a jsf, jspx or jsff page in a URL Pattern and usage id of corresponding page definition file.

                Page Definition Usages :-  It contains the entry of usage id of page definition file and the path/location of page defination file.

                Data Control Usages :-  It contains the entry of data control defined in DataControl.dcx, whose methods or iterators are used on pages. And also the entry of BC4J Data control i.e Application Module data control. 

3.  DataControl.dcx  :-

• This file is created when data control is created on Business layer such as web service data control, Placeholder data control etc.
• Appmodule data control entry is not defined in DataControl.dcx file because it is a part of  ADF Model layer transaction technology, which creates it own data control in order to access   at view layer.
• One Model project contains one dcx file.

In below screen shot you can see that for Appmodule data control their is no entry in dcx file, but  we have an entry of placeholder data control and adapter data control entry in dcx file.

4.  adfm.xml :-

• This file contains the path of other registry files which is used on model project.
• This file is automatically generated by jdeveloper while creating a model project.
• This file contains the path information of following files :-

             modelprojectname.jpx

             bc4j.xcfg

             DataControl.dcx

             DataBinding.cpx 

5.   AppModule.xml :-

• This file contains the configuration of view object/view link/app module instances to interact with client interface.

•  It also contains the configuration of java custom interface, web service interface to work with web services.

6.  adf-settings.xml  :-

• Jdeveloper create this file automatically while creating an ADF Fusion application in META-INF folder.
• adf-settings.xml file holds project-level and library-level settings such as ADF Faces help providers and ADF Controller phase listeners.
• The configuration settings for adf-settings.xml are fixed and cannot be changed during or after application deployment.
• There can be multiple adf-settings.xml files in an application. 

7.   adf-config.xml  :-

     It Specifies application-level settings that are usually determined at deployment (deployment profile) and often changed at run time by a managed bean that is registered for the component configuration to specify run-time settings.

Default configuration an adf-config.xml file will be:-

8.  adfc-config.xml :-

•  It is a configuration file for ADF UnBounded Task Flow.
• It contains the information about the activities used on unbounded task flow and the control flow between the pages used on unbounded task flow.
• It also contains the reference of exception handler for view activity. and reference to a managed bean or create managed bean.

9.  faces-config.xml :-

• The faces-config.xml file contains the configurations for a web application built using JSF. This file allows to configure managed beans, data convertors, and validators used in the UI, navigation cases, global resource bundles, view handlers, page lifecycle phase listeners, and custom lifecycle factory implementation for the application.
• The search order is such that the reference to a managed bean is first resolved to faces-config.xml. If the bean is not found there, then ADFc configuration file is referenced.

10.  trinidad-config.xml :-

This file contains the configuration of asf skin files.

11.  web.xml :-

  The web.xml file acts as a deployment descriptor for a java-based web application.

You must configure the following in web.xml for all applications that use JSF and ADF Faces:

• JSF servlet and mapping : The javax.faces.webapp.FacesServlet servlet that manages the request processing life cycle for web applications using JSF to construct the user interface.
• ADF Faces filter and mapping : A servlet filter to ensure that ADF Faces is properly initialized by establishing an AdfFacesContext object. This filter also processes file uploads.
• ADF resource servlet and mapping : A servlet to serve web application resources (images, style sheets, JavaScript libraries) by delegating to a ResourceLoader.

The JSF servlet and mapping configuration settings are automatically added to the web.xml file when you first create a JSF project.

12.  connection.xml  :-

• This files contains configuration of database connection.
• If webservice is exposed on an application then that web service connection configure on this file.

13.  jps-config.xml :-

• This file contains the configuration of oracle platorm securities such as key store files etc.