Deploy the Connections Portlets

Overview

Follow these instructions to install, configure, and deploy the Connections portlets for IBM WebSphere Portal.

To deploy Connections portlets on anonymous pages that do not require authentication, see:

Use IBM WebSphere Portlet Factory portlets in an anonymous IBM WebSphere Portal page

Follow the steps for Enabling session IDs for anonymous users

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 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 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.

See

• Update from a previous release
  
• Import a certificate to support SSL
  
• Update the portal theme
  
• Configure authentication for the portlets
  
• Installation Scenarios
  
• Configure common directory services for the security configuration
  
• Configure the Ajax proxy to allow FileNet requests
  
• Configure the portlets on a page
  
• Test the Ajax proxy configuration
  
• Set public render parameter-sharing for the Connections portlets
  
• Remove the Connections portlets
  

Parent topic:
IBM Connections Portlets for WebSphere Portal