Skip directly to searchSkip directly to the site navigationSkip directly to the page's main content

IBIS-Q System Documentation - Introduction

The View system documentation includes high level view of the IBIS-PH View System's architecture, System Design (goals, Features, History), Requirements, Request Flows, URL Mapping Magic, Files, Dependencies, Artifacting, installation, configuration, customization, Tomcat Setup, how to build the deployment package, user interface/response page customization, XML content management and data files element descriptions, Tutorials, HTML page design (508 Compliance, Javascript menus, scaleable fonts), CSS, XSLT Page Design, API Docs (for Java, XSLT, and XML files), user preference Cookies, Javascript, Adobe SVG Viewer Browser Plugin, URL Options, Java servlet code aArchitecture, Spring Framework, and filters.

View System - End-User's Perspective

The View System provides three basic types of pages:
  • Meta data pages that describe the web site and the Utah Department of Health
  • Indicator Profile reports
  • Interface that allows custom queries of SAS datasets

And has these high level features:
  • HTML pages that can be formatted in a printer friendly manner
  • High quality, interactive SVG based charts and maps
  • Standard JPEG charts and maps for those users who do not want to use the SVG browser plugin
  • User preferences - ability to specify the graphic type and how to control the query builder interface.

Listed here are some of the pages that discuss main topics of the IBIS System.
  • Overview of the IBIS Query System
  • Overall System Architecture - High level architecture showing all parts of the IBIS-PH System - Admin, View, IBIS-Q
  • View System Design - Features, design goals, decisions, and history
  • View System Architecture - High level architecture discussing the various parts of the IBIS-PH View System
  • View System Requirements - Recommended hardware, operating systems, server software, and software & hardware dependencies
  • Page Request Flows - This describes to a fairly detailed level what the decision points are that define the steps and software components used to create a page. All of the major page type requests are defined and include: request flow: user -> filter -> Spring Request Dispatcher -> controller found via url mapping -> model specified on URL -> view specified as a bean passed in xml config files. See RD section
  • URL to XSLT/XML Transformation Mapping Magic - Describes the process of how a static ".html" page URL is broken down by the system to determine which XSLT and which XML data content to dyamically transform/create the requested HTML page. This also discusses the Java web application's "web.xml" and the Spring Framework's Bean XML configuration files and how these settings work.
  • Artifacting - System's XML/XSLT transformation caching mechanism - how it works and what are the issues.
  • Naming Conventions - Naming conventions for Java, CSS, HTML Elements, XML Elements, Javascript, cookies, and filenames.
  • Application's Directories and Files - Table of all directories with a description of that directories contents are and when applicable, a description of specific files (like control files etc.). This also points out which directories are static and which ones can be changed and where those changes need to be reflected in which configuration file.
  • Internal Tools - Describes the internal developer used pages like the system information jsp, the http response jsp, the module xinclude cross reference reports, and module debugging.
  • Error Handling - This page describes how the system handles internal system errors.
  • Issues and Future Features - Lists known issues of the system and lists potential future features.
The information provided was retrieved on: Thu, 19 September 2019 20:06:27.

Content updated: Wed, 4 Nov 2015 09:26:28 MST