Chapter 3. Medium-size organization OmniFind scenario on Red Hat Enterprise Linux platform 275
Figure 3-125 Status of the CUSTINFO and GENINSINFO collections with Search running
3.3.5 LSTEP5: Query GENINSINFO and CUSTINFO collections
In this step, we query the GENINSINFO and CUSTINFO collections using the
sample search Web application, and the sample search portlet application with a
modified config.properties file specifying the SEQUOIA_secure search
application ID.
Using the Web sample application
OmniFind Enterprise Edition V8.4 has a new capability to customize a custom
search application, type the URL for the Search Application, and append the
name of the configuration file for your search application. For example:
http://SearchServer.com/ESSearchApplication/search.do?configFile=/WEB-I
NF/myConfig.properties
If the file that you specify (myConfig.properties file in the above example) does
not exist, values in the config.properties file (which has the applicationName
property value of Default, as shown in Example 3-4 on page 276) for the sample
search application are used.
276 IBM OmniFind EE V8.4: Configuration and Implementation Scenarios
Example 3-4 config.properties file
# Search Application
applicationName=Default
.........
.......
We are showcasing this capability here since the Default search application only
has access to the GENINSINFO collection, while the SEQUOIA_secure search
application has access to both the GENINSINFO and CUSTINFO collections.
This requires the creation of a separate config.properties file named
sec_config.properties with the applicationName property changed to
SEQUOIA_secure, as shown in Example 3-5.
Example 3-5 sec_config.properties file contents
# Search Application
applicationName=SEQUOIA_secure
.........
........
# SSO related values
# The ssoCookieName corresponds to the name of the HTTP header
# that contains the Single Sign On cookie value.
ssoCookieName=LtpaToken
.........
.......
Accessing the GENINSINFO collection
Figure 3-126 on page 277 through Figure 3-129 on page 280 describe the user
interactions searching the GENINSINFO collection.
The Sample Search application is invoked without specifying a config.properties
file (http://falcon.itsosj.sanjose.ibm.com/ESSearchApplication/), which implicitly
uses the config.properties file. After logging in to the sample search Web
application with the esadmin user ID (Figure 3-126 on page 277), you are
presented with the Search box, as shown in Figure 3-127 on page 278. Click the
Preferences link in Figure 3-127 on page 278 to view the default preferences
and modify it as required. Figure 3-128 on page 279 shows a number of options
that can be modified for the search session, including inclusion of quick links, the
data sources to be searched, file types to be excluded/included, number of
results per page, and whether to search for synonyms. By default, if multiple
collections exist, the sample search application automatically searches across all
the collections using a “remote” federator”.
8
In this case, since only the Default
Chapter 3. Medium-size organization OmniFind scenario on Red Hat Enterprise Linux platform 277
application only has access to the GENINSINFO collection, only that collection
appears in the list of choices in the Preferences window. Click Apply to save the
choices made.
In Figure 3-129 on page 280, enter the string “insurance” in the search box and
click Search. The results of this query is shown in Figure 3-129 on page 280.
Figure 3-126 Login to Sample Search application
8
A federator is used to issue a federatedsearch request across a set of heterogeneous searchable
collections and get a unified document result set. Search federators are intermediary components
that exist between the requestors of service and the agents that perform that service. They
coordinate resources to manage the multitude of searches that are generated from a single
request. Enterprise search provides “local” and “remote” federators. A local federator federates
from the client over a set of searchable objects across collections in more than one server, while a
remote federator federates from a server over a set of collections in the same server. For a brief
description of federators, refer to Chapter 5, “Merger of SMB and medium-size organizations” on
page 409. For more detailed information about federators, refer to the IBM OmniFind Enterprise
Edition V8.4 Programming Guide and API Reference for Enterprise Search, SC18-9284.
278 IBM OmniFind EE V8.4: Configuration and Implementation Scenarios
Figure 3-127 Search box
Chapter 3. Medium-size organization OmniFind scenario on Red Hat Enterprise Linux platform 279
Figure 3-128 Preferences options

Get IBM OmniFind Enterprise Edition Version 8.4 Configuration and Implementation Scenarios now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.