Versions Compared

Old Version 3

changes.mady.by.user Lyndsey Burt

Saved on

compared with

New Version 4

changes.mady.by.user Andres Aguilar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • connector instance
    • General behavior of connector application inside the worker. Mostly all properties under "Advanced Configuration" in Aspire 4.0 are present here. Connectors API
    • A single connector instance can be reused for many different connections.
  • credential
    • All access related properties, account names, passwords, authentication type, etc. Credentials API
    • A single credential instance can be reused for many different connections.
  • connection
    • Everything that has to do with the actual connection to the repository like: server URL, connection timeouts, proxies, etc. Connections API
    • Can be associated with 1 credential instance.
    • Can be associated with 1 connector instance
  • workflow
    • Same old workflow, this must be configured from scratch on the UI or via REST commands, as this is no longer an xml file. Workflow API
  • schedule
    • Similar to the "content-source" schedules in Aspire 4.0, it supports time schedules, but also supports the new "sequence" schedules which can trigger crawls after another schedule has been completed. Schedules API
  • policies
    • New to Aspire 5.0, there are two types of policies Policies API.
      • routing
        • Determines which worker nodes can receive jobs flagged with certain tags. Must be applied to seeds.
      • throttle
        • Throttles job batch delivery to worker nodes, allowing the crawl rate to be controlled.
        • Can be applied to seeds, connections or credentials
  • seed
    • Starting point of a crawl. Seeds API
    • In Aspire 4.0 this was a list of URLs in the same content source, or a file containing all the seed URLs. In Aspire 5.0 each seed must be configured separately, and crawl independently of each other.
    • Can be associated with one or more schedules
    • Can be associated with 1 connection instance
    • Can be associated with 1 throttle policy
    • Can be associated with 0 or more routing policies
    • Can be associated with 0 or more workflows (will execute sequentially)

What's next?