Getting Started With Endeca Latitude

Unauthorized reproduction or distribution prohibited Copyright 2011, Oracle and/or its affiliates
le
b
fera
n
a
r
t
n-
no
a
Getting Started
s with Endeca
a
h
) 2 e
Latitude
m
o
c Guid
e
l
c
Guide
t
ra Student
n
o
e
n@ Stud
a
m this (Version 2.2.1)
e
l
fsu use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
D75432GC10
Edition 1.0
February 2012
D75730
Copyright 2000, 2011, Oracle and/or its affiliates. All rights reserved.
Disclaimer
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may
copy and print this document solely for your own use in an Oracle training course. The document may not be modified or
altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download,
upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in
part without the express authorization of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document,
please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This
document is not warranted to be error-free.
This training manual may include references to materials, offerings, or products that were previously offered by Endeca
Technologies, Inc. Certain materials, offerings, services, or products may no longer be offered or provided. Oracle and its
affiliates cannot be held responsible for any such references should they appear in the text provided.
Restricted Rights Notice
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the
United States Government, the following notice is applicable:
Trademark Notice
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their
respective owners.
Ka
fS
i
h
s
n
a
r
t
n-
U.S. GOVERNMENT RIGHTS

The U.S. Governments rights to use, modify, reproduce, release, perform, display, or disclose these training materials are
restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
le
b
fera
Student Guide
Table of Contents
Getting Started with Latitude 2
Table of Contents
Module 1 Latitude 2 Core Concepts____________________________________ 1
Lesson 1 Introduction to Latitude ___________________________________ 1.1
Lesson 2 Data Ingest _____________________________________________ 1.2
Lesson 3 Capabilities Overview_____________________________________ 1.3
Lesson 4 Latitude Studio Overview __________________________________ 1.4
Lesson 5 - Data Exploration in a Latitude Application ____________________ 1.5
Module 2 Basic Data Design _________________________________________ 2
Lesson 1 Project Basics with Latitude _______________________________ 2.1
Lesson 2 Working with Latitude Studio ______________________________ 2.2
Lesson 3 Data Modeling and Joining Data ____________________________ 2.3
Module 3 Search and Navigation Configuration Enhancements _____________ 3
Lesson 1 Introduction to Search ____________________________________ 3.1
Lesson 2 Enhancing Navigation ____________________________________ 3.2
Module 4 Advanced Topics ___________________________________________ 4
Lesson 1 Data Ingest and Modeling Overview _________________________ 4.1
Lesson 2 Integrating with Other ETL Tooling __________________________ 4.2
Lesson 3 Security _______________________________________________ 4.3
Lesson 4 Text Enrichment in Latitude _______________________________ 4.4
Lesson 5 Latitude 2 Deployment Features ____________________________ 4.5
Lesson 6 Next Steps for Enablement ________________________________ 4.6
Module 5 Analytics _________________________________________________ 5
Lesson 1 Introduction to Endeca Analytics____________________________ 5.1
Lesson 2 Analytics Workshop ______________________________________ 5.2
n
a
r
t
n-
Ka
fS
i
h
s
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
le
b
fera
Ka
le
fS
i
h
s
u
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
n
a
r
t
nb
fera
Student Guide
Module 1
Latitude 2 Core Concepts
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
anmin. licen
Lesson Time:
~45
m
ule~30 min.
Lab Time:
S
if
h
s
a
Lesson 1
Introduction to Latitude
Copyright2011 Endeca Technologies, Inc.

All rights reserved. Proprietary and confidential.
1.1.1
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.2
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.3
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n information
en management software that guides people to better decisions. We
aagile
Endeca provides
c
i
m
l
do this with
uletwo products: Latitude for agile BI and InFront for agile commerce. One improves daily
S
decisions
for employees, the other for consumers. Both products are based on the MDEX Engine, a
if
h
s
a hybrid search-analytical database that empowers IT to cope with the increasing diversity and change
inherent in delivering information in today's enterprises. More on the MDEX later
We provide the new kind of information management companies need for better decision-making:
agility to handle diverse and changing data, to answer diverse and changing questions asked by
people with no training in the underlying technology.
Endeca Company Facts:
Based in Cambridge, MA with global sales/services offices
$100M+ annual revenue
600+ customers
Lesson 1

1.1.4
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cen to agile BI based on three principles.
Endeca takes
aa
uniquelapproach
m
le behind: i
u
No data
left
f S We bring together structured data and unstructured content, whether inside the company or
i
h
as
out. Our core technological innovation, the MDEX engine, enables you to easily combine all
data needed for true insight. Latitude also offer analytic apps to help you solve problems
previously unthinkable. Additionally, Latitude is the only BI technology that unifies structured
content & social media for re todays decisions.
Guidance in daily decisions:

We make software people actually want to use software that guides them to better decisions
than they would reach with any alternative, through the industrys only patented Guided
Navigation. Latitude offers user interfaces that tell people about the data before they interact
with it, extending discovery for every user.
Agile delivery:
Using agile delivery principles, Endeca has developed the Slipstream iterative release
methodology. This unique methodology enables IT to be both more responsive to the business
and more cost-effective. Because the engine at the heart of our solution is so different from
traditional BI technologies, IT can quickly load disparate data, get a look at it in the application,
and then collaborate with the business to refine it. This helps IT discover the true requirements
of the project more quickly, and in turn leads to faster user adoption.
Lesson 1

1.1.5
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n Endeca MDEX engine, the industrys only solution that is a cross
epatented
an by lthe
Latitude is powered
c
i
m
between
ualesearch engine and an analytical database.
S
if
h
s
a As a result of the internal data architecture, each record has its own set of attributes based on the
original source data as well as any metadata added by Endeca during data integration. This data
architecture simplifies modeling requirements and ensures new content can easily be added in the
future. Furthermore, the work of creating conformed dimensions and facts, which is typically done
when setting up multiple data marts, is not required here. As an added benefit, the engine is able to
handle your unstructured content in the same flexible manner.
The MDEX engine operates as a memory leveraged model, optimizing the use of main memory,
caching, and storage resulting in faster responses and flexibility to deal with large volumes of data.
Additionally, you can load your source data as is meaning you practice load, expose, refine instead
of extract, transform, and load.
Lesson 1

1.1.6
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
ento being able to combine data as-is.
anadvantages
There are several
c
i
m
l
le
uData:
Diverse
S
if Here we can see records from four very different source systems combined together in the
h
s
a
MDEX Engine. In this example, all the sources are considered structured. We are not
conforming the data to fit a target schema; we are simply stacking records in their native
format on top of each other. This enables you to get data into the hands of the end-users
rapidly, without having to wait for a perfect consolidated data model. Similarly, as additional
source systems or attributes are indexed over time, Endeca can easily accommodate the new
or changed data without needing any target schema redesign.
Unique Attributes:
Every source system will contain its own unique set of attributes. The MDEX Engine
summarizes and allows navigation on all of these unique attributes without compromising their
original structure so that it fits into a neat box.
Jagged Data:
The MDEX Engine allows information to stay naturally jagged. Every record may have its own
set of unique attributes; even if the records are from the same source system. Accommodating
jagged data eliminates issues caused by data sparseness. For example, the MDEX Engine
negates the need to create expensive dummy fields that are not relevant to the record on
which they are attached (e.g., flavor=NO FLAVOR for a pair of shoes).
Lesson 1

1.1.7
Module 1
Student Guide
Global Attributes :
Information sources will also contain common or global attributes across many records and
source systems (e.g. common part numbers, employees, regions and territories, suppliers,
etc). Whenever a record contains an attribute that is shared with another record or system a
relationship is identified. Records in the MDEX Engine are related whenever a common
attribute exists. This means that relationships exist at the attribute level not at the table or
record level - which is the finest granularity possible.
End-users interacting with the Endeca application can use any starting point to enter the data,
even a basic search term. The user is not forced down a pre-defined analysis path as with
traditional BI drill down technologies (OLAP, ROLAP, etc.), and as a result they constantly
discover new insights in the data as they interact with it. Not only can they drill down, they can
drill anywhere and pivot across any type of information in any source system wherever a
relationship exists across common attributes in the data. This offers far more flexibility than
relationships defined in advance in a specific data model.
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

le
b
fera
1.1.8
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cconvinced
en
It is not enougha
that IT be
Endeca is a great compliment to the BI ecosystem. The ultimate
i
m
l
test liesuwith
le the business user and how successfully they are utilizing the solution to make effective
S
and
actionable
business decisions every day. Endeca applications help users not only find what they
f
i
h
need, but analyze what they found, so they can better understand their options. The Endeca user
s
a
experience brings together:

Search Easy access to all related data with state-of-the-art search.
Navigable Unstructured Content The MDEX engine makes documents and web-content
part of the searchable decision data not just reference information.
Guided Navigation Our patented Guided Navigation drives users to ask precise questions,
enabling them to better express what theyre really looking for. Guided Navigation arms users
with the ability to navigate your unstructured content encouraging them to discover
unanticipated, and oftentimes better answers.
Interactive Visualizations Users can point and click on visualizations to learn more
without the need to formulate a query or traverse a prepared hierarchy of data.
All in all, Endecas consumer ease-of-use combined with all of the data users need, enables them to
reach high confidence answers; answers that can only be derived by bringing together otherwise
siloed information into a single pane of glass.
Lesson 1

1.1.9
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en may be, it has to be in the hands of your users in order to solve
an anylictechnology
No matter how
good
m
the business
ule problem and create value. Thats why we have focused a great deal of our attention on
S
hfastif deployments and time-to-value. Our Iterative Release Methodology, Slipstream, is designed to
s put production applications not conference room pilots in the hands of your users in as little as 10-
Ka
12 weeks.
Slipstream is based on the premise of delivering an operating application every 2 to 3 weeks. In order
to do that we have spent a great deal of effort building out our technology and delivery processes to
speed the delivery of configured applications for your users. Specifically, the manner in which we
handle data in our MDEX engine simplifies the process of loading data and supports the incremental
addition of new or changed data sources.
Similarly, because it is impossible to define all requirements upfront we developed the Latitude Studio
to speed the initial configuration and deployment as well as support a collaborative improvement
process between users and IT.
Endecas Iterative Release Methodology allows development to start before requirements are
finalized, getting critical information into the hands of the business early. As requirements are realized
throughout the project lifecycle the application can be quickly changed to accommodate unforeseen
benefits
Lesson 1

1.1.10
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
MDEX Engine:
m
e heart of Endeca Latitude is MDEX Engine technology, the industrys only hybrid
uAtlthe
S
if search-analytical database designed to bring together all of the information required for making
h
s
a
critical business decisions, regardless of its original type, format, or source. This allows users
to explore data and content in an unconstrained and impromptu manner, rapidly addressing
new questions as they arise. Bringing together diverse datasets without complex modeling and
integration, the engine conducts search, navigation, and analytics. With support for ITmanaged data governance and data security as well as industry standards such as XQuery,
XML, and SOA, the MDEX Engine is designed to fit easily into existing enterprise
architectures.
The Latitude Information Integration Suite:

Endeca Latitude supports an agile approach to deployment that reduces the data modeling
and integration inherent in traditional software deployments. It provides powerful integration
capabilities through the Latitude Data Integrator (LDI), the Endeca Content Acquisition System
(CAS), and various custom MDEX connectors. It provides an extensible framework for ingest
of a broad range of unstructured content, and through support for best-of-breed data adapters
and ETL tools. These tools enable rapid integration of both structured data and unstructured
content and the flexibility to easily add new data sources.
Lesson 1

1.1.11
Module 1
Student Guide
Latitude Studio:
The user interface configuration part of Endeca Latitude provides a library of components that
deliver advanced search capabilities, Endecas patented Guided Navigation experience, rich
visualizations, and analytics for the rapid configuration of Latitude applications. This enables IT
organizations to respond to changing business needs by re-designing reports and dashboards
in minutes, incorporating diverse data sources in days, and deploying entirely new applications
in just a few weeks.
How Latitude Works:
1. Data is loaded into the Latitude Information Integration Suite; LDI, or another connector,
then loads data into the MDEX Engine
2. Records received from the LDI are indexed in the MDEX Engine, which then receives and
processes query requests from Latitude Studio
le
b
fera
n
a
r
t
n-
3. Latitude Studio application contains components, which you use to query the MDEX
Engine and manipulate the query results.
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.12
12
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.13
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.14
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enhierarchy, dynamic refinement ranking, grouping, precedence rules all
anrefinement
Features such
as
c
i
m
l
le your information.
help you
uorganize
S
if
h
s
a Navigation is contextual to the characteristics of the search results. The goal of navigation is to
provide refinements to offer guidance to your next steps. Because Endeca enables all of the attributes
in your data set to be use for refinement, Endeca offers way in which you can organize your attributes
and attribute values for a better user experience.
Lesson 1

1.1.15
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.16
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.17
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.18
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.19
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.20
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cen
Definition: ma
li
leof the Latitude
u
Part
Information Integration Suite, Endecas Content Acquisition System
S combines a robust and
f
i
extensible framework for retrieving and manipulating semi-structured
ash
content with a broad library of data adapters and text enrichment modules.
Features:
Extensible framework for data source connectivity and data manipulation
64-bit, multi-threaded platform available on Windows and Linux
Out-of-the-box connectivity to Documentum, FileNet, Lotus Notes, Sharepoint, Interwoven,

and OpenText
Crawlers for file systems and the web; includes data store for capturing crawl output
Text and metadata extraction for 500 file formats
Benefits:
Easily integrate data from a variety of unstructured data repositories
Best-of-breed partner technologies available for text enrichment
Low cost introduction of new data sources and manipulators through extensibility SDK
Lesson 1

1.1.21
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cenIntegration Suite features a new ETL tool, the Latitude Data Integrator.
The Latitudem
2.1aInformation
li
lePart of the Latitude
u
Definition:
Information Integration Suite, the Latitude Data Integrator (LDI) is a
S
f
i
high-performance data integration platform that lets you extract source records from a variety of
ash
source types (from flat files to databases) and send that data to the Data Ingest Web Service. The
Data Ingest Web Service in turn loads the records into the MDEX Engine.
Features: Designer with powerful graphical interface, Connectors to leading enterprise applications, A
comprehensive enrichment library, Integrations with industry-leading ETL tools for data ingest, A
direct connection to the MDEX Engine, Best-of-breed crawlers for file systems and web sites
Benefits: The right tool for the data at hand, Easily unify multiple data sources, The Designer
enables quick and easy way to graphically lay out the most complex graphs using drag and drop
functionality
For more information: Endeca has produced the Latitude Data Integrator Guide, available for
download on EDeN.
For further reference, an extensive set of Clover documentation is available at
http://www.cloveretl.com/resources. From that Web site, you can access the Quickstart Guide,
the Designer User's Guide, and the Server Reference Manual. Other resources, such as a
users forum, can also be accessed from this Web page.
Lesson 1

1.1.22
Module 1
Student Guide
le
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cen
Definition: ma
li
le ETL connectors
u
Other
will become available as Latitude evolves.
S
f
i
ashFeatures:
b
fera
Provides custom transformations to build the records
Provides custom targets that reassemble single-assignment records into complete

Endeca records and loads the complete records into an MDEX Engine
Provides a custom connection object that specifies the host, port, and other configuration
information of the server running the MDEX Engine
Lesson 1

1.1.23
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cen
Definition: ma
li
lecore data management
u
The
solution of Latitude is the MDEX Engine technology, a hybrid
S search-analytical database that
f
i
is highly-scalable and column-oriented. The MDEX Engine
ash
provides support for guided exploration, search, and analysis on any kind of information;
structured, semi-structured or unstructured, from inside the firm or from external sources.
Features:
Unification of structured, semi-structured and unstructured data through "No data left
behind" approach
Uses advanced data structures and algorithms that allow real-time responses to client
requests
Benefits
Enablement of users to explore data and content in an unconstrained and impromptu

manner to rapidly address new questions
Frees IT from the burdens of traditional data modeling
Support of the broad exploration and analysis needs of business users
Lesson 1

1.1.24
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cen
Definition: ma
le Studio lisi a highly-interactive, component-based environment for building enterpriseu
Latitude
f S class analytic applications powered by MDEX Engine technology. It is built on robust webi
h
as
based infrastructure technologies that enable building analytic applications delivered through
the use of popular Web browsers.
Features:
Components-based analytics and visualization product
Assortment of templates and themes for flexible styling
Robust library of components (e.g., Data Explorer, Guided Navigation, Charts)
Granular role-based authorizations
Multi-language support
Benefits:
Support of decision-making through quick access to data
Enables rapid time-to-value through minimal configuration effort
Support of agile development methodology
Seamless upgrades of applications as new components and features are released
Lesson 1

1.1.25
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.26
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.27
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.28
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.29
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.30
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.31
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.32
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

1.1.33
Ka
le
fS
i
h
s
u
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
n
a
r
t
nb
fera
Student Guide
Module 1
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
anmin. licen
Lesson Time:
~25
m
ule
S
if
h
s
a
Lesson 2
Data Ingest

1.2.1
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Data Ingest

1.2.2
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Data Ingest

1.2.3
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
an liceIntegration
The Latitude
Information
Suite features a comprehensive set of data integration
m
e
l
options.
in the Suite are the Latitude Data Integrator, an out-of-the-box ETL
SuIncluded
f
i
product;
the
Content
Acquisition System; and connectors for industry-standard ETL
ash
products.
The Endeca Latitude connectors are used to load data into the MDEX Engine. These
connectors enable you to extract and load both structured and unstructured data sources into
the MDEX. In addition, open Web service APIs for data and configuration integration make it
possible to integrate more varied information into the MDEX Engine.
Lesson 2
Data Ingest

1.2.4
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enchallenge for enterprises. To address these concerns, information
aisna continual
Data integration
c
i
m
l
le
access u
applications
need to be based on technology that both provides out-of-the-box connectors to
S
f
common
enterprise systems and supports connecting to novel systems through simple extension
i
ashpoints. Endeca's Content Acquisition System, consists of a mixture of standards-based connectivity,
packaged adapters, and an extensible framework for creating and configuring adapters to new
systems.
Key benefits of the Endeca Content Acquisition System include:
Consolidated view of information from diverse sources to support analysis
Low-risk, rapid deployments using pre-packaged functionality
Support for new data sources as business requirements change
Low maintenance overhead
Information security
Lesson 2
Data Ingest

1.2.5
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en is a high-performance data integration platform that enables
an Integrator
The Latitude
Data
c
i
m
l
you extract
ule source records from a variety of source types (from flat files to databases) and
S
if the records into the MDEX Engine. From a high-level, the LDI consists of the Designer,
load
h
s
a
Endeca-developed connectors and (optionally) a Server.
Lesson 2
Data Ingest

1.2.6
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
an liceLatitude
As previously
mentioned,
connectors are part of the palette, or available design
m
e
l
elements,
Su in the LDI Designer.
f
i
hThe Designer is where you create the graphs for loading your data. A graph is a pipeline of
Ka
components that processes the data. The simplest graph has one Reader component to read
in the source data and one of the Latitude connectors to write (send) the data to the MDEX
Engine. An edge, the line that connects component ports, carries data between components.
More complex graphs will use additional components, such as the Transformer and the
Joiner components.
The Designer offers a powerful graphical interface, providing an easy way to visually lay out
even the most complex graphs. The Designer is also simple to use--you are able to drag and
drop the components from the Palette and then configure them by clicking on the component
icon. The Designer tool is covered in detail later in this course.
Lesson 2
Data Ingest

1.2.7
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en connectors have been specifically engineered to work with
an licLatitude
The Endeca-developed
m
leEngine's Data Ingest Web Service and Bulk Load Interface. These connectors are
the MDEX
u
S
incorporated
into the Designer Palette, so that you can easily drag them into your graphs.
if
h
s
a These connectors can be found in the Palette under Endeca, and include:
Add KVP (Key Value Pairs)

Add Managed Values (Hierarchy definition)
Add/Update Records
Bulk Add/Replace Records
Delete Data
Export Config
Import Config
Reset MDEX
Transaction RunGraph
ReadRecordStore (only available through Endeca Consulting)
Each of these connectors is discussed in detail later in this course (with exception of
ReadRecordStore).
Lesson 2
Data Ingest

1.2.8
Student Guide
Module 1
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
an is not
Because them
Server
aemandatory component for loading data into the MDEX Engine, it is not
c
i
l
documented
ule in detail in this course. For information on the setup and use of the Latitude Data
S
Integrator
Server, see the Data Integrator Server pdf.
if
h
s
a
Lesson 2
Data Ingest

1.2.9
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Data Ingest

1.2.10
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n interfaces to the MDEX Engine. The Data Ingest Web service
eprovide
anservices
The Latitudem
Web
c
i
l
leinterface to ETL tools and a means of loading, updating, and deleting records. The
provides
uan
S
Configuration
Web service allows you to update the schema and configuration. These two Web
if
h
s
a services are public, enabling you to program custom connectors against them.
There are also two private Web services:

Private Web services include: the Conversation Web service, which provides the primary means of
querying data in the MDEX Engine; and the Administration Web service, which is used by IT
engineers and administrators to integrate the MDEX Engine server and its reporting with third-party IT
tools.
Lesson 2
Data Ingest

1.2.11
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
e
anan open
Latitude provides
data ingest API, the Data Ingest Web service, to allow you to use
c
i
m
l
whichever
uleETL tool is most appropriate for the job.
S
if structured data, you can use your ETL tool of choice, or use our out-of-box Latitude Data
For
h
s
a
Integrator. For unstructured data, use CAS and combine it with your structured data in ETL.
Lesson 2
Data Ingest

1.2.12
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cen
Delimited: ma
li
leIs the most frequently used format because it is easy to create and maintain
u
f S First row identifies field names
i
h
Each subsequent row represents a record
as
XML:
Can use any field and row delimiters
Requires any non-Endeca XML data to be transformed with XSLT

Is useful if the source data is already in an XML format
Fixed Width:
Is much less frequently used because it is difficult to maintain and can cause values to be
truncated
Requires you to specify the field names, starting position, and field widths within the ITL
configuration
Lesson 2
Data Ingest

1.2.13
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Data Ingest

1.2.14
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en supports the following content management systems:
an liSystem
The Contentm
Acquisition
c
u leDocumentum
S
if eRoom
h
s
FileNet P8
a
FileNet Document and Image Services

Hummingbird DM
JSR-170 compliant repositories
OpenText LiveLink
Lotus Notes
Microsoft Sharepoint 2003 & 2007
Interwoven TeamSite
Document conversion is provided by a licensed version of Oracle OutsideIn which can convert over
500 file formats.
For data sources that are not supported by CAS, the Content Adapter Development Kit (CADK)
provides the capability to create custom adapters.
Lesson 2
Data Ingest

1.2.15
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enEngine consists of records and attributes.
ainnthe MDEX
The data model
c
i
m
l
u leRecords are the fundamental units of data.
S
if Attributes are the fundamental units of the schema.
h
s
a
For each attribute, a record may be assigned one or more attribute values. An attribute is the basic
unit of a record schema. Attributes describe records in the MDEX Engine.
For a data record, an attribute provides information about that record. For example, for a list of books,
the Author attribute contains the author of the book.
For an attribute schema record, an attribute provides configuration information. For example, each
attribute is itself represented by an attribute schema record. Each attribute in that attribute schema
record controls an aspect of the attribute, such as the format of the attribute values and whether the
attribute can be used for searches.
The term attribute collectively refers to both standard attributes and managed attributes.
Lesson 2
Data Ingest

1.2.16
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enrefers to both standard attributes and managed attributes. Standard and
ancollectively
The term attribute
c
i
m
l
e
managed
are both described by system records. The system records that describe standard
ulattributes
S
f
attributes
are known as Property Description Records (PDRs), where the system records that
i
ashdescribe managed attributes are known as Property Description Records (PDRs) and Dimension
Description Records (DDRs). These will be discussed in detail later in the course.
Each standard attribute, includes the following attributes:

Name and type
Display name
Configuration parameters (whether an attribute is searchable)
Navigability settings (whether to show record counts for available refinements, whether to
enable multi-select, and how to sort refinements)
A managed attribute has the same name as the associated standard attribute, but it is used to enable
the creation of hierarchical standard attribute values.
Each managed attribute includes the following schema attributes:
Name
Enable refinements (True or False)
Enable value search (True or False)
Enable record search (True or False)
Lesson 2
Data Ingest

1.2.17
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Data Ingest

1.2.18
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Data Ingest

1.2.19
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Data Ingest

1.2.20
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Data Ingest

1.2.21
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Data Ingest

1.2.22
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n ceofnattribute/value pairs, with no segmentation into tables and no
Each record m
is aacollection
le schema. li
overarching
u
f Srecord is self-describing, representing its own, possibly unique schema that accommodates both
i
Each
h
as
multi-valued and unstructured fields.
Lesson 2
Data Ingest

1.2.23
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en strings
an character
String: represents
c
i
m
l
ule supports representation of three numeric data types:
Numeric
S
if Integer represents a 32-bit signed integer
h
s
a
Long represents a 64-bit signed integer
Double represents a floating point value, or a values that can be specified in a decimalpoint format (such as 20.0) or in a scientific notation format using "e" or "E"
Geocode represents latitude and longitude pairs, used for geospatial filtering and sorting
Boolean used for tracking true/false conditions; 1 = true and 0= false
dateTime represents the year, month, day, hour, minute, and seconds of a time point, with the
optional specification of fractional seconds. You can specify a dateTime value as either a
universal (UTC) date time or as a local time plus a UTC time zone offset. Note that specifying just
a local time is not supported.
Time represents an instant of time that recurs every day; the hour and minutes of an instance of
time, with the optional specification of fractional seconds. A time zone is not allowed as part of the
time representation.
Duration represents a duration of the days, hours, and minutes of an instance of time. A time
zone is not allowed as part of the time representation.
Lesson 2
Data Ingest

1.2.24
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Data Ingest

1.2.25
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Data Ingest

1.2.26
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Data Ingest

1.2.27
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Data Ingest

1.2.28
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Data Ingest

1.2.29
Ka
le
fS
i
h
s
u
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
n
a
r
t
nb
fera
Student Guide
Module 1
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
anmin. licen
Lesson Time:
~40
m
ule
S
if
h
s
a
Lesson 3
Capabilities Overview

1.3.1
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

1.3.2
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

1.3.3
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

1.3.4
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
ento Record Search, you edit the recsearch_config index
an related
To configurem
settings
c
i
l
configuration
ule document and send it to the MDEX Engine through the Latitude Data Integrator.
S
if document is covered in detail later in the course.
hThis
Ka
Lesson 3

1.3.5
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en group of at least one attribute or a set of attributes against which a
an is laicnamed
The search interface
m
le is applied. Search Interfaces utilize match modes, which allow you to specify whether
search u
term(s)
S
you
if want to match on all, some, or at least one search terms entered by the user. There is also a
h
s
a Boolean match mode that allows you to be more explicit with your search (and, or, not, etc.), as well
as numerous other settings that can be applied to record search results and the type-ahead feature in
the Search component.
Search Interfaces and Match Modes are discussed in detail later in this course.
Lesson 3

1.3.6
Student Guide
Module 1
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enthe system to return matches for related concepts to words or phrases
an allows
The thesaurus
feature
c
i
m
l
contained
ulein user queries. This is covered in detail later in the course.
S
if
h
s
a
Lesson 3

1.3.7
Student Guide
Module 1
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en search results to include word roots and word derivations. Stemming
an broadens
The stemming
feature
c
i
m
l
is enabled
ulein the MDEX Engine by default and is available only for English. Stemming is intended to
S
allow
if words with a common root form (such as the singular and plural forms of nouns) to be
h
s
a considered interchangeable in search operations.
Lesson 3

1.3.8
Student Guide
Module 1
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en
anis a lclosely-related
Spelling correction
feature to stemming and thesaurus functionality, because
c
i
m
le
spellinguauto-correction
provides an additional mechanism for computing alternate versions of the
fS
user
query.
i
h
as
Lesson 3

1.3.9
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n provides
en the ability to return an excerpt from a record called a snippet to
afeature
The snippeting
c
i
m
l
an application
ule user who performs a record search query.
S
f
A isnippet
contains the search terms that the user provided along with a portion of the terms
h
s
a
surrounding content to provide context. A front-end application in Latitude Studio displays these
snippets on the record list page of a querys results. With the added context, users can more quickly
choose the individual records they are interested in.
You enable snippeting on individual members (fields) in a search interface that typically have many
lines of content. You can also enable snippeting on a per-query basis.
Lesson 3

1.3.10
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en ranking, means:
an ltoicrelevancy
Stacked, asm
it pertains
u leThe first module applied has the greatest impact on result order
S
if
h
Each record receives a score
s
a
Records are displayed in descending score order
If the first module results in the same score for multiple records, a second module can be
applied to break ties
Each subsequent module is treated as a tie-breaker to the module preceding it
You can create and control relevance ranking for both record search and value search at a systemdefault level. You can also apply record search relevance ranking as you are creating a search
interface, or afterwards.
Lesson 3

1.3.11
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n valuecsearch
en performs a wildcard attribute search returning all values containing
athe
In this example,
i
m
l
e so far, pro.
the string
ulentered
S
if
h
s
a
Thesaurus entries are NOT applied when a user selects an attribute or attribute value that is offered
via the type-ahead functionality because they are making an attribute refinement. In this sense, it
functions in a similar manner as Guided Navigation, assisting the user in their exploration of the data.
By default, all string attributes are value searches.
Lesson 3

1.3.12
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

1.3.13
Student Guide
Module 1
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n business
en analysts using Latitude Studio to create a set of filters, where each
aallows
The Range Filter
c
i
m
l
le attribute. End users can then use these filters to refine the displayed data to only
filter is auspecific
S
include
if records that have attribute values within a specified range.
h
s
a
Lesson 3

1.3.14
Student Guide
Module 1
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en to filter within a geographic area. The map component allows a user
anenable
Geographic Filters
users
c
i
m
l
le
to filter u
geographically
by clicking and dragging to select the desired region.
S
f
i
ash
Lesson 3

1.3.15
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

1.3.16
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enhierarchy, dynamic refinement ranking, grouping, precedence rules all
anrefinement
Features such
as
c
i
m
l
le your information.
help you
uorganize
S
if
h
s
a Navigation is contextual to the characteristics of the search results. The goal of navigation is to
provide refinements to offer guidance to your next steps. Because Endeca enables all of the attributes
in your data set to be use for refinement, Endeca offers way in which you can organize your attributes
and attribute values for a better user experience.
Lesson 3

1.3.17
Student Guide
Module 1
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en applications be initially configured with all attributes as Multi-OR. As
anthatlLatitude
It is recommended
c
i
m
your users
ulework with the data, you can refine this. The other configuration for attributes is Mulit-AND.
S
if
h
s
a
Lesson 3

1.3.18
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
Standard Attribute:
m
le a single refinement can be chosen from a standard attribute
u
Only
S
if Once a refinement has been chosen, that attribute is no longer included in the response object
h
s
a Multi-OR Attribute:
Multiple refinements can be chosen from a Multi-OR attribute

As more refinements are chosen, the result set grows (OR filter)
Once a refinement has been chosen, that attribute remains in the response object
The refinements that are returned now indicate valid next steps given every other specified
filter excluding selections within this attribute
Multi-AND Attribute:
Multiple refinements can be chosen from a Multi-AND attribute. Only attributes with multiple
assignments per record are logical for Multi-AND.
As more refinements are chosen, the result set narrows (AND filter)
Once an refinement has been chosen, that attribute remains in the response object.
The refinements that are returned now indicate records with additional assignments exist.
Lesson 3

1.3.19
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en the user to define the order of Endeca records returned with each
an liallows
The sorting functionality
c
m
query. Record
ule sorting only affects the order of records. It does not affect the ordering of attributes or
S
attribute
if values that are returned for query refinement. Note that all attributes are automatically
h
s
a enabled for record sorting when they are created. Therefore, no attribute configuration is required for
sorting.
Lesson 3

1.3.20
Student Guide
Module 1
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enprevents the page size problems that large lists of refinements can
an Ranking
Dynamic Refinement
c
i
m
l
create. ule
fS
i
h
as
Lesson 3

1.3.21
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

1.3.22
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

1.3.23
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

1.3.24
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enValue as the Source for a Precedence Rule, the Target Dimension will
aanDimension
When specifying
c
i
m
l
le only after the specified DimVal of the Source Dimension has been refined on.
becomeuvisible
S
if
h
s
a
In the above example, the Resolution dimension will only become visible when you select Digital
Cameras from the list of Categories. Whereas the Processing Speed dimension will only become
visible when you select Computers from the list of Categories.
Alternative Use Case:
Another great use case for this type of scenario is when you want to use different "price range"
dimensions for different categories of products:
You might setup a different set of price range dimension values for phones ($75-$200, $201-$300,
$301-$400) then you would use for televisions ($75-$499, $500-$749, $750- $1000, $1000-$2499,
$2500).
You could setup a precedence rule to show the "Phone Price Ranges" dimension when the user
browses on "Phones" as the category and setup a 2nd precedence rule to show the "tv Price Ranges"
dimension when the user browses on "Televisions".
Lesson 3

1.3.25
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

1.3.26
Student Guide
Module 1
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n out
eofn the box support for analytics, including integrated support for analytic
aincludes
Latitude Studio
c
i
m
l
le any standard or custom component. This capability enables you to directly leverage
queriesu
within
S
high
if performance MDEX query capabilities.
h
s
a
Lesson 3

1.3.27
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

1.3.28
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n a platform for constructing applications that enable data
eprovides
an Engine
The Endecam
MDEX
c
i
l
consumers
uleto quickly and efficiently locate information of interest in large databases, using the Guided
S
Navigation
interface. Endeca Analytics builds on the core capabilities of the Endeca MDEX Engine to
if
h
s
a enable applications that examine aggregate information such as trends, statistics, analytical
visualizations, comparisons, and so on, all within the Guided Navigation interface.
Lesson 3

1.3.29
Module 1
Student Guide
le
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en
an can
Analytics Statements
include:
c
i
m
l
le
Su
Unary operators - e.g., absolute value, square root, ceiling/floor,
if Aggregate operators - average, total, min, max, standard deviation,
h
s
a
b
fera
Multi-dimension aggregation - e.g., group by region and then by gender
Having and Where Clauses - e.g., restrict results by pre/post-aggregate values
Arithmetic and Logical Expressions - e.g., A times B minus (X plus Y)
Sorting and Paging - e.g., top ten results by metric in descending order
Lesson 3

1.3.30
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

1.3.31
Ka
le
fS
i
h
s
u
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
n
a
r
t
nb
fera
Student Guide
Module 1
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
anmin. licen
Lesson Time:
~20
m
ule
S
if
h
s
a
Lesson 4
Latitude Studio Overview

1.4.1
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

1.4.2
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en component-based application with a focus on light-weight
ais nan extensible,
Latitude Studio
c
i
m
l
architecture,
ule standard component interfaces, and configurability. Latitude Studio is generally used for
S
internal-facing
applications that exist behind the firewall. However, it is also appropriate for lowif
h
s
a throughput external-facing applications; for example, extranets. Latitude Studio was created to provide
more granular layout and configuration control for a broader audience of users, enabling them to
control their own experience.
Driven by increasing customer demands and competition, every organization needs to rapidly address
new challenges of performance and profitability at the very heart of their operations. To help
enterprises address these challenges by leveraging existing IT investments, Endeca has developed
an innovative solution that provides the ability to rapidly access the most important enterprise
information. This search-based approach connects all necessary information in a user-friendly
environment, that provides ease of discovery for key decision-making tasks. This solution is Latitude
Studio.
Latitude Studio enables rapid configuration of search applications that offer the highly interactive
Guided Navigation user experience across a full range of structured and unstructured enterprise
data. Search applications leveraging Latitude Studio use Latitude technology to deliver the clearest
visibility into information, driving significant cost savings and increased revenue for our customers.
Lesson 4

1.4.3
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
n cforeapplication
ainterface
Intuitive
developers and administrators
i
m
l
e
l
Su
SOA (Service Oriented Architecture) framework for application integration
f
i
h Granular, role-based authorizations
Ka
Enables creation of personal user pages
Multi-language support
Extensible standards-based system for creating components
Lesson 4

1.4.4
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

1.4.5
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n set of standard components included with Latitude Studio that enable
an arelicaecore
Latitude components
m
out-of-the-box
le configuration of the initial search application and empower you to be more productive
u
S
quicker.
if Components are a planned concept to enable partners and 3 party Independent Software
h
Vendors (ISV) develop and customize components.
s
a
rd
Latitude Components:
Are JSPs that include all logic for

Retrieving/manipulating MDEX data
Rendering results
Provide specific features for specific market-oriented applications

For example in manufacturing, guided navigation, analytics result grid for Spend Analysis
Promotes high value functionality
Are included with the source license

Customers can extend component features and customize, if needed
Are self-contained and will contain all of their own custom business/event/data
retrieval/rendering logic
Lesson 4

1.4.6
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

1.4.7
Student Guide
Module 1
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en the components in your Latitude Studio implementation and power
anteamlchooses
The development
c
i
m
users typically
ule configuring their layout and certain functionality, such as analytics. Though end users
S
cannot
if configure the components directly, it is important that they are familiar with their functionality.
h
s
a
Lesson 4

1.4.8
Student Guide
Module 1
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
encharts, tables, and metrics-based components that are driven by
an several
Latitude studio
offers
c
i
m
l
e
analytics.
Analysts can include Endeca analytics statements in analytics-enabled
ulBusiness
S
f
components
to create powerful data visualizations for end users.
i
ash
Lesson 4

1.4.9
Module 1
Student Guide
le
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
Security Themes
m
ule - User credentials validated against external systems
Authentication
S
if Supports Active Directory / LDAP authentication
h
s
a
b
fera
Supports Multi-Domain Security (Single Sign-On)
Authorization: User and entitlement data maintained in and imported from source systems
Single point of control for operational simplicity
Enables rapid update of users and entitlements
Complex role expressions (AND, OR, NOT) enable dynamic query-time entitlement filters
System: Endeca builds on the security of the underlying OS and server
Set up separate user account for Endeca processes and data
Isolate Endeca servers from other network segments
Mutually-authenticated SSL to secure network traffic (if desired)
Endeca indices constitute a complete copy of the corpus:
Files on disk not encrypted
Rely on OS/network layers to protect sensitive data from unauthorized user access
Lesson 4

1.4.10
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

1.4.11
Ka
le
fS
i
h
s
u
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
n
a
r
t
nb
fera
Student Guide
Module 1
Latitude Core Concepts
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
anmin. licen
Lesson Time:
~20
m
ule
S
if
h
s
a
Lesson 5 Data Exploration

in a Latitude Application

1.5.1
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


1.5.2
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an youlicwillenbuild in this course is the same application used in the Latitude Getting Started
The sample application
m
leThis application uses data from a fictitious bicycle manufacturer named Adventure Works, and
Experience.
u
S
serves
if as the reference data set for Endeca Latitude. Included in the data set are financial and transactional
h
sales data, which support numerous business intelligence scenarios. The Latitude Sample application is
s
a
designed to enable you to quickly learn how to load data into Latitude, and then to explore the main features of
the front-end application powered by Latitude.


1.5.3
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n user types business analysts and end users. A business analyst is
eprimary
anhavelitwo
Latitude applications
c
m
le
typicallyu
responsible
for configuring Latitude Studio components and creating the pages or dashboards that end
S
users
access.
End
users
of Latitude applications are generally experts in their field of business, but not
f
i
h
technology specialists. Typically, end users rely on business analysts to create Latitude applications that enable
s
a
them to use discovery techniques to answer open-ended questions, and research and view their existing data in
new and powerful ways.
Because the Latitude Sample Application is shipped with the Latitude product as a teaching tool, this application
is designed to address a broad user audience. Toward that end, all components in this application are displayed
in business analyst mode with Preferences available. Note that in a live environment, end users are not able to
access component preferences for editing.


1.5.4
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


1.5.5
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enNavigation component, the tabs for different pages in the application
aofnthe Guided
Notice the position
c
i
m
l
leSales Overview, Products), and the Search box. The components on the left update are used to
(Welcome,
u
S
reveal
if information in the components on the right, such as when a record or value search is performed. Note
h
how search and navigation choices are tracked in the Breadcrumbs component.
s
a
Ideally, most applications will have the Search Box, Breadcrumbs and Guided Navigation down the left side of
the page.


1.5.6
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


1.5.7
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


1.5.8
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


1.5.9
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


1.5.10
Module 1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


1.5.11
Ka
le
fS
i
h
s
u
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
n
a
r
t
nb
fera
Student Guide
Module 2
Basic Data Design
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cen
Presentation:
~a
40 minutes
m
li
e
ulminutes
Lab: S
~50
if
h
s
a
Lesson 1
Project Basics with Latitude

2.1.1
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.2
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.3
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enIntegration System is composed of the Latitude Data Integrator
anInformation
The Latitude
c
i
m
l
leContent Acquisition System (CAS), and the Connector for Informatica PowerCenter.
(LDI), u
the
S
Additional
third-party ETL connectors may be added in the future.
if
h
s
a
CAS includes the Endeca Web Crawler and the Endeca CAS Server, as well as a rich set of
packaged adapters. These components allow you to create and manage a set of file system,
Content Management System (CMS), and Web crawls. Packaged adapters reach the most
common systems, including JDBC and ODBC. The Content Adapter Development Kit (CADK)
allows developers to write custom adapters and Java manipulators.
Data and configuration are ingested using the Latitude Data Integrator. Examples of
configuration information are:
Which fields to enable for text search
Which options will be available for browsing and refining
Precedence rules
The MDEX engine, the core of the Latitude solution, loads the index into memory at start-up.
Once the MDEX engine is online, it is ready to handle queries from Endeca-powered Web
applications.
Latitude Studio is the tool used to create and configure an Endeca front-end application. A
Latitude Studio application is configured to query the MDEX Engine via the Conversation Web
Service. This capability is built into the various Latitude Studio components (e.g., search box,
breadcrumbs, guided navigation, results list).
Lesson 1

2.1.4
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an intolictheenMDEX via the Data Ingest Web Service or the Bulk Load Interface. The
Data is ingested
m
le Integrator comes with Latitude Connectors which interact with these services.
Latitude
uData
S
if Configuration is ingested into the MDEX via the Configuration Web Service. This is done using
h
s
a LDI components that that use the Configuration Web Service to communicate with the MDEX
Engine. The Configuration Web Service is used to configure the record schema and MDEX Engine
features.
A Latitude Studio application is configured to query the MDEX Engine via the Conversation Web
Service. This capability is built into the various Latitude Studio components (e.g., search box,
breadcrumbs, guided navigation, results list).
The Administration Web Service is used by IT engineers and administrators to integrate the
MDEX Engine server and its reporting with third-party IT tools (e.g., monitoring and backups). This
service interacts with the MDEX Engine server outside of the MDEX Engine data layer, while the
other Endeca Web services interact with the indexes within the MDEX Engine data layer.
Lesson 1

2.1.5
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.6
Student Guide
Module 2
Basic Data Design
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enis based off CloverETL Designer technology. The Designer and the
an Integrator
c
i
m
The Latitude
Data
l
le rely on the Engine library to assemble and execute graphs. All products build on
uproducts
Server
S
if Java platform.
the
h
s
a
Lesson 1

2.1.7
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.8
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.9
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.10
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.11
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.12
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.13
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.14
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.15
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.16
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.17
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.18
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n Integrator, it will first ask which workspace to use. Within the
eData
athenLatitude
When starting
c
i
m
l
workspaces,
ule projects are defined and used to manage work across the whole Eclipse platform.
S
Itifis important to define the project structure carefully, because other plugins may want to access
h
s
a
your project (e.g. version control), and changes to project descriptors may affect Designer or
Eclipse behavior.
Lesson 1

2.1.19
Student Guide
Module 2
Basic Data Design
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n which may be project specific For example, when testing it is
efolders
anotherlisub
It is usual to
add
c
m
le to add an mdex sub folder where the dgraph log files would then appear in the
not unusual
u
S
project.
Config-in is also usually created to store configuration input files.
if
h
s
a
Lesson 1

2.1.20
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.21
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.22
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.23
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
Navigator pane
m
le Each project contains folders such as data-in (input data files) and graph (pipeline
uprojects;
Lists
S
ifof components that process the data)
h
s
a
Graph Editor pane
Where you create a graph/pipeline and configure its components
Palette pane
List of components available for use in building a graph:
Readers
Transformers
Joiners
Writers
Latitude components
Add/Update Records
Bulk Add/Replace Records
Add KVPs
Add Managed Values
Delete Data
Palette pane also provides functionality to connect components and define metadata.
Lesson 1

2.1.24
Module 2
Basic Data Design
Student Guide
Outline pane
Components used in graph, metadata defined in graph, connections defined (DB, JMS,
QuickBase)
Tab pane
Report windows for Properties, Console (reports output of running a graph), Problems, CloverETL
Regex Tester, CloverETL Graph tracking, CloverETL Log
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.25
Student Guide
Module 2
Basic Data Design
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en these steps, see the Latitude Data Integrator Designer Guide.
aonnhowltoiccomplete
For information
m
ule
S
if
h
s
a
Lesson 1

2.1.26
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
eofn records in which every two adjacent fields are separated from each
anis theltype
Delimited. m
This
c
i
other by
ulaedelimiter and the whole record is terminated by record delimiter as well.
S
if
h
s
a
Fixed. This is the type of records in which every field has some specified length (size). It is
counted in numbers of characters.
Mixed. This is the type of records in which fields can be separated from each other by a delimiter
and also have some specified length (size). The size is counted in number of characters. This
record type is the mixture of the two cases above. Each individual field may have different
properties. Some fields may only have a delimiter. Others may have specified size. The rest of
them may have both delimiter and size.
Lesson 1

2.1.27
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.28
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.29
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.30
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.31
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.32
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.33
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.34
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.35
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.36
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.37
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.38
Module 2
Basic Data Design
le
b
fera
n
a
r
t
n-
i
ash
Student Guide
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n values
n cedefault
mkmdexacommand
i
m
l
le
Su--bulk-_load_port = http port + 1
--threads = 2
Note: The Latitude Sample Application has graphs with built-in scripts for deletion and re-creation of
the MDEX and running of a dgraph. Investigate the InitMDEXWindows or InitMDEXLinux graphs
for detailed information. These scripts can be modified for your purposes. They are intended for
testing; usually you will develop separate scripts for production use.
Lesson 1

2.1.39
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
etonthe MDEX installation/bin on your path you need to specify it in your
anthe path
If you do notm
have
c
i
l
command
uleto point to where the mkmdex command exists (e.g. c:\Endeca\MDEX\7.1.0\bin)
S
if The bulk load port defaults to the HTTP port + 1 (e.g. 77767777); the default number of
Note:
h
s
a
threads is two.
Lesson 1

2.1.40
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
ento modification. This is the process implemented by the Latitude
an is subject
Note: This process
c
i
m
l
le
SampleuApplication.
Your application may apply different logic e.g. You may do the above process
S
f
occasionally
(which would be equivalent to a complete Baseline Update for earlier versions of the
i
ashMDEX engine). However you may run incremental processes for revising data and metadata in
between (roughly equivalent to a Partial Update in earlier releases).
Lesson 1

2.1.41
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

2.1.42
Student Guide
Module 2
Basic Data Design
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en
anminutes
Presentation:
~25
c
i
m
l
e
ulminutes
Lab: S
~30
if
h
s
a
Lesson 2
Working with Latitude Studio

2.2.1
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

2.2.2
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

2.2.3
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

2.2.4
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
eLatitude
anto access
Before attempting
Studio, ensure that you have started the application server
c
i
m
l
e
l
instance
with
Latitude
Studio
loaded
on
it.
u
S
f
i email address and password provided on this slide are the defaults. For information on how to
The
ash
change the credentials, see the Latitude Studio Users Guide.
Note: Latitude Studio 2.x is compatible with Microsoft Internet Explorer 8.0( with compatibility mode
disabled), Mozilla Firefox 3.6 and Firefox 6.
Lesson 2

2.2.5
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
etonvarious commands and menus in the portal. Some of these will be
anaccess
The Dock provides
c
i
m
l
covereduinle
greater detail later in this lesson.
S
f
i
ash
Note: Only business analysts can see these menu items, unless end user permissions have been
configured otherwise.
Lesson 2

2.2.6
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n which can completely transform the look and feel of the pages in
n ceplugins
Themes are m
hotadeployable
i
l
your Latitude
ule Studio application. Most organizations have their own standards for look and feel, which
S
they
if tend to use across all Web sites and Web applications in their infrastructure. Themes make it
h
s
a possible for a site designer to customize a companys Latitude Studio application and align its look
and feel with those of existing applications.
The Latitude Studio includes one theme out of the box; however, there are several theme plugins
available on Liferay's web site. Choosing a Liferay theme that closely resembles what you want to do
and then customizing it is much easier than building a theme from scratch. For more information on
theme development, see the Liferay Developer's Guide.
To configure your Latitude Studio applications theme, go to the Manage Pages page (accessible
through the Dock menu) and click the Look and Feel tab.
Lesson 2

2.2.7
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

2.2.8
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en
anthe portal:
To add a page
to
c
i
m
l
le Add Page.
1.Su
Click
hif2. Type the name for the new page in the yellow textbox.
Ka
3. Click Save or press Enter.
Note: Only business analysts can add pages, unless end user permissions have been configured
otherwise.
Lesson 2

2.2.9
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
Ka
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
entool that provides pre-determined page arrangements for component
anis alportal
A Layout Template
c
i
m
placement
uleon a page. Each template divides the body of a portal page in various ways, providing a
S
f of sorts, into which you drag, drop and arrange your components. The Latitude Studio ships
container
shi
with 10 layout templates from which you can choose; however, if you have a complex page layout,
you may wish to create a custom layout template of your own.
To access the Layout Template tool, click Layout Templates in the Dock drop-down menu.
Lesson 2

2.2.10
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n you to add components (and other features/tools) to the Latitude
eenables
an menu
The Add Component
c
i
m
l
Studio portal.
ule The Add Component menu provides access to Content Management features, the
S
Latitude
if standard components, Layout Control components, and Tools.
h
s
a
To access the Add Component list, choose Add Component from the Dock drop-down menu. To add
components to your portal page, drag a component onto the main page layout or click Add.
Lesson 2

2.2.11
Student Guide
Module 2
Basic Data Design
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
anpagelicinethen lab that accompanies this lesson.
You will create
this
m
ule
S
if
h
s
a
Lesson 2

2.2.12
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

2.2.13
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

2.2.14
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

2.2.15
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
an licecomponent
The Guidedm
Navigation
provides classic "left hand" navigation for end users. In
e
l
this component,
attributes are grouped, and only a single managed attributes refinements are
Su to the end
f
i
available
user at any given time via fly out menu.
ash
The Guided Navigation component can enable end users to expand and/or close multiple
attribute groups; view values for a single attribute at a time via fly out menu; and utilize the
Submit Selections control for multi-OR/multi-AND attributes (i.e., selections not submitted on
checkbox select).
Lesson 2

2.2.16
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enthe Guided Navigation component, power users can configure
an page
On the Preferences
for
c
i
m
l
component
ulebehavior and manage attribute groups.
S
if
h
s
a
For information on how to configure this component, see the Latitude Studio Users Guide.
Lesson 2

2.2.17
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
ensummarizes any Guided Navigation selections, keyword searches, or
ancomponent
The Breadcrumbs
c
i
m
l
range filters
ule that have been specified.
S
if
h
s
a
Business analysts need only select a data source to configure the Breadcrumbs component for use.
Lesson 2

2.2.18
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n end users to type in a keyword for searches in Latitude Studio. It
n ceallows
acomponent
The Search Box
i
m
l
also offers
uletype-ahead functionality, which is designed to provide end users with suggestions for their
S
search
if as they type. Provided suggestions are based on available attributes in the data source
h
s
a selected for that component, and they are clickable; in other words, end users can choose to click a
suggestion in the type-ahead list to view the results.
End users may also choose to select the Search within Results checkbox, which will limit their search
to the results that are currently displayed.
Lesson 2

2.2.19
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enthe Search Box component, power users can configure search interfaces
an page
On the Preferences
for
c
i
m
l
and type-ahead
ule behavior.
S
if
h
s
a
Lesson 2

2.2.20
Student Guide
Module 2
Basic Data Design
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
n cedisplays
The Results m
Listacomponent
a list of records reflecting the current refinement state in a list
i
l
e
l
format similar
to
web
search
results.
Su
f
i
ash
Lesson 2

2.2.21
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enthe Results List component, business analysts can configure display
an page
On the Preferences
for
c
i
m
l
configuration
ule and sorting options as well as design the Results Template (pictured).
S
if
h
s
a
Lesson 2

2.2.22
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

2.2.23
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

2.2.24
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

2.2.25
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en
an Panel:
To access the
Control
c
i
m
l
le
1.Su
Point to the Dock in the upper-right corner of the page. A drop-down menu displays.
hif2. Choose Control Panel from the drop-down menu.
Ka
Lesson 2

2.2.26
Student Guide
Module 2
Basic Data Design
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en business analysts to view configured data sources and test their
anpageliallows
The Data Sources
c
m
connection
uleto them. End users have the ability to reload updated configurations.
S
if sources colored red are not active (have no MDEX engine currently running on that port)
Data
h
s
a
Lesson 2

2.2.27
Student Guide
Module 2
Basic Data Design
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cenBindings area to configure which data source your components use.
You can usem
theaData Source
li
le
u
fS
i
h
as
Lesson 2

2.2.28
Student Guide
Module 2
Basic Data Design
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n the power user to select a data source; to create, edit, and delete
eallows
an page
The Attributem
Settings
c
i
l
le and to change display names for any attribute in a selected data source.
attributeugroups;
S
if
h
s
a
Lesson 2

2.2.29
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

2.2.30
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
Timings
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
Su
f
i
shLab: ~40 minutes
Presentation: ~55 minutes
Ka
Lesson 3
Data Modeling and Joining Data

2.3.1
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.2
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.3
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.4
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.5
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.6
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.7
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.8
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.9
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.10
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.11
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.12
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.13
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.14
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.15
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.16
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.17
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.18
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.19
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en is an industry jargon term for a type of measure of performance.
an licIndicator
* KPI = Keym
Performance
ule
S
f
shi
Ka
Lesson 3

2.3.20
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en is an industry jargon term for a type of measure of performance.
an licIndicator
* KPI = Keym
Performance
ule
S
f
shi
Ka
Lesson 3

2.3.21
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.22
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.23
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.24
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.25
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.26
Student Guide
Module 2
Basic Data Design
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n statements be sure you are rolling up (Group By) the correct grain
eanalytics
an your
When you are
writing
c
i
m
l
lecalculations are accurate.
so that u
your
S
if
h
s
a
Lesson 3

2.3.27
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.28
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.29
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.30
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.31
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.32
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.33
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.34
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.35
Student Guide
Module 2
Basic Data Design
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n memory, then for each row of each subsequent source, does an
einto
anslaves
A hash join m
reads
c
i
l
in-memory
ulelookup to find a matching row in the first source. This is works when the slaves
S
if small enough to fit into memory, and doesnt require anything to be sorted.
are
h
s
a
Lesson 3

2.3.36
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.37
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enshared records are processed. With this type of join only the records that
an that
An inner joinm
ensures
all
c
i
l
le
have alluproperties
from all sources will be processed. In the above example notice that the record
S
f
i ID=B and ID=E both get discarded because they do not contain all values.
hwith
Ka
Lesson 3

2.3.38
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.39
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n to determine which records get processed. In the example above
esource
anfirst ldata
A left join uses
the
c
i
m
all records
ulefrom Data Source 2 that have a corresponding record in Data Source 1 are merged and
S
processed.
Since the record with ID=E in Data Source 2 does not have a corresponding record in
if
h
s
a Data Source 1 it is not processed.
Note that a join in LDI does result in null columns it is only when the data is loaded into the MDEX
that missing attributes will occur where data is null.
Lesson 3

2.3.40
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.41
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enrecords from both data sources get processed. After the join, some
an that
An outer joinm
ensures
all
c
i
l
le not have values for all properties. This occurs when a record in one data source does not
recordsu
may
S
if a corresponding record in the other data source.
hhave
Ka
Lesson 3

2.3.42
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cen to read in FactSales data
1. Instantiate
aareaderlcomponent
i
m
le a reader component
u
2. Instantiate
to read in DimDate data
S
f
i
h3. Connect FactSales reader components output to the master input port of the ExtHashJoin
Ka
component
4. Connect the DimDate reader components output to the slave input port of the ExtHashJoin
component
5. Double-click the ExtHashJoin component.
6. Select Inner join from the drop-down menu
7. Click in the value field for Join key and then click the ellipsis
8. Drag and drop the appropriate slave field to the Slave Key field column
9. Click OK
10. Click in the value field for Transform and then click the ellipsis
11. Left-click all rows in the Field column
12. Click Auto-rules
13. Verify Transformations are defined
14. Click OK
Lesson 3

2.3.43
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
Ka
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n sources to be sorted, and finds matching rows by just reading
edata
an lall
A merge join
requires
c
i
m
e from each source and seeing if the keys match, and keeping on reading rows
the next
ulrow
S
if each source it finds a non-matching row. This has the advantage of working even if all
shfrom
the data sources are too big to fit into memory, but requires them to be sorted.
Lesson 3

2.3.44
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.45
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.46
Student Guide
Module 2
Basic Data Design
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
ena Joiner component as it is found on the Transformers component tab,
an speaking
Although notm
strictly
c
i
l
the DataIntersection
can be considered to be a type of join.
ule
S
f
i
ash
Lesson 3

2.3.47
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.48
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.49
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.50
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.51
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.52
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.53
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en
an lrepresentation
Star schemam
= Generic
of a dimensional model in a relational database
c
i
e
l
ufor the bulk ingest LDI component to submit records into the MDEX engine it requires a
In order
S
f
i
unique identifier, a record specifier, for each record. For this project the record specifier is defined as a
ash
transform in the FactSales_SalesTransaction data.
It is defined to be FactSales_RecordSpec and is the concatenation of FactSales_SalesOrderNumberFactSales_SalesOrderLineNumber.
Lesson 3

2.3.54
Module 2
Basic Data Design
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3

2.3.55
Ka
le
fS
i
h
s
u
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
n
a
r
t
nb
fera
Module 3
Search and Navigation
Configuration Enhancements
Student Guide
le
b
fera
n
a
r
t
n-
Timing
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
Su
f
i
shLab: ~90 minutes
Ka
Lesson 1
Introduction to Search

3.1.1
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.2
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.3
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licareenmapped to lower case equivalents because Endeca search indexing is
Note: Capitalm
characters
always
ule case-folded.
S
if
h
s
a
Lesson 1

3.1.4
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n interface to search across for a match
n coresearch
Search Key:m
Anaattribute
i
l
le Mode: Criteria for a record to be successfully matched, based on the number of terms
uMatch
Search
S
if
h
Search Terms: One or more search terms entered by the end user
s
a
Lesson 1

3.1.5
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en
anmethod:
Alternative ingest
c
i
m
l
le
1.Su
Read in XML directly using a UniversalDataReader LDI component
if2. Ingest the XML directly into the MDEX using the Add/Update Records LDI component(see LDI
h
s
a
Guide documentation for details) OR
3. Ingest the PDR into the MDEX using the WebServiceClient LDI component
Lesson 1

3.1.6
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.7
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.8
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cen by default and record search is disabled by default. You may want to disable
Notice that valuea
search isienabled
m
l
lefor specific managed
value search
attributes to avoid unnecessary MDEX performance degradation.
u
S
f
The
i Type property is set to mdex:string by default but also supports the following data types: mdex:boolean;
ashmdex:dateTime; mdex:double; mdex:int; mdex:long; mdex:duration; and mdex:geocode. The Selectability
property can also be set to Multi-AND or Multi-OR. The Sortability property has one other option: Lexical.
PDR Property Names
Key = mdex-property_Key
Display Name = mdex-property_DisplayName
Type = mdex-property_Type
Value Search Enabled = mdex-property_IsPropertyValueSearchable
Single Assign = mdex-property_IsSingleAssign
Record Search Enabled = mdex-property_IsTextSearchable
Is Unique = mdex-property_IsUnique
Wildcard Record Search Enabled = mdex-property_TextSearchAllowsWildcards
Selectabilty = system-navigation_Select
Show Record Counts = system-navigation_Select
Sortability = system-navigation_Sorting
For more information, see the Data Ingest Guide.
Lesson 1

3.1.9
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
DDR Property
Names
m
ule
Key =Smdex-dimension_Key
if for display in Guided Navigation component = mdex-dimension_EnableRefinements
h
s
Enabled
a
Enabled for hierarchical value search = mdex-dimension_IsDimensionSearchHierarchical
Enabled forhierarchical record search = mdex-dimension_IsRecordSearchHierarchical
For more information, see the Data Ingest Guide.
Lesson 1

3.1.10
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cenfrom the Getting Started Experience (GSE) sample application and can
Example on m
thea
slide isltaken
i
lea starting point.
be useduas
fS
i
h
as
Alternative ingest method:
1. Read in XML directly using a UniversalDataReader LDI component

2. Ingest the XML directly into the MDEX using the Add/Update Records LDI component
Lesson 1

3.1.11
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en the transformation of metadata based on the input metadata. This is
an tolidefine
The developer
needs
c
m
e slide using CTL (Clover Transformation Language).
shown in
ulthe
S
if
h
s
a
Lesson 1

3.1.12
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enWSDL URL (e.g., http://localhost:5555/ws/config?wsdl
atonconfigure:
Required inputs
c
i
m
l
le
uStructure:
Request
The Edit Request structure dialog reads in an xml string that is generated by the
S
f
i
Create Search Interface (Denormalizer) component.
ash
Lesson 1

3.1.13
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.14
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enDenormalizer is introduced into the graph to batch web service requests
anRequests
Note that them
Build
c
i
l
based upon
ule a generated singleAggregateKey value calculated if required in the Reformat (Make
S
Attributes
Searchable) component.
if
h
s
a
Lesson 1

3.1.15
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.16
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.17
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enPrecedence Rules are now submitted by submission of a record type,
an 2.2
* Note that inm
Latitude
that
c
i
l
not an Index
ule Configuration Document.
S
if
h
s
a
Lesson 1

3.1.18
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.19
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.20
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en
ancan lbeicconfigured
A search interface
with one or more search interface members. RelRank strategies
m
le before Search Interfaces via LDI graphs for both record searches and value searches.
must beuloaded
S
f technique
The
is similar.
i
h
s
Ka
Lesson 1

3.1.21
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en
anmethod:
Alternative ingest
c
i
m
l
le
1.Su
Read in XML directly using a UniversalDataReader LDI component
if2. Ingest the XML directly into the MDEX using the WebServiceClienLDI component(see the LDI
h
s
a
MDEX Component Guide for details)
Lesson 1

3.1.22
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en definition, only the AttributeName field is used. Both fields are
an attribute
Note: for searchable
c
i
m
l
used when
uledefining search Interfaces
S
if
h
s
a
In this case you are reading in only a list of 1 attribute, SurveyResponse.
Required input: Define the full pathname (File URL) for the file to be read (e.g. SearchAttributes.txt
found in the data-in directory in the LDI project).
Lesson 1

3.1.23
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
ea <MEMBER_NAME>
ancreates
This denormalizer
element for each attribute listed in the input file
c
i
m
l
e
l
provided
in
the
SearchableAttributes.txt
file
read
in from the UniversalDataReader component.
u
S
f
i
Required
inputs to configure: Key, denormalize transformation
ash
Lesson 1

3.1.24
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en WSDL URL (e.g., http://localhost:5555/ws/config?wsdl
anto configure:
Required inputs
c
i
m
l
e
ulStructure:
Request
The Edit Request structure dialog defines a search interface named all that
S
f
i
contains all the members defined by the XML generated by the Create Default
ash
Search Interface (Denormalize) component.
Sample of a resulting recsearch_config XML document generated by a similar LDI graph (Item in bold
would be the $xmlString contents):
<config-service:putConfigDocuments xmlns:configservice=http://www.endeca.com/MDEX/config/services/types
xlms:mdex=http//www.endeca.com/MDEX/Xquery/2009/09>
<mdex:configDocument name=recsearch_config>
<RECSEARCH_CONFIG>
<SEARCH_INTERFACE CROSS_FIELD_BOUNDARY=NEVER CROSS_FIELD_RELEVANCE_RANK=0
DEFAULT_RELRANK_STRATEGY=WineRelRank NAME=All>
<MEMBER_NAME RELEVANCE_RANK=1>SurveyResponse</MEMBER_NAME>
</SEARCH_INTERFACE>
</RECSEARCH_CONFIG>
</mdex:configDocument>
</config-service:putConfigDocuments>
Lesson 1

3.1.25
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.26
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.27
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n apply to record searches with multiple search terms specified.
eonly
anmatches
Note: Cross-field
c
i
m
l
ule
S
if
h
s
a
Lesson 1

3.1.28
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.29
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.30
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
eoperations
ansearch
By default, Endeca
match user query terms to entire words in the indexed text.
c
i
m
l
e
l
Su
f
i
h
Ka
Lesson 1

3.1.31
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en members of a search interface are enabled for wildcard search,
an oflisearch
Note: If onlym
a subset
c
wildcard
ule search only works for those members as configured.
S
if
h
s
a
Wildcard Search Performance Impact:
Enabling wildcard search generally increases the time and disk space required for indexing. To
optimize performance, the MDEX Engine performs wildcard indexing for words that are shorter
than 1024 characters.
Refer to the Latitude Developers Guide chapter Using Wildcard Search for more details.
Lesson 1

3.1.32
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.33
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.34
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enbuilt from electronic dictionaries, and each language is stored in a
aarenXMLlifiles
Stemming files
c
m
e
separate
ulfile.
S
if
h
s
a
Performance Impact:
Stemming and thesaurus equivalences generally add little or no time to data processing and
indexing,and introduce little space overhead (beyond the space required to store the raw string forms
of the equivalences).
In terms of online processing, both features will expand the set of results for typical user queries.While
this generally slows search performance (search operations require an amount of time that grows
linearly with the number of results), typically these additional results are a required part of the
application behavior and cannot be avoided.
The overhead involved in matching the user query to thesaurus and stemming forms is generally low,
but could slow performance in cases where a large thesaurus (tens of thousands of entries) is asked
to process long search queries (dozens of terms). Typical applications exhibit neither extremely large
thesauri nor very long user search queries.
Because matching for stemming entries is performed on a single-word basis, the cost for stemmingoriented query expansion does not grow with the size of the stemming database or with the length of
the query.
Lesson 1

3.1.35
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n for baby only returns the 212 results for baby. A search for
n caesearch
adisabled,
With Stemming
i
m
l
le returns the 37 results for babies.
babies u
only
S
if
h
s
a
With Stemming enabled, a search for either baby or babies returns all 249 results for baby & babies.
Lesson 1

3.1.36
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.37
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en you to explicitly enumerate all thesaurus entries for each specific
an lirequires
The Endecam
Thesaurus
c
MDEX configuration.
The Thesaurus also works with an XML file that can be externally generated or
ule
S
f
modified.
Slang and acronyms are both great reasons to use Thesaurus entries on your site.
i
ash
One-way XML construct:
<THESAURUS>
<THESAURUS_ENTRY_ONEWAY>
<THESAURUS_FORM_FROM>California</THESAURUS_FORM_FROM>
<THESAURUS_FORM_TO>Sonoma</THESAURUS_FORM_TO>
<THESAURUS_FORM_TO>Napa</THESAURUS_FORM_TO>
</THESAURUS_ENTRY>
</THESAURUS>
Two-way XML construct:

<THESAURUS>
<THESAURUS_ENTRY>
<THESAURUS_FORM>United States</THESAURUS_FORM>
<THESAURUS_FORM>USA</THESAURUS_FORM>
</THESAURUS_ENTRY>
</THESAURUS>
Lesson 1

3.1.38
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n a one-way
en thesaurus entry has been created from California to Sonoma &
asince
In this example,
c
i
m
l
Napa, when
ule a user searches for California they will get all 255 results for all three terms: California,
S
Sonoma
if & Napa. Yet, if they search for either Sonoma or Napa (the other side of the one-way
h
s
a entry), they get the same individual results they would get without a thesaurus entry.
Lesson 1

3.1.39
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n a two-way
en thesaurus entry has been created for United States and USA, when
asince
In this example,
c
i
m
l
a user searches
ule for United States they will get all 131 results for both United States & USA. The
S
same
if is true if the user searches for USA.
h
s
a
Lesson 1

3.1.40
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.41
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n expansion
en can potentially impact the results sets & possibly performance; for
athe
Be aware of m
how
c
i
l
e end result for an initial search on cab returns matches for cab, cabs, cabernet, and
example,
ulthe
S
if
hcabernets.
Ka
Lesson 1

3.1.42
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.43
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.44
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enphrases enclosed in quotes. All words between quotes are treated as a
anotnremoved
Stop words are
c
i
m
l
single search
ule term.
S
if
h
s
a
Lesson 1

3.1.45
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.46
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an : licen
Spelling Correction
m
le of the MDEX Engine to return expected search results even when the user misspells
uability
The
S
if or more of the query terms.
one
h
s
a
Endeca provides two spelling correction features: Auto-Correct (for record & value search), DidYou-Mean (for record search only).
The MDEX Engine auto-computes alternate spellings for user query terms returning zero results.
Lesson 1

3.1.47
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
Did-You-Mean:
m
le of the MDEX engine to provide alternative suggestions for searched terms resulting in
uability
The
S
if matches than the threshold. It is always enabled. The threshold is 30. The number of
fewer
h
s
a
suggestions is 1. It is currently not configurable in the MDEX.
Lesson 1

3.1.48
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.49
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
Ka
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enterms the user provides along with a portion of the surrounding content
anthe search
A snippet contains
c
i
m
l
to provide
ulecontext.It is used on individual members of a search interface that contain many lines of
S
f (e.g., Description, Abstract, etc.) It allows the user to more quickly choose individual records
content
shi
of interest. Snippeting is enabled in the recsearch_config XML configuration document. . For details
refer to the Developers Guide and the LDI MDEX Components Guide.
Match Modes: MatchAll, MatchPartial*, MatchAny, MatchAllAny, MatchAllPartial*, MatchPartialMax*,

MatchBoolean
The value of some" for partial match modes is defined in the recsearch_config index XML
configuration document (as part of the search interface definition). For details refer to the Data Ingest
Guide.
The standard alphanumeric characters for English are a-z, A-Z, and 0-9. Non-alphanumeric
characters considered to be punctuation are: !@#&()_[{]}:;,?/* and are treated as whitespace by
default. Non-alphanumeric characters considered to be symbols are: `~$^+=<> and are treated as
whitespace by default. For details refer to the Latitude Developers Guide.
Lesson 1

3.1.50
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 1

3.1.51
Ka
le
fS
i
h
s
u
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
n
a
r
t
nb
fera
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
Timing
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
Su
f
i
shLab: ~75 minutes
Ka
Lesson 2
Enhancing Navigation

3.2.1
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.2
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.3
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
edisplaying
anto control
A second method
some attributes (managed attributes ONLY) is by disabling the
c
i
m
l
e
l
mdex-dimension_EnableRefinements
property in the DDR. This disables the refinement
u
S
f
computation
in the MDEX engine entirely.
i
ash
Lesson 2

3.2.4
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
eisnset on by default for both standard and managed attributes. This is
an counts
Enabling refinement
c
i
m
l
definedu
inle
the PDR (system-navigation_ShowRecordCounts). For relatively simple applications
S
f
this
i can be very useful. However, for applications with complex data, refinement counts may
ashnot refer to anything obvious to the user. This is because the refinement counts are
computed in terms of the physical Endeca record data model which the application often
never shows this to the end users (e.g., via record lists, charts, etc.). Instead, analytics are
used to roll up the physical records into more meaningful entities.
Lesson 2

3.2.5
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cenmanaged or standard, can be sorted in the guided navigation
Refinementsm
foraany attribute,
lein two ways:liby record count (aka dynamic ranking) or lexically. You can configure this
component
u
programmatically
at data ingest time by setting the system-navigation_Sorting property on the
fS
i
h
s
a PDR for each attribute, or configure it manually after the fact in the Latitude Studio Attribute Settings
component.
Lesson 2

3.2.6
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enallows control of the maximum number of managed attribute values
an Ranking
Dynamic Refinement
c
i
m
l
le from a navigation query. It ranks managed attribute values according to the number
that getu
returned
S
f
ofirecords
associated with a refinement or alphabetically. Dynamic Refinement Ranking is very useful
h
s
a for managed attributes with many managed attribute values and can be configured on a attribute by
attribute basis.
With the application displayed above, notice that Michael G Blythe is first in the refinement list for
Male employees while Jillian Carson is first in the list for Female employees.
Lesson 2

3.2.7
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
eofnrefinements that appear for an attribute. If an attribute, managed
annumber
You can limit
the
c
i
m
l
or standard,
ule has a lot of values, you often want the Guided Navigation component to show
S
if the first few attribute values and then display a more link. This is true regardless of
only
h
s
a
how the refinements are sorted, or whether youre showing refinement counts in parentheses
after the refinement text. You configure this in the preferences menu of the Guided
Navigation component in Latitude Studio.
Lesson 2

3.2.8
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.9
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.10
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.11
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en (standard or managed) as the Source for a Precedence Rule, the
an anliattribute
When specifying
c
m
Target attribute
ule will become visible after any attribute value of the Source attribute has been refined
S
on.
if
h
s
a
In this example, once you select any country, the State/Province attribute will become visible.
Also, once you select any State/Province, the City attribute will become visible.
Lesson 2

3.2.12
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.13
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en value as the Source for a Precedence Rule, the Target attribute will
an anliattribute
When specifying
c
m
le only after the specified attribute value of the Source attribute has been refined on.
becomeuvisible
S
ifIn the above example, the Resolution attribute will only become visible when you select Digital
h
s
a
Cameras from the list of Categories. Whereas the Processing Speed attribute will only become
visible when you select Computers from the list of Categories.
Lesson 2

3.2.14
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.15
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.16
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.17
Module 3
Student Guide
le
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n reading
einnonly a list of 2 precedence rules
aare
In this case you
c
i
m
l
ule
S
if
h
DimGeography_StateProviceCode > DimGeography_City
s
a
b
fera
DimGeography_StateProviceName > DimGeography_City
Required input: Define the full pathname (File URL) for the file to be read (e.g. PrecedenceRules.csv
NOTE: any file format that you can read in and convert to the required Precedence Rule record format
is acceptable
Lesson 2

3.2.18
Module 3
Student Guide
le
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n reading
einnonly a list of 2 precedence rules
aare
In this case you
c
i
m
l
ule
S
if
h
DimGeography_StateProviceCode > DimGeography_City
s
a
b
fera
DimGeography_StateProviceName > DimGeography_City
Required input: Define the full pathname (File URL) for the file to be read (e.g. PrecedenceRules.csv
Lesson 2

3.2.19
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n structure for the precedence rule for each trigger -> target data
n thecerecord
acreates
This Reformat
i
m
l
leprovided (PrecedenceRules.csv) and read in from the UniversalDataReader component.
listed inufile
S
if
h
s
a
Required inputs to configure: transform (written in CTL)
Lesson 2

3.2.20
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
encreates the list of precedence rule records.
ancomponent
This Denormalize
c
i
m
l
e to configure: transform (written in CTL)
ulinputs
Required
S
if
h
s
a
Lesson 2

3.2.21
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enWSDL URL (e.g., http://localhost:5555/ws/config?wsdl
atonconfigure:
Required inputs
c
i
m
l
le
uStructure:
Request
The Edit Request structure dialog defines a precedence rule that contains all the
S
f
i
record list generated by the Reformat component.
ash
Lesson 2

3.2.22
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.23
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.24
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.25
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.26
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.27
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.28
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en list, in the Key for a new group text box, type the name of the group
an liGroups
1. Under the
Attribute
c
m
e NCName compliant).
(must
ulbe
S
2.ifIn the Display name for a new group field, type the display name (does NOT need to be
h
s
a
NCName compliant).
3. Click Add.
4. In the All Attributes, list check the attributes you want to add to the group.
5. From the Add selected attributes to group drop-down list select the group.
6. Click Add.
Lesson 2

3.2.29
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n care
enconfigured in Latitude Studios Attribute Settings component. They are
Default orderm
ofa
attributes
i
l
le group basis.
set on auper
S
if new Latitude Studio components that use groups (e.g., Guided Navigation, Record Details,
For
h
s
a
Compare) this default display order will be used. The Power User can configure a different display
order for individual components using the preferences option for that component.
Lesson 2

3.2.30
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cfrom
ena group, it is restored as a member of the default Other group. When
If you deletem
ana
attribute
i
l
you attempt
uleto delete an attribute group you will be prompted to confirm the deletion because this
S
action
if cannot be undone. However, you can recreate the attribute group and reselect attributes to be
h
s
a added to it.
Lesson 2

3.2.31
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.32
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.33
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.34
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.35
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.36
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.37
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
erequired
anformat
This data structure
is
by the Add Managed Values Latitude component. Required
c
i
m
l
e
l
metadata
definition
is
to
be
found
in
the
Getting Started project.
u
S
f
i
ash
You can use your own custom import formats if you use the Web Service component and generate
the required XML request structure through your own custom logic. This may be required if you wish
to add custom properties to each hierarchical value (not currently supported by Latitude Studio
standard components).
Lesson 2

3.2.38
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.39
Student Guide
Module 3
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n work if all expected data values for the managed attribute are
eonly
an liwill
Note that thism
approach
c
represented
ule in the taxonomy structure read by the Read Taxonomy component.
S
if
h
s
a
Lesson 2

3.2.40
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.41
Module 3
Student Guide
le
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
This example creates
hierarchical managed attribute of the form:
en
an a Restaurant_Cuisine
c
i
m
l
e
<Static Hierarchy
read
by
the
Read
Static
Taxonomy
component>
ul
S
if
h
s
a
b
fera
American
Traditional
Regional
Asian
Chinese
Thai
European
Italian
Italian South
Italian North
French
Others ...
<Generated list of values from data output by AutoGen Taxonomy component>

The source data record is in the format:
Note: In the diagram, the Normalize Cuisines component splits the Cuisine field below into separate Cuisines.
This operation is not required if your data has single values for Cuisine stored in the field.
Restaurant_Name
Fred's Diner
Gastropod
Herges
Cuisine
American:Regional:French
Italian: Italian North
German
Lesson 2

3.2.42
Module 3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2

3.2.43
Ka
le
fS
i
h
s
u
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
n
a
r
t
nb
fera
Student Guide
Module 4
Advanced Topics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
anmin. licen
Lesson Time:
~40
m
ule
S
if
h
s
a
Lesson 1 Data Ingest

and Modeling Overview

4.1.1
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.2
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.3
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en we have chosen to have a unique record for each color variation of
an separation,
In the first example,
c
i
m
l
vest. Perhaps
ule there is a unique order amount or inventory total for each of these items. In our data
S
source,
if our data may already be organized this way. Or we may split it apart into individual records
h
s
a when we extract the data or during the ETL process.
In the second example, consolidation, we have chosen to have each record represent a type of
product, in this case, a style of sweater. Each record has multiple color Properties associated with it.
In our data source, the data may already be organized this way. Or we may combine multiple rows
into a single record during the extraction process or while running the data through the ETL tool.


4.1.4
Student Guide
Module 4
Advanced Topics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an tolictheensingle record design, is a loss of precision among attributes. In the
One of the drawbacks
m
le there is no correlation between the Color attribute and the AmountOrdered attribute.
example
uabove,
S
if
h
s
a


4.1.5
Student Guide
Module 4
Advanced Topics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n into distinct records, one drawback is the potential for large result
edata
atonseparate
When choosing
c
i
m
l
sets of what
ule is largely the same thing. In this case, our record list contains many similar items, which
S
vary
if based on color and size. This can be overwhelming for end users.
h
s
a


4.1.6
Student Guide
Module 4
Advanced Topics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cen
a
m
li means incorporation of elements of both of these techniques where
Endeca record
e design always
l
u
data S
f is combined.
i
h
as


4.1.7
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.8
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.11
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n alsochave
en different types of records. For instance, a car database may contain
amay
Your application
i
m
l
car records,
ule accessory records, dealer records, and user review records. We refer to these different
S
types
if as being heterogeneous.
h
s
a
In the above example, a financial services index contains 3 types of records: Holdings, News, and
Research. Each of these records has different sets of standard and managed attributes. For instance,
the News record has a managed attribute called NewsPublisher, but neither the Holdings nor the
Research record types have this managed attribute.
There are a few options for how data is modeled in your index under these conditions to enable
association among records of different types. The next few slides discuss options available to you to
enable relational type queries.


4.1.12
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.13
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.14
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n haveccommon
en attributes, e.g. AuthorName, but each of them certainly has
amay
All record types
i
m
l
le e.g. AuthorAge and PublishYear.
distinct u
attributes,
S
hByifdefault, there is no association among the different record types that enables you to determine a
s distinct attribute of a record based on a shared field with another record of a different type. For
Ka
example, you cannot query to return books written by 40 year-old authors. Nor can you return authors
who published books in 2006.


4.1.15
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n centhe data down to a single record type. In the example above, we have
One option ism
toadenormalize
li data (like Age) to each book record. In this way, each book record will
le secondary
attached
Author
u
f Sall related author information associated with it. The merging of data would occur either before or
have
i
h
as during the ETL process. Performance is also improved because the association is made during
indexing.


4.1.16
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en to denormalization; the first is loss of precision. By merging multiple
an drawbacks
There are two
primary
c
i
m
l
author records,
ule we lose the delineation between each author and his/her associated age.
S
if second drawback is an increased memory footprint. The book records must now contain
The
h
s
a
redundant author data for every book that is written by the author. Because this example is very
simplistic, its impact may not be apparent. However, consider an index that contains parts, suppliers,
and orders. If we denormalize all data into part records, each part must contain every related supplier,
and for each supplier, every related order. You can begin to see how thiis method can produce an
exponentially large index.


4.1.17
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.18
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.19
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.20
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.21
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.22
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.23
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.24
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
e(sometimes
an type
With the date
record
called the calendar record type), you can add a record
c
i
m
l
e
l
to the
MDEX
u for each day (going back 3 years for example) and merely attribute that record
Swith
f
i
type
some of the date dimensions required. Then in analytics statements we can do
ash
things like show total sales by month for the last 90 days:
DEFINE Last90Days AS SELECT
p_Date AS Date
WHERE IsLast90Days=Y AND RecordType = Date;
RETURN 90DayTrendReport AS SELECT
SUM(p_Sales_Trans_Amt) AS TotSales
WHERE RecordType = Sales AND [p_Date] IN Last90Days
GROUP BY Region
This allows us to have trending reports that update dynamically day after day so long as we
keep the calendar record type up-to-date. This is much easier that updating attribution on
millions of sales transactions.

4.1.25
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.26
Student Guide
Module 4
Advanced Topics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enusing setLanguageId method (Java API) or
abenidentified
Language can
c
i
m
l
navigationcommand.LanguageId
instance property (RAD.NET API).
ule
S
f
i
ash


4.1.27
Student Guide
Module 4
Advanced Topics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n shown in the table that this property does not exist on the record.
n fields
eare
ablank
Note that where
c
i
m
l
ule
S
if
h
s
a


4.1.28
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.29
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.30
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.31
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.32
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.33
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.34
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.35
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.36
Module 4
Advanced Topics
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka


4.1.37
Ka
le
fS
i
h
s
u
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
n
a
r
t
nb
fera
Student Guide
Module 4 - Advanced Topics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an min.licen
Lesson Time:
~10
m
ule
S
if
h
s
a
Lesson 2 Integrating with

Other ETL Tooling

4.2.1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka

Other ETL Tooling

4.2.2
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka

Other ETL Tooling

4.2.3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n clessons,
en the MDEX Engine comes packaged with the Latitude Data
As coveredm
in a
previous
i
l
Integrator.
uleThe Latitude Data Integrator is a high-performance data integration platform that
S
if source records from a variety of source types and sends the data to the MDEX
hextracts
s Engine via the Data Ingest Web Service (DIWS) or the Bulk Load Interface. The Latitude Data
Ka
Integrator communicates with the DIWS and the Bulk Load Interface using a series of
Endeca-developed Latitude connectors which are accessible through the Latitude Data
Integrator.
The MDEX Engine can also connect with other ETL clients via custom-developed DIWS
connectors. Customers who use ETL clients other than the LDI can develop their own
connectors using stubs generated from the Data Ingest WSDL and calls from the ETL clients
SDK.
For more information on the data ingest process, see both the Latitude Data Integrator Guide
and the Latitude Data Ingest Guide.

Other ETL Tooling

4.2.4
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en (DIWS) loads data into a running MDEX Engine and can also
anWebliService
The Data Ingest
c
m
le records.
updateuexisting
S
if
h
s
a
The DIWS therefore allows you to use a data integration platform to load data into an Endeca
application. Endeca is packaged with one such platformthe Latitude Data Integrator.
Customers also have the option of creating custom connectors for other ETL clients which run
against the DIWS.
The data-related tasks listed in the slide are performed via two DIWS operations:
ingestRecords: adds, modifies, and deletes records (including removing managed
value assignments)
ingestDimensionValues: adds and updates managed values
The DIWS is able to modify a record multiple times in a single transaction (any combination of
creating, adding assignments, deleting assignments, and deleting records).
For more information on the Data Ingest and Configuration Web Services, see the
Developers Guide.

Other ETL Tooling

4.2.5
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka

Other ETL Tooling

4.2.6
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en connector adds or replaces records via the MDEX Engines Bulk Load
an lRecords
The Bulk Add/Replace
c
i
m
Interface.lItedoes NOT use the Data Ingest Web Service. This connector loads data source records
u load PDRs, DDRs, managed attribute values, the GCR, nor the MDEX Engine index
only;S
it cannot
f
i
configuration
files.
ash
When employing this connector, existing records in the MDEX Engine are added, not updated.
Therefore, the key-value pair list of the incoming record will completely replace the key-value pair list
of the existing record.
The Bulk Add/Replace Records connector is intended to be used with bulk data when delayed update
visibility and compromised concurrent query performance are acceptable. Some of the use cases for
this connector are:
Full index initial load of records, with no loaded schema.
Full index initial load of records, with your record schema already loaded.
Adding more records to the MDEX Engine any time after the initial loading of records.
Replacing existing records in the MDEX Engine any time after the initial loading of records.
Note that at this time, the Bulk Load Interface is a private, proprietary interface, and custom
connectors cannot be built against it. In order to employ the bulk ingest process, you must use the
Latitude Data Integrator.
For more information on this connector, see the Endeca Latitude Data Integrator Guide, specifically
the chapter entitled Latitude Connector Reference.
Other ETL Tooling

4.2.7
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen Latitude connectors are used as follows:
The four Endeca-developed
m
ule
S
if
h
s
Add/Update Records connector: Adds new records to a running MDEX Engine. The
a
records can be added to an empty MDEX Engine (a full index initial load) or to one that
already has records. This connector can also be used to load the Latitude applications
record schema via the PDRs and DDRs. Endeca standard attributes that do not
already exist are created automatically.
Add KVPs connector: Updates existing records by adding new key-value pair (KVP)
assignments to those records. This connector can also create new records for the keyvalue pairs.
Add Managed Values connector: Adds a taxonomy (managed values) to a running
MDEX Engine. If the managed values belong to a managed value that is currently not
in the MDEX Engine, the managed attribute is created automatically.
Delete Data connector: Removes KVP assignments from records and/or deletes
entire records from the MDEX Engine.
Reset MDEX: deletes all records (including schema records) and configuration, and
provisions the MDEX Engine.

Other ETL Tooling

4.2.8
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en Config connectors are intended to be used in the following
an andlicImport
The Export m
Config
cases:
ule
S
if
h
Both of these connectors support cases where, after loading the default configuration, you
s
a
change portions of it in Latitude Studio, such as attribute groups, or attribute group names.
From this point on, you may want to keep using this changed configuration, even if you run
subsequent data updates. The connectors allow you to do this.
The Export Config should also be used as part of the graph in which you run a baseline
update for loading data (although, it is not intended to be used with the initial baseline
update).
In a typical scenario of a repeatable baseline update, you create a graph in which you start a
transaction using the Transaction RunGraph component, export all configuration and schema
using Export Config, run the Reset MDEX to remove all records and provision a new MDEX
Engine, import the previously saved configuration and schema with Import Config, and then
reload the records. At this point, the transaction can close and the node on which the baseline
update was run can resume answering queries.

Other ETL Tooling

4.2.9
Student Guide
le
b
fera
n
a
r
t
n-
Ka
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enconnector you must generate client stubs from the DIWS and
ana custom
In order to create
c
i
m
l
Configuration
ule Web Service and MDEX Engine WSDL.
S
f
shi
For information on this process, see the Endeca Latitude Data Ingest Guide and Endeca
Latitude Developers Guide for more details.

Other ETL Tooling

4.2.10
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka

Other ETL Tooling

4.2.11
Ka
le
fS
i
h
s
u
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
n
a
r
t
nb
fera
Student Guide
Module 4 Advanced Topics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an min.licen
Lesson Time:
~20
m
ule
S
if
h
s
a
Lesson 3 - Security

4.3.1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.2
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cen
Stateless ma
le structureslias Guided Navigation
Same data
u
fS
i
h
as
Lesson 3 - Security

4.3.4
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.5
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.6
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.7
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
an licesolutions:
Supported authentication
LDAP, Central Authentication Service (CAS), NTLM,
m
e
l
OpenID,
Su Atlassian Crowd, OpenSSO, SiteMinder
f
i
ash
A list of common Active Directory LDAP bind errors
525 - user not found
52e - invalid credentials
530 - not permitted to logon at this time
532 - password expired
533 - account disabled
701 - account expired
773 - user must reset password
775 - account locked
For more details:
http://www.nordicedge.se/support/kb/questions/179/NSD1103+Common+Active+Directory+LD
AP+bind+errors
Lesson 3 - Security

4.3.8
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.9
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.10
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.11
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.12
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.13
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enManagers name is renamed Hawkeye Pierce after LDAP
an howlicJoe
In lab you will
see
m
integration
uleis setup. The new name was imported from LDAP.
S
if
h
s
a
Lesson 3 - Security

4.3.14
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n that displays a different greeting. Its configured in dock.vm
etheme
aancustom
You can make
c
i
m
l
as <span>$user_greeting</span>.
You can either modify dock.vm directory or change the
ule
S
f
i
setting
of
$user_greeting
in
your
init_custom.vm
to #set ($user_greeting = Welcome +
h
s$user_first_name + + $user_last_name + !).
Ka
Lesson 3 - Security

4.3.15
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.16
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.17
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.18
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.19
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.20
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
edrop-down
an inlithe
1. From the
Dock,
menu, choose Control Panel
c
m
e
l
2. In the
Su Latitude Studio section of the Control Panel navigation panel, select Framework
f
i
Settings
ash
3. Change the df.mdexStateManager or df.mdexSecurityManager property to the full
name of your class (e.g., df.mdexStateManager =
com.endeca.portal.extensions.YourStateManagerClass)
4. Click Update Settings
5. Restart the Latitude Studio
Lesson 3 - Security

4.3.21
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.22
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.23
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 3 - Security

4.3.24
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an min.licen
Lesson Time:
~20
m
ule
S
if
h
s
a
Lesson 4
Text Enrichment in Latitude

4.4.1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

4.4.2
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

4.4.3
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

4.4.4
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

4.4.5
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

4.4.6
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

4.4.7
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

4.4.8
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

4.4.9
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

4.4.10
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n process you set up to get your raw information (from a PDF,
an licisethe
Content m
Enrichment
for example)
ule into the form you need for your application to be effective. This process
S
hiftransforms the information found in your file or document into Endeca record format
Ka
key-value pairs that contain data and metadata.
Lesson 4

4.4.11
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

4.4.12
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

4.4.13
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 4

4.4.14
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an min.licen
Lesson Time:
~20
m
ule
S
if
h
s
a
Lesson 5
Latitude 2 Deployment Features

4.5.1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 5

4.5.2
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 5

4.5.3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cen
aStarted
m
liApplication for Latitude 2.2 is already enabled for transactions.
The Getting
e
l
u
f S graphs are also included showing how to execute Begin, Commit and Rollback
iExample
shtransactions as separate operations. Baseline.grf uses the Transaction RunGraph

a
K component to wrap all called graphs with transactions.
Documentation:
DevGuide.pdf: About the Transaction Web Service
LDIMDEXcomponents.pdf: Transaction RunGraph component
Lesson 5

4.5.4
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 5

4.5.5
Student Guide
le
b
fera
n
a
r
t
n-
Ka
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
eindividual
antesting
Note that m
when
graphs and not using the Transaction RunGraph
c
i
l
e
l
component,
you
will
need
to
Begin,
Commit and Rollback transactions through web
u
S
f
shiservice calls. The BeginTransaction.grf, CommitTransaction.grf, and
RollbackTransaction.grf graphs provided in the Getting Started application are designed

for this usage.
Note that if a transaction cannot be closed that you will need to shut down the MDEX
engine with a call to (wget is in the MDEX bin folder):
wget http://<host>:<dgraph_Port>/admin?op=exit
e.g. http://localhost:5555/admin?op=exit
Lesson 5

4.5.6
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 5

4.5.7
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 5

4.5.8
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enassociated Universal Data Writer to write the output file. It is
anneeds
This component
an
c
i
m
l
recommended
ule that the export graph is run by the Transaction RunGraph component in a
S
if
separate
graph to do this in a transaction to prevent any likelihood of changes during the
h
s
a
operation.
Note: the default buffer sizes in LDI are usually not large enough to support the generation
of the output file using this component. Details of changing the buffer sizes can be found
under Troubleshooting in the LDIMDEXComponents.pdf. It requires extraction of a
defaultProperties text file from
DataIntegrator\plugins\com.cloveretl.gui_3.1.0\lib\lib\cloveretl.engine.jar and then placing it in

your LDI project co-located with the workspace.prm file. Edit the file to change settings as required,
and then refer to the file in the Run Configuration for the graph under arguments using
config defaultProperties
Lesson 5

4.5.9
Student Guide
le
b
fera
n
a
r
t
n-
i
ash
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
tinstructions.
n detailed
S
a
See the LDIMDEXComponents.pdf
for
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
Su
Lesson 5

4.5.10
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 5

4.5.11
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 5

4.5.12
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enare directed at the Leader Node.
anchanges
All updates
and
c
i
m
l
ule database file system is shared by all nodes.
The
MDEX
S
if
shFollowers only use the updated database when notified by the Cluster Coordinator.
a
K
All operations on the Leader node must be placed in transactions; transactions cannot be
nested.
The cluster must entirely run on Windows or Linux.
The leader node returns an HTTP 403 if a transaction is in progress which allows the load
balancer to direct requests to other nodes.
Lesson 5

4.5.13
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 5

4.5.14
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an min.licen
Lesson Time:
~10
m
ule
S
if
h
s
a
Lesson 6
Next Steps for Enablement

4.6.1
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 6

4.6.2
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 6

4.6.3
Student Guide
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n 2, navigate to http://eden.endeca.com. Click Encyclopedia,
eLatitude
an lon
For more information
c
i
m
thenS
Latitude
ule 2 Enablement Wiki.
if
h
s
a
Lesson 6

4.6.4
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 6

4.6.5
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 6

4.6.6
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 6

4.6.7
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 6

4.6.8
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 6

4.6.9
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 6

4.6.10
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 6

4.6.11
Student Guide
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 6

4.6.12
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
Timings
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
Su
f
i
shLabs: ~90 minutes
Ka
Lesson 1 Introduction
to Endeca Analytics

5.1.1
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.2
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.3
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.4
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n a platform for constructing applications that enable data
eprovides
an Engine
The Endecam
MDEX
c
i
l
consumers
uleto quickly and efficiently locate information of interest in large databases, using the Guided
S
Navigation
interface. Endeca Analytics builds on the core capabilities of the Endeca MDEX Engine to
if
h
s
a enable applications that examine aggregate information such as trends, statistics, analytical
visualizations, comparisons, and so on, all within the Guided Navigation interface.
to Endeca Analytics

5.1.5
Student Guide
Module 5 Analytics
le
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
eanalyzing
an lifor
Bike Stores m
application
sales
c
e
l
Su
Business objective: Increase profitability of bike store
f
i
ash User: Business Analysts
b
fera
User goal: Improve sales totals and margins
Provides views of the data that the users didnt even know they wanted until they started exploring the
data themselves.
to Endeca Analytics

5.1.6
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.7
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.8
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.9
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.10
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.11
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
efornaccessing analytics results from the MDEX query result. This is
anthe key
RETURN provides
c
i
m
l
e more than one statement is submitted with the MDEX query, or multiple analytics
important
ulwhen
S
statements
are nested. You will learn more about this later in the course.
if
h
s
a
Important: Strings with spaces or non-alpha values need to be wrapped in double quotes. Literals
should be wrapped in single quotes. Numbers that remain constant can either be wrapped
in single quotes or without quotes.
to Endeca Analytics

5.1.12
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enfor each expression, and defines an attribute to be returned with each
anthe lname
Each key specifies
c
i
m
le result.
Endecaurecord
S
if expression defines the derived values that are computed for each result record, and computes
Each
h
s
a
the Property value to be returned with each ERec object.
One important difference with Endeca Analytics and SQL is that with Endeca the AS aliasing is not
optional like it is in SQL.
to Endeca Analytics

5.1.13
Student Guide
Module 5 Analytics
le
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enof different core functions including:
ana number
Analytics supports
c
i
m
l
ule
COUNT
S
if
h
SUM
s
a
b
fera
AVG
MEDIAN
STDDEV
VARIANCE
MIN
MAX
ARB
Note that grouping is required for all of these functions.
to Endeca Analytics

5.1.14
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enspecified, a bucket (record) is created for each unique combination of
an licare
When multiple
groupings
m
e If only GROUP is specified, a single bucket is created.
grouping
ulvalues.
S
if
h
s
a
Usage: GROUP BY <grouping1>, <grouping2>
<grouping> may only be pre-filter standard or managed attribute names; post-filter names
(result of an AS) will cause a parser error
to Endeca Analytics

5.1.15
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
n ceinclude:
afunctions
Additional Unary
i
m
l
le
Su
ROUND (can take an optional second numeric variable as the order of magnitude of the
if round; 0 is default, positive number = round to the right of the decimal, negative number =
h
s
a
round to the left of the decimal)
SIGN
SIN
SQRT
TAN
TO_DURATION (time function)
TRUNC (has the same optional second variable like ROUND)
POWER (requires a second numeric variable like ROUND)
The ARB function returns an arbitrary value from a set of values. In the example above since
all the Credit Ratings for a given customer are the same you just want to know the value for
any of them.
to Endeca Analytics

5.1.16
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.17
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en can be both used as unary and binary functions.
anand lTRUNC
Note that ROUND
c
i
m
ule
S
if
h
s
a
to Endeca Analytics

5.1.18
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.19
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n used to round a DateTime value down to a coarser granularity.
ebe
an lcan
The TRUNC
function
c
i
m
For example,
ule this is useful when performing a GROUP BY on DateTime data based on
S
if time ranges (such as GROUP BY Quarter given DateTime values).
coarser
h
s
a
The EXTRACT function extracts a portion of a DateTime, such as the day of the week or
month of the year. This is useful in situations where the data must be filtered or grouped by a
slice of its timestamps, for example computing the total sales that occurred on any Monday.
to Endeca Analytics

5.1.20
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n the highest total will be the first record in the Analytics result. Note that
n regioncewith
athe
In this example,
i
m
l
le keys can be specified. Ascending order is the default.
multipleusort
S
if ORDER BY <key> ASC|DESC
Usage:
h
s
a
The <key> must be defined in the return table; this means either a post-filter name (result of an
AS) or the GROUP BY <grouping> name
to Endeca Analytics

5.1.21
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enthe Latitude Analytic Query language has date-time functions for
an because
YEAR is reserved
c
i
m
l
attributes
ulofeDate-Time type. YEAR is the function to extract the year value from the Date-Time
S
attribute.
if
h
s
a
to Endeca Analytics

5.1.22
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.23
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n five
enEndeca components that require Endeca analytics query statements to
aincludes
Latitude Studio
c
i
m
l
render their
uleresults/display. These components include: Chart, Results Table (Analytics), Metrics Bar,
S
Cross
if Tab and Advanced Visualization. In addition, developers can create custom components that
h
s
a utilize the Endeca analytics query language.
to Endeca Analytics

5.1.24
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en end users to view data in a variety of different chart types. All charts
an enables
The Chart component
c
i
m
l
lekey and/or labeling on the X and Y-axis when applicable. The Chart component allows
display u
with
S
end
if users to switch the chart view by selecting drop-down choices; for example, an end user may
h
s
a choose to switch the Metric or Group By that is summarized in the chart.
The Chart component reveals specific numeric data when a cursor is rolled over it and provides a drilldown feature, allowing end users to filter results by the value(s) displayed in the chart. The Chart
component can accommodate two types of analytics statements: fixed and parametric.
to Endeca Analytics

5.1.25
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
epreferences
an oflithe
Using the topm
portion
page, power users can configure basic display settings for the
c
e
l
Chart such
as
title
and
size,
as
well
as
select
the style of chart they would like to display. OOTB Corda
u
S
f
chart
i templates include vertical bar, vertical stacked bar, horizontal bar, line, bar, pie, and dual-axis
ashline/bar combo charts.
The chart height/width can not exceed the HTML Height and width.
1.
Enter a Chart Title
2.
Select a Style of chart
Vertical bar, vertical stacked bar, horizontal bar, line, bar, pie, and dual-axis line/bar
combo charts
3.
Define the Chart Height and Chart Width
Or accept defaults
to Endeca Analytics

5.1.26
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
eanfixed Analytics statement to the Chart component, or configure a
ancan add
The power user
c
i
m
l
parametric
uleAnalytics statement that allows end users to see drop-down lists across the top of
S
if chart.
the
h
s
a
The Metric Selector allows you to specify an ORDER BY in the Analytics statement without
including it in the display. The Metric Selector does not appear until you have tested and
saved the Analytics query.
When the Enable Top-N Sort checkbox is selected, the chart's results can be sorted in
ascending or descending order. If the Enable end user control checkbox is also selected,
the end user can toggle the sort order.
to Endeca Analytics

5.1.27
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en the results of an analytics query:
anTableltoicdisplay
To use a Results
m
le
1.Su
Choose a data source
hif2. Select the Use analytics statement checkbox
Ka
3. Create your statement in the Analytics statement field

4. Click Test analytics query; if the statement is valid the Save Analytics Configuration
button will be enabled
to Endeca Analytics

5.1.28
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cenprovides a table that allows end users to perform comparisons and
acomponent
The Cross Tab
i
m
le acrosslseveral
identify
trends
cross sections of data.
u
S
f
i
ashA cross tab consists of a specific configuration of rows, columns, and summary cells that
together make up the table body. The values displayed in the header rows and columns
represent every possible grouping value of the specified data fields. Summary cells exist at
the intersection of rows and columns. The value of a given summary cell is a metric
corresponding to the intersection of those two groupings.
to Endeca Analytics

5.1.29
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
n cecomponent:
To configurem
theaCross-Tab
i
l
ulea data source
1) Choose
S
h2)ifEnter an analytics statement; notice that the statement is a fixed statement as parametric analysis
Ka
for the cross tab component is not currently supported
3) Click Test analytics query, this will populate the configuration with the different metrics, row
groups and column groups
4) Configure which metrics you want displayed.
5) Configure the rows and columns of how you want the records shown by dragging to reorder them.
to Endeca Analytics

5.1.30
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.31
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.32
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.33
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en intermediate result sets for further analysis by additional statements.
anfor computing
DEFINE is useful
c
i
m
l
For example,
ule DEFINE could help you compute the average customer age from transactional records
S
without
if improper weighting.
h
s
a
to Endeca Analytics

5.1.34
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en statements to be nested. Without a FROM component, an
anallows
Essentially, FROM
analytics
c
i
m
l
e
analytics
will always refer to the base record set returned by the Navigation query.
ulstatement
S
f
i that you may only have one FROM per query.
Note
ash
The default FROM is the current navigation state.
to Endeca Analytics

5.1.35
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
Global WHERE clauses
n frequently used, since Navigation or Record Filters can be used
enot
an liare
c
instead. em
ul
S
f
hi these common operators and/comparisons:
asNote
OR
AND
>
<
<=
>=
IS NULL
to Endeca Analytics

5.1.36
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en attributes (calculated values).
an onlderived
HAVING only
works
c
i
m
ule
S
if
h
s
a
to Endeca Analytics

5.1.37
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n
eAnalytics
atonanother
IN can only refer
statement that was grouped and whose GROUP BY list
c
i
m
l
e
l
matches
the
Key
list
indicated
within
the
brackets.
u
S
f
i
ash
to Endeca Analytics

5.1.38
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
anrefer ltoicanenAnalytics statement that was grouped and whose GROUP BY list
Lookups canm
only
le Key list indicated between the brackets.
matches
uthe
S
if example above computes the percentage of sales per Varietal per Region.
The
h
s
a
to Endeca Analytics

5.1.39
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
enallows for user-specified null-handling. You can use COALESCE to
anexpression
The COALESCE
c
i
m
l
le for multiple values and return the first non-null value encountered, in the order
evaluate
urecords
S
specified.
The following requirements apply:
if
h
s
a
You can specify two or more arguments to COALESCE
Arguments that you specify to COALESCE should all be of the same type
The types of arguments that COALESCE takes are: integer, integer64,
double and string
You cannot specify managed attributes as arguments to COALESCE. However, you can
specify a standard attribute as arguments to COALESCE resulting in a valid query.
The COALESCE expression can only be used in a SELECT clause, and not in other clauses
(such as WHERE)
In the following example, all records without a specified price are treated as zero in the computation:
AVG(COALESCE(price, 0.0))
COALESCE can also be used on its own, for example:
SELECT COALESCE(price, 0.0) WHERE
to Endeca Analytics

5.1.40
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.41
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cthat
enreturns results to the application returns all results. In some cases, it is
astatement
By default, any
i
m
l
le results in smaller increments for presentation to the user (such as presenting the
useful to
urequest
S
if reps ten at a time, with links to page forward and backward). For example, the following query
hsales
s groups the records by SalesRep, returning the 10th through 19th resulting buckets (order in this case
Ka
is arbitrary but consistent between queries):

DEFINE Reps AS
GROUP BY SalesRep
PAGE(10,10)
Paging can also be used in combination with ORDER BY to achieve top-k type queries. For
example, the following query returns the top 10 sales reps by total sales:
DEFINE Reps AS
SELECT SUM(Amount) AS Total
GROUP BY SalesRep
ORDER BY Total DESC
PAGE(0,10)
to Endeca Analytics

5.1.42
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n BY case
eORDER
an for the
Additional example
c
i
m
l
le BY with a GROUP BY key.
uORDER
You can
S
if
h
s
a
to Endeca Analytics

5.1.43
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n ceinna specific order.
aprocessed
Statements are
m
li
le
u
fS
i
h
as
to Endeca Analytics

5.1.44
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.45
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.46
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.47
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en be pre calculated in the database or during data ingest rather than at
anfieldslishould
Popular Group
By
c
m
runtime.ule
fS
i
h
as
to Endeca Analytics

5.1.48
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.49
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n analysis
en is added to the Chart component end users see drop down menus
abased
When parameter
c
i
m
l
across the
uletop of the chart that enable various analytic views to be selected/created on the fly.
S
Toifcreate parameter based charts, Power users must first add a parametric analytics statement in the
h
s
a
Analytics Statement field and then establish the Metrics, X-options and/or Cross tab choices in
their respective fields. The contents of the Metrics Options field display for the end user on the
Metrics drop down menu and subsequently on the Y-axis of the Chart component; the contents of the
X-Axis Options field display for the end users on the Group By drop down menu and subsequently
on the X-axis of the Chart component. The Cross tab axis is best thought of as the z axis and gives
you another way to look at the data. Use both the XAXIS and CROSSTAB when you want to give the
end user options when doing a GROUP BY of two.
To configure a parameter based analytic statement:
1. Use an analytic statement and parameterize it with the parametric tokens
2. Define the different fields that should be used for metrics, x-axis and cross tab.
to Endeca Analytics

5.1.50
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.51
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.52
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en when:
an liiscused
An analyticsm
dashboard
le
u
Information
related to a particular organizational function or role needs to be monitored
S
f
hi regularly, possibly in real time.
Ka
The information sources represent critical metrics that must be understood at a glance.
The information sources are diverse and complex, requiring some degree of summarization or
aggregation to be comprehensible.
Deviations from expected or desired values or thresholds are of particular importance and
require immediate investigation or action.
The optimal selection of key information and data is specific to a particular individual or role (or
may be customized by the end user).
A view of the overall trends for key metrics is required, providing visibility into the relationship
between key values and trends.
Users need access to the above functionality without being obliged to build a complex query.
Users need access to the above functionality without being obliged to undergo extensive
training or familiarization with the system.
to Endeca Analytics

5.1.53
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.54
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
n cein nLatitude Studio, your users need a concise, high-level overview of a
aanalytics
When conveying
m
li one that usually focuses on key metrics which represent the status of
le of information,
complex
set
u
f S organizational entities, processes, or activities as a means of determining potential areas
important
i
h
as that may require investigation or intervention.
A well-designed dashboard allows end users to make better decisions by maximizing the visibility of
relevant organizational information and data, thus saving time and increasing productivity. It reduces
information overload by summarizing key metrics and trends without requiring the user to interact with
the application. It groups and aggregates key information sources so that immediate insight may be
obtained at a glance, and discovery of patterns and relationships in the data is maximized. It directs
users attention to the most important areas, and highlights deviations from expected values so that
issues requiring further investigation or action can be immediately identified.
to Endeca Analytics

5.1.55
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
to Endeca Analytics

5.1.56
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
Timings
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
Su
f
i
shLabs: ~4 hours
Ka
Lesson 2
Analytics Workshop

5.2.1
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Analytics Workshop

5.2.2
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
no
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
en
an lrepresentation
Star schemam
= Generic
of a dimensional model in a relational database.
c
i
e
l
ufor the bulk ingest LDI component to submit records into the MDEX engine it requires a
In order
S
f
i
unique identifier, a record specifier, for each record. For this project the record specifier is defined as a
ash
transform in the FactSales_SalesTransaction data.
It is defined to be FactSales_RecordSpec and is the concatenation of FactSales_SalesOrderNumberFactSales_SalesOrderLineNumber.
Lesson 2
Analytics Workshop

5.2.3
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Analytics Workshop

5.2.4
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Analytics Workshop

5.2.5
Student Guide
Module 5 Analytics
le
b
fera
n
a
r
t
n-
n
a
has
)
om uide
c
cle nt G
a
r
o ude
@
t
n
S
a
s
em thi
l
u
fs use
i
h
as se to
k
(
an licen
m
le
fS
i
h
s
Ka
Lesson 2
Analytics Workshop

5.2.6

Getting Started With Endeca Latitude

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Getting Started With Endeca Latitude

Încărcat de

Drepturi de autor:

Formate disponibile

Unauthorized reproduction or distribution prohibited Copyright 2011, Oracle and/or its affiliates

U.S. GOVERNMENT RIGHTS

Getting Started with Latitude 2

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Guidance in daily decisions:

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

experience brings together:

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

The Latitude Information Integration Suite:

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Extensible framework for data source connectivity and data manipulation

64-bit, multi-threaded platform available on Windows and Linux

Out-of-the-box connectivity to Documentum, FileNet, Lotus Notes, Sharepoint, Interwoven,

Text and metadata extraction for 500 file formats

Easily integrate data from a variety of unstructured data repositories

Best-of-breed partner technologies available for text enrichment

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Provides custom transformations to build the records

Provides custom targets that reassemble single-assignment records into complete

Copyright2011 Endeca Technologies, Inc.

Getting Started with Latitude 2

Enablement of users to explore data and content in an unconstrained and impromptu

Frees IT from the burdens of traditional data modeling