Operate a modular framework

Framework overview

Leverage your existing development skills with a platform that is based on open standards. Use the engine behind the edoras one platform as a Java framework for any type of work-related solution.

Use it standalone or even embed it into your own application stack. Benefit from the combination of cases, processes, tasks and content on a single, light-weight infrastructure. Easily extend the framework through its well designed extension points, listeners and providers or just simply benefit from its simple APIs.

null

Embed it into a larger application

  • Use the engine behind the edoras one platform as a java framework for any type of work-related solution
  • Easily extend the framework through its well designed extension points, listeners and providers or just simply benefit from its simple APIs.
null

Light-weight infrastructure

  • Benefit from the combination of cases, processes, tasks and content on a single, light-weight infrastructure
  • Create ad-hoc tasks, processes; simply create and manage work items through a single framework
null

Extend a modular architecture

  • An extensible framework integrates loosely coupled and pluggable building blocks
  • Apply specific domain objects, extend or exchange existing providers and even use more than one provider at the same time.
null

Based on open standards

  • Leverage your existing development skills – Standards are a pre-requisite for communication, leveraging know-how and working on a common system
  • Combine native BPMN 2.0 processes running on the embedded Activiti engine with the adaptive case management or any type of content

Architecture overview edoras one

edorasware ribbon

Use the engine behind the edoras one platform as a Java framework for any type of work-related solution. Use it standalone or even embed it into your own application stack. Benefit from the combination of cases, processes, tasks and content on a single, light-weight infrastructure. Easily extend the framework through its well designed extension points, listeners and providers or just simply benefit from its simple APIs.

edoras one architecture picture

Client / Web Browser

edoras one is fully web-based and only needs a web browser to work with it. Even the graphical modeling environment is fully running within the browser without the need of a plugin. The client part is based on HTML5 / CSS3 and uses a client side model-view-controller framework (AngularJS) to abstract the data from the view and the controllers.

Web Container

edoras one runs in a Java web-compliant container such as Tomcat. You can also deploy edoras one into a JEE compliant server like JBoss, although the JEE parts of the container are not necessarily needed but are integrated with, if available.

RDBMS

All information within edoras one is stored transactionally in an RDBMS. The following database systems are supported by edoras one: Oracle, MS SQL Server, MySQL, PostgreSQL and H2.

Content Repository

File-based content or large unstructured content is stored within the content repository of edoras one. There is a simple, built-in repository supporting a light-weight content storage system with built-in versioning capabilities. The content can also be stored in an external system like Alfresco, Sharepoint or any other system.

Search Infrastructure

edoras one supports a full text search integration, so each work item is searchable as well as its content. The search can be integrated with the featured Java based query API or through the search REST endpoint, supporting full text search as well as structured search

Work Item Infrastructure

The core of edoras one is its work item infrastructure, the work management framework. Please follow this link for more information about work items. 

Modeling Infrastructure

Part of edoras one is the modeling infrastructure. It is embedded into edoras one for a smooth modeling experience, deploying directly into edoras framework and runtime experience. For each supported type of model there is an appropriate provider interpreting that model. Process models for instance are modeled with the BPMN 2.0 standard and executed by the process provider, based on the Activiti process engine. The form models are stored in JSON and rendered through the form engine in the client.

REST API

edoras one supports a REST API based on the JSON data protocol. The edoras one client actually uses the same API as well for all of its features. Additionally, the REST API can be used for any kind of integration with edoras one.

Extensions / Listeners / Providers

There are a lot of well designed extension points in edoras gear that can be used to extend the work item platform in many ways.

Client / Server Communication

The client / server communication is based on the REST API supported by the edoras one backend services. JSON is used for the data in the requests and HTTP / HTTPS as the transfer protocol. edoras one can be integrated with SSO infrastructures as well.