+

Search Tips   |   Advanced Search


Create the entity type on Windows

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. List the names and types of configured repositories...

      cd profile_root/ConfigEngine
      ConfigEngine.bat wp-query-repository -DWasPassword=password

  2. Edit...

      profile_root/ConfigEngine/properties/wkplc.properties

  3. Enter the following parameters under the VMM LDAP entity type configuration heading:

  4. Save changes to wkplc.properties.

  5. To create an LDAP entity type...

      profile_root/ConfigEngine
      ConfigEngine.bat wp-create-ldap-entitytype -DWasPassword=password

  6. Propagate the security changes:

    Option Description
    Standalone

    1. cd profile_root/bin
      stopServer.bat server1 -username admin_userid -password admin_password

    2. cd profile_root/bin
      stopServer.bat WebSphere_Portal -username admin_userid -password admin_password

    3. cd profile_root/bin
      startServer.bat server1

    4. cd profile_root/bin
      startServer.bat WebSphere_Portal

    Cluster

    1. cd dmgr_profile/bin
      stopManager.bat -username admin_userid -password admin_password

    2. cd profile_root/bin
      stopNode.bat -username admin_userid -password admin_password

    3. cd profile_root/bin
      stopServer.bat WebSphere_Portal -username admin_userid -password admin_password

    4. cd dmgr_profile/bin
      startManager.bat

    5. cd profile_root/bin
      startNode.bat

    6. cd profile_root/bin
      startServer.bat WebSphere_Portal

  7. Edit...

      profile_root/ConfigEngine/properties/wkplc.properties

  8. Enter a value for the following parameters under the VMM LDAP entity type configuration heading:

  9. Save changes to wkplc.properties.

  10. Run...

      ConfigEngine.bat 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 Windows


Related tasks


Enable LDAP security after cluster creation