State Manager Service

The portal State Manager Service is the access point for managing the navigational state of the portal. The navigational state represents the current view of portal resources as displayed to a user.

In the WAS console, the portal State Manager Service is listed as WP StateManagerService.

The portal State Manager Service holds the following properties:

preprocessors = (com.ibm.wps.state.preprocessors.selection.StandardPortalSelectionImpl )

This specifies a list of one or more preprocessors used. It can take multiple values.

1. To add our own custom preprocessors in the WAS console, first enter the default values in the following sequence and then append your custom preprocessors to the end of the list. This is for the following reasons:

   1. If we specify a value for this parameter, that value overwrites the default value.

   2. The default value is mandatory. Therefore we cannot replace it by a different value.

   3. The following preprocessors must be arranged in order, as for requests they are processed in that order.

2. The required syntax is (classname (, classname) * ) 1 .

The default value is as follows:

preprocessors = com.ibm.wps.state.preprocessors.urlmapping.URLMappingPreProcessor, com.ibm.wps.resolver.friendly.preprocessors.FriendlyPreProcessor, com.ibm.wps.resolver.portal.ResolvedPreprocessor, com.ibm.wps.state.preprocessors.selection.StandardPortalSelectionImpl, com.ibm.wps.state.preprocessors.selection.FragmentSelectionImpl, com.ibm.wps.state.preprocessors.selection.ResourceSelectionImpl, com.ibm.wps.state.preprocessors.eclipse.ExtensionPreProcessor, com.ibm.wps.state.preprocessors.portlet.RequestParameterMerger

Of the default values given, the following two selection preprocessors are alternative options. They process the page selected by the user. All other preprocessors are for portal internal use only and must not be changed.

Both of the following selection preprocessors are mutually exclusive. This means they cannot be used in combination with each other.

com.ibm.wps.state.preprocessors.selection.StandardPortalSelectionImpl

This value implements the standard portal selection behavior which prefers displaying pages over displaying labels. This means that if a user selects a label, the portal displays a page under that label, rather than the label itself with the message saying there is no content available. (In this case the page displayed is the last page the user selected under this label, or if that page is not available, the first available page under the label.) This value is the default.

com.ibm.wps.state.preprocessors.selection.SimpleSelectionImpl

This value implements a simple selection strategy; it always displays the element selected by the user, regardless of whether the user selects a label or a page. If the user selects a label, the portal displays that label with the message there is no content available. We can replace this value for the previously listed default value.

com.ibm.wps.state.preprocessors.selection.StandardPortalSelectionImpl.selection.fallback.enabled

What happens if a user requests a page that does not exist, for example by selecting a bookmark for a page that was deleted. Specify one of the following values:

true

Default value. With this value, the portal takes the user to the default fallback page, for example the home page.

false

With this value, the portal gives an HTTP 404 error.

Use this property together with the state.decoding.fallback property in the portal WP configuration service. Set the values for the two properties in a consistent way.

keymanager.lru.size = ( integer )

Specify the history expiration limit of portal pages visited by users. The number specified defines the minimum number of different pages selected by the user after which the portal can discard the render parameters of a page. (The decision whether the render parameters of the page are actually discarded depends on the expiration policy of the internal cache that stores the render parameters of those pages.) If the user returns to a page after visiting the specified number of other pages and if the render parameters of that page have expired, the portal displays that page in its default state.

We can specify by which circumstances the render parameters of a page are stored or discarded:

1

Each time the user selects a different page, the render parameters of the portlets on the previously selected page can be discarded.

A positive integer

Specify the required number of pages. The render parameters of a given page can be discarded after the user has visited that number of other pages.

0

Render parameters are always stored in the portal session memory and never discarded.

Do not specify a value less than zero ( 0 ). Negative values are considered to be not valid.

• URL normalization for search of portal pages by external search engines
  The following properties are used to configure the normalization of the URL of the portal. URL normalization is required to enable external search engines to crawl the content of the portal.

Parent Portal service configuration