Using Apache Solr as your search solution
The Solr search index lifecycle includes tasks that you perform after Commerce+ Transaction Server search is deployed. For example, building, replicating and propagating
the search index, backing up and restoring the search index, and monitoring indexing
activities across different search servers.
Commerce+ Transaction Server use Apache Solr as their standard search engine. Elsaticsearch is the default, however you can still use Solr.
Deploying Apache Solr in Commerce+ Transaction Server environments
If you choose to deploy Apache Solr in your prduction environments, follow the instructions in ../install/tasks/tdeploydocker91-deploysolr.html, for Db2 environments, or ../install/tasks/tdeploydocker91-deploysolroracle.html if you are using Oracle.
Elasticsearch is the default Developer Legacy environment in Commerce+ Transaction Server. If you would like to develop for the Solr engine instead, you can revert back to it. For more information, see ../install/tasks/tigdevrevertsolr.html.