Designing E-Campus for Hamton University

Background Section 1

History Section 1

Executive Summary Section 1

Phase I: Portal Definition Section 2

Phase II: Project Planning Section 3

Phase III: Portal Design Section 4

Phase IV: System Implementation Section 5

Phase V: Identity Management Integration Section 6

Oracle Application Server Portal Appendix

Examples: scripts, ldif, cron jobs Appendix

Training presentations Appendix

Background

Commercial off-the-shelf (COTS) products have an appealing attraction that makes it seem that those products can easily fit into any organization’s structure. The reality tells us that, the “one size fits all” just might not fit at all. The lack in flexibility that COTS provide can limit an organizations technology growth, by hindering innovation.

History

In 1999, the Information Technology department at Hampton University was tasked to design an infrastructure that would be world class. Several phases and areas of technology were to be addressed. Stronger web presence was an area that needed attention. The current Hampton University web portal was a commercial of the shelf product that did not have the flexibility needed to position the institution to provide a full bodied self-service application. . The challenge to find a product that would enhance the current offerings and provide a means of capturing an audience would prove to be a measurable task. Open source was the answer. Several products were looked at. There was an opportunity to enter for a grant through Campus EAI. Campus EAI is a consortium of higher education institutions that focused on portal development utilizing the latest technology offered by Oracle Corporation. The Oracle portal would help in bringing about a solution to fill Hampton University’s need.

Executive Summary

Hampton University secured a $1.3 million grant with Campus EAI and Oracle Corporation to work in collaboration with 35 other institutions to...