Update the base entry on Linux

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.

Update the base entry

  1. Edit...


  2. Enter a value for the following parameters under the VMM repository base entry configuration heading to create additional base entries within the LDAP user registry to use when creating realms:

  3. Save changes to wkplc.properties.

  4. Update the base entry...

      cd profile_root/ConfigEngine
      ./ConfigEngine.sh wp-update-base-entry -DWasPassword=password

  5. 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
    cd profile_root/bin
    ./startServer.sh WebSphere_Portal

If you performed these steps after creating the clustered environment, run the enable-jcr-security task on the secondary node; see Enabling LDAP security after cluster creation.

Parent topic:

Updating the user registry on Linux

Related tasks

Enable LDAP security after cluster creation