STEP-C . Students Tracking and Engagement Proof of concept. Rajesh Sinha (CEO, Fulcrum). Agenda. STEP-C Objective HE vision Implementing STEP-C (SOA + ESB) Future – ESB in Cloud Enterprise Architecture Q & A. STEP- C Objective.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
STEP-C Students Tracking and Engagement Proof of concept Rajesh Sinha (CEO, Fulcrum)
Agenda STEP-C Objective HE vision Implementing STEP-C (SOA + ESB) Future – ESB in Cloud Enterprise Architecture Q & A
STEP- C Objective UK Higher Education has been facing challenges since last few years. A few amongst them are: • UK HE organizations have adopted “best of breed” approach for acquiring information related to student. Each institution then has to integrate the various application systems and develop over-arching management reporting systems. • There was a need for information to be acquired and integrated across multiple Institutions to satisfy legislative needs. • UK legislation (anti-terrorism rules) require all UK Universities to be able to monitor whether students who have obtained a visa to attend an educational course are actually attending and studying.
HE Vision Other App EDW Portal Services Customers, Partners & vendors Cloud Computing Students Record Enterprise Service Bus Email Exchange Finance APP Library System VLE Data Enrichment Using Data Quality Services
Traditional Vs. SOA Enterprise Service Bus (ESB) • Students Track • Students Record • Personal Info • Finance • Identity Check • Process Payment • VLE • VLE plan • Course Attended • Students Tracking • Students Record • Personal Info • Finance • Identity Check • Process Payment • VLE • VLE plan • Course Attended • Distributed applications • Backbone-based integration • Reusable services • Decoupling • Metadata driven – Services, Policy's and Bindings • Centralized Operation and Management • Monolithic application development • Point-to-point integration • Hard-wired • Resource Intensive • High bandwidth utilization • High number of Communication Channels
SOA- ESBDe Montfort University Finance System Student Records DMU: Agresso QLX V3.9 Agresso QLS (V4(1.13)) Using Web Services [ ] ESB - ENTERPRISE SERVICE BUS Reporting System DMU: Blackboard V8.0 (SP5) Google Mail Virtual Learning Environment University Email CREATE A REPOSITORY OF ACTIVITY / ENGAGEMENT DATA
SOA-ESBSouthampton Solent University Library System Student Records SSU: Exlibris: Aleph Campus IT: Quercus Plus [ ] ESB - ENTERPRISE SERVICE BUS SSU: Open Source Moodle Virtual Learning Environment Reporting System
SOA-ESB - Comparison Finance System Student Records Library System Student Records DMU: Agresso QLX V3.9 Agresso QLS (V4(1.13)) SSU: Exlibris: Aleph Campus IT: Quercus Plus IBM WEBSPHERE ESB MICROSOFT BIZTALK SSU: Open Source Moodle DMU: Blackboard V8.0 (SP5) Google Mail Virtual Learning Environment Virtual Learning Environment University Email DMU SSU Reporting System Reporting System
STEP-C Reporting From Agresso -Students From Aleph From Quercus From Moodle From Agresso -Finance From Blackboard From Gmail DMU Report SSU Report
Implementation Benefits • The solution is deemed to be technology and platform independent • The total solution is a loosely coupled architecture that any systems can be added to the existing frame work without disturbing the current environment. • The reusability concepts of the SOA based architectures are implemented by consuming all the functionalities as services through the ESB. • The development time to add new systems is very less as retesting the existing solution and recompilation of the total solution for minor changes can be avoided. • With the concepts of Itineraries the data flow can be defined by a business analyst without knowing the underlying implementation of the any tool.
ESB in Cloud Internet Service Bus XML XML XML Subscribe Subscribe Publish • Services re-used • across various HEI • - Common services • Interoperability & • Standardization • Involvement of • Vendors, Suppliers • & System Integrators Publish • Common Data • Structures • - Data Security • Data Management • & Governance • Reporting & BI HE EDW HEIs XML XML HEI 1 HEI 2
Today’s IT Environment • Inflexible, • expensive to • change • systems • Not easily • scalable • Tightly coupled • systems • Data with • frequent • inconsistencies
ENTERPRISE ARCHITECTURE GOVERNANCE ‘To Be’ Enterprise Architecture SECURITY Services and Procedure LIFECYCLE Management CoE Service Management Authentication Security policies Security management Compliance TAC Process Policies Monitoring Service administration & management Confidentiality Security standards Authorization Standards SCM DGC Logging Quality control Auditing Consumer Channels Printer/ Telephone Mail Browser Channel Mobility SSO and SSL enabled Process Tier BAM BRMS Process modeling Process automation Process monitoring Process analysis & control Service Consumer Rules engine Campaign engine Application Tier Composite Apps Business Intelligence Productivity Apps Portal and CMS SOA Apps Enterprise products Integration Tier Legacy Services SERVICE ORCHESTRATION Data Integration IDS ETL Data quality Enterprise Service Bus Service Provider Shared Services Reusable Components Framework Metadata Notification & subscription Deployment services MDM Communication Tier Reliable messaging Publish/subscribe Asynchronous Synchronous Queuing Data Tier APP 2 Others Reporting Repository APP 1 Infrastructure Tier Mail Exchange Virtualization Firewall Servers and Desktop Clustering & Load Bal Telephony N/w, SAN FTP Green IT Grid Computing Citrix Security ENV provisioning Scalability
STEP-C Background Each of the 167 UK HEIs have application architectures built with • Different combinations of ‘Best of Breed’ applications • Applications that are linked with point-to-point interfaces • Few “standards” for interfaces which are shared across the entire sector Hence, each University has a different starting point and also a different size of IT department
System Architecture using Microsoft ESB Agresso Finance SQL Server 2005 Agresso Students Record system Value Added • Publish and Subscribe Architecture • Message Transformation • Adapter Framework • Reusable Orchestration (Business Process Management) • Itinerary Services • Deployment Management • Security • ESB Toolkit Request Message To Web service BizTalk SQL adapter Response Message From Web service Aggregation of all the messages into a single message BizTalk Server ESB ramp On Ramp Off RAMP Request & Response from Google API BizTalk SQL adapter BizTalk SQL adapter Google API Reporting DatabaseSQL Server 2005 Black Board SQL Server 2005
System Architecture using IBM ESB • Value Added • Enterprise Messaging • Request/Response Architecture • Message Transformation • Automated Process Flows • Business Process Services • Service Mediation • Aggregation (FAN-IN; FAN-OUT) • ESB Toolkit
Measuring EA Maturity MATURITY LEVELS BY CATEGORY • Business Architecture • Data Architecture • Governance • Planning • Framework • Architecture Blueprint • Communication • Compliance • Integration • Team Involvement • Performance • IT Implementation • Overall EA Maturity