Use custom URIs to identify, access, and display IBM® Connections in a portlet.

When you configure IBM® Connections portlets to use single signon, you may need to change the Portal realm name to match the one used in IBM Connections.

In 3.0.1.1, you can integrate Connections Communities into your Portal site to enhance your portal's social collaboration capabilities.

Load the IBM® Connections portlets CSS bundle to properly render the user interfaces for the IBM Connections portlets.

Configure the IBM® Connections portlets to use the common directory services to enable directory lookup from IBM Connections in the IBM WebSphere® Portal environment. This enables typeahead for finding names.

You must add IBM® Connections server URLs to the WebSphere® Resource Environment provider before you can add an IBM Connections repository to the Virtual Member Manager.

Search Collections uses a seedlist framework to crawl and index all of the IBM® Connections data locally on a WebSphere® Portal server.

After installing and deploying the IBM® Connections portlets, configure and wire the Tags portlet so it works in concert with other portlets in an IBM WebSphere® Portal application.

Set up single signon integration between IBM® Connections and WebSphere® Portal using thirdparty security products, or configure basic authentication to enable access to the portlets.

The impersonation feature lets you access another user's system as though you are that user so that you can test user access.

You can configure the portlets so that when a user clicks a Connections link it opens Lotus® Connection in the same browser window rather than the default, which is to open in a new window.

Use URIs to identify, access, and display IBM® Connections content and profiles in a portlet.

IBM® Connections search integration in IBM Websphere Portal allows users to perform search queries and view query results for IBM Connections content within the context of their portal environment.

Use the Remote Content Server Search Service Type (RCSS) to implement live search for IBM® Connections content from an IBM WebSphere® Portal application.

Configure IBM® Connections portlets to use single signon with Computer Associates' SiteMinder and SPNEGO.

Configure IBM® Connections portlets to use single signon with IBM Tivoli® Access Manager and SPNEGO.

Enable the IBM® Connections Business Card so that your users can access Connections data such as a person's profile information.

Configure the applicationspecific AJAX proxy to manage authentication for the IBM® Connections portlets.

Configure DynaCache to store community feeds in order to reduce server requests.

h2 Before you beginh2 This task is done when the server is stopped. In a cluster, you can change the configuration files directly on the deployment manager and then synchronize the changes to all cluster nodes. h2 About this taskh2 The wimconfig.xml file governs a single ID attribute for ...

Configure the IBM® Connections portlets on a WebSphere® Portal page.

You must add IBM® Connections server URLs to the WebSphere® Resource Environment provider as part of the configuration.

IBM® Connections is social networking software that consists of these applications: Activities, Blogs, Bookmarks, Communities, Files, Forums, Home page, Profiles, and Wikis.

Understand the syntax for creating a custom URI to access a piece of content.

Deploy libraries required to integrate information from IBM® Connections profiles and communities with your WebSphere® Portal environment.