$Date: 2008-11-23 12:57:20 -0500 (Sun, 23 Nov 2008) $
[français]
MetPX is a message switching system for use with Wmo Global Telecommunications System circuits based on TCP/IP. Developed at the Canadian Meteorological Centre of Environment Canada for our own use. MetPX is a work in progress, the development process is being externalized in the hopes of fostering a community around a switching system which all can share and improve together. The system is already production quality for a limited set of features and is in production use at the CMC as the core of our national bulletin switching infrastructure. The software is under continuous, but low-intensity development. Features are carefully being layered on top of existing stable functions.
[Documentation]
[Download]
[Getting Source Code]
[References & Links]
[ mailing-lists: metpx-devel.,
metpx-commit. ]
[ Main Project page: Sourceforge ]
Protocol support:
features:
There are three modules in the project right now. Modules of MetPX are named after species of plant which are endangered in Canada (see Species at Risk for more details.)
Platform: we build packages for Debian Derived Linux (Debian Sarge, Etch. any Ubuntu will do). Any modern Linux should do. (stock 2.6 or 2.4 with many patches.) Python >2.3
Licensing: GPLv2
Documentation
Sundew is rather stable for now, current work is on improving the installation process by
implementing Debian packages. A package for the sundew module is available from
the sourceforge site, in either source or .deb form. We hope to produce packages for
columbo at some point.
Currently internal installations are done, one at a time, from source. Development
is done on the trunk release. When we install operationally, the process consists
of creating a branch, and running the branch on a staging system, and then implementing
on operational systems. There are README and INSTALL files that can be used for
installation of sundew. One can follow those instructions and get an initial installed
system.
It is critical to install the cron cleanup jobs (mr-clean) since otherwise the
server will slow down continuously over time until the system slows to a crawl. If you
Best bet is to subscribe to the mailing list and let us know what is stopping you from
trying it out, it could inspire us to work on that bit faster to get some collaboration
going.
with those explanations, feel free to grab a snapshot can be obtained using subversion via:
AMQP implementations are not JMS plumbing. JMS standardizes the API programmers use, but not the on the wire protocol. So typically, one cannot exchange messages between people using different JMS providers. AMQP standardizes for interoperability, and functions effectively as an interoperability shim for JMS, without being limited to Java. AMQP is language neutral, and message neutral. there are many deployments using python, C++, and ruby. One could adapt WMO protocols very easily to function over AMQP. JMS providers are very Java oriented.
Getting Source Code
svn co https://metpx.svn.sourceforge.net/svnroot/metpx/trunk
Available for anonymous read-only access. One can also download a stable release by doing an checkout by accessong the currently highest numbered branch.
References & Links
Other, somewhat similar software, no endorsements or judgements should be taken from these links: