Attached is a zip file of the student schedule portlet used at the University of St. Francis in uPortal 2.5.2 which displays a student schedule from our Banner ERP system. It
The primary component of the portlet queries sfrstcr to get the courses a student is registered for. It then loops through each course the student is in and gets additional details such as the instructor(s) from sirasgn, and meeting times from ssrmeet.
You'll notice that the portlet also does an insert into a table called activity_log. This is just our custom logging table where we insert the pidm of the currently logged in user, an event_code of every item rendered in our portal, and a description about what was rendered. This allows us to really analyze the usage of our portal, and join it to all of our banner data to look at trends by age, major, student type, or any other attribute in the system.
It requires a jdbc connection to the Banner database, called BannerDb, and it requires the pidm of the student to be obtainable by the portlet. The implementation details of how to do that are surely going to be different at each school. At USF, we had the students pidm stored in the workforceId attribute in Novell eDirectory, and our portal would grab that to use.
...