Release Date: February 03, 2011
Unless you have already done so, please download the Metro 2.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:
These files are used to install the Metro binaries into the respective web containers. The installation procedure is explained in the next section.
GlassFish 3.x bundles Metro by default. Should you want to replace the default Metro version by a more up-to-date release of Metro please check the Update Center for GlassFish 3.x. Follow these steps to install Metro 2.1 into GlassFish 3.x using the GlassFish 3.x Update Ceter:
bindirectory and run
In case you don't have an Internet access or want to experiment with an unofficial build or release of Metro not available on the official GlassFish 3.x update center, you may try the experimental standalone GlassFish 3.x installer. To stop GlassFish 3.x instance, install Metro 2.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>
GlassFish v2 bundles Metro. However you may want to replace the default Metro version by this more up-to-date release. To do that, you must pass the name of the GlassFish v2 top-level directory into ant. In our instructions bellow, that information is passed as an ant property value on the command line. To stop GlassFish v2 instance, install Metro 2.1 on top of it and restart the GlassFish v2 instance again execute the following commands:
asadmin stop-domain <domain-name> ant -Das.home=<GF_INSTALL_DIR> -f <METRO_INSTALL_DIR>/metro-on-glassfish.xml install asadmin start-domain <domain-name>
This process creates a backup copy of the original Metro installation, copies the Metro 2.1 jar files into your GlassFish v2 installation's lib directory and makes the necessary classpath alterations in the domain configuration file: domain.xml. It will also update the classpath for the utility script files: wsimport and wsgen.
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:
catalina.sh stop ant -Dtomcat.home=<TOMCAT_INSTALL_DIR> -f <METRO_INSTALL_DIR>/metro-on-tomcat.xml install catalina.sh start
For Tomcat, the installation process copies the two Metro jar files into Tomcat's shared/lib directory. No Tomcat configuration files are modified.
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.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.
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:
asadmin stop-domain domain1 ant -Das.home=<GF_INSTALL_DIR> -f <METRO_INSTALL_DIR>/metro-on-glassfish.xml uninstall asadmin start-domain domain1
catalina.sh stop ant -Dtomcat.home=<TOMCAT_INSTALL_DIR> -f <METRO_INSTALL_DIR>/metro-on-tomcat.xml uninstall catalina.sh start
Metro 2.1 release consists of following components:
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.
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.
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 https://svn.java.net/svn/wsit~svn/tags/2.1 metro-2.1-sources