Deploying the Mainsoft SharePoint Integrator Portlets to WebSphere Portal Version 5.1
The Mainsoft SharePoint Integrator portlets can be deployed on WebSphere Portal version 6.0 or later without modifications. To deploy them on WebSphere Portal version 5.1, you'll need to make a few modifications to the WAR file, specifically to the portlet.xml deployment descriptor file.
Cause:
WebSphere Portal 6.0 (and later) supports multiple levels of portlet configuration:
- Administrator preferences (Config portlet mode): Portlet configuration done in Config portlet mode applies to all occurrences of the portlet, on all pages, for all users.
- Shared preferences (Edit_defaults portlet mode): Portlet configuration done in Edit_defaults portlet mode applies to a particular occurrence of a portlet definition on a page, for all users viewing that portlet in that page.
- Personalized preferences (Edit portlet mode): Portlet configuration done in Edit portlet mode applies to a particular user that views the portlet in a particular page.
The default configuration of the Mainsoft SharePoint Integrator portlets is handled in the Edit_defaults portlet mode, as defined in the portlet.xml configuration file. This portlet mode was introduced in WebSphere Portal 6.0.
Resolution: Use the Config portlet mode
To deploy the WAR file to WebSphere Portal 5.1, move the Mainsoft Sharepoint Integrator portlets configuration parameters to the Config portlet mode:
- Unzip the MainsoftSharePointFederator.war file, and open the portlet.xml deployment descriptor file.
- Move the configuration sections to the Config porlet mode:
- Locate the following line in the required portlet::
<!-- Defaults for Edit_Defaults mode -->
The initialization parameters are listed after this line, in this format:
<init-param> <name>edit_defaults.$configuration-section.enabled</name> <value>true</value> </init-param> - Change edit_defaults to config, to move the configuration section to the Config portlet mode.
- Locate the following line in the required portlet::
- Replace the supported mode by changing the following line:
<portlet-mode>edit_defaults</portlet-mode>
to:
<portlet-mode>config</portlet-mode>
You may also decide to move some of the portlet configuration options to the portlet privileged users, to be configured in the Edit portlet mode. For example, moving the Columns, Sort, and Filter configuration parameters of the List Viewer portlet to the Edit portlet mode enables the portlet users to configure their own list view in order to see the list items that are most important to them.
To move a configuration parameter to the Edit portlet modes, repeat step 2 above, but replace config with edit.
Limitation: The Config portlet mode is global for all portlet instances
Moving the configuration parameter to the Config portlet mode results in a global configuration of all instances of that portlet, on all pages, and for all users.
Workaround: Use the Copy portlet feature
If you need to configure multiple portlets to federate different contents from different SharePoint sites and lists, you should create multiple copies of the Mainsoft SharePoint Integrator portlets. This will allow you to configure each copy of the portlet differently, at the administrator level.
To create a new copy of a SharePoint Integrator portlet, do the following:
- Launch the portal Administration portlet.
- Select Portlet management > Portlets.
- Locate the Mainsoft SharePoint Integrator portlet, and click the Copy portlet button next to it. Each copy of the Mainsoft Sharepoint Integrator portlet can be configured differently at the administrator level.
