Oracle Endeca Information Discovery 3.0 Now Available
You probably missed it over the weekend, but a couple of days ago I posted an article on our blog about Endeca Information Discovery 2.4, and whether it could be a viable alternative to Oracle BI’s Analysis Editor (aka “Answers”). In that posting I said that, whilst the in-memory search/analytic database that powers Endeca Information Discovery could potentially be a great back-end for OBIEE, the current generation of dashboarding and analysis tools weren’t quite user-friendly enough for Oracle BI “power users”. I did say though that the next, 3.0 release of Endeca Information Discovery might improve on this usability though, and in fact over that same weekend, Endeca Information Discovery 3.0 actually became available for download on Oracle’s Edelivery site. So what’s in the 3.0 release, and have there been any usability improvements in the visualisation components?
Oracle Endeca Information Discovery 3.0 actually has changes and new features in a number of areas. Probably the most significant is in the area of infrastructure; the Endeca Server, Studio Server and Integrator Server all now run on Oracle WebLogic Server as well as Tomcat, with Endeca Server actually requiring WebLogic now to host the java-based server engine. I’m not sure at this point whether Endeca Server will include a limited-use WebLogic license, or whether you’ll need to license it separately, but the Endeca Server goes into WebLogic and can now be clustered over several WebLogic managed server nodes, with one Endeca Server per cluster providing read/write access to the Endeca Server Datastore (now called “Data Domain”), and multiple Endeca Servers providing read-access with traffic passed across using a load-balancer. A cluster can contain multiple Endeca Servers, and multiple data domains, and presumably you’d need an Enterprise Edition license for WebLogic as opposed to Standard Edition if you want to make use of this clustering.
Endeca Information Discovery Studio and Integrator are now formally separate products in terms of packaging, both can still run on Tomcat but both can now also run on WebLogic, though the installation process is quite tricky and you’ll need to be aware of Java minimum versions, libraries that also need to go into WebLogic and so forth. In fact installation is quite a lot harder than with version 2.4, as the Quick Installation option has now gone and every product needs to be separately installed, deployed to the application server and so forth. You’ll need quite a bit more familiarity with WebLogic or Tomcat compared to 2.4 to get this all up and running, but it’s do-able and took me about an hour to get going.
Integrator, visually, looks just the same as before, but there are a number of enhancements and new features, and under-the-cover changes to reflect the move to WebLogic for the Endeca Server. The Quickstart project is now renamed “Getting Started”, is again slightly more involved to install, but once running has the same content, albeit with the new Studio 3.0 look-and-feel. Studio itself can now run in WebLogic (though it’s not mandatory), like Endeca Server can now be clustered, and has an interesting new feature associated with it called the Provisioning Service that allows end-users to upload files (in this initial release, just Excel files) and automatically create an Endeca Server data domain so that it can then be analysed in Studio.
Studio itself has a new look and feel, and there are a bunch of incremental improvements to the data visualisation and analysis component, though nothing game changing. These include:
- The Crosstab component being renamed to Pivot Table component, which has more or less the same functionality as before but now uses views, rather than raw EQL, for its data source
- The concept of Studio applications, rather than Liferay’s communities
- Each components’ Preferences button and dialog is now renamed Configuration, and what was the old Configuration dialog (used for component access permissions) has now gone, as part of a wider overhaul of user groups and organisation
- Studio 3.0 applications are now bound to a single datastore/data domain data source, whereas 2.x ones could bind individual application page components to separate data sources
- Incremental improvements to the search and navigation components, which we’ll go into more detail on in a future post
So to go back to the original question, around whether Endeca Information Discovery 3.0 now provides a more OBIEE-like environment for end-user reporting, particularly “power users” – well no, there’s nothing significantly different in this release, the pivot table, results table, chart and other components are much the same, but at least there’s a bit more consistency now around selecting and configuring their data sources (via “views”, the nearest Endeca has to the concept of subject areas and dimension/attribute/measure metadata).
Views and their administration tasks have now been moved to a new part of Studio, with this functionality removed from the Control Panel and moved to a new Application Settings area, which also configures the application itself, and the maintenance of attribute groups.
Of course – OLAP-style complex ad-hoc analysis isn’t really the main use case for Endeca Information Discovery, which is really aimed first and foremost at data discovery and access to unstructured data, with graphing and analysis to my mind a “bonus”. That said, the ad-hoc analysis capabilities at least with this initial 3.x release haven’t changed all that much compared to the 2.x releases, with the improvements and new features being mostly focused around infrastructure, security and manageability, but with some incremental improvements to the end-user and developer experience.