When upgrading to CE 5.0 or 5.1, the CE asynchronously upgrades Object Store metadata to the current release level. This includes upgrading the metadata of CFS-IS federated documents and annotations. Two issues have been found with federated documents being processed through the asynchronous upgrade process. These issues must be addressed before starting an upgrade to CE 5.0 or 5.1.
1. If CFS-IS updates occur on federated documents that have not yet been processed through the async upgrade process, the CFS-IS updates will be dropped. No errors or logging will indicate this and the updates will be lost. The metadata of these federated documents will now be out of sync between the IS and CE.
2. CE 4.x (4.0.1, 4.5.0 and 4.5.1) federated documents that have duplicate annotations, cause the CE 5.0 or 5.1 async upgrade to fail. This is because CE 4.x allows for duplicate annotations on federated documents but CE 5.0 and 5.1 do not.
Both of these issues will be fixed in upcoming CE 5.0 and 5.1 Fix Pack releases.
Currently there is a Test Fix available for CE 5.0 (188.8.131.52-P8CE-ALL-TF009), which must be installed prior to upgrading. A similar Test Fix for CE 5.1 can be made available through a request to IBM Support.
A work-around to the first problem can be achieved by disabling the CFS-IS dispatcher prior to the CE upgrade. This will stop CFS-IS updates from occurring. Disabling the dispatcher is done through the IS Import Agent tab in FileNet Enterprise Manager. The dispatcher should remain disabled until the asynchronous upgrade process completes. You can check the status of the asynchronous upgrade process through this link (which needs to be customized for your environment): http://<server>:<port>/FileNet/AutomaticUpgradeStatus
Please refer to Tech Note 1514824 for more details.
|Enterprise Content Management||FileNet Content Federation Services||Content Federation Services for Image Services|