Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "SMILA/Documentation/ConnectivityManager"
(→API) |
m (→Implementations) |
||
| Line 9: | Line 9: | ||
== Implementations == | == Implementations == | ||
| − | It is possible to provide different implementations for the ConnectivityManager interface. At the moment there is one | + | It is possible to provide different implementations for the ConnectivityManager interface. At the moment there is only one implementation available: |
| − | ===org.eclipse.smila.connectivity. | + | ===org.eclipse.smila.connectivity.bulkbuilder=== |
| − | This bundle contains the default implementation of the ConnectivityManager interface. | + | 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 Record objects are | + | 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 record and micro bulk 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]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== Configuration === | === Configuration === | ||
There are no configuration options available for this bundle. | There are no configuration options available for this bundle. | ||
Revision as of 03:51, 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 record and micro bulk API.
This chart shows the Connectivity Manager implementation, it's Sub-Components and the relationship to other components:
Configuration
There are no configuration options available for this bundle.