Transcript General

ALMIS Database Seminar
ALMIS Distributed Access
Method (ADAM) Presentation
San Diego, California
August 15 – 17, 2005
ADAM System Back Ground





ALMIS Database Development and Implemented
States Loading Surrounding States ALMIS Data
Proof of Concept Project Undertaken
ADAM Proposal Submitted and Approval Granted
ADAM System Pilot Releases (May 13 & June
17, 2005)
The ADAM Solution
• A standard programming methodology for
cross-state access to ALMIS data over the
Internet
• A means to query and compare data across
multiple states simultaneously – local state
data, remote state data, local/remote state
data, remote/remote state data
• Participating States control who and how
user access their ALMIS data
• A flexible system, with customizable
interfaces, queries and data access security
options
Major Goals of the ADAM System

Multi-state ALMIS Data Accessibility –





Focusing on the ALMIS Core tables for the Pilot Project
Demonstrating Access Security Methodologies
Control of query execution and data access
Distributed Computing – No Single Point of Failure
Robust Extensibility

Non-core ALMIS Tables

Non-ALMIS Tables
Major Goals of the ADAM
System con’t

Flexible Web Functionality – Offering States three
options for accessing the system:

Utilization of the ADAM Display Tool provided

Adaptation of existing state-specific web applications

Creation of new state-specific web applications
Pilot States
Pilot testing in 5 states –


Washington – SQL – Installation in
progress

Alaska – SQL – Installed and running

New Hampshire – Oracle – Waiting
on hardware

Nebraska – SQL – Installed and
running

North Carolina – SQL – Installed and
running
Pilot
States
May 13, 2005 Release
ADAM Documentation:




ADAM Pilot State User Agreement
Draft of the ADAM Installation Guide
Draft of the ADAM Content Manager Installation Guide
System Components






ADAM MS SQL Repository Scripts (the Oracle Local repository
scripts are not complete at this time, see Section 1.4)
ADAM Server Component
ADAM Loader Application (note: this is an update that includes fixes
for reported bugs)
ADAM Client Component
ADAM Web Display Tool and ADAM Content Manager (Note: this
component will be available on or before 5/17/2005 see Section 1.4)
June 17th, 2005 Update Release Provided Oracle Functionality
June 17th, 2005 Update Functionality







23 Core ALMIS Table Queries – Pilot States can use to
access data from any participating State
Ability to load Local ADAM Repository both initially and
after data updates
Grantee of data returned for selected time and geography
Ability to define user data access levels
Data suppression at the ALMIS table level
Ability to create custom queries
Ability to view other participating States ALMIS data by
using the ADAM Display Tool
Additional Functionality to Come




Grantee of data return for selection parms in
addition to time and geography
Data suppression for analyst role refined to
specified geographies and time periods
Ability to sum query results sets across (via a Tool
Kit):
 Geographies
 Time periods
Additions to the ADAM Display Tool
ADAM System Components
ALMIS Database
 ADAM Local Repository
 ADAM National Repository
 ADAM Server
 ADAM Client
 ADAM Toolkit
 Interfaces

ADAM – Technical Details –
Technologies Used





XML – ADAM Queries are written in ANSI SQL and translated into
XML documents
SOAP – SOAP is the messaging protocol used to transport the XML
documents securely between the ADAM Server and the ADAM
Webtool
Database Options 
MS SQL – 1 of 2 types of ALMIS Databases supported by the ADAM
System

ORACLE – 1 of 2 types of ALMIS Databases supported by the ADAM
System
C# - Programming language in which the ADAM System was
developed
RSA/DES – ALL communication between the User, the ADAM
System, and the ALMIS Database is encrypted using RSA and DES
ADAM – Technical Details – Two State
Physical Infrastructure Diagram
National
Repository
State A's ADAM Server:
- Controls access to
State A's data
- Holds all queries used
on State A's data
- Performs data
suppression for State
A's data
National Repository provides:
- Access information for each
state's ADAM Server
- Copies of Gold-Standard Queries
Addre
e
Addr
tate B
's AD
State A's Local
Repository provides:
- Profile information
for State A's ALMIS
Data
ss of
State
B's A
State B's
Local
Repository
provides:
- Profile
information
for State B's
ALMIS Data
ss of
S
AM S
erver
DAM
e
Serv
ALMIS Database/
Local ADAM
Repository
r
User
ALMIS Database/
Local ADAM ADAM Server/
ADAM Client
Repository
User
ADAM Server/
ADAM Client
ADAM
Webtool/
ADAM Client
Library
State B's ADAM Server:
- Controls access to State
B's data
- Holds all queries used on
State B's data
- Performs data suppression
for State B's data
ADAM Webtool/
ADAM Client Library
ADAM National Repository
•Master Server Directory
•Master XML Queries
ALMIS Database and ADAM
Repository


Core tables in ALMIS 2.3 database
ADAM repository, which contains data
about data (or metadata)
ADAM Server
The ADAM Server serves as a gateway to
data on the local ALMIS Database and Local
Repository
It Contains:
• State’s ADAM Directory Address
• XML Queries
• Query Execution Function
• ADAM Administrator Application
ADAM Client
The ADAM Client stores the class library
that allows the a custom web (or windows)
application to communicate to ADAM
Server
ADAM – System Interfaces

State Admin:
ADAM Administrator
 ADAM Loader
 ADAM Content Admin


End User:
ADAM Webtool
 Others

ADAM Administrator
Configures the ADAM Server
 Coordinates the XML query
Updates
 Allows ADAM Admin to:

Enter Meta Data not contained
in the ALMIS database
 Setup Users and Suppression
by user

ADAM Loader
•Windows Dot Net Applications
• Loads data into the ALMIS tables
• Updates the Local ADAM Repository
after ALMIS table updates
ADAM Content Administrator
(ACM)


Optional Component that Provides
States the Ability Customize the
ADAM Web Display Tool
Configure Tabs
Configure Modules
Control Display of Data Columns
 Control Button, Link Titles
 Etc…

ADAM Web Display Tool
Optional Component that Provides States
with an End User ALMIS Database Web
Display Tool That:
• Provides States with Fully Customizable Interface via the
ACM
• Enables the End User to View Data from Participating
ADAM States
• Grantees that User’s Choices Will Return Data
The ADAM System in the future
• Obtain Copyright
• Complete Version 1.0 - One release
remaining
• Submitted Plan to State WIC Reps which
Included:
• Extending Participation to Remaining
States
•Installation and Issue Support
ADAM Functional Flow – Two State Example










User Accesses the ADAM Webtool
Through the Webtool, user in State A. Accesses the ADAM Server in State
A
State A Recognizes that user is requesting data from State B and transmits
to the Webtool the Address for State B
Webtool Accesses State B
User Selects Query to run
Based on the query selected, ADAM Server dynamically provides
parameter options for the user to select from
User selects from parameter values to filter query results and submits query
ADAM Server uses database profile information in the repository, user
provided parameter information to create dynamic SQL statement to run
against the database
Database returns results to the ADAM Server
The ADAM Server performs data suppression based on user id and role,
converts results into XML and moves it to the calling application to present
to user
8.
ADAM Workflow Diagram
ADAM
Server
usesdynamically
database
6. The
ADAM
Server
10.
ADAM
Server
performsprofile
information
the repository,
user
providesinparameter
options
for the
data
suppression
based
on
7.
User
selects
from
parameter
provided
parameter
information
user to
select from
based ontothe
State A ALMIS
user
id
and
role,
converts
values
to
filter
query
results and
create
dynamic
SQL statement
to run State A ADAM
query
selected.
Database
Repository
against
theinto
database.
results
XML and moves it
submits
query.
to the calling application to
State A ADAM
present to user.
Server
State B ADAM
Repository
State B ALMIS
Database
3. State A Recognizes that
State A ADAM
user
is requesting
data from
User Accesses
Accesses
the
Webtool
4. 1.Webtool
State B ADAM 9. State
ADAM
Webtool.
B andB.transmits
State
Database
returns to the
Server
Webtool
the
Address
for
results
toWebtool,
the
ADAM
2.
Through
the
user
Server.
B.
in State
State
A. Accesses the
State A User
ADAM Server in State A.
Internet Access
ADAM Web Interface URL:
http://adamnc.esc.state.nc.us/adamwebtool/
ADAM Contact Information
[email protected]
(919) 733 - 4806 ext 423
Thank You!
ADAM – Technical Details –
Hardware and Software
Requirements – ADAM Server
Required Software
 Install ADAM server web service on a web server running
IIS 6 or higher installed outside firewall (port 80). It is
highly recommended that this be a dedicated server, but is
not a mandatory requirement
 At least 1 GHz processor and a minimum of 512 MB
RAM. A minimum of 500 MB of disk space available for
caching.
 This web server must be running on a network that can be
accessed from outside the firewall
 Microsoft Dot Net framework 1.1 or higher
 Internet Explorer
ADAM – Technical Details –
Hardware and Software
Requirements – ADAM Client
Required Software
 Microsoft Dot Net framework 1.1 or higher
 Network Connection - Must be able to
connect via port 80 to your local ADAM
Server.
ADAM – Technical Details –
Hardware and Software Requirements
– ALMIS Database Server
Required Software

A standard installation of the ALMIS
2.3 database

SQL Server 2000 or Oracle 9i

Latest SQL Server or Oracle service
packs installed

Local ALMIS Database can be
accessible from a remote ADAM server

Database must be configured to support
data between 2 GB and 10 GB. For very
large states, the upper limit may be
higher than 10 GB.

ADAM database account
Required Hardware

100 GB Hard drive minimum

640 MB memory minimum

Windows 2003 Operating System
minimum

Pentium 4 processor

Read/Write CD Rom
Note: the Local ADAM
Repository must reside on
the same server as the Local
ALMIS Database