In this section:
Tools to troubleshoot Developer Studio are available in the WebFOCUS Administration Console, Developer Studio program folder, and Reporting Server Console.
To run the verification tools installed with the WebFOCUS Administration Console, access the console.
Note: The verification tools are only supported with Internet Explorer, and you may receive errors if you use other browsers.
If you are using Apache Tomcat standalone, you can also go to:
For IIS with Tomcat, you can go to:
The WebFOCUS Sign In page opens, as shown in the following image.
If the WebFOCUS Sign In page does not appear, ensure that your web server is started. If the web server is started and this page does not appear, you may need to manually configure the web server, as explained in Configuring the Web Server or Application Server.
The WebFOCUS Administration Console appears, as shown in the following image.
Using this console, you can edit various configuration settings. Information about the various settings in this console can be found by clicking Help. The WebFOCUS Administration Console contains a verification tool to further test the configuration.
Several tests are available from the Diagnostics node.
Expand Verification and then select WebFOCUS Client.
A page similar to the following image appears on the right with a list of tests. The list varies depending on your license and configuration. For a Tomcat standalone configuration, the web/app server tests may not appear.
If a test fails, a Possibilities link appears proving information on what the problem might be and possible solutions. The verification tools are only supported with Internet Explorer, and you may receive errors if you use other browsers.
Expand Verification and then select WebFOCUS Reporting Server to test the connection between the WebFOCUS Client and the WebFOCUS Reporting Server.
The Client Path field is displayed with the path to the WFConsole.cfg file. You are also allowed you to select a node in the Remote Services area, as shown in the following image.
The Client Path specifies how the connection is made. The default servlet URL appears.
You can test the following areas:
The Diagnostics menu in the WebFOCUS Administration Console lets you view and delete WebFOCUS Client trace files. Trace files track requests processed by the WebFOCUS Client. Since tracing can slow performance, you should only turn on traces when troubleshooting.
In the left pane of the WebFOCUS Administration Console, expand Diagnostics, and then expand Traces. You can view the trace files by selecting the type of trace from the list. For example, to view traces generated by the WebFOCUS Servlet, in the left pane of the WebFOCUS Administration Console under Diagnostics and Traces, select WFServlet.
The following image shows the WebFOCUS client traces screen.
A page lists any generated traces. The first column lists the generated trace file. The second column shows a timestamp for when the request ran. You can view a trace file by clicking it.
For more information about the available trace options, click Help in the top-right corner of the WebFOCUS Administration Console.
The Developer Studio trace utility (Communication Layer Trace) generates trace files for tasks performed by the Developer Studio development environment communication layer. It captures information for tasks performed by Developer Studio when a request is submitted or retrieved by the product.
You can use this utility to help troubleshoot issues such as communicate failures, connection problems, and transfer of files.
To generate traces for issues you might encounter at startup, you should start the trace utility prior to launching Developer Studio.
To generate traces for a failure to connect to a Data Server or to determine why applications are not listed, you should start and enable the trace at the point prior to performing the task that fails.
The Communication Layer Trace tool opens, as shown in the following image.
Is your Windows user ID.
Note: The Application Data directory may not be visible by default. To see this directory, open Windows Explorer, click Tools, choose Folder Options, and select the View tab. Then select Show hidden files and folders and click OK.
You can turn WebFOCUS Reporting Server traces on when you start the server or dynamically after the server has started.
Note: Viewing traces is only available to a server administrator.
You can use the Reporting Server Console to view server traces as well as turn them dynamically on or off for a running server.
If tracing is set to off and it was never turned on, the page shows that no traces are available and enables you to turn traces on. If tracing is on, the page displays the available traces in drop-down boxes. Which traces are available depends on what requests were made against the server.
To turn traces on dynamically, click Enable Traces. Be aware that a dynamic trace is not the same as turning traces on at server startup. A dynamic trace is usually not sufficient for following a problem through with Customer Support, but it may suffice for other purposes, such as seeing how something is parsed.
Note: The default for tracing is to trace all components when tracing is turned on. However, the trace settings file (ibitrace.fex) may have been altered. Therefore, components that you expect to be traced may not be traced.
A list of traces displays in the right panel.
The file opens (or is deleted) according the option you choose.