Collaboration

Whether the information was retrieved from pre-cached information. See

The Pre-caching sync. data group of functions contains the following field:

Pre-cache enabled
If this field is set to Yes, pre-caching is enabled on the server. Please note that if you are using a technical user (DME_Server) for scanning the users' mailboxes, this technical user must have full access to all the users' mailboxes for pre-caching to work correctly. You are using a technical user if the field Store user password (encrypted) in the Authentication panel is No (see Authentication). If this is the case, you must accept a warning about this in order to enable pre-caching.

See below for an explanation of the DME concept of pre-caching.

Pre-caching is a mechanism to reduce the time it takes to synchronize e-mails to the DME client. This mechanism was introduced in DME 3.5 Service Pack 7. Pre-caching does not require any new client.

Whenever the notification scanner detects a change in a user’s mailbox, a request is sent to the connector in charge of synchronizing that user’s e-mail. On receiving the request, the connector immediately begins to build a read-ahead cache where links to the user’s e-mails are stored. When the cache is complete, the notification scanner sends a push using Adaptive Push to the client with information that new e-mail has arrived. When the client connects to the server in order to pick up new e-mail, the synchronization request is routed to the pre-built cache, and the new items are immediately available. Before synchronizing, the connector checks if a new e-mail has arrived in the space between the building of the cache and the actual synchronization by comparing the latest e-mail in the cache with the latest e-mail in the collaboration system.

If the cache exists already, it will be used if it is less than 30 minutes old. This means that any changes such as marking read/unread, moving to folders etc. that have been made in the collaboration system within this period of time will not be reflected in the DME client until the next synchronization.

If the cache is older than 30 minutes, the mailbox content from today and yesterday, including changes due to marking read/unread and moving to folders, is read out from the collaboration system and merged into the cache.

The cache is removed when the client synchronizes. See illustration below.

This applies to push, scheduled, and manual synchronization. In case of an import, the cache is never used.

Benefit

The user will experience significantly faster e-mail synchronization when receiving a push, because the server can compare the contents of the client's mailbox with the cache and does not need to contact the collaboration system for anything other than getting the new e-mails (or information about deleted or read e-mails, or whatever is required by the changes discovered in the mailbox). This speed optimization is especially significant on devices that do not support e-mail synchronization as a background process (as in Apple's iOS).

Security

The cache stored on the connector does not include the e-mails as such, only an MD5 checksum and a reference to the e-mail (a so-called minimal note). The e-mail content is stored securely in the collaboration system mailstores.

S/MIME

Due to the way in which S/MIME e-mails are handled by the collaboration system, enabling pre-caching will not benefit overall system performance if most of your e-mails are S/MIME. In other words, if your users primarily send and receive S/MIME e-mails, you should not enable pre-caching on the server.

Function	This is the type of communication which was performed with the collaboration system. This could be E-mail sync., Calendar sync., Addressbook sync., or E-mail folder.
Operation type header	Depending on the type of connection (function), up to four types of operations can be performed in the collaboration system as a result of a client connection: delete, create, update, and read.
Entries	How many operations of the available types were performed by the collaboration system as a result of the current connection. If a number is preceded by (x2), it means that the specified number of items were read twice.
Duration	How long time did the above operations take.
(total)	This row calculates how long time it took to process each document.
Storage	The path to the user's mail file (Domino) or mailbox (Exchange).
Logon duration	The number of milliseconds it took to log on to the collaboration system.
Total collab. duration	The total duration of the client's interaction with the collaboration system during this session.
Total sync. duration	The total duration of the client's session with the DME server, including authentication, negotiation, etc. This corresponds to the total time of the connector/collaboration system interaction and the device/DME server interaction (see the Synchronizing category).
PreCache	Whether the information was retrieved from pre-cached information. See Pre-caching sync. data. The Pre-caching sync. data group of functions contains the following field: Pre-cache enabled If this field is set to Yes, pre-caching is enabled on the server. Please note that if you are using a technical user (DME_Server) for scanning the users' mailboxes, this technical user must have full access to all the users' mailboxes for pre-caching to work correctly. You are using a technical user if the field Store user password (encrypted) in the Authentication panel is No (see Authentication). If this is the case, you must accept a warning about this in order to enable pre-caching. See below for an explanation of the DME concept of pre-caching. Pre-caching is a mechanism to reduce the time it takes to synchronize e-mails to the DME client. This mechanism was introduced in DME 3.5 Service Pack 7. Pre-caching does not require any new client. Whenever the notification scanner detects a change in a user’s mailbox, a request is sent to the connector in charge of synchronizing that user’s e-mail. On receiving the request, the connector immediately begins to build a read-ahead cache where links to the user’s e-mails are stored. When the cache is complete, the notification scanner sends a push using Adaptive Push to the client with information that new e-mail has arrived. When the client connects to the server in order to pick up new e-mail, the synchronization request is routed to the pre-built cache, and the new items are immediately available. Before synchronizing, the connector checks if a new e-mail has arrived in the space between the building of the cache and the actual synchronization by comparing the latest e-mail in the cache with the latest e-mail in the collaboration system. If the cache exists already, it will be used if it is less than 30 minutes old. This means that any changes such as marking read/unread, moving to folders etc. that have been made in the collaboration system within this period of time will not be reflected in the DME client until the next synchronization. If the cache is older than 30 minutes, the mailbox content from today and yesterday, including changes due to marking read/unread and moving to folders, is read out from the collaboration system and merged into the cache. The cache is removed when the client synchronizes. See illustration below. This applies to push, scheduled, and manual synchronization. In case of an import, the cache is never used. Benefit The user will experience significantly faster e-mail synchronization when receiving a push, because the server can compare the contents of the client's mailbox with the cache and does not need to contact the collaboration system for anything other than getting the new e-mails (or information about deleted or read e-mails, or whatever is required by the changes discovered in the mailbox). This speed optimization is especially significant on devices that do not support e-mail synchronization as a background process (as in Apple's iOS). Security The cache stored on the connector does not include the e-mails as such, only an MD5 checksum and a reference to the e-mail (a so-called minimal note). The e-mail content is stored securely in the collaboration system mailstores. S/MIME Due to the way in which S/MIME e-mails are handled by the collaboration system, enabling pre-caching will not benefit overall system performance if most of your e-mails are S/MIME. In other words, if your users primarily send and receive S/MIME e-mails, you should not enable pre-caching on the server.