Tip:
Highlight text to annotate it
X
Welcome back to the Getting Started with Oracle Endeca Information Discovery v 3.0 screencast series.
This is the beginning of Part 3 -- Loading and Viewing Data.
This screencast will demonstrate how to setup an Integrator project and create a new Oracle
Endeca Server data domain that we'll use for our project.
The first task we are going to do is create a new Integrator project, that we'll call BikeStore.
You can see that our new BikeStore project is setup with the default directory structure.
The next step is to create an Oracle Endeca Server data domain for our bikestore application.
Before we do that, let me give you a quick overview of Oracle Endeca Server and Data Domain concepts.
Oracle Endeca Server is a Java Server process that is typically installed once per physical server and started as a service.
Therefore, it will run on a specific host and port.
Oracle Endeca Server then manages a set of named data domains via a management web service.
For example, the Getting Started application uses a data domain named GettingStarted.
Oracle Endeca Server is intended to be a single access point for query and ingest requests across all of its data domains.
In order to create an Oracle Endeca Server data domain for our bikestore application, we'll reuse some of the components from the existing
project -- the Getting Started project, which contains data for the Getting Started application.
Let's start with the workspace.prm file.
This file contains the parameters that we'll use in the BikeStore application.
Although a basic workspace.prm file in included in our BikeStore project when we created it, the file in the Getting Started project has some
additional parameters that are necessary for our project.
So, let's copy the workspace prm file from the Getting Started project.
And now we'll take a look at it
You'll notice 3 new parameters that specify the location of the Oracle Endeca Server data domain.
The first two specify the host and port of Oracle Endeca Server.
The third specifies the name of the data domain.
Also notice that the default language for this project is set to en for English.
For this application, we want to reuse Oracle Endeca Server, so we'll keep the host and port as-is,
but we want to create a new data domain called BikeStore.
Next, we want to create this new data domain. We'll first create a new graph called InitDataDomain.
Now we'll copy one component from the Getting Started project that contains the appropriate web service call to create a data domain.
Let's navigate to the InitDataDomain graph in the Getting Started project.
This graph contains additional logic that we don't need at this point.
We only need to copy the "Create Data Domain" component.
Let's paste that component into our InitDataDomain graph.
If we open up this component, you'll see that it is making a web service call to create the data domain,
passing in the data domain name, that it is pulling from the workspace.prm file.
So we do not need to make any changes to this component.
Now let's run this graph.
You'll notice logs are being written to the Console as the graph runs.
We know the graph has successfully completed when "Execution of graph successful" displays in the console.
In addition, you'll see a blue checkmark icon appear on the component.
We can verify the data domain is up and running by pinging it from a browser
http://localhost:7001/endeca-server/admin/bikestore?op=ping
This response confirms there is a data domain named bikestore that is managed by Oracle Endeca Server on localhost:7001
In this screencast, you learned how to setup an Integrator project and create a new Oracle Endeca Server data domain.
The next screencast in the series will show you how to load configuration information into the Oracle Endeca Server data domain.