11-4 Desktop Integration Developers Guide for Oracle Application Development Framework
To reset a workbook ID: 1.
Open the integrated Excel workbook.
2. Click Workbook Properties in the Oracle ADF tab.
3. In the Edit workbook Properties dialog, click the Reset WorkbookID link.
4. Click Yes to confirm and reset the WorkbookID workbook property in the dialog
that appears.
5. Click OK.
11.3.2 How to Disable the Metadata Tamper-Check in the Fusion Web Application
By default, ADF Desktop Integration verifies that the metadata it uses to integrate an Excel workbook with a Fusion web application is not tampered with after you publish
the Excel workbook for end users. You can disable the metadata tamper-check by configuring a parameter in the deployment descriptor file web.xml of the Fusion
web application, although this is not recommended.
To disable the metadata tamper-check in the Fusion web application: 1.
Stop your Fusion web application.
2.
Open the web.xml file of your Fusion web application.
3.
Add an initialization parameter to the adfdiRemote servlet to disable the metadata tamper-check, as described in
Table 11–1 .
Figure 11–3 shows the web.xml editor in JDeveloper.
Table 11–1 Disabling Metadata Tamper-Check
Property Value
Name Enter the name of the initialization parameter as follows:
TamperingCheck.Enabled Value
Set the value of TamperingCheck.Enabled to False.
Securing Your Integrated Excel Workbook 11-5
Figure 11–3 Disabling the Metadata Tamper Check In JDeveloper
4.
Save the web.xml file. The web.xml file of your Fusion web application has the following entries:
servlet servlet-nameadfdiRemoteservlet-name
servlet-class...servlet-class init-param
param-nameTamperingCheck.Enabledparam-name param-valueFalseparam-value
init-param servlet
5.
Rebuild and restart your Fusion web application. For more information about the web.xml file, see
Appendix E, ADF Desktop Integration Settings in the Web Application Deployment Descriptor.
11.3.3 How to Allow Missing Entries in the ADF Desktop Integration Client Registry
You can configure the metadata tamper-check so that a missing entry for the WorkbookID workbook property is allowed in the adfdi-client-registry.xml
file. To do this, you configure a parameter in the deployment descriptor file web.xml of the Fusion web application, although this is not recommended.
To allow missing entries in the metadata of the Fusion web application: 1.
Stop your Fusion web application.
11-6 Desktop Integration Developers Guide for Oracle Application Development Framework
2.
Open the web.xml file of your Fusion web application.
3.
Add an initialization parameter to the adfdiRemote servlet to allow missing entries in the metadata as described in
Table 11–2 .
Figure 11–4 shows the web.xml editor in JDeveloper.
Figure 11–4 Enabling Missing Metadata Entries In JDeveloper
4.
Save the web.xml file. The web.xml file of your Fusion web application has the following entries:
servlet servlet-nameadfdiRemoteservlet-name
servlet-class...servlet-class init-param
param-nameTamperingCheck.AllowMissingEntriesparam-name param-valueTrueparam-value
init-param servlet
Table 11–2 Allowing Missing Entries in the Metadata
Property Value
Name Enter the name of the initialization parameter as follows:
TamperingCheck.AllowMissingEntries Value
Set the value of TamperingCheck.AllowMissingEntries to True.
Securing Your Integrated Excel Workbook 11-7
5.
Rebuild and restart your Fusion web application. For more information about the web.xml file, see
Appendix E, ADF Desktop Integration Settings in the Web Application Deployment Descriptor.
11.3.4 What Happens When the Metadata Tamper-Check is Performed
