Useful documents to be found in the OpenEdge Development Group

 

Making HTTP REST Requests with OpenEdge.NET

https://community.progress.com/community_groups/openedge_development/m/documents/1800.aspx

 

Using the JSDO with Kendo UI - Whitepaper

Kendo UI from Progress Telerik is a JavaScript framework that can be used to build web and mobile apps using HTML5 and JavaScript. It provides a very powerful set of UI widgets (controls) that can be bound to a data source.

Kendo UI widgets use the Kendo UI DataSource to access local and remote data. The Kendo UI DataSource is an abstraction on top of both local data (arrays) and remote data (HTTP endpoints) that makes it much easier to request data, fill widgets with data, and then make and track changes to that data. The transport property in the Kendo UI DataSource configures how to perform the CRUD operations for the DataSource by defining the corresponding properties: create, read, update, and destroy.

Kendo UI has been enhanced to support JSDO as a DataSource as of May 2015. The OpenEdge backend can be accessed through the Kendo UI DataSource using the same architecture used for Mobile app development in OpenEdge 11.2 and greater, the JSDO.

The Progress JavaScript Data Object (JSDO) provides support for a complex data model and API to manipulate data while maintaining data integrity. The JSDO catalog defines the logical schema and mapping to a remote data source. The catalog also defines an API to invoke remote business logic in addition to simple CRUD operations. The JSDO is designed to work with any Web / JavaScript framework. Similarly Kendo UI is designed to provide the best UI regardless of backend provider. Naturally the two work great together.

This whitepaper describes how to use the new JSDO dialect of the Kendo UI DataSource with Kendo UI to access data and business logic on an OpenEdge AppServer.

https://community.progress.com/community_groups/openedge_development/m/documents/2135.aspx

 


Generic JMS Adapter for Progress OpenEdge 11.5.1

Progress OpenEdge provides a generic Java Message Service (JMS) adapter for messaging. This generic JMS adapter can operate with any JMS-compliant vendor, for example, SonicMQ, IBM WebSphereMQ, and ActiveMQ

https://community.progress.com/community_groups/openedge_development/m/documents/1986.aspx

 

Making a Progress OpenEdge Application Available as a REST Service

In this video, you will learn how to make a Progress OpenEdge application available as a REST service that can be accessed by any REST client.

https://community.progress.com/community_groups/openedge_development/m/documents/2076.aspx