Back to top

Aspire 2.1 - Overview

Aspire 2.1 is a major release that builds on the legacy of previous versions, maintaining the dedication to standards based technologies, component enabled flexibility and focus on scalability with performance. Defining aspects of this release:

  • Staging repository
  • Decoupling of core and connectors/pub
  • Performance reporting tool
  • Index auditing tool
  • Group Expansion refactor
  • Ability to map fields without changing the XSLT

Staging Repository

A full crawl of multiple data stores can consume significant amounts of networking, application and connector resources. Previously, connectors only published processed content directly to the target system, typically a search engine, and when the job is finished it is thrown away without maintaining a local copy. 

With Staging Repository support, connectors can be configured as they are today to crawl “source” repositories such as SharePoint and Documentum, but can publish to a 'local repository” on a local disk providing fast access when needed. This enables Aspire's Local Repository connector to quickly access that content with a much lower burden on the IT infrastructure and perform any necessary processsing and publish to the target system as required. Also the reprocessed content can be written back to the Staging Repository to support background processing.

This new functionality enables search and Big Data engineers the agility to do continuous quality improvement, testing new content processing ideas and using the results to update the system enhancing user satisfaction.

Decoupling of Aspire Core from Connectors and Publishers

In previous versions of Aspire, Connectors and Publishers were required to be updated in lockstep with the version of Aspire Core. This decoupling breaks this dependency for versions going forward.  Starting with Aspire 2.1, customers will be able to upgrade connectors, publishers and other components independent of the Aspire Core. Likewise, they will be free to upgrade the Aspire core without upgrading connectors and publishers.

Performance Reporting Tool

The efficiency of content processing is critical to the success of the overall solution. The Performance reporting tool logs statistics about the processing work done by Aspire (content processing, data extraction, crawling, indexing, etc.) and helps identify bottlenecks. This tool provides a report with data on the time it takes to do individual processing steps within an Aspire job and help find bottlenecks, allowing engineers to make modifications to increase productivity. 

Index Auditing Tool

The Aspire Index auditing tool is a feature to help Aspire Administrators easily maintain consistency between the search engine index and Aspire publisher.The Index Auditing consists in three new additions: Content Source auditing, Search Engine index auditing and a Reconciliation file. Content source auditing keeps track of the actions done within the specific content source. Search engine index auditing does a dump of the documents from the search engine specified by the publisher in the content source and creates an internal report. The Reconciliation file is a comparison between the Content source report and the internal search engine report.

Group Expansion Refactored

Group expansion refers to the process of receiving a username and calculating the full set of groups to which the user belongs, a critical part of support for document level security. Aspire 2.1 includes a major rewrite of Group expansion to provide better performance, reliability and ease of use.

Ability to Map Fields without Changing the XSLT

This feature simplifies mapping Aspire document object fields to the specific search engine index schema without having to hand modify the XSLT. This is accomplished by using the Field Mapper application in the Aspire Administrator's UI to simply add as many field mappings as they want, and then choose a type for each field mapping. This turns a developer's task into one an administrator can perform.

0