Try OpenEdge Now
skip to main content
Guide for New Developers
Understanding OpenEdge Reference Architecture : OpenEdge Reference Architecture design principles and its usage

OpenEdge Reference Architecture design principles and its usage

The OpenEdge Reference Architecture (OERA) is intended to provide high-level design guidance focused on building modern competitive applications. OERA defines the general functional categories of components that comprise an application. OERA is generally used as a high-level blueprint for developing OpenEdge service-oriented business applications.
The following diagram shows the high-level elements of the Architecture:
Each layer of OERA consists of distinct components that have specific characteristics, roles, and responsibilities. In addition, OERA provides guidelines about how each of the architectural components interact. The Reference architecture makes it possible for application developers to solve business problems efficiently, effectively, and flexibly.
*The Data Access Layers manage the retrieval of data from either Managed Data Stores such as the OpenEdge RDBMS, or Unmanaged Data Stores such as flat files and XML documents, and the writing of data updates back to those data stores.
*The Business Components Layer holds the business logic that is central to the application’s behavior and value, along with application elements that provide general services to the application, such as security, auditing, and translation.
*The Presentation Layer manages the user interface and the communicating of data and logic between the application’s users and the business logic.
*The Enterprise Services Layer manages communication to other applications and services outside the bounds of the target application, to allow the application to be part of a wider enterprise.
* Recommended order for an OERA design