Planning
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
454
On Slideshare
454
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
1
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Copyright UC Regents 2006. This work is the intellectual property of the author. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission of the author. To disseminate otherwise or to republish requires written permission from the author.

Transcript

  • 1. Planning & Delivering Service Oriented Architecture (SOA) University of California, San Diego May 24, 2006 © Copyright UC Regents, 2006
  • 2.
    • About UCSD
    • What is SOA?
    • Why Implement SOA?
    • Implementation Challenges
    • The UCSD SOA Framework
    • UCSD Examples Experiences and Case Studies
    • Q&A
    Topics
  • 3.
    • 26,100 Students
    • 23,500 Employees (Including Medical Center)
    • $1.9 Billion Annual Budget
    • $728 Million Annual Research Funding
    • _______________________________________________________________________________________
    • IBM Mainframe and Sun Solaris Servers
    • Java (J2EE)
    • DB2
    About UCSD
  • 4. External Recognition
    • UC San Diego and the University of Minnesota cited as best practices in December 2005 cover story about administrative cost savings in universities
  • 5. External Recognition
    • “ Using a combination of technological and organizational resources, UCSD fosters a continuous improvement cycle that constantly strives to enhance university business operations.”
    • Nov. 2005 Study by the Educause Center for Applied Research
  • 6. The New Business Architecture
  • 7.
    • Ease of Use and Access
    • Common Look & Feel
    • Web-Based Systems
    • Interoperability and Open Architecture
    • Single Signon
    • Evolution v. Revolution
    • Cost-Effectiveness
    About UCSD UCSD Goals:
  • 8. About UCSD: Business Portal
  • 9. About UCSD: MyDashboard – Leave Activity Report
  • 10. About UCSD: MyDashboard – Financial Information
  • 11. SOA Alphabet Soup
  • 12.
    • Web
    • Life-cycles continue to shrink
    • Systems constantly changing for business needs
    • Regardless of platform, DB, technology – all systems need to:
      • Interoperate
      • Communicate
      • Integrate
    • Leverage departmental IT staff in enterprise development
    IT Challenges
  • 13. Architecture Needs
      • Loosely-coupled with reusable components
      • Promote productivity - reduce the time-to-market
      • Greater business agility
      • To drive business processes closer to end users
      • Technology independent
      • Leverage and integrate existing applications
      • Provide standard connections between systems
      • Abstract the complexity for the developers
  • 14.
    • What is SOA? SOA (service-oriented architecture) is a broad framework within which enterprises build, deploy, and manage services; these services are application components that can be called upon by other applications using standard protocols . The primary objective is a more agile application infrastructure that responds swiftly to shifting business demands.
    What is Service-Oriented Architecture?
  • 15. What is a Service?
    • Services are application components that are available to other applications using standard protocols (typically XML)
    • Examples:
      • Create a PO inside a mainframe application
      • Retrieving & updating student info
      • Reviewing & changing HR benefits
  • 16. What is a Service
  • 17.
    • Analogy to A/V Components
    • Years ago electronic systems were self-contained monolithic systems
    • Today’s electronics are pluggable and independent
    • Standardized connections.
    What is SOA?
  • 18. Benefits of SOA
  • 19. Key Components of a SOA
    • A service oriented architecture is a software architecture that is based on the following key concepts:
      • A service consists of a contract, one or more interfaces and an implementation
  • 20. Using a Service
    • Development time discovery imposes a fairly simple model. The developer is responsible for locating all required information from the service repository in order to create a client that interacts correctly with the service instance.
  • 21. A Service Example
  • 22. Planning for SOA @ UCSD
    • Approach:
      • Think strategically and plan tactically
      • Evolutionary not revolutionary
      • Focus on approach, not technology
      • “ Leave & layer vs. rip & replace” Gartner Group
      • Make it easy for developers to adopt
      • Natural progression of original OO Architecture and Approach
      • Not going to happen overnight- It takes time: “the true adoption is about two years behind the hype”. Gartner Group
  • 23. Planning for SOA @ UCSD
    • Process
      • Experiment with Web Services
        • Small project high degree of success
        • Helpful not vital
      • Adapt some existing systems to use Services
      • Remove Intersystem dependencies
      • Establish an Internal SOA
      • Expand Internal SOA to include external services.
  • 24. Single Sign-On
    • Uses Shibboleth for Authentication http://shibboleth.internet2.edu/
    • Supported on different platforms (based on SAML)
    • Uses UCSD Roles & Affiliates as the data repository for authentication and authorization
    • Part of the UC-Trust Collaboration project for cross-campus identity management.
  • 25. Case Study - MyRecords Portlets
    • Student portlets are provided through the MyRecords tab.
    • Each portlet is populated from a web service.
    • Information comes from either the mainframe or data warehouse.
    • Portlet content is cached and managed through event driven messages which implement the cache policy.
  • 26. ElementK Integration
    • UCSD supplies the Portal top banner navigation, page footer and right sidebar
    • Single Sign-On provides user pass through from UCSD portal to KnowledgeHub.
    • Web Services create user account at the time of login.
    UCSD Portal KnowledgeHub Integration
  • 27. Implementation Challenges
    • Technical Challenges
      • Creating object-like services using:
        • Legacy Procedural Mainframe (CICS) Applications
        • Legacy Web-Applications (Perl/CGI)
      • Monitoring process
        • Trouble shooting
        • Dealing with failures
      • Managing the environment
  • 28. Implementation Challenges
    • Technical Challenges (cont)
      • Security challenges - loosely coupled environment
      • Performance - XML brings robustness not speed
      • Optimization
      • Organizing the services – Registry & Repository
  • 29. UCSD Server Environment
  • 30. Implementation Challenges
    • Organizational and Cultural Challenges
      • Paradigm shift for developers
      • Paradigm shift for IT Managers
      • More organizational discipline
      • Governance
  • 31. Implementing SOA @ UCSD
    • Organizational Structure
      • Web Application Developers
      • Enterprise Architecture & Integration Team
      • Portal Services - Web Content Analysts & Writers
      • Security Team
      • Legacy Mainframe Application Programmers
      • DBA & Data Warehouse Team
      • System & Tech Support (Unix & Mainframe)
  • 32. Implementation Challenges
    • Staffing Challenges
      • Recruitment
      • Retention
      • Compensation
      • Adoption - Buy-in
      • Keeping staff motivated and excited
  • 33. Implementing SOA @ UCSD
    • Staffing Transition
      • Wiki Training
      • Framework Bootcamp
      • UCSD Toolbox
      • Conferences & classes
        • Supervisors
        • Project Managers
      • Bi-weekly staff meeting
      • Student Interns
  • 34. UCSD Toolbox
  • 35. UCSD Toolbox
  • 36. UCSD Application Infrastructure
    • What did we build?
      • We had an application infrastructure which supported the concept of services. It could be extended and runs in a J2EE container
      • We already had support for and interoperability with open source technology
    • What did we buy?
      • Adobe eForms
      • Vignette Portal & Content Management
      • ElementK (hosted)
      • InfiNET (hosted)
      • SciQuest (hosted)
      • WebSphere Z/OS (hopefully, waiting for funding)
      • We currently have over 400+ services developed for our applications. There has been a high percentage of reuse over the last year. These will be the building blocks of our campus wide services planned for the next 12 months.
  • 37. UCSD Timeline UCSD History & Milestones
  • 38. Marty Backer [email_address] Christopher De Rosa [email_address] Elazar Harel [email_address] Thank You