Version 8.2 (2013-03-18)
 —  Introduction  —

Concept

This document covers the following topics:


Layout Creation - Binding to Application

The Application Designer concept follows the commonly accepted paradigm of separating the layout (view) of an application as much as possible from the application logic itself.

To write a page (view) as a front-end to an application, you proceed as follows:

The class does not provide a large amount of logic but connects to existing application logic. This is the reason why it is called the "interaction adapter" in this documentation.

Layout creation

Top of page

Server Side Architecture

The Application Designer server runtime is a web application which is based on the Java Servlet standard. It can be deployed multiple times to a servlet engine of your choice. XML layout definitions, generated intelligent HTML pages, adapter classes and other resource files are part of this web application.

Server side architecture

You either install Application Designer as a web application inside your servlet engine and build your application modules around it, or you add and integrate the Application Designer environment into an existing web application.

In case of a multiple-deployment setup, each deployed instance of Application Designer is a self-contained, independent environment, completely separate from the other instances. With the example shown in the graphics above, you have three independent instances. Pages of the first instance are, for example, accessible via http://host:port/aaaaa/..., pages of the second instance via http://host:port/bbbbb/..., and so on.

Top of page