Page History

Introduction

Blueriq consists of the following main components:

• Studio
• Runtime
• Publisher
• Composer

In studio

Runtime

Publisher

Composer

Interaction

These components How they interact with each other is as depicted in the following 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.

...

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

...

The main purpose of the runtime is to execute a modelan 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 main purpose of the publisher is to publish a model an application from one environment to another environment.

Via the connection with studio, the publisher can pick up the actual studio model 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.

...