- EDQ SIEBEL INTEGRATION GUIDE DRIVER
- EDQ SIEBEL INTEGRATION GUIDE FULL
- EDQ SIEBEL INTEGRATION GUIDE SERIES
ODI 11g in the Enterprise Part 3: Data Quality and Data Profiling using Oracle EDQ.ODI11g in the Enterprise Part 2 : Data Integration using Essbase, Messaging, and Big Data Sources and Targets.ODI11g in the Enterprise Part 1: Beyond Data Warehouse Table Loading.Here's a quick recap of the links to those postings, and the remaining two in the series. In yesterday's posting we saw how recent extensions to ODI 11g have now given it the ability to connect to Hadoop clusters and run MapReduce jobs via Apache Hive, and how it can make use of the new Oracle Loader for Hadoop connector to move data out of Hadoop and into the data warehouse "proper".
EDQ SIEBEL INTEGRATION GUIDE SERIES
EDQ then runs a batch job on these records and when matching occurs the matches are written back to the shared staging database, which Siebel picks up and uses to link records together.In this special Christmas Break series of postings on Oracle Data Integrator 11g, we've been looking at how ODI has moved beyond being just a relational data movement tool to one that can connect to multi-dimensional databases such as Oracle Essbase, or perform a bulk-data movement role within an Oracle Fusion Middleware-based SOA environment.
EDQ SIEBEL INTEGRATION GUIDE DRIVER
In this case, the driver and candidate records for matching or health checks are written to the shared staging database.
EDQ SIEBEL INTEGRATION GUIDE FULL
The EDQ real-time interface is also used for batch cleansing (standardization) tasks: Siebel sends each record selected for batch processing to the EDQ cleansing web services.īatch duplicate identification and data quality health check jobs (either Full Batch or Incremental Batch) use the EDQ batch interface.
When records are added or updated in Siebel CRM, the EDQ real-time interface is used to standardize the data, and then match it against existing data. Measure the quality of account, contact, prospect, and address data on both an ad-hoc, and a regular basisĪs Siebel CRM has only a single set of data to manage, EDQ deployment is simple. Perform batch duplicate identification and cleansing tasks Standardize account, contact, prospect, and address data as it is entered or updated in the system Prevent duplicate contacts, account and prospect records from being added to the system by automatically matching all new and updated records against the other records in the system For batch jobs, EDQ jobs are called from the Siebel Data Quality Manager and a shared staging database is used to pass data between Siebel and EDQ.ĮDQ can be deployed to protect and monitor the quality of data in a Siebel Customer Relationship Management (CRM) environment. To enable real-time services, the EDQ Siebel Connector translates Siebel function calls into web service requests for EDQ. The EDQ Siebel Connector is a small footprint application that resides on the Siebel server and enables communication with EDQ for real-time (as records are inserted and updated into Siebel) and batch (for running regular data quality jobs on data in Siebel) data quality services. Section 1.3, "Preparing for the EDQ Siebel Connector Integration" Section 1.2, "Verifying the Siebel Server and Instance" Section 1.1, "Understanding the Enterprise Data Quality Siebel Connector" This chapter includes the following sections:
This chapter helps to prepare you for your Enterprise Data Quality (EDQ) Siebel Connector installation and integration to an existing Siebel server. Home / Middleware / Oracle Enterprise Data Quality 5/7 1 Planning the Enterprise Data Quality Siebel Connector Integration
0 kommentar(er)
