Virtual member manager identifiers

Every entity in virtual member manager needs a unique identifier.

When an application calls virtual member manager with the unique identifier for an entity, the entity’s properties can be retrieved. The unique identifier can also be used by an application to associate application-specific data for the entity. Such application-specific data are stored in the application’s own data store. For instance, WebSphere Portal may have information about portlets associated with a person and such information is stored in the Portal database. Portal can use the virtual member manager unique identifier as a key to the person-specific portlet information. Similarly virtual member manager uses the unique identifier as a key to data in the property extension repository that virtual member manager keeps for the same entity that exists in a main repository.

When an identifier is used to retrieve a profile, all that is required of the identifier is that it be unique. However, when an identifier is used to associate data in different systems (between virtual member manager and an application which calls virtual member manager or between virtual member manager and a repository that virtual member manager uses), it is highly desirable that not only is the identifier unique, it is also static (once created won't change) and never reused.

Terms of use | Feedback
(C) Copyright IBM Corporation 2005. All Rights Reserved.
IBM virtual member manager 6.1