Aspire 5.0 compared to its predecessors Aspire 3.x and 4.x had a major architecture re-design, for the purpose of tackling the most common source of complexity in managing Aspire deployments: configuration, availability, coordination of crawl execution.
The biggest change you would noticed compared to prior versions is that there isn't a content-source anymore. The configuration of crawls have been split into re-usable peaces with relationships to one another.
What used to be called a "content-source" now is a collection of related configuration objects:
- Connector
- Common connector behavior
- Credential
- To authenticate to a specific repository
- Connection
- Server IP/host/port
- Connection properties (timeouts, concurrency, etc)
- Throttle and Routing Policies
- How often should documents be processed
- Which nodes should the documents be processed
- Workflow
- Sequence of rules to be executed for each document
- Seed
- Starting point of a single crawl to execute
In this new approach of configuration, you can configure everything only once and reuse them to create multiple seeds for the same source repository. So if you need to change the credentials, you don't have to do it on all seeds but rather on the credentials object only, and all seeds related to it will be affected.
Overview
Content Tools
Copyright © 2024 Accenture
