viaMedia Architectural Overview

Conceptually, viaMedia works across a number of different layers, which could represent geography, security, function, or a combination of these. This flexibility makes viaMedia well suited to operate in today’s world of intranets, databases, distributed content builders, separate web servers and databases, and a geographically dispersed user base.

Beginning at the Application layer, you’ll find the viaMedia Authoring application. This .exe is installed on the Authors local personal computer.

Content is the next layer. Here is where the actual modules are stored, prior to being published. In simple terms, this can be thought of as the storage layer for Authors original version. This storage may be local or centralized depending upon the needs and preferences of the organization.

Delivery on-line is the top layer, which has two main components. First is the module server which maintains the web service and logical layer required to manage the merging and delivery of web content. When a module is published, a server at this level stores and serves the modules content to end users. The second component at this level is the Database Server, an SQL database which manages lists of users, groups, modules, logins, passwords and assessment results. Together these two components provide the content which the end user will experience.

The Browser layer is where the end users experience takes place. All that is required is a current browser; there is no application or separate 'Player' required. Privileges defined within the Database server determine what access each user is granted, which may vary from viewing modules available to the general public to viewing modules available to specific predetermined groups. With appropriate privileges administrative functions to maintain and query the database can also be done from the Browser layer.