The SolrCloud Search Service Adapter connects the Intershop Commerce Management (ICM) with a Solr server that runs in cloud mode. The search index configuration and maintenance in the ICM back office uses the Schema- and ConfigSet-REST-APIs provided by Solr. Thus, the Solr server is separate and independent of the ICM application server cluster.
Intershop Commerce Management | SolrCloud Search Service Adapter | Solr Server |
---|---|---|
11.0+ | 4.7.1 | 8.11 |
Please see Reference - ICM 11 Release Versions for versions that are released and tested together.
The following table lists the cartridges contained in the SolrCloud Adapter:
Cartridge | Description | Required |
---|---|---|
ac_solr_cloud | The main implementation cartridge of the adapter defining and registering the search service. | |
ac_solr_cloud_bo | Additional functionality for the Commerce Management application. It provides additional configuration options for the index management, especially for suggest and spell-check. |
Follow the basic setup of ICM 11 customization described in Concept - Customization ICM 11 - Deployment to add the customization cartridges to ICM and to the cartridge list.
Add the ft_solr_cloud
feature to the cartridge list:
environment: CARTRIDGE_LIST: "ft_demo_search ft_headless ft_solr_cloud"
Add the Solr adapter to the customizations section of the helm chart:
... customizations: solrcloud: repository: intershophub/icm-as-customization-f_solrcloud:4.7.0 ....
The following environment variables show the setup of the most common options:
environment: SOLR_CLOUDSOLRSERVERURLS: "https://slr-test-slr-test-solrcloud.test.intershop.com/solr" SOLR_CLUSTERINDEXPREFIX: "cstmr-int-ed" SOLR_COLLECTIONREPLICATIONFACTOR: 2 SOLR_CLOUDBACKUPLOCATION: "/var/solr/data/backup-restore/local-collection-backups-1" SOLR_BASICAUTH: "solr:SolrIsAwesome!"
The environment variables in detail (from top to bottom):
With SolrCloud Adapter 4 it is required to configure a common Solr service URL with SOLR_CLOUDSOLRSERVERURLS
instead of a connection to a list of zookeeper hosts. (required)
The cluster index prefix is required to distinguish the indexes from multiple ICM systems, e.g., if data replication is used. (optional on development environment)
The recommendation for the replication factor is 2 to have redundancy of indexes on two nodes. This way, there is always an index online even if the Solr cluster is re-started with a rolling restart. (Set to 1 if there is only a single Solr, e.g., in development environments.)
A backup location is needed if data replication for search indexes is used.
In general, basic authentication is used for the connection from ICM to the Solr server. To set the user/password for the basic authentication, add it to the environment.
The basic authentication user and password string can also be used from a generic secret instead of adding it as plain text in the environment:
secrets: - env: SOLR_BASICAUTH name: icm-secrets key: solr_basicauth
The adapter comes with an initial Solr configset configuration that is prepared into sites/root/1/solrcloud. If the customization is added after database initialization, it is important to execute the initialization for the ac_solr_cloud
to make this configuration available.
Enable the managed services in Operations, see Intershop Organization Management Help | Managing Services.
Create search services in the organization and channels, see Intershop Commerce Management Help | Managing Search Index Services.
Create and Manage Search Indexes, see InterShop Commerce Management Help | Managing Search Indexes.
The Solrcloud Search Service Adapter 4 connects the Intershop Commerce Management (ICM) Platform with Apache Solr to provide integrated search and navigation capabilities based on ICM's managed search service integration framework. The adapter provides the full backend feature-set as known from ICM 7.10 Search and Navigation. However, some of the features (display of spell-checking results, search redirects, object suggest search) are not integrated out of the box into the ICM 11 standard storefront (PWA) anymore.
ID | Title |
---|---|
No update of ish-config.xml after search index config changes |
ID | Title |
---|---|
Support multiple value attributes in object suggest search indexing |
ID | Title |
---|---|
SolrAdapter ConcurrentModificationException in "BackupAndRestoreSolrCloudIndexesDecorator" during staging | |
Object suggest index build - offline content index causes NullPointerException | |
SKU is not usable as separate entry in object suggest type search |
ID | Title |
---|---|
Add property to change Solr client to use HTTP/1.1 or HTTP/2 |
ID | Title |
---|---|
Improve DELETE request handling |
Features
ID | Title |
---|---|
Parallelize restore & backup of search indexes during replication | |
Rebuild inconsistent search indexes during replication |
ID | Title |
---|---|
Automatic search index update after product deletion via back office is not reflected in search index list | |
Restore collection fails with server exception | |
Concurrent upload of default config set fails with "configuration already exists in zookeeper" | |
Replication fails on BackupAndRestoreSolrCloudIndexesDecorator.onPostReplicationHook due to Solr Cloud OverseerCollectionMessageHandler.waitForCoreNodeName method exception |
Release for referencing updated icm-as/11.3.x
ID | Title |
---|---|
Wrong collection alias set when entry in aliases is missing before replication but a collection exists | |
Collection named like the alias is not deleted | |
Solr Cloud adapter code throws "Closing JDBC connection via finalize method" exception | |
ac_solr_cloud cannot reference intershop.EnterpriseBackoffice.Cartridges |
Initial version that was re-synced from the Solr Adapter Version 3.4.0