Set up a Web content fallback page
Set up a Web content fallback page to be used when the JSR 286 Web content viewer cannot dynamically determine which page to use when displaying a content item or when the user does not have sufficient privileges to view the page originally associated with the content item.
- Create the portal page to be used as the Web content fallback page.
- Specify a unique name for the page so you can reference the page later.
- Assign any access rights required for users. For example, if the fallback page is available in the public part of the portal, ensure that anonymous users have view access to the page.
- Add a JSR 286 Web content viewer to the fallback page.
- Click the Edit Page Layout icon (small pencil) for the new page.
- Click Add portlets and select Web Content Viewer (JSR 286) from the list of portlets.
- Click OK and Done.
- Update the WebSphere Portal configuration service to enable the fallback page.
- Log in to the WAS administrative console.
- Click Resources -> Resource Environment -> Resource Environment Providers.
- Click WP ConfigService.
- Under Additional Properties, click Custom Properties.
- Click New, and enter the property name wcm.fallback.page, and set the string value to the unique name or object ID of the portal page you created as the fallback page.
- Click OK, and save the changes to the master configuration.
- Restart the portal.
The Web content fallback page is now displayed when a JSR 286 Web content viewer is configured with a link broadcast setting of Dynamically select a web content page and one of the following conditions occurs:
- The Web content viewer cannot determine which page should be used to display the linked content item.
- The Web content viewer identifies the page associated with the content item, but the user does not have sufficient privileges to view that page.
Work with web content pages
|
|
| Apr 1, 2011 1:26:17 PM
|
|
|
|
});
|