Skip Headers

Oracle Configurator Implementation Guide
Release 12.1 for
Part Number E14322-03
Go to Table of Contents
Go to previous page
Go to next page

Implementation Tasks

This chapter presents an overview of all known tasks in an Oracle Configurator implementation, including custom tasks.

This chapter covers the following topics:


This chapter provides an overview of tasks performed prior to implementing Oracle Configurator. The list of tasks is organized into the following categories:

General Implementation Tasks

General implementation tasks are the initial tasks that set up an environment and enable the implementer to begin working with Oracle Configurator Developer.

Database Tasks

Database tasks are the tasks that set up and support the development and deployment of the CZ schema.

Required Database Tasks

These tasks must be performed to set up and support development and deployment of a runtime Oracle Configurator.

Optional Database Tasks

Optional tasks for providing additional flexibility in your Oracle Configurator implementation include:

Integration Tasks

Integration tasks enable Oracle Configurator to work with a particular host application.

Required Tasks for All Integrations

These tasks must be performed for all integrations of Oracle Configurator with a host application.

Optional Integration Tasks

These tasks provide additional aspects of integration between Oracle Configurator and a host application, and apply to both custom and predefined integrations.

Tasks for Custom Integration

These tasks (in addition to the required tasks listed in Required Tasks for All Integrations) must be performed if you are integrating Oracle Configurator with a custom host application. A custom host application is one that does not provide any predefined integration with Oracle Configurator.

Model Development Tasks

Model development tasks enable you to extend a BOM Model by adding additional structure, rules, UIs, and publishing your configuration model to a host application.

Required Tasks for Model Development

These tasks must be performed so that you can create Models or add additional structure, rules, and UIs to BOM Models.

Optional Tasks for Model Development

The following tasks can be performed to provide additional Model functionality.

Deployment Tasks

Deployment involves making a runtime Oracle Configurator available to end users. The following tasks complete the deployment of a runtime Oracle Configurator either embedded in a host Oracle Application or in a custom host application.

Required Tasks for All Deployments

The following tasks are required for the runtime Oracle Configurator to use the currently supported user interfaces. (As of this release, DHTML UIs are no longer supported.)

Optional Tasks for Deployment

These tasks can be performed to maximize performance, usability, and functionality when your configuration model is deployed to end users.

Tasks for Custom Deployments

If you are implementing a custom deployment, then consider the following:


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

The table below lists other conventions that are also used in this guide.

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 per cent 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.
& Indicates a character string (identifier) that can display text dynamically in Configurator Developer or a runtime Oracle Configurator. For example, "&PROPERTY" can be used to dynamically construct and display a Property of a Model structure node.

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:

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:


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 more information about logging, see: