Quick Search:   

Home | About Us | Customer Login | Document Library | Contacts
e-Commerce and Document Management:
UniData RedBack Architecture
REDBACK ARCHITECTURE
The RedBack architecture is based on a three-tier, client-server model in which the client is independent of the application server, which in turn is independent of the database. The RedBack architecture comprises four main components:

1. RedBack Designer
A Windows-based, object-oriented development environment for building and maintaining web applications. Its graphical form painter lets you drag and drop user interface objects, set their properties, attach methods, define data sources, and associate handlers and methods with user-interface events. The Developer connects to RedBack's multi-user Repository at development time via a direct HTTP connection. The Developer is not required for deploying an application; the only software needed on the client to run the application is a standard web browser

2. RedBack Gateway
A middleware component that maintains and schedules requests between a standard web server and the RedBack Application Server. Its functions include:

Managing request and response communication between the web (HTTP) server and RedBack Application Server
Supporting optional placement of the web server and RedBack Application Server on different computers
Dynamically creating and maintaining open connections to RedBack Application Server installs
Maintaining persistent and non-persistent connections to web users
Maintaining statistics on wait times, service durations, and other runtime measures Controlling the number of simultaneous users

3. RebBack Application Server
The control point for accessing server-side application objects and databases. It manages server-side methods and event handlers, database locking and transactions, and the dynamic generation of HTNL pages.

Application objects define the business rules of the application and perform all non user-interface processing.

4. RedBack Repository
A database that contains all the definitions and code that define the application. The RedBack Repository stores web pages, application objects, and client and server event-handler code. All Repository objects are stored in a location-independent manner, and are accessible through a published API. Repository contents are defined and maintained using Developer.

Back to top ^