Go to parent topic - Pattern 2: Putting social into context.
For the integration with search, IBM Connections portlet needs to be configured in IBM WebSphere Portal. Also, we need to configure the search results navigation to the connections portlet in IBM WebSphere Portal.
There are two ways to search IBM Connections content. They are :
Search Collections : Using this way the Portal Search Engine (PSE) which is a text search engine, crawls and indexes Connections content and stores it in an Operating System files directory (also called collection). PSE internally uses the Seedlist Framework to index content. The indexing process happens at a regular interval updating the changes made in the Connections server to the collections directory. The advantage with this approach is that the indexing and search process is performed by a separate engine and it does not affect the Connections server. The disadvantage is that during the indexing process the Connections server may be overloaded and the performance is bit affected during this time.
Remote Content Search Service : Using this way, the Search service uses the Connections API which internally uses REST framework to search content directly from a Connections server. This search service is also known as RCSS Type search. The advantage using this approach is that the maintenance is easy as there is no Collections to maintain. Since it is a live search, there is a disadvantage of Connections being overloaded during search process.
Configuring portal for integrated search
For configuring integrated search of Portal with Connections, the following files need to be copied from IBM Connections portlet (available in Lotus Greenhouse catalog) install zip to Portal Server :
Piece of Content (PoC) handler jar file : Copy the file com.ibm.lconn.lcaccelerator.poc.jar from location <portlet install zip>/POCResolver to Portal Server in <PortalServer>/shared/app
Display provider plug-in (DPP) jar file : Copy the file com.ibm.lconn.lcaccelerator.dpp.jar from location <portlet install zip>/DisplayProvider to Portal Server in <PortalServer>/shared/app
Icons Folder : Copy the folder icons from location <portlet install zip>/DisplayProvider to Portal Server in <wp_profile>/installedApps/NODE_NAME/wps.ear/wps.war/images/icons
This article is one of several which describes how to configure the search component:
5.6 Searching across Portal and Connections
This topic is part of the Pattern 2 description: