test

Oracle Waveset 8.1.1 System Administrator's Guide

Chapter 6 Errors and Exceptions

This chapter describes the error and exception messages generated by Waveset.

The topics in this chapter include:

Before Working with Waveset Messages

Review the following information before you start working with Waveset error and exception messages:

Important Notes About Waveset Messages

Be sure to read the following information before you start working with Waveset error and exception messages:

Related Documentation and Web Sites

In addition to the information provided in this chapter, consult the documents and web sites listed in this section for information related to tuning Waveset for your deployment.

Recommended Reading

See the following documents for information related to Waveset error and exception messages:

Useful Web Sites

The following table describes some web sites you might find useful.

Table 6–1 Useful Web Sites

Web Site URL 

Description 

http://sharespace.sun.com/gm/document-1.26.2296

Waveset FAQ on Oracle’s Share Space 

Note: This space is only available to Oracle employees and Oracle partners. In addition, these individuals must have a Share Space ID to access the information on this site.

http://sunsolve.sun.com/

Web site containing diagnostic tools, forums, features and articles, security information, and patch contents 

Note: The information on this site is partitioned into three areas:

  • Internal. Oracle employees only

  • Contract. Available only to customers with contract access

  • Public. Available to everyone

About Waveset Errors and Exceptions

This section describes the Waveset error and exception message system and the components that can generate errors and exceptions.

The information is organized into the following sections:

Where Messages Are Stored

Error messages are stored as follows:

Note –

You can create a customized message catalog to add messages or to modify messages provided with the system.

See Chapter 9, Customizing Message Catalogs, in Oracle Waveset 8.1.1 Deployment Guide for instructions.

How Messages Are Displayed

For easy identification, Waveset displays page-level error and exception messages along the top of the page as boxed text with a unique error icon.

Figure 6–1 Example Login Authentication Error

Example error message.

Note –

In the Waveset messaging system, items displayed as {0} or {1} represent parameters that are supplied by code. For example:

The file is larger than the maximum supported length of
 {0} bytes.

In this exception, the code replaces the {0} with the parameter value representing the maximum number of bytes.

Error Severity Levels

Within Waveset, error severities are defined as follows:

Note –

You can check the Waveset System Log for more information about an error or exception message. (See Viewing Errors in the System Log Report.)

Viewing Errors in the System Log Report

System Log reports can provide information about errors generated by Waveset. The System Log report consists of the error’s timestamp, severity, server name, component name, error code or ID, stack trace (structure of the execution stack at that point in the program’s life), and error text information.

You can use Waveset’s Administrator interface or command-line interface to run and view System Log reports.

Note –

Instructions for creating and editing System Log reports are provided in Oracle Waveset 8.1.1 Business Administrator’s Guide.

ProcedureTo Run a System Log Report From the Administrator Interface

Perform the following steps to run a System Log report from the Administrator interface:

  1. Log in to the Waveset Administrator interface.

  2. Select Reports -> Run Reports to open the Run Reports page.

  3. Locate the appropriate System Log Report entry in the Report Type column, and then click the Run button in that same row.

    The Report Results page displays, listing the system messages that were reported during the specified interval. For example, Figure 6–2 depicts information about two system messages.

    Figure 6–2 Example Report Results Page

    Graphic showing an example Report Results page.

    The Report Results table shows the following information:

    • Timestamp. Shows the day, date, and time the error occurred.

      Click the Timestamp links to view detailed information about that System Log record. For example, if you clicked the first Timestamp link shown in Figure 6–2, the following information displays.

      Example showing details of a partial System Log Record.

    • Event. Identifies the syslog ID of the target entry (when applicable).

    • Severity. Shows the severity level of the error.

      Severity levels include

      • Fatal. A severe error that causes the system to crash, resulting in the loss or corruption of unsaved data.

      • Error. A severe error that might cause the loss or corruption of unsaved data. Immediate action must be taken to prevent losing data.

      • Warning. Action must be taken at some stage to prevent a severe error from occurring in the future.

      • Info. An informative message, usually describing server activity. No action is necessary.

    • Server. Identifies the server on which the error occurred.

    • Component. Identifies the system component that generated the error.

    • Error Code. Shows the error code associated with that error.

    • Message. Shows the actual error message text.

ProcedureTo Run a System Log Report From the Command-Line Interface

Note –

These instructions assume you are familiar with the Waveset command-line interface and lh commands. For more information, read Appendix A, lh Reference, in Oracle Waveset 8.1.1 Business Administrator’s Guide.

Perform the following steps to run and view a System Log report from the command line:

  1. Open a command window.

  2. Change directories to the default Waveset installation directory.

  3. At the prompt, type the lh syslog [options ] command.

    Use these options to include or exclude information:

    • -d: Number – Show records for the previous number of days (Default is 1.)

    • -F – Show only records with fatal severity level

    • -E – Show only records with an error severity level or higher

    • -i logid – Show only records with a specified Syslog ID

      Syslog IDs are displayed on some error messages and reference a specific System Log entry.

    • -W – Show only records with a warning severity level or higher (default)

    • -X – Include reported cause of error, if available

Customizing a Default Error Message

Note –

To add message catalog entries or to modify entries provided with the system, you must create a customized message catalog. See Chapter 9, Customizing Message Catalogs, in Oracle Waveset 8.1.1 Deployment Guide for instructions.

Waveset’s default error messages are stored in a WPMessages.properties file in the idmcommon.jar file and in an RAMessages.properties file in the idmadapter.jar.

The Waveset Service Provider’s default error messages are located in the IDMXMessages.properties file.

You can customize these default error messages by modifying attributes in the ErrorUIConfig object provided with that message.

ProcedureTo Modify the ErrorUIConfig Object:

  1. Log in to Waveset Administrator interface.

  2. Open the System Settings page by typing http:// host:port/idm/debug in to your browser.

  3. Locate the Type menu, located next to the List Objects button. Choose Configuration from the menu.

    Figure 6–3 List Objects Type Menu

    Graphic showing the List Objects Menu on the System Settings page.

  4. Click the List Objects button.

  5. On the List Objects of type: Configuration page, click the ErrorUIConfig edit link.

    The following example shows the XML for an ErrorUIConfig object on Checkout Object: Configuration page:


    <?xml version=’1.0’ encoding=’UTF-8’?>
<!DOCTYPE Configuration PUBLIC ’waveset.dtd’ ’waveset.dtd’>
<!--  MemberObjectGroups="#ID#Top" extensionClass="GenericObject" 
id="#ID#9787BA467E01441B:178655:1156195C008:-7FFE" 
lastModifier="com.waveset.object.ErrorUIConfig" name="ErrorUIConfig"-->
<Configuration id=’#ID#9787BA467E01441B:178655:1156195C008:-7FFE’ name=’ErrorUIConfig’ 
lock=’Configurator#1200600790328’ creator=’com.waveset.object.ErrorUIConfig’ 
createDate=’1191343145328’ lastModifier=’com.waveset.object.ErrorUIConfig’ 
lastModDate=’1191343145328’>
  <Extension>
    <Object>
      <Attribute name=’Enabled’>
        <Boolean>true</Boolean>
      </Attribute>
      <Attribute name=’ErrorMsgID’ value=’UI_ERROR_DEFAULT_FATAL_MESSAGE’/>

    </Object>
  </Extension>
  <MemberObjectGroups>
    <ObjectRef type=’ObjectGroup’ id=’#ID#Top’ name=’Top’/>
  </MemberObjectGroups>
</Configuration>

  6. Modify the ErrorUIConfig object attributes as needed.

    You can modify any of the following attributes:

    • Enabled. Controls whether the message is enabled (true) or disabled (false).

      Note –

      The ability to disable this attribute is provided for backward-compatibility; however, disabling this attribute will result in cryptic messages and you will not see the typical extended messages in the System Log.

    • ErrorMsgID. Identifies the error message to be displayed.

      Change the ErrorMsgID attribute value to provide the message text you want displayed.

      The current setting for this attribute is as follows, and it references the UI_ERROR_DEFAULT_FATAL_MESSAGE message in the message catalog:


      <Attribute name=’ErrorMsgID’ value=’UI_ERROR_DEFAULT_FATAL_MESSAGE’/>
      Note –

      If you are using parameterized messages with single or double quotes in the message, you must use an additional single or double quote to escape the message. (You will see only one quote symbol when the message is output to the system.)

      For example, the following message begins and ends with two single quote marks:


      ”’{0}’’

  7. When you are finished, click Save to save your changes.

    Note –

    If you have difficulty creating a default error message, contact your Administrator or Administrator hotline.