OData やSwagger などの標準化されたインターフェースを使って、CData API Server とADO.NET Provider for REST (もしくは200+ の他のADO.NET Providers) を組み合わせて、Logic Apps やMicrosoft Flow からREST へのデータ連携を実装できます。OData は、データへのリアルタイム連携を、Swagger はLogic Apps およびMicrosoft Flow のスキャッフォールディング、コード生成を可能にするほか、PowerApps でのスキャッフォールディングを可能にします。本記事では、Logic App のIFTTT ワークフローにREST を追加する方法を説明します。
Follow the steps below to begin producing secure and Swagger-enabled REST APIs:
The API Server runs on your own server. On Windows, you can deploy using the stand-alone server or IIS. On a Java servlet container, drop in the API Server WAR file. See the help documentation for more information and how-tos.
The API Server is also easy to deploy on Microsoft Azure, Amazon EC2, and Heroku.
After you deploy the API Server and the ADO.NET Provider for REST, provide authentication values and other connection properties by clicking Settings -> Connections and adding a new connection in the API Server administration console. You can then choose the entities you want to allow the API Server access to by clicking Settings -> Resources.
See the Getting Started chapter in the data provider documentation to authenticate to your data source: The data provider models REST APIs as bidirectional database tables and XML/JSON files as read-only views (local files, files stored on popular cloud services, and FTP servers). The major authentication schemes are supported, including HTTP Basic, Digest, NTLM, OAuth, and FTP. See the Getting Started chapter in the data provider documentation for authentication guides.
After setting the URI and providing any authentication values, set Format to "XML" or "JSON" and set DataModel to more closely match the data representation to the structure of your data.
The DataModel property is the controlling property over how your data is represented into tables and toggles the following basic configurations.
See the Modeling REST Data chapter for more information on configuring the relational representation. You will also find the sample data used in the following examples. The data includes entries for people, the cars they own, and various maintenance services performed on those cars.
You will also need to enable CORS and define the following sections on the Settings -> Server page. As an alternative, you can select the option to allow all domains without '*'.
After determining the OData services you want to produce, authorize users by clicking Settings -> Users. The API Server uses authtoken-based authentication and supports the major authentication schemes. You can authenticate as well as encrypt connections with SSL. Access can also be restricted by IP address; access is restricted to only the local machine by default.
For simplicity, we will allow the authtoken for API users to be passed in the URL. You will need to add a setting in the Application section of the settings.cfg file, located in the data directory. On Windows, this is the app_data subfolder in the application root. In the Java edition, the location of the data directory depends on your operation system:
[Application]
AllowAuthtokenInURL = true
You can use the API Server in a Logic App to create process flows around REST data. The HTTP + Swagger action provides a wizard to define the operations you want to execute to REST. The following steps below show how to retrieve REST data in a Logic App.
If your table has a column containing the creation date of a record, you can follow the steps below to write a function to check the column values for any new records. Otherwise, skip to the Create a Logic App section to send out emails to entities that match a filter.
To find new REST entities since a certain time, you can write a function that retrieves a datetime value for the start of the interval:
module.exports = function (context, data) {
var d = new Date();
d.setHours(d.getHours()-1);
// Response of the function to be used later.
context.res = {
body: {
start: d
}
};
context.done();
};
Follow the steps below to create a trigger that searches REST for results that match a filter. If you created the function above, you can search for objects that were created after the start of the interval returned.
http://MySite:MyPort/api.rsc/@MyAuthtoken/$swagger
Use the descriptions for each property to specify additional parameters such as the columns to retrieve, filters, etc. Below is an example filter:
[ personal.name.last ] eq 'Roberts'
The API Server returns the descriptions and other documentation in the swagger document. You can find more information on using the OData API and supported OData in the API Server help documentation.
To use the datetime value returned from the getInterval function, use the "ge" operator with a datetime column in the people table and select the Body parameter in the dialog. Note that quotes must be used to surround the datetime value.
Switch to Code View and modify the $filter expression to extract the property containing the start of the interval. Use the syntax '@{body('MyFunc')['MyProp']'.
"getAllAccount": {
"inputs": {
"method": "get",
"queries": {
"$filter": "CreatedDate ge '@{body('getInterval')['start']}'"
},
"uri": "https://MySite:MyPort/api.rsc/@MyAuthtoken/people"
}
You can now access REST as data sources and destinations in your workflows.
Follow the steps below to email a report with any new people entities.
Click Save and then click Run to send email notifications on any REST records created in the last hour.
