Upload Solr Configset on Managed Cloud Solr Server

When you are using Sitecore managed cloud and you want to deploy Solr configsset to Solr cloud, there are lots of APIs available here to download, upload, delete, start, stop, etc. In this blog, we are going to discuss a few APIs. There is a GitHub repo is also available with PowerShell script which can be used easily.

Upload New Solr ConfigSet

Below are the steps to upload the Solr config set:

Download the existing configset from Github.
Update ACCOUNT, uid, NAME, APIKEY.

The account will be SitecoreLive
uid will be a short name provided by Sitecore like ss256325
NAME will be Sitecore Configset which you want to download
APIKEY will be the Solr API key provided by Sitecore

Run PowerShell script in PowerShell console. It will download configset in the same folder.

Create Sitecore Configset

Download the existing configset from Github.
Update ACCOUNT, uid, NAME, APIKEY.

Account will be SitecoreLive
uid will be a short name provided by Sitecore like ss256325
In form object, add name as a configset name from which name you want to create and in files, you can give the name of configset zip.
APIKEY will be Solr API key provided by Sitecore.

Run PowerShell script in PowerShell console. It will upload Sitecore configset in /configs folder as mentioned below the image.
Now you can create a new core using this Sitecore configset.

Note: If you are getting the below error, then make sure to use PowerShell 7.0+ version.

Delete Sitecore Configset

Download the existing configset from Github.
Update parameter in PowerShell script and run PowerShell script. It will delete configset that you have mentioned in PowerShell.

Stop Solr Port

Download the existing configset from Github.
Update parameter in PowerShell script and in NODE mention, uid-node number, like 1,2,3, depends on how many nodes you have. Stop nodes one by one.

Start Solr Port

Download the existing configset from Github.
Update parameter in PowerShell script and in “NODE” mention, “uid-node number”, like 1,2,3, depends on how many nodes you have. Start nodes one by one.

Comments

Sitecore 10.2 - “Failed to start service ‘Sitecore Marketing Automation Engine’” on Windows 11

Sitecore 10.2 - “Failed to start service ‘Sitecore Marketing Automation Engine' ” on Windows 11 Today I started to install Sitecore 10.2 using Sitecore Instance Manager on Windows 11 and I got this issue “Failed to start service ‘Sitecore Marketing Automation Engine' ” . Error : On event viewer it was showing the below error: I also tried to run ‘ Sitecore.MAEngine.exe ’ like this C:\Windows\system32>C:\inetpub\wwwroot\sclocal102xconnect.dev.local\App_Data\jobs\continuous\AutomationEngine\Sitecore.MAEngine.exe Which was throwing below error: Starting Marketing Automation Engine... 2022-01-29 22:21:11 ERR Error initializing XConnect client. System.AggregateException: One or more errors occurred. ---> Sitecore.XConnect.XdbCollectionUnavailableException: An error occurred while sending the request. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected err

Azure AD Integration with Sitecore 10.2

Azure AD Integration with Sitecore 10.2 Sitecore identity server that comes with Sitecore 9.1 allows you to log in through an external identity provider like Azure Active Directory, Facebook, Apple, or Google. It is built on Federation Authentication. What is Federation Authentication? Federation authentication is a technology to allows users to access multiples application, tools, and domains using one credential. Using one set of credential user can access multiple applications, and resources after authentication. Federation authentication consists of two systems, the Identity provider and the Service provider. Identity providers that maintain/create/manage identity information like name, email address, device, and location. Some examples of identity providers are Azure AD, Google, Facebook, and Apple. Service providers basically refer to a website, software, or app that the user is trying to access and SP basically relies on the identity provider to authenticate the user and provi

Sitecore Custom API Issue with Federation Authentication

Sitecore Custom API Issue with Federation Authentication In earlier segments, detailed in Part 1 and Part 2 of the blogs on Keycloak Integration with Sitecore, I introduced Keycloak functionality for CM login. Concurrently, I addressed a necessity to develop custom APIs for retrieving Sitecore users and roles. Following the development of custom APIs, during authentication failures, the API erroneously returned a status code of 200 instead of 401. The problem arose because API requests were being routed through the "owin.identityProviders" pipeline, which was not intended for API usage. Solution: When OWIN identifies a 401 response and the AuthenticationMode is set to "Active," it fails to capture the URL hash included in the request. Another choice is to activate the "Passive" AuthenticationMode, wherein OWIN refrains from actively intercepting 401 responses. In passive mode, your application needs to explicitly issue a Challenge to trigger the OWIN aut

Swati Gupta (3x Sitecore MVP) | Blogs

Search This Blog