![]() |
VOOZH | about |
In this article, we will guide you through the process of utilizing wizards within Visual Studio to seamlessly integrate the CData ADO.NET Provider for Elasticsearch into a basic MVC (Model, View, Controller) project.
Accessing and integrating live data from Elasticsearch has never been easier with CData. Customers rely on CData connectivity to:
Users frequently integrate Elasticsearch data with analytics tools such as Crystal Reports, Power BI, and Excel, and leverage our tools to enable a single, federated access layer to all of their data sources, including Elasticsearch.
For more information on CData's Elasticsearch solutions, check out our Knowledge Base article: CData Elasticsearch Driver Features & Differentiators.
Follow the steps below to save connection properties and map tables to entities in the data model.
If you are using Entity Framework 6, you will need to take the preliminary step of registering the Elasticsearch Entity Framework provider for your project. See the "LINQ and Entity Framework" chapter in the help documentation for a guide.
Note that MVC 3 scaffolding and MVC 4 scaffolding do not support Entity Framework 6. You can use your scaffolding with Entity Framework 6 by upgrading to the latest version of MVC.Specify the required connection string properties.
Set the Server and Port connection properties to connect. To authenticate, set the User and Password properties, PKI (public key infrastructure) properties, or both. To use PKI, set the SSLClientCert, SSLClientCertType, SSLClientCertSubject, and SSLClientCertPassword properties.
The data provider uses X-Pack Security for TLS/SSL and authentication. To connect over TLS/SSL, prefix the Server value with 'https://'. Note: TLS/SSL and client authentication must be enabled on X-Pack to use PKI.
Once the data provider is connected, X-Pack will then perform user authentication and grant role permissions based on the realms you have configured.
A typical connection string is below:
Server=127.0.0.1;Port=9200;User=admin;Password=123456;๐ The connection for the model. (QuickBooks is shown.)
Name the connection and select whether to include sensitive information, such as connection credentials, in the connection string. For simplicity, this example saves sensitive information in Web.config. The connection settings are saved as ElasticsearchEntities.
๐ The completed connection step in the ADO.NET Entity Data Model wizard. (A QuickBooks connection is shown.)Once you've established the model and completed the project build, you can employ ASP.NET Scaffolding wizards to generate both the controller and the views.
Download a free trial of the Elasticsearch Data Provider to get started:
Download NowLearn more:
๐ Elasticsearch IconRapidly create and deploy powerful .NET applications that integrate with Elasticsearch.