B
Generating trace information in Discoverer

B.1 Generating trace information in Discoverer

This chapter explains why you might want to generate trace information and how to do it, and contains the following topics:

• Section B.2, "About trace information"

• Section B.3, "How to generate trace information"

B.2 About trace information

Occasionally, you might want to look at exactly what operations the Discoverer Server is performing. For example, your Web server might not be responding, or Discoverer SQL queries might not be returning data. In these scenarios, you might generate trace information and save it in a log file so that you can diagnose problems.

B.3 How to generate trace information

To generate trace information into a log file:

1. Open the register session script file in a text editor.

   The name of this file depends on the operating system platform on which you are running the Discoverer Server, as follows:

   • on UNIX, open the registersession.sh file

   • on Windows, open the registersession.bat file

   To find out more about the location of these files, see Section A.2, "List of Discoverer file locations".

2. Add a logdir entry to the file using the following syntax:

   -logdir <directory> -loglevel <level>
   
   

   where:

   • <directory> is a directory in which the log file will be created

   • <level> is a number between 1 and 3, indicating the level of detail of information that will be saved in the log file (the higher the number, the more detailed the information that will be saved)

   For example, before the change a file might contain the following line:

   oadutil ... dis51ws.exe -a session -a MySession -a -preference -a 
   MyPreference ...
   
   

   After appending the logdir command, this might look like this:

   oadutil ... dis51ws.exe -a session -a MySession -a -preference -a 
   MyPreference -a -logdir -a C:\temp -a -loglevel -a 3 ...
   
   

   Note: If you omit the logdir argument, the log file is created in the current directory.

3. Unregister the session (for more information about unregistering sessions, see Section 6.6, "How to register and unregister the Discoverer Session component with the OAD").

4. Re-register the session (for more information about registering sessions, see Section 6.6, "How to register and unregister the Discoverer Session component with the OAD").

Notes:

• To stop the generation of trace information:
  1. Remove the logdir and loglevel parameters from the file containing the register session script.

  2. Unregister the session.

  3. Re-register the session.