Presentation on theme: "Joint Information Systems Committee 25/08/2014 | slide 1 JISC Core Middleware Programme Meeting Middleware in Development Joint Information Systems CommitteeSupporting."— Presentation transcript:
Joint Information Systems Committee 25/08/2014 | slide 1 JISC Core Middleware Programme Meeting Middleware in Development Joint Information Systems CommitteeSupporting education and research
Joint Information Systems Committee 25/08/2014 | | Slide 2 JISC Core Middleware Programme Meeting Middleware in Development Nicole Harris JISC Programme Manager
Joint Information Systems Committee 25/08/2014 | slide 3 JISC Structure Committee-led, with a high level board. Six sub-committees: –Networking. –Support. –Content and Services. –Learning and Teaching. –Integrated Information Environments. –Support of Research. Four teams: –Policy (bidding process, funding letters, committee support etc.). –Outreach and communications. –Content and services. –Development.
Joint Information Systems Committee 25/08/2014 | slide 4 JISC Funding Core funding from funding councils (recently reduced funding from Learning and Skills Council has led to a decrease in activities for Further Education). Approximately £64 million to date (not including withdrawal of LSC support). More than half goes to JANET. Additional funding from (C)SR funds (Comprehensive Spending Review – no longer comprehensive). Theoretically capital expenditure. Examples of core funding programmes: Core Middleware: Technology Development, Repositories, Preservation. Examples of CSR programmes: Core Middleware: Infrastructure, VRE, e-Learning regional pilots, digitisation. Core Middleware programmes currently funded exclusively by JIIE and JSR committee funding and additional CSR funding. Work within development does cut across all domains, regardless of funding committee, which requires planning…
Joint Information Systems Committee 25/08/2014 | slide 5 The JISC e-Framework A tool for planning, mapping, identifying gaps and ensuring cohesion and coherence across development (I’ve done something in that box). Will include reference models, reference implementations and guidance / advice / support. Domain Specific Services e-Learning e-Research e-Admin Common Services e-Resources Management Messaging/ Collaboration Middleware (Security and Logging)
Joint Information Systems Committee 25/08/2014 | slide 6 The framework in use Lightweight tools, used in different domains, calling on robust common services (very common) Domain Services User Agents (Tools, Applications, Portlets, Rich Clients, etc.) Learning Services Lighter weight User Tools, Applications, Portlets, etc. call on domain specific services, such as Learning, Teaching or Research, and either through them, or directly, they call on Common Services Research Services Administration Services Common Services Etc… Resource Services Security Services Messaging Services Etc… Users
Joint Information Systems Committee 25/08/2014 | slide 7 Security?? Middleware?? Common?? Shared?? The JISC e-Framework uses the term ‘common services’ to refer to the services that are ‘common’ requirements across all the domains, and can be usefully developed in a centralised way. The services themselves may NOT be national, or central services. The JISC Information Environment has been responsible for developing ‘shared services’, These are centralised, normally national, services performing central tasks on the behalf of a wide range of institutions / services. Athens, therefore is a ‘shared service’ but not a ‘common service’ as it does not serve e- Research or e-Learning. The new federated access management system aims to be a ‘common’ service. JISC refers to its development within the areas of authentication and authorisation as ‘core middleware’. It further defines this as development relating to the areas of authentication, authorisation, identifiers and directories. The broader area of ‘security’ is of interest to several JISC committees and draws on work within Outreach and Services (such as the recently produced security toolkit).
Joint Information Systems Committee 25/08/2014 | slide 8 Development (not Services) As part of Core funding: 15 projects looking at a range of issues: –AMIE – attribute management. –DYCOM – development of PERMIS for fine-grained, multi-layer / multi-authority access control. –DYVOSE – dynamic delegation of authority. –ESP GRID – shibboleth and grid? –FAME-PERMIS – level of assurance. –GROUPS MANAGER – attribute tools. –GUANXI – shibboleth implementation. –IAMSECT – shibboleth implementation. –IMPETUS – shibboleth implementation. –KC-ROLO – shibboleth implementation. –LICHEN – AA and wireless developments. –PERSEUS – shibboleth and portals. –SDSS – shibboleth support service. –SIPS – implementations of PERMIS. –SPIE – shibboleth and portals. –(2 NEW) SHIBGRID: specific solutions for NGS.
Joint Information Systems Committee 25/08/2014 | slide 9 What Next?? New planning cycle starting April 2006. Should be informed by current developments, and events such as this. Sessions at this event planned with the aim of looking forward as well as reviewing. Ideas to be considered: –‘e-Infrastructure’ developments. –Web Service Security developments: use of WS-Security and wider suite, n-tier issues, service to service (rather than user to application). –PKI developments, wider implementation and use of certificates. –User credential management in a wider environment. –Shibboleth associated: virtual home for identities, multiple WAYF. –Accounting, auditing, diagnostics. Should all meet JISC strategy and other relevant strategies: DFeS e-Strategy, HEFCE e-Learning Strategy, Science and Innovation Framework etc. Other ideas???
Joint Information Systems Committee 25/08/2014 | slide 10 Questions?? Your ideas and input are welcome