Add attributes on Windows in a clustered environment

To ensure proper communication between WebSphere Portal and your LDAP server, you may need to add new attributes to your configuration so that you can map the attributes between WebSphere Portal and the user registry.

Add new attributes to the user registry

1. Install the .ear file for adding properties...

   Option	Description
   Standalone	Run... ConfigEngine.bat wp-la-install-ear -DWasPassword=password ...from the profile_root/ConfigEngine directory.
   Cluster	Run... ConfigEngine.bat wp-la-install-ear -DWasPassword=dmgr_password -DServerName=dmgr_server_name -DNodeName=node_name ...only on the primary node, from the profile_root/ConfigEngine directory. To look up the dmgr name, from the admin console... System administrator | Deployment Manager | Configuration tab | General Properties | Name To look up the node name... System administrator | Deployment Manager | Runtime tab | General Properties | Node Name

2. Propagate the security changes:

   Option	Description
   Standalone	cd profile_root/bin stopServer.bat server1 -username admin_userid -password admin_password cd profile_root/bin stopServer.bat WebSphere_Portal -username admin_userid -password admin_password cd profile_root/bin startServer.bat server1 cd profile_root/bin startServer.bat WebSphere_Portal
   Cluster	cd dmgr_profile/bin stopManager.bat-username admin_userid -password admin_password cd profile_root/bin stopNode.bat-username admin_userid -password admin_password cd profile_root/bin stopServer.bat WebSphere_Portal -username admin_userid -password admin_password cd dmgr_profile/bin startManager.bat cd profile_root/bin startNode.bat cd profile_root/bin startServer.bat WebSphere_Portal

3. Edit
   profile_root/ConfigEngine/properties/wkplc.properties

   .

4. Enter a value for the following parameters under the VMM Property Extension Properties heading:
   • la.providerURL
   • la.propertyName
   • la.entityTypes
   • la.dataType
   • la.multiValued

5. Save changes to wkplc.properties.

6. Run...
   ConfigEngine.bat wp-add-property -DWasPassword=password

   ...to 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 sas.client.props, 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.

7. Propagate the security changes:

   Option	Description
   Standalone	cd profile_root/bin stopServer.bat server1 -username admin_userid -password admin_password cd profile_root/bin stopServer.bat WebSphere_Portal -username admin_userid -password admin_password cd profile_root/bin startServer.bat server1 cd profile_root/bin startServer.bat WebSphere_Portal
   Cluster	cd dmgr_profile/bin stopManager.bat-username admin_userid -password admin_password stopNode.bat-username admin_userid -password admin_password from the profile_root/bin directory cd profile_root/bin stopServer.bat WebSphere_Portal -username admin_userid -password admin_password cd dmgr_profile/bin startManager.bat startNode.bat, from the profile_root/bin directory cd profile_root/bin startServer.bat WebSphere_Portal

If you performed these steps after creating the clustered environment, run enable-jcr-security on the secondary node.

Parent topic:

Adapting the attribute configuration

Previous topic:

Query defined attributes on Windows

Next topic:

Mapping attributes on Windows in a clustered environment

Related tasks

Enable LDAP security after cluster creation

---