Remove attributes

The Virtual Member Manager has a limitation. There is no task to update an attribute.

Remove an attribute for any of the following circumstances:

• We added an attribute to a property extension database that was spelled incorrectly
• You adapted an attribute to match the LDAP server that was spelled incorrectly
• Your migration added the attribute

Use caution when you do these steps. Do not remove attributes populated with user values because it can cause inconsistencies. In a clustered environment, complete these steps on the deployment manager and then resynch the nodes.

1. Before configuring security, use backupConfig to create backup of the portal configuration.

2. To remove an attribute stored in a property extension database:

   1. Open the tool that we use to edit the database.

   2. Verify the attribute name is available in the LAPROP table.

   3. Delete the required attributes from the LAPROP table.

   4. Edit dmgr_profile_root/config/cells/cellname/wim/model/wimxmlextension.xml

   5. Locate and delete the propertySchema definition for the attributes deleted from the LAPROP table. For example:

          <wim:propertySchema nsURI="http://www.ibm.com/websphere/wim" dataType="String"
              multiValued="true" propertyName="attribute_name">
            <wim:applicableEntityTypeNames>PersonAccount</wim:applicableEntityTypeNames>
          </wim:propertySchema>

   6. Save the changes to the wimxmlextension.xml file.

   7. Open wimconfig.xml in the dmgr_profile_root/config/cells/cellname/wim/config directory.

   8. Locate and delete the attributes or propertiesNotSupported definitions for the attributes deleted from the LAPROP table. For example:

      <config:attributes name="attribute_name" propertyName="attribute_name">
      <config:entityTypes> PersonAccount </config:entityTypes>
      <config:entityTypes> Group </config:entityTypes>
      </config:attributes>

      or
      <config:propertiesNotSupported name="attribute_name">

   9. Save the changes to wimconfig.xml.

   10. Stop and restart all the deployment manager, node agents, and WebSphere_Portal server to propagate the changes.

3. To remove an attribute that is not stored in a property extension database:

   1. Open the wimxmlextension.xml file.

   2. Locate and delete the propertySchema definition for the attributes you previously added. For example:

      <wim:propertySchema nsURI="http://www.ibm.com/websphere/wim" dataType="String"
              multiValued="true" propertyName="attribute_name">
         <wim:applicableEntityTypeNames>PersonAccount</wim:applicableEntityTypeNames>
          </wim:propertySchema>

   3. Save the changes to the wimxmlextension.xml file.

   4. Open wimconfig.xml.

   5. Locate and delete the stanza that corresponds to the custom attribute you deleted from the wimextension.xml file. For example:

      <config:attributes name="attribute_name" propertyName="property_name">
                  <config:entityTypes>PersonAccount</config:entityTypes>
       </config:attributes>

   6. Save the changes to wimconfig.xml.

   7. Stop and restart the WebSphere_Portal server.

Parent Add more attributes to VMM

Previous topic: Mapping attributes

Related tasks: