Oracle ADF Single Node Architecture Oracle ADF External Dependencies

Configuring High Availability for Oracle ADF and WebCenter Applications 6-5 To achieve these front-end capabilities, ADF Faces components use a rendering kit that handles displaying the component and also provides the JavaScript objects needed for the rich functionality. This built-in support enables developers to build rich applications without needing extensive knowledge of the individual technologies on the front or back end. For more information about ADF Faces, including the architecture and detailed information about each of the components, go to the Oracle Fusion Middleware Web User Interface Developers Guide for Oracle Application Development Framework.

6.1.1.2 Oracle ADF Single Node Architecture

You can install the Oracle ADF runtime to the Oracle WebLogic Server using either the Oracle JDeveloper Installer or the Oracle Fusion Middleware Application Developer Installer. The Application Developer Installer also lets you optionally install Fusion Middleware Control to provide web-based administration support for all Managed Servers in the domain. The Oracle JDeveloper installer does not install Fusion Middleware Control. Both of these options are described in the deployment chapter of the Oracle Fusion Middleware Fusion Developers Guide for Oracle Application Development Framework. When you use the Application Developer Installer to install the Oracle ADF runtime, it results in the creation of an Oracle Application Developer home directory by default, Oracle_APPDEV1 located under the Middleware home. After the administrator uses the domain configuration wizard to create an Application Developer domain base_ domain based on the JRF domain template, the administrator can configure the topology of the server. In a typical set up, the domain contains an Administration server containing the WLS Administration Console and Fusion Middleware Control. Typically, the Oracle ADF runtime libraries part of the Java Required Files get deployed to the Managed Servers, in addition to the user-facing custom Fusion web applications. To provide customization and personalization features, an optional MDS repository may also be installed, and needs to be configured separately. Figure 6–3 shows a basic single-node Oracle ADF architecture. Figure 6–3 Basic Single-Node Oracle ADF Architecture For more information about domains and servers, see the Oracle Fusion Middleware Administrators Guide.

6.1.1.3 Oracle ADF External Dependencies

If the Fusion web application involves customization using Oracle Metadata Services MDS, you should register your MDS repository with the Oracle WebLogic Server 6-6 Oracle Fusion Middleware High Availability Guide domain before you deploy the application. For information about registering MDS, see the Oracle Fusion Middleware Administrators Guide. Then, when you deploy the application, JDeveloper prompts you to choose the target metadata repository or shared metadata repository. You will be able to choose from the list of metadata repositories registered with the Oracle WebLogic Administration Server. To ensure that you receive the metadata repository prompt, the application’s adf-config.xml file must define a cust-config element in the mds-config section. This element specifies an ordered and named list of customization classes. A customization class is the interface that MDS uses to define which customization applies to the base definition metadata. In JDeveloper, you can use the overview editor for the adf-config.xml file to define a cust-config element. For information about configuring the adf-config.xml file for MDS, see the chapter on customizing with MDS in the Oracle Fusion Middleware Fusion Developers Guide for Oracle Application Development Framework. For more information about the MDS architecture and metadata repositories database and file-based and archives EAR, MAR, refer to the Oracle Fusion Middleware Administrators Guide.

6.1.1.4 Oracle ADF Log File