This appendix includes the following sections:
The property inspector does not validate that values you enter for a property or combinations of properties are valid. Invalid values may cause runtime errors. To avoid runtime errors, make sure you specify valid values for properties in the property inspector. For more information about the property inspector, see Using the Property Inspector.
Using a server ping test, you can verify that the Fusion web application is running the ADF Desktop Integration remote servlet (
adfdiRemote), and the version of ADF Desktop Integration. This information can be useful if you encounter errors with an integrated Excel workbook. For example, you can determine whether the ADF Desktop Integration remote servlet is running when you are troubleshooting an integrated Excel workbook.
For Fusion web applications that enforce authentication, you can use the server ping test to confirm that the proper authentication configuration is in place for the ADF Desktop Integration servlet URL.
ADF Desktop Integration relies on various Internet Explorer specific settings. For this reason, please perform the verification test using Internet Explorer.
To verify that the ADF Desktop Integration remote servlet is running:
RemoteServletPathinto the address bar of your web browser. This corresponds to a URL similar to the following:
If the ADF Desktop Integration remote servlet is running, a web page returns displaying a message similar to Figure C-1.
Figure C-1 ADF Desktop Integration Remote Servlet
ADF Desktop Integration provides a number of tools so that you and end users can diagnose and resolve issues that may occur in the client-side environment. These include the Client Health Check Tool, described in Running the Client Health Check Tool. This determines if the client environment is configured correctly and provides options to resolve some commonly-encountered issues. You or end users can also generate a diagnostic report (
adfdi-diagnostic-report.txt) from an integrated Excel workbook, as described in the following section.
You or your end users can generate the diagnostic report by clicking the Save Diagnostic Report menu entry that ADF Desktop Integration adds to Microsoft Excel’s File > Add-Ins menu, as shown in Figure C-2.
Figure C-2 File Menu to Save Diagnostic Report
The location of this menu entry depends on the version of Microsoft Excel that you use. Figure C-2 shows the location of this menu entry in Microsoft Excel 2013.
Alternatively, you or end users can generate the diagnostic report from the About dialog.
To generate the ADF Desktop Integration diagnostic report from the About dialog:
If you have opened the integrated Excel workbook in runtime mode, click the About button of the runtime ribbon tab.
Desktopdirectory (for example,
The diagnostic report is a text file and includes a variety of information such as:
ADF Desktop Integration add-in version
Microsoft Windows version
Microsoft Excel version
Values of all properties from the Version tab of the About dialog
Values of all properties listed in the Properties tab of the About dialog
List of Excel COM add-ins
Branding items from the About tab, if the report is generated at runtime
ADF Desktop Integration servlet version, if the report is generated after a valid login
You can open and edit the text file in any text editor, or Excel. Each row in the file consists of a key-value pair separated by tabs.
Before end users send the diagnostic file to you, ask them to review the report and remove any sensitive information that they do not want to share.
ADF Desktop Integration provides end users with connection failure reports to help diagnose the cause of connection failures from integrated Excel workbooks to Fusion web applications.
A connection failure report contains information that ADF Desktop Integration generates when an attempt to connect to a Fusion web application fails or the end user cancels the connection attempt. Figure C-3 shows the dialog that appeared when the
EditCustomers.xlsx workbook failed to connect to the Summit sample application because the latter application was offline. End users click Save Report to save the report to a directory on their machine.
Figure C-3 End User’s Dialog to Save a Connection Report
Before end users send the connection failure report file to you, ask them to review the report and remove any sensitive information that they do not want to share. The following example shows an extract of the report generated in Figure C-3.
Report: Oracle ADF Desktop Integration (ADFdi) Connection Failure Report Generated: (UTC) 04/12/2015 09:47:13 Language: en-US *** NOTE: this file contains detailed diagnostic information. Review the contents and edit out any information you do not wish to share with third parties. *** === Summary === Failure Phase AuthenticationTest Failure Reason UnexpectedHttpStatusException - ADFDI-00501: An unexpected status: 404 (NotFound) was returned from the server while requesting the URL: http://127.0.0.1:7101/summit/adfdiRemoteServlet ADFdi servlet URL http:// 127.0.0.1:7101/summit/adfdiRemoteServlet ...
For more information, see the documents that you can retrieve from My Oracle Support (https://support.oracle.com) if you search for Doc IDs
If end users of an integrated Excel workbook do not get prompted for user credentials when they invoke an action that interacts with the Fusion web application configured with ADF security, it may mean that security is not configured correctly for either the integrated Excel workbook or the Fusion web application. You can verify that your secure Fusion web application authenticates end users and that it is security-enabled by carrying out the following procedure.
To verify that a secure Fusion web application authenticates end users, in the web browser's address bar, enter the URL that you used to verify whether ADF Desktop Integration remote servlet is running. For more information, see Verifying That Your Fusion Web Application Supports ADF Desktop Integration. If the Fusion web application is security-enabled, it will request that you enter user credentials.
For more information about securing your integrated Excel workbook, see Securing Your Integrated Excel Workbook.
ADF Desktop Integration can generate log files that capture information based on events triggered by the following pieces of software within ADF Desktop Integration:
HTTP filter and the ADF Desktop Integration remote servlet on the web server (server-side logging)
For more information about server-side logging, see About Server-Side Logging.
Excel workbook which you integrate with your Fusion web application (client-side logging)
For more information about client-side logging, see About Client-Side Logging.
You configure the generation of server-side log files for ADF Desktop Integration the same way as for other Oracle ADF modules. This involves setting values that specify the verbosity level and output location in a configuration file named
logging.xml. You can also use Oracle Diagnostic Logging Configuration of JDeveloper to configure the logging levels specified in the
logging.xml file. For more information about using the JDeveloper debugging tools and ADF Logger, see the "Using the ADF Logger" section in the Developing Fusion Web Applications with Oracle Application Development Framework.
Table C-1 describes the package names that you supply as attribute parameters to the
<logger> elements in the
logging.xml file to configure log file generation in ADF Desktop Integration.
Table C-1 Package Names for Log File Configuration
|To generate log file entries for this component...||Enter this package name...|
All ADF Desktop Integration server logic
ADF Desktop Integration HTTP filter
Using the Oracle Diagnostics Log Analyzer, you can view a hierarchical breakdown of elapsed time spent performing each ADF Desktop Integration servlet request. The hierarchical breakdown also includes the time spent in other ADF components, such as the ADF Model layer. For more information about using the log analyzer for viewing web requests, see the "How to Use the Log Analyzer to View Log Messages" section in the Developing Fusion Web Applications with Oracle Application Development Framework.
The hierarchical breakdown can be helpful in identifying performance bottlenecks due to unusually long execution times.
In order to log a complete hierarchy tree of ADF event messages, including ADF Desktop Integration events, specify log level
CONFIG for the
oracle.adfdiagnostics package. For more information about the
oracle.adfdiagnostics logger, see the "How to Create an Oracle ADF Debugging Configuration" section in Developing Fusion Web Applications with Oracle Application Development Framework.
ADF Desktop Integration provides a number of methods to create log files of activity that occur within the ADF Desktop Integration add-in. Logging is always enabled at a high level, the
Information level. These logs are in plain text format and include the basic user steps as well as any errors and warning. For more information, see What You May Need To Know About Always-On Logging.
In some cases, you may need more detailed logs to troubleshoot a particular problem. There are several methods for producing detailed logs at the
Verbose level. The simplest method is to enable transient verbose logging by selecting Enable Logging... from the Excel add-in menu that ADF Desktop Integration adds to Microsoft Excel. These logs are in XML format and include a very detailed account of client-side activity. For more information, see Enabling Transient Verbose Logging for One User Session.
Additionally, there are two other methods for controlling client logs:
Using the Logging options that the Oracle ADF tab exposes, as described in How to Configure Logging in the Oracle ADF Tab.
Using the ADF Desktop Integration Configuration file, as described in About the ADF Desktop Integration Configuration File.
Configuring environment variables, as described in How to Configure Logging Using User Environment Variables.
Consider using one of the latter two options if you want to capture log information that spans one or more integrated Excel workbook restarts and/or you want to configure a lower logging level than
Table C-2describes the different log levels that you can enable for client-side logging.
By default, ADF Desktop Integration enables logging at the
Information level to a text file in the
adfdi-logs sub-directory of one of the following directories, listed in order of preference:
To determine which of the above directories ADF Desktop Integration uses to store log file information, see the Log Files property that you can view from the About dialog of your integrated Excel workbook, as shown in Figure C-4.
Figure C-4 Directory Location of Always-on Log Files
ADF Desktop Integration creates a new log file each time you start a new user session with an integrated Excel workbook. It uses the convention
.txt when naming log files where
timestamp is the time at which you start the integrated Excel workbook (for example,
Note:ADF Desktop Integration purges the oldest always-on log file(s) in the folder when the folder reaches a certain size.
For more information, see the document that you can retrieve from My Oracle Support (https://support.oracle.com) if you search for Doc ID
You or your end users can enable verbose logging from a menu in the active integrated Excel workbook. ADF Desktop Integration writes verbose log information to a file in a directory you specify when you enable the logger from the menu.
The filename that ADF Desktop Integration creates when you enable this logging has the following format:
Where timestamp is the time at which you enable logging. For example,
Figure C-5 Excel File Menu to Enable Verbose Logging
Once you quit Microsoft Excel, ADF Desktop Integration stops logging information to the log file.
To enable transient verbose logging for one user session:
Launch Microsoft Excel from the Windows menu but do not open the integrated Excel workbook with the issue for which you want to capture verbose log data.
From the Office or File menu of Excel, select Add-Ins > ADF Desktop Integration > Enable Logging, as shown in Figure C-5.
Save the log file to a location of your choosing or use the default Desktop location that the Save Logging Data As dialog proposes. Note the log file name and location for later reference.
Open the integrated Excel workbook and repeat the steps to reproduce the issue for which you want to capture verbose log data.
Once you have completed the steps, you can quit Microsoft Excel. Once you quit Microsoft Excel, ADF Desktop Integration stops logging verbose data to the log file you created in Step 3.
Tip:Save a diagnostic report with information about the environment where ADF Desktop Integration runs that you can submit to Technical Support with the verbose log data that you have captured for your issue. From the Office or File menu of Excel, select Add-Ins > ADF Desktop Integration > Save Diagnostic Report, as shown in Figure C-5.
For more information, see the document that you can retrieve from My Oracle Support (https://support.oracle.com) if you search for Doc ID
The Oracle ADF Tab, shown in Figure C-6, provides a Logging group of menu options that are available in both design mode and test mode.
Figure C-6 Logging Tools in Oracle ADF Tab
The Logging group provides the following buttons:
Displays the Logging Console window, which enables you to review the recent log entries while you are developing and testing the integrated Excel workbook. The console displays entries that are logged while the console is open. Figure C-7 illustrates the Logging Console window with error log entries.
The console is a resizable, non-modal window with a buffer size of 64,000 characters. When the buffer is full, the old entries are removed.
Figure C-7 Logging Console Window
The dialog has the following buttons:
Set Level: Click to set the log output level. The button opens the Logging Output Level dialog, where you can choose the desired log output level.
Clear: Click to clear the log buffer.
Close: Click to close the dialog.
A common Logging Console window logs entries for all open integrated Excel workbooks.
Set Output Level
Prompts you to choose the log output level. Table C-2 describes the log levels that client-side logging supports. The log levels are cumulative as you read down the list in Table C-2. That is, the
Information level includes the data logged in the
Warning levels, but not the
Figure C-8 Logging Output Level Dialog
Table C-2 Client-Side Logging Levels
Captures critical information.
Captures information about severe errors and exceptions.
Captures information about warnings.
Captures lifecycle and control flow events. This is the default value.
Captures detailed information about the execution flow of the application.
The log output level applies to all listeners for a given logger.
Add Log Output File
Creates a new temporary logging listener to direct logging output to the specified file or format. In the Add New Temporary Logging Output File dialog, choose the desired file output type (text or XML), and specify the path and file name of the log output file.
Figure C-9 Add New Temporary Logging Output File Dialog
The temporary listener directs the logging output for the current Excel session only, and is not registered in the ADF Desktop Integration configuration file. After you exit Excel, the temporary listener is removed.
When you click the Add Log Output File button, a new listener is created. The new listener does not replace any existing listener defined in the ADF Desktop Integration configuration file, or any other temporary listener.
Reloads the ADF Desktop Integration configuration file. The ADF Desktop Integration configuration file can determine the level of information logged by the ADF Desktop Integration add-in.
For more information about the creation and configuration of the ADF Desktop Integration configuration file, see About the ADF Desktop Integration Configuration File.
The ADF Desktop Integration configuration file is saved as
adfdi-excel-addin.dll.config. To determine the correct file name and location, click the About button in the Workbook group of the Oracle ADF tab. In the dialog that opens, click the Properties tab, and consult the Configuration entry for file name and location of configuration file.
For more information about elements of the configuration file, see the "Configuration File Schema for the .NET Framework" section in Microsoft Developer Network documentation. For more information about trace and debug settings, see the "Trace and Debug Settings Schema" section in Microsoft Developer Network documentation.
Example C-1 shows a sample configuration file, one of many valid ways to configure client-side logging, that generates an
.xml log file. The file captures different types of information such as
DateTime at a
Verbose logging level.
Example C-1 Sample Configuration File
<?xml version="1.0"?> <configuration> <system.diagnostics> <sources> <source name="adfdi-common" switchValue="Verbose"> <listeners> <add type="System.Diagnostics.XmlWriterTraceListener" name="adfdi-common-excel.xml" initializeData="c:\logs\adfdi-common-excel.xml" traceOutputOptions="ThreadId, ProcessId, DateTime"/> </listeners> </source> </sources> </system.diagnostics> </configuration>
Users who do not have access to the directory that stores the ADF Desktop Integration configuration file can change the location where log files are saved, and the logging level by setting values for user environment variables. You can add two user environment variables to configure the logging level and location for XML log files.
For more information, see the “How To Obtain Log Files For ADF Desktop Integration” document that you can retrieve from My Oracle Support (https://support.oracle.com) if you search for Doc ID
Tip:Be sure to exit Excel completely prior to configuring the environment variables.
To add or configure user environment variables on Windows:
Table C-3 User Environment Variables to Configure Logging
|Enter a variable named...||With a value...|
That defines the directory path and file name for the XML file that captures logging information.
The directory that you specify here must exist before you add the
That specifies the level of logging. Table C-2 lists valid values.
adfdi-common object is an instance of the
TraceSource class from the
System.Diagnostics namespace in the Microsoft .NET Framework. This object is used to generate log files that capture information about events triggered by the Excel workbook that you integrate with your Fusion web application. To know the location of the log file, check the Log Files attribute in the Properties tab of the About dialog.
For more information about the
TraceSource class, see Microsoft Developer Network documentation.