I want to know if there is any inbuilt feature kentico provides where one can use elastic search in Kentico CMS OR Is there a way we can integrate Elastic search with kentico CMS. Any suggestions or ideas will be highly appreciated.
Well, you should follow the Elastic search documentation to use their API how to integrate. In Kentico you can use e.g. REST service or, the integration bus or, simply the API to expose the data you want to the Elastic search engine. There is no special magic. Simply said - it is up to you how you will get the data from Kentico and pass them to Elastic engine.
Related
Does any know of any examples out there that show how to implement ISearchService using Azure search service in Sitefinity?
Sitefinity supports Azure search out of the box. And you don't need to implement your own ISearchService.
This is official documentation how to connect your Sitefintiy to Azure search service: https://www.progress.com/documentation/sitefinity-cms/generate-and-store-search-indexes-in-the-cloud
The closest one I found is from their official forum:
https://knowledgebase.progress.com/articles/Article/search-mark-a-field-in-azure-search-as-facetable
I am trying to set up a custom API for my application. This is a corporate application that I installed in my environment. The application comes with it's own out-of-the-box REST API, but I'm looking for a way to create my own custom API leveraging the existing one. The reason I want to create a custom API is because of all the customizations that have been made to the underlying database. I'm looking at using Node.js and the Express application framework to create the custom API, but all the use cases I've seen for this are for creating new APIs from scratch. I guess my question would be, how can I integrate my existing web services API into a Node.js (Express) set up. My existing web services API runs an Apache Tomcat web service. This publishes the existing web service endpoints in a format like this:
http://://?fields=,...
I'm looking for tips, pointers or something that can point me in the right direction. If there are any alternate (better) solutions available aside from Node.js (Express) I am open to exploring that as well.
I'm developing a simple site consisting of an Angular frontend and a simple NodeJS backend. I currently see 3 ways to setup the project:
have 1 Web App to serve the static HTML and 1 Web App for the NodeJS backend
serve both REST API and static files using the same NodeJS instance
I read about virtual directories for Azure Web Apps, but wasn't able to find appropriate documentation. Is that even a viable solution?
What's the standard setup to use for Azure? Is there any in-depth documentation I missed?
I would say that this is a type of question for which it is difficult to get an answer, because someone could write an entire book on this topic and a lot of aspects are a matter of personal preferences, approaches and so on.
Before I try to attempt a first answer I would like to point out that I am not familiar with Node.js at all, but I am fairly familiar with Azure AppService and ASP.Net Core MVC.
There is no standard setup in Azure AppService (websites in this case) and in fact all the 3 options that you mentioned are valid. Based on my expperience with Azure AppService I would say that option one is suitable when you have a publicly available API. In that case you could also register your API with Azure Management API.
The second option is, in my opinion, best suitable when your frontend is the only consumer of your API.
The third option is not that common, but 100% possible. Here is a very good article on how to set virtual directories up and how to deploy an application to them using Visual Studio. I am not sure how this would be done exactly with the tooling at your disposal, but conceptually it should be possible. However, deploying NODE.js projects in virtual directories could cause some problems you should be prepared for. More information here.
I would however stick with what I said in the start: I would deploy both backend and frontend to the same web app if my Angular application is the only consumer of the API and I would deploy to 2 different web apps if my API was public.
I'm curious what other might think in this regard.
We have been using Azure Easy API using Node.js for some of the mobile apps. Given the fact that the mobile apps stay in different versions, we need to have different versions of the same API available. In such a case, how do we carry out the versioning? Is there any azure documentation that someone can point to? thanks in advance.
There is no documentation on versioning for Azure Mobile Apps. Internally, we use the ZUMO-API-VERSION to switch between protocols. If you are using EasyAPI, then that is designed for the most simple cases - versioning of your API is not supported.
Instead of using EasyAPI, the site underneath is just a Node.js application. Download it (via Kudu), check it into source code, and use regular old Express routing for your API. You can then version it any which way you like.
If you need further information on versioning WebAPIs, I recommend Designing Evolvable Web APIs with ASP.NET - it's on ASP.NET, but covers a lot of the required semantics for versioning within it.
I have a bit of challenge. Knowing only the basic URL for the sharepoint installation, can I get a list of the site collections that have been created using only the basic web services that are installed?
Using the Webs web service or the SiteData web service I've been able to get information on the default site collection that's at the base URL (http://MySharePointServer/). I can also get a full list of sites below the site collection and a description of the site collection itself but I can't seem to get any info on the other site collections under the same web application.
Any help would be appreciated, I thought it would be a piece of cake to get the info.
Unfortunately, no. That functionality isn't available from the out-of-the-box web services. The only option that might work is using the Search Web Service (I'm not familiar enough with it to know).
This walkthrough describes how to add your own custom web services to the product. I strongly recommend this approach as it's very likely there will be other missing functionality you will need to add - if not now, in the near future.