Page History

...

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:

...

Working with Studio provides a complete guide on the Studio.

Runtime

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 plugins are available, e.g. Dashboard, CMIS, which provide specific functionality.

...

Working with Runtime provides a complete guide on the Runtime.

Publisher

The Publisher is a standalone applicatoin. 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.

...

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 plugin has a connection to the Studio to store the changes that are made with the Composer.

...