Service Oriented Architecture (SOA) Enterprise Architecture (EA) Enterprise Service Bus (ESB)

1. Service Oriented Architecture (SOA)Enterprise Architecture (EA)Enterprise Service Bus (ESB) Yale Solutions Design October 2012

2. Current Integration Challenges All issues, technical and non-technical need to be addressed in order to effect positive architecture change across the enterprise. • Each team follows unique standards for technology selection, design, build, and deployment • Connectivity is point to point and not reusable • Projects are always time bound which forces teams to make decisions at the project level • Improvements happen at the team or project level

3. Current Integration Challenges: Results Fortunately there is a proven way forward! It will require a significant paradigm shift, however. • Few assets/services are shared/reused (even within teams) • Redundancies may exist (which yield disparate results) • The Development teams operate within their respective domain and are therefore unable to collaborate on standards • There is inconsistent behavior across teams in terms of solution delivery • Clients miss opportunity to benefit from team collaboration • Separate, discreet application construction and deployment does not scale

4. 4 Sample EDS System Connectivity

5. Definitions Page What is an Enterprise Service Bus (ESB)? • A secure and robust middleware environment that enables systems to interoperate independently of technology • An integration facilitator that allows internal and external systems to share information • Implements SOA through Virtualization and management of service interactions What is Service Oriented Architecture (SOA)? • An architecture strategy that drives a close alignment to the business by deconstructing IT systems into discreet services that perform business functions • Services communicate via the ESB and may be reused • Can drive architecture disintermediation via the composition of independent services into mashups or apps • Examples: search, impersonation, login, person lookup, course lookup, etc.

6. Why do we need an ESB and SOA? • Systems no longer connect directly thereby allowing greater control and enforcement of the following principles: • Standards • Security • Governance • Reusability • Consistency • Data Integrity • We can build and leverage a suite of business services that can be assembled into composite applications • Multiple channels (Web, Portal, Cloud, etc. ) can be authenticated to access shared services • Data synchronization managed through the ESB • Publish/Subscribe queue

7. Additional Benefits and Opportunities • Standardized, Streamlined, and Simplified Architecture • Teams spend less time on complex and redundant architectures and now focus on business process, reuse, and quality • ITS team focus, collaboration, and consistency • SOA practices enable ITS to shift focus to becoming a ‘Change Ready’ and ‘Change Enabled’ organization • Teams collaborate to build shared services vs. siloed applications • Individual customizations replaced by standardized and governed practices • Improved Customer Service • Client benefits range from helping define business services and processes, to being able to consume shared services • ITS’ ability to adapt to changing business needs enables positive and consistent business process improvement • Clients move from being ‘customers’ to ‘partners’

8. Cost/Relationship Savings Opportunities One time • Service Reuse • Maintenance reduced through consolidation and reduced redundancy of business functionality • Pre-built services pulled ‘off the shelf’ to compose applications thereby reducing the time to build and deploy (same as COTS) Recurring • Operational costs • Maintenance and support of services • Improved System Quality • Deployed services are certified thereby reducing defect remediation • Improved Data Quality • Redundant data access minimized and replaced by standardized data services that can be reused by authorized personnel

9. Enterprise Service Bus Basic “Service Based” Architecture The initial SOA architecture includes the creation of reusable interface services that connect disparate systems. Enables initial system/data decoupling. Med Apps Systems CIMS Teaching Fellows Users Services Services (Global or Local) Transport Layer Services HR DW Banner

10. ESB Future SOA Environment (Sample) New applications will take full advantage of composite applications via services. User interface is completely decoupled from the data source. Web Access Mobile Cloud Vendors Vendor Packages Standard access mechanism Data Service Data Service Data Service Data Service System of Record DW Banner Alumni HR

11. Data Synchronization with Queues Change events are published to a common transient queue where multiple applications can subscribe to the same topic App 1 App 2 App 3

12. “Build-to-Change” versus “Build-to-Last” The SOA Imperative:

13. SOA Services Strategy and Delivery SOA lifecycle management moves us from a linear thinking mode to a circular or evolutionary process. Start Evaluate, Enhance, De-commission Identifyand Define Governance Governance Monitor Develop/Modify Test/Deploy

14. Community / ITS Relationship • The alignment between the community and ITS can be improved and facilitated through a well-defined and governed Enterprise Architecture process • Enterprise Architecture is a Critical Success Factor for the entire Yale community to achieve their expected results

15. Enterprise Architecture The ESB and SOA technologies are enablers: The end goal is managed Enterprise Architecture. • Links ITS to the Yale Community by translating Yale’s vision and strategy into scalable and adaptable technology principles and models • Manages current and future state technology vision • Enables a ‘going in position’ when evaluating software, vendors, or new projects • Manages risk and cost through standardization, reusability, and governance • Consistently maintains a view at the enterprise level to ensure efficient utilization and orchestration of all resources

16. Enterprise Architecture Enterprise architecture principles drive a global perspective within an organization across business, data, application, and technology domains.

17. 17 Starting with a Mission The Mission should define the strategy and all activities should map back and fully support it Data Architecture Define, support, secure, and maintain the types, sources, and relationships of data necessary to enable the goals of the organization in a way that is complete, consistent, trusted, and understandable by all constituents.

18. Why Focus on Architecture? IT Strategy Business Strategy Enterprise Architecture • Enterprise Architecture provides the tight cohesion and loose coupling between IT and Business strategies • It is the ‘glue’ that ties together Business and IT strategies and enables them to drive each other • Enterprise Architecture can provide the technology innovation engine that enables ITS to better serve business partners

19. Benefits of SOA • Respond Better, Faster, Cheaper to Change • Align ITS with Business • Agility, Flexibility • Reusability • Improved Quality • Platform, Technology Independence • Reduced Redundancy Responding to Business Change via Architecture Managing Change is Key Business Driver • Change is Constant • Customer Needs • SaaS / PaaS Solutions • Vendor Solutions • ITIL • Legacy System Support • Integration across all environments

20. “Build-to-Change” versus “Build-to-Last” The SOA Imperative:

21. ‘Change Ready’ Organization • Flexibility • Speed • Agility • Adaptability • Responsiveness • Thoughtfulness • Innovation • Collaboration • Rapid Evolution • How do we accomplish this? • Organizational alignment • Tools • Architecture • Processes • Mind-set • Commitment ...Leveraging our Strengths

22. Why focus on Change Readiness now? • Strong need to integrate disparate environments to ensure consistency and data synchronization across all platforms. • Key Building Blocks and Drivers are in-place or underway • ITIL • Relatively new organizational model • Student Information Systems (YaleBluebook, Leep Frog, etc.) • Cloud Vendor proliferation (SalesForce, ServiceNow, QB, etc.) • Rethinking ERP environment • DARCY / Blackbaud • Identity and Access Management Initiative

23. What will this do for us??? • If we are successful, we will become • Able to adjust to any newer technology or business trends more rapidly and calmly • Able to integrate both internal and external systems and data in a consistent manner that models our standards • Able to drive more effective and consistent technology decisions through a well thought out strategic architecture plan • More effective at collaboration between teams and with our customers • Better service providers to our customers

24. Current Services Status

25. Change Management for SOA & EA ITS needs to embrace five key aspects of change management as we move forward toward general adoption.

26. Thank you for your time!

27. Appendix