Solr

Ckan-solrPre-configured Solr Docker images for CKAN.Note: These images are built on top of the upstream Solr images. These images receive bug fixes from time to time which we pull into ours, but you won't get them unless you re-pull the CKAN Solr image.The recommended Solr version for the currently supported CKAN version is Solr 9.You can get a local Solr instance targeting a specific CKAN version by running the following command:docker run --name ckan-solr -p 8983:8983 -d ckan/ckan-solr:2.11-solr9The following versions are available as different image tags:CKAN VersionSolr versionDocker tagNotes2.11Solr 9ckan/ckan-solr:2.11-solr9, ckan/ckan-solr:2.11-solr9.8This is the recommended version if you are unsure which one to use2.11Solr 9ckan/ckan-solr:2.10-solr9-spatial, ckan/ckan-solr:2.10-solr9.8-spatialContains fields needed for the ckanext-spatial geo search2.10Solr 9ckan/ckan-solr:2.10-solr9, ckan/ckan-solr:2.10-solr9.82.10Solr 9ckan/ckan-solr:2.10-solr9-spatial, ckan/ckan-solr:2.10-solr9.8-spatialContains fields needed for the ckanext-spatial geo search2.10Solr 8ckan/ckan-solr:2.10-solr8 (previously ckan/ckan-solr:2.10)2.10Solr 8ckan/ckan-solr:2.10-solr8-spatial (previously ckan/ckan-solr:2.10-spatial)Contains fields needed for the ckanext-spatial geo searchmasterSolr 9ckan/ckan-solr:masterThe master image is built nightlyThe following tags are no longer supported:CKAN VersionSolr versionDocker tagLegacy Docker tagsNotes2.7Solr 6ckan/ckan-solr:2.7ckan/ckan-solr-dev:2.72.8Solr 6ckan/ckan-solr:2.8ckan/ckan-solr-dev:2.82.9Solr 6ckan/ckan-solr:2.9ckan/ckan-solr-dev:2.92.9Solr 9ckan/ckan-solr:2.9-solr9Requires at least CKAN 2.9.52.9Solr 9ckan/ckan-solr:2.9-solr9-spatialContains fields needed for the ckanext-spatial geo search2.9Solr 8ckan/ckan-solr:2.9-solr8Requires at least CKAN 2.9.52.9Solr 8ckan/ckan-solr:2.9-solr8-spatialContains fields needed for the ckanext-spatial geo searchAll these images expose the CKAN Solr endpoint at so that's what you should set the value of solr_url in your ini file to.Building the imagesGo to the relevant folder for the Solr version (eg solr-9) and use the Makefile included:# Default version is 2.11make build# Specify a different versionmake build CKAN_VERSION=2.10Use your own configuration filesIf you want to play around with the solr config files you can copy them from the container to your local host and then run the container with a bind mount.Run a container:docker run --name ckan-solr -p 8983:8983 -d ckan/ckan-solr:2.11-solr9Copy the config file of the target core to your machine (eg ckan):docker cp ckan-solr:/opt/solr/server/solr/configsets/ckan/conf ./my_confStop the container:Run the container with a bind mount:docker run -p 8983:8983 --mount type=bind,source="$(pwd)"/my_conf,target=/opt/solr/server/solr/configsets/ckan/conf -d ckan/ckan-solr:2.11-solr9Edit your local filesReload the core using the Solr admin page:

Solr nodes: Solr process 12755 running on port 7574{ "solr_home":"/home/russell/Documents/docs-projects/solr-docs/solr-5.2.1/example/cloud/node2/solr/", "version":"5.2.1 1684708 - shalin - 2015-06-10 23:20:13", "startTime":"2016-08-19T18:11:27.087Z", "uptime":"0 days, 0 hours, 13 minutes, 2 seconds", "memory":"50 MB (%10.2) of 490.7 MB", "cloud":{ "ZooKeeper":"localhost:9983", "liveNodes":"2", "collections":"1"}}Solr process 12564 running on port 8983{ "solr_home":"/home/russell/Documents/docs-projects/solr-docs/solr-5.2.1/example/cloud/node1/solr/", "version":"5.2.1 1684708 - shalin - 2015-06-10 23:20:13", "startTime":"2016-08-19T18:11:21.637Z", "uptime":"0 days, 0 hours, 13 minutes, 8 seconds", "memory":"44.9 MB (%9.2) of 490.7 MB", "cloud":{ "ZooKeeper":"localhost:9983", "liveNodes":"2", "collections":"1"}}To stop Solr while running in SolrCloud mode, use the stop command, like this:bin/solr stop -allConfigure the Solr Adapter for SolrCloudThere’s only one thing left to do: specify the client type as CLOUD inLiferay’s Solr adapter.From System Settings or your OSGi configuration file, set the Client Typeto CLOUD. clientType="CLOUD"Start Liferay DXP if it’s not running already.Now you’re able to configure Liferay DXP for Solr, and Solr for Liferay DXP. Rememberthat Elasticsearch is the default search engine for Liferay DXP, so if you’re notconstrained to use Solr or already a Solr expert, consider Elasticsearch for yousearch engine requirements. If you do use Solr, then you can tell all yourcolleagues that your Liferay DXP installation’s search capability is Solr powered(pun intended).

Solr is a popular enterprise search platform build on Apache Lucene. It’spopular for its reliability, scalability, and fault tolerance. Read more aboutit here.Although Elasticsearchis the default search engine that ships with Liferay DXP, it’s perfectly valid touse Solr instead. In particular, if you’ve already been using Solr with aprevious version of Liferay DXP, or your deployment system (for example, your OS orJVM) isn’t supported by Elasticsearch,you might choose to use Solr to search and index your Liferay DXP data.Liferay’s support for Solr is compatible with Solr versions 5.2.x through 5.5.x.To make Liferay DXP and Solr talk to each other, you’ll need to install the LiferaySolr adapter. There are two ways to do this:Navigate to the Liferay Marketplacewebsite and download the LPKG file for Liferay (CE) Solr 5 SearchEngine. Once you do, copy the LPKG to your Liferay_Home/osgi/marketplacefolder.In your running Liferay instance, navigate to Control Panel → Apps→ Store. Sign in using your credentials, search for Solr SearchEngine, and purchase (it’s free) the Liferay (CE) Solr 5 SearchEngine entry.This guide leads you through the process of installing and configuring Solr.As you proceed, these terms will be useful to keep in mind:Solr Home: The center of the Solr system (pun intended). This directory issolr-[version]/server/solr.Liferay Home: The root folder of your Liferay DXP installation. It containsthe osgi, deploy, data, and license folders, among others.Before configuring Liferay DXP for Solr, you need to install and set up Solr.Installing and Configuring Solr 5To install and properly configure Solr for Liferay DXP:Download Solr and unzip it.Navigate to solr-[version]/server/solr. This is Solr Home.Create a new folder called liferay.In the liferay folder, create two new folders: conf and data.Copy the contents of Solr_Home/configsets/data_driven_schema_configs/confto Solr_Home/liferay/conf.Open the Liferay Solr Adapter’s LPKG file with an archive manager.Open the com.liferay.portal.search.solr.jar file, and extract META-INF/resources/solrconfig.xmland META-INF/resources/schema.xmlto Solr_Home/liferay/confThis replaces the current solrconfig.xml and schema.xml files with onesthat tell Solr how to index data coming from Liferay DXP.Create a core.properties file in Solr_Home/liferay, and add thesecontents: config=solrconfig.xml dataDir=data name=liferay schema=schema.xmlCheckpoint: your Solr_Home/liferay folder should now have this structure: liferay ├── conf │ ├── currency.xml │ ├── elevate.xml │ ├── lang │ ├── managed-schema │ ├──

//index.md --> Back upThere are a number of ways to back up Search Services. You can set the Solr indexes backup properties either by: Editing the ‘solrcore.properties’ file Using a JMX client, such as JConsole. Note: This feature is only available when you are using Alfresco Content Services Enterprise.This task shows you how to specify the Solr backup directory by using the /solrhome/templates/rerank/conf/solrcore.propertiesTo set the Solr backup directory using the solrcore.properties file, set the value of the following properties to the full path where the backups should be kept after starting solr (remember to make sure it is an exsisting location and the path is the correct format depending on if uisng MAC/Windows/Linux):solr.backup.dir=Then stop solr and repeat the same step for each of the cores created after startup. The above path should have copied the path to the cores at creation but alfresco and archive would need to be specified for each core.To set the Solr backup directory for each core use the /solrhome/alfresco/conf/solrcore.properties and /solrhome/archive/conf/solrcore.properties file and edit the same property as above.Then restart solr with these properties added and then use the admin console to edit the frequency of the backup.You can only see the Admin Console if you’re an administrator.To edit the frequency of the backup, you can use the Cron Expression via the admin console. Launch the Admin Console. For information, see Launch Admin Console. In the Repository Services section, click Search Service. You see the Search Service page. Scroll down to the Backup Settings section. Here, you can edit backup properties for each core of the Solr index: Main Store and Archive Store. Backup Cron Expression: Specifies a Quartz cron expression that defines when backups occur. Solr creates a timestamped sub-directory for each index back up you make. Backups To Keep: Specifies the maximum number of index backups that Solr should store. Click Save.This task shows how to specify the Solr backup directory by using the /shared/classes/alfresco-global.properties file.To set the Solr backup directory using the alfresco-global.properties file, set the value of the following properties to the full path where the backups should be kept:solr.backup.archive.remoteBackupLocation=solr.backup.alfresco.remoteBackupLocation=The values set on a subsystem will mean that the property values from configuration files may be ignored. Use the solrcore.properties or JMX client to set the backup location.If you have installed the Oracle Java SE Development Kit (JDK), you can use the JMX client, JConsole, to backup Solr indexes, edit Solr backup properties and setup the backup directory. You can set the backup of Solr indexes using the JMX client, such as JConsole on the JMX MBeans > Alfresco > Schedule > DEFAULT > MonitoredCronTrigger > search.alfrescoCoreBackupTrigger > Operations > executeNow tab. The default view is the Solr core summary. Alternatively,

Managed Search Fully-Managed Solr Service in any cloud Automate, manage and scale high-availability, hosted Solrsearch infrastructure. Automate, manage and scale high-availability, hosted Solrsearch infrastructure. Build Faster, Scale Faster and Reduce Incidents with SearchStax Managed Search Service Build Faster Our customers spend 90% less time setting up Solr vs. DIY Scale Faster Customers who scaled with SearchStax did it 16x faster than DIY Reduce Incidents 95% of customers had no downtime in last 12 months Managed Search is Designed for Developer Productivity All the Features You Need for Production-Grade, Highly Available Hosted Solr Click on Each Card Below to Learn More Our Dedicated and Customized Plans can deploy Solr search infrastructure on AWS, Azure or Google Cloud in over 70 regions across the globe Cloud Automation Lets You Set Up and Deploy Solr Infrastructure in Minutes Compared to DIY Configure Dedicated Solr Nodes or Clusters Set up, configure, deploy and expand your search applications with ease. Go from one node to many in a matter of minutes with no downtime. Our web interface allows you to orchestrate and automate all of the critical operational tasks you currently perform manually. Monitor the Health of your Solr Deployments Monitoring and Alerting makes it easy to stay on top of Solr infrastructure health We’ve got your monitoring and alerting needs covered. Spend just a few minutes with SearchStax configuring the metrics and thresholds you want, type in where you want the alerts sent and you’re ready to keep a tab on your Solr health. Maximize Uptime with Disaster Recovery & Backups Multiple options to meet all business requirements and budgets Choose from Cold, Warm and Hot SLA-backed disaster recovery options to meet your RPO and RTO objectives. Easily create on-demand or scheduled backups for your Solr deployments. Enterprise-Grade Security for Solr Deployments Reduce project risk from Solr and meet all security and compliance requirements Single Sign-on Two-Factor & Basic Authentication Whitelisting Encryption at Rest & Transport Role-Based Access Control SOC2, HIPAA & GDPR Compliant Private Environments via Peering Priority Patching Vulnerability Scanning Private Environments for Increased Security Get private cloud infrastructure (VPC or VNet) to meet privacy & governance requirements Accelerate Implementation with Connectors & APIs Seamlessly integrate Solr into custom applications & major CMS platforms -- Sitecore, Adobe Experience Manager, Drupal & Acquia Cloud Connector Install & configure Solr for Sitecore in minutes. Developer APIs Leverage APIs to create, delete & manage Solr

Params.json │ ├── protwords.txt │ ├── schema.xml │ ├── solrconfig.xml │ ├── stopwords.txt │ └── synonyms.txt ├── core.properties └── dataStart the Solr server by entering ./bin/solr start -ffrom the top-level folder of your Solr installation (solr-[version]).The Solr server listens on port 8983 by default. Navigate to (assuming you’re testing locally withlocalhost as your host), and confirm that the liferay core is available.Solr is now installed. Next install and configure Liferay DXP’s Solr adapter.Installing and Configuring the Liferay Solr AdapterSince Elasticsearch is the default search engine in Liferay DXP, the Elasticsearchadapter is already installed and running. Stop it before configuring the Solradapter.Stop the Elasticsearch adapter bundle using the App Manager, the Felix Gogoshell, or the bundle blacklist. If you’re a Digital Enterprise customer, use theblacklist feature as described below. The App Manager and Gogo shell rely on theosgi/state folder to “remember” the state of the bundle. If you delete thisfolder (recommended during patching) the Elasticsearch connector will bereinstalled and started automatically.Navigate to Control Panel → Apps → App Manager.Once you’re in the App Manager, search for elasticsearch. Find the LiferayPortal Search Elasticsearch module and click the edit(()) button. Choose the Deactivateoption. This leaves the bundle installed, but stops it in the OSGi runtime.Alternatively, use the Felix Gogo shell tostop the Elasticsearch adapter. First, open a Gogo shell and enterlb elasticsearchYou’ll see an active bundle named Liferay Portal Search Elasticsearch (version)listed in the Gogo shell.ID |State |Level|Name239|Active | 10|Liferay Portal Search Elasticsearch (2.0.4)Stop the Elasticsearch adapter by enteringstop [bundle ID]In the case above, the [bundle ID] is 239.Now you can install and configure the Solr adapter:Start Liferay DXP, then deploy the Solr adapter by copying the LPKG youdownloaded to Liferay_Home/deploy.You’ll see a STARTED message in your Liferay DXP log once the solr adapter isinstalled. Here’s what the log message looks like: 08:48:24,165 INFO [localhost-startStop-1][BundleStartStopLogger:35] STARTED com.liferay.portal.search.solr_2.0.3 [47]To reindex against Solr, navigate to Control Panel → Configuration→ Server Administration, and click Execute next to the Reindex allsearch indexes option.Figure 1: Once the Solr adapter is installed, you can reindex your Liferay DXP data against your Solr server.In production deployments, specify your edits to