It is expected that the user is familiar with both the Apache Maven project management tool and the Apache Ant scripting utility.
Jetspeed's security model requires a database to authorize users and to retain the user information. Jetspeed security should work with any JDBC 2.0 compliant driver. The following databases are tested:
The database configuration will be setup during the installation process. If you are not going to use the default Derby database, you need to select another database during installation.
In theory, Jetspeed 2 portals can be run under any servlet container supporting the 2.3 specification or greater. Successful Jetspeed 2 portal applications have been deployed using:
Jetspeed 2 can use the Tomcat Manager application for managing portlet applications with the Portlet Application Lifecycle Manager Portlet (PALM). To be able to do so it needs a configured Tomcat user with the predefined 'manager' role in the ${org.apache.jetspeed.server.home}/conf/tomcat-users.xml.
A minimal example tomcat-users.xml can look like:
<tomcat-users>
<role rolename="manager"/>
<user username="j2deployer" password="xxxxx" roles="manager"/>
</tomcat-users>
${org.apache.jetspeed.services.autodeployment.user}
and
${org.apache.jetspeed.services.autodeployment.user}
as described above.
Depending on what you want to do, you have the choice of installing Jetspeed from a binary release or from the sources. If you want to modify the core functionality of Jetspeed or contribute to the development of Jetspeed, you need to work with the sources. If you are only interested in building your own custom enterprise portal, you can start with a binary release of Jetspeed. Most people should start with the binary distribution.
Your installation instructions will depend on whether you are building from source or building from a binary distribution or installing with Jetspeed-2 installer .