You can configure the search portlets for local operation, or you can configure them for remote search service. Depending on your configuration, remote search service might have performance benefits by offloading and balancing system load.
You can provide the remote search service either as an EJB or as a Web service via SOAP. With EJB you can have security enabled. With SOAP this is not possible.
When you want to index and search portal sites, search results are filtered according to the user security credentials. This filtering occurs independently of whether security is enabled on the remote search server or not. However, if security is not enabled, an unauthorized user can connect to the remote server and obtain unfiltered search results. If you want to prevent this, you need to use EJB and enable security on the remote server.
Showing posts with label administersearch. Show all posts
Showing posts with label administersearch. Show all posts
Configuring Portal Search in a cluster
To support Portal Search in a clustered environment, you must install and configure search for remote search service on an IBM WebSphere Application Server node that is not part of the IBM WebSphere Portal cluster.
To install and configure the search service remotely, perform the following tasks:
1. Install and configure the search service to work remotely, that is, on a remote WebSphere Application Server node which is not part of the portal cluster. You can provide the remote search service either as an EJB or as a Web service via SOAP. Deploy the appropriate EJB or SOAP EAR file on the remote WebSphere Application Server node. For details about how to do this, refer to the WebSphere Application Server documentation.
2. Configure the search portlets for remote search service so that they access the remote server accordingly.
To enable search in a cluster for content stored in the JCR database, you must configure each machine in the cluster to access a shared directory. JCR-based content includes content created with Web Content Management or Personalization.
Create a shared directory called jcr/search on a machine in the network and ensure that each node in the cluster has network access to the directory.
To install and configure the search service remotely, perform the following tasks:
1. Install and configure the search service to work remotely, that is, on a remote WebSphere Application Server node which is not part of the portal cluster. You can provide the remote search service either as an EJB or as a Web service via SOAP. Deploy the appropriate EJB or SOAP EAR file on the remote WebSphere Application Server node. For details about how to do this, refer to the WebSphere Application Server documentation.
2. Configure the search portlets for remote search service so that they access the remote server accordingly.
To enable search in a cluster for content stored in the JCR database, you must configure each machine in the cluster to access a shared directory. JCR-based content includes content created with Web Content Management or Personalization.
Create a shared directory called jcr/search on a machine in the network and ensure that each node in the cluster has network access to the directory.
Enabling anonymous users to search public pages of your portal
You can enable anonymous users (sometimes also called unauthenticated users) to search public pages of your portal by using a portal search portlet.
To do this, make the Search and Browse portlet or the Search Center portlet available on a public page of your portal, so that users can access them without having to log in to the portal.
You also need to enable public sessions for your portal. The reason is that both the Search and Browse portlet and the Search Center portlet need a valid session for their run time, and by default, sessions are not enabled on anonymous pages in the portal. By default, sessions are only created when a user authenticates and logs in to the portal.
Take a look at Infocenter document for step by step procedures on how to enable search for anonymous users
To do this, make the Search and Browse portlet or the Search Center portlet available on a public page of your portal, so that users can access them without having to log in to the portal.
You also need to enable public sessions for your portal. The reason is that both the Search and Browse portlet and the Search Center portlet need a valid session for their run time, and by default, sessions are not enabled on anonymous pages in the portal. By default, sessions are only created when a user authenticates and logs in to the portal.
Take a look at Infocenter document for step by step procedures on how to enable search for anonymous users
Subscribe to:
Posts (Atom)