Dynamic model: adding new properties to virtual member manager built-in entities at deployment time

Express (Distributed operating systems), v8.0 > Secure applications and their environment > Authenticate users > Select a registry or repository > Manage realms in a federated repository > Virtual member manager > Develop with virtual member manager > Extend virtual member manager functionality in the application > Dynamic model schema loading process

Dynamic model: adding new properties to virtual member manager built-in entities at deployment time

Virtual member manager is configured to use the dynamic model. We can create new property types and add them to existing virtual member manager built-in entity types at deployment.

About this task
You need to add new property types to virtual member manager built-in entity types at deployment.

Procedure
Stop the virtual member manager service.

Open wimxmlextension.xml under the VMM_HOME\model directory. If this file does not exist, create a new one with the same name.
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 wimxmlextension.xml and add the definitions of the new property types and the entity types they apply to. Ensure that the XML is well-formed and conforms to the schema defined in wimschema.xsd.
For example, the following sample defines a new property type called “postOfficeBox” and adds this property type to the virtual member manager built-in entity type “PersonAccount”:
<?xml version="1.0" encoding="UTF-8"?>
<sdo:datagraph xmlns:sdo="commonj.sdo"
    xmlns:wim="//www.ibm.com/websphere/wim">
<wim:propertySchema nsURI="//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  ://www.yourco.com/wim/yourext"
     dataType="STRING" multiValued="true" propertyName="postOfficeBox">
<wim:applicableEntityTypeNames>PersonAccount
</wim:applicableEntityTypeNames>
</wim:propertySchema>
</wim:schema>
</sdo:datagraph> 
For more information about using the propertySchema and extensionPropertySchema data objects, see the section, Extend property schema in the topic, Program prerequisites. Also read about Configure a property extension repository in a federated repository in the WebSphere Application Server information center.
Manually add the new property types to each repository adapter.

LDAP adapter

Add the mapping of the new property types to LDAP attributes to the wimconfig.xml configuration file.

DB adapter

Add the definition of the new property types to the property XML file of DB Adapter (wimDBProperties.xml) and run DB property loader.

Restart the virtual member manager service.
Parent topic: Dynamic model schema loading process

+
Search Tips | Advanced Search