How to Identify whether Oracle Coherence is correctly Configured in Webcenter Portal Application

This blog explains about various techniques to monitor whether Coherence is properly configured and actively being used for a Portal application or not.

Remember,  it's important to note that not all the content that you fetch from UCM will automatically gets cached. Only if you are using Content Presenter or other out of the box components then it gets cached. Any calls using RIDC and not using content presenter would not be cached. 

- If you notice below entry in your <Managed_Server>-diagnostic.log file, that means coherence is not properly configured, you need to correct.

[APP: AviTrustSamplePortal#V2.0] Unable to load Coherence configuration file content-coherence-cache-config.xml. Using in-memory (local) caches.

- Use Oracle EnterPrise MBean Browser as shown below
     - Login to Enterprise Manager
     - Select the application which you want to verify
     

- Select 'Application Deployment' drop down, Select 'System MBean Browser'

       - Ensure, You should see 'Managed Server Instances' in 'Application Defined MBeans -> Coherence' , If you don't see your managed server instances here, that means Coherence is not configured .

 - Another way of identifying is, Login to 'Webcenter Content Server'
 - Select 'Administration-> System Audit Information'
- Select 'system, requestaudit' and 'Full verbose Tracing' ash shown below, click on 'Update'

- Click on 'View Server Output' link
- Clear the content by 'Clear' link
- Open the page which has content presenter, Click on 'Refresh' button on UCM Server - View Server output window
- You should see a query and execution time in the UCM Log
- Now clear the log, and refresh the page again, You shouldn't see that query in UCM, It should have got the data from Oracle Coherence.

Trouble Shooting
- Ensure 'portal-coherence.jar' available in src->APP-INF->lib
- Ensure 'content-coherence-cache-config.xml' contains valid entries based on your requirements, focus on 'local-cache' or 'distributed-cache' based on your hardware infrastructure, concurrent user count, throughput
- Ensure 'portal-coherence.jar' deployed to '/tken4o/admin/wcp_domain/mserver/wcp_domain/lib' - This is example only, you need to find your {WL-HOME} path and identify as per this.