IBM WebSphere Portal Widget Portlet provides customizable, personalized, and managed access to widgets that are compliant with the iWidget Specification, thus extending the existing capabilities of WebSphere Portal to provide flexible integration with web components, independent of their technology. With the IBM WebSphere Portal Widget Portlet, users can leverage widgets on their portal pages side by side with portlets, Gadgets or other web components, enabling the creation of portal-based mashups tailored to the situational requirements of an enterprise. Read more about IBM WebSphere Portal Widget Portlet.
The new, enhanced version of IBM WebSphere Portal Widget Portlet for WebSphere Portal Version 6.1 incorporates support for Infosphere MashupHub V1.1, a more robust and customizable security model using AJAX proxy, and a simpler, more intuitive procedure for editing widget preferences.
The enhanced version of IBM WebSphere Portal Widget Portlet for WebSphere Portal Version 6.1 incorporates the following new features:
- Support for InfoSphere MashupHub V1.1
- AJAX proxy based security implementation
- Simpler and more intuitive procedure for editing widget preferences
Support for InfoSphere MashupHub V1.1
The portlet is now supported for InfoSphere MashupHub V1.1.
AJAX proxy based security implementation
IBM WebSphere Portal version 6.1 introduced an HTTP proxy for AJAX applications or the
AJAX proxy. Using this AJAX proxy, you can configure either the
global proxy settings for all the AJAX-based applications running
on your Portal or define application-specific proxy configuration
for a single application. The AJAX proxy enables you to restrict
access to trusted domains in a very flexible way by editing an xml
configuration file, the
proxy-config.xml file. For global proxy
configuration, you must edit the
proxy-config.xml file in the
WEB-INF directory of the
wp.config.proxy.war WAR file. For
defining application-level proxy configuration, you must have the
proxy-config.xml file in the
WEB-INF directory of your portlet
WAR file and the portlet code must have the provision to
implement the proxy settings you define in the
widgetportlet.war file in the
WP6.1 folder of the installation package, which must be
installed if you are using WebSphere Portal version 6.1, now
proxy-config.xml file in
WEB-INF directory. You can edit
this xml file to fine-tune the level of security that your setup
requires. IBM WebSphere Portal Widget portlet is an AJAX-based
application that loads content from external servers; the AJAX
proxy implementation enables you to regulate the level of
interaction with the external, even though trusted servers.
To understand and define the AJAX proxy configuration, see The proxy-config.xml topic in the WebSphere Portal version 6.1 Information Center.
As an example, consider the following snippet from the
<proxy:policy url="http://127.0.0.1:9082/*" acf="none">
The policy element defines an access policy for a specific URL pattern. Use the url attribute of the policy element to specify the URL pattern, for example, http://127.0.0.1:9082/*, as in the above example. Use the cookies sub-element of the policy element to specify the cookie type. The above code snippet defines LTPA as the cookie type.
Note: You may no longer see the
LTPA option as the
authentication type for this version of the portlet that you
deploy for Portal version 6.1. Instead, you need to specify it in
Similarly, you can define other configuration parameters for your
setup. Read more details about the
proxy-config.xml file from The proxy-config.xml topic in the
WebSphere Portal version 6.1 Information Center.
Restriction: For form-based and basic authentication types, only GET and POST methods are allowed in this implementation. Thus, you can specify only GET and POST as the values of the actions sub-element of the proxy element.
Simpler and more intuitive procedure for editing widget preferences
Earlier, editing the widget preferences involved the following steps:
In this version of the portlet for Websphere Portal 6.1, the widget preferences can be edited by directly going to the Personalize or Edit Shared Settings mode, as in case of most of the other portlets. Here are the updated steps:
The changes made to the widget are applied and saved and an inline message confirming the changes is displayed in the portlet. User can click the Back button to view the widget in the view mode.
Note: The updated steps for editing widget preferences are applicable only if the Allow that widget selection can be changed in "Personalize" or "Edit Shared Defaults" mode? (Note: This will disable the eventing support) setting has been disabled from the General Settings section.