The document discusses IBM and Marist College's efforts to port Sakai to run on WebSphere Application Server. Key points: - They notified the Sakai Foundation of their goal and tracked issues in JIRA. After testing, they contributed code back to the community. - Challenges included differences between WebSphere and Tomcat, and integrating with other groups' work. They collaborated to resolve over 60 issues. - Automated testing scripts were developed to help with frequent regression testing as the community code evolved rapidly towards release. - After review, the Sakai community accepted the code contributions and they were merged back into the main codebase.