Architecture

Introduction

Blueriq consists of the following components:

• Studio
• Runtime
• Publisher
• Composer

In studio

Runtime

Publisher

Composer

Interaction

These components interact with each other as depicted in the next diagram.

A model which is created in studio can be directly tested in the runtime via the development plugin (only available on the develoment environment). The same model can be distributed to another environment via the publisher. The publisher puts the specified model in the correct database and the runtime uses this database to execute the model.

Studio

The main purpose of the studio is to be able to create and maintain an application. The studio consists of two layers:

• studio server
• studio client

The studio server provides the core functionality and is responsible for maintaining the studio repository. It also provides a management service (via Soap), which todo.

The client handles all user interface elements (the studio screen). Both layers run on top of an ISS application server. The studio client is built with XBAP technology and runs only in Internet Explorer.

Key features of the studio:

• Revision control of elements
• External and internal libraries
• Multilingual elements
• Process modelling

Runtime

The main purpose of the runtime is to execute an application. The runtime runs on top of an application server, e.g. Tomcat, JBoss, Websphere or ISS. On the next level the SDK is available which contains the Blueriq engines. The webapp is located on the next layer, which handles all web interaction. On top of the stack a number of plugins are available, e.g. Dashboard, CMIS, which serve special functionality.

The runtime runs on java or .Net and is almost browser independent.

Key features of the runtime:

• todo

Publisher

The main purpose of the publisher is to publish an application from one environment to another environment.

Via the connection with studio, the publisher can pick up the actual studio application from the development environment and publish it to a central database. This central database can be accessed by the runtimes of different environments, e.g. test, acceptation or production environment. See also the following figure. This publisher is available in Java and .Net.

Key features of the publisher:

• 4 eyes principle
• Select a tag/revision to publish
• Well-organized overview

Composer

With the composer it is possible to edit parts in an application when running in runtime.