Aspire is a framework and libraries of extensible components.
...
Aspire is designed to enable creation of solutions to acquire data from one or more content repositories (such as file systems, relational databases, cloud storage, or content management systems).
Aspire uses Apache Felix (an open source implementation of OSGi).
Anchor | ||||
---|---|---|---|---|
|
Aspire is flexible. By pulling data processing pipelines out of the search engine, Aspire uses its power and efficiency to:
The Aspire framework supports creating Natural Language Processing (NLP), machine learning, and other analytic processing for text through a rich set of basic components.
You can install, start, stop, update, and uninstall Aspire components and applications.
...
...
...
...
...
...
...
...
...
Anchor | ||||
---|---|---|---|---|
|
The administrator installs, configures, and maintains Aspire deployments. Manage Aspire deployments using a web-based, point-and-click interface, which is the same one an Aspire developer uses. However, an administrator needs to fill in only configuration information. Depending on your environment, you can use a single Aspire system administrator or several; each responsible for different content sources.
The System Administration UI has the following main functions.
Administration UI security
Connection security
Document level security
Anchor | ||||
---|---|---|---|---|
|
Aspire deployments are built dynamically from components and subcomponents. Aspire also includes the concept of application bundles, which are groups of pre-packaged components that perform a specific function and contain embedded files to define their look and feel within the Aspire Administration UI. System developers can combine components easily to process data according to the specific needs of an application. You can mix Standard Aspire components with custom third-party components or with new components.
The high level developer’s view of Aspire processing control is based on three major component types.
Anchor | ||||
---|---|---|---|---|
|
Distributed processing and automatic threading
The ability to split document processing jobs into sub jobs that can run in parallel
Standard technology to manage and restart processes on servers for high availability
Can be placed within an architecture for Backup Failover
You can divide Aspire deployments into three high-level functional areas: content access, content processing, and publishing.
Component - An atomic piece of Aspire logic.
Aspire Core releases use version numbers to identify which software an Aspire solution is built upon.
Anchor | ||||
---|---|---|---|---|
|
Note: Aspire Connector version numbers match the major and minor releases. Over time, the numbers after the major digit can diverge.
There is no version dependency between Aspire Core and Connectors / Publishers. This allows Search Technologies to release new versions (of Connectors or Publishers) independently of Aspire Core releases. The major version number must always match.
...