Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "SMILA/Documentation/ConnectivityManager"
m (→Implementations) |
(bulkbuilder impl. changes) |
||
Line 15: | Line 15: | ||
This bundle contains the default implementation of the ConnectivityManager interface. It is based on the routing of records to asynchronous workflows resp. jobs (see [[SMILA/Documentation/JobManager|Jobmanager]]). Therefore the records are pushed to the [[SMILA/Documentation/Bulkbuilder|Bulkbuilder]]. | This bundle contains the default implementation of the ConnectivityManager interface. It is based on the routing of records to asynchronous workflows resp. jobs (see [[SMILA/Documentation/JobManager|Jobmanager]]). Therefore the records are pushed to the [[SMILA/Documentation/Bulkbuilder|Bulkbuilder]]. | ||
− | The ConnectivityManagerImpl contains the core execution logic as it does the actual processing of the incoming requests. Incoming | + | The ConnectivityManagerImpl contains the core execution logic as it does the actual processing of the incoming requests. Incoming record objects are pushed to the Bulkbuilder via bulkbuilder's record and microbulk API. |
This chart shows the Connectivity Manager implementation, it's Sub-Components and the relationship to other components: | This chart shows the Connectivity Manager implementation, it's Sub-Components and the relationship to other components: | ||
[[Image:ConnectivityManager.png]] | [[Image:ConnectivityManager.png]] | ||
+ | |||
+ | '''[[SMILA/Documentation/CrawlerController|CrawlerController]]/[[SMILA/Documentation/AgentController|AgentController]]''': Provide the records imported via Crawler/Agent. | ||
+ | |||
+ | '''[[SMILA/Documentation/DeltaIndexingManager|DeltaIndexing]]''': Check if records have changed since their last processing | ||
+ | |||
+ | '''[[SMILA/Documentation/Bulkbuilder|Bulkbuilder]]''': Builds record bulks stored in [[SMILA/Documentation/ObjectStore/Bundle_org.eclipse.smila.objectstore|Objectstore]]. Stores record's attachments in [[SMILA/Documentation/Binary_Storage|BinaryStorage]] via [[SMILA/Documentation/Usage_of_Blackboard_Service|Blackboard]]. | ||
=== Configuration === | === Configuration === | ||
There are no configuration options available for this bundle. | There are no configuration options available for this bundle. |
Revision as of 04:48, 5 September 2011
Contents
Overview
The Connectivity Manager is the single point of entry for data in the SMILA. It's functionality is divided into several Sub-Components for better modularization. The Connectivity Manager and its Sub-Components are implemented as Java OSGi services.
API
See javadoc: org.eclipse.smila.connectivity.ConnectivityManager
Implementations
It is possible to provide different implementations for the ConnectivityManager interface. At the moment there is only one implementation available:
org.eclipse.smila.connectivity.bulkbuilder
This bundle contains the default implementation of the ConnectivityManager interface. It is based on the routing of records to asynchronous workflows resp. jobs (see Jobmanager). Therefore the records are pushed to the Bulkbuilder.
The ConnectivityManagerImpl contains the core execution logic as it does the actual processing of the incoming requests. Incoming record objects are pushed to the Bulkbuilder via bulkbuilder's record and microbulk API.
This chart shows the Connectivity Manager implementation, it's Sub-Components and the relationship to other components:
CrawlerController/AgentController: Provide the records imported via Crawler/Agent.
DeltaIndexing: Check if records have changed since their last processing
Bulkbuilder: Builds record bulks stored in Objectstore. Stores record's attachments in BinaryStorage via Blackboard.
Configuration
There are no configuration options available for this bundle.