Appendix I. Geographic Information System (GIS) Documentation
Purpose of This Document
The purpose of this document is to provide necessary information required to properly
document, deploy, and host a Geographic Information System (GIS) created as part of the operating of the National Available Beds for Emergencies and Disasters (HAvBED) system as implemented at Denver
Health and Hospital Authority. It is limited to hardware, software, and database specifications.
Contents
1. Introduction
1.1. Objectives
1.2. Scope
1.4. References/Attachments
2. Application Name
2.1. Application Narrative/Overview
2.2. High Level Application Architecture
2.3. Schematic Diagram of the Application
2.4. Application Profile
2.4.1. DNS Requirements
2.4.2. SSL Requirements
2.4.3. Firewall Ports Requirements
2.4.4. Hardware
2.5. Contacts
2.5.1. Technical Contacts
3. Operations Guide
3.1. Application Components
3.2. Backup/Restore Requirements
4. System Administration Guide
4.1. Configuration Parameters
4.2. GIS Data
4.2.1. GIS Data Details
5.1. Future Recommendations Narrative/Overview
1. Introduction
1.1. Objectives
This document describes software, database architecture, and hardware configuration for the HAvBED GIS application.
Return to Appendix I Contents
1.2. Scope
This document is focused on the HAvBED GIS details.
Return to Appendix I Contents
1.4. References/Attachments
- ArcIMS9 Architecture and Functionality, ESRI
http://www.esri.com/library/whitepapers/pdfs/arcims9-architecture.pdf
- Install IIS 6.0 with Tomcat 4.1.29 using J2SDK 1.4.2 for ArcIMS 9.0 on Windows 2003, ESRI
http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow&d=25867
- Identifying Firewall TCP Server Ports In a Enterprise ArcIMS Configuration, ESRI
http://www.esri.com/systemsint/kbase/docs/arcims_tcp_port_tb_rev2.pdf
- Configure ArcIMS to work with HTTPS, ESRI
http://support.esri.com/index.cfm?fa=knowledgebase.techArticles.articleShow&d=21669
- Customizing ArcIMS—Using the ActiveX Connector, ESRI, Software Documentation Library for ArcGIS 9.
- Managing ArcSDE Application Servers, ESRI, Redlands, CA, 2004.
- ArcSDE Developer Help, http://edndoc.esri.com/arcsde/9.1
Return to Appendix I Contents
2.
Application Name
2.1. Application Narrative/Overview
The HAvBED system is a national hospital bed-tracking tool
which was implemented as an internet-based system available for secure Web site
viewing by federal, regional and local offices of emergency management and
others. This is a Department of Health and Human Services (HHS) Agency for
Healthcare Research and Quality (AHRQ) grant-funded research effort to develop
a national hospital bed-tracking system in the event of a medical emergency
such as a bioterrorist attack.
The Geographic Information System (GIS) is comprised of a database,
Web services and a Web site. The database is store the secure information that
is queried via an eXtensible Markup Language (XML) from disparate hospital
systems located around the U.S.
The Web service is a secure system-to-system transfer of bed
availability information into the HAvBED database. The Web site allows a secure
information display as well as a secure log-in for bed availability data entry
from other participating hospitals which do not have a computer system
interface with HAvBED. This is a proof of concept project, and all hardware
specifications have been designed to meet this limited functionality.
The decision to purchase Environmental Systems Research Institute, Inc. (ESRI) software,
ArcEditor, ArcIMS, and ArcSDE, was determined by the need of the project to
present a graphical displayed in large geographic databases stored in Microsoft
Structure Query Language (SQL) Server 2000. The Internet GIS system would go
through development environment, where application components configured to
interact with Web services and spatial engines to generate maps across the
Web. The final production was transferred to the Secured Server where several
issues arose. Security features would intermittently allow the display of map
images within the Web application. The issue was resolved by discontinuing to
use the ArcSDE connection and place the ESRI shapefiles directly on the
Application Server.
Select to access Application Narrative/Overview.
Return to Appendix I Contents
2.2.
High Level Application Architecture
-
The user-defined query generated by the Web application passing stored procedures on Microsoft SQL Server 2000 database to the ArcIMS tasker and monitor, running on the application server, which returns a .jpg map to the Web application using a set of Microsoft Common Object Model (COM) objects that expose interfaces to the Application Server, or an ActiveX Connector.
- The Application Server is located in a secure environment, only allowing Secure Hyper Text Transfer Protocol (S-HTTP) traffic on port 443 from the World Wide Web (WWW).
- The Microsoft® SQL Server database is located in a second secure environment, and accessible only via port 1433 from the Application Server Internet Protocol (IP).
Return to Appendix I Contents
2.3. Schematic Diagram of the Application
Select to access Schematic Diagram of GIS Architecture using ArcSDE.
The initial configuration involved the use of ESRI ArcSDE connecting to ArcIMS on the Application
Server. Once the need to open Port 137 was determined by Farrugut System
Consultants, the configuration was determined to be a security threat the use
of ArcSDE was discontinued.
Select to access Schematic Diagram of GIS Architecture using ESRI Shapefiles.
The final configuration involved the use of ESRI shapefiles directly on the Application Server to bypass the
need to open Port 137.
Return to Appendix I Contents
2.4. Application Profile
2.4.1. DNS Requirements
Return to Appendix I Contents
2.4.2. SSL
Requirements
Return to Appendix I Contents
2.4.3 Firewall Ports Requirements
Select to access Firewall TCP Server Ports.
S-HTTP port 443 allows access from Internet user (client) to Web servers. ArcSDE port 5151 allows
access from ArcIMS to ArcSDE. Port 5300 was opened so the ActiveX connector can
call the appropriate data derived a user defined query. Using ArcSDE on a
Secure Server requires that Port 137 be opened. Due to security concerns Port
137 was not open and subsequently data residing in ArcSDE was placed on the
Application Server.
Return to Appendix I Contents
2.4.4. Hardware
- For Application Server, require 1 GB RAM and 2 Processors with 40 GB hard disk space.
- For Microsoft® SQL Server, require 1 GB RAM and 2 Processors with 40 GB hard disk space.
Return to Appendix I Contents
2.5. Contacts
2.5.1. Technical Contacts
The responsibilities of these technical contacts for the application include providing technical support.
Name |
Title |
Role/Responsibility |
Phone |
Email |
Pager/Cell |
Gerald Pattyn |
Senior Consultant |
ArcIMS |
(303) 666-9133 x112 |
pattyn@farragut.com |
(720) 840-4699 |
Return to Appendix I Contents
3. Operations Guide
3.1. Application Components
- ArcEditor 9.0:
- ArcEditor is the complete GIS desktop
system for editing and managing geographic data. ArcEditor was used primarily
to move spatial data to Microsoft SQL Server 2000.
- ArcIMS 9.0:
- ArcIMS is the solution for delivering dynamic maps and GIS data and services via the Web. It provides a highly
scalable framework for GIS Web publishing that meets the needs of corporate
Intranets and demands of worldwide Internet access. Using ArcIMS, city and
local governments, businesses, and other organizations worldwide publish,
discover, and share geospatial information.
- ArcSDE 9.0:
- ArcSDE is a server software product used to access large geographic databases stored in relational database management systems (RDBMSs). It is an integrated part of ArcGIS and a core
element of any enterprise GIS solution. Its primary role is to act as the GIS
gateway to spatial data stored in a RDBMS. ArcSDE provides a suite of services
that enhance data management performance, extend the range of data types that
can be stored in a RDBMS, enable schema portability between RDBMSs, and offer
configuration flexibility.
- Tomcat 4.1.29 using J2SDK 1.4.2:
- ArcIMS components are Java components and require a JavaVirtual Machine (VM), which provides the basic application programming interface (API) for running these applications. The JavaVM is
included in the Java Developer Kit (JDK). ArcIMS requires a JRE, which is
installed if it is not already on the machine. It is possible to have more than
one JavaVM on a machine, and ArcIMS can be made to use an existing JavaVM as
long as it is compatible. Servlet engine, or small program running on the
Server. ArcIMS requires a servlet engine. A servlet engine is an extension to
the JavaVM and provides support for servlets through a servlet API.1
1. ArcIMS 9 Architecture and Functionality, ESRI, http://www.esri.com/library/whitepapers/pdfs/arcims9-architecture.pdf
Return to Appendix I Contents
3.2. Backup/Restore Requirements
- ArcSDE Configuration and Tuning Guide for Microsoft SQL Server, Backup and Recovery, ESRI, Software Documentation Library for ArcGIS 9: page 73-89.
Return to Appendix I Contents
4. System Administration Guide
4.1. Configuration Parameters
Installation Process:
Install Java Servlet —> Install ArcIMS —> Install ArcSDE.
Servlet Installation:
Using the document: Install Internet Information Server
(IIS) 6.0 with Tomcat 4.1.29 using J2SDK 1.4.2 for ArcIMS 9.0 on Windows® 2003,2 the servlet was installed on both the Development Server and the Secured Server to allow ArcIMS to communicate with Web services. The installation is very particular and if not the the
installation steps are not followed precisely the results include a
non-responsive Internet GIS system.
The article, Configure ArcIMS to work with HTTPS,3 is necessary for ArcIMS to work on a Secure Server. A security certificate must be exported out of the Trusted Root
Certification Authority and import certificate into the JAVA installation.
2. http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow&d=25867
3. http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow&d=21669
Return to Appendix I Contents
4.2. GIS Data
4.2.1. GIS Data Details
GIS Shapefiles:
- lines_freeways
- National coverage ESRI shapefile.
- lines_highways
- National coverage ESRI shapefile.
- lines_rivers
- National coverage ESRI shapefile.
- lines_roads
- National coverage ESRI shapefile.
- points_airports
- National coverage ESRI shapefile.
- points_hospitals_name
- American Hospital Association latitude and longitude data converted to feature points using ESRI's ArcGIS.
- points_landmarks
- National coverage ESRI shapefile.
- points_schools
- National coverage ESRI shapefile.
- polygons_airports
- National coverage ESRI shapefile.
- polygons_cdc
- National coverage ESRI shapefile.
- polygons_counties
- National coverage ESRI shapefile.
- polygons_countries
- National coverage ESRI shapefile.
- polygons_lakes
- National coverage ESRI shapefile.
- polygons_parks
- National coverage ESRI shapefile.
- polygons_fema
- National coverage ESRI shapefile.
- polygons_msa
- National coverage ESRI shapefile.
- polygons_ocean
- National coverage ESRI shapefile.
- polygons_States
- National coverage ESRI shapefile.
Return to Appendix I Contents
5.1. Future Recommendations
The HAvBED GIS component operation could be improved. The initial architecture
included the use of the spatial database engine ArcSDE, a GIS component that
works with multiple users editing and using the GIS data without compromising
the performance. The use of ArcSDE will also allow the dispersion of GIS
components away from a single machine setup which burdens the processing power
of a single server. Individual components of the ArcIMS system can be broken
out and distributed among several server and thus balancing the work load and
increasing the performance significantly. The diagram below shows the outgoing
and incoming server port traffic in a typical four-node ArcIMS
High-Availability Configuration. All the outgoing TCP connections on an ArcIMS
component are consolidated onto a single "any" port. Listening ports are
illustrated with black boxes and white numbers.4
Select to access Server Port Diagram for a Four-Node ArcIMS High-Availability Configuration.
4. http://www.esri.com/systemsint/kbase/docs/arcims_tcp_port_tb_rev2.pdf
Return to Appendix I Contents
Return to Contents
Proceed to Next Section