Integration Model

Well-integrated information and processes lead to better user experiences, organizational efficiencies and overall performance improvements. If information is spread throughout different systems, access to it is a constant challenge -- for your employees, as well as your customers. The complex IT environments that exist in enterprise organizations necessitate a comprehensive approach to integration. Our approach leverages Service Oriented Architecture (SOA) fundamentals to provide a seamless integration of Progress Rollbase data and functionality with other systems and applications.

Progress Rollbase provides a flexible integration model via fine-grained SOAP, REST, and AJAX APIs as well as a growing number of integration connectors. In addition, built-in integration with Google Apps (GMail, Calendar and Docs) provides a way to sync Progress Rollbase application data with Google tools including the ability to use GMail as the outbound email mechanism. More on Google Apps integration...

AJAX API

The Progress Rollbase AJAX API is designed for extending application pages with custom dynamic behavior. This API can be used by client-side components, such as those created in Flex or JavaScript, and field-level event handlers to retrieve and modify data, and use results to dynamically update the client user interface. The AJAX API is subject to the same permissions and access control restrictions as the standard Rollbase user interface, and SOAP/REST Web APIs. For more information see Chapter 15 of Rollbase In Action

SQL Query API

The Rollbase SQL Query API allows both client-side (Script and Template components, page layouts, and field event-handling code) as well as server-side (formulas, conditions, validations, reports, etc) to perform SQL queries to retrieve specific data necessary for the task at hand. The SQL Query API is subject to the same permissions and access control restrictions as the standard Rollbase user interface, and SOAP/REST Web APIs. For more information see Chapter 15 of Rollbase In Action

REST API

The Rollbase REST API is designed to enable integration between the Rollbase platform and external systems via REST calls. The Rollbase REST API uses the same permissions mechanism as the standard Rollbase user interface. API users must have permission to view, create, update, or delete records in order to perform these actions via API calls. The SOAP API consists of standard CRUD (create, read, update, delete) methods as well as search, binary file upload/download methods for working with file and image fields, methods for working with relationships, and a method for retrieving a full XML representation of an Object definition and all of its components. For more information see Chapter 15 of Rollbase In Action.

SOAP API

The Rollbase SOAP API is designed to enable integration between the Rollbase platform and external systems via standards-based SOAP calls. The Rollbase SOAP API uses the same permissions mechanism as the standard Rollbase user interface. API users must have permission to view, create, update, or delete records in order to perform these actions via API calls. For more information see Chapter 15 of Rollbase In Action

JavaScript Data Objects

JavaScript Data Objects (JSDO) provides simplified integration between Progress Rollbase and Progress OpenEdge back-end data.

Google Apps Integration

Any application created with Progress Rollbase can automatically use Gmail to send email, synchronize any event information with Google Calendar, and export application data directly into Google Docs & Spreadsheets, increasing the productivity of any Progress Rollbase and Google Apps users. More...

Integration Connectors

In addition to Web APIs, Progress Rollbase also provides a growing library of pre-built integration connectors. For example, an FTP backup connector allows you to periodically back up all of your Rollbase data and automatically send it to a secure FTP server. A Rollbase to Rollbase connector allows you to synchronize data between different Progress Rollbase accounts.