Virtual Member Manager integration
HCL WebSphere Portal uses Virtual Member Manager, an interface that enables communication between HCL WebSphere Portal and any repository. The VMM is an abstract component within the WebSphere Application Server infrastructure. HCL WebSphere Portal uses the Portal User Management Architecture (PUMA) SPI to retrieve and set attributes on user objects. PUMA passes these requests to VMM, which then passes the requests on to a corresponding registry adapter that connects VMM to the repository.
Components:
- Federated repositories
- An out-of-box implementation of the UserRegistry interface that supports multiple repositories. To communicate with the federated repositories, both WebSphere Application Server and HCL WebSphere Portal dispatch all operations to VMM.
- VMM SPI
- VMM offers a Service Provider Interface (SPI), wim.Repository, that enables communication with repositories. WebSphere Application Server uses this SPI to connect to federated repositories. HCL WebSphere Portal uses this SPI to connect to all repositories.
- User registry adapter
- An implementation of the VMM SPI that enables VMM to connect to a specific repository, whether an LDAP directory, database, files, or other repository. Registry adapters enable communication between HCL WebSphere Portal and any repository.
To use a custom user registry or repository that HCL WebSphere Portal does not support out-of-box create a user registry adapter. Implement the wim.Repository interface:
- Repository SPI. System programming interfaces for virtual member manager adapters.
- Sample custom adapters for federated repositories examples
Parent topic: User registry considerations