Configuring Portal to work with IBM Connections

For WebSphere® Portal to work with IBM® Connections you must configure the portal Ajax proxy, and set up single sign-on.

  • Set up Ajax proxy
    The support for community pages uses the Ajax proxy to access the remote server. The Ajax proxy is updated for the base Connections URLS during the Connections Portlets installation. If FileNet is used, you must still configure the Ajax proxy manually to update for FileNet. 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.
  • Set up single sign-on
    Site visitors want to sign in one time. Set up single sign-on to ensure that visitors receive only one authentication challenge. The instructions for deploying the IBM Connections portlets include multiple options for configuring authentication for the portlets. If you did not complete the procedures in the IBM Connections documentation, you must configure single sign-on using the applications server. For best results, follow the procedures that are provided in the IBM Connections documentation.
  • Configuring common directory service
    IBM Connections use the common Directory Services to enable directory lookup from Connections in the WebSphere Portal environment
  • Configuring authentication for the portlets
    Configure authentication to enable access to the portlets.
  • Configuring the IBM Connections integration
    Run the configure-wp-connections-integration task to configure the integration between Connections and IBM WebSphere Portal.
Parent topic: IBM Connections