4 Installing the Application Files

Enterprise DQ for Product R12 PIM Connector includes a set of application components that the users use to process data. These include a set of DSAs, Governance Studio Projects, and AutoBuild application templates. Each of these is described in this chapter.

R12 PIM Connector Application Server Template Files

The R12 PIM Connector Application Server Template Files are a collection of DSAs that must be present on your Oracle DataLens Server to process your data.

Configure your Oracle DataLens Server to use the Application Server Template files with one of the following sections:

Files Do Not Exist on Server: Use "Installing the R12 PIM Connector Application Server Template Files".
Files Exist on Server: Use "Updating the R12 PIM Connector Application Server Template Files".

Installing the R12 PIM Connector Application Server Template Files

Install the R12 PIM Connector application server template files:

On your Oracle DataLens Administration Server system, log in using the administrator user you established when installing the server in preparation to copy files.

Note:
This step does not refer to the Oracle DataLens Administration Server Web page.
Copy the edqp_server_templates.zip file that you extracted from the patch set to the local directory of your Oracle DataLens Administration Server. By default, these directories are:

On Linux and UNIX: /opt/Oracle/Middleware/opdq/local

On Windows: C:\Oracle\Middleware\opdq\local

Note:
The preceding directories are the defaults when installing your Oracle DataLens Server; your installation directory may vary.
Change directories to the local directory of your Oracle DataLens Administration Server.
Unzip the edqp_server_templates.zip file.

This automatically deploys (autodeploys) the DSA and data lens template files to your Oracle DataLens Server. The Oracle DataLens Administration Server polls the local directory every 10 minutes and attempts to autodeploy the DSA and data lens template files that are placed in the respective folders under the autodeploy parent folder.
Log out of the Oracle DataLens Administration Server system.
Wait 10 minutes to ensure that the server templates have been autodeployed.
Log into the Oracle DataLens Server Administration Web page.

For more information about these Web pages, see Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide.
Verify that the AUPIM_ DSAs and AUPIM_Capacitors.project data lens have been autodeployed.

Updating the R12 PIM Connector Application Server Template Files

You can update previously installed R12 PIM Connector application server template files using the following steps:

Log into the Oracle DataLens Server Administration Web page.

For more information about these Web pages, see Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide.
In the Server section, click Data Lenses.
Unlock the AUPIM_Capacitors.project data lens.
In the Server section, click DSAs.
Unlock any locked DSA that is prefixed with AUPIM_.
On your Oracle DataLens Administration Server system, log in using the administrator user you established when installing the server in preparation to copy files.

Note:
This step does not refer to the Oracle DataLens Administration Server Web page.
Copy the edqp_server_templates.zip file that you extracted from the patch set to the local directory of your Oracle DataLens Administration Server. By default, these directories are:

On Linux and UNIX: /opt/Oracle/Middleware/opdq/local

On Windows: C:\Oracle\Middleware\opdq\local

Note:
The preceding directories are the defaults when installing your Oracle DataLens Server; your installation directory may vary.
Change directories to the local directory of your Oracle DataLens Administration Server.
Unzip the edqp_server_templates.zip file.

This automatically deploys (autodeploys) the DSA and data lens template files to your Oracle DataLens Server. The Oracle DataLens Administration Server polls the local directory every 10 minutes and attempts to autodeploy the DSA and data lens template files that are placed in the respective folders under the autodeploy parent folder.
Log out of the Oracle DataLens Administration Server system.
Wait 10 minutes to ensure that the server templates have been autodeployed.
Return to your Oracle DataLens Server Administration Web page.
Verify that the DSAs prefixed with AUPIM_ and the AUPIM_Capacitors.project data lens have been autodeployed.

Installing the R12 PIM Connector Application Client Template Files

Install the R12 PIM Connector application client template files:

On your Enterprise DQ for Product client system, copy the edqp_client_templates.zip file from the temporary directory where you unzipped the R12 PIM Connector patch file to your Desktop.
Unzip the edqp_client_templates.zip file to your Desktop.

The preconfigured AutoBuild Excel workbook in the spreadsheet_templates folder. For more information about these workbook, see "Preconfigured Excel Spreadsheet Template".

The preconfigured Governance Studio projects are in the gov_studio_projects folder.
Start the Governance Studio and import each project file (*.ams) in the .../desktop/edqp_client_templates/gov_studio_projects directory.

For more information about importing, see Oracle Enterprise Data Quality for Product Data Governance Studio Reference Guide. For more information about these projects, see "Preconfigured Governance Studio Projects".
Start the Knowledge Studio and check out the DLS_Import_Template data lens.

Note:
Before using the AutoBuild application, delivered in Services for Excel, the DLS_Import_Template data lens must be checked out from the Oracle DataLens Server. For information about checking data lenses in and out of the Enterprise DQ for Product, see Oracle Enterprise Data Quality for Product Data Knowledge Studio Reference Guide.

Enterprise DQ for Product DSA Overview

There are four main categories of DSAs that define the architecture of Enterprise DQ for Product.

Metadata Import
- Semantic Model build from PIM metadata extract.
- Alternate Catalog build from PIM metadata extract.
Creating and updated the semantic cache information that is used by the integration services to perform semantic matches.
Creating a new batch from a query of Production data.
Processing interface table batches thorough the Integration Services DSA and updating the results back in the interface tables.

Default Entries in DSAs

All DSAs shipped as part of the Enterprise DQ for Product R12 PIM Connector have default entries that allow for a quick configuration. The following default entries will need to be reviewed and configuration changes may be required. These changes are outlined in the Oracle Enterprise Data Quality for Product Data R12 PIM Connector User's Guide.

Default Database Connection: The default database connection name for all DSAs is, PIM_Connector. This database connection will be pointing to a fictitious server name with a fictitious user and password that will need to be configured as part of the initial server configuration.
Default Data Lens: The default data lens for all DSAs that process items in Enterprise DQ for Product is AUPIM_Capacitors.project. This data lens contains semantic models that work with the Capacitors Item Class category in the Vision Database installed with most R12 PIM Connector systems. A process of testing the system using this sample lens and then updating this data lens with actual customer specific data lenses is documented in Enterprise DQ for Product.

Creating and Updating Semantic Models from PIM Metadata Import

AUPIM_CREATE_SEMANTIC_MODEL: This DSA is used by AutoBuild to generate data lenses from the PIM metadata. This DSA is typically run using the Enterprise DQ for Product Services for Excel to create the data needed by the AutoBuild application. This data includes attributes and sample descriptions.

Importing Alternate Catalog Metadata

AUPIM_EXTRACT_ALT_CATALOGS: This DSA is used by the AutoBuild application to import one or more alternate catalogs and create classification schemas inside a selected data lens. This DSA is typically run using the Services for Excel to create the data needed by the AutoBuild application. This data includes the metadata for the Alternate Catalog entered during the run including the id and parent information.

Creating and Updating the Semantic Cache

AUPIM_CREATE_SEMANTIC_CACHE: This DSA is run as a nightly job to update the Semantic Index from Oracle PIM Production data; this semantic index is used for matching and checking for duplicates.

Creating Production Batches

Oracle PIM System users will be able to process data from the interface tables where the source system is an external source system or where the source system is the PIM Data Hub. In order to process data from external source systems, the PIM users will continue to use the existing methods of loading data into the interface tables, usually the Excel Import Templates or a direct database load. The PIM users will also have a new feature to load data directly from PIM Production tables into the interface tables using a batch creation process that is included in this application.

AUPIM_PROCESS_EXTERNAL_DATA: This DSA is run to insert your external data into interface tables by the Oracle DataLens Server.
AUPIM_CREATE_PRODUCTION_BATCH: This DSA is run to create a new batch of data from the PIM Production tables. This batch will then be processed by the Oracle DataLens Server and updated back into interface tables.

Processing a Batch of Data Thorough the Cleansing and Matching Process

AUPIM_MAIN_PROCESS: This DSA is run as the main DSA from the DGS. This will take an Oracle PIM batch and clean/standardize/classify/extract attrs/etc from the description and load it into the DGS for further processing. The batches are populated with data from external systems or as pulls from the PIM Production data.

Secondary Data Service Applications for Reprocess and Apply

Secondary DSAs called by the main process as previously described that Reprocess or Apply the changes to the interface table.

DSA Name	Notes
`AUPIM_REPROCESS`	Reprocesses rows from the following outputs of the Main Process DSA: Dups within Batch Match on Mfg Part Match Against PIM Items for Enrichment Exceptions Based on specific process flags, this DSA will reroute the items back to the Governance Studio Main project, or will update the rows back in the interface tables with the correct match_status.
`AUPIM_APPLY_RESULTS`	Applies rows from the Ready for Load step and updates all pertinent fields in the interface tables.
`AUPIM_EXTRACT_ALT_CATALOGS`	Applies rows from the Alternate Catalog Review and updates all pertinent fields related to Alternate Catalogs
`AUPIM_SET_BATCH_TO_ACTIVE`	Updated the batch status from Pending to Active so that the PIM user can go into the Import Workbench UI and invoke the import process.

Preconfigured Governance Studio Projects

Enterprise DQ for Product R12 PIM Connector includes the following Governance Studio project. This project is used by users to create batch specific Governance Studio projects to process interface batch data. The process is documented in the Oracle Enterprise Data Quality for Product Data R12 PIM Connector User's Guide.

AUPIM_Cleansing_and_Matching: The main process that runs the main Data Service Applications that cleanse and match the items in the interface tables.
AUPIM_Create_Production_Batch: The process that automatically creates a new Import Workbench batch from a set of production items.
AUPIM_CREATE_SEMANTIC_CACHE: This administrative process can be run thorough the Governance Studio or can be scheduled to run as a nightly or weekly process. This should be run by System Administrators when not batches are being processed.

For information about how these project templates are used, see Oracle Enterprise Data Quality for Product Data R12 PIM Connector User's Guide.

Preconfigured Excel Spreadsheet Template

The Enterprise DQ for Product R12 PIM Connector includes the following Excel workbook for use with the AutoBuild application. This preconfigured workbook contain VBA applications that are used to export PIM metadata and to create a set of semantic models with one or more associated alternate catalogs for use in cleansing and matching your specific product data.

CapacitorsExternalBatchTestInput.xlsx: Use this workbook to test your input data prior to executing a PIM external batch load.

For information about how the AutoBuild templates are used to create a data lens and add an alternate catalog to the data lens, see Oracle Enterprise Data Quality for Product Data R12 PIM Connector User's Guide.