KeppiProxy can be made to portlet container using portal platform
which runs on top of servlet container.
Get Jetspeed2 installer distribution
or get Liferay package bundle with Tomcat 6.0
or get uPortal-only release
or get iPoint war file package
or get Sakai demo package.

Get zip-package containing bat- and
shell-scripts for copying relevant files from portal directories to
KeppiProxy-directory and parameter files.

jetspeed-script presumes that Jetspeed-portal is installed in
directory <user's home>/Jetspeed-2.1.2 (in Win32
C:\Apache\Jetspeed-2.1.2).

liferay-script presumes that Liferay-portal is installed in
<user's home>/liferay-portal-tomcat-6.0-5.0.1
(in Win32 C:\liferay-portal-tomcat-6.0-5.0.1).
Login to liferay with username test@liferay.com
and password test.

ipoint-script presumes that zip-file has been extracted
to <user's home> with directory name ipoint_oe_2.4.2_war

sakai-script presumes that zip-file has been extracted
as <user's home>/sakai-demo-2.5.4
(in Win32 C:\sakai-demo-2.5.4).
Login to sakai with username admin and same password.

All scripts presume that KeppiProxy is installed in
<user's home>/KeppiProxy.  These directories can be changed giving
arguments to scripts. Directory of KeppiProxy-program as first argument
and directory of portal program as second argument.

uPortal must be installed replacing file build.properties with
the one in portals.zip-file. Property named server.home can be edited from
this file to location of KeppiProxy-program. In supplied file
location points to <user's home>/KeppiProxy.
Then running command
ant hsql
and then command
ant initportal
After that script uportal.sh (or uportal.bat) must be run.
Script presumes that KeppiProxy is installed in
<user's home>/KeppiProxy. This directory can be changed
giving argument to script.
If tomcat-examples are hosted from KeppiProxy-server,
it must be installed to port 8080.

iPoint-zip-file can be extracted to user's home directory.
KeppiProxy-server must be installed to port 8080 for iPoint-portal to
work.  Database must be created and populated as described in portal's
installation instructions. By default mysql-database is
used. ipoint-script assumes that mysql-database has no password for
root user.  If that is not the case, file
ipoint_oe_2.4.2_war/iPoint/META-INF/context.xml from portals.zip-file
must be edited to change password-attribute. If other database is
used, attributes driverClassName and url must be also changed, and
jdbc-driver-jar-library must be copied to shared/lib-directory. Then
ipoint.sh (or ipoint.bat) must be run. Admin-username with same
password can be used to log in to the portal.

It is possible that portal containers may not run together,
so only one portal can be installed at one time.