Chapter 2. Small business OmniFind scenario on a Windows 2003 Enterprise Edition platform 133
Figure 2-76 Filter search results for “insurance” by Windows file system source
134 IBM OmniFind EE V8.4: Configuration and Implementation Scenarios
Figure 2-77 Edit Default search application name
Chapter 2. Small business OmniFind scenario on a Windows 2003 Enterprise Edition platform 135
Figure 2-78 Disallow Default search application name access to NWINSURANCE
Using the sample search portlet
In this step, we modified the sample search portlet to access the
NWINSURANCE collection. Appendix A, “Install Sample Search application
portlet” on page 431 describes the installation of the sample search portlet in
WebSphere Portal Server.
Since we had only permitted the NWINSURANCE search application name to
access the NWINSURANCE collection, the config.properties file has to be
modified to change the applicationName property to NWINSURANCE, as shown
in Example 2-2 on page 136. Also shown here are the credentials for
authenticating to the search runtime in the user name (wasadmin) and password
(wasadmin).
136 IBM OmniFind EE V8.4: Configuration and Implementation Scenarios
Figure 2-79 on page 137 through Figure 2-81 on page 139 describe some user
interactions with the sample search portlet. After the user logs in to the
WebSphere Portal, you can access the sample search portlet by clicking the
OmniFind - Windows tab, as shown in Figure 2-79 on page 137.
Figure 2-80 on page 138 shows the search query “insurance” and its
corresponding search results, while Figure 2-81 on page 139 shows the
Preferences details for this sample search portlet, which is identical to the one
shown with the sample search Web application shown in Figure 2-69 on
page 126.
Example 2-2 config.properties file contents
#Wed Dec 06 14:41:29 PST 2006
logoff.backgroundImage=/images/IIOF_logout.gif
username=wasadmin
..........
password=wasadmin
................
applicationName=NWINSURANCE
................
Note: In OmniFind V8.4, the user name / password no longer needs to be
updated in the config.properties file. If you are using the search portlet and
you are sharing the same LtpaToken between WebSphere Portal and
OmniFind, then you do not need a user name / password combination, since
the LtpaToken can be used by the underlying API to communicate securely to
the search server.
Note: At this point, we have the functional requirements met for the enterprise
search solution for Northwest Insurance Inc. Further tests, measurements,
and tuning need to be performed to ensure that the solution fully addresses
the capacity and workload requirements as well.
Chapter 2. Small business OmniFind scenario on a Windows 2003 Enterprise Edition platform 137
Figure 2-79 WebSphere Portal

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.