• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Powerpoint slides
 

Powerpoint slides

on

  • 444 views

 

Statistics

Views

Total Views
444
Views on SlideShare
444
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Powerpoint slides Powerpoint slides Presentation Transcript

  • Planning & Delivering Service Oriented Architecture (SOA) University of California, San Diego October 30, 2006
    • About UCSD
    • What is SOA?
    • Why Implement SOA?
    • Planning for SOA
    • UCSD Examples Experiences and Case Studies
    • Implementation Challenges
    • The UCSD SOA Framework
    Topics
    • 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
    • Ease of Use and Access
    • Common Look & Feel
    • Web-Based Systems
    • Interoperability and Open Architecture
    • Single Signon
    • Evolution v. Revolution
    • Cost-Effectiveness
    About UCSD Administrative Computing Goals:
    • Application life-cycles continue to shrink – demand increases
    • Systems constantly changing for business needs
    • Regardless of platform, DB, technology – all systems need to: Interoperate, Communicate & Integrate
    • Leverage departmental IT staff in development
    Driving Factors for UCSD
  • 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
    • 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?
  • 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
  • What is a Service
    • 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?
  • 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
  • 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.
  • A Service Example
  • Benefits of SOA
  • Planning for SOA @ UCSD
    • Approach:
      • Think strategically and plan tactically
      • Evolutionary not revolutionary
      • “ 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
  • 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.
  • 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.
  • 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.
  • 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
  • UCSD Server Environment
  • 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
  • Implementation Challenges
    • Technical Challenges (cont)
      • Security challenges - loosely coupled environment
      • Performance - XML brings robustness not speed
      • Optimization
      • Organizing the services – Registry & Repository
  • Implementation Challenges
    • Organizational and Cultural Challenges
      • Paradigm shift for developers
        • Specialists vs. Generalist
      • Paradigm shift for IT Managers
      • More organizational discipline
      • Governance
  • Implementing SOA @ UCSD
    • Organizational Structure
      • Portal Services: Web Content Analysts, Writers, UI & Usability
      • Enterprise Architecture & Middleware Team
      • Security Team
      • DBA & Data Warehouse Team
      • System & Tech Support (Unix & Mainframe)
      • Legacy Mainframe Application Programmers
      • Web Application Developers
        • UI Developers
        • Services developers
        • Process Centric Developers
  • Implementation Challenges
    • Staffing Challenges
      • Recruitment
      • Retention
      • Compensation
      • Adoption - Buy-in
      • Keeping staff motivated and excited
  • Implementing SOA @ UCSD
    • Staffing Transition
      • Wiki Training
      • Framework Bootcamp
      • UCSD Toolbox
      • Conferences & classes
      • Bi-weekly staff meeting
      • Student Interns
  • Implementing SOA @ UCSD
    • Gartner Conferences – 2002-2006
    • Things we did:
      • Take stock of what you already have
      • Build on existing technology
      • Train staff
      • Design Services for Re-use
      • Move in incremental adoption
    • Things we avoided:
      • Avoid guidance from vendors
      • SOA is NOT a technology, not a single solution, buy the technology that compliments your goals and environment
      • Don’t do the “Big Bang” approach
      • Avoid thinking of an SOA projects any differently that other project
      • Plethora of products in the SOA space - Common myth that you have to start with buying products
  • UCSD Toolbox
  • UCSD Toolbox
  • 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
      • IBM WD4Z
      • We currently have over 50+ services in production and 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.
  • Marty Backer [email_address] Christopher De Rosa [email_address] Elazar Harel [email_address] Thank You