UC Middleware Needs

David WalkerInformation & Educational Technology

University of California, DavisDHWalker@ucdavis.edu

UC Middleware Needs

UCTrust Integration Federated Processes Do we need common middleware in

the first place? What do we mean by “common”

middleware?

University of California

• Ten campus

• Five medical centers

• Lawrence Berkeley National Lab

• Office of the President

• One legal entity

IT Environment

• Nearly all operation at each location– Local authority and responsibility for

the “business” of the University

• Some shared components– Employee systems

– Student application system

– UCTrust

What We Need

• Interoperable, robust, secure solutions that enhance reuse and sharing of software among UC locations

Example

• User Provisioning for LMS, Connexxus

UCTrust Integration

UCTrust is really just part of InCommon LoA Entitlements

Federated Processes

Intercampus work flow, service bus, etc. to support:

– Shared Infrastructure

– Software as a Service