Common Tasks

This appendix describes certain tasks that may be required while implementing an Oracle Configurator.

This appendix covers the following topics:

Overview
Running Configurator Concurrent Programs
Connecting to a Database Instance
Verifying CZ Schema Version
Server Administration
Viewing the Status of Configurator Concurrent Requests
Viewing Log Files
Managing Oracle Configurator Caching
Checking BOM Model and Configuration Model Similarity

Overview

This appendix describes common tasks of an Oracle Configurator implementation:

For details about specific Oracle Configurator concurrent programs, see Concurrent Programs.

Running Configurator Concurrent Programs

To run any Oracle Configurator concurrent programs, you must log in to Oracle Applications and select one of the predefined Oracle Configurator responsibilities. For details about these responsibilities, including to which concurrent programs they provide access, see The Predefined Configurator Developer Responsibilities. For information about assigning responsibilities, see the Oracle E-Business Suite System Administrator’s Guide.

The procedure for running concurrent programs is provided in the Oracle E-Business Suite User Guide.

For details about specific Oracle Configurator concurrent programs, see Concurrent Programs.

Connecting to a Database Instance

Some implementation tasks must be performed using SQL*Plus while connected to a specific database instance. For example, during data migration you must connect to your source database instance prior to running a SQL script that sets up the migration packages, database link, and appropriate log file.

Note: Connecting to a database instance using SQL*Plus is not to be confused with starting and logging on to Oracle Applications. For information on logging on to Oracle Applications, see the Oracle Application User’s Guide.

To connect to a specific database, you must specify a user or schema and the instance in which it is defined. For example:

Connect to your CZ schema by connecting to the database instance as a user of the schema.
```
Example:
SQL> connect oc/ocpass@appssid
```
where oc is the owner (DBOwner) of the CZ schema, and ocpass is the owner’s password, and appssid is the name for the database instance.

Alternatively, connect to the database instance as a user with DBA privileges:
```
Example:
SQL> connect dba/dbapass@appssid
```

Verifying CZ Schema Version

You can determine the version information of an CZ schema by either running the View Configurator Parameters concurrent program or by querying the CZ_DB_SETTINGS table as follows:

Connect to the database instance in which you need to know the version information of the CZ schema.

Use SQL*Plus to enter the following query:

SQL> select setting_id, value, desc_text 
from cz_db_settings 
where setting_id like ’%_VERSION"

Querying the version of Release 12 available with the publication of this book results in MAJOR_VERSION = 27, MINOR_VERSION = a.

These values will vary depending on the latest installed version. To determine which version of the limited edition of Oracle Configurator Developer goes with which version of Oracle Configurator, refer to the Oracle Configurator Patch Matrix (Doc ID 131088.1) on MetaLink.

For information about MAJOR_VERSION, MINOR_VERSION, and other CZ_DB_SETTINGS parameters, see CZ_DB_SETTINGS Table.

Server Administration

If you are using separate database instances you need to define, enable, and possibly modify the remote server. Defining and enabling a remote server establishes the database link for:

Importing data (see Populating the CZ Schema)
Publishing configuration models (see Publishing Configuration Models)

Oracle Configurator provides the following Server Administration concurrent programs for the Oracle Configurator Administrator responsibility in Oracle Applications:

For details on running these concurrent programs, see Server Administration Concurrent Programs.

Viewing the Status of Configurator Concurrent Requests

Any Oracle Applications reportor program that you submit is sent to the concurrent manager and is stored in a queue with other requests until it is selected for processing. You can view the status of your concurrent requests by selecting Concurrent Programs > View from the Oracle Application Navigator window. The Requests page displays the Name, Status, Phase, Scheduled Date, Request ID and other details about your requests. To view the log file for a completed concurrent program, click the icon in the Details column, and then click View Log.

For additional information, see the Oracle Application User’s Guide.

Viewing Log Files

Log files contain error and warning messages that result from running a concurrent program or a SQL script. For information about the location of log files generated when running scripts, see Oracle Configurator Installation Guide. For information about viewing log files that result from running a concurrent program, see Viewing the Status of Configurator Concurrent Requests. See Publishing Error when Checking BOM Model and Configuration Model for an illustration of an error found in CZ_DB_LOGS.

Managing Oracle Configurator Caching

Oracle Applications Java Caching Framework (OAJCF) is the caching mechanism for all Oracle Applications products. OAJCF provides the ability to manage the caching and decaching of Model and UI data thereby improving performance of a runtime Oracle Configurator. For more information, see the Oracle Configurator Performance Guide.

Checking BOM Model and Configuration Model Similarity

See Synchronizing BOM Model Data for more information on checking the similarity between the configuration model and the original BOM Model.