Page History

...

An application which is created in studio can be directly tested in directly in the runtime via the development plugin (typically only available on the develoment 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 Studio shows that there are two layers internally:

• studio Studio server
• studio Studio client

The studio Studio server provides the core functionality and is responsible for maintaining the studio Studio repository. It also provides a management service, via Soap, which handles the connections to different components (publisher, development plugin on the runtime the Publisher, Composer and the composer Development plugin on the runtime)Runtime.

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

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

Key features of the studioStudio:

• Revision Complete revision control of elements
• External Work with external and internal libraries
• Multilingual elements
• Process modelling
Creating dashboards
• User and access management
• Working with multiple projects

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 level 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 serve special provide specific functionality.

The runtime Runtime runs on java Java or .Net and is almost browser independentworks with modern browsers.

Key features of the runtime:

• todo

Publisher

Runtime:

• Customizable dashboard to run applications
• Variety of plugins to extend functionality
• Different APIs to further extend and customize functionality

Working with Runtime provides a complete guide on the Runtime.

Publisher

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 Publisher is used to transfer the application to the following environments (TAP)Via the connection with studio, the publisher can pick up the actual studio application from the development environment and publish it to a central database. This central database can be accessed by the runtimes of different environments, e.g. test, acceptation or production environment. See also the following figure.

Key features of the publisher:

• 4 eyes principle
• Select a tag/revision to publish
• Well-organized overviewAdministration of published/unpublished applications

Composer

With the composer it is possible to edit parts in an application when running in runtime. For instance, the label of an attribute, the label of a button or a container name can be changed. In a lot of cases it is not desirable to do this change on a production environment. This is solved by using an extra environment called 'staging' (which is placed between the acceptance and production environment). On this environment the change is performed and can be put live by using the publisher.