6 Configuration of the data service plugin
The SIS data services will be used in order to process information from a removed system and to make them available e. g. in the CRM. Thereby, those information can be context related to a synchronisation connection (company, person or account) or even completely independet of the synchronisation (My CRM). The data service plugin defines thereby the kind of the source system and in which context the data should be processed.
The SIS supports four types of usage of data services.
The direct implementation
As soon as a data service will be invoken e. g. by the ERP Focus, the defined demand in the source system will be implemented and the processed result will be redelivered. This kind can also be named as real time data display.
For a direct implementation, the data service processing of the SIS does not need to be active.
The buffering in the SIS
By using a data service processing, the demand of the data service can be implemented time-controlled and the result can be saved in the SIS data base. As soon as the data service will be invoken afterwards e. g. by the ERP focus, the demand will not be implemented, but the already processed data from the SIS data base will be redelivered. This option is recommendable when the demand is too complex in order to be provided in a user-friendly time frame.
A combination of the saved and direct implementation is also possible. Thereby, the user can switch between both options in the CRM.
The buffering in the CRM
The demand will be implemented time-controlled also for this buffering by the data service processing. However, the target is thereby not the SIS data base, but the CRM itself where the data will be saved in a generic XML format. In addition, a table mode can be activated in the CRM whereby the XML data will be copied in an own relational table. This increases the demanding speed enormously for extensive data in the CRM, but also augments the saving requirements.
This option offers the opportunity to evaluate the data directly in the CRM for instance in reports, groups or own developments. Furthermore, a direct access on the SIS is not required for this option whereby the systems can also be operated in a separate infrastructure.
The saving of the data will be implemented by CRM webservice and can also be implemented by data base access on the CRM. This can influence the implementation time and the load on the CRM.
Emailing
This option is not a buffering. The demand of the data service will be implemented timed-controlled by the data service processing and will be made available as an Excel file. Afterwards, this file will be emailed to a desired address. This implementation cannot be used in the context of a synchronisation connection
The implementation of the set up data service will be regulated by the queue for data services. Thereby, the data service decides according to its implementation on its own how the next implementation in the queue will be planned ("queued"). That will be influenced for instance by the time-controlling or the debugging. The SIS server does not observe this process. The data service processing needs to be started in order to implement data services by the SIS. This can be implemented by using the context menu of the server node in the navigation tree.
There are 4 possibilities in order to generate a new data service:
By context menu or double click on the plugin
Select the desired plugin in the navigation tree under "Data service plugins". The plugin name includes the type of source and target system as well as if applicable the names of source and target object. The menu option "Generate new data service" and the double click open the characteristics dialogue of the plugin.
This kind of new generation starts with a complete "empty" data service. All parameter and the demand need to be inserted manually.
The menu option "Version information" delivers the version number of the available plugin.
By set up resources
We deliver a collection of data service templates together with the installation files. These are completely defined by a standard scenario and enable a quicker commissioning of the integration.
By using the context menu or double clicking on a template, you open the characteristics dialogue of the plugin with the loaded template. You can adapt these according to your requirements.
By copying
You can open the feature menu by using the right mouse button on a data service under "Data services" in the navigation tree. The entry "Copy" generates a new data service based on the selected one.
The following features can also be selected:
| Activate time schedule | In case a time-controlling is defined, the entry will be generated in the queue at the earliest possible date.
|
| Deactivate time schedule | In case a still not processed and planned entry is available in the queue, it will be deleted. Running processes will not be influenced.
|
| Start manually | Generates an entry for the immediate implementation in the queue. The implementation proceeds thereby as a planned implementation. |
| Start manually for a record | Generates an individual transfer for the immediate implementation in the queue. Thereby, the ID of the data image need to be provided. |
| Export | The data service can so be exported in a file in its current definition. This can then be imported with the SIS administrator in a desired SIS installation. For this, it needs to have the required plugin available. |
| Copy | see above |
| Delete | So you delete the data service, all bufferings, all entries in the queue and the record for this data service. The deletion is definite. |
| Version information | see above (plugin) |
| Characteristics | Opens the characteristics dialogue of the plugin with this data service |
By import
You can implement the import of a data service definition by using the context menu on the entry "Data services". For this, you require the XML file from the data service export or the set up resources. After selecting the file, the characteristics dialogue will be opened.
Furthermore, this menu contains features for activation and deactivation of time schedules as well as for a manual start of all available data services. In case a data service does not have a valid time schedule, it will be skipped.