The release packaging and flavours

Proximity is released in public in various packagings:

  • Proximity/Extend - Proximity bundled with Extend appserver.
  • Proximity/Jetty - Proximity bundled with Jetty webapp container.
  • WAR - The standard J2EE Web Application Archive format.
Proximity is released in public in various configurations (flavours):
  • default - The default general purpose configuration.
  • demosite - The configuration used for demoing. Not usable in real life.
  • minimal - The smallest working subset of Proximity (without indexing, search, artifact view, etc.).
  • pmaster - Proximity configured as "master" in chained configuration.
  • pslave - Proximity configured as "slave" in chained configuration.
The "default" configuration should suffice in 90% cases (a rought estimate :). For more information about configuring Proximity, see Configuration.

Deployment guide for bundled packaging

Proximity Extend bundle

Just unzip the package, and you will have a Extend with Proximity configured. Use the provided shell scripts to start it up.

Proximity Jetty bundle

Just unzip the package, and you will have a Jetty with Proximity configured. Use the provided shell scripts to start it up.

Deployment guide for WAR packaging

Proximity is released as standard J2EE Web Application Archive (WAR). Due to default IoC container used (Spring Framework), it is a must to unpack the WAR before using it (Tomcat does it per default). Since Proximity uses SLF4J API for logging, see SLF4J Site for additional logging or deployment-time configuration possibilities. The default logging back-end is log4j.

Now, we will see some web container specific tasks for Proximity deployment.

Apache Tomcat

Proximity has been extensively tested on Tomcat 5.5.x line. For deployment on Tomcat, you simply need to "drop" the WAR file in $CATALINA_HOME/webapps directory, or better, unzip it into $CATALINA_HOME/webapps/proximity directory. You may need some additional steps:

  • If you can, remove log4j.jar from Tomcat installation, or swap logger implementation during deployment, as described on SLF4J site.
Advanced users may edit the configuration files. Also, please review the logging settings (Log4j currently), since it may not be suited your needs!

Jetty

Proximity has been extensively tested on Jetty 6.1.x line.

Simply "unpack" the WAR file in $JETTY_HOME/webapps/proximity directory.

Advanced users may edit the configuration files. Also, please review the logging settings (Log4j currently), since it may not be suited your needs!