1. Current State of Affairs in SOA Along with Migration Strategies and Methodologies www.oasis-open.org John Harby

2. John Harby is currently working with MIRO Technologies, a global aerospace defense contractor headquartered in San Diego. He specializes in the SOA and middleware areas. He is a member of several OASIS Technical Committees and is also on several JSR expert groups.MIRO Technologies He was co-author of The Middleware Company SOA Blueprints initiative. He has previously worked in product development for vendors including Oracle, BEA Systems and was a Sr. Architect in the HP Web Services (e-speak) lab. His first experience in SOA was in the mid-90's developing systems for U.S. Intelligence using CORBA/C++

3. PGFSOA n Practical Guide to Federal SOA n Are using OASIS standards such as the SOA Reference Model n Still accepting volunteers

4. The Standards have Arrived n OASIS SOA RM, SCA, SDO n WS-Transaction n WS-Addressing n Etc.

5. Product Maturity n Orchestration – IBM, BEA, Oracle, et al are maturing n Registries, ESBs, etc. also no longer new n Many support tooling now exists, e.g. management tools

6. Open Source Contributions n JBoss – jBPM, ESB n Mule ESB n ServiceMix n Synapse

7. External to Technology n Governance n Methodologies n Management

8. REST Approach n Further decoupling through abstraction of contract n Lack of declarative standardization n Can one use REST within SOA?

9. Practices, What Works? n Choose pilots carefully n Governance always comes first n Vendor selection matters even more

10. Practices, What Works? n SOA as a pattern n Migration strategies n Platform integration

11. Novel approach – AOP/SOA n Services can be woven rather than orchestrated. n Especially useful for lightweight services with many join points. n Examples, logging, properties, etc. The Jaffa framework employs some of these strategies.

12. REST – Friend or Foe n REST exhibits more simplicity than the other alternatives n REST offers further decoupling than SOAP/WSDL/etc. n REST potentially violates the SOA contract requirements

13. ROA vs. SOA n My opinion is to strive for a blend n OASIS SOA-RM: “A contract … represents an agreement by two or more parties” n Does the level of abstraction of the contract really matter?

14. Why does this matter? n Adds capability to the SOA n Further enablement of end-end enterprise architecture

15. Platform migration n Seek a generalized methodology n Migration strategies are available n Initially target the “low hanging fruit”

16. SOA Migration Path

19. Some Interesting Links n Web Methods SOA Master Class: http://www.soamasterclass.com/index.php?option=com_content&task=view&id=74&Itemid=88888 964 http://www.soamasterclass.com/index.php?option=com_content&task=view&id=74&Itemid=88888 964 n Estimate SOA costs: http://weblog.infoworld.com/realworldsoa/archives/2006/11/how_much_will_y.html http://weblog.infoworld.com/realworldsoa/archives/2006/11/how_much_will_y.html n REST FAQ: http://rest.blueoxen.net/cgi-bin/wiki.pl?RestFaq http://rest.blueoxen.net/cgi-bin/wiki.pl?RestFaq n Two IBM SOA success stories: http://www.soainaction.com/blog/2007/03/post_4.php http://www.soainaction.com/blog/2007/03/post_4.php n Web Services Standards poster: http://www.innoq.com/soa/ws-standards/poster/ http://www.innoq.com/soa/ws-standards/poster/