Do not use the IBM Content Collector Expiration Manager when archiving Lotus Notes calendar entries in a mailbox management scenario, because this might lead to data loss when archiving appointments that users have created locally in their own mailbox.
When archiving Lotus Notes calendar entries that users have created locally in their own mailbox, but have neither sent nor received, the "Received Date" metadata attribute is extracted with a value of January 1st, 1970, instead of the creation date of the document.
Normally, the ReceivedDate metadata attribute is set to the DeliveredDate item. If the DeliveredDate item is not available, the ReceivedDate attribute is set to the PostedDate item. Locally created calendar entries have neither a DeliveredDate item nor a PostedDate item (because they have never been sent). In this case, the ReceivedDate attribute should be set to the creation date of the document. However, the ReceivedDate attribute will be set to the default value 01/01/1970.
This might lead to data loss, particularly if both of the following two conditions exist:
- The task route that is used is either a mailbox management task route that includes the "Calendar entry" message type, or a special task route to archive calendar entries.
- A "Calculate Expiration Date" task that computes the expiration date based on the ReceivedDate metadata attribute has been added to the task route.
None of the task route templates that are delivered with IBM Content Collector fulfill both of the above prerequisites. By default, the "Calendar entry" message type is excluded from archiving in task routes for mailbox management. Calendar entries are archived only with the special task routes "CM_LD - Archiving Calendar Entries" or "P8_LD - Archiving Calendar Entries". In addition, neither mailbox management task routes nor calendar entry task routes use a "Calculate Expiration Date" task. The "Calculate Expiration Date" task is included only in journal task route templates by default. Because local appointments have never been sent, they do not end up in a journal. For this reason, it is not anticipated that journal scenarios will be subject to the issue described above.
If both conditions exist and you run the IBM Content Collector Expiration Manager, locally created calendar entries are deleted from the archive, because their expiration date was set to a date much earlier than their actual creation date.
If you are running IBM Content Collector in production in the scenario described above, contact IBM Response Center. Do not run the Expiration Manager and disable any life cycle task routes that stub or delete calendar entries.
If you are not running in production yet or if you plan to include calendar entries in the future, install Interim Fix 001 for IBM Content Collector Server 220.127.116.11, which implements changes to address this issue.
IBM Content Collector 18.104.22.168 Interim Fix 001 is available on Fix Central for download.
For additional support questions, contact the IBM Response Center at 1-800-IBM-SERV.