SOA Implementation Issues BJA Regional Information Sharing Conference Jacksonville, Florida June 6, 2007 Scott Came Director of Systems and Technology SEARCH

Recap of Yesterday

SOA Implementation So, if SOA is the right style for your information sharing architecture, how do you “do” it?

Key Issues What terminology do we use? How do we identify and describe services? What is a good service? What protocols define interactions? What shared infrastructure do we need to support interactions? How will we adapt existing capabilities? How do developers find services and descriptions? How do we manage and govern services and shared infrastructure?

Adopting the style What kinds of choices tend to result from SOA adoption? Provisioning (shared services) Models Independence Location (registry) Controlled vocab Repositories SOAP XML WS-* Agility Emphasize that SOA is not primarily about implementing particular infrastructure…it’s more about adopting a philosophy to guide your information sharing and integration architecture/approach. Thus the proper way to talk about SOA implementation is the kinds of implementation choices that result from adopting the style. Also discuss how SOA adoption is the iterative pursuit of a continuum. There are things you can do to “tend towards” the style without doing it all. Infrastructure investment (and investment strategy) depends on where you are on the continuum. Each step also introduces additional governance issues, skills needs, risks, etc. Shared Message Transport Separation of Business logic (intermediaries) Event-driven architecture Industry Standards Standard messages (IEPDs)

Discussion Introducing: Kael Goodman GovCore Solutions kael@govcore.com 212-420-7870

Director, Systems and Technology Contact Information Scott Came Director, Systems and Technology SEARCH scott@search.org 916-212-5978