Web Contexts Included in uPortal
- Jen Bourey
- Laura McCord
The current uPortal distribution includes a number of deployed webapps, each with its own web context.
If your selected portal configuration requires you to explicitly map all Tomcat web contexts (e.g. with some mod_jk configurations), you will need to map the following contexts:
Core Modules
Context | Use |
|---|---|
/uPortal | The portal itself |
/cas | Bundled CAS server and uPortal's default authentication strategy. This may be removed if your institution is not using CAS or is using a separate CAS server. |
/ResourceServingWebapp | Static, versioned UE resources such as javascript, css, and image libraries. This application offers the portal and portlets a common target to ensure the user's browser can make efficient use of local caching. |
Test Suites
Context | Use |
|---|---|
/cas-proxy-test-portlet | CAS proxy test and resources for testing CAS proxy capabilities from other portlets. |
/pluto-testsuite | JSR-168 tests |
/FunctionalTestsPortlet | Additional portlet tests |
Removing a bundled webapp
All bundled webapps (other than uPortal itself) are included in the portal's build via an overlay. To remove a bundled web context from the build and from the deployed portal, you will need to perform the following steps:
- Remove the line <module>dependency</module from uportal-portlets-overlay/pom.xml for the item you wish to remove. You may also optionally delete the directory for that module.
- Remove the dependency and webModule elements for this item from uportal-ear/pom.xml.
- If your build.properties file contains the line "
cleanShared=false", then next execution of "ant clean deploy-ear" will remove the webapp from Tomcat