Introduction

This chapter covers the following topics:

Scope of this Guide

This book contains a table of contents, examples, tables, figures, a reader comment form, a preface, several chapters, a glossary, and an index.

Conventions

In code examples, an implied carriage return occurs at the end of each line, unless otherwise noted. You must press the Enter key at the end of a line of input.

In rule examples, the order in which the rules are presented does not indicate a sequence in which Oracle Configurator processes the rules. You cannot assume a particular sequence, and the sequence can differ each time the rules are processed by the Oracle Configurator engine.

The following conventions are also used in this manual:

Convention Meaning
.
.
.
Vertical ellipsis points in an example mean that information not directly related to the example has been omitted.
... Horizontal ellipsis points in statements or commands mean that parts of the statement or command not directly related to the example have been omitted.
boldface text Boldface type in text indicates a new term, a term defined in the glossary, specific keys, and labels of user interface objects. Boldface type also indicates a menu, command, or option, especially within procedures.
italics Italic type in text, tables, or code examples indicates user-supplied text. Replace these placeholders with a specific value or string.
[ ] Brackets enclose optional clauses from which you can choose one or none.
> The left bracket alone represents the MS DOS prompt.
$ The dollar sign represents the DIGITAL Command Language prompt in Windows and the Bourne shell prompt in Digital UNIX.
% The percent sign alone represents the UNIX prompt.
name( ) In text other than code examples, the names of programming language methods and functions are shown with trailing parentheses. The parentheses are always shown as empty. For the actual argument or parameter list, see the reference documentation. This convention is not used in code examples.

Product Support

The mission of the Oracle Support Services organization is to help you resolve any issues or questions that you have regarding Oracle Configurator Developer and Oracle Configurator.

To report issues that are not mission-critical, submit a Technical Assistance Request (TAR) using Metalink, Oracle’s technical support Web site at:

http://www.oracle.com/support/metalink/

Log into your Metalink account and navigate to the Configurator TAR template:

  1. Choose the TARs link in the left menu.

  2. Click on Create a TAR.

  3. Fill in or choose a profile.

  4. In the same form:

    1. Choose Product: Oracle Configurator or Oracle Configurator Developer

    2. Choose Type of Problem: Oracle Configurator Generic Issue template

  5. Provide the information requested in the iTAR template.

You can also find product-specific documentation and other useful information using Metalink. For a complete listing of available Oracle Support Services and phone numbers, see:

www.oracle.com/support/

Troubleshooting

Oracle Configurator Developer and Oracle Configurator use the standard Oracle Applications methods of logging to analyze and debug both development and runtime issues. These methods include setting various profile options and Java system properties to enable logging and specify the desired level of detail you want to record.

For general information about the logging options available when working in Configurator Developer, see the Oracle Configurator Developer User’s Guide.

For details about the logging methods available in Configurator Developer and a runtime Oracle Configurator, see: