Thursday, April 13, 2017

Oracle Enterprise Data Quality Usage Document

Starting Oracle Data Lens Server

Go to the domain installation path and start the server

Login into the server with the following url http://localhost:2229/datalens
Default user name and password is admin and admin1, after successful login it asks for change password

give the password you want and re login to the datalens server administrative page with new password

Creating Database connections
Login to Oracle Datalens Administration Server Web page
In the configuration group select Database Connections

Click on create New Db Connection
Provide the database connection details and click on save

Click on the database connection you created and Test the configuration.
If the test was not successful check the connection details and retest the connection.

Installing the client software
Start the microsoft internet explorer
Initiate a connection and download the client software by browsing to http://localhost:2229/datalens/datalens.jnlp

Click Run
The client will start now

Give User Id and Password and click on ok

Starting Oracle Datalens Application Studio
Start the Application Studio by clicking on Oracle Datalens Application Studio Launch pad of client.

Understanding the Client Workspace
The Application Studio graphical user interface provides the client workspace used to create and manage DSA.
It contains two types of workspaces
1. DSA Builder
2. Transformation Map Builder
DSA Builder :
It is the default workspace when the application studio is opened

Frame Functionality
The Application Studio Client workspace frame contains useful information and interactive functions including the following
Title Bar
Indicates the current application and open DSA or Transformation Map.

Status Field
Provides the status of the DSA or Transformation Map one line at a time. Though this
field cannot be resized, the scroll arrows on the right-hand side can be used to view all
available status information.
Changes the view between the DSA Builder and Transformation Map Builder client
Application Switch
Returns you to the last EDQP application used.
Oracle Enterprise Data Quality for Product Data Launch Pad
This button opens the Oracle Enterprise Data Quality for Product Data Launch Pad so
that you can select other applications.
Time and Date
The time is displayed and when you hover over this field, the date displays.
Memory Cache
Indicates the amount of memory cache currently used and the total amount allowed.
You can dump the memory cache by clicking on the trash can icon in this interactive
field. This functionality does not appear in the Transformation Map Builder

DSA Menu and Toolbar Explained
The DSA menus and toolbar are the main client workspace and the default when the
Application Studio is opened. The following briefly describes the DSA toolbar buttons
from left to right:

File Menu

Edit Menu

 View Menu

DSA Menu

Tools Menu

Help Menu

DSA Components Tree Pane

This task pane contains all of the components necessary for building a DSA. These
components are categorized into the hierarchical tree structure with the main folder
indicting the name of the current DSA or 'No Data Service Application' to indicate that
there is no DSA open. The sub-folders of any DSA are as follows:
Process Steps
Contains the main components to transform data.
Data Input
Contains the nodes used to indicate one of the three methods that data is
communicated to the DSA: text, a database, or an XML file.
Data Output
Contains the nodes to form how the data is output from the Application Studio.

Output Adapters
Contains the nodes to output XML information to correspond with XML input data.
Pre-Post Processing Steps
Contains the steps that can be used before and after the data is processed.
Defined Processing Steps
Lists all of the processing steps defined for the current DSA. This folder is helpful in
locating processing steps in large, complex DSAs that do not easily fit into the
Graphical DSA Builder pane.
Unused Transformation Maps
Lists any transformation maps that you have created in the current DSA or imported,
and are not assigned to a processing step. This folder acts as a container for maps that
you are either in the process of developing or have imported from other DSAs.
Importing maps allows you to re-use maps originally developed for other DSAs

Creating or Opening a DSA
From the File menu, click New to create your new DSA

Provide the name and description for DSA and click on ok

DSA Building Components
There are 3 types of DSA building components
1. Processing Steps Folder
2. Data Input Folder
3. Data Output Folder
Processing Steps Folder
Processing your input data can take on a myriad of different steps. You can create a
simple DSA that only looks for a minimum of data matching or one that vigorously
reviews the data for matches, duplication, and enriches it. This section describes how
the processing nodes can be used to process data.

Core Processing Steps
The core processing steps are the foundation of transforming data. These steps are
used to define how the input data will be manipulated in preparation for output
formatting. You can add as many core processing steps as needed to transform your
data effectively.
Add a core step by selecting core step node from Map Component Tree and dragging it into the Graphical DSA Builder

Give the name and description and click on New

Give New Map Name and click ok

click ok
This adds a new core processing step  to the Graphical DSA Builder
Add the input data to the core step by dragging the input node and dropping it onto the core step.

Alternative Step Nodes
An Alternative step receives exceptions from the core step that feeds into it.
Alternative steps are added in the same way that core steps are added. They are then connected to core steps by dragging the core step and dropping it onto the alternative step.
The Application Studio adds a route line between the two nodes. Before defining the alternative step, it is advised that you connect the alternative step to the core step; this ensures that the outputs defined in the core step will pre-populate the inputs of the alternative step
Note:  If you do not create an alternative step for exception data handling, the exceptions are discarded and so are not processed or output in any form.
Sleep Step Nodes :
You can use a sleep (wait) step in your processing schema to tell the DSA to halt for a specified amount of time. The addition of these steps can help you in debugging your DSA, allow a particular step that operates slowly the time to complete, or to aid in a processing race condition

Drag a Sleep node from the Map Component Tree pane and drop it into the
Graphical DSA Builder pane

Give the Name and time and click on ok

Drag and drop the Test input to core processing step

Drag and Drop the sleep step onto the processing step you want to wait, connecting the two steps

Editing or Deleting an Input Node
You can rename the text input node or change the description, by right-clicking the
input node, and selecting Edit Step

Edit the name and description if you want and click ok

click on delete node and click yes to delete the node.
Data Output Folder
The final step in DSA creation is to define the output steps.
Text Output Nodes
From the DSA Component Tree pane, in the Data Output folder, drag an Output node (Text, DB, or XML) into the Graphical DSA Builder pane

Provide the values in the opened dailog box and click ok
And now drag the processing step to the output step

Editing a Text Output Step
You can edit an Output Step by right-clicking on it and selecting Edit Steps. The Output Step dialog is displayed so that you can edit the step.

Select the Do NOT return results to caller check box in order to output the results to a file-based output. You must specify a File-based Output selection, text or Excel, with this option. The output of this step will not be available to the Governance Studio.

Use of this check box deactivates the Oracle DataLens Governance Studio tab and the  data output is only stored provided in the methods you select in the File-based Output section

No comments:

Post a Comment

  Opatch reports 'Cyclic Dependency Detected' error when patching ODI   Issue: When applying a Patch Set Update (PSU) to WebLogic Se...