service oriented architecture (soa) at nih bill jones [email protected]

Service Oriented Architecture (SOA) at NIH

Bill Jones

[email protected]

Website: http://EnterpriseArchitecture.nih.govContact: [email protected]

What is SOA?

• In a Service Oriented Architecture (SOA) implementation, an application’s business logic functions are modularized and presented as “black box” services for other applications to consume.

• The services are “loosely coupled” and independent of implementation and should be designed to support specific business processes. The providing application owns the service and interface definitions.

• Developers can build applications by consuming services without knowing the underlying implementations.

• Services are reusable across applications, which greatly reduces application development costs over time.

At NIH, the heart of our SOA implementation is an enterprise service bus (ESB) which hosts service interfaces to enterprise applications.

http://www.youtube.com/watch?v=-9zgeS9B2NE&NR=1


What is SOA Continued

SOA is a services driven design approach that integrates business and IT strategies to provide Common Services that leverage existing and new functionality

The strategy of SOA includes:• Integration with NIH strategic Planning • Providing modernization through the sharing & reuse of services across the enterprise• Streamlines existing business processes for greater efficiency and productivity

• The approach for SOA:• Leverage existing IT investments and open standards• Connect applications and data to deliver connectivity and interoperability• Reduce redundancy in functionality and data stores

• Development using SOA:• Shifts the focus from writing and rewriting code to application and service assembly• Promotes the use of consistent design patterns and tools across development efforts

• Standards allow applications to be designed for reuse• Components that can be used over and over again• Standardized interfaces and standard data definitions• Business logic is separated from the infrastructure


SOA at NIH

• The SOA effort at NIH began about 3 ½ years ago on the recommendation of the Applications Integration Domain Team

• A project team was formed to determine the utility of SOA for NIH, evaluate products, and select an Enterprise Service Bus (ESB) on which to build an infrastructure.

• The project team found great potential utility for SOA at NIH and selected TIBCO software.


SOA at NIH Continued

• NIH Chief Architects Office agreed to provide initial funding.

• Integration Services Center (ISC) created to maintain infrastructure and provide a center of excellence for SOA – http://isc.nih.gov.

• Integration Oversight Committee (IOC) formed to provide high level governance.

• SOA infrastructure based on TIBCO software and a series of Infrastructure Services announced in May 2007.


SOA Infrastructure Services

The NIH Integration Service Center (ISC) manages the following service interfaces to enterprise applications:

• Extract/Publish Changes to NED Data Services• NED Person Data Web Service• Commons Person Data Web Service• Security Training Data Web Service• Create Requisition Web Service• Travel Data Web Service• Vulnerability Tracking Data Web Service• FTP Data Web Service


SOA Usage Chart

ISC Infrastructure Web Service Usage

0

2000

4000

6000

8000

10000

12000

14000

16000

October 07 November 07 December 07 January 08 February 08 March 08 April 08 May 08 June 08

Month

Ser

vice

Invo

cati

on

s

PublishHRChange

SQL to Excel

Vendor Info

Create Requisition

Travel

FTP

Tech Transfer

Security Training

Commons Person

Ned Person


Why Modernize with SOA?

• Point to point integration is much more difficult to maintain

• Lots of custom software development

• Difficult to share and collaborate

• Too many proprietary systems and related training and maintenance

• Hard coding makes it difficult to change/add/remove, and Retire

• Inflexibility to address new technology and business directives

• Can’t readily support process level integration

A pplication

A pplicationA pplication

A pplication

L o a dP r o g r a m

E x t r a c tP r o g r a m

E x t r a c tP r o g r a m

L o a dP r o g r a m

E x t r a c tP r o g r a m L o a d

P r o g r a m

Dow nloadFile

Dow nloa dFile

Transaction

File

M essageQ ue ue

Dow nloadF ile

T ransaction

F ile

M essa geQue ue

BusinessUnit B

BusinessUnit A

BusinessUnit C



A pplication

Legacy of Point to Point Solutions


What SOA Means for App DevelopmentBusiness Requirements

Context

Simplification • Reduce the complexity of existing systems by decomposing into common services• Reduce the amount of custom code

Service Reuse • Leverage common application and infrastructure services to achieve operational efficiencies, and cost savings

• Lower costs required to maintain complex systems to free capital for value added capabilities• Enable modernized applications to leverage CPE based services

Agility • Create a business and technology architecture that can support changing regulatory, business and customer needs

• Unlock the power of data for transformation of the business• Create a flexible architecture

Enable Transformation

• Support a phased modernization (Transformation) that leverages both legacy and new technologies

• Proactively blur the legacy and modernization boundaries through enterprise common services• Reduce time to market

Regulatory Requirements

• Federal Enterprise Architecture Service Reference Model• Treasury Enterprise Architecture Service Reference Model• OMB EA Assessments, Clinger Cohen Act, Federal Transition Framework

Security Requirements

• GAO Oversight Findings on Security• Establish Common Security Services• Reduce Complexity of Security Solutions


Examples at NIH

• Automated requisition submission– Developed by NBS in support of NIAID/AMBIS– Can be used by NINDS POTS with minimal cost and

coding

• Funds check and automated PO submission– Developed by NBS in support of eTravel– Can be used by eRA for on line grants funding

• Security Training service provides business logic for AD account and VPN registration compliance


SOA at NIH Next Steps

• Work with NIH application developers to use existing services.

• Work with NIH business owners to identify and implement new service opportunities.

• “Spread the SOA word” to the NIH community.

service oriented architecture (soa) at nih bill jones [email protected]

Documents