This chapter covers the following topics:
This chapter presents the following topics:
To utilize some Oracle Configurator Developer functionality or access a runtime Oracle Configurator from other Oracle Applications such as Order Management, you must set some profile options. See the Oracle Configurator Installation Guide for information about Oracle Configurator Developer profile options.
Multiple Language Support (MLS) enables you to create a Model and one or more user interfaces in your base language and then display the runtime UI in any language in which you do business. For more information on MLS see the Oracle Configurator Developer User’s Guide and Multiple Language Support.
For background on the relationship of Oracle Configurator Developer to the Oracle Configurator architecture, see Configurator Architecture.
Access to specific Configurator Developer functions, such as creating Model structure, defining rules, and generating a User Interface, is controlled by the responsibility to which each Oracle Applications user is assigned. For example, a responsibility may enable user CTHOMAS to generate UIs, but not allow that user to define or modify rules.
For more information about Oracle Applications responsibilities and function security, see the Oracle E-Business Suite System Administrator’s Guide.
To set up access to Oracle Configurator Developer, your System Administrator must:
Define Oracle Configurator Developer users in Oracle Applications.
For details, see the Oracle E-Business Suite System Administrator’s Guide.
Assign at least one of the predefined Configurator Developer responsibilities listed in The Predefined Configurator Developer Responsibilities to each Oracle Configurator Developer user.
The following table describes the predefined Oracle Configurator Developer responsibilities.
|Configurator Administrator||Access to all forms-based Oracle Configurator related concurrent programs. For more information on concurrent programs, see Concurrent Programs.|
|Configurator Developer||Access to some forms-based Oracle Configurator related concurrent programs. For more information on concurrent programs, see Concurrent Programs.|
|Oracle Configurator Administrator||Can create, edit, and delete the same objects as the Configurator Developer responsibility (see below).|
Can create, import, migrate, refresh, publish, synchronize, and populate Models.
Has access to all HTML-based Oracle Configurator related concurrent programs. For more information on concurrent programs, see Configurator Administration Concurrent Programs for more information.
|Oracle Configurator Developer||Unrestricted read-only access to all objects (including Model structure, rules, User Interfaces, UI Templates, and so on).|
Can create, edit, and delete the following: Folders, Model structure; rules and rule folders; Properties; Items and Item Types; Usages; Effectivity Sets; UI Templates; User Interfaces.
Can create, import, refresh, publish, and populate Models.
Has access to some HTML-based Oracle Configurator related concurrent programs. For more information on concurrent programs, see Concurrent Programs.
|Oracle Configurator Viewer||Unrestricted read-only access to all objects (including Model structure, rules, User Interfaces, UI Templates, and so on).|
Cannot modify any objects.
Warning: Oracle strongly recommends that you do not modify the predefined Oracle Configurator Developer responsibilities. If you need to provide access to a different combination of menus and functions, then define new responsibilities in Oracle Applications. For information about defining responsibilities, see the Oracle E-Business Suite System Administrator’s Guide.
Oracle Configurator Developer provides an intuitive and powerful environment for the creation and maintenance of configuration models.
Using Oracle Configurator Developer, the developer makes modifications to a Model (structure, rules, UI definitions). These modifications of the model data are committed to the Oracle Applications database server. This is shown as the Model development environment in Three tier Architectural Overview of Oracle Configurator Developer.
After making modifications to the Model, the Model can be tested in either the runtime Oracle Configurator or the Model Debugger. For more information see the Oracle Configurator Developer User’s Guide.
The unit-testing configuration data is committed to the database, after the developer clicks Apply or Finish.
All Oracle Configurator runtime database commits are through JDBC. When the end user closed the Configurator window, the resulting configuration data is saved directly to the database.
To test the configuration model, there are certain objects that must be in place:
In order for Functional Companions to run, you must have access to Java classes. For more information, see the Oracle Configurator Developer User’s Guide.
OC Servlet must be restarted if you add or modify the Java class for a Configurator Extension.
Open a new configuration session in a new browser window by going to the Model’s Utility page to view any Model, rules, or UI changes.
Check that the OC Servlet is running and what version of the runtime Oracle Configurator software is being used. Enter the following URL in a browser using the specific local settings for host and port where the OC Servlet is installed:
For more information about the runtime Oracle Configurator and Oracle Configurator Developer, see Configurator Architecture.