Metro 2.2.1-1

Release Date: September 03, 2012

Downloading Metro 2.2.1-1

Unless you have already done so, please download the Metro 2.2.1-1 ZIP archive. Once downloaded, you can expand it by executing following shell command:


On Windows or Mac, you may as well just double-click the zip file to expand it.

The expanded metro directory contains following ant files:

  • metro-on-tomcat.xml
  • metro-on-glassfish-3.xml

These files are used to install the Metro binaries into the respective web containers. The installation procedure is explained in the next section.

Installing Metro 2.2.1-1

GlassFish 3.x

GlassFish 3.x bundles Metro by default. You should not update Metro version separately - always update to full Glassfish update.

In case you want to experiment with an unofficial build or release of Metro not available on the official GlassFish 3.x update center or in the official GlassFish update, you may try the GlassFish 3.x installer. To stop GlassFish 3.x instance, install Metro 2.2.1-1 using the standalone installer on top of it and restart the GlassFish 3.x instance, execute the following commands:

asadmin stop-domain <domain-name>
ant -Das.home=<GF_INSTALL_DIR> -f <METRO_INSTALL_DIR>/metro-on-glassfish-v3.xml install
asadmin start-domain <domain-name>


The installation process for Tomcat is very similar to that of GlassFish v2. Again, the top-level directory of the Tomcat installation is passed as an argument to the ant command. To shutdown Tomcat, change directories, invoke ant, and restart Tomcat by executing these commands: stop
ant -Dtomcat.home=<TOMCAT_INSTALL_DIR> -f <METRO_INSTALL_DIR>/metro-on-tomcat.xml install start

For Tomcat, the installation process copies the two Metro jar files into Tomcat's shared/lib directory. No Tomcat configuration files are modified.

Updating to Metro 2.2.1-1

Once a version of Metro web services stack has been installed on a web container, it can be updated with a new version of the Metro binaries. To update your Metro installation to Metro 2.2.1-1, follow the same steps used for the initial install, shown above.

Note that for GlassFish v2, the second and subsequent installs only update the Metro binaries; no configuration files are modified.

Uninstalling Metro

To remove the Metro binaries and configuration changes from your web container, the steps are almost identical to the ones in the installation process. The following steps will restore your web container to the state before Metro installation:

GlassFish 3.x

asadmin stop-domain <domain-name>
ant -Das.home=<GF_INSTALL_DIR> -f <METRO_INSTALL_DIR>/metro-on-glassfish-v3.xml uninstall
asadmin start-domain <domain-name>

Tomcat stop
ant -Dtomcat.home=<TOMCAT_INSTALL_DIR> -f <METRO_INSTALL_DIR>/metro-on-tomcat.xml uninstall start

Release Notes

Metro 2.2.1-1 release consists of following components:

Users Guide

We have created a snapshot of Metro Users Guide at the time of this Metro release. You may also wish to consult the latest version of the Metro Users Gude.

Technical Support

Please subscribe to the users list and send comments/feedbacks/opinions to the list. Additionally, we encourage you to report any bugs you might find while using Metro through our Metro issue trackers.

Workspace Snapshot

If you'd like to hack the source code used to build these binaries, please check out the Metro sources running the following command from the command line:

        svn export -r 7272 metro-sources
This component is released under the Common Development and Distribution License (CDDL) version 1.1 + GNU General Public License (GPL) version 2. You must agree to these licenses as part of installation before viewing and/or using the code.
Terms of Use; Privacy Policy; Copyright ©2013-2017 (revision 20160708.bf2ac18)
Please Confirm