Adventures in Installing - Oracle Endeca 3.1 Integrator

Published November 7 2013 by Patrick Rafferty
Back to insights

The newest version of Oracle's Endeca Information Discovery (OEID v3.1), Oracle's data discovery platform, was released yesterday morning.  We'll have a lot to say about the release, the features, and what an upgrade looks like in the coming weeks (for the curious, Oracle's official press release is here) but top of our minds right now is: "How do I get this installed and up and running?"

After spending a few hours last night with the product, we wanted to share some thoughts on the install and ramp-up process and hopefully save some time for others who are looking to give the product a spin.  The first post concerns the installation of the ETL tool that comes with Oracle Endeca, OEID Integrator.

Installing OEID Integrator

When attempting to install Integrator, I hit a couple snags.  The first was related to the different form factor that the install has taken vs. previous releases.  In version 3.1, the install has moved away from an "Installshield-style" experience to more of a download, unzip and script approach.  After downloading the zip file and unpacking it, I ended up with a structure that looks like this:


Seeing an install.bat, I decided to click it and dive right in.  After the first couple of prompts, one large change becomes clear.  The Eclipse container that hosts Integrator needs to be downloaded separately prior to installation (RTFM, I guess).

Not a huge deal but what I found was that is incredibly important that you download a very specific version of Eclipse (Indigo, according to the documentation) in order for the installation to complete successfully.  For example:

I tried to use the latest version of Eclipse, Kepler.  This did not work.
I tried to use Eclipse IDE for J2EE Developers (Indigo).  This did not work.
I used Eclipse IDE for Java Developers (Indigo) and it worked like a charm:


In addition, I would highly recommend running the install script (install.bat) from the command line, rather than through a double-click in Windows Explorer.  Running it via a double-click can make it difficult to diagnose any issues you may encounter since the window closes itself upon completion.  If the product is installed from the command line, a successful installation on Windows should look like this:


Hopefully this saves some time for others looking to ramp up on the latest version of OEID.  We'll be continuing to push out information as we roll the software out in our organization and upgrade our assets so watch this space.


Contact us