Overview

Blueriq consists of a number of main components, which are:

1. Studio
2. Runtime
3. Publisher

How they interact with each other is depicted in the following 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 model. 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. Both layers run on top of an ISS application server. The studio is built with XBAP technology and runs only in Internet Explorer.

Key features:

• revision control
• libraries
• multilingual

Runtime

The main purpose of the runtime is to execute a model. This runtime runs on top of an application server (Tomcat, JBoss, Websphere, Jetty or ISS). It consists of a number of plugins and the web application (the SDK, configuration, rendering and webservices). This web application runs on java or .Net and it is almost browser independent.

The main purpose of the monitor is to monitor forms. This component is an extension of the runtime for Websphere and JBoss.

The main purpose of the development plugin is to be able to

Publisher

The main purpose of the publisher is to publish a model from the development environment (D) to another environment (TAP).

This component is available in Java and .Net

features

4 eyes principle

Select a tag/revision to publish.

The studio is connected to the publisher. Via this link it is possible for the publisher to retreive the actual studio model. This model can be published to different databases. These databases tothether with their specific runtime serve the test environment, the acceptance environment and the production environment.