Kuali Rice: General Overview Brian McGough Kuali Rice Project Manager Kuali Lead Architect Director, Enterprise Software, IU May 13, 2008.

Slides:



Advertisements
Similar presentations
CASE STUDIES Indiana University University of California, Davis University of Maryland San Joaquin Delta College University of Arizona University of Washington.
Advertisements

Rice Next Generation Infrastructure for Applications Brian McGough (Indiana University) Aaron Godert (Cornell University)
Evolution of the Kuali Rice Project Charter, Governance and Roadmap.
Kuali Technology Mark Norton – Nolaria Consulting Zachary Naiman – Member Liaison, Kuali Foundation.
Introduction to Kuali Rice ITANA Screen2Screen: Kuali on Campus May 2009 Eric Westfall – Kuali Rice Project Manager.
Open source administration software for education software development simplified RAD, Rules, and Compatibility: What's Coming in Kuali Rice 2.0 Eric Westfall.
KUALI ENTERPRISE WORKFLOW OVERVIEW Eric Westfall.
Edoclite and Managing Client Engagements What is Edoclite? How is it used at IU? Development Process?
Overview of Kuali Student Technical Architecture Kuali Days :: Chicago May 13-14, 2008.
© 2006 IBM Corporation IBM Software Group Relevance of Service Orientated Architecture to an Academic Infrastructure Gareth Greenwood, e-learning Evangelist,
Evolution of the Kuali Rice Project Charter, Governance and Roadmap
© 2004, The Trustees of Indiana University 1 OneStart Workflow Basics Brian McGough, Manager, Systems Integration, UITS Ryan Kirkendall, Lead Developer.
Systems Integration & Consulting June Copyright ® 2009 Ayenda Agenda Introduction to Systems Integration System Integration Challenges and Opportunities.
© 2004, The Trustees of Indiana University 1 Kuali Enterprise Workflow (KEW) Basics Brian McGough, Manager, Systems Integration, UITS.
Open source administration software for education software development simplified KRAD Kuali Application Development Framework.
Kuali Enterprise Workflow Eric Westfall (Indiana University) Andrew Hollamon (University of Arizona)
Introduction to Kuali Rice Presented at Internet2 April 2009 Eric Westfall – Kuali Rice Project Manager Bill Yock – Vice Chair, Kuali Rice Board of Directors.
Technical Overview of Kuali Rice UC Davis, Information & Educational Technology January 2009.
James Smith, University of Arizona Barbara Sutton, Cornell University
SOA, BPM, BPEL, jBPM.
Architecting and Building KRA using Kuali Rice Terry Durkin, KRA DM/Lead Developer (Indiana University) Bryan Hutchinson, KRA DM/Lead Developer (Cornell)
Kuali Rice Technical Overview February Components of Rice  KEWKuali Enterprise Workflow  KNSKuali Nervous System  KRADKuali Rapid Application.
1 Kuali Identity Management Advanced CAMP: Identity Services Summit for Higher Ed Open / Community-Source Projects.
Kuali Enterprise Workflow Kuali Days – May 2008 Eric Westfall - Indiana University.
Kuali Rice Overview January 2008 Aaron Godert - Cornell University.
Kuali Rice at Indiana University Rice Setup Options July 29-30, 2008 Eric Westfall.
Technical Overview for “Functionals” (Kuali-eze…It’s a Foreign Language!) Ailish Byrne, Indiana University Barbara Sutton, Cornell University.
Kuali Enterprise Notification Tell Me What I Want And Need To Know Aaron Godert (Sr. Software Architect, Cornell University) John Fereira (Programmer/Analyst,
Eric Westfall – Indiana University Jeremy Hanson – Iowa State University Building Applications with the KNS.
Rice Status Update University of California July 20, 2009 Eric Westfall – Kuali Rice Project Manager.
Eric Westfall – Indiana University James Bennett – Indiana University ADMINISTERING A PRODUCTION KUALI RICE INFRASTRUCTURE.
Kuali Rice: Cross Project Middleware November ???, 2007 Nate Johnson - Indiana University.
Kuali Nervous System Aaron Godert, Cornell University Jonathan Keller, University of California, Davis.
Kuali Enterprise Notification Aaron Godert (Sr. Software Architect, Cornell University) John Fereira (Programmer/Analyst, Cornell University)
Kuali Rice and Enterprise Workflow May 22, 2008 David Elyea.
Kuali Enterprise Workflow Eric Westfall (Indiana University) Aaron Hamid (Cornell University)
Kuali Rice: Cross Project Middleware May 21, 2007 Aaron Godert - Cornell University Nate Johnson - Indiana University.
Kuali Nervous System Aaron Godert, Cornell University Jonathan Keller, University of California, Davis.
Kuali Enterprise Workflow Presented at ITANA October 2009 Eric Westfall – Kuali Rice Project Manager.
KUALI IDENTITY MANAGEMENT Provides services for Identity and Access Management in Kuali Integrated Reference Implementations User Interfaces An “integration.
Indiana University’s Workflow Experiences Brian McGough Manager Systems Integration (IU) Kuali Lead Architect.
Building Applications with the KNS. The History of the KNS KFS spent a large amount of development time up front, using the best talent from each of the.
© 2004, The Trustees of Indiana University Kuali Project Development Methodology, Architecture, and Standards James Thomas, Kuali Project Manager Brian.
Adobe PDF Workflow Documents for Kuali Rice May 19th, 2009 Aaron Godert Manager, Enterprise Integration Cornell Information Technologies.
1 UCD Kuali Rice Road Map David Walker Curtis Bray Hampton Sublett Information & Educational Technology University of California, Davis.
Eric Westfall – Indiana University James Bennett – Indiana University ADMINISTERING A PRODUCTION KUALI RICE INFRASTRUCTURE.
Kuali Enterprise Workflow Kuali Days – November 2008 Scott Gibson, University of Maryland Bryan Hutchinson, Cornell University James Smith, University.
1 Kuali Nervous System (KNS) Part 2 Presented by: Jerry Neal – KFS Development Manager Geoff McGregor – KC Lead Developer Brian McGough – KRice Project.
Kuali Enterprise Workflow Ryan Kirkendall (Indiana University) Brian McGough (Indiana University)
1 Kuali Nervous System (KNS) Part 1 Presented by: Jerry Neal – KFS Development Manager Geoff McGregor – KC Lead Developer Brian McGough – KRice Project.
Kuali Rice Evolving the Technology Framework for Kuali Applications Brian McGough (Indiana University) Aaron Godert (Cornell University) Warner Onstine.
Kuali Rice A basic overview…. Kuali Rice Mission First and foremost to provide a consistent development framework and common middleware layer for Kuali.
Kuali Rice at Indiana University From the System Owner Perspective July 29-30, 2008 Eric Westfall.
Notification System. Functional Goals Provide a single list for all university related communications –Workflow items –Non-workflow items Examples of.
© 2006, The Trustees of Cornell University © 2006, The Trustees of Indiana University Kuali Nervous System Aaron Godert, Kuali Development Manager Brian.
KS configuration application workshop Kuali Days :: Chicago May 13-14, 2008.
Kuali IAM and Security Aaron Godert Sr. Software Architect/Engineer Kuali Rice Development Manager Cornell University.
Kuali Rice: Cross Project Middleware Nate Johnson - Indiana University November 17, 2007.
Kuali Nervous System Nate Johnson, Indiana University Jonathan Keller, University of California, Davis.
KIM: Kuali Abstraction Layer for Identities, Groups, Roles, and Permissions.
Eric Westfall KUALI ENTERPRISE WORKFLOW OVERVIEW.
Kuali Rice Evolving the Infrastructure for Kuali Applications Brian McGough (Indiana University) Aaron Godert (Cornell University)
Kuali Rice: Cross Project Middleware October 24, 2007 Aaron Godert - Cornell University.
Evolution of the Kuali Rice Project Charter, Governance and Roadmap.
Kuali Enterprise Notification Tell Me What I Want And Need To Know Aaron Godert (Sr. Software Architect, Cornell University) John Fereira (Programmer/Analyst,
Kuali Enterprise Notification Tell Me What I Want And Need To Know Aaron Godert (Sr. Software Architect, Cornell University) John Fereira (Programmer/Analyst,
Notification Service JA-SIG June 6, 2006 One stop shopping
Kuali Enterprise Notification An Update for Cornell - January 2007
Kuali Rice Overview April 2008 Aaron Godert
Kuali Rice: General Overview
Presentation transcript:

Kuali Rice: General Overview Brian McGough Kuali Rice Project Manager Kuali Lead Architect Director, Enterprise Software, IU May 13, 2008

Agenda Mission Why did we decide to build Rice Rice components brief overview –Acronym Familiarization What’s coming next

Kuali Rice Mission First and foremost to provide a consistent development framework and common middleware layer for Kuali Foundation based applications to leverage

Maybe We All Do? Who Cares? The users? Implementing intuitions? The kuali foundation? Partners? Commercial Affiliates? Programmers? Designers? Functional experts?

Thinking Outside of the Wok Most administrative applications have a common needs for: –Screen Rendering/input –Data Validation & Saving –Workflow based processes –Business Rules –Integration with other systems

What is Rice? Kuali Rice is the sum of its parts –KSB (Kuali Service Bus) –KNS (Kuali Nervous System) –KEW (Kuali Enterprise Workflow) –KEN (Kuali Enterprise Notification) –KIM (Kuali Identity Management)

What do all these pieces of rice have in common? By themselves they don’t do much Leveraged in a context to add value What kinds of context? –Business Administration Apps –Student Apps –Research Apps –Arbitrary data collection Apps

How do these add value? Shared consistent solutions: –Allow developers to focus on business functionality rather than how to achieve it technically. –Allow for re-use so that the code base remains as small and maintainable as possible –Example: On the Ford F-150, you have all kinds of options, but all models re-use many of the same parts and all look very similar

KSB Overview - The Goals 1.Enable applications and services deployed on the bus to interact with other applications and services 2.Provide (a)synchronous communication 3.Provide flexible security 4.Provide Quality of Service (QoS) 5.Keep it simple (light weight)

KSB A common registry of services –Lists all services on the bus and how they can be connected –Through simple Spring configuration, Java based services can be “exported” from a rice enabled application, which is then ready to be consumed by another application

KSB A common resource loading layer that provides access to services (bus or local) –Services can be local to the application, in which case the bus is short circuited –Services can be remote, in which case the bus is leveraged to ascertain the service endpoint For a closer look -

KNS Overview Provides reusable code, shared services, integration layer, and a development strategy Provides a common look and feel through screen drawing framework A document (business process) centric model with workflow as a core concept

KNS Overview Cont. More Core Concepts / Features –Transactional documents –Maintenance documents –Inquires –Lookups –Rules –Questions –Data dictionary

KEW Overview Facilitates routing and approval of business processes throughout an organization Provides re-usable routing rule creation which defines how business processes should be routed Provides hooks for client applications to handle workflow lifecycle events of business processes Provides route log functionality for auditing and other purpouses

KEW Overview Cont. End users interact with central workflow GUIs for all client applications –Document Search: Allows users to search for documents (business process transactions) –Action List: One place to go to find all documents that you must take action on

KEN Overview Works with the action list to provide a single place for all university related communications –Workflow items come from KEW –Non-workflow items from KEN Non-workflow example items –Overdue library book –A concert on campus –Graduation checklists for seniors

KEN Overview Cont. Provides a secure and controlled environment for notifying the masses Eliminate sifting through Communication broker which provides any combination of action list, text messages, , etc... Audit trail just as in KEW

KIM Overview Consistent service interfaces used by all Kuali apps Leverages KNS and KEW to provide a reference implementation out of the box Flexibility for dynamic attribute associations with IdM entities (persons, groups, roles, etc) Pluggable support for Internet2 (Grouper, Signet, etc) products or other IDM tools

KIM Overview Cont. Basic concepts –Namespace –Person –Group –Permissions –Roles –Qualified Roles

Kim Overview Cont.

What’s Next? Looking to the Future… Rice components will piggy back on each other –KEW and KEN will use KNS to draw screens, etc. –KIM retrofitted back into Rice in release Standards –JPA for data persistence (underway) –JSR 168/286 portlets for user interfaces (portals) –BPEL for process orchestration –WS-* support Easier configuration and turnkey upgrades Light weight service interfaces (WSDL, XSD) Open source ESB replacement for KSB

Kuali Rice - Current Status Public beta version available at --> Download Rice is in development and early testing –Shipping with built in mysql support Rice scope is being planned Rice 1.0 expected mid next year

The Rice Interactive Diagram Available at Click anywhere on the diagram to begin Click on any component for details

The main Rice web site – –Sign up for our public mailing list –Access to our wiki: roadmap, project plans, documentation, etc Documentation is a weakness About the website

The Rice Team Current Core Contributors –Brian McGough - Indiana University –Aaron Godert - Cornell University –Nate Johnson - Indiana University –Eric Westfall - Indiana University –David Elyea - Indiana University –Aaron Hamid - Cornell University –Chi-Thanh Dang - University of Arizona Past Contributors –John Fereira - Cornell University –Phillip Berres - University of Southern California –Ryan Kirkendall - Indiana University –Scott Battaglia - Rutgers University –Tom Clark - Indiana University

Future Contributors

Wrap Up The mission Why Build Rice General introduction to rice components –Acronym Familiarization What’s coming next

That’s it! Q & A