Source Adapter
A plugin solution from TIVITY.
Last updated
Was this helpful?
A plugin solution from TIVITY.
Last updated
Was this helpful?
This documentation provides an overview of a plugin solution from TIVITY. First, a brief description of the system is given. After that there is a overview about the process from the plattform request to the adapter and back. Then the individual components are looked at. On the one hand the source adapter itself, on the other hand the REST Service that calls the Adapter.
The adapter provides universal access to information sources. These can be database adapters (MS SQL), object adapters (exchange) or document adapters. The result of a request will be given back accordingly universal valid from the respective adapter. Adapter will be used several times for the same kind of information sources (one adapter instance per source). For example, a database adapter can be used for several available databases.
The overview above illustrate adapters beeing applied in the TIVITY plattform itself. These adapters will be configured on the plattform. For example a database adapter could contain the login credentials for the configuration or a WebService adapter contains the URL to the service. There is another possibility to permit the access to information sources per adapter. This possibility will be explained in the next chapter.
There is already an API for the SourceAdapter that can be implement in a REST Service. The service can then communicate with the plattform. This was made possible by a set of interfaces (API) provided by TIVITY. A customer can use this opportunity to develop there own adapter and configurate and call the service from the plattform.
TIVITY provides a own developed REST Service for customers. This service can be used to build your own adapter. There are still exist source code from an example adapter delivered together with the REST Service in one package. Both are Microsoft .NET projects for Visual Studio 2017.
You can also develop your own service which is for example a pure Java Service. And thus you can also have your own adapter in the chosen technology docking on the service. As long as the REST interface corresponds to the provided service interface, the client can communicate within inside the plattform.
