Architectural Overview

OAT is built using Scala ( and the Play! web framework (

Play contains its own built-in web server. So the Play app runs on one machine ( with pretty much nothing else on it. We might eventually want to put an Apache server in front of it to do load balancing, but right now it's just Play.

The database runs on another machine (postgres165.cs.uwaterloo.cs). Also pretty much the only thing on that machine.

Both machines are accessible via the campus network, but to get to them from off-campus you need to use the VPN.


It is our intent that the data in the database be accessible in the following use cases:

  1. Authenticated users (eg advisors) via the OAT web site ( This includes ASIS to display student data as well as "Canned Queries" to run pre-written queries with user modified parameters.
  2. Authenticated users (eg students either as themselves or via a portal) via web services provided by the OAT web site.
  3. Direct SQL for a small set of selected users (eg: OAT developers, people developing Canned Queries, people doing "what if" analysis of the data). Tools in use as of 20131022 are
    • psql (command-line tool)
    • pgAdmin (GUI wrapper on psql)
    • Excel
In addition to the above, CSCF has access for some administrative processes.
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r2 - 2013-10-22 - ByronWeberBecker
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback