Workload management

Only one Personalization engine can be installed on an appserver. Consequently, there is one Personalization engine per servlet engine. Personalization supports appserver clustering, because each Personalization instance in the cluster shares the same DB2 Content Manager. Therefore, each Personalization instance accesses the same customer data stores. To set up a clustered run-time environment, see Updating Personalization properties in the cluster.

WebSphere Application Server dynamic caching is used to cache resource instance and the results of queries used in rules. The dynamic cache shares expiration notification for the cache across clones in a cluster. Although Personalization uses the dynamic cache internally to cache the results of rules, it is also possible to use the WebSphere Application Server dynamic cache to cache the entire response from a JSP or servlet.

Note: Care must be taken when using Personalization and the dynamic cache of JSPs, servlets, or portlets. When using the dynamic cache to cache JSPs or servlets, the cache key must take into accout all the inputs into any rules on that page. Thus, if rules on the page use an employee department attribute of a user resource, the cache key must be configured to contain this employee department attribute.

Parent topic: Personalization programming reference

---

Home |

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.