Skip Headers
Oracle® Database Lite Administration and Deployment Guide
10g (10.0.0)
Part No. B12262-01
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

11 Tracing

This document enables the Mobile Server Administrator to set tracing parameters. Topics include:

11.1 Overview

The Mobile Server enables the Administrator to turn the trace feature on and off as required and change the server's trace configuration, while the server is running. Based on the required trace output type, the Mobile Server administrator can choose a trace output destination.

When the Mobile Server is running in standalone mode, the Console option generates trace output to the Console window only, with the -d0 command line option on. If you set this parameter to the option -d0, the trace output automatically appears on your console screen. Using the -d0 option with this parameter overrides trace settings for other trace parameters, such as destination and level, in the webtogo.ora file. The -d0 setting enforces the trace output to appear on your console screen instead of appearing in a file.

To generate trace output to a file, the Administrator can choose the File option. When required, the Administrator can also generate trace output to a remote machine. Trace output can then be viewed using the wsh -m% utility and the corresponding remote trace parameter. Applying changes that are associated with remote trace support automatically launch wsh -m%TRACE_REMOTE_PORT% in the console window. If the port number changes when a wsh -m process is running, the previous process is terminated immediately.

If you specify a valid value for the trace destination, the specified destination is used. If the necessary parameters for the specified destination are missing, then the default value for such parameters are applied to ensure that the trace output is generated to the default destination. If the default value for the specified parameter is missing, the default trace destination is automatically chosen, depending on the mode of the Mobile Server.

For more information on Mobile Server modes, see Section 11.2.1, "Mobile Server Modes".

For a description of the Tracing parameters and information on how to set them, see Appendix B, "Mobile Server Configuration Parameters".

11.2 Setting Trace Parameters

To set trace parameters, perform the following steps.

  1. Login to the Mobile Server and click the Mobile Manager link in the workspace. The Mobile Server farms page appears. Click the following links. Your Mobile Server -> Administration -> Trace Setting. As Figure 11-1 displays, the Trace Settings page appears.

    Figure 11-1 Trace Settings Page

    This image displays the Trace Settings page.

    Using the Trace Settings page, you can choose to generate trace output, specify the trace output destination to the local console, file or remote machine. The Trace Settings page provides system and user filters to generate trace output to the required system level and choose users that require the trace output generation utility.

  2. As Table 11-1 describes, enter data in the Trace Settings page.

    Table 11-1 Trace Settings Page Description

    Field Description
    Trace Output To generate trace output, click this box and choose Yes.
    Console To specify the local console as the trace output destination, select this option.
    File To specify the trace output file (error.log) as the trace output destination, select this option.

    If selected, enter the Trace Base File Name, Trace File Size (in MB), and Trace File Pool Size in the corresponding fields. To create a trace file for every user, click the Create Trace File for Every User box and choose Yes. The Trace Settings page displays default values for these fields.

    Remote To specify trace output to a remote destination, select this option.

    If selected, enter the Trace Monitor Host name and Trace Monitor Port number in the corresponding fields.

    For more information on Mobile Server modes, available trace destinations, and default trace destinations, refer Section 11.2.1, "Mobile Server Modes".

    HTTP Request To generate HTTP output and webtogo trace information as trace output, select this option.
    SQL Statements To generate Consolidator's SQL queries as trace output, select this option.
    Java Methods To generate all system.out output from the Mobile Server and Consolidator's Java methods, select this option.

    Note: The Mobile Server automatically filters exceptions and errors as trace output to a Mandatory level. Mandatory trace output is automatically generated, only when the trace feature is turned on.

    All Users To generate trace output for all users, select this option.
    No Users If selected, does not generate trace output for users.
    Selected Users To generate trace output for specified user names only, select this option. In the Selective Users field, enter comma separated user names. For example, arnold, john, jack.

  3. Click the Apply button.

11.2.1 Mobile Server Modes

Table 11-2 lists all Mobile Server modes, the available trace destinations, and the corresponding default trace destinations.

Table 11-2 Trace Destinations for Mobile Server Modes

Mobile Server Mode -d0 Option Available Trace Destinations Default Trace Destination
Standalone Overrides webtogo.ora setting Console, File, Remote Console
NT Service N/A File, Remote File
Oracle9iAS
N/A File, Remote File

11.3 Editing the webtogo.ora File

To edit the webtogo.ora file, navigate to the Administration page and click the Edit Config File link. As Figure 11-2 displays, the Edit Configuration File webtogo.ora page appears.

Figure 11-2 Edit Configuration File webtogo.ora Page

Edit Configuration File webtogo.ora page.

Edit the webtogo.ora file in the required areas and click Apply.

Using the webtogo.ora File or Command Line -d Option

To specify the required trace output level, the administrator can optionally use the Mobile Server or the webtogo.ora file or the Command Line -d option. The administrator must specify a number that represents all the levels filtered in, as the number is a Bitwise OR operation of the chosen levels. To display trace output for all three levels, you must use 1|2|4=7. To be compatible backward, you must use the value 0 instead of the value 7, which hides all trace output.

If you set this parameter to the option -d0, the trace output appears on your console screen without appearing in a file, because using the -d0 option with this parameter overrides the trace settings for other trace parameters, such as destination and level, in the webtogo.ora file. The -d0 setting enforces the trace output to appear on your console screen instead of appearing in a file.

For more information on Mobile Server configuration parameters, see Appendix B, "Mobile Server Configuration Parameters".

11.4 Running the Mobile Server in Debug Mode

This document enables the Mobile Server Administrator to debug the Mobile Server and generate debugging output.

To run the Mobile Server in debug mode, perform the following steps.

  1. Open the file webtogo.ora from the following location.

    mobile\server\bin

  2. Locate the following parameters and change their existing values as given below.

    1. TRACE_ENABLE=Yes

    2. TRACE_DESTINATION=FILE

    3. TRACE_FILE_NAME=trace.log


      Note:

      Debugging output is not generated when you set the Trace Destination value to Console.

The following log files can be used to debug problems while running applications in OC4J.

  1. Use this log file to view OC4J server level output messages.

    <OC4J_HOME>\log\server.log

  2. Use this log file to view HTTP requests handled by the server.

    <OC4J_HOME>\log\http-web-access.log

  3. Use this log file to view exceptions or errors that are handled by OC4J.

    <OC4J_HOME>\application-deployments\webtogo\application.log

  4. Use this log file to view the file trace_sys1.log and other log files that are generated by the Mobile Server in the same directory.

    <OC4J>_HOME>\application-deployments\webtogo\trace_sys1.log


    Note:

    All output generated by the parameter JupDebug in the Mobile Server is recorded in the above listed log files.