+

Search Tips   |   Advanced Search


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 you want 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 portal 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 portal page to render the item selected. The best matching portal page is the page mapped to the closest parent site area of the selected item in the Web Content Management system. If more than one portal page is found that maps equally well to the same parent site area, the first page found is used with the exception that the current portal page is preferred. If no portal page is found mapped to any of the parent site areas of the selected item, the item is rendered through the Web Content Management 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 portlet page

Broadcast the context of the current Web Content Viewer to Web Content Viewers on a different portal page. You must 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 that can be used to control which Web content item is rendered by the Web Content Viewer portlet. Context processor plug-ins must implement the com.ibm.workplace.wcm.api.ContextProcessor interface described in the Javadoc documentation for the Web Content Management 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="yourcom.example.MyContextProcessorPlugin"/>
 </extension>
</plugin>

For more information on 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 (JSR 286) portlet application. The preferred way to do this is to create a new shared library that contains the custom resource bundle files using the administrative console. Creating a new shared library that contains 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 appserver 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 a context processor plug-ins that should be run during rendering of Web 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 deselect 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.


Locked settings

If a lock icon is displayed for setting instead of an Edit link, the setting has been locked using the Configure mode and cannot be changed using Edit Shared Settings.


Parent topic:

Set up a local Web Content Viewer