IBM virtual member manager provides support for multiple
repository types.
To
use virtual member manager, Content Platform Engine requires WebSphere® Application
Server version 7.0 or above.
When
you run the Configuration Manager’s Configure LDAP task:
- Set the value of WebSphere Application
Server LDAP
repository type to Federated repositories.
(Virtual member manager equates to Federated repositories.)
- Set the value of the Login properties field
to uid for every WebSphere Federated Repository.
(Do not use other properties such as cn or email.)
- Realm information
- Although virtual member manager supports multiple realms, WebSphere Application
Server supports only a single
realm. This realm is defined at the cell level and is shared by all
applications. So virtual member manager always has only one realm
in WebSphere server, which maps to one Content Platform Engine realm.
- For the VMM provider, the Content Platform Engine realm name is dc=vmmrealm.
- For the Connections provider, the Content Platform Engine realm name is dc=collaborationrealm.
These realm names are hardcoded and cannot be changed.
- User mapping
- The User type in Content Platform Engine maps
to the PersonAccount type in virtual member manager. One Content Platform Engine User object maps to
one virtual member manager PersonAccount object.
This Content Platform Engine User
property... |
... maps to this virtual member manager PersonAccount Property |
ID |
UniqueId |
ShortName |
uid |
DisplayName |
cn |
DistinguishedName |
UniqueName |
Name |
UniqueName |
EmailAddress |
mail |
- Group mapping
- Content Platform Engine Group
type maps to the virtual member manager Group type. One Content Platform Engine Group object maps to
one virtual member manager Group object.
This Content Platform Engine Group
property... |
... maps to this virtual member manager Group Property |
ID |
UniqueId |
ShortName |
cn |
DisplayName |
cn |
DistinguishedName |
UniqueName |
Name |
UniqueName |
The mapping between Content Platform Engine and virtual member
manager is fixed, but you can use WebSphere tools to configure the
mapping between virtual member manager and the directory service.
For example, if you used IBM
Tivoli® Directory Server as
your virtual member manager repository, you could add the following
element to the WebSphere Application
Server wimconfig.xml file
under <config:attributeConfiguration>. This code
maps the Tivoli cn attribute to the virtual member
manager uid property.
<config:attributes name="cn" propertyName="uid">
<config:entityTypes>PersonAccount</config:entityTypes>
</config:attributes>