A data provider defines a single data service and one or more data sources that represent tables provided for access by that data service, which you can bind to views. You can specify a data provider as one of the following:
Progress Data Provider — Represents a single point of authorization with read-only or read-write access to an OpenEdge or Rollbase Data Object Service. This single point of authorization is the URI of a server web application that supports a specified Data Object Service. Each Data Object Service provides access to one or more Data Object resources that provide the tables that define data sources for the data provider. Each Data Object Service is defined by a Data Service Catalog, which is a JSON file on the web server that you can specify using its URI, and which specifies the tables for the Data Object Service. This data provider definition also includes the authentication model required to authenticate access to the data server (web application) that it supports, and which you must specify from the following options:
Anonymous
Basic
Form
OData Provider — Represents a single point of authorization with read-write access to an OData service. This single point of authorization is the URI of an OData service root. An OData service provides access to one or more data sources and their definitions.
Generic REST Provider — Represents a single point of authorization with read-write access to a generic REST service. This single point of authorization is the URI of a server web application that supports a specified REST service.
For a Progress Data or OData Provider, you can create and define data sources that you want the data provider to provide, either automatically, when you first create the data provider, or manually, by adding data sources to the data provider after you create it.
You can also create multiple data providers, especially if you need to access Progress Data Object Services hosted by multiple web applications.