Currently, only Pluto 1.1 has a binary distribution.
There are a number of distributions to choose from depending on your needs.
svn checkout https://svn.apache.org/repos/asf/portals/pluto/trunk/ plutoTo check out Pluto 1.1.4 source to the 'pluto' directory use this command:
svn checkout https://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.4 plutoZipped up Pluto 1.1 source distributions can also be downloaded from a distribution mirror.
~/.m2/settings.xml
and add the <pluginGroups> element:
<settings> ... <pluginGroups> <pluginGroup>org.apache.pluto</pluginGroup> </pluginGroups> ... </settings>
org.apache.pluto
specified as a <pluginGroup>
,
then the pluto:install
will fail.
<PLUTO_SRCHOME>
is the local directory where the
Pluto 1.1 source distribution has been checked out or unzipped into.
$> cd <PLUTO_SRCHOME> $> mvn install $> mvn pluto:install -DinstallDir=path/to/appserver
The install
goal is a built in Maven 2 lifecycle
which builds the project artifacts and installs them into the Maven
repository.
The pluto:install
goal will take the resulting artifacts
and properly deploy them within the configured Tomcat installation.
Currently, the Pluto install has been tested on Tomcat 5.5.9, 5.5.17 and 5.5.20, 5.5.23, and 6.0.13.
The Tomcat 5 archive can be found here.
If installing to a directory that contains spaces, installDir
needs to be enclosed within quotes:
C:\pluto> mvn pluto:install -DinstallDir="C:\Program Files\Apache Software Foundation\Tomcat 5.5"
This section documents the manual installation of Pluto 1.1 and 2.0 into Tomcat. It replaces
the pluto:install goal, but requires that the built-in Maven 2 install goal
(mvn install
) be run from <PLUTO_SRCHOME>
.
Step 1:
$> cd <PLUTO_SRCHOME> $> mvn install
Step 2: Copy the following to
<TOMCAT_HOME>/shared/lib
:
<TOMCAT_HOME>/common/endorsed
:
<TOMCAT_HOME>/conf/Catalina/localhost
:
<TOMCAT_HOME>/webapps
:
PortletSession
attributes in Pluto, modify
the Connector element for port 8080 in <TOMCAT_HOME>/conf/server.xml
by
adding the following attribute and value: emptySessionPath="true".
pluto
'
to run the Security Mapping Test. So before starting tomcat, you should
edit <TOMCAT_HOME>/conf/tomcat-users.xml
, add the
role 'pluto
', and add a user in that role. The simplest way
to do this is to edit add the 'pluto
' role to the
'tomcat
' user's record. Here is a sample
tomcat-users.xml
file:
<?xml version="1.0" encoding="utf-8"?> <tomcat-users> <role rolename="manager"/> <role rolename="pluto"/> <role rolename="tomcat"/> <role rolename="role1"/> <user username="tomcat" password="tomcat" roles="tomcat,pluto,manager"/> <user username="role1" password="tomcat" roles="role1"/> <user username="both" password="tomcat" roles="tomcat,role1"/> <user username="pluto" password="pluto" roles="pluto,manager"/> </tomcat-users>
startup.bat
(for windows) or startup.sh
(for
*nix) in <TOMCAT_HOME>/bin
, and browse to
http://localhost:8080/pluto/portal
. Login to Pluto using
the user and password you just created in tomcat-users.xml
.
If you added the 'pluto' role to the 'tomcat' user's record, you can
login as 'tomcat/tomcat'.