1. Enterprise Architecture 2013 University of California, Irvine: EA Case Study - Enterprise Service Bus Data Architecture Prepared by for ITANA Face-to-Face: Larry Coon, lcoon@uci.edu Durendal Huynh, durendal.huyhn@uci.edu Tony Toyofuku, toyofuku@uci.edu Jason Lin, jlin@uci.edu Marina Arseniev, marsenie@uci.edu October 15, 2013

2. Enterprise Architecture 2013 UC Irvine’s Case Study: Problem Statement Student data files are delivered point-to-point from Registrar to departments via sFTP on a quarterly basis. Office of Institutional Research (OIR) and other units needed daily student enrollment trends for decision support analysis. The size and frequency of the daily enrollment data complicated the data delivery using the current point- to-point architecture. Data access is currently ad-hoc and the new recipient on-boarding process is manual. Tracking of authorized data dissemination is difficult.

3. Enterprise Architecture 2013 UC Irvine’s ESB Case Study: Objectives Leverage Enterprise Service Bus (ESB) to mediate data between publisher and subscribers. Use Enterprise Integration Pattern and event driven architecture to enable real-time data transfer. Exercise different types of data containers (file, record, table). Exercise different mediation mechanism (sFTP, database). Explore data transformation integration with ESB (inside ESB, at subscriber). Exercise ESB development, deployment, administration, monitoring and notification capability. Evolve from point-to-point data distribution to single publisher/multiple-subscribers architecture.

4. Enterprise Architecture 2013 Architecture

5. Enterprise Architecture 2013 UC Irvine’s Case Study: Outcome ESB is in production with Registrar being a publisher of raw daily student enrollment data, and OIR the first subscriber to this data with more to follow. OIR receives data from ESB, processes it, and adds values by transforming complex student records to both relational and dimensional datasets. OIR then becomes publisher of these datasets via ESB. Dimensional data is consumed by Student Enrollment Trend Analysis Decision Support in Cognos and Tableau. Next Steps – ESB to publish daily enrollment files to other subscribers – OIR to publish relational and dimensional dataset via ESB messages – Data sets from Cognos enrollment reports to be published as WebServices via ESB.

6. Enterprise Architecture 2013 UC Irvine Registrar Enrollment Data Analysis

7. Enterprise Architecture 2013 UC Irvine’s Case Study: Lessons Learned Development – Configuration: Endpoint configuration templates will help speed up project initiation – Development: Integrated development platform and available design patterns will accelerate adoption. – Data Integration: ESB is a Service Container and Service Mediator. Data transformation while possible to deployed, is better off as a separate integrated layer. – Develop a standard test bed to encourage publishers/subscribers to validate robustness of services Operation – Deployment: centralized deployment is best achieved with a reusable service repository. – Administration & monitoring: Beside security configuration and integration, usage statics, error recovery, monitoring and error notification are important operation aspects to gain user acceptance. – Access to logs: in the absence of BPM, a commonly defined log and API to access the log would enable the publishers/subscribers to self-monitor.