I recently worked with a customer, and have 2 others come in right after that. They had been working with Filenet for a few months and just noticed that they were not getting notifications from files or updates to file uploaded to CCM libraries. The problem was always something in this part of the filenet configuration
Once we corrected it, notifications began working again. The easiest way to test was to upload a file, then access recent updates in the community. If the file information appeared there, notifications is working correctly from files to news.
The problem for these customers was just after we fixed the issue, people started getting mail notifications of files that were uploaded months an months ago. The reason for this is because if Filenet fails to send the event to the news component it saves it in a table in the DB and will try again later. These had backed up over the months and now it was working started being sent.
The following steps will remove the rows from this table so you don't have to get mail notifications about something that happened a long time ago:
- Stoping of Connections,
- Backuping of databases (FNOS and FNGCD),
- Removing all rows from the LCUSER.UT_CLBACTIVITYSTREAMQUEUEENT table except the row with OBJECT_ID = "00000000000000000000000000000000",
DELETE FROM LCUSER.UT_CLBACTIVITYSTREAMQUEUEENT WHERE ENTRY_STATUS = 2 AND OBJECT_ID <> x'00000000000000000000000000000000'