Deleting the LDAP entity type on Solaris
If you made changes to your LDAP user registry and no longer require an entity type that you created, you can delete it.
In a single server environment the WebSphere_Portal and server1 servers can be either stopped or started.
In a clustered environment stop all appservers on the system including WebSphere_Portal and server1 and then start the nodeagent and deployment manager servers before starting the following task.
Perform the following steps to delete the LDAP user registry entity type:
- Edit...
profile_root/ConfigEngine/properties/wkplc.properties
- Enter the following parameters under the VMM LDAP entity type configuration heading:
- et.ldap.id
- et.entityTypeName
- et.objectClass
- et.searchFilter
- et.objectClassesForCreate
- et.searchBases
- Save changes to wkplc.properties.
- Run...
./ConfigEngine.sh wp-delete-ldap-entitytype -DWasPassword=password
from the profile_root/ConfigEngine directory, to delete an LDAP entity type.
- Propagate the security changes:
Option Description Standalone cd profile_root/bin
./stopServer.sh server1 -username admin_userid -password admin_password
./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password
./startServer.sh server1
./startServer.sh WebSphere_PortalCluster cd dmgr_profile/bin
./stopManager.sh-username admin_userid -password admin_password
cd profile_root/bin
./stopNode.sh -username admin_userid -password admin_password
./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password
cd dmgr_profile/bin
./startManager.sh
cd profile_root/bin
./startNode.sh
./startServer.sh WebSphere_Portal
If you performed these steps after creating the clustered environment, run enable-jcr-security on the secondary node.
Parent topic:
Deleting the user registry configurations on Solaris
Related tasks
Enable LDAP security after cluster creation