IBM BS029ML - WebSphere Portal Server, Самоучитель

Страница: 93 / 242

Chapter 3. WebSphere Portal installation
79
user registry
→
Tivoli Directory Server/IBM SecureWay/Domino Directory/Active
Directory/Novell eDirectory/Sun™ System Directory Server
→
Configuring (your
specific LDAP user registry name here)
→
non-realm/realm support in the InfoCenter at:
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp
Once the files have been modified, you will need to save them and stop the WebSphere
Portal server.
To validate the configuration before enabling security, you can run the following tasks for:
򐂰
UNIX/Windows:
./WPSconfig.sh (bat) validate-wmmur-ldap -DWasPassword=password
-DPortalAdminPwd=password -DLTPAPassword=password -DLDAPAdminPwd=password
򐂰 i5/OS®:
WPSconfig.sh - profileName profile_root -DWasPassword=password
-DPortalAdminPwd=password -DLTPAPassword=password -DLDAPAdminPwd=password
where profile_root is the name given to the WebSphere Application server profile in use.
To configure WebSphere Portal security, you can run one of the following two tasks for
UNIX/Windows:
򐂰 Realm Support:
./WPSconfig.sh(bat) enable-security-wmmur-ldap
򐂰 i5/OS:
WPSconfig.sh -profileName profile_root -DPortalAdminPwd=password
-DLTPAPassword=password -DLDAPAdminPwd=password
򐂰 Non-Realm Support:
./WPSconfig.sh(bat) enable-security-ldap
3.3.4 Is it working
Below are the steps listed to verify that portal security enablement using an LDAP user
registry is successful. For clustered environments, the verification steps should in it ally be
performed on the primary node. If you encounter problems during any of the steps in the
recommended validation process below, refer to 3.4, “Problem determination” on page 80.
Verification
1. After the enabling security task completes, you should receive a BUILD SUCCESSFUL
message indicating that the transfer process has now completed. Review the
ConfigTrace.log file located in WP_root/log for any errors.
Note: If this is a clustered environment, you will need to make sure the deployment
manager and all the node agents are active.
Important: Before enabling or disabling security in a clustered environment, using the
appropriate tasks mentioned, you must stop all cluster members.