SOA in Wisconsin

1
SOA in Wisconsin
NAJIS Annual ConferenceOctober 17, 2007Santa
Fe, NM
Jim PingelDirector, Wisconsin Justice
Information Sharingjames.pingel_at_wisconsin.gov
2
Information-SharingObjectives

• Make it Affordable
• Leverage Existing Investment Dont Force
  Upgrades
• Cheap to Build and Maintain
• Security and Privacy
• Role-Based Access
• Reuse!

3
Crossing Boundaries

• State/Local
• Justice Domain (Law Enforcement, Prosecution,
  Courts, Corrections, PP)
• and beyond (Public Health, Transportation, etc.)
• Proprietary Systems
• Set the Stage for Interstate Sharing

4
WIJIS Value-Adds

• Consistent Data Definition (GJXDM/NIEM)
• Consistent Messaging (URIs)
• Reusable Security Components
• Technical Assistance

5
From the Local Perspective
WIJIS Justice Gateway(One-Stop Search)
WIJIS WorkflowEngine
Local Law EnfRecords Mgt Systems
State/NCICHot Files/CHRI
6
The State Perspective

• Less Stuffing of Filing Cabinets (real or
  virtual)!

7
SOA Governance
This is SOA DESIGN
8
but so is this
SOAGovernance SharedDefinitions
9
Its not painless.

• Adapters can be expensive
• Getting proprietary systems to talk to an open
  standard
• Extracts are not SOA but theyre a prerequisite
  to the seamless open cost-effective
  connections implied by SOA.
• Limited capacity and expertise in small local
  governments
• WIJIS Developers Toolkit
• Big ROI from documenting!

10
Do We Need an ESB?

• According to the Aberdeen Group
• Enterprise SOA requires and uses mission-critical
  SOA middleware suite capabilities.
• SOA ERP is used by companies that are choosing to
  deploy SOA surrounding their ERP application
  software.
• SOA Lite is for users who are primarily deploying
  web services that do not require mission-critical
  capabilities such as high-volume scalability,
  high availability and failover, management,
  governance, and security.

The Aberdeen Group. Enterprise Service Bus and
SOA Middleware. Boston, MA. Exeutive Summary
Accessed on October 8, 2007 at http//www.aberdee
n.com/summary/report/benchmark/RA_IT_ESB_PK_3170.a
sp
11
Do We Need an ESB?

• Not Yet.
• Not (Necessarily) A Large, Proprietary Middleware
  Suite.
• Can We Grow Our Own?
• Watch XQuery.
• XQuery has the potential to become the most
  applicable language for extracting and
  transforming data from any source that can be
  represented as a real or virtual XML document.
  Its SQL-like syntax is relatively easy to learn
  and it already has a role in SOA for extracting
  and transforming data.

Fancellu, Dino and Edmund Gimzewski. Extended
XQuery for SOA. OReilly xml.com. Accessed on
October 8, 2007 at http//www.xml.com/pub/a/2007/
09/12/extended-xquery-for-soa.html See Also
Denis Sosnoski at http//www.parleys.com/display/
PARLEYS/SOA lite
12
This work was supported in part by federal grants
2006-LD-BX-K394, 2004-GR-T4-K009, and
2005-WF-AX-0051. Points of view or opinions in
this document are those of the author and do not
represent the official position or policies of
the United States Departments of Justice or
Homeland Security.
For more information please visit http//oja.wi.g
ov/wijis http//wijiscommons.org