The JSDO is a client side typescript library for Progress Data Object Services published by Progress Software Corporation. Its purpose is to provide an easy to understand API for querying, creating, updating and deleting Progress Data Objects as well as invoke server side business logic. The JSDO is a free and open-source full-featured implementation that can be used in web, mobile web and hybrid mobile apps.
Progress® Data Objects in an OpenEdge business application can be accessed using the JSDO on the client. For more information, see the Overview of Progress Data Objects, Services and Catalogs.
This is an npm package. This means that node and npm need to be installed to use it.
To use the JSDO, you normally will simply install it from the public NPM registry via an npm install. You'll need to select a JSDO package depending on your environment:
# For vanilla JS, e.g. running it in a browser:
npm install @progress/jsdo-core
# For usage with node:
npm install @progress/jsdo-node
# For usage with Angular:
npm install @progress/jsdo-angular
# For usage with Nativescript:
npm install @progress/jsdo-nativescript
If you want to add changes and build packages yourself from this repository, you will need to use the scripts in package.json. The package.json in the root folder corresponds to the @progress/jsdo-core package.
Here is a quick overview of the npm scripts:
npm install
This installs the necessary dependencies that the JSDO has and needs to be run at least once.
npm run build:jsdo
This creates a
buildfolder and produces in it aprogress.jsdo.jsfile that can be used either via including it in a<script>tag or via aprogress = require('/path/to/build/progress.jsdo.js').progress;in your Node app.
npm run test
This runs the
build:jsdoscript and then runs the Mocha tests found in thetestfolder. This can also be run manually by installing Mocha on your environment and then runningmocha --recursivein the JSDO folder.
npm run lint
This runs
eslinton the JSDO source files.
| JSDO version | OpenEdge version |
|---|---|
| 6.0.1 | 11.7.x, 12.0.x |
You can download a copy of the full JSDO to a zip file.
| Source File | Purpose |
|---|---|
| progress.js | JSDO core |
| progress.session.js | JSDO session management |
| progress.util.js | Helper classes for the JSDO |
| progress.data.kendo.js | Kendo UI DataSource for the JSDO |
| auth/progress.auth.js | JSDO authentication provider |
| auth/progress.auth.basic.js | JSDO authentication provider (BASIC auth) |
| auth/progress.auth.form.js | JSDO authentication provider (FORM-based auth) |
| auth/progress.auth.sso.js | JSDO authentication provider (SSO auth) |
| Lib File | Purpose |
|---|---|
| progress.all.js | The JSDO plus the Kendo UI DataSource for JSDO |
| progress.all.min.js | The JSDO plus the Kendo UI DataSource for JSDO minified for deployment |
| progress.jsdo.js | The JSDO core components (JSDO, Session, Util classes) |
| progress.jsdo.min.js | The JSDO core components (JSDO, Session, Util classes) minified for deployment |
The JSDO can be used by hybrid mobile apps, mobile web apps and web browser apps to access OpenEdge and Rollbase servers. Other implementations include a client in a mobile Hybrid App (a variation of the browser client), a Telerik® NativeScript client, a Node.js server, and a Java server. The JSDO has successfully been used with servers other than OpenEdge such as Node.js to export data created / aggregated in Modulus™ to a Progress® Rollbase Application.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.