Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search


This is deprecated for SMILA 1.0, the connectivity framework is still functional but will aimed to be replaced by scalable import based on SMILAs job management.


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.


See javadoc: org.eclipse.smila.connectivity.ConnectivityManager


It is possible to provide different implementations for the ConnectivityManager interface. At the moment there is only one implementation available:


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: ConnectivityManager-0.9.0.png

(original slides can be found here:

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.


There are no configuration options available for this bundle.

Back to the top