|Oracle® Enterprise Data Quality for Product Data R12 PIM Connector Installation Guide
Release 11g R1 (18.104.22.168)
Part Number E29141-02
|PDF · Mobi · ePub|
The R12 PIM ConnectorApplication Server sample files are a collection of DSAs that are delivered with EDQP so that you can install them on your Oracle DataLens Server as an example of how you could process your data, using the R12 PIM sample data. These include a set of DSAs, Governance Studio Projects, and AutoBuild application samples. Each of these is described in this chapter.
The R12 PIM Connector Application Server sample files are a collection of DSAs that are delivered with EDQP so that you can install them on your Oracle DataLens Server to see how you could process your data.
Install the R12 PIM Connector application server sample 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.
\edqp_template1\autodeploy directory that you extracted from the product package to the WebLogic
dls_domain directory on your Oracle DataLens Administration Server. By default, these directories are:
On Linux and UNIX:
Note:The preceding directories are the defaults when installing your Oracle DataLens Server; your installation directory may vary.
This automatically deploys (autodeploys) the DSA sample files to your Oracle DataLens Server. The Oracle DataLens Administration Server polls the
autodeploy directory every 10 minutes and attempts to autodeploy the DSA sample files that are placed in the
autodeploy parent folder.
Log out of the Oracle DataLens Administration Server system.
Wait 10 minutes to ensure that the server samples 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.
Install the R12 PIM Connector application client sample files:
On your Enterprise DQ for Product client system, copy the
pdqcms_application_templates folder from the directory on the server where you unzipped the product package to your client Desktop. By default, these directories are:
On Linux and UNIX:
The preconfigured AutoBuild Excel workbook in the
spreadsheet_templates folder. For more information about these workbook, see "Preconfigured Excel Spreadsheet Sample".
The preconfigured Governance Studio projects are in the
Start the Governance Studio and import each project file (
*.ams) in the
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_Templatedata 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.
There are four main categories of samples DSAs that illustrate the overall integration capabilities between the R12 PIM Connector and PIM.
Semantic Model build from PIM metadata extract.
Alternate Catalog build from PIM metadata extract.
Creating and updating 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.
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.
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.
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.
This DSA retrieves the semantic model metadata for a given ICC from the PIM system. AutoBuild uses this semantic model metadata to build a data lens that as a starting point for the cleansing and enrichment process. 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.
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.
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.
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 samples 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.
This DSA is run to insert your external data into interface tables by the Oracle DataLens Server.
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.
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 DSAs called by the main process as previously described that Reprocess or Apply the changes to the interface table.
||Reprocesses rows from the following outputs of the Main Process DSA:
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.
||Applies rows from the Ready for Load step and updates all pertinent fields in the interface tables.|
||Applies rows from the Alternate Catalog Review and updates all pertinent fields related to Alternate Catalogs|
||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.|
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.
The main process that runs the main Data Service Applications that cleanse and match the items in the interface tables.
The process that automatically creates a new Import Workbench batch from a set of production items.
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 samples are used, see Oracle Enterprise Data Quality for Product Data R12 PIM Connector User's Guide.
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.
Use this workbook to test your input data prior to executing a PIM external batch load.
For information about how the AutoBuild sample workbook is 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.