Fixing browser URL length problems : WP7

By default WebSphere Portal includes navigational state information along with other information in browser URL in encoded form. Sometimes the length of the URL’s will exceed browser URL max chars limit. This may happen because navigating many pages and portlets on these pages and this even can apply if long render parameters are swapped to the session..

With latest fix (WP CF002) , we can resolve this issue with following configurations. These can be set in the resource environment provider "WP StateManagerService":

1 - Go to the WebSphere Application Server administrative console.
2 - Resources > Resource Environment > Resource Environment Providers
3 - Click on "WP StateManagerService" and "Custom properties"
4 - Add the properties as needed
5 - Save the changes to the master configuration
6 - Restart the portal server

The following properties are available:

The HistoryManager allows to cleanup state for pages visited some time ago.
Allowed values are "true" or "false".
Default value is "true".
Example: historymanager.enabled = true
The threshold meaning the number of pages whose portlets and shared state should be kept. Must be a positive integer.
Default value is "10"
Example: historymanager.threshold = 10
Defines a strategy how the shared state is cleaned up.
Possible values are
a). no_removal : public render parameters will not be removed, i. e. only portlet specific state will be removed.

b). wcm_id  :  Public render parameters will be removed if the expired page has an explicit shared state bucket assigned that starts with the String "ibm.wcm."

c). explicit_bucket_assignment : Public render parameters will be removed if the expired page has an explicit shared state bucket assigned  regardless
of a prefix. This is a more general strategy than "wcm_id"

Default value is "explicit_bucket_assignment"
Example: historymanager.prp.removalstrategy = explicit_bucket_assignment

No comments:

Post a Comment