180 WebSphere Commerce V7.0 Feature Pack 2 Search Solution Overview and Deployment
7.1 Solr V1.3 indexes
Solr is a stand-alone enterprise search server with a Representational State Transfer
(REST)-like application programming interface (API). You put documents in the Solr server,
which is called
You query it via HTTP GET and receive XML, JSON, or binary results. Solr uses the Lucene
search engine API.
7.2 IBM WebSphere Commerce V7.0 index
WebSphere Commerce V7.0 search uses one index configuration, the catalog index. Multiple
catalog instances, or
cores, exist in a production environment. For our exercise, we deploy the
index inside the WebSphere Commerce Developer Edition 7.0 in embedded mode.
Search tools to work with indexes require a master catalog to be used, and they index the
sales catalogs correctly. When a Solr query is received, you must always use a master
catalog and not a sales catalog. You still have full use of sales catalogs for search driven
navigation and searching, by continuing to use catalogId=<sales catalog id> when making
requests. Commerce adds a filter query, fq=catalog_id:<catalogId>. This filter query
causes the response to contain only documents in that catalog.
7.2.2 Setting up the search index
In this section, we run the setupSearchIndex.bat to set up the catalog index. The
setupSearchIndex.bat creates the configuration files that are needed to preprocess the
index data. Follow these steps:
1. Start the WebSphere Commerce Developer Edition test server (see Figure 7-1 on
page 181). Complete these tasks:
a. Start Rational® Application Developer for WebSphere Software.
b. Select the Servers tab.
c. Select WebSphere Commerce Test Server.
d. Right-click, and then, select Start.