Implementation of search collections is different in clustered environment than standalone environment.
Standalone WCM search collection implementation is very straight forward and can be done by following steps mentioned in this link:
http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Indexing_web_content_wcm7
But for clustered environment, IBM documentation suggests to implement Remote Search collection.
As per the documentation provided here:
http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Configuring_Portal_Search_in_a_cluster_on_Windows_wp7
An instance of WAS node is required which should not be part of Portal Cluster.
Having a separate WAS node or instance depends upon your requirement. If the portal or WCM search is used very extensively in the Portal then somethings it is better to have a new instance of WAS installed for Remote Search.
But if you have a very limited use of Search, then you can create a new "default" profile of WAS on any one of the cluster member machines. This can be achieved by either using Profile Management tool or ./manageprofiles.sh
Once you have successfully created a new WAS profile, start the profile and then follow the steps mentioned in following link on to perform tasks on newly created profile and cluster primary node:
http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Preparing_for_remote_search_service_wp7
Once these steps are complete follow the steps mentioned in following link to configure remote search service:
http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Configuring_a_remote_search_service_wp7
0 comments:
Post a Comment