1 / 48

The Foothill-De Anza Technology Environment

The Foothill-De Anza Technology Environment. Willie Pritchard Vice Chancellor, Technology. Goals for the session. Show models of current technology environment Physical Network Software Help audience understand technology challenges and opportunities

Ava
Télécharger la présentation

The Foothill-De Anza Technology Environment

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. The Foothill-De Anza Technology Environment Willie Pritchard Vice Chancellor, Technology

  2. Goals for the session • Show models of current technology environment • Physical • Network • Software • Help audience understand technology challenges and opportunities • Layout a road map for our near term future • Provide a glimpse of our longer term future

  3. CAUTION TECHNICAL JARGON AHEAD

  4. Physical Network Software Think of our technology environment as a series of layers… Technology Layers Computers, servers, switches, printers, cable cable, switches, routers, hubs, software, applications, browsers, databases, educational information system Now we’ll take one layer at a time. First the physical environment…

  5. Physical Physical Environment Internet User

  6. Physical Physical Environment Internet User

  7. Physical Physical Environment Internet User

  8. Physical Physical Environment Admin User Internet User

  9. Physical Physical Environment Admin User Internet User E-mail User

  10. Physical Physical Environment Admin User Internet User E-mail User Database User

  11. Physical Physical Environment Admin User Internet User E-mail User Database User

  12. Physical Physical Environment Admin User Internet User E-mail User Database User x 200+ switches

  13. Physical Physical Environment Admin User Internet User E-mail User Database User x 200+ switches

  14. Physical Physical Environment Admin User Internet User E-mail User Database User x 200+ switches

  15. Physical Physical Environment Admin User Internet User E-mail User Database User x 200+ switches

  16. Physical Physical Environment Admin User Internet User E-mail User Database User x 200+ switches

  17. Physical Physical Environment Admin User Internet User E-mail User Database User x 200+ switches

  18. Physical Network Network Environment • What are the characteristics of an “excellent” network? • Reliable • Secure • Fast • What technical requirements ensure each? • Firewall • Lots of bandwidth • Authentication/Authorization • Switched network • Segmented networks (VLANs) • VPN

  19. Physical Network Network Environment • What are the characteristics of an “excellent” network? • Reliable • Secure • Fast • What technical requirements ensure each? • Firewall (Reliable, Secure) • Lots of bandwidth (Fast) • Authentication/Authorization (Reliable, Secure) • Switched network (Secure, Fast) • Segmented networks (VLANs) (Reliable, Secure, Fast) • VPN (Secure)

  20. Physical Network Network Environment • Two ways to view our network • Physical Network • Virtual Network

  21. Physical Network ADF (hub) Backbone Spokes Foothill Physical Network

  22. Physical Network ADF (hub) Backbone Spokes De Anza Physical Network

  23. Physical Network Important Point! Virtual Network • What are VLANs? • “Virtual Local-Area Networks” • A “virtual” method for separating an enterprise network into different segments (LANs) for performance and security • The FHDA network has several VLANs • Open (to the world) • Secure (only authorized users have access) • Academic (for instructional uses) • Based on physical location of network jack • Not currently applicable to wireless

  24. Physical Network Off Campus Users Virtual Network Environment Campus Users

  25. Physical Network Off Campus Users Virtual Network Environment Campus Users

  26. Physical Network Off Campus Users Virtual Network Environment Campus Users

  27. Physical Network Off Campus Users Virtual Network Environment Campus Users

  28. Physical Network Off Campus Users Virtual Network Environment Campus Users

  29. Physical Network Security for Outside Access • We need a Virtual Private Network (VPN) • Provides secure method for connecting from off campus to our Secure VLAN • Authentication • Authorization • Encryption • Tunneling

  30. Physical Network Off Campus Users Virtual Network Environment Campus Users

  31. Physical Network Off Campus Users Virtual Network Environment Campus Users

  32. Software Environment

  33. Physical Network Software Software Environment • State of our current software environment • Multiple applications • Multiple interfaces • Steep learning curve • Incompatible applications • Multiple passwords and accounts • Expensive to acquire, develop, or replace • Multiple database formats • Inflexible backend database for our information system

  34. Desktop Applications Browsers “Network-aware” applications APIs Physical HTML, XHTML Java, JavaScript Network XML Middleware SOAP Software JSR 168 WSRP Backend Databases & Applications RDB SCT IA+ (Flat file) SQL (Relational) Oracle Portal (Relational) Software Environment Meeting Maker IR Data Warehouse Automated workflow Student Tracking TouchNet Registration SIRSI Tech Help www.foothill.edu AccuStream Go Print SEVIS Resource 25 Student ID cards CATS MS Active Directory ETUDES-ng

  35. Physical Network Software New Portal Environment… • Will provide the following remedies • Single sign-on • Unified interface • Integrated applications • One-stop shop • Inexpensive, quick development • Portable to new information system • Individualization and customization • Transparent backend databases • Little training needed

  36. Physical Network Software FHDA Portal • What is a portal? • An electronic, personalized, customized newspaper

  37. Physical Network Software FHDA Portal • What is it? • Entrance (portal) to all of your district resources

  38. Physical Network Software FHDA Portal • What is it? • Uses standard web technologies • Graphical User Interface • Industry standards • Made up of channels (or portlets) of information and functionalities • Provides access to many different resources

  39. Physical Network Software FHDA Portal • What kind of channels/portlets are there? • Informational • News, weather, book and movie reviews • Campus news, events, significant dates • Functional • Workflow processes (timesheets, evaluations, grade submittals, etc.) • Data retrieval • Search tools • Where do we get portlets? • CampusEAI Consortium (open source) • Develop ourselves

  40. Physical Network Software FHDA Portal • How is it customizable? • By group • Students • Faculty • Staff • Managers • Campus (Foothill, De Anza, Central Services)

  41. Physical Network Software FHDA Portal • How is it personalized? • Each individual will have a selection of portlets to choose from • Some portlets will be required of all • Emergency notifications • Some will be required of certain groups • Students – registration • Employees – workflow

  42. Physical Network Software FHDA Portal • Demonstration of current prototype • Lots of work yet to be done • This is not the final design • Many more portlets to acquire and build

  43. Physical Network Software FHDA Portal • What are some possible portlets?

  44. Physical Network Software FHDA Portal • What portlets might we develop?

  45. Physical Network Software FHDA Portal • What is the timeline for implementation? • As fast as we can do within the constraints we have • What still needs to be done? • User interface design underway • Identity Management • Authentication & Authorization • FHDA portlets need to be developed

  46. Physical Network Software Workflow (Forms) Processing • How does it work? • Applies logic to the flow of our paperwork • Allows for electronic distribution through the web • Electronic approvals • Examples • Timesheets/payroll • Faculty Evaluation • Grade Submittals • Next?

  47. Physical Network Software Technology Layers Remember the three layers… Computers, servers, switches, servers, cable cable, switches, routers, hubs, software, applications, browsers, databases, educational information system On most projects and work requests,we have to deal with all three

  48. Questions?

More Related