Skip to main content

Integrate Sitecore With OPENSOLR


Here goes the story...
Personally when I looked up on the internet I did not find lot of documents which could tell how you can integrate Sitecore with OPENSOLR cloud provider, So I did hands on to it, Talked to their support and successfully integrated our sitecore to create indexes in cloud, Following are the highlights and troubleshooting points that I faced and how you can avoid it.
Quick "How-to" integration points

  • Register on https://opensolr.com/users/login
  • From Dashboard hover over "My Indexes" and select "Add New"

  • Select GEO location server where you want to put index

  • One important thing here is, OPENSOLR does not allow indexes with default keyword "sitecore_", so you will not be able to create those indexes, but to create them, you will need to use following configuration in those config files

    • <index id="sitecore_master_index" type="Sitecore.ContentSearch.SolrProvider.SolrSearchIndex, 
Sitecore.ContentSearch.SolrProvider">
            <param desc="name">$(id)</param>
           <param desc="core">mysitecore_master_index</param>

  • I have shown the content of Sitecore_ContentSearch_Solr_Index_Master.config file and as you can see my index name is same but I have provided the "CORE" name so that it does not contain "sitecore_" keyword, You will need to use this name to create indexes in OPENSOLR.
  • On prompt of create index supply index name, NOTE: If you have specified CORE in search index config, name you give here must match with the CORE name of index and if no CORE is specified in search config, It should match with the index name, Default Sitecore index config will have CORE specified and custom indexes might not.
  • Click on "gear icon (settings icon)" on created index to go to index settings page
  • Click "UPLOAD CONFIG FILES" tab
  • Upload SCHEMA.zip first and after that upload SolrSchema.zip NOTE: Here we need to ask support to provide these files and upload order must match.
  • Do step 2-7 for all other indexes
  • Change ContentSearch.Solr.ServiceBaseAddress URL value in Sitecore.ContentSearch.Solr.DefaultConfiguration.config file pointing to the OPEN SOLR cloud URL (you can get that URL by clicking "Admin Panel" button on each of INDEXes settings page (Step-5)

  • Restart IIS and Open sitecoreintsance/Sitecore
  • From Sitecore launchpad->Control panel->Populate Solr Managed Schema
  • Rebuid index from Sitecore launchpad->Control panel->Indexing manager
  • If everything goes well and if you are able to generate schema and rebuild indexes, you can verify the same by going into "Admin Panel" of any index settings and you can see your SOLR user interface and observe that new documents are created as it will show document count.

Major errors and issues
Personally I faced two major issues,
  • Getting 400 bad requests with different field errors, like unknown field_indexName or unknown field "version_im" or Document is missing mandatory uniquekey field: id
  • Managed-schema.xml of my current on-prem sitecore "conf" did not work at all, which is the known issue in SOLR and Sitecore, Refer to the url https://kb.sitecore.net/articles/227897

Solution
  • Very first thing is you need to make sure is that your SOLR schema, contents of the "conf" folders are corrected, you will need to make sure that there are no "managed-schema.xml" file but rename it to "schema.xml" file, From SOLR 6+, There are no schema.xml files available but only Managed-Schema.xml is there, but that needs to be renamed.
  • Make sure you are referring to correct "conf" of SOLR version, My life saver was OPENSOLR support guy, He provided me two files Schema.xml and SolrSchema.xml (zip files), and uploading those files to my index configuration worked like a charm, So you may want to contact OPENSOLR chat support or via email to talk about this issues, They will see the logs on their end to find out what is the actual issue.
  • Make sure upload order of those two files are followed, first upload schema.xml and later on upload SolrSchema.xml (zip)

I hope this would be helpful for people to get started and integrate with OPENSOLR, Cheers !!!
Labels:

Comments

Post a Comment

Popular posts from this blog

High CPU to completely normal CPU - SXA issue, SXA pages not loading in mobile device

  Hi Team, Today i am going to share one of the nightmarish issue with you all, We are having Sitecore 9.1.1 hosted in azure PaaS environment Our site was working just fine and no noise, but we have been working on a feature release where 7-8 months of development needed to be released to production, Big GO LIVE event right?  Also to make the development smoother we also introduced BLUE/GREEN deployment slots in the same release, so we can easily SWAP slots and go live Everything went well, we went live, we even did load and performance testing on our staging and pre-prod and we were confident enough of results Very next day we started getting "SITE DOWN" alerts, and also product owners and clients mentioned that site is very slow for them in US time and in our morning when we were accessing it, it was working lighting fast so we were clue less at start, but we started digging  1) First thing caught our eyes were HIGH CPU spikes, in US time, also without any traffic CPU u...
3 comments
Read more

Set up leprechaun code generation with Sitecore XM Cloud Starterkit

Hi Sitecorians, It has been amazing learning year so far and with the change in technology and shift of the focus on frontend frameworks and composable products, it has been market demand to keep learning and exploring new things. Reasons behind this blog Today's topic is something that was in my draft from April-May, and I always thought that there is already a good documentation out there for  Leprechaun  and a blog post is not needed, Until I realized that there was so many of us facing same kind of issues and same kind of problems and spending same amount of time, That is where I thought, if I could write something which can reduce that repetitive troubleshooting time, That would really help the community. 1)  In a project environment, if we get into some configuration issues, we resolve them, we make sure we are not blocked and continue, but if you think same issue, same step and same scenario will come to other people, so if we can draft it online, it will help othe...
Post a Comment
Read more

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!
1 comment
Read more