I was thinking to restart the series of blogs on Webcenter –
Content (prior UCM, Stellent) from long. I will start with the basic problem
that we face in content server i.e. Cache.
The case study belongs to a Site studio External Application
(SSXA) Project.
My team member was working on one assignment where she had
to update some taxonomy values via Content Server. She had made all the changes
but she didn’t get new values in application although new values were
reflecting in DocMeta table. So she bounced the Content Server then she got the
new values. She was happy!!
Here comes the situation, we can’t bounce the production server
daily or weekly for this purpose. So we need to have some mechanism which can
reflect our changes without bouncing Server. Here are some options:
1. 1. Content Server Cache:
This feature is very important. There might be a case when
you see new data in table or view but it doesn’t reflect in Content Server
forms like in dropdowns, list of values etc. In such cases, you try publishing
schema explicitly. This populates new data changes in Content Server forms.
2. Site Studio External Application Cache:
When we work on Site Studio External Application (SSXA) then
such problems come frequently. This problem is associated with above case, so
you need to be sure that changed values are coming in Content Server first then
you can proceed for Site Studio External Application. We can use Clear
Entire Cache option for Site Studio External Applications.
3. Site Studio External Application Cache via browser:
There is one more trick that you can apply if above both
options didn’t work. Sometimes we send a request to Content Server to clear the
cache and it responses with new values. We use refresh_cache parameter in this
situation. You need to write complete application path and append ?refresh_cache=true
at the end. This will load your page with some delay but it works well.
