K2 SyncService
K2 SyncService
K2 SyncService is synchronization service which is used to synchronize records (Contact Persons) with Exchange server. This service synchronizes records with K2 IS via Application Server. Application server therefore must be installed and launched. Records are always synchronized with K2 IS at which Application Server, communicating with K2 SyncService, is connected.
If K2 SyncService is launched, it allows synchronization both ways, i.e. it creates record in Exchange server or possibly creates new contact person in K2 IS.
Service at synchronization reads first Primary Source records. Primary Source for synchronization is always K2 IS. This can also be seen in Primary System field in form where we set up synchronization. Further description is available in Synchronization Settings chapter.
Primary source is important also to resolve synchronization conflicts. Conflicts happen in case of identical records, i.e. when there’s equal contact person in Exchange server and in K2 IS. During synchronization K2 SyncService compares Electronic Addresses from Primary Source, i.e. from K2 IS and compares them with all fields on the other side. If conformity is found, conflict arises. Record is always modified according to Primary Source.
Contact person must be assigned to synchronization. This can be done by checking Synchronization Exchange field on page 5 of contact person.
Picture: Contact Persons – page 5
If contact person has Synchronization Exchange field checked, it’ll be added to Exchange server and it’ll always be synchronized with the server. If contact person is saved in Exchange server and during synchronization is located in K2 IS, this field is automatically checked by K2 SyncService.
Synchronization settings
Synchronization settings are available in K2 IS via function no. 1095 Admin - contact synchronization with Exchange settings. Button for this function must be added to desktop. User must have Contacts synchronization with Exchange settings right set up. All settings are only for initial synchronization set up! We don’t recommend to change the settings during later use of synchronization service.
After function is initiated form for synchronization set up is displayed.
Picture: Contacts synchronization for Exchange set up
Contacts synchronization with Exchange settings tab is used to set up Exchange server box (MBox). K2 SyncService runs against this box and with this account records will be synchronized. Email address of the box in Exchange server is set up in Exchange Sync Email Address field. User name and password for this account is then set up in fields Exchange Credential Username and Exchange Credential Password.
Primary System field provides information about primary source to resolve synchronization conflicts. Field cannot be edited and is for information only. Primary Source is always K2 IS.
Exchange Sync Time Interval field is used to set up synchronization repetition interval. Value is entered in milliseconds. Default interval set up is 1500 milliseconds.
Form to set up synchronization of Electronic Addresses can be displayed with Mapping of Electronic Addresses Fields button.
Picture: Set up of electronic addresses for synchronization
In form there are electronic addresses of Exchange server which can be with K2 SyncService synchronized with K2 IS. Specific type of electronic addresses from contact person in K2 IS can be here assigned to these electronic addresses. Electronic addresses of contact persons are always synchronized according to this set up.
Fields Mapping tab is used to set up other fields’ synchronization of contact person with Exchange server. In this tab we assign appropriate field of contact person from K2 IS to specific field in Exchange server. However no electronic addresses!
Picture: Fields Mapping tab
New item can be inserted with Insert key.
Picture: Form to pair synchronization fields
In form we add name of filed from K2 IS contact persons to K2Field. Exchange Field is used to define adequate field for Exchange server. When saved these fields will always be synchronized against each other with K2 SyncService.