AIX stand-alone: Add attributes
Overview
The VMM is configured with a default attribute schema that might not be compatible with LDAP server. If this is the case, extend the VMM attribute schema by adding new attributes that you can map between WebSphere Portal and user registry.
Prerequisites
Query the defined attributesAdd new attributes to user registry:
- Install WIMSYSTEM.ear...
Stand-alone environment
cd WP_PROFILE/ConfigEngine
./ConfigEngine.sh wp-la-install-ear -DWasPassword=fooClustered environment, on the primary node.
cd WP_PROFILE/ConfigEngine
./ConfigEngine.sh wp-la-install-ear -DWasPassword=dmgr_password -DServerName=dmgr_server_name -DNodeName=node_nameYou can find the dmgr_server_name under
System administrator -> Deployment Manager -> Configuration tab -> General Properties -> Name
You can find the node_name in under
System administrator -> Deployment Manager -> Runtime tab -> General Properties -> Node Name.
- Stop and restart the appropriate servers to propagate the changes.
- Edit WP_PROFILE/ConfigEngine/properties/wkplc.properties
- Enter a value under the VMM Property Extension Properties heading:
la.providerURL
la.propertyName
la.entityTypes
la.dataType
la.multiValued
- Save changes to wkplc.properties.
./ConfigEngine.sh wp-add-property -DWasPassword=footo add the attribute to the user registry.This task performs an EJB call to WAS, which must authenticate against WAS. Depending on the configuration in the sas.client.props file, you may receive a popup window or a command line prompt asking for user identity and password. Enter the WAS user ID and password.
If you have multiple properties to add, repeat all steps, except for the wp-la-install-ear task, until all new attributes are added.
- Stop and restart the appropriate servers to propagate the changes.
Parent
Adapt the attribute configuration
Previous
Query the defined attributes
Next topic
Map attributes
Related tasks
Start and stop servers, dmgrs, and node agents