Debugging EDQ-CDS / Siebel Matching Issues

The attached document provided by Oracle itself and sharing the same for knowledge purpose only.


Link

Oracle Enterprise Data Quality (OEDQ) - Auto Monitor CDS Jobs

Hi,

I came across one requirement to auto monitor EDQ jobs without manual intervention.


Requirement:
    We need to send auto alert message whenever EDQ Jobs are down or not running.

Solution:

I have implemented solution as follows:

Created Java program which will need to monitor Jobs and send alert message as accordingly.

File attached:

JMX Code Sample

    The attached files contains following files:

1.       JMX_Status.sh is unix file which calls the Java program. It passes the required parameters while calling java program.
2.       SystemConfigClient.class is compiled java program which needs to be placed in EDQ server.
3.       JMX_JAVA_CLASS.txt is java code.
4.       EDQ_Param.txt is parameter file.
 
 
         

EDQ Sequence Generator Processors

As per the requirement, I need to generate the Sequence in EDQ.

The following is the processor, which will generate the sequence.  

"Add Message Id "

OCH (Siebel UCM) - OEDQ Real-Time Matching Process

- In real time, when a new record(driving record) come to UCM, Siebel calls EDQ web services to      generate cluster keys for the new record
- EDQ generate the cluster keys and its send back to Siebel
- Siebel stores these new keys and then looks up all records that share any key with the driving record- Once Siebel find a matching key, it submits driving and candidate records to the matching service
- Driver record and all candidate records are send back to EDQ, to be ranked by Match score
- Siebel then pop-up the Matching record with the match score and user can select 'pick' or 'ignore' to commit the record.
Cluster keys are stored in S_DQ_xxx_KEY tables; 


Accounts: S_DQ_ORG_KEY
Contact:    S_DQ_CON_KEY 

Prospects:  S_DQ_PRSP_KEY

Monitor-OEDQ-Webservice-with-Siebel

Monitor Oracle Enterprise Data Quality (OEDQ) web service when connected with Siebel instance. 

The post will explain, how to visualize the data running through EDQ process:

Here we have two options:

1. Based on process:

 a). Temporary: cancel real-time process from the Director application user     
      interface and select the match processor, the rules hit, data in and data out etc.,related output tabs can view on results browser.

 b). Permanent: we can used writer processor to write output of match processor.


2. EDQ Web service Tester:

   Launchpad -> web Service Tester, by using this we can easily identify the whether the web service is            working as expected or not (for more details please refer the Oracle documentation).

OEDQ Overview Presentation

Please go through the following link which will give the brief idea on Oracle Enterprise Data Quality overview for quick understanding.

OEDQ Presentation

Thanks

Oracle Enterprise Data Quality – About Profilers

Oracle Enterprise Data Quality – About Profiler:

·          The profilers are intended purely to analyze data

·          They are used to quickly understand the data

·          They are used to help find the issues in provided data

·          Profilers  do not 'check' data for business rules

·          Profilers  do not have output filters like ‘valid’ or ‘invalid’ records

The following are some of the different Profilers:

1.     Quickstats Profiler: It is used to analyze overall data i.e. analyze high-level completeness, duplication, and value frequency across many attributes, and highlights possible issues.  Input as ‘any’ data type

2.     Character Profiler: it is used to analyze a number of attributes and counts of the instances of each character. Input as ‘strings’ data type only

3.     Contained Attributes Profiler: it is used to analyze records to find pairs of attributes where one attribute value commonly contains another. Input as ‘any’ data type

4.     Data Types Profiler: it is used to analyze attribute values for their data type e.g String, Number or Date - and assesses data type consistency.  Input as ‘any’ data type

5.     Date Profiler: it is used to analyze a Date attribute for date distribution by day of week, day of month, day of year, month and year.  Input as ‘Date’ data type only

6.  Equal Attributes Profiler:  it is used to analyze records to find pairs of attributes that commonly have the same values.  Input as ‘any’ data type

7.     Frequency Profiler: it is used to analyze value frequency across many attributes.  Input as ‘any’ data type

8.     Length Profiler:  it is used to analyze a number of attributes and measures the length of values by number of characters.  Input as ‘any’ data type

9.     Max/Min Profiler: it is used to find minimum and maximum values e.g:  longest, shortest, lowest and highest.  Input as ‘any’ data type

10.  Number Profiler:  it is used to analyze a Number attribute for number distribution across user-defined bands.  Input as ‘Number data type only

11.  Patterns Profiler: it is used to analyze character patterns, and pattern frequency, across many attributes.  Input as ‘any’ data type

12.  Record Completeness Profiler:  it is used to analyze records for their completeness across many attributes.  Input as ‘any’ data type

13.  Record Duplication Profiler:  it is used to analyze records for duplicates across many attributes.  Input as ‘any’ data type

                 14. RegEx Patterns Profiler:  it is used to analyze a number of attributes for values 
                      that match a list of regular expressions.

Oracle Enterprise Data Quality (OEDQ) - Siebel Configuration (high Level)

This post will explain about the Oracle Enterprise Data Quality (OEDQ)  with Siebel configuration:

Click the link below for more details:

Oracle Enterprise Data Quality (OEDQ) - Siebel Configuration (high Level)


will provide the more details soon.....

Oracle EDQ features and its architecture (high level)

The post will explain about Oracle EDQ features and its architecture (high level)

Click the link below for more details:
Oracle EDQ features and its architecture (high level)

Next post will explain about Oracle EDQ User Interface......