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:
...
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.
...
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:
...
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:
...
Overview
Content Tools