1 / 15

Architectural Vision

Architectural Vision. Layered Infrastructure. Architecture Purpose. Create reliable, extendable, standards-based, maintainable infrastructure Distribute management and development Speed deployment with increased reliability Support necessary security and extensive self-service applications.

moral
Download Presentation

Architectural Vision

An Image/Link below is provided (as is) to download presentation 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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Architectural Vision Layered Infrastructure

  2. Architecture Purpose • Create reliable, extendable, standards-based, maintainable infrastructure • Distribute management and development • Speed deployment with increased reliability • Support necessary security and extensive self-service applications

  3. Expanded Architectural Model School/Department/Division Applications Specialized Enterprise Applications Core Enterprise Systems CONDUITS, School NAS CMS, Alumni, Library Applications Financial, HR, SES, Research Identity, SSO, Messaging Integration Middleware Delivery Systems Data Management Oracle, SQL Win2003, UNIX, Linux Servers IP, VOIP, Wireless Network Platforms Desktop, Mobile User Devices Systems Management Directories Security

  4. User Devices • Situation • Desktop, mobile, handheld units • Current efforts • Purchasing guidelines; anti-virus license • Maintenance contracts; software site-licenses • Future directions • Device independence through Web interfaces • Network backup services

  5. Network • Situation • state-of-the-art connectivity • Current efforts • Access to National/International networks; on-campus wireless; iCAIR R&D • Advancing applications of network • Future directions • Voice services (VoIP); cellular-IP services • Role-based access and service levels

  6. Servers • Situation • Highly-available service platforms • Current efforts • Redundant power and network paths • Narrowing supported systems to focus skills • Future directions • Parallel/hot service site; flexible server management • Consolidation of server support

  7. Data Management • Situation • Holding and protecting University information • Current efforts • Data stewards moving to common definitions • Future efforts • Data warehousing for analysis and reporting • Near real-time access to data across systems • Standard reporting and data retrieval tools

  8. Integration Middleware • Situation • Delegated identity management and access control • Current efforts • Improve identity management processes • Deploy and leverage standard technology • Future directions • Define standard inter-application work flows • Role-based portal to integrate presentation

  9. Core Enterprise Systems • Situation • Three major systems replaced in past 6 years • Current efforts • Leverage abilities of newer systems (HRIS, SES) • Implement new financial and research systems • Future directions • Integrate cross-system transactions • Open data to near real-time secure queries

  10. Specialized Enterprise Applications • Situation • Relatively independent activities; isolated from core systems • Current efforts • Interface Advance alumni system with core systems • Continue Course Management improvements • Future directions • New specification and procurement processes to anticipate integration with core systems; enforce security model

  11. School/Department/Division Applications • Situation • Local systems holding institutional information • Procurements often isolated from IT planning • Current efforts • Identify systems and data (SIMS, CONDUITS) • Future directions • Procurements must meet integration plans • Eliminate data replication; enforce security model

  12. Systems Management • Ensure service availability • Current efforts • Automatic monitoring of central network and central servers • Future directions • Monitor all network devices • Monitor enterprise applications

  13. Directories • Authenticate and authorize • Current efforts • Widely-used identifier (NetID) • Deploy standard infrastructure • Future directions • Web single sign-on • Unified identity management for all applications • Enterprise portal roles

  14. Security • Prevent intrusion or disruption • Current efforts • Installing network firewalls • Installing intrusion detection • Future directions • Network-wide anti-virus • Continuous vulnerability scanning

  15. Expanded Architectural Model School/Department/Division Applications Specialized Enterprise Applications Core Enterprise Systems CONDUITS, School NAS CMS, Alumni, Library Applications Financial, HR, SES, Research Identity, SSO, Messaging Integration Middleware Delivery Systems Data Management Oracle, SQL Win2003, UNIX, Linux Servers IP, VOIP, Wireless Network Platforms Desktop, Mobile User Devices Systems Management Directories Security

More Related