Jim Helwig (University of Wisconsin-Madison) Aaron Grant (Oakland University) Lori Tirpak (Oakland University) Session presentation at the 2012 Jasig Sakai Conference uPortal is a highly powerful and flexible portal framework that institutions have used in a variety of innovative ways to solve very real campus problems. This presentation showcases two different uPortal implementations demonstrating the diverse ways campuses make use of a central portal. Oakland University (located in beautiful Oakland County Michigan) is a relative newcomer to uPortal: they first launched their uPortal-based campus portal, MySail, in 2009, using framework version 3.1. But on February 22nd 2012 they became the first school to run a portal based on uPortal4 in production. In this session we will showcase the new Oakland MySail portal and discuss the processes they used to migrate to uPortal 4. We will cover tips and tricks, best practices, and lessons learned. We will also highlight the use of Jasig portlets and talk about getting the most from those collaborative portlet projects. The University of Wisconsin-Madison has operated a campus portal, My UW-Madison, since 2001. In 2010 we rolled out virtual portals running on the same instance for our 13 sister campuses in the University of Wisconsin System. A migration to uPortal was completed in 2006 and the infrastructure was upgraded to uPortal 4 in April of this year. In this session we will highlight the personalized yet unified portal experience for our applicants, students, faculty and staff. We will showcase some of the innovate portlets we have implemented as well as our adoption of Jasig portlets. Finally we will highlight the benefits of developing Open Source portlets and engaging with the uPortal community.

1. Lori Tirpak & Aaron Grant
June 10-15, 2012
Growing Community;
Growing Possibilities

2.  Oakland University is located in Rochester, Michigan
 We have approximately 20,000 students
 We have been running a Portal environment for 5 years and
converted to Jasig uPortal in 2009
 We were running uPortal 3.1.1 before upgrading to 4.0.2
 We have 2 full time staff members and 4 student employees
dedicated to uPortal, CAS, uMobile and portlet development
 We have only focused on student experience
 Staff and faculty can log in but there are limited predefined
features
2012 Jasig Sakai Conference 2

3.  Jasig uPortal 4.0.2 (soon to be 4.0.5)
 Red Hat Enterprise Linux 5.0
 Apache Tomcat 6.0.35
 Oracle JDK 1.6.30
 Groovy 8.4
 PostgreSQL 8.4
 Maven 3.0.3
 Ant 1.8.2
2012 Jasig Sakai Conference 3

4. ◦ LDAP - Red Hat Directory Server
◦ CAS (Central Authentication Service) 3.4.8
◦ Ellucian (formerly SunGard HE) Banner
◦ F5 BIG-IP 3900 using Local Traffic Manager
Used for Load Balancing, SSL Termination, Port
Redirection
2012 Jasig Sakai Conference 4

5. uPortal Web Servers
◦ 2 Nodes - 50/50 Load Balanced
 Dell Poweredge R610
 Two Quad Core Xeon Processors
 Processor, X5550, 2.66/6.4, 8mb L1 Cache Intel Dual
Socket Nehalem
 24 gb of RAM
uPortal Database Servers
◦ 2 Nodes - Primary and Failover
 Dell Poweredge R610
 Two Quad Core Xeon Processors
 Processor, X5550, 2.66/6.4, 8mb L1 Cache Intel Dual
Socket Nehalem
 24 gb of RAM
2012 Jasig Sakai Conference 5

6. 2012 Jasig Sakai Conference 6

7.  LDAP and Banner group configurations
◦ This allows us to target specific groups of users with Tabs and
portlets
 Progress to Degree portlet
◦ Displays academic courses needed to complete degree
 Grades portlet
◦ Displays to student midterm and final grades
 Academic Information portlet
◦ List of student ID, Major, Advising info
 Class schedule portlet
◦ List of courses a student is registered for along with a link to
OU Bookstore to purchase required text books
2012 Jasig Sakai Conference 7

8.  LDAP Password Information portlet
◦ Password age, best practices and link to reset password.
 Groovy build process
◦ Rapid deployment of uPortal, Puppetmaster script that runs
Maven and Ant commands
 CAS single sign
◦ Google apps for education, Moodle, Org Sync, Symplicity
NACELINK, Blackboard Xythos, National Student Clearinghouse
 Oakland University Google custom search engine integrated into
Jasig Search portlet
2012 Jasig Sakai Conference 8

9.  Announcements
 Feedback
 Calendar
 Campus Map
 Bookmarks
 Weather
 Simple CMS portlet
 News Reader RSS
 Jasig widget portlets (uPortal tips, sitemap, Google
map, Google search, etc)
 Search
2012 Jasig Sakai Conference 9

10.  Drew Wills and Jacob Lichner from Unicon worked with us to re-skin
uPortal 4.0.
 Drew worked with us to migrate our uPortal from 3.1 to 4.0.
 We decided to start from scratch on student layouts. We deleted all
database content.
 We moved from SVN to GitHub for our source code repository.
Using GitHub has improved our upgrade process to include patches
from the latest Jasig releases
 We implemented Groovy Build process which helps with rapid
deployment of uPortal. Puppetmaster script runs Maven and Ant
commands
 We created Quickstart data to help streamline the Portal build
process
2012 Jasig Sakai Conference 10

11.  Load test. Load is higher than prior versions.
 Use initportal on the first node and then deploy-ear on all other
nodes. We had layout issues with our tabs because we used
initportal on all nodes.
 Have a minimum of 4 gb for heap space. We were experiencing
Tomcat crashes and Tomcat 500 errors.
 Reduce logging levels to info or warn. Some portlets come with
logging levels of debug or trace and this caused a lot of RAM
usage and IO on disk.
 We fine tuned our PostgreSQL database to optimize our uPortal
performance
2012 Jasig Sakai Conference 11

12.  We deactivated uPortal event tracking. This was putting a high
load on front ends and database server and utilizing 50% of our
switch traffic. 500 mb per second.
 We had to change code on OU and Jasig portlets to catch and not
display 503 errors.
 We doubled physical memory on front ends and database server
from 12 to 24 gb
 With uPortal 4.0.5 and our additional portlets we found a
need to increase the amount of files that could be opened at
once in the OS, the default for Red Hat Enterprise Linux was
1024, we increased this to 2048.
2012 Jasig Sakai Conference 12

13. 2012 Jasig Sakai Conference 13

14. 2012 Jasig Sakai Conference 14

15. https://mysail.oakland.edu
2012 Jasig Sakai Conference 15

16. 2012 Jasig Sakai Conference 16

17. 2012 Jasig Sakai Conference 17

18. 2012 Jasig Sakai Conference 18

19. 2012 Jasig Sakai Conference 19

20. 2012 Jasig Sakai Conference 20

21. 2012 Jasig Sakai Conference 21

22. 2012 Jasig Sakai Conference 22

23. Jim Helwig
June 10-15, 2012
Growing Community;
Growing Possibilities

24. 2012 Jasig Sakai Conference 24

25.  5 clustered Solaris servers
 uPortal 4.0.5, Tomcat, Apache httpd
 Oracle portal database
 Nortel Alteon Layer 4 load balancing
2012 Jasig Sakai Conference 25

26.  CVS - legacy portlets
 SVN - new portlets, configuration files
 GitHub - uPortal framework
 Pre-dev – framework testing
 Shared dev – some portlet development
 Test – integration testing
 QA – deployment validation, customer testing
 Production
 Jenkins, Perl, shell scripts for deployment
 jMeter for load testing
2012 Jasig Sakai Conference 26

27.  Attribute sources
◦ Shibboleth
◦ LDAP
◦ various other databases
 Group sources
◦ PAGS groups based on attributes for major
populations and enterprise roles
◦ Local group store for administrative groups
◦ External custom group database for fine grained,
manually managed groups
◦ Likely to use Grouper in the future
2012 Jasig Sakai Conference 27

28. 2012 Jasig Sakai Conference 28

29.  Single, clustered portal application
 Three domains
2012 Jasig Sakai Conference 29

30.  Publicly accessible curricular guide
 View differs, depending on whether or not
you are authenticated
2012 Jasig Sakai Conference 30

31.  UW-Madison campus portal
 80,000+ faculty, staff, students, applicants
2012 Jasig Sakai Conference 31

32.  UW System wide portal for 13 campuses
 Campus-specific skins
2012 Jasig Sakai Conference 32

33. 2012 Jasig Sakai Conference 33

34. 2012 Jasig Sakai Conference 34

35.  Add, remove, move content
 Add tabs
2012 Jasig Sakai Conference 35

36. 2012 Jasig Sakai Conference 36

37. 2012 Jasig Sakai Conference 37

38. 2012 Jasig Sakai Conference 38

39.  Focused on personalized content
 Aggregation of campus applications
 Simple Content Management
 IFrame
 XML Transform
 Dynamic Menu
 WebProxy
 Jasig Bookmarks, Weather and Courses
 And many custom portlets
2012 Jasig Sakai Conference 39

40. 2012 Jasig Sakai Conference 40

41. 2012 Jasig Sakai Conference 41

42. 2012 Jasig Sakai Conference 42

43. 2012 Jasig Sakai Conference 43

44. 2012 Jasig Sakai Conference 44

45. 2012 Jasig Sakai Conference 45

46. 2012 Jasig Sakai Conference 46

47. 2012 Jasig Sakai Conference 47

48. 2012 Jasig Sakai Conference 48

49. 2012 Jasig Sakai Conference 49

50. 2012 Jasig Sakai Conference 50