What happens when you create a database connection in ADF application?

When you create a database connection, JDeveloper generates a set of metadata XML files to keep the connection information. Let us take a quick look at these files.
                                                         

1. connections.xml:-

-This file contains the database connection detail that we create for development. If your application consumes web services or map viewer services, the corresponding connection uniform resource locator (URL) will also be present in this file.

2. jps-config.xml:-

-The jps-config.xml file is used to store the Oracle Platform Security configurations.
-The location of this file is configured in adf-config.xml.
-If your application is not configured to use ADF Security, this file, at a minimal level, acts as a pointer to cwallet.sso, which contains the password for the database connection details present in connections.xml.

3. cwallet.sso:-

-The cwallet.sso file follows the Oracle Platform Security Services (OPSS) specification and it is used as a credential provider in connecting to external systems, such as databases.
-This file is normally not edited directly.

Thanks...

What are the ADF Business Components configuration files

When you generate business components, the wizard will also generate metadata configuration XML files to manage the runtime behavior of ADF Business Components. Let us take a quick tour of these metadata configuration files.

1. bc4j.xcfg:

-The bc4j.xcfg file contains metadata information about the application module and runtime parameters that have been configured to manage the runtime behavior of each application module instance. When you generate an application module, this file will be automatically generated in common subfolders relative to the folder where you create the application module definition. If you edit an application module configuration by using the editor, the modified values are set in the corresponding bc4j.xcfg file.

2. <ModelProjectName>.jpx:

-The <ModelProjectName>.jpx file is used by both design-time editors and runtime framework components.
-JDeveloper uses the <ModelProjectName>.jpx file as a registry to track the contents of the model packages. It also contains metadata for shared application modules present in the project, which is used by both design-time and runtime components.

3. adfm.xml:

-The adfm.xml file contains path information for other registry files used in the model project. You may not see this file in a model project source during development. Jdeveloper generates this file with appropriate entries when you build a model project.
-The adfm.xml records path information for the following files, if they are present in the project:
•    bc4j.xcfg
•     <ModelProjectName>.jpx
•     DataControls.dcx
•     DataBindings.cpx
-This file is used as a registry of registries in the view controller (Web UI) project as well.


Thanks...

Why ADF Business Components?

Business service implementation for any enterprise application generally involves the following three major tasks:
-Building business logic for the application
-Building generic infrastructure services such as connecting to a database, transaction management, business data audit, validation, security and product customization
-Exposing the services through multiple channels such as EJB, web service, plain Java to be used by various clients

Thanks...

Auto generated metadata files in ADF application

When you create the Fusion web application, the below files are generated inside the source folder. Let us take a quick look on these metadata XML files to understand the role of each item in our application.
                                                     

1. adf-settings.xml:

-The adf-settings.xml file keeps the UI project configurations.

-The adf-settings.xml file holds project- and library-level settings such as ADF Faces help providers and caching/compression rules. 

-The configuration settings for the adf-settings.xml files are fixed and cannot be changed during and after application deployment.

-This file is present in side < project-root >/src/META-INF folder

-There can be multiple adf-settings.xml files in an application.

2. faces-config.xml: 

- The faces-config.xml file contains the configurations for a web application built using JSF.

-This file allows us to configure managed beans, data convertors, and validators used in the UI, navigation cases, global resource bundles, view handlers, page life-cycle phase listeners and custom life-cycle factory implementation for the application.

3. adfc-config.xml:

-The default name for an ADF unbounded task flow's XML source file is adfc-config.xml.

-Each Fusion web application optionally contains a single ADF unbounded task flow.

-The adfc-config.xml file contains activities, control flow rules, and managed beans interacting to allow a user to complete a task.

4. trinidad-config.xml: 

-The generated trinidad-config.xml file contains only the skin family name. However, trinidad-config.xml can be used to override the default configurations for accessibility settings, locale settings, state management, and so on.

-We can configure the Page animation, Level of page accessibility support, Time zone, Enhanced debugging output and Oracle Help for the Web (OHW) URL through trinidad-config.xml file.

5. web.xml:

-The web.xml file acts as deployment descriptor for a Java-based web application. When you generate a Fusion web application by using JDeveloper, a default web.xml file with default settings will be created for you.

-The default entries include context parameters for configuring the runtime state of the system, security filters, data binding filters for web pages, and resource look up filters.

-The web.xml file also includes servlet context listeners for initializing the management and monitoring services for view and model layers.

6. adf-config.xml:

-The adf-config.xml file contains application-level settings, which manage the runtime infrastructure such as failover behavior for the application modules, global fetch limit for all the view objects, caching of resource bundles, automated refresh of page bindings, and so on—for your application.

-The properties like initial-size, max-size, load-factor, expire-time you can configure inside the adf-config.xml.

7. weblogic-application.xml:

-This file is the WebLogic Server-specific deployment descriptor.

For more information you can follow the below links:

http://docs.oracle.com/cd/E15586_01/web.1111/b31974/appendixa.htm#BGBIFEJE

http://docs.oracle.com/cd/E15586_01/web.1111/b31973/ap_config.htm#CEGDJBHH

Thanks...