Page History
Blueriq consists of the following components:
- StudioEncore: create and maintain an application
- Runtime: execute an application
- Model Analyzer: gives an objective judgment about the quality of an application
- Publisher: publish an application from one environment to another
...
Excerpt |
---|
Below the preferred deployment of Blueriq is outlined. An application is developed with StudioEncore, which runs on the Development environment. This environment also contains a Runtime which is linked to the StudioEncore. With this setup changes in Studio Encore 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. |
Blueriq
...
Encore
A closer look at the Studio Encore shows that there are two layers internally:
- Studio server
- Encore
...
- providing the core functionality and is responsible for maintaining the
...
- repository containing the model. It provides a management service, via SOAP, which handles the connections to the Publisher,
...
- Model Analyzer and the development plug-in on the Runtime.
...
- Encore, in which the interface elements (the screens) are handled
...
- . This frontend requires
...
- Chrome, Edge, or
...
- Firefox to run.
Both Studio layers run on top of an IIS application server.
Key features of the Studiodevelopment environment:
- Complete revision control
- Work with external and internal libraries
- Multilingual elements
- User and access management
- Working with multiple projects
Blueriq StudioEncore provides a complete guide on the StudioEncore.
Blueriq 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. 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/Encore into the Runtime:
Via a direct link between the Studio server and Runtime
Via a generated export on the file system (by default in
Include Page _ConfigLocation _ConfigLocation /exports
)- Via the Publisher
The Runtime runs on Java or .Net and works with modern browsers.
...
Blueriq Runtime provides a complete guide on the Runtime.
Blueriq
...
Model Analyzer
Blueriq Model Analyzer gives an objective judgment about the quality of Blueriq models and lift these models to a higher level.
More information on the Blueriq Model Analyzer can be found here: Blueriq Model Analyzer ➔.
Blueriq offers an App Builder, enabling the deployment of a Blueriq application as an app. See Blueriq App Builder [OUT OF PRODUCTION]
Blueriq Publisher
The Publisher is a standalone application. It is connected to the Studio server to retrieve applications. An application can be published from the Studio server 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 Publisher ➔.
Blueriq Control Center
The Blueriq Control Center is the linking pin between multiple Blueriq Studios and multiple Blueriq Runtimes. Every studio can be connected to the Control Center by giving the connection a name and by using the management service.
To be able to publish the project(s) to a runtime, the Blueriq Control Center currently uses the Blueriq Publisher.
Blueriq Model Analyzer
Blueriq Model Analyzer gives an objective judgment about the quality of Blueriq models and lift these models to a higher level.