1. May 10, 2001An Overview of the Princeton University Web 1 Technical Infrastructure  History –www.Princeton.EDU running since 1993.www.Princeton.EDU –User website support announced 1994. –User CGI service added in 1997. –Organic, not architected.

2. May 10, 2001An Overview of the Princeton University Web 2 Technical Infrastructure  History (cont) –Today 42 Sites with www.???.Princeton.EDUwww.???.Princeton.EDU

3. May 10, 2001An Overview of the Princeton University Web 3 Technical Infrastructure  Rationale for method –Initial platform choice based on support from Unix Systems. –Server choices based on server availability and ability to modify server for special uses –Growth by piecemeal addition and revolution –Look and feel buy-in

4. May 10, 2001An Overview of the Princeton University Web 4 Technical Infrastructure  Implementation –1993 Two people less than 1 week –2001 Many people many man months

5. May 10, 2001An Overview of the Princeton University Web 5 Technical Infrastructure  Resources –CIT –Departmental –Outside Services

6. May 10, 2001An Overview of the Princeton University Web 6 Technical Infrastructure  Project management –You stay out of my way and I’ll stay out of yours –Is there some way we can help you?

7. May 10, 2001An Overview of the Princeton University Web 7 Technical Infrastructure  Project maintenance –Its 10 pm, do you know what your data is? –How do I update without destroying access?

8. May 10, 2001An Overview of the Princeton University Web 8 Technical Infrastructure  Project success –No worse than many places –Success stymied by Lack of coordination Lack of standards Lack of time

9. May 10, 2001An Overview of the Princeton University Web 9 Technical Infrastructure  Futures –Move to an architected service –Support true 24x7 where needed –Provide alternatives to machine upgrades to relieve performance problems –Provide ability to host anywhere transparently

10. May 10, 2001An Overview of the Princeton University Web 10 Technical Infrastructure  Futures (cont) –Continue to respond to outside world even when internal network down.