KM Content Issue

[stephen_spalding]

Hi all,

We are ready to do a hardware swap of our production portal server dispatcher, and we've come across something that we're not sure about. We have both the new and old production portal dispatchers running, and both of them have a reference to a CM FSDB repository. In one particular folder on the old server, we could see files. In that same folder on the new server, we could not see the files.

I made sure that we were not running into a lifetime property issue on the new server. The new server was created with a snapshot of the old server that was made a few months ago. The files that were not showing up in the new portal server had been added since the snapshot had been taken.

I figured that this was a metadata - filesystem inconsistency problem. I tested this theory by adding a file to the old portal server, expecting it to not show up in the new portal server. However, the file did show up in the new portal server. Then I tried adding the exact same file in the old portal server into the original folder whose content was not showing up in the new portal server. After adding that file, the contents of the folder then showed up in the new portal server.

I figured that something got refreshed when I uploaded the file into the folder where the files were not showing up, and that's what made the files suddenly show up in the new portal server. My concern is that there may be other folders where this is the case. We have thousands of folders, and we cannot possibly compare the contents of every one of them on each server.

Is there any kind of command to issue to the portal that tells it to take a fresh look at the contents of it's folders? We are swapping out the hardware this weekend, and I need an answer for my boss about this ASAP.

Thanks!

-StephenS

[abdulbasit · Accepted solution]

I had the similar issue. Although it is really bad solution, you can use if you don't have any other option.

There was a network folder which is filled by non-SAP application and we have created a CM repository with FSDB persistence. When new folder is created on filesystem by application we couldn't see the folder but if we create folder manually on filesystem we could see.the folder on portal.

I couldn't find any solution except this silly solution :

We developed a small windows service which checks the folder for some period of time. When new folder is created, it creates and deletes an empty file in the folder.

In your case, check if you could see the folder contents when you create a file manually. If yes, then you can create/delete file on each folder programatically just once.