Page History

Introduction

Blueriq consists of the following components:

• Studio: create and maintain an application
• Runtime: execute an application
• Publisher: publish an application from one environment to another
• Composer

The purpose of the studio is to create and maintain an application. Creating an application consists of creating a workflow, the user interaction and the domain model. The studio typically runs on a development environment.

The goal of the runtime is to execute an application. The runtime is accessed via a browser. In the default configuration a user can specify which flow in which project should be started. It is also possible to define the language and the style. Each environment, e.g. development, test, acceptation and production (DTAP), runs its own runtime.

The publisher is responsible for publishing an application from one environment to another environment. It is the control room

With the composer it is possible to perform some changes to an existing application at runtime.

• : change simple text elements of an application at runtime

Below the preferred deployment of Blueriq is outlined. An application is developed with Studio, which runs on the Development environment. This environment also contains a Runtime which is linked to the Studio. This allows changes in Studio to be directly reflected in the Runtime, which enables rapid application development.

The following figure shows the preferred setup for DTAP environments, where the Runtime is linked to the Studio on the Development environment, which allows users to test changes made in Studio directly in the Runtime. The Publisher is used to transfer the application to the following environments (TAP).

Image Added

Interaction

The previously described components interact with each other as depicted in the next diagram. Note that the composer actually is a plugin which runs on the runtime.

...

Working with Runtime provides a complete guide on the Runtime.

...

The following figure shows the preferred setup for DTAP environments, where the Runtime is linked to the Studio on the Development environment, which allows users to test changes made in Studio directly in the Runtime. The

Publisher

...

Key features of the publisher:

• 4 eyes principle
• Select a tag/revision to publish
• Administration of published/unpublished applications

...