Working Paper, February 6 , 2009 Working Target Enterprise Architecture for the U.S. EPA Using SOA, Web 2.0, and Cloud Computing by Brand Niemann, Senior Enterprise Architect, OEI/OTOP/MISD/ITSPB. NEW: EPA MediaWikis (about 50) Web 2.0/3.0, CAP (Tony email, Brian Burch email), Weaver ROT better way (c.f., Ontology for National Map), Shu and Brian new, Matrix of Systems

holeknownSecurity

Nov 5, 2013 (3 years and 7 months ago)

98 views

Working Paper,
February 6
, 2009

Working
Target Enterprise Architecture for the U.S. EPA Using SOA, Web 2.0, and Cloud
Computing by Brand Niemann, Senior Enterprise Architect, OEI/OTOP/MISD/ITSPB
.

NEW: EPA MediaWikis (about 50) Web 2.0/3.0, CAP (
Tony email
,
Brian Burch email),
Weaver ROT


better way (c.f., Ontology for National Map), Shu and Brian new, Matrix of
Systems



Summary

Some simple architecture diagrams for SOA, Web 2.0, and Cloud Computing are first provided.
These are then illustrated with a ve
ry specific example. Appendices are provided that contain
Thoughts on Target Architecture and CPIC Integration and
a preliminary Announcement for a
Fed
eral Cloud Computing Week.

.

Outline

1. Service
-
Oriented Architecture

2. Web 2.0

3. Cloud Computing

4. Sp
ecific Example

5.
References

6.
Appendices

A.
Thoughts on Target Architecture and CPIC Integration December 22, 2008 (Updated
January 5, 2009)

B.
Preliminary
Announcement


1.
Service
-
Oriented Architecture

In
computing
,
Service
-
oriented architecture

(
SOA
) provides methods for
systems development

and
integration

where systems group functionality around
business processes

and package these
as
interoperable

services
. SOA also
describes IT infrastructure

which allows different
applications to exchange data with one another as they participate in
business

processes
. Source:
Wikipedia
.



Source:
Wikipedia

1. WOA. A Web Services Framework and
Web Services Orchestration Engine

I have to start with thi
s
one because I’m often
surprised with the
notion that MindTouch
Deki is a wiki. Yes,
there is a very polished
“wiki
-
like” interface
that exposes
most,
but
not all, of the
capabilities of the web
services layer.
Anything you can do
through the “wiki
-
like”
interface,
and
more
, can be done
through
RESTful

interfaces. In fact,
every
Deki page is an
XML web service

that
is RESTful. We call
this a
Web Oriented
Architecture

(
WOA
).
This has many
profound and
interesting benefits for developers and enterprise IT architects alike. To start with, you can
e
xtend the platform in any programming language. It is easily embedded into other applications
and easy to connect other systems, web services and data sources. Also, many use MindTouch
Deki as a specialized application server for developing social or colla
borative applications. A
great public example of this is
www.Shelfari.com
.

This was acquired by
www.Amazon.com

in
mid
-
2008. Most importantly, while all other social and collabo
rative enterprise applications
provide you with a walled
-
garden/point
-
application that forces you to adapt to their pre
-
defined
workflow, MindTouch, with the WOA and DekiScript, allows you to
adapt the platform to suit
your workflow, needs and existing ent
erprise ecosystem
and you don’t need an army of
engineers to do this.




http://epaenterprisearchitecture.wik.is/Web_2.0_Server_Inventory_of_Web_2.0_
Applicati
ons

2.
Web 2.0


The term "
Web 2.0
" describes the changing trends in the use of
World Wide Web

technology
and
web design

that aim to enhance
creativity
, communications, secure information sharing,
collaboration and functionality of the web. Web 2.0 concepts have led to the deve
lopment and
evolution of web culture communities and
hosted services
, such as
social
-
networking sites
,
video
sharing sites
,
wikis
,
blogs
, and
folksonomies
. Source:
Wikipedia
.


Below is a
matrix

I originated for the Web 2.0 Team Report last January and that has been adopted by
the Federal Web Content Managers Forum.


































Source:

Federal Web Content Managers Forum
3.
Cloud Computing

Cloud computing

is
Internet
-
based (
"cloud"
) development and use of computer technology
("
computing
"). The
cloud

is a metaphor for the Internet, ba
sed on how it is depicted in
computer
network diagrams
, and is an abstraction for the complex infrastructure it conceals.
[1]

It is a style
of computing in which IT
-
related capabilities are provided “
as a service
”,
[2]

allowing users to
access technology
-
enabled services from the
Internet

("in the cloud")
[3]

without knowledge of,
expertise with, or control over the technology infrastructure that supports them.
[4]

"Cloud
Computing is a paradigm in which information is permanently stored in servers on the Internet
and cached temporarily on clients that include desktops, entertainment cente
rs, tablet computers,
notebooks, wall computers, handhelds, sensors, monitors, etc."
[5]

Cloud computing is a general concept that incorporates
software as a service

(SaaS),
Web 2.0

and other recent, well
-
known technology trends, in which the common theme i
s reliance on the
Internet for satisfying the computing needs of the users. For example,
Google Apps

provides
common business applications online that are accessed from a
web browser
, while the
software

and
data

are stored on the server
s. Source: Wikipedia.



Source:
Wikipedia
4. S
pecific Example


Now in this new Target Architecture, the Web 2.0 Tool (e.g. Mashup Editor like IB
M's
Greenhouse
used in this

specific example)
generates the architectural diagram which is also
an executable artifact

-

it make the data flow from the Web Services to the end result specified
(e.g. a data visualization, data table, data statistics, map. e
tc.). This new paradigm will take
conventional Enterprise Architects some adjustment because they are used to just static diagrams
on a page, PowerPoint slide, etc.


So image that you have the EA diagrams at three levels and types:


1. High
-
level like
for
SOA, Web 2.0,
and Cloud Computing
in Section 1
-
3 above
(schematic on
paper)
.


2. Mid
-
level like how the specific Web 2.0 Mashup tool works (connects web services in a SOA
using cloud computing services) (schematic on paper and/or executable with visual int
erface and
underlying computer code)
.


3. Detailed
-
level like how the specific Web 2.0 Mashup tool works (inputs connected to outputs
in actual data flows and displays) (executable with visual interface and underlying computer
code)


Of course there are a
few of type 1., one for each Web 2.0 Mashup Tool, and many for all the
data flows our agency might want to do. Some tools maintain the later in a "portfolio
environment" so they can be readily reused, adapted, etc.


There are videos and slides decks that s
how this. For example, from our 5th SOA for E
-
Government Conference, please see
slides

that
will be
demonstrated
at our
February 17th
Workshop
.


For the Deki Wiki, that support
s

WOA (Web Oriented Architecture
-

a subset of SOA),
there are
both
architecture
diagrams

and
videos

that also demonstrate the above. David Eng
posted
a
three
part discussion

on Web
2.0 WOA for the recent OEI National Conference at. He understands a
the need for a
Web 2.0 Tar
get Architecture for the agency, especially for Wikis.


What follows next is a recent pilot using the
IBM Lotus Greenhouse

Web 2.0 Mashup Toolkit.
The da
ta feeds are in the InfoSphere M
ashupHub catalog. Search by using the keyword “water”
or tag “epa” and you will find the samples. For the Reuter sample, you can search using the
keyword “reuter”.


This
co
uld
be
extend that to include Data
Architecture by
getting best practices for data
warehousing into the Web 2.0 and Cloud Computing environment

and
the use of a competit
i
ve
system for new IT projects that would get funded based on first delivering success
over the short
term and then based on delivering reuse to other projects over the longer term.
See Appendix A.
We created a feed to consume the web service. Then we created a feed mashup below to
manipulate the result so that it can be dropped onto an Open
Streep map widget. This is how the
feed mashup looks
.






Here's how we

limit the result to the repeating elements of the monitoring location.











The transform takes the data and converts it i
nto the format that is understood by OpenStreet
map which is contains the address, data, and info nodes. The Address node contains the
concatenated values of longitude & latitude of the monitoring locations.




This is how it lo
oks in the mashup when dropped onto an OpenStreet map
widget.



Water Quality Station Finished Demo


Hi Brand,


I have completed the sample for the water quality stations. I'll send you the chart demo in a separate
email. Plea
se let me know once you've decided which data you would like to display in the mashup page
for the other web service (Activity Result web service).


Have a great weekend!


Here's the scenario:

The 1st data viewer widget is data coming from DB2 table

Us
er Input is out of the box widget

OpenStreetMap is wired to both the 1st data viewer widget and the user input
-

the feed mashup which is
the source of the map data refreshed based on which organization is selected or entered (wiring). I have
both the dat
a viewer and user input to demonstrate multiple ways to specify the organization ID

Finally the 2nd data viewer widget (on the bottom) contains more detail about the selected station from
the map


Hi Brand,


Here's the screenshot of the chart demo takin
g data from your spreadsheet and transform it into a format
that can be dropped to a chart widget.



Hi Brand,


I sent you the finalized demos that I have so far. I haven't had the chance to record my keystokes. I'm
leaving for Lotusphere this Sunday and

if it's OK with you, I'll do the recording after I get back. Also, I
think it will be good to do another quick e
-
meeting at your convenience so I can explain to you what I've
done
-

the recording will have no audio.

5. R
eferences

U.S. EPA Target Archit
ecture Version 1.0, December 16, 2002, Final. Binder and CD
-
ROM. See
EPA Enterprise Architecture Pilot Web 2.0 Wiki
. Also contains EPA SOA Work.


Federal SOA Community of Practice

http://semanticommunity.wik.is/Federal_SOA_Community_of_Practice


http://federalsoa.wik.is/


EA SIG, Government Transformation: Service Oriented Gover
nment, Role of EA & SOA in
Government Transformation, Archit
ecturePlus, November 18, 2008, David M
ayo, Everware
-
CBDI, 8 slides. Also see
http://smw.osera.gov/pgfsoa/index.php/Welcome


EPA USGS
Water Quality
Web Service. See
http://epadata.wik.is/EPA_USGS_Water_Quality_Web_Service


EPA OEI National Conference Discussion Forum (
http://connect4environment.ning.com/forum
)

Meeting Future EPA Business Needs with Web 2.0 Technologies and Tools (Part 1 of 3) David
Eng

Web 2.0 Technology, Where EPA should go.(part 2)
-

Web 2.0 Requirements David S. Eng

Web 2.0 Technology, Wh
ere EPA should go.(part 3)


Plug and Play Web Service and WOA
David S. Eng

Reply by Brand Niemann on December 5, 2008 at 9:14am.
W
hat if we could have the best of
both worlds? A COTS Web 2.0 capability that came out of and still has its roots in the OS
Co
mmunity. That is what we are looking at to put EPA in the forefront of Web 2.0!


Network
-
centric Interoperability Framework (NIF) Patterns Catalo
g, Legacy Integration Pattern,
February
5, 2008, 17 pages.

Network
-
centric

Operations Industry Consortium

(NCOIC)
.

This working paper is an internal NCOIC NIF WG paper that has not been approved to be
released either inside NIF WG or inside NCOIC. It can be distributed as
-
it
-
is for comments
without any kind of warranty to the N
COIC members. This pattern is being developed as a pilot
pattern to experiment preliminary versions of NIF v2 and get early feedback to improve NIF
development.

This pattern covers the integration of existing systems in operational use (legacy
systems) int
o a net
-
centric environment, such as a Service Oriented Architecture (SOA). I.e. how
systems that were not originally developed for SOA can be integrated into the SOA concept in a
flexible and cost efficient way.


Net
-
Centric Services Framework (NCSF), Ver
sion 1.0, December 1, 2008, Robert Palmqvist,
Saab, Lars Schylberg, Saab, and Allen Jones, Boeing, Developed on behalf of
Network
-
centric
Operations Industry Consortium

(NCOIC), 53 pages.


Emerging Technologies in Social Networking
, National Academy of Sciences

2009 Annual
Meeting of the Transportation Research Board, Hilton Hotel, Washington, DC. Jefferson East
Room. January 13th, 10:15 AM
-
12
:00 PM.


From E
-
Gov to Connected Governance
: The Role of Web 2.0 and Web 3.0 Semantic
Technologies, Semantic Community

Semantic Exchange Workshop, Februa
ry 17, 2009
.
6. A
ppendices


A.
Thoughts on Target Architecture and CPIC Integration December 22, 2008 (Updated
January 5, 2009)


Lisa, I liked your presentation at the IIS Meeting that the Target Architecture would address
SOA, Web 2.0, and Cloud Computing
, and that the number of segments should be reduced and
aligned with the Strategic Plan Goals. I made the suggestion that the segments should be aligned
with the Report on the Environment Topics (my Ontology for EPA Segment Data Architecture)
and have hear
d the suggestion that they be aligned with the BRM. I think we need to further
discuss the number and alignment of segments, but also include in the Target Architecture 2009,
its closer integration with CPIC which itself is defined as the structured, integ
rated approach to
managing IT investments to ensure that all IT investments align with EPA Mission/Goals and
Business needs (BRM).


Since this is and should be all related and integrated, suggest the following structure:


Target Architecture 2009 Technolo
gies: SOA, Web 2.0, and Cloud Computing


Target Architecture 2009 Method (Architect, Invest, Implement): A Specific Example SOA:
Web services from major systems (e.g. EPA and USGS Water Quality Web Services) Web 2.0:
Mashup using the the Water Quality Web
Service (piloted recently using the IBM Greenhouse
Toolkit for example)


Cloud Computing: IBM Greenhouse Toolkit is a cloud computing application that could be used
in one of three ways by EPA (IBM hosts it, EPA hosts it, it is hosted in a Federal
-
Secure c
loud).


Now there

is an investment/cost associated with each of these as follows:


SOA/Web services: The major (and minor) systems should be required to make progress towards
this as part of their annual (now quarterly) process. I have proposed a Maturity
Matrix to track
and explain this to senior management (see below).


Web 2.0/Mashup: This would be part of the new IT Infrastructure Segment where EPA would
have some sort of Service
-
Level Agreement to deliver these services for the entire agency and
even t
hose it collaborates with on using (reusing) EPA and other data sources.


Cloud Computing/Tools: This would also be part of the new IT Infrastructure Segment where
EPA would have some sort of Service
-
Level Agreement to deliver these services for the entire

agency and even those it collaborates with on using (reusing) EPA and other data sources.


Federation of Deki Wikis as Web Services in a SOA Conference presentation at
http://semanticommunity.wik.is/@api/deki/files/1288/=BNiemannGov204252008.ppt


Pilot Example: Chesapeake Action Plan:
http://chesapeakeactionplan.wik.is/


SOA/Web Services Maturity Matrix for Sen
ior Management


The first column would list the EPA Systems

The next three columns would list three performance/maturity measures as follows:

1. The system has a data architecture and description of interfaces to other systems for
information sharing

2. Th
e system has a data dictionary and data quality plan

3. The system has exposed its data by state
-
of
-
the
-
art web services and is participating in
collaborative development of a SOA for the agency and its partners


I hope that we can discuss these ideas at t
he Target Architecture and EA WG meetings in
January or before if you are around. Brand


B.
Preliminary
Announcement


The combination of the four

events during a "Federal Cloud Computing Week" should increase
participation at all of them especially for peo
ple who have to travel to DC. In particular, it would
help publicize the events and draw senior representatives of Cloud Resource Providers and
potential customers.


April 28, 2009, Federal SOACoP/MITRE Conference on Cloud Computing and SOA (Brand
Niemann
)
http://federalsoa.wik.is/


April 29, 2009, 1105 Media Group Cloud Computing Conference & Exhibition (Christina
Condos)
http://events.fcw.com/E
ventOverview.aspx?Event=CLC09



April 29, 2009. Federal Cloud Camp (Kevin Jackson) (late afternoon/evening)
http://www.cloudcamp.com/


April, 30?, 2009, Cloud Computing for Tactical Networks (OSD NII) (Bob Marcus
)

http://federalcloudcomputing.wik.is/