Advanced options
The Advanced Options settings specify link broadcast behavior between Web Content Viewers and whether context processor plug-ins are applied.
Links
Use the Links section to enter the details of how to receive and broadcast links with other portlets. This determines whether the Web Content Viewer is aware of the state or context of other portlets.
Broadcast link options:
- Dynamically select a web content page
- Use the information about the web content item from the page properties to dynamically determine to which page the context is broadcast. When using this option, a lookup is done to determine the best matching Web content page to render the item selected. The best matching web content page is the page that is mapped to the closest parent site area of the selected item in the WCM system. If more than one web content page is found that maps equally well to the same parent site area, the first page found is used with the exception the current web content page is preferred. If no web content page is found that is mapped to any of the parent site areas of the selected item, the item is rendered through the WCM servlet.
- This portal page
- Broadcast the context of the current Web Content Viewer to other Web Content Viewers on the same portal page.
- The following portal page
- Broadcast the context of the current Web Content Viewer to Web Content Viewers on a different portal page. Then enter the unique identifier or unique name to select the target portal page.
- None
- Do not broadcast the context of the current Web Content Viewer to other Web Content Viewers.
Receive link options:
- Other portlets and this portlet
- Receive the context from any Web Content Viewer broadcasting its context.
- This portlet
- Use the context of the content item, component, or element displayed in the Web Content Viewer.
- None
- Do not receive the context of any other Web Content Viewers.
Plug-ins
Use the Plug-ins section to specify which context processor plug-ins are run during rendering.
The Web Content Viewer provides a plug-point for context processor plug-ins used to control which web content item is rendered by the Web Content Viewer Portlet. Context processor plug-ins implement the com.ibm.workplace.wcm.api.ContextProcessor interface described in the Javadoc documentation for the WCM APIs and must provide a plugin.xml file that defines the extension of the com.ibm.workplace.wcm.api.ContextProcessor extension point. The following example shows how such an extension entry could be defined in a plugin.xml file:
<?xml version="1.0" encoding="UTF-8"?> <?eclipse version="3.0"?> <plugin id="your.plugin.id" name="MyContextProcessor" version="1.0.0" provider-name="Example"> <extension point="com.ibm.workplace.wcm.api.ContextProcessor" id="MyContextProcessorPlugin"> <processor class="mycom.example.MyContextProcessorPlugin"/> </extension> </plugin>For more information about plugin.xml files or the extension framework, refer to the Eclipse Extension Point Framework documentation.
The JAR file that implements the extension plug-in must be located in a directory that is part of the classpath of the Web Content Viewer portlet application. The preferred way to do this is to create a new shared library containing the custom resource bundle files using the WAS administrative console. Creating a new shared library containing the resource bundle allows a clean separation of the custom resource bundle code from the base WebSphere Portal code. After creating a shared library, add it to the classpath of WebSphere Portal application server classloader. For details about creating shared libraries and adding shared libraries to the classloader's classpath, refer to the Shared library collection topic in the WAS information center.
To select the context processor plug-ins that should be run during rendering of content items through the Web Content Viewer, click on the name of the context processor plug-in in the box that lists all found plug-ins. To clear a plug-in, hold down the control key and click on the name of the plug-in. If more than one plug-in is selected, the processing order of the plug-ins is not defined.
Scope tag cloud results
With the Scope tag cloud results settings, we can limit the results shown by instances of the Tag Cloud portlet on the same page as the Web Content Viewer to only display those tags associated with the following scopes:
- Parent of selected content item
- The tag cloud displays tags that have been applied to content items with the same parent, such as a site area, as the content item being displayed.
- Authoring template used for selected content item
- The tag cloud displays tags that have been applied to content items based on the same authoring template as the content item being displayed.
- Categories used to profile selected content item
- The tag cloud displays tags that have been applied to content items that are profiled with the same categories as the content item being displayed. In this way, we can manage scopes from within your web content system by defining taxonomies for the content items.
Locked settings
We can lock settings in the Configure mode of the viewer. When a setting is locked, a lock icon is displayed in the Edit Shared Settings mode of the viewer, and no Edit link is available.