Overview

Table of contents

Overview

Below, a schematic outline is given on how Blueriq makes this possible.

In Studio, models are creates and maintained. The runtime executes models, which are displayed in a browser, an app or an application. The same diagram, but with more detail is shown below.

Components

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

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. With this setup changes in Studio are directly reflected in the Runtime, which enables rapid application development. Once an application is ready for test, the Publisher is used to transfer the application from the Development environment to the Test(/Acceptation/Production) environment. On this environment only the Runtime is deployed to run the application.

Studio

A closer look at the Studio shows that there are two layers internally:

• Studio server
• Studio client

The Studio server provides the core functionality and is responsible for maintaining the Studio repository. It provides a management service, via SOAP, which handles the connections to the Publisher, Composer and the development plug-in on the Runtime.

The interface elements (the Studio screens) are handled by the client. This client is built with XBAP technology which requires Internet Explorer to run.

Both Studio layers run on top of an IIS application server.

Key features of the Studio:

• Complete revision control
• Work with external and internal libraries
• Multilingual elements
• User and access management
• Working with multiple projects

Blueriq Studio provides a complete guide on the Studio.

Runtime

The Runtime is the execution platform that executes the application. The Runtime runs on top of an application server, e.g. Tomcat, JBoss, Websphere (all Java) or IIS (.Net). On the next layer the Blueriq 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 plug-ins are available, e.g. Dashboard, CMIS, which provide specific functionality.

There are several options to load an application from the studio into the runtime:

1. Via a direct link between studio and runtime

2. Via a generated export on the file system (by default in aquima.home/exports)

3. Via a database with the use of the publisher

The Runtime runs on Java or .Net and works with modern browsers.

Key features of the Runtime:

• Customizable dashboard to run applications
• Variety of plug-ins to extend functionality
• Different APIs to further extend and customize functionality

Blueriq Runtime provides a complete guide on the Runtime.

Publisher

The Publisher is a standalone application. It is connected to Studio to retrieve applications. An application can be published from Studio to the Publisher database. An environment with a Runtime can connect to this database and start a published application through the Publisher Client, which runs on top of Runtime.

Key features of the publisher:

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

More information on the Publisher can be found here: Blueriq Standalone Publisher.

Composer

The Composer allows editing simple text elements of an application at runtime, such as a question text or a button label. The changes are directly visible. In order to maintain the changes, they are stored in the Studio repository by the Composer. The Composer is a plugin which runs on top of the Runtime. This plug-in has a connection to the Studio to store the changes that are made with the Composer.

More information on the Composer can be found here: Blueriq Composer.