Page History

...

An application which is created in studio can be directly tested in the runtime via the development plugin (typically only available on the develoment 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

The studio consists of A closer look at the studio shows that there are two layers internally:

• studio server
• studio client

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

The client handles all user interface elements (the studio screenscreens) . Both layers run on top of an ISS application server. The studio are handled by the client. This client is built with XBAP technology and runs only in Internet Explorer.

Both studio layers run on top of an ISS application server.

Key features of the studio:

• Revision control of elements
• External and internal libraries
• Multilingual elements
• Process modelling
• Creating dashboards

Runtime

The runtime runs on top of an application server, e.g. Tomcat, JBoss, Websphere or ISS. On the next level the 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 functionality.

...