View some best practices for using web content viewers.
User authentication to web content viewers is managed by IBM
® Portal Express
® and IBM WebSphere
Application Server. Seehttp://www.lotus.com/ldd/portalwiki.nsf/dx/Enabling_stepup_authentication_the_Remember_me_cookie_or_both_wp7
for further information.
Security when using WSRP
When displaying web content from remote servers using WSRP and the JSR 286 web content viewer, it is recommended that you configure security and authentication between the portal server acting as the WSRP Consumer and the web content server acting as the WSRP Producer. Refer to the topic Security considerations for WSRP services
and a value of true
. Note that this should only be done if you are not planning to use authoring tools components or remote authoring action URLs with the web content viewer.
User access to Web Content Manager content and components
Users will only be able to view content and components that either their portal user's logon or the user of the WSRP Consumer has access to. If a portal user's logon or the user of the WSRP Consumer does not have sufficient rights in Web Content Manager to view a Web Content Manager content or component, errors may occur.
Content and component design
Not all content or components built in a Web Content Manager solution are suitable for inclusion within an IBM WebSphere
- Web Content Manager content or components to be displayed within a WebSphere Portal Express page should be self-contained and not rely on other Web Content Manager content or components.
- When creating presentation templates or page styles to use when displaying Web Content Manager content within a portlet, it is best practice to reference just the content you would like to display. Components, such as menus and navigators, should be displayed in separate portlets and linked to the Content Portlet as required.
Path component tags
The URLs generated by the path component will be fully qualified when viewed through a portal. To generate URLs with no prefix, use the following "Type" parameters instead of the standard parameters:
- Type="noprefixbase" instead of Type="base"
- Type="noprefixservlet" instead of Type="servlet"
- Type="Prefix". When viewed through portal the, prefix value will be printed. If no prefix exists then empty string is returned.
- The results of a POST in a form are only displayed within the portlet that sent the POST. You cannot send the result of a POST to another portlet.
- An anonymous WebSphere Portal Express Server user will also be classed as an anonymous Web Content Manager user so that the logon override does not work for anonymous users.
- If a Web Content Manager proxy server is being used with web content viewers, all URLs rewritten by the proxy will not be fully-qualified, but server-relative instead. To address this issue, redirect mappings can be created in the HTTP Server configuration that will pass the URLs to the proxy server.
- Category selection trees cannot be used with the local web content viewer.
- Only advanced caching can be used with a local web content viewer.
- Tagged web content that is displayed in the JSR 286 web content viewer is only available when there is a single instance of the portlet on the page. When you click on a tag result, the Tag Center broadcasts the information on what content should display in the viewer using a public render parameter. If you have multiple instances of web content being displayed in the JSR 286 web content viewer, these instances display the content that you tagged rather than the original content of these instances.