Rutgers uP3 Testing
Rutgers plans to spend a couple of weeks looking at the recently released uP3 RC1 in the context of what it would take to get it up and running. The plan is to spend a tightly time-boxed iteration from now (12/6) until 12/22 looking at various areas of uP3, and provide feedback to the uP3 team and uPortal community. The hope is to test the existing code and identify any gaps in the core feature-set needed for institutional deployment.
Goals
- evaluate current state of uP3 RC1
- get a feel for the completeness/coverage of the core feature set
- evaluate the ability/difficulty of basic migration/porting tasks
- initial performance/scalability benchmarking
uP3 Evaluation Report
Comments
Tasks (in rough order)
dynamictasklist: task list macros declared inside wiki-markup macros are not supported
Environment
Current myRutgers
- uP 2.5.2+ [local mods]
- Tomcat 5.5
- JDK 1.5 (32-bit)
- Solaris 9
- SPARC
uP3 Test
- uP 3.0 RC1
- Tomcat 5.5
- JDK 1.5 (32-bit)
- Solaris 10
- AMD Opteron
Middleware
- CAS Server 3.0.4+
- Oracle 9i
- Sun ONE LDAP