Virtual member manager is configured to use the static model. You
can create new property types for virtual member manager built-in entity types
at deployment time.
You need to add new property types to virtual member manager built-in
entity types at deployment time.
- Stop the virtual member manager service.
- Open the wimdomain.xsd file under the VMM_HOME\model directory.
Note: VMM_HOME is the directory where the virtual member manager files
are located. This location is set to either the system property wim.home or user.install.root/config/cells/local.cell/wim.
- Edit the wimdomain.xsd file and add the schema of the new property
types. The following sample adds a new property called postOfficeBox.
<xsd:element name="postOfficeBox" type="xsd:string"/>
- Add the new property types to the virtual member manager entities.
The following sample adds a new property, postOfficeBox, to entity, Person.
<xsd:complexType name="Person">
<xsd:complexContent>
<xsd:extension base="wim:Party">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" ref="wim:postOfficeBox"/>
<xsd:element maxOccurs="1" minOccurs="0" ref="wim:uid"/>
- Regenerate static model packages based on the updated XSD files
and deploy the jar files under class path.
- Manually add the new property types to each repository adapter.
- LDAP adapter
- The LDAP schema of the new properties needs to already exist on the LDAP
server. If the virtual member manager property name is different
than LDAP attribute name, you need to add the mapping to the wimconfig.xml
file. For example:
<config:attributeConfiguration>
<config:attributes name="userPassword" propertyName="password"/>
- DB adapter
- Add the definition of the new property types to the property XML file
of the DB Adapter (wimDBProperties.xml) and run the DB property loader.
- Restart the virtual member manager service.