# Appendix A Oracle ADF XML Files

For more information about configuring GlassFish Server for Oracle ADF Essentials, see "Configuring GlassFish Server" in Administering Oracle ADF Applications.

Metadata files in an Oracle ADF application are structured XML files used by the application to:

- Specify the parameters, methods, and return values available to your application's Oracle ADF data control usages.

- Define configuration information about the UI components in JSF and ADF Faces.

- Define application configuration information for the Java EE application server.

The ADF metadata files created by OEPE are listed below.

## Oracle ADF Data Binding Files

OEPE creates the following ADF data binding files:

- `adfm.xml`: This file lists the `DataBindings.cpx` file that is available in the current project. For more information about `adfm.xml`, see Section A.4, "adfm.xml" in Developing Fusion Web Applications with Oracle Application Development Framework.

- `DataBindings.cpx`: This file contains the page map, page definitions references, and data control references. The file is created the first time you create a data binding for a UI component. The `DataBindings.cpx` file defines the Oracle ADF binding context for the entire application. The binding context provides access to the bindings and data controls across the entire application. See Section A.7, "DataBindings.cpx" in Developing Fusion Web Applications with Oracle Application Development Framework.

- `pagename` `PageDef.xml`:This is the page definition XML file. It associates web page UI components with data, or data controls. OEPE creates this file each time you design a new web page. These XML files contain the metadata used to create the bindings that populate the data in the web page's UI components. For every web page that refers to an ADF binding, there must be a corresponding page definition file with binding definitions. See Section A.8, "pagenamePageDef.xml" in Developing Fusion Web Applications with Oracle Application Development Framework.

## Web Configuration Files

OEPE creates the following Oracle ADF web configuration files:

- `web.xml`: Part of the application's configuration is determined by the contents of its Java EE application deployment descriptor, `web.xml`. The `web.xml` file defines everything about your application that a server needs to know. The file plays a role in configuring the Oracle ADF data binding by setting up the ADFBindingFilter. Additional runtime settings include servlet runtime and initialization parameters, custom tag library location, and security settings.

  An ADF Faces application typically uses its own set of configuration files in addition to `web.xml`. For more information, see the "Configuration in `trinidad-config.xml`" section in Developing Web User Interfaces with Oracle ADF Faces.

- `adfc-config.xml`: The configuration file for an ADF unbounded task flow. The configuration file contains metadata about the activities and control flows contained in the unbounded task flow. The default name for this file is `adfc-config.xml`, but an end-user can change the name.

- `task-flow-definition.xml`: The configuration file for an ADF bounded task flow. The configuration file contains metadata about the activities and control flows contained in the bounded task flow. The default name for this file can be `task-flow-defintion.xml` or whatever an end user specifies when creating the task flow. The same application can contain multiple task flow definition files.

For more information on Oracle ADF configuration files, see the Oracle ADF XML Files appendix in Developing Fusion Web Applications with Oracle Application Development Framework.