![]() |
VOOZH | about |
The CData ADO.NET Provider for AlloyDB enables you to rapidly develop service-oriented applications using the Windows Communication Foundation (WCF) framework, providing AlloyDB data data to OData consumers. This article guides you through creating an entity data model for connectivity and a WCF Data Service to expose OData services. You can then consume the feed with various OData clients, such as Power Pivot or applications using the CData ADO.NET Provider for OData.
Follow the steps below to create a WCF service application that will provide connectivity to AlloyDB data via OData.
Use the Package Manager Console in Visual Studio to install the latest version of Entity Framework. Run the following command to download and install Entity Framework automatically:
Install-Package EntityFramework
<configuration> ... <entityFramework> <providers> ... <provider invariantName="System.Data.CData.AlloyDB" type="System.Data.CData.AlloyDB.AlloyDBProviderServices, System.Data.CData.AlloyDB.Entities.EF6" /> </providers> </entityFramework> </configuration>
In the Connection properties dialog, select the CData AlloyDB Data Source and enter the necessary credentials.
A typical connection string is below:
User=alloydb;Password=admin;Database=alloydb;Server=127.0.0.1;Port=5432
The following connection properties are usually required in order to connect to AlloyDB.
You can also optionally set the following:
Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.
No further action is required to leverage Standard Authentication to connect.
There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.
Find instructions about authentication setup on the AlloyDB Server here.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.
The authentication with Kerberos is initiated by AlloyDB Server when the β is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos.
π Required connection properties, specified in the Add Connection dialog. (Salesforce is shown.)Specify the data source class and configure access to the new WCF Data Service. In the example below, the Access Rule for the entities is set to All. This means that any user will be able to read and modify data.
using System;
using System.Collections.Generic;
using System.Data.Services;
using System.Data.Services.Common;
using System.Linq;
using System.ServiceModel.Web;
using System.Web;
namespace AlloyDBService{
public class AlloyDBDataService : DataService<AlloyDBEntities> {
public static void InitializeService(DataServiceConfiguration config) {
config.SetEntitySetAccessRule("*", EntitySetRights.All);
config.DataServiceBehavior.MaxProtocolVersion = DataServiceProtocolVersion.V3;
}
}
}
You can now use the service from any OData client; for example, Excel Power Pivot.
Download a free trial of the AlloyDB Data Provider to get started:
Download NowLearn more:
π AlloyDB IconRapidly create and deploy powerful .NET applications that integrate with AlloyDB.