Create the entity type on i5/OS

To map an entity type between WebSphere Portal and your LDAP user registry...

1. Create the entity type within your LDAP user registry
2. 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.

1. Optional: Run...
   ConfigEngine.sh wp-query-repository -DWasPassword=password task, from the profile_root/ConfigEngine directory, to list the names and types of configured repositories.
   • 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 task, from the profile_root/ConfigEngine directory, to create an LDAP entity type.
     • Propagate the security changes:

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

     • 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 task, 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 ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password ./startServer.sh server1 ./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 ./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:

Updating the user registry on i5/OS

Related tasks

Enable LDAP security after cluster creation

---