This install guide covers the following types of installations:
The binary distribution of Pluto is packaged with Tomcat (currently version 5.0.28). Pluto leverages Tomcat to provide the web container in which the Pluto portlet container executes. The binary distribution includes the Pluto Portlet Container, The Portal Driver, and Pluto Testsuite.
To install the binary distribution:
The pluto library distributions are packaged to allow integration with an external portal server.
To install the library distributions to your portal server:
Installing the source distribution requires the most effort, and is recomended only for those individuals who are interested in modifying the container. The source distribution is basically a snapshot of the source code repository at a given time. Because of this, please see the build instructions, which will provide information about how to build Pluto from scratch.
To install the source distribution into tomcat:
Property | Value | Example(s) |
---|---|---|
maven.tomcat.home | Tomcat Installation Directory | \\usr\\local\\jakarta-tomcat.5.0.27 ,
c:\\jakarta-tomcat.5.0.27 |
maven.tomcat.version.major | Tomcat Major Version Number | 5 |
'maven fullDeployment'
Currently, to automate the deployment/installation of portlets you must utilize the source distribution of pluto.
In order to deploy a portlet application to pluto, you must follow the steps below:
Run the maven deploy goal on your war
This can be done by:
maven deploy -Ddeploy=/MyPathToMyPortlet/target/MyPortlet.war
See the Building From Source document for detailed instructions.
Alternatively, there is an interactive ant script in the portlet-deploy directory that will perform the same task as the Maven deployment goal.
[portal-home]/WEB-INF/data/portletentityregistry.xml [portal-home]/WEB-INF/data/pageregistry.xml
The Portlet entity registry file requires that you specify an application and a Portlet ID for your new Portlet. The Application ID must be unique. It also needs to know the name of the Portlet so that it can go out and find it in the webapps path. Furthermore, this information is used to map the Portlet name to the appropriate class path for loading the class. The following is an example of some additions you can make to the entity registry file:
<application id="6"> <definition-id>MyPortlet</definition-id> <portlet id="1"> <definition-id>MyPortlet.MyPortlet</definition-id> </portlet> </application>
The page registry provides Pluto with the layout information for your Portlet. The names used in the fragments must be unique as done in the following example:
<fragment name="MyPortlet" type="page"> <navigation> <title>My First Portlet</title> <description>...</description> </navigation> <fragment name="row3" type="row"> <fragment name="col3" type="column"> <fragment name="p4" type="portlet"> <property name="portlet" value="6.1"/> </fragment> </fragment> </fragment>