IBIS System Installation and Customization

Garth BraithwaiteSoftware Technologies GroupJune 8, 2007

Overview

This section provides a brief, 30,000 foot installation and customization overview for two of the three IBIS-PH systems/applications. For the purpose of this session, I will assume that each of these applications will be hosted on a separate server. Each server is commonly referred to as a “tier.” Since there are two applications, each on different servers, I’ll refer to them as two tiers.

Installation Outline

IBIS-PH View System Server (public)Software ComponentsInstallationCustomization

IBIS-Q CGI System/SAS Server (private)Software ComponentsInstallationCustomization

IBIS-PH Software ApplicationsIBIS-PH View SystemPublic web/internet based application that allows the viewing of static web content, delivery of published reports, viewing of health indicator profile reports, and provides the interface portion of the custom queries.

IBIS-Q CGI SAS Interface Query SystemTypically a private web/intranet application that interfaces with SAS to build and run custom queries. This application can run by itself without the View System front end or can deliver XML data to the View System.

IBIS Data Administration and Maintenance SystemInternal web/intranet based application that allows different health program offices to maintain/edit health indicator profile data and publish these data to the public View System for consumption by the public.

System Architecture

System Architecture

View System Server

View Server - Software ComponentsOperating System (Windows, Linux, Unix Solaris, etc.)

Java JDK (Java Development Kit)

Java Web Application Server Container (Tomcat, IBM’s Websphere, Sun’s JavaOne etc.).

IBIS-PH View System ApplicationJava class files (controls how to respond to user requests)XML Data filesXSLT Translation files (transforms XML to HTML)CSS Stylesheets (controls web page colors, positions etc.)Image files (static graphics like banners, headers – not the charts)Javascript files (provides interactive web pages)

View Server – InstallationDownload and install the Java JDK of your choice for your operating system/hardware platform (Sun’s version 1.5+ recommended) (see java.sun.com or ibm.com etc.)

Download and install the Java Web Application Server Container (Tomcat 5.5.x recommended - apache.org)

Install the IBIS-PH View System ApplicationContact Utah for the latest production versionPut the ibisph-view.war in appropriate application container (for Tomcat this is typically tomcat/webapps).-OR-Unzip the ibisph-view.war or ibisph-view.zip file’s contents to the appropriate webapp container folder/directory.

View System – Customization (1 of 2)HTML Page Look and Feel Customization

Determine HTML page layoutModify the main _site_specific.xslt to override any “html” page layout API type templatesUpdate the *.css files to change font preferences, colors, page widths etc.Create or link to static banner images, button images etc.Update the appropriate menu XML data files (if using the IBIS menuing system) or create/link to the appropriate menuing code (if doing the latter will need to modify more site specific xslt templates which are used to create dynamic context menu items)

Update/create any desired static HTML page XML files (similar to HTML server side include type files)

View System – Customization (2 of 2)Update the Spring request_dispatcher.xml xml URL mapping file (depending on the desired View System modules used, page XML file directories etc)

Update/create the query dataset associated Query Module/Builder page XML file

Copy Utah module files which best matches the SAS dataset and questions/answersModify the measure titles, question titles, answer values and titles, and other parameter names and values as needed

Edit the site_specific.properties file and change the value of the QueryApplication.URL property to the appropriate IBIS-Q CGI URL value

System Architecture

IBIS-Q CGI Query System and SAS Server

IBIS-Q CGI/SAS Server – Software ComponentsOperating System (Windows, Linux, Unix, Solaris, etc.)

Web Application Server (Apache, MS-IIS, anything that supports CGI)

SAS Application (requires appropriate modules and licenses)

IBIS-Q ApplicationCGI (c program specifically complied for the hardware and operating system)Configuration text control files (*.cfg) (specifies the SAS executable path, path to the associated SAS data file, how to map URL request parameters to SAS procedure variables, and other misc control items)SAS template text control files (func*.def) (specifies SAS procedure information and SAS code needed to query and calc the measures)SAS procedure code text files (*.sas) (optional SAS procedural program files – include files)Map text control files (xml*.map) (specifies how to map the queried/calculated SAS data values to the appropriate output XML data elements - which is requested by the IBIS-PH View System)Group control text files (*.grp) (optional control files that specify how to map dynamic SAS variable values)

SAS data files -or- SAS database connection components)

IBIS-Q CGI/SAS Server – InstallationInstall Operating System and SAS Server Software Components

Install a CGI Web Server (Apache recommended - apache.org)

Contact Utah for the appropriate CGI executable (based on the hardware platform and operating system)

Contact Utah for the appropriate back end control files

Contact Utah for the appropriate dataset file structures

Create the CGI and backend control directory structure and copy files into appropriate directories

IBIS-Q CGI System – CustomizationCopy/create/update the SAS dataset (data file/database tables)

Update/create the backend configuration (.cfg) control text file associated with the SAS dataset. This includes creating/updating:

SAS dataset path and filename to useSAS application locationSAS variable names and how they map to HTTP request parameters

Update/create the appropriate SAS template function definition (.def) control text file(s)

Update/create any needed SAS procedure code (.sas)

Update/create any needed grouping files (.grp)

Update/create the output value xml mapping file (.map)