Apache tomcat 7.0.59
The username in the database that will be used to authenticate the type of resource: a JDBC DataSource provider Here we make use of the Apache Commons DBCP (Database Connection Pooling) library We have configured several important features of the database configuration specific to Tomcat including: attribute If you run the Jetspeed installer, which comes with Tomcat built-in,Īll the configuration is managed by the installer program for you. Getting Jetspeed to run in Tomcat requires some minimal configuration describing in the following section. Configuring a JAAS Realm - you can configure JAAS Realm features in Tomcat specific to Jetspeed like providing your own role and user classes.Renaming the Context Path - you can give Jetspeed a different context path name.The classes from these jars are shared between Jetspeed and all portlet applications Common Class Loader - Jetspeed requires loading several jars in Tomcats shared class loader.Tomcat requires a context file be provided in order for Jetspeed to use Tomcat connection pooling Database Configuration - By default, Jetspeed lets Tomcat manage the database connections.
Cross Context Invocation - Jetspeed must be configured in Tomcat to execute cross-context request dispatching.It has a few special requirements in order for it to run in Tomcat: However, since Jetspeed is also a portal server, with the ability to include content from other deployed portlet applications in the application server, Jetspeed is a normal web application, thus it runs in Tomcat like any other web application.