Introducing the message exchange

The company I work for is called eVision, and their main product is called MessageXchange. (See what happens to your spelling when you’re looking to find a good .com address?)

It’s basically a B2B message broker… messages go in, messages go out, and in the middle they get conditionally routed and transformed. The upshot is you can set up to hook up a bunch of systems that use completely different types of message… one system’s PurchaseOrderCreate in a fixed-length FTP’d batch file can happily go along as another system’s PurchOrdReq XML HTTP message.

The clever bit is in the monitoring, letting you see what’s pumping through the system at any time. And the fact that the whole shebang is configurable through a web interface.

It started out as a software package… well, not exactly a package, not in the MS Office sense, but a system you’d plonk on a Windows server or two and away you go. I haven’t been directly involved, but over the past year they’ve rejigged it as an ASP… a paid hosted service, that is, so that if you don’t want to run it on your own boxes, you pay to access it on fully maintained servers instead.

At the same time they’ve expanded its reportoire to cover a lot of the new and emerging XML standards such as ebXML and RosettaNet. As well as some of the more ancient, creaking standards like EDI.

Handy stuff. The whole B2B area must surely grow, it’s a no-brainer for reducing the cost of commerce. Will be an interesting area to watch. In fact I might get one of the guys to expand a bit on some of these topics…

If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.

1 thought on “Introducing the message exchange

Comments are closed.