adf-config.xml and connections.xml both store design time configuration information, such as the mail server or content server that is used by the application in the development environment:

• adf-config.xml - Stores application-level settings, such as which mail server the application is currently using.

• connections.xml - Stores connection details for WebCenter Portal services.

  See Developing Fusion Web Applications with Oracle Application Development Framework.

After you deploy WebCenter Portal to a production environment, Oracle recommends that you use Fusion Middleware Control or WebLogic Scripting Tool (WLST) commands to reconfigure properties in these files. For example, you may want to modify connection details to point to production server instances. See Configuration Tools.

The main advantage of using Fusion Middleware Control and WLST commands is that any configuration changes that you make, post deployment, are stored as customizations in the application's Oracle Metadata Services (MDS) repository. MDS uses the original deployed versions of adf-config.xml and connections.xml as base documents and stores all subsequent customizations separately into MDS using a single customization layer. If the application is redeployed in the future, all previous configuration changes are retained.

When WebCenter Portal starts up, application customizations stored in MDS are applied to the appropriate base documents and the application uses the merged documents (base documents with customizations) as the final set of configuration properties.

This section includes the following subsections:

• Reviewing Post Deployment Customizations in MDS

• Exporting Configuration Files with MDS Customizations

• Handling Configuration Conflicts

• Deleting MDS Customizations for adf-config.xml or connections.xml

For more information on MDS customizations, see Understanding the MDS Repository in Administering Oracle Fusion Middleware.

web.xml is a standard J2EE application deployment descriptor file and it is located in the /META-INF directory for your application. Typical run-time settings in web.xml include initialization parameters, custom tag library locations, and security settings.

Most web.xml properties are static so they are specified for the application at design time before generating and deploying the application's .par file. If you need to modify some properties in a deployed environment, you can edit some properties through the "Configure Web Modules" screen on the "Deployment Settings" page.

Unlike connections.xml and adf-config.xml, web.xml does not store post deployment customizations in MDS and you cannot use Fusion Middleware Control or WLST commands to modify web.xml in an existing deployment, such as WebCenter Portal.

There are very few instances where you might want to modify web.xml, for example, in some circumstances you may want to change:

• Content repository upload parameters: UPLOAD_MAX_MEMORY, UPLOAD_MAX_DISK_SPACE, and UPLOAD_TEMP_DIR.

  For WebCenter Portal, use the uploadedFileMaxDiskSpace parameter in webcenter-config.xml to configure a maximum upload size for files. For details, see webcenter-config.xml.

• Time after which HTTP sessions expire.

  See Specifying Session Timeout Settings.

• JSP page timeout value.

• Browser compatibility notifications for Internet Explorer. Set the oracle.adf.view.rich.HIDE_UNSUPPORTED_BROWSER_ALERTS parameter:

      <!-- Suppress Browser Compatibility popup messages -->
      <context-param>
        <param-name>
            oracle.adf.view.rich.HIDE_UNSUPPORTED_BROWSER_ALERTS
        </param-name>
        <param-value>IECompatibilityModes</param-value>
      </context-param>
  

  Note: Alternatively, Internet Explorer users can turn off Compatibility Mode before trying to access WebCenter Portal. In Internet Explorer, select the Tools menu, and the Compatibility View Settings. In the Compatibility View Settings dialog, deselect all the options, and click Close.

webcenter-config.xml is a configuration file for the out-of-the-box application WebCenter Portal. This file contains application-level settings, such as the application name and logo. Most of the properties in this file are managed through WebCenter Portal administration screens so there is no need to edit webcenter-config.xml directly. For more information, see Exploring the Settings Pages in WebCenter Portal Administration and Configuring Global Defaults Across Portals.

There are a few instances where you might be required to manually modify settings in webcenter-config.xml:

• Maximum file upload size (uploadedFileMaxDiskSpace) - the default setting is 2 GB. This setting is applicable when specifying the maximum upload size for files uploaded from features such as a wiki, blog, or activity stream.

  Note:

  For information about specifying the maximum upload size for files uploaded using Content Manager, see Modifying the File Upload Size in Content Manager.

If you want to modify this setting, you must export the latest version of webcenter-config.xml from MDS and modify the uploadedFileMaxDiskSpace value as follows: