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. This allows With this setup changes in Studio to be are 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 Once an application is ready for test, the Publisher is used to transfer the application from the Development environment to the following environments (TAP).
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.
Test(/Acceptation/Production) environment. On this environment only the Runtime is deployed to run the application.
An application which is created in studio can be tested directly in the runtime via the development plugin (typically only available on the development environment). The publisher can transfer it to a seperate database which contains all published models. Each runtime will check this database for the correct application and will execute it. By using the composer plugin it is possible to make some changes on the runtime in the application (which runs in studio).
Studio
A closer look at the Studio shows that there are two layers internally:
...
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 development plugin 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.
...
Working with Studio provides a complete guide on the Studio.
Runtime
The runtime 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.
Key features of the publisher:
...
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.
More information on the Composer can be found here: Blueriq Composer.
Overview
Content Tools