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 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 Web Content Manager 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
that 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 Web Content Manager 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. 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 Manager 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 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 (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 WebSphere Application Server 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, you need to 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 WebSphere Application Server information center.
To
select the 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 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, you 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 that are associated
with the following scopes:
- Parent of selected content item
- The tag cloud displays tags that have been applied to content
items that have 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 that are 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, you can manage scopes from within your
web content system by defining taxonomies for your content items.
Locked settings
You
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.