Recent Posts by Jim Prantzalos

Introduction When it comes to debugging Endeca Content Acquisition System (CAS) related issues, there are few tools that Endeca developers have at their disposal to aid them in their troubleshooting. Most know to review the CAS service logs, but occasionally an issue arises where a peek inside a record store can be very revealing. If you’re a savvy Endeca developer you already know that you can export record store content using the "recordstore-cmd" command. Combined with a...

Introduction Single sign-on, or “SSO” as it’s commonly referred to, is an authentication method that allows a user access to multiple applications through a single, secure, point of entry. Rather than authenticate separately for each application, users authenticate once through a centralized service. The benefits of SSO to end users are obvious, but there are also many cost and compliance advantages that are of interest to large organizations, which is why Oracle’s enterprise...

Introduction I've always felt that the best way to understand something is to take it apart and try to put it back together. In this blog we'll be doing that by deconstructing the Endeca application scripts and reconstructing them in Java, revealing their inner workings and familiarizing developers with the Endeca CAS, RecordStore, and EAC API's. Beyond exploring these API's, the solutions presented herein may be useful to Endeca application developers needing...

Introduction When working with Endeca indexes, a question frequently asked by customers is whether it is possible to insert quality checks into the baseline update procedure, such that if the checks don’t succeed, the baseline update doesn’t proceed. In this blog I will demonstrate a technique using the Endeca CAS API that allows customers to validate the data in a Record Store to ensure the quantity/quality of data, prior to performing a baseline update. This technique can be...