A Troubleshooting Customizations

Customizations are stored in XML files. You can export the customizations for diagnosing issues in a number of ways, as described in About Exporting and Moving Customizations.

Before you make customizations, you can create a backup of a known good state by creating a label. If an issue occurs after creating the label, you can revert back to that label by promoting it to the tip as described in the "Creating Metadata Labels" and "Promoting Metadata Labels" sections of the Administering Oracle Fusion Middleware.

Another way to back up and restore customizations is by exporting and importing customization files, as described in About Exporting Customizations.

When you make customizations, be careful to choose the correct layer:

• Use the site layer for customizations that affect all end users.

• Use the global layer for ADF Business Components customizations.

• Use product-specific layers appropriately as documented.

/package/mdssys/cust/layer-name/layer-value/document-name.suffix.xml

1. Go to the page that contains the customized region and choose Customize page_name Pages from the Administration group in the Settings and Actions menu to open Page Composer.
2. If you have more than one layer available for customization, the Layer Picker dialog is displayed. In the Edit column, select the desired layer.
3. Choose Source from the View menu.
4. In the hierarchical list, drill down to and hover over the customized region to display the full document path of the JSF fragment that contains the customization, such as /oracle/apps/hcm/dashboard/hrSpecialist/publicUI/page/mdssys/Site/SITE/VisaWorkPermitExpirationRegion.jsf.xml. Make a note of this path.

Customizations do not appear if the customization layer is not active in an application. To determine if a customization layer is active, open the adf-config.xml file for the application and look for the <cust-config> tag, as shown in Example A-1. The nested <customization-class> tags show the active layers.

<adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
<mds-config xmlns="http://xmlns.oracle.com/mds/config" version="11.1.1.000">
<cust-config>
  <match path="/">
    <customization-class name ="oracle.apps.fnd.applcore.customization.GlobalCC"/>
    <customization-class name ="oracle.apps.fnd.applcore.customization.SiteCC"/>
    <customization-class name ="oracle.apps.fnd.applcore.customization.UserCC"/>
  </match>
</cust-config>
</mds-config>
</adf-mds-config>

To turn on runtime logging for customizations that are applied to a page, set the log level for the oracle.mds.custmerge module to FINEST. You can set the application's log level by choosing Troubleshooting from the Help menu. You might need to ask your administrator to give you privilege to set the log level.

If you have administration privileges, you can also use Fusion Applications Control to set the log level.

1. Make a note of the string that follows the host name in the URL of the deployed application. For example, if the URL is http://myhost.mycompany.com:7401/myProd/faces/MyPage, make a note of myProd.
2. Open Oracle WebLogic Server Administration Console.
3. Select Deployments.
4. In the Overview tab, click the entry with a name similar to the text that you noted in Step 1, such as MyProdApp (V2.0), to display the settings for that deployed application.
5. In the Overview tab, find the Path setting to see the path to the EAR file.