4.1 The Sage CRM connection plugin

The following parameters are available for a Sage CRM connection:

1.1 Displayed name	will be used in the SIS administrator and in the CRM as a designation for this connection.
1.2 Description	can contain administrative hints which will only be shown in the SIS administrator.
1.3 ID	Data base ID of the connection (write-protected).
1.4 Adapter name	Name of the plugin (write-protected).
2.1 URL for webservice	The URL to the desired CRM instance (the part before "eware.dll"). The SIS uses the webservice of the CRM for reading and writing data.
2.2 User name for webservice	A CRM user name with activated webservice access. It is recommended to use a user here whose password needs to be changed randomly and who may read and write all relevant data. The webservice access underlies the authorisation control of the CRM. Data which are not available for the user, cannot be synchronised. For instance the system administrator is recommendable. CRM registration of webservice and Desktop/mobile could be carried parallely whereby the integration can also be implemented by a real user. Just the transperancy (Created by, Updated by) suffers.
2.3 Password for webservice	Password of the user

3.1 Proxy server	If the SIS can only reach the CRM by a proxy, you can configurate it here.
3.2 Proxy user name	User name for proxy, if required.
3.3 Proxy password	Password of the user, if required.
4.1 Data base type	For a standard integration with Sage CRM, it is completely sufficient to leave the type on "None". The SIS also supports a data base access to the CRM which however should not be used for the synchronisation. The following situations favour the installation of a reading data base access: You would like to install the data services on the CRM. You can leave the parameter 4.2 on "No". You would like to read larger data volumes from the CRM. Here the speed of the webservice is limited. The writing access on the CRM data base needs to be activated manually at each process and data service. Therefore, no business logic will be implemented when writing (TLS, system columns). If data services with larger data volumes need to be saved in the CRM, the capacity of the webservice can exceed. In this case, the data base access can be recommended in order to optimise implementation time and system load. The data base access can also be used in a temporary process for mass updates for instance when panel alloactions have been changed.
4.2 Use data base connections for demands	Read data from webservice and data base differentiate textually. The webservice translates selection panels according to the language of the used CRM user. Data base accesses deliver raw data what could affect falsified on your transformations and allocations. This parameter is not required for the usage of CRM data services and writing data base accesses.
4.3 Data base server	Address of the data base server inclusive available instance designation if applicable.
4.4 Data base user name	SQL user name
4.5 Data base password	Password of the user
4.6 Data base	Name of the CRM data base. This one normally has the same name as the instance.
5.1 Deactivate connection verification	The connection verification verifies the webservice connection before each action by invoking the CRM version. If the connection is broken, it will be reconstructed. Without this connection verification, a broken connection leads to an error and an error resolving. Deactivating the verification reduces the load on the CRM.
Update scheme (checkbox)	The saving with activated checkbox updates the data scheme of the connection in the SIS.