What's Different in Aspire 2.0?
For Information on Aspire 3.1 Click Here
The Aspire 2.0 release has six major areas of focus:
- Improved Administration UI
- Graphical interface for Content
- Workflow support for content processing logic
- Integration of Hadoop
- Server administration
- Bug fixes
Administration UI Aspire 2.0 brings the concept of Content Sources to the forefront. A Content Source is a specific configuration of Aspire access, content processing and publishing applications. For example connection to content in a Lotus Notes repository, processing of that content to normalize people and product names and then publishing the content to an instance of Solr searches. Multiple Content sources can publish to the same search engine to provide a single point of search across disparate content sources. The improved process of developing Aspire solutions begins with selecting from one of many connector types such as File, Database, SharePoint 2010 or 2013, Amazon S3 and providing the configuration information
Work Flow support for content processing logic The new Aspire 2.0 Administration UI includes a drag and drop graphical interface for defining the workflow of content processing within Content Sources. In the previous version of Aspire, this was done by writing an XML. The new Workflow section of the Aspire UI permits administrators and solution engineers to drag and configure processing and logical components to define the workflow for the required content processing , including connecting to the specific Aspire Publisher to post content to the selected search engine.
Integration of Hadoop The advent of Hadoop to store and process data and content is a major IT trend in many organizations. Aspire 2.0 has the ability to write to HDFS the file system for Hadoop) and then create and run map/reduce jobs on that data. This powerful functionality opens up content processing to take advantage of elastic computing resources for storage and processing, run complex analysis algorithms that were not feasible for most organizations in the past and provide greater understanding of the content, resulting in higher levels of relevance and improved user satisfaction
Content Source Failover -Whenever a system on a server involves reaching out to other processes running on other servers across networks, there will be multiple points of potential failure and eventually the system will go down. Aspire 2.0 utilizes ZooKeeper as a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. This allows Aspire to sense when a Content Source goes down and quickly restart it with the correct configuration, resulting in a more reliable system
Bug Fixes – See release notes