Service Oriented Architecture (SOA) at NIH Bill Jones wkj@nih

1. Service Oriented Architecture (SOA) at NIH Bill Jones wkj@nih.gov

2. 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 Website: http://EnterpriseArchitecture.nih.gov Contact: EnterpriseArchitecture@mail.nih.gov

3. 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 applicationsto 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 Website: http://EnterpriseArchitecture.nih.gov Contact: EnterpriseArchitecture@mail.nih.gov

4. 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. Website: http://EnterpriseArchitecture.nih.gov Contact: EnterpriseArchitecture@mail.nih.gov

5. 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. Website: http://EnterpriseArchitecture.nih.gov Contact: EnterpriseArchitecture@mail.nih.gov

6. 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 Website: http://EnterpriseArchitecture.nih.gov Contact: EnterpriseArchitecture@mail.nih.gov

7. SOA Usage Chart Website: http://EnterpriseArchitecture.nih.gov Contact: EnterpriseArchitecture@mail.nih.gov

8. Why Modernize with SOA? Legacy of Point to Point Solutions • 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 Website: http://EnterpriseArchitecture.nih.gov Contact: EnterpriseArchitecture@mail.nih.gov

9. What SOA Means for App Development Website: http://EnterpriseArchitecture.nih.gov Contact: EnterpriseArchitecture@mail.nih.gov

10. 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 Website: http://EnterpriseArchitecture.nih.gov Contact: EnterpriseArchitecture@mail.nih.gov

11. 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. Website: http://EnterpriseArchitecture.nih.gov Contact: EnterpriseArchitecture@mail.nih.gov