Portal - StandAlone LDAP Configuration

db2set DB2_EXTSECURITY=NO
restart db2
create ldif files
import ldif data using ITDS Configuration Tool
login to ITDS Web Administration console [superadmin/secret]
add host in manage console servers in ITDS console
logout of console and
log into Directory Server again with LDAP Server hostname, cn=root, root
add realm/users

stanalone LDAP
--------------
wp_security_ids.properties

Modify the following attributes
standalone.ldap.id=ldaptds
standalone.ldap.host=makandas.in.ibm.com
standalone.ldap.bindDN=cn=root
standalone.ldap.bindPassword=root
standalone.ldap.serverId=cn=wpsadmin,o=sample
standalone.ldap.serverPassword=wpsadmin
standalone.ldap.realm=realm_portal
standalone.ldap.primaryAdminId=cn=wpsadmin,o=sample
standalone.ldap.primaryAdminPassword=wpsadmin
standalone.ldap.primaryPortalAdminId=cn=wpsadmin,o=sample
standalone.ldap.primaryPortalAdminPassword=wpsadmin
standalone.ldap.primaryPortalAdminGroup=cn=wpsadmins,cn=realm_portal,o=sample
standalone.ldap.baseDN=o=sample
standalone.ldap.personAccountParent=cn=realm_portal, o=sample
standalone.ldap.groupParent=cn=realm_portal, o=sample

Open a command prompt, go to directory c:/IBM/WebSphere/wp_profile/ConfigEngine, and 
execute the following command to validate the properties modified in wp_security_ids.properties
configengine.bat validate-standalone-ldap -DWasPassword=wpsadmin
-DparentProperties=<Path of wp_security_ids.properties>

Execute the following command to change the portal default file-based repository to IBM TDS

configengine.bat wp-modify-ldap-security -DWasPassword=wpsadmin
-DparentProperties=<Path of wp_security_ids.properties>

once the above command executes, goto SystemOut.log file of WebSphere_Portal
you can see
The user registry is currently connected to the LDAP server ldap://makandas.in.ibm.com:389.

The Portal server should start without any errors and you should be able to log in, indicating that
the TDS has successfully integrated with WebSphere Portal.

In the Portal Administration portlet, expand Access, select Users and Groups, and click New User.

Create a user “makandas” with password as “makandas” (see figure 51). Click OK; you should get
a message that the user is added successfully.

Now, go to TDS with server as makandas.in.ibm.com, and expand Users and groups. The user
created in WebSphere Portal should be reflected; specifically, the user makandas is displayed
under the realm “realm_portal” (see figure 52). The standalone LDAP configuration always uses a
single realm that is specified in wp_security_ids.properties file.