- Change the wp_security_ids.properties file on the primary portal node to match the LDAP configuration
- Validate the values that you entered by executing
./ConfigEngine.sh validate-standalone-ldap
comand - Once the validation is completed successfully you can modify the security by executing
./ConfigEngine.sh wp-modify-ldap-security
command - Restar the DMGR, all NodeAgents and all cluster members
- Copy the wp_security_ids.properties file to the secondar cluster node. Copy the settings from the helper file to wkplc.properties file by executing
ConfigEngine.bat -DparentProperties=
/ConfigEngine/config/helpers/wp_security_ids.p
roperties -DsaveParentProperties=true - Update the portal security information on the secondary node by executing the following command
ConfigEngine.bat wp-change-portal-admin-user -DnewAdminId=wpsadmin -DnewAdminPwd=wpsadmin -DnewAdminGroupId=wpsadmins
- Restart the secondary portal node
Steps for enabling security in clustered environment
The enable security steps should be performed after the horizontal/vertical cluster is setup. You can also keep using File repository in clustered environment, in that case you create a new user on DM machine and push the fileRepository.xml to nodes.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment