Tag Archives: OData

Tutorial: Powering Salesforce Lightning Connect with MongoDB

Tutorial: Powering Salesforce Lightning Connect with MongoDB
// Kogonuso
By Bryan Leboff

One of the more powerful new features in Salesforce (GA Winter ‘15) is the ability to create external objects from external data sources using Lightning Connect. For the most part these external objects act in the same way as a custom object (though there are some limitations I will note at the end). Lightning Connect helps solve several issues commonly faced by organizations that want to present data in Salesforce, but do not necessarily want to store it within Salesforce. This could be to reduce integration complexity or concerns over security or performance. To get started all you need is a data store exposed via an OData 2.0 endpoint, and in this blog I will show you how to set one up that uses MongoDB as a backend.

New Features in ASP.NET Web API 2

We can say there are mainly 5 new features are available in Web API 2. Attribute Routing According to convention-based routing, Web API 2 now supports attribute routing as well. In case of convention-based routing, we can define multiple route templates. When a request comes, it will be matched against already defined route templates, and […]


SMP 3.0 : REST API Application Development

via SMP 3.0 : REST API Application Development | SCN.

New release of SAP Mobile Platform 3.0. We got many approaches to develop a mobile application like Kapsel  app development, native OData based app, REST API based app. From SUP 2.2 onwards, this mobile platform provides REST APIs which enable standard HTTP client apps running in any platform to access platform REST services. This platform provides different functionality like

  1. Management and monitoring the apps
  2. Native push notification like APNS , BES, GCM, WNS, MPNS

There is a proper procedure to get start with. First we have to register a client application with proper device information. Once registration is successful, we have follow REST API method to retrieve and update the application.

How to create a SAP Fiori app using an EDMX file?

via Promoleaf: How to create a SAP Fiori app using an EDMX file?.

This post will show you how to create a Fiori app with no backend system but using an EDMX file which contains the model of the OData service and could leverage SAP Web IDE mock service to test the application.

This kind of approach is useful in that case when backend is not ready (or no connectivity to backend system) and development for frontend and backend is done in parallel.

OData server on NodeJS

via OData server on node.js.

At the very beginning when I started to work on jsreport I decided to give it a standard based API. The decision was based on the fact I didn’t want to design my own API syntax for doing queries like give me an entity by name, give my top five last modified entities or give me just entity ids. For this kind of requests OData has already very nice syntax with bunch of clients in bunch of languages so the work for the consumers is very simple. The other stuff what OData provides like batching requests or entity relationships is rather too much for me but the plain queries are very nice so why not to use it.

I quickly found jaydata library which provides JavaScript OData client as well as server libraries. It was looking great at the first glance, but unfortunately it was a huge pain for me to use it over a year. The mongodb based odata server it provides is super slow. It for example creates a complete new mongo client with new connection pool for every request. The client provides a nice unit of work pattern but it is something what I don’t need in the browser and it just makes troubles. The jaydata team didn’t answer any of my questions about the mongo server so I was forced to fork jaydata and fix or workaround very often. Finally I decided to abandon jaydata and write my own OData server. I took me couple of weeks but now it’s here, with free MIT license, ready for you.

The project is stored in github repository node-simple-odata-server

How to consume SQL Spatial Data with Web API V2.2 for OData V4

via How to consume SQL Spatial Data with Web API V2.2 for OData V4 – OData Team – Site Home – MSDN Blogs.

Today, along with the increasing demands of Location-Based Services (LBS), it becomes more and more important to provide functionalities on SQL Spatial Data through a unique, robust and scalable service based on a standard protocol.

This post is intended to give a tutorial about how to consume the SQL Spatial Data through EF & Web API V2.2 for OData V4. The method in this blog is similar to the method in How to use SQL Spatial Data with WCF ODATA Spatial, but the latter is based on WCF Data service. However, for more information about how to create a simple OData V4 service based on Web API, please refer to Create an OData v4 Endpoint Using ASP.NET Web API 2.2.

Ok, let’s get started.

A turn-key library for building RESTful services

via OData/RESTier · GitHub.

RESTier is a RESTful API development framework for building standardized, OData V4 based REST services on .NET. It can be seen as a middle-ware on top of Web API OData. RESTier can provide convenience to bootstrap an OData service and add business logic like what WCF Data Services does as well as flexibily and easy customization like what Web API OData does.

Please be noted that currently RESTier is still a preview version.