If you plan to deploy IBM Connections portlets on anonymous pages that do not require authentication, find out more in the article
" target="external">Using IBM WebSphere Portlet Factory portlets in an anonymous IBM WebSphere Portal page
in the IBM Web Experiences wiki. Follow the steps for setting up anonymous access in the
article from the IBM WebSphere Portal wiki.
In order to use common directory services, Portal must be configured to use a federated LDAP. Use of a stand-alone LDAP is not supported.
The VMM Adapter uses the externalId field to map the user object ID field from the LDAP server to identify users and determine Community Membership for logged in users to control access for Community pages based on community membership in IBM Connections. WebSphere Portal must be configured to use the same LDAP that was used to import users into the People database for the Connections Profiles service so that the externalId between the two servers matches. Other WebSphere Portal components such as Social Rendering and the integrated person card require the externalId between the two servers to match as well.
Updating from a previous release
If you are installing from a previous release where you installed the Portal application archive (PAA) with the Portal Solutions Installer, update the installation to get the newest features. This installation method was available starting with the IBM
Connections Portlets for WebSphere
Portal version 220.127.116.11 Refresh. If you installed a previous version of the IBM
Connections portlets using the manual installation, you cannot update the installation. You must uninstall the portlets and then reinstall using the complete installation steps.
Importing a certificate to support SSL
Import a certificate so that IBM Connections and WebSphere Portal can communicate over Secure Socket Layer (SSL).
Updating the portlet theme
Update the theme profile for the Connections portlets to functions properly.
Configuring authentication for the portlets
Set up single sign-on integration between IBM
Connections and WebSphere
Portal using third-party security products, or configure basic authentication to enable access to the portlets.
Choose between the complete deployment option which installs all of the infrastructure and portlet modules, or choose to just deploy the infrastructure to support the Social Rendering portlets.
Configuring common directory services for your security configuration
Configure the common directory services to work with your security configuration.
Configuring the Ajax proxy to allow FileNet requests
Configure the Ajax proxy so that direct requests that the CCM portlet makes to the FileNet server are allowed to pass through the proxy server.
Configuring a global proxy for POC
Configure a global proxy for POC to handle URL redirections.
Configuring the portlets on a page
By default, the installation process creates sample pages for the different portlets. You can customize those pages to fit your needs or remove them and create new pages. This article describes how to configure the IBM
Connections portlets on a WebSphere
Testing the Ajax proxy configuration
Test the configuration of the application-specific Ajax proxy to manage authentication for the IBM
Set public render parameter-sharing for the IBM Connections portlets
Public render parameters are set by default during installation but you can manually set these parameters when you deploy new portal pages. These parameters communicate what content to render when navigating between portlets and from IBM
Connections content accessed from the search center portlet.
Removing the IBM Connections portlets
OPTIONAL: If you no longer want the Portlets that are installed, you can remove them from IBM WebSphere