Virtual Member Manager integration
IBM WebSphere Application Server includes Virtual Member Manager (VMM), which IBM WebSphere Portal uses to access user and group information. VMM enables communication between portal and any repository, including federated repositories or custom user registry.
VMM is an abstract component within the WAS infrastructure. The Portal User Management Architecture (PUMA) SPI retrieves 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.
Federated repositories are an implementation of the UserRegistry interface. To communicate with the federated repositories, both WAS and Portal dispatch all operations to VMM. The VMM SPI, wim.Repository, enables communication with repositories. WAS uses wim.Repository to connect to federated repositories. WebSphere Portal uses wim.Repository to connect to all repositories. User registry adapters enable VMM to connect to a specific repository, whether an LDAP directory, database, files, or other repository. Registry adapters enable communication between portal and any repository.
To use a custom user registry, we create a user registry adapter using the wim.Repository interface.
Parent User registry considerations
Related :
- Set up custom user repositories
- Webcast replay of WebSphere Portal WMM to VMM comparison
- Set up a custom user repository with VMM for IBM WS and IBM WebSphere Portal
- IBM WebSphere Developer Technical Journal: Expand user registry options with a federated repository in WAS using the VMM
- Virtual member manager APIs
- Sample custom adapters for federated repositories examples
- Repository SPI