Tip:
Highlight text to annotate it
X
Welcome back to the Getting Started with Oracle Endeca Information Discovery v3.0 series.
This screencast, Getting Started Integrator Overview, will provide an overview of the Integrator components as well as introduce you
to some key concepts within Integrator. In the previous screencast, you were introduced to the Getting Started Studio application, that
lets you explore sales and product data from a fictitious bicycle manufacturer.
However, before you can use Studio to explore such data, you first need to load the data into Oracle Endeca Server.
This screencast will show you how we did that for the Getting Started application using Integrator.
Later, I will show you how to load data using an Excel upload.
The Integrator Designer is an eclipse-based enterprise ETL tool that can extract data from any number of sources, and join, transform, and
enrich that data before loading it into an Oracle Endeca Server data domain.
Integrator Designer consists of a number of panes:
The Navigator pane contains a list of your projects, their subfolders and files.
From here, you can drag any file over to the canvas to view or edit it.
A graph defines data flows and transformations in a quick, visual, and intuitive way.
A graph contains components, that can be individually configured,
and edges that represent data that flows between the components.
You can select components from the palette and drop them onto the graph editor.
The Palette contains a variety of components that allow you to perform common data operations such as reading, writing,
transforming, and joining data.
It also includes operations specific to Oracle Endeca Information Discovery, such as loading data into the Oracle Endeca Server data
domain.
The Outline pane organizes the graph’s content by type, providing an alternate way of viewing or editing the graph information.
Finally, the Tabs pane consists of a series of tabs, such as the Properties tab and the Console tab,
that provide information about the components and the results of graph executions.
The Getting Started application consists of a number of graphs that, when run in sequence, perform a full refresh of the data and
configuration. Let’s take a look at them:
The Baseline graph is essentially a wrapper around the other graphs.
Its main purpose is to kick off the other graphs in a particular order.
This is the graph that you run in order to get the Getting Started application up and running.
When the Baseline graph is started, it first kicks off the InitDataDomain graph, that creates the Oracle Endeca Server data domain for the
Getting Started application, if one is not yet created.
The ResetDataDomain graph is then called, that clears all data, schema, and config from the data domain.
The LoadConfiguration graph loads configuration information, such as attribute groups, attribute display names and attribute sort order.
This graph will be covered in more detail later in this screencast series.
The LoadData graph is responsible for reading in, joining, transforming, and loading all of the data into an Oracle Endeca Server data domain.
Later in this screencast series, you will use the graph to load and join data.
Finally, the LoadViewDefinitions graph loads the View definitions that are required to power the Studio visual components,
such as charts and some tables. Views are covered in more detail in part 4 of this screencast series.
So, once the baseline graph is processed, the Oracle Endeca Server data domain is ready to be queried!
Future screencasts in this series will walk you step-by-step through the core knowledge required to re-build this application.
Once you’ve completed this screencast series and have learned the basics, you can explore all of the other features and benefits provided by
Oracle Endeca Information Discovery on your own, or take a class at Oracle University.
In this screencast, you received an overview of the Getting Started Integrator component, and learned about some key concepts within
Integrator.
Part 3 of this screencast series will show you how to iteratively load data into an Oracle Endeca Server data domain and view the results
within Studio.