Starting with version 6.1, IBM WebSphere
Application Server uses a component called Virtual Member Manager (VMM) to manage information about community membership. VMM provides an interface that enables communication between WebSphere
Portal and any repository, whether federated repositories, a stand-alone repository, or your own custom user registry. You can configure VMM to recognize IBM
Connections as a repository so that Portal can access community user and group information from IBM
Connections communities. For example, once this is configured, users will be able to select IBM
Connections private or public communities as groups when assigning security roles or access rights.
For more information about the architecture of VMM, see this article
from the IBM WebSphere
For more information about configuring a user repository for VMM, see this white paper
After configuring IBM
Connections to work with VMM, user can:
- Search for IBM Connections public and private communities by name (represented as groups in WebSphere)
- Resolve public and private community membership for particular users (represented as group membership in WebSphere)
- Display the WebSphere users that are members of a particular IBM Connections public or private community
The following are some known limitations:
- When using the VMM get operation to get a single identifier and querying by name, instead of using the unique externalID, nothing will be returned if more than one community name matches the query.
- The operation to display WebSphere users that are members of a particular IBM Connections community can have a perfromance impact for large groups.
- Tivoli® Directory Integrator is recommended for populating user data into Connections. When using the profile data population wizard, a user's email may not be populated into the Communities database. Consequently, a user may not appear in the proper communities until they have logged into Communities, used a feature from the Communities service, or their profile has been synchronized with Tivoli Directory Integrator.
In order to configure the VMM to recognize an IBM
Connections repository, the following must be true:
Configuring the IBM Connections repository to work with VMM
Complete these tasks to configure the IBM
Connections User Repository Adapter. When configuration is complete, you can verify that it is working by logging in to WebSphere
Portal as an administrator. Open the Users and Groups portlet from the Administration tab. Search for groups that should be present as communities in your IBM
Connections deployment. If you find the correct groups and the members of the groups are listed, the deployment is successful.
Parent topic: Community Pages