IBM 6.1.X manual Use of Dynamic Content Features, content.topology.dynamic=false

M I N I M U M A T T R I B U T E S E T

Generally, the minimum set of attributes does not need to be modified from the default provided by WebSphere Portal, as that attribute set is satisfactory for the user management applications provided with WebSphere Portal. However, if your site contains a custom application for managing users and groups, and it uses attributes other than those in the minimum set, then you should consider expanding the minimum attribute set.

Use of Dynamic Content Features

WebSphere Portal contains dynamic content support infrastructure which supports two dynamic content features: dynamic user interfaces and attribute based administration. If neither of these features is being used, the dynamic content support can be disabled. Note that attribute based administration is only one use of the Personalization capabilities in WebSphere Portal; other uses of Personalization, such as placing content spots within a portlet, do not require the dynamic content features.

Disabling the dynamic content features will provide a modest performance benefit. It will provide a reduction in the memory needed for each user, and also reduce the processing time for generating pages in WebSphere Portal. For example, in one measurement with our Base Portal scenario, capacity improved about 5% when disabling the dynamic content support.

Disabling dynamic content support is done by adding a custom property to the ConfigService.properties resource provider. The property is:

content.topology.dynamic=false

See “Overview of configuration services” in the WebSphere Portal information center for more information on how to update configuration properties.

5 5

W E BS P HE R E P O R T AL V 6 . 1 T U N I N G G U I D E