To use Business Space widgets
in WebSphere® Portal, you
must prepare a wrapper for the Business Space widgets, which
are in the iWidget format.
Before you begin
Topic scope: This topic applies
to the following products:
- WebSphere Business
Modeler Publishing Server
- WebSphere Enterprise
Service Bus
- WebSphere Process
Server
Procedure
- Download the IBM® WebSphere Portal Widget Portlet
from the following URL: http://www.ibm.com/software/brandcatalog/portal/portal/details?catalog.label=1WP1001PI and extract the file to your
system. The WebSphere Portal
Widget Portlet provides iWidget support for WebSphere Portal so that Business Space widgets can
be used in WebSphere Portal.
Note: Make
sure that you download the most recent version so that the widgets
work properly.
- Copy the widgetportlet.war file to PortalServer_root/installableApps,
where PortalServer_root is the installation location
for the portal server component of WebSphere Portal. For a clustered environment, complete this step on each node
where you want to add widgets.
- Copy the setupWidgetintegration.xml file
to PortalServer_root/bin. For a clustered environment, complete this step on each node
where you want to add widgets.
- Open a command prompt, change directories
to PortalServer_root/bin,
and run one of the following commands, based on your platform. For a clustered environment, complete this step on each node
where you want to add widgets.
On i5/OS® platforms: ./xmlaccess
-in setupWidgetIntegration.xml -user admin_user_name -password admin_password -url
http://host_name:port_number/wps/config

On Linux®, UNIX®, and z/OS® platforms: ./xmlaccess.sh
-in setupWidgetIntegration.xml -user admin_user_name -password admin_password -url
http://host_name:port_number/wps/config
On Windows® platforms: ./xmlaccess.bat
-in setupWidgetIntegration.xml -user admin_user_name -password admin_password -url
http://host_name:port_number/wps/config
- Log on to the administrative console for WebSphere Portal and navigate to . For a clustered environment, complete
steps 5-6 on the administrative console of the deployment manager.
- For the PA_Widget application, click Security
role to user/group mapping, select the All
Authenticated check box, and click OK and Save.
- Edit the proxy-config.xml file to
so it works with the Business Space widgets. The proxy-config.xml file is located in wp_profile_root/installedApps/node_name/PA_Widget.ear/widgetportlet.war/WEB-INF/,
where wp_profile_root is the profile location for WebSphere Portal and node_name is
the name of the WebSphere Portal
node.
Make sure the file looks like the following example.
Note: If
you are configuring Business Space widgets
to work with WebSphere Portal
for the first time, replace the file with the following content.
<?xml version="1.0" encoding="UTF-8"?>
<proxy-rules
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:proxy="http://www.ibm.com/xmlns/prod/websphere/portal/v6.0.1/
proxy-config">
<proxy:mapping contextpath="/myproxy/*"/>
<proxy:mapping contextpath="/myportalproxy/*"/>
<proxy:policy url="*" acf="none">
<proxy:actions>
<proxy:method>DELETE</proxy:method>
<proxy:method>GET</proxy:method>
<proxy:method>POST</proxy:method>
<proxy:method>PUT</proxy:method>
</proxy:actions>
<proxy:cookies>
<proxy:cookie>LtpaToken</proxy:cookie>
<proxy:cookie>LtpaToken2</proxy:cookie>
</proxy:cookies>
<proxy:headers>
<proxy:header>Cache-Control</proxy:header>
<proxy:header>Pragma</proxy:header>
<proxy:header>User-Agent</proxy:header>
<proxy:header>Accept*</proxy:header>
<proxy:header>Content*</proxy:header>
<proxy:header>X-Method-Override</proxy:header>
</proxy:headers>
</proxy:policy>
<proxy:meta-data>
<proxy:name>forward-http-errors</proxy:name>
<proxy:value>true</proxy:value>
</proxy:meta-data>
</proxy-rules>
- Restart the PA_Widget application.