Documentum Composer Cache

Raghu_A

I have seen this now quite a good number of times.

Using Documentum Composer for Documentum 6.5, I created a custom aspect Module and aspect type. Once done I deployed it to Documentum Content Server and everything worked like a charm. However, later on I edited my aspectType to include a new attribute and then Installed the Documentum Composer project back to Documentum Content Server. Now when I called my aspect's new property I was always getting a Bad Attribute Error message indicating that the changes to Aspect attributes have not yet been picked up either on my client side or on my server side. I already deleted the cache which is present on the client side's calling JVM however, I want to know if there exist any other cache either on Documentum Composer side, client side, server side which could be the culprit for this issue?

Thierry1

Hi,

Which cache are you refering to  on the client side's?

Else, this could be a DFC BOF cache issue.

You can try flushing the DFC BOF cache used by your client. To find the location of this cache, look for the dfc.data.dir entry in the dfc.properties. The DFC BOF cache is located in dfc.data.dir/cache/<DFC_VERSION>/bof/REPOSITORY

1. Stop your DFC client

2. Remove all the files in the dfc.data.dir/cache/<DFC_VERSION>/bof/REPOSITORY directory

3. Restart your DFC client

Thierry