This chapter describes features in ADF Desktop Integration that help you test your integrated Excel workbook as you configure it. It includes the following sections:
Testing an integrated Excel workbook before you publish and deploy it to your end users enables you to verify that the functionality you configure behaves as you intend. Before you test your integrated Excel workbook, test the Fusion web application with which you integrate the Excel workbook. Once your Fusion web application functions as you intend, use the test mode provided by ADF Desktop Integration to test the functionality in your integrated Excel workbook.
Test the Fusion web application that you integrate your Excel workbook with before you start testing the integrated Excel workbook. For information about testing a Fusion web application, see the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework. Verify that the Fusion web application you want to integrate an Excel workbook with, supports ADF Desktop Integration by carrying out the procedure described in Section C.1, "Verifying That Your Fusion Web Application Supports ADF Desktop Integration."
There are some differences between the test mode and the runtime mode when you run the integrated Excel workbook. Table 13-1 lists these differences.
Table 13-1 Differences between Test mode and Runtime mode
| Test mode | Runtime mode |
|---|---|
|
Does not perform tamper check |
Performs tamper check |
|
Does not display the connection confirmation dialog |
Displays the connection confirmation dialog |
|
Displays the Oracle ADF ribbon tab |
Does not display Oracle ADF tab |
|
Allows you to switch back to design mode |
Does not allow you to switch back to design mode |
Before you run the Fusion web application in JDeveloper, ensure that you have closed all integrated Excel workbooks and the Excel application. The application deployment may fail if it encounters locked files as Excel locks the files that it opens.
Tip:
If you plan to test integrated Excel workbooks that you downloaded from web pages of the Fusion web application, you should republish them before redeploying the application. Republishing the workbooks ensures that you have their latest versions.If you make changes to the Fusion web application to resolve problems identified by testing the application, you need to:
Close Excel and all integrated Excel workbooks. The application deployment may fail if it encounters locked files, as Excel locks the files that it opens.
Rebuild the JDeveloper project where you develop the Fusion web application.
Run the Fusion web application.
Reload the page definition files that are associated with the integrated Excel workbook. Click the Refresh Bindings button in Oracle ADF tab of the integrated Excel workbook to reload the page definition files.
These steps make sure that the changes in the Fusion web application are available to the integrated Excel workbook. For information about how to reload a page definition file, see Section 4.3.3, "Reloading a Page Definition File in an Excel Workbook."
The server ping test enables you to check the version of ADF Desktop Integration Remote Servlet in a running system. It also helps to confirm that the remote servlet is loaded and responding.
After running the Fusion web application and logging in as a valid user, open a URL in the following format to verify whether the remote servlet is running:
http://<hostname>:<portnumber>/<context-root>/adfdiRemoteServlet
For example, if you run the Master Price List Fusion web application, open the following URL:
http://127.0.0.1:7101/FODMasterPriceList/adfdiRemoteServlet
The following response verifies that the remote servlet is running:
Oracle ADF 11g Desktop Integration (11.1.1.55.30) [1738]
Response from oracle.adf.desktopintegration.servlet.DIRemoteServlet: OK.
In the above example, the remote servlet version is 11.1.1.55.30 and the ADF Desktop Integration version corresponding to the remote servlet is 1738.
Note:
A valid user session is required to run the server ping test. If authentication is enabled for the web application, you will be prompted for valid credentials to log in.As you configure your Excel workbook to integrate with a Fusion web application, you can switch to test mode from design mode to test the functionality that you add to the workbook. You use the Oracle ADF tab to switch to test mode from design mode and from design mode to test mode.
Test mode enables you to test the functionality of your integrated Excel workbook as you configure it incrementally. It also enables you to view the integrated Excel workbook from the end user's perspective, as test mode corresponds to what end users see when they view and execute the published integrated Excel workbook. The difference between an integrated Excel workbook in test mode and a published integrated Excel workbook is that the ADF Desktop Integration task pane is not available to users of the published integrated Excel workbook.
For more information about test mode and design mode, see Section 5.1, "Introduction to Development Tools."
ADF Desktop Integration can generate log files that capture information based on events triggered by an integrated Excel workbook. For more information about these log files, see Appendix C, "Troubleshooting an Integrated Excel Workbook."
Note:
Before you start testing the integrated Excel workbook, ensure that:The Fusion web application is running
The ping to server is successful, and the server is configured for ADF Desktop Integration
To run an integrated Excel workbook in test mode:
To test and run an integrated Excel workbook, click the Run button on the Oracle ADF tab.
The integrated Excel workbook switches to test mode from design mode.
To stop test mode and return the integrated Excel workbook to design mode:
In the integrated Excel workbook that you are testing, click the Stop button on the Oracle ADF tab.
The integrated Excel workbook switches to design mode from test mode.
Note:
When the end user tries to close the integrated Excel workbook, Microsoft Excel prompts a dialog to save the workbook even if the end user has not modified it after opening it. This behavior is expected because ADF Desktop Integration modifies an integrated Excel workbook each time the end user opens it.