IBM WebSphere Commerce uses Apache SOLR Search as a search engine solution that provides a full range of packages, mainly in the following areas:
- SOLR Multi-core creation
- Preprocess & Indexbuild processed by DIH (Data Import Handle)
- A convenient query for index files provided by the Search REST service
These three aspects are also throughout the entire life cycle of the SOLR search.
Description: Development environment
The WCS version I am currently using is WebSphere Commerce version 7-feture Pack 7, which integrates the SOLR 4.3.0,FEP7 changes to search and I think there are two main points:
- Previously, search was embedded in the WC ear package as a war package. It is now the separation of the two into two separate applications.
- Provides a search REST Service. Better through the API to query the index file.
In addition, the application server is the was 7.0.0.31 that corresponds to the WCS FEP7, and the local Integrated development environment (IDE) is rad.
Apache SOLR Introduction
SOLR is an enterprise-class full-text search engine built on Lucene, providing a reliable, scalable, and highly customizable solution.
SOLR addresses the creation and persistence of files from the enterprise database to the local index, reduces the load on the database server, and provides a load-balanced solution: SOLR master and slave servers, distribution servers, and the replication of SOLR index.
SOLR and Lucene?
Lucene focuses primarily on the underlying design, while SOLR is responsible for the design of the application layer, and Lucene is essentially a search base rather than a standalone application. Comprehensive two points, one sentence overview: SOLR is built on Lucene, in the face of enterprise-class application of the search application.
Lucene provides the underlying design, such as analyzer.
The profiler's general role is to index a document, where the data in each field will undergo analysis (analysis is the combination of Word and filter), the end of a sentence into a single word, remove the blank symbol in the sentence, uppercase conversion lowercase, plural to the singular, remove superfluous words, The substitution of synonyms and so on.
Example: This is a blog! This, is, a will be removed, the last most left blog. Of course, this symbol will be removed as well.
This process occurs both in the index and in the query process, and is usually done in the same way, in order to ensure that the index and query are correctly matched.
CM Development Log-search engine (i)