Provide OData Services of EnterpriseDB Data from a WCF Application

Ready to get started?

Download for a free trial:

Download Now

Learn more:

EnterpriseDB ADO.NET Provider

Rapidly create and deploy powerful .NET applications that integrate with EnterpriseDB.



This article shows how to publish an OData feed of EnterpriseDB data by creating a WCF Service Application.

The CData ADO.NET Provider for EnterpriseDB enables you to use the Windows Communication Foundation (WCF) framework to rapidly develop service-oriented applications that provide EnterpriseDB data to OData consumers. This article shows how to create an entity data model to provide the underlying connectivity to the EnterpriseDB data, as well as how to create a WCF Data Service to expose the OData service. You can then consume the feed with any OData client, for example, Power Pivot or an application that uses the CData ADO.NET Provider for OData.

Create the OData Service

Follow the steps below to create a WCF service application that will provide connectivity to EnterpriseDB data via OData.

  1. Open Visual Studio and create a new project. Select the WCF Service Application template.
  2. Delete the autogenerated IService.cs and Service1.svc.
  3. Install Entity Framework 6:

    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

  4. Register the Entity Framework provider:
    1. Add the following provider entry in the "providers" section of your App.config or Web.config file. This section should already exist if the Entity Framework installation was successful. <configuration> ... <entityFramework> <providers> ... <provider invariantName="System.Data.CData.EnterpriseDB" type="System.Data.CData.EnterpriseDB.EnterpriseDBProviderServices, System.Data.CData.EnterpriseDB.Entities.EF6" /> </providers> </entityFramework> </configuration>
    2. Add a reference to System.Data.CData.EnterpriseDB.Entities.dll, located in lib/4.0 in the installation directory.
    3. Build the project to complete the setup for using EF6.
  5. Click Project -> Add New Item -> ADO.NET Entity Data Model.
  6. In the Entity Data Model wizard that is displayed, select the 'EF Designer from Database' option.
  7. In the resulting Choose Your Connection dialog, click New Connection.
  8. In the Connection properties dialog, select the CData EnterpriseDB Data Source and enter the necessary credentials.

    A typical connection string is below:

    User=postgres;Password=admin;Database=postgres;Server=127.0.0.1;Port=5444

    The following connection properties are required in order to connect to data.

    • Server: The host name or IP of the server hosting the EnterpriseDB database.
    • Port: The port of the server hosting the EnterpriseDB database.

    You can also optionally set the following:

    • Database: The default database to connect to when connecting to the EnterpriseDB Server. If this is not set, the user's default database will be used.

    Connect Using Standard Authentication

    To authenticate using standard authentication, set the following:

    • User: The user which will be used to authenticate with the EnterpriseDB server.
    • Password: The password which will be used to authenticate with the EnterpriseDB server.

    Connect Using SSL Authentication

    You can leverage SSL authentication to connect to EnterpriseDB data via a secure session. Configure the following connection properties to connect to data:

    • SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
    • SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
    • SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
    • SSLClientCertType: The certificate type of the client store.
    • SSLServerCert: The certificate to be accepted from the server.

  9. Select EnterpriseDB tables and views that you want OData clients to access.
  10. Click Project -> Add New Item -> WCF Data Service.
  11. 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 EnterpriseDBService{ public class EnterpriseDBDataService : DataService<EnterpriseDBEntities> { public static void InitializeService(DataServiceConfiguration config) { config.SetEntitySetAccessRule("*", EntitySetRights.All); config.DataServiceBehavior.MaxProtocolVersion = DataServiceProtocolVersion.V3; } } }
  12. Run the project. Applications that support OData can now access the Salesforce data and reflect any changes. You can access the feed in your browser. The feed will resemble the following:

Consume the OData Service from Power Pivot

You can now use the service from any OData client; for example, Excel Power Pivot.

  1. Open Excel and click on the Power Pivot Window button.
  2. A new pop-up will appear. Select the option From Data Feeds.
  3. In the resulting Table Import Wizard, enter the OData URL. For example, http://localhost:12449/EnterpriseDBDataService.svc/.
  4. After connecting to the OData service, click the Next button at the bottom of the window.
  5. A table listing of the available tables will appear in the next window of the wizard. Select which tables you want to import and click Finish.
  6. Click Close to import the data in Power Pivot.