Kevin Griffith on building solutions with IBM software
with Tags: omnifind X
This post continues with the Omnifind install and configuration.
The customer needs to search Quickr and WCM content. There is one collection having each type of crawler.
I had some problems configuring WCM search. When the collections had both pre and post filtering security activated there were no WCM results displayed. This was traced to a problem with the Distinguished Names of WCM objects in the collection. During the course of the project the LDAP structure evolved. I used the WCM member fixer tool to update the DNs and this corrected the problem.
Another minor issue occurred concerning the use of disk space. I had the delta build indexer scheduled to run every night while the main build indexer was not scheduled. Eventually data in the delta index directory filled up the available disk space. The solution is to regularly run the main build indexer. When it runs it initializes the delta index directory, deleting old files and freeing up disk space.
IBM support helped identify and correct both these issues.
The Omnifind portlet can be customized in several ways:
Portlet configuration parameters
The Top Results section of the portlet was deactivated with these parameters. Also the value of the parameter having the standard background image was deleted.
The portlet has a resource bundle with labels. Some of these labels were changed.
The JSP that displays the list of results (searchResultsTable.jsp) was modified to launch a DOJO dialog when the user clicks on a search result.
Here is the script:
This post continues the report on the Omnifind install.
I configured WAS security with a Domino LDAP and imported a LTPA key generated from the WAS where portal runs.
This customer needs to search WCM, Quickr, Connections, and the file system. I created one collection containing the WCM, Quickr, and file system crawlers. Configuring the Connections 2.5 crawler will have to wait for the release of an upcoming Omnifind fixpack 5.
To get the WCM crawler to work with Portal Server the ESPACServer application needs to be installed on the Portal Server. To do this, a script that is supplied by Omnifind needs to be run on the portal server. This is a portal server cluster so on each node there is a script that copies resources, then another script that installs and configures the ESSearchPortlet.ear and the ESPACServer.ear applications. Jars that are put in place: es.search.provider.jar, es.security.jar, esapi.jar, ESPortalUtils.jar. The web server plug-in is also updated. All of this is described in the OmniFind infocenter.
The portal search center also needs to be configured. I created a new portal search service and configured it with the host name of the search server, the admin userid/password, and SSO cookie name. See infocenter for the procedure.
To use the standard portal search bar that is in the theme header there is a detailed description in the Omnifind infocenter of what needs to be done. Basically, you replace the standard banner_searchControl.jspf in your theme with the code that is given in the infocenter. Our theme at this customer does not use the standard IBM search bar and control so I had to adapt our search form using the infocenter code as a guide. The important part is making sure the search form action and text input name are correct so that the new omnifind/portalSearchBar.jsp (which was also installed by the script mentioned earlier) is called and receives the search parameter. The jsp passes the parameter to the Omnifind portlet and triggers the search. The user can then enter a search text in the theme’s search bar from anywhere in the portal, click the search button and have the results displayed in the Omnifind portlet.
The next step is to configure the portlet to meet the customer’s requirements: both graphical and functional. There are many configuration parameters available in the portlet to do this. For example, there is a config parameter to identify the WCM fields that are to be displayed in the search results. There are many GUI parameters available to configure as well.