Create the entity type on AIX
To map an entity type between WebSphere Portal and your LDAP user registry...
- Create the entity type within your LDAP user registry
- Add the relative distinguished name (RDN) to the entity type
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.
The wp-create-ldap-entitytype task creates a new LDAP entity type.
To update the LDAP entity type, first run wp-delete-ldap-entitytype and then run wp-create-ldap-entitytype to recreate.
- To list the names and types of configured repositories...
cd profile_root/ConfigEngine
./ConfigEngine.sh wp-query-repository -DWasPassword=password- 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-create-ldap-entitytype -DWasPassword=password
from the profile_root/ConfigEngine directory, to create an LDAP entity type.
- Propagate the security changes:
Option Description Standalone
- cd profile_root/bin
./stopServer.sh server1 -username admin_userid -password admin_password- cd profile_root/bin
./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password- cd profile_root/bin
./startServer.sh server1- cd profile_root/bin
./startServer.sh WebSphere_Portal
Cluster
- cd dmgr_profile/bin
./stopManager.sh-username admin_userid -password admin_password- cd profile_root/bin
./stopNode.sh -username admin_userid -password admin_password- cd profile_root/bin
./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password- cd dmgr_profile/bin
./startManager.sh- cd profile_root/bin
./startNode.sh- cd profile_root/bin
./startServer.sh WebSphere_Portal
- Edit...
profile_root/ConfigEngine/properties/wkplc.properties
- Enter a value for the following parameters under the VMM LDAP entity type configuration heading:
- et.ldap.id
- et.entityTypeName
- et.objectClass
- et.searchFilter
- et.objectClassesForCreate
- et.searchBases
- et.rdnName
- Save changes to wkplc.properties.
- Run...
./ConfigEngine.sh wp-add-ldap-entitytype-rdn -DWasPassword=password
from the profile_root/ConfigEngine directory, to add an LDAP entity type with a relative distinguished name.
- Propagate the security changes:
Option Description Standalone
- cd profile_root/bin
./stopServer.sh server1 -username admin_userid -password admin_password- cd profile_root/bin
./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password- cd profile_root/bin
./startServer.sh server1- cd profile_root/bin
./startServer.sh WebSphere_Portal
Cluster
- cd dmgr_profile/bin
./stopManager.sh-username admin_userid -password admin_password- cd profile_root/bin
./stopNode.sh -username admin_userid -password admin_password- cd profile_root/bin
./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password- cd dmgr_profile/bin
./startManager.sh- cd profile_root/bin
./startNode.sh- cd profile_root/bin
./startServer.sh WebSphere_Portal
If you performed these steps after creating the clustered environment, run enable-jcr-security on the secondary node.
Parent topic:
Updating the user registry on AIX
Related tasks
Enable LDAP security after cluster creation