Further features

CollectedMailboxes.xml

By default, connector gets the list of users whose mailboxes are supposed to be synchronized from Aurea CRM.

Furthermore, connector supports additional filtering of the user list via an XML file (CollectedMailboxes.xml). If such a file exists in the installation directory the list of users (mailboxes) is restricted to the users, which are both activated in Aurea CRM via their ID table settings and their e-mail addresses are included in the file.

This feature, on the one hand, allows for faster initialization of the service since building the synchronization list is quite an expensive operation for connector and on the other hand might help to analyze purposes since with this feature you can quickly reduce the number of synchronized users to one by editing the XML file.

To create this XML file start update.Server.exe with the parameter "- collectMailboxes". The service creates the XML file and will end itself afterward.

While generating a new CollectedMailboxes.xml file an empty section is added to the file. All the mailboxes that aren't supposed to be synchronized should be copied into this section, so that connector can retrieve the short names from this section. This is necessary, since connector cannot retrieve the short names from Domino Server in case of the usage of CollectedMailboxes.xml file as input source

Assume the following situation:

somebody sends an e-mail to two recipients using the short name address and only one of the recipients is supposed to be synchronized (and therefore listed in the CollectedMailboxes.xml file). In such a situation connector cannot recognize that the address of the second recipient is a short name and therefore cannot resolve this address into the SMTP address. With the second recipient added to the <NonSyncDataSources> section, connector can convert the short name address into the SMTP address and CRM.interface can assign the e-mail to the user in Aurea CRM.

Example configuration of CollectedMailboxes.xml

<Logging>
<!-- logLevel - possible values are: NoLogging, Emergency, Alert, Critical, Error, Warning, Notice, Info, Debug -->
      <Channel  logLevel="Warning" 
                writerName="ConnectorfileLogWriter" 
                formatterName="Default"/>
<!-- rollingMode - possible values are: Date (when date changes), Size (when exceeding defined size), Startup (on every startup). Values can be combined, e.g. "Size,Startup" means when exceeding the size and on every restart of connector -->
      <Writer   filePath="log\connector.log"
                name="ConnectorfileLogWriter"
                maxSizeKB="50000"
                rollingMode="Size,Startup"
                compressBackup="true"
                maxBackups="50"
  includeDateInBackupFileName="true"
                closeOnIdleTimeout="5"
                type="update.Lib.Logging.Writers.FileLogWriter,update.Lib"/>
      <Formatter name="Default" 
                logDate="true" 
                logTicks="true" 
                logFacility="true" 
                logLevelFormat="Name" 
                logException="true" 
(on every startup). Values can be combined, e.g. "Size,Startup" means when exceeding the size and on every restart of connector -->
      <Writer   filePath="log\connector.log"
                name="ConnectorfileLogWriter"
                maxSizeKB="50000"
                rollingMode="Size,Startup"
                compressBackup="true"
                maxBackups="50"
  includeDateInBackupFileName="true"
                closeOnIdleTimeout="5"
                type="update.Lib.Logging.Writers.FileLogWriter,update.Lib"/>
      <Formatter name="Default" 
                logDate="true" 
                logTicks="true" 
                logFacility="true" 
                logLevelFormat="Name" 
                logException="true" 
                logMemory="True" logCpu="True" 
                type="update.Lib.Logging.Formatters.DefaultLogFormatter,update.Lib" />
</Logging>

Sending warning and error messages to users

CRM.connector stores the reason of the last failure on the message or appointment level (mmSyncStatus property) respectively, so that only one message per item is sent unless the reason for an error changes.

In other words, in case that the reason for a failure matches the one stored in the mmSyncStatus property, no additional message is sent to the user. Restarting the connector does not change this behavior.

There is one exception from the above rule: if connector fails while reading/decoding a message, this usually means that the connection with Domino Server was lost/failed. In this case it is not possible to save any changes to the message (cannot store the reason on mmSyncStatus) and it can happen that connector sends multiple error messages to the user, but connector will hold this information in memory and not send the error message as long the item stays unchanged and connector is not restarted.

These options are intended to give feedback to the users in case that during the synchronization of items either not the full information could be synchronized (e.g. if an attachment exceeded the configured size limit) or an error occurred (e.g. that due to fact, that the message could not be assigned properly in the CRM system).

Although connector typically – see details above - doesn’t send multiple error / warning messages for the same item, in case of a systematic problem enabling this option could result in lots of messages to the dedicated users.

For example, if the e-mail address of the synchronizing user is not unique in the CRM system, such an error message would be sent over and over (for every new item), unless this problem is corrected.