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