AGENDA: 10.00 - 11.00 Patterns in the Enterprise 11.00 - 11.30 Break

2. AGENDA:10.00 - 11.00Patterns in the Enterprise 11.00 - 11.30 Break 11.30 - 12.30Integration Patterns 12.30 - 13.30 Lunch 13.30 - 14.30 Showcase 14.30 - 15.00 Break 15.00 - 16.00Web Services: Interoperability and Integration 16.00 - 16.15 Summary - The book ? Questions ? Visual Studio 2005 Beta ? Review form ?

3. AGENDA:10.00 - 11.00 Patterns in the Enterprise Repeatable success in delivering complex enterprise systems depends on the ability to leverage experience from past systems. On an architectural level, direct reuse is usually not practical and blueprint architectures are often not flexible enough for complex systems. However, design patterns provide a middle-ground by describing idiomatic use of technologies and capturing the essence of successful designs. Erik Doernenburg is a Senior Developer and Architect at ThoughtWorks, Inc. Coming from a background in enterprise applications and new media systems, Erik is currently exploring advanced patterns of enterprise integration and application architecture on the Microsoft .NET and J2EE platforms. Erik has been an advocate of domain-driven design and agile development for many years. Erik holds a degree in Informatics from the University of Dortmund.

4. AGENDA:11.30 - 12.30 Integration Patterns Based on the Integration Patterns book from Microsoft's Patterns & Practices team, this session discusses how patterns can be used to describe an integration architecture from business to implementation. Christopher Baldwin is an Architect with the Microsoft EMEA Developer and Platform Evangelism Group. With 25 years experience in software engineering across numerous environments, Christopher now helps enterprises leverage the Microsoft .NET platform. Prior to joining Microsoft 9 years ago, Christopher’s background was in the financial industry. Christopher’s latest studies are in the software factories area. Christopher holds a Bachelor of Science degree in Computer Science from Westminster College.

5. AGENDA:13.30 - 14.30 Showcase Know IT presents an integration solution in Microsoft BizTalk Server using integration patterns and a SOA based architecture. Anders Kingstedt has been active in the IT industry since the latter part of the 80’s, previously working as a developer and systems designer. Having worked in the web industry for a few years, Anders is currently employed as a consultancy manager at Know IT, focusing on integration solutions. Anders is also the Alliance Manager with Microsoft at Know IT. Alan Smith is a BizTalk expert and the only BizTalk MVP in Sweden.Alan is form the north of England, and living in Stockholm Sweden, he has been working as a developer with Microsoft technologies since 1995.

6. AGENDA:15.00 - 16.00 Web Services: Interoperability + Integration This session addresses the use of web services to build highly interoperable solutions that fit into an enterprise integration architecture. Daniel Akenine is an Architect Evangelist at Microsoft. For the last five years he has been focusing on Enterprise Application Development – on both the J2EE and Microsoft platforms. Previously he has been working as a researcher at Karolinska Institutet, division IT-manager at the Karolinska Hospital and as a technical specialist and counsellor for a number of IT projects in the Stockholm Financial Sector – e.g. the OMX stock exchange. Daniel holds a M.Sc in Engineering Physics.

7. Theme • Interoperability + Integration > open • Interoperability • Able to operate in conjunction1 • Integration • Combining of diverse parts into a complex whole1 • Open • Open system, open source, open solution 1 Definition from Oxford Dictionary

8. ThoughtWorks at a Glance Industries: > Insurance > Asset Finance > Mortgage > Retail • Expertise: • > NET • > Java • > SOA • > EAI • > Open Source • > Agile • > DA Company: > 600 employees > $80M in revenue > Global WW Reach > Major corporations < ThoughtWorks’ publications

10. Web Services:Interoperability + Integration Daniel Akenine Architect Evangelist dakenine@microsoft.com

11. Are we serious ? • 3 feb – 2005: Bill Gates and interopability • “interoperability is a proven approach for dealing with the diversity and heterogeneity of the marketplace ..” • Our strategy: Work with what you got: • Host Integration Server, BizTalk, Identity Integration Server • AppleTalk, Netware, Unix/Linux, C++, JAVA, Oracle, Sybase, DB2, SAP, Siebel, SWIFT, HL7, Use XML to get "Interoperability by Design“ • Office XML, WS-*

12. Agenda • - Service Oriented Architecture • - Web Services and Integration • - Web Services and maturity • - Services in the future

13. Agenda • - Service Oriented Architecture • - Web Services and Integration • - Web Services and maturity • - Services in the future

14. Why are we talking about SOA today ? • It is not the strongest of the species that survive, or the most intelligent, but the ones most responsive to change.- Charles Darwin

15. Treasury / Forex Payment Systems and Card Mgmt 3D Secure Trading / Back office Wealth Management Core Banking Branch Banking Internet Banking EAI Aggregation Wireless ATM / POS No Application Is An Island Business Intelligence Straight through Processing CRM

16. Devices User interface Services Infrastructure The “service oriented enterprise”

17. Services and Systems are not the same • A service is a program you interact with via message exchanges • Services are built to last • Availability and stability are critical • A system is a set of deployed services cooperating in a given task • Systems are built to change • Adapt to new services after deployment

18. What is Service Orientation (SO)? • An approach to building systems using services which adhere to the 4 tenets of Service Orientation: • Boundaries are Explicit • Services are Autonomous • Services share schema and contract, not class • Service compatibility is determined based on policy

19. Understanding Tenet 1: Boundaries are Explicit • Each Service interaction is a boundary crossing • Crossing service boundaries may have costs • Service Orientation makes interaction formal, intentional, and explicit Respect my Boundaries.

20. Understanding Tenet 2: Services are Autonomous • Topology of a system evolves over time • No presiding authority • Services in a system are deployed, managed, versioned independently Don’t be Codependent.

21. Understanding Tenet 3: Services Share Schema and Contract, not Class • Services interact solely on schemas for structures, contract for behaviors • Unlike OO classes, services do not combine structure and behavior • Contracts and schema remain stable over time Don’t (expect me to) overshare.

22. Understanding Tenet 4: Service Compatibility is Determined Based on Policy • Separates the interactions the service can have from the constraints on those interactions. • Service capabilities and requirements are expressed in terms of a policy expression • Assertions identified by stable, globally unique names The fact that I can, doesn’t mean I will.

23. Complexity Complexity Service-Oriented Architecture From Tightly Coupled Objects… To Loosely Coupled Services Your Partner You Programming Language Programming Language Database Database Agreements Object Model Object Model Contract Operating System Operating System Application Application

24. Architecting with ServicesPromoting Loose Coupling Service provider Service consumer How is it implemented? What does it do? How does it work? Contract How to use it? How to build it? Where to host it? Where to find it? How to publish it?

25. What kind of tools do we need to do SOA ? • “A fool with a tool is still a fool :-)” • - Old saying

26. Process and Architecture Guidance Static Code Analyzer Change Management Work Item Tracking Reporting Project Site Integration Services Dynamic Code Analyzer Build Server Code Profiler Project Management Visio and UML Modeling Code Coverage Unit Testing Application Modeling Manual Testing Logical Infra. Modeling Class Modeling VS Pro Team Foundation Client Load Testing Test Case Management Deployment Modeling Visual Studio Industry Partners Visual Studio Team System Visual StudioTeam Architect Visual StudioTeam Developer Visual StudioTeam Test Visual StudioTeam Foundation

27. Logical Infra. Modeling Deployment Modeling Application Modeling Class Modeling Process and Architecture Guidance Code Profiler Change Management Work Item Tracking Reporting Project Site Integration Services Project Management Static Code Analyzer Unit Testing Dynamic Code Analyzer Visio and UML Modeling Code Coverage Logical Infra. Modeling Application Modeling Manual Testing Team Foundation Client VS Pro Build Server Load Testing Test Case Management Deployment Modeling Visual Studio Industry Partners Visual Studio Team System Visual StudioTeam Architect Visual StudioTeam Developer Visual StudioTeam Test Probably the best development tool in the world :-) Visual StudioTeam Foundation

28. Service-OrientedArchitecture model Number 1Application Designer Port Details editor

29. Logical Infrastructure Designer Number 2 Infrastructure Designer Services assignedto logical infrastructure Architecture validatedagainst operationalsettings and constraints

30. Class Designer Class Designerandtwo-way code synch And the last.Class designer

31. Agenda • - Service Oriented Architecture • - Web Services and Integration • - Web Services and maturity • - Services in the future

32. "Every generalization is dangerous, especially this one." — Mark Twain • Web services is the only way to do integration !

33. Security Transactions Reliable Messaging Metadata Messaging Security Transactions Reliable Messaging XML Metadata Messaging XML A basic web service is not always OK ! • Security • Encryption • Authentication • Authorization • Non-repudiation • Federation • Trust • Reliable Messaging • Guaranteed delivery • In order processing • Idempotency • Transactions • Coordinated activity • Atomic transaction • Business activity • XML • Data • Schema • Interoperability • Messaging • Functional data • Operational data • Address services & resources • Attach binary data • Metadata • Service description • Policy • Discovery

34. WS-I Integration Orchestration Security Adapters Security ebXML MSMQ JMS JTA JCA ES .NET J2EE CLR JVM Windows Linux

36. Enterprise DCOM Integration? Database Server Components Client Application (VB6, Delphi or PowerBuilder) Existing Client/Server Application

37. Enterprise C/S 1: Expose Database Web Service Façade DCOM Database Server Components Client Application (VB6, Delphi or PowerBuilder)

38. Enterprise C/S 2: Expose Server Web Service Façade DCOM Database Server Components Client Application (VB6, Delphi or PowerBuilder)

39. Enterprise C/S 3: Expose Client Web Service Façade DCOM Database Server Components Client Application (VB6, Delphi or PowerBuilder)

40. Web Services: Messaging and more • Web services provide the benefits of messaging • loose-coupling • service oriented • And more • vendor neutral • suitable for access through Internet

41. Web Services: Tenets • Boundaries are explicit • Services are autonomous • Services share schema and contract • Service compatibility is based on policy • Tenet conformance gives better Interoperability • Better Interoperability means stronger Integration

42. Web Services: Active community • Web Services are expected to become the default Messaging solution in the future • WS-* standards are evolving rapidly, most important • WS-Security • WS-Policy • WS-Addressing • WS-I defines profiles, sample applications and testing tools • Profiles are guidelines for using WS specifications • Use Basic profile 1.1 to build interoperable solutions • Further research on WS is being carried out

43. Why integrate through Web Services? • To get • Messaging and more • Tenets • Active community • Required for external integration • Beneficial for internal integration

44. Building Interoperable Web Services

45. Agenda • - Service Oriented Architecture • - Web Services and Integration • - Web Services and maturity • - Services in the future

46. The Web Services Maturity Model Drivers Technical Business Enterprise Industry/ Ecosystem Service Perspective TechnicalInterface BusinessCapability BusinessProduct Domain Standard Service Deployments Integrated Architected Measured and Managed Federated Collaborations Internal Limited External Virtual Business Anonymous Service Process Momentum Extended Momentum Reengineered Standardized Early Learning Integration Reengineering Maturity

47. Phase 1 - Early Learning • In this phase the predominant service deployments will be: • Mostly internal • Low-risk external • Using existing security mechanisms • Not mission critical • Focused on better application integration

48. Phase 2 – Integration • Business process oriented • Project level implementation • Mostly internal usage

49. Phase 3 – Reengineering • Enterprise level, with common services used right across organizations • Services implemented as an integral part of business products • Supported by guarantees and standards based measurement and monitoring systems

50. Phase 4 – Maturity • Services are ubiquitous • Federated services collaborate and create complex products with individual services provided from potentially many providers • Services are designed to support the consumer in their ecosystem, not in a company specific system or service