Portal - Multiple Realms

add 1st LDAP [ITDS] and creating Realm1, making it Default
##########################################################

wkplc.properties

• federated.ldap.id=fed1
• federated.ldap.host=manju.rtp.raleigh.ibm.com
• federated.ldap.port=390
• federated.ldap.bindDN=cn=root
• federated.ldap.bindPassword=p0rtal4u
• federated.ldap.ldapServerType=IDS6
• federated.ldap.baseDN=dc=raleigh,dc=com

configengine.bat validate-federated-ldap -DWasPassword=wpsadmin

configengine.bat wp-create-ldap -DWasPassword=wpsadmin

Restart server1 and WebSphere_Portal

configengine.bat wp-query-repository -DWasPassword=wpsadmin

Check that all defined attributes are available in the configured LDAP user
registry.Run the following task :
configengine.bat wp-validate-federated-ldap-attribute-config -DWasPassword=wpsadmin

NOTE: After running the above task, check the ConfigEngine/log/ConfigTrace.log file for missing attributes in portal.Then proceed
to the following steps.


adding realm
============
start server1 and WebSphere_Portal servers before starating this task
VMM realm Configuration section
 realmName
 addBaseEntry
 securityUse
 delimiter

configengine.bat wp-create-realm -DWasPassword=wpsadmin

To update the default parents per entity type and realm.Run the following task:
 realmName
 realm.personAccountParent
 realm.groupParent
 realm.orgContainerParent

configengine.bat wp-modify-realm-defaultparents -DWasPassword=wpsadmin

restart server1 and WebSphere_Portal servers

Launch Portal Page in Web browser.Login as New Portal Admin User id /pwd

you can see Administration page

set realm to Default:
====================
wkplc.properties
 realmName
 defaultRealmname

configengine.bat wp-default-realm -DWasPassword

restart server1 and WebSpher_Portal.

add 2nd LDAP [Sun One Directory LDAP Server] and creating Realm2
################################################################

Make sure that both the LDAP's have Unique entries(base DN's) and unique users.
especially the wpsadmin/wpsbind default portal admin id's doesn't exist in both LDAP's. If they exist in both ldap's one has to use Full User DN/pwd
to login to WAS and Portal.

wkplc.properties
a. federated.ldap.id=fed2
b. federated.ldap.host=dora1.rtp.raleigh.ibm.com
c. federated.ldap.port=395
d. federated.ldap.bindDN=cn=Directory Manager
e. federated.ldap.bindPassword=p0rtal4u
f. federated.ldap.ldapServerType=SUNONE
g. federated.ldap.baseDN=dc=raleigh,dc=ibm,dc=com

configengine.bat validate-federate-ldap -DWasPassword=wpsadmin

configengine.bat wp-create-ldap -DWasPassword

restart server1 and WebSphere_Portal servers.

add Realm2
==========
start server1 and WebSphere_Portal servers before starting this task

wkplc.properties
 realmName=SUNRealm2
 addBaseEntry=dc=prasad,dc=ibm,dc=com
 securityUse=active
 delimiter=/

Run the Following task to add new realm to the Virtual Member Manager Configuration

 configengine.bat wp-create-realm -DWasPassword=wpsadmin

Restart server1 and WebSphere_Portal servers.


Launch portal page in web browser and tried to login as Second Realm admin
user id/pwd .Should be able to login to portal successfully.

Logout and to login as First Realm admin user id/pwd .Should be able to login to
portal successfully.Search for users/groups belong to both realms and results
should show both realms users and groups.