Implementing Portlet Caching
Caching on the Portal Server can be set in
two ways: programmatically through HTTP headers and/or using the administrative
settings in the Web Service editor. You should always implement caching
programmatically, although the administrator can still choose to override
caching through administrative settings.
For details on implementing caching, see the following topics:
While caching is an integral and necessary part of portlet design,
it is helpful to disable it while developing and debugging. Otherwise,
it can be very difficult to view the results of any modifications
you have made. To disable the caching implemented by the Portal Server,
go to the HTTP Configuration page of the Portlet Web Service editor
(shown under Portlet Settings above) and set the minimum and maximum
caching times to 0. Clear the checkbox marked “Suppress errors where
possible (use cached content instead).”
Note: After the code has
been developed and debugged, make sure to turn caching on and test
the performance of your portlet. For details on troubleshooting portlets,
see Portlet Debugging. If you using the Oracle WebCenter Interaction
Logging Utilities to debug caching, turn on all types of tracing for
the OpenKernel.OpenHttp.Cache component.