The configuration is stored in a file named Apsis.Service.exe.config located in the installation folder. Since the installation folder is usually protected by Windows, administrator privileges are probably necessary to edit the file. The configuration file specifies how the application can access the Lime CRM database (through Lime CRM Web Service) and the Apsis account.

The following is an example of a typical Apsis Integration configuration file:

<?xml version="1.0"?>
    <section name="lundalogik.dataaccess" type="Lundalogik.DataAccess.Configuration.DataAccessConfiguration, Lundalogik.DataAccess" />
    <section name="lundalogik.apsis" type="Apsis.Configuration.ApsisConfigurationSection, Apsis.Configuration" />
      <database name="LIME" accessMethod="WebService">
        <webServiceOptions binding="BasicHttp" address="http://limeapp01.lundalogik.local:4057/" />
        <lime database="LIME" />
        <apsis userName="lundalogikab" password="t0ps3cRet!" />
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>

The lundalogik.dataaccess section specifies how the application connects to Lime CRM Web Service for adding and updating Lime CRM data. The name attribute of the database element must match the database attribute of the lime element in the lundalogik.apsis section. Apsis account details are specified in the apsis element. The apsis userName is the Apsis-API account, specified for the customer (customer must order this in advance). The standard Apsis Integration can only be mapped to ONE Apsis account.

It is possible to modify how often the service synchronizes data with the Apsis web service.


The format used for these attributes is “d.hh:mm:ss”, e.g. “1.00:00:00” is once every day and “08:00” is once every eight hours.


These settings should only be changed in rare cases or for troubleshooting purposes as they can severely impact performance and also result in overloading the Apsis servers.

  • Last modified: 5 years ago
  • by Isabel Azcárate