Oracle has quietly made available version 3.2.0 of Endeca Information Discovery. Mid February it arrived on their Software Delivery Cloud although their website doesn’t make much reference to it so perhaps an “official” release date is still planned.
Either way the question we all have is what’s new & improved with this version from 3.1?
I’ve reviewed the technical documentation that was available, so a quick summary of changes are below:
Oracle Endeca Server 7.7.0
- Only supports Windows 2012 and Linux 6.
- Requires Weblogic 12, support for 11gR1 (10.3.6) is dropped.
- Requires Java 7 or 8, 6 is no longer suported.
- Application Developer Framework (ADF) Runtime no longer required.
- Reduced remote administration, which could be a security improvement but I think translates to saying “endeca-cmd –host remoteServerName” won’t work.
- New EQL function, CountDistinctMembers(attrName) has been added to support multi-assign attributes. Same as the more convoluted Cardinality(Set_Unions(attrName)) but apparently faster.
- Sorting of records by geocode distance from a reference point. (supported by the Conversation Web Service, not Studio’s UI)
- Default idle timeout increased from 10 to 15 minutes. You can increase it with a custom data domain profile, but 15 minutes is also the minimum.
- Improvements apparently to how hostname is handled. Possibly good since there were some issues with localhost references before, though I usually blamed them more on Windows 7.
- Improved handling of individual records that the Bulk Load Interface (Data Ingest Web Service) can detect as invalid and will identify. Previously the whole batch would just be rejected.
- Much faster restart if WebLogic restarts.
Oracle Integrator ETL 3.2.0
- Requires OES 7.7 and Java 7 or 8.
- Still includes the bundled Salience Engine, which is better news that you might think since with closely related Oracle Big Data Discovery they went with an in house text engine and Salience is more robust. At least as far as sentiment scoring went it was.
- Graph formats have changed and would need to be converted from 3.1. What has changed isn’t clear, but there was a path for Studio 3.1 that required changes to how attributes were identified so perhaps there’s a bit of that.
- Trans folder must be present. Wasn’t a strict requirement before that I can recall but I never did anything other than ignore it.
- Secure Graph Parameters feature lets you create a master password that encrypts graph parameters.
- Social Media .zip library is not longer separated. This language file (TE_SocialData.zip) is now part of Salience.
EID Studio (3.2.0)
- Requires WebLogic 12, Java 7 or 8, and either Linux 6 or Windows 2012. When you read Windows 7 is supported but not for prod environments, don’t believe it. You’re on your own there.
- Numerous bug fixes, though most seem to be available as patches to clients through Oracle support. No core functionality or new components are included as far as I’ve seen from the documentation.
I didn’t look at IAS (Integrator Acquisition System), Provisioning Services, Integrator ETL Server, or the Web Acqusition Toolkit. However I will note the first three at least all require the same versions of Java, WebLogic, and O/S. 3.2.0 is a Platform Upgrade.
Is it worth it for you to upgrade to 3.1?
Full disclosure I’ve only looked at the technical documents. I’ve seen nothing released identifying functionality changes other than release notes listing all the fixed bugs. Time allowing if I uncover any new usability functions I’ll report back.
Upgrading WebLogic might be a small nuisance. A newer version of Java isn’t a shock, I already get prompted to update Java more often than Acrobat! Upgrading server operating systems could be a hassle though.
If you’re not already running Linux 6 or Windows 2012 I’d say talk to Oracle support. Most of those bug fixes for Studio are available as patches for 3.1. Your business users will appreciate the bug fixes, but from what I’ve looked at so far they may not gain much from you upgrading Windows.