Configure the virtual portal Manager portlet
We can modify the maximum number of search results per page displayed by this portlet. In addition, we can specify xmlaccess.sh script to be used when creating a new virtual portal. Depending on the access rights, we can configure or edit some of the standard features of this portlet.
- If we select Configure, changes affect all occurrences of the portlet on all pages for all users.
- If we select Edit shared settings, changes affect a particular instance of a portlet on a page and apply to all users who view that instance of the portlet on that page, or on pages derived from that page.
- To make changes to the individual portlet, click Personalize.
Changes made in Edit shared settings override changes made in Configure. To make changes to the portlet settings, perform the following steps:
- Hover the mouse over the portlet title bar and view the downward arrow.
- Click the downward arrow to open the portlet context menu with portlet mode selection options.
- Select the appropriate option from the menu, depending on the available options and the task to perform:
- To change how the portlet will appear to all users, click Configure.
- To make changes to a particular instance of the portlet on a page and on its derived pages for all users, click Edit Shared Settings.
- To make individual changes to the portlet, click Personalize.
- Modify the data in the data entry fields as required:
- Never show more than this number of items:
- Use this field to enter the maximum number of items the search will return. The default and maximum is 500.
- Number of items per page:
- Use this field to enter the number of rows on the page in the field. The default is 10.
- XML script to create virtual portal content tree:
- Use this field to enter the name of the custom XML script in the field. This sets the XML script to be used when creating a new virtual portal. We can specify this as a file inside a WebSphere Application Server asset, for example, similar to the following syntax example:
WebSphere:assetname=VirtualPortal.zip:MyVirtualPortalScript.xml
where VirtualPortal.zip is the name of the asset, and MyVirtualPortalScript.xml is the name of a file inside the asset. For more details about assets and how to create them refer to the WAS Information Center topic about Assets.
- Click OK to continue or Cancel to quit. Manage Virtual Portals returns to the main panel. We can also return by selecting Back from the portlet context menu.
What to do next
To see the updates, log out of the portal, and then log back in.