AS2 protocol support

[desktopman]

I've been looking around for Fuse Message Broker/ActiveMQ AS2 protocol support, but have found next to nothing. Does anyone have any experience with this?

Also, there are various components that includes support for different message formats, but e.g. the EDI format has many many different versions. Is there a list of this somewhere?

[lvisnick]

I've been looking around for Fuse Message Broker/ActiveMQ AS2 protocol support

As of today, there is nothing available.  You could write your own camel component.  See here for guide on how to do that:

   camel.apache.org/writing-components.html

lorinda

[lvisnick]

there are various components that includes support for different message formats, but e.g. the EDI format has many many different versions. Is there a list of this somewhere?

My apologies, but I do not understand the question.  Are you looking for a list of the various EDI standards (there are hundreds).  Or are you looking for a list of components available that support any given EDI standard.  Or are you looking for a list of the different messages that are supported by FUSE Message Broker?

Please clarify, tx,

Lorinda

[desktopman]

Then I will clarify.

1. What type of EDI messages are supported out of the box in Fuse MB?

2. Are there other external components that add support for formats that aren't supported? This isn't necessarily only EDI, e.g. ebXML.

I guess unsupported formats could be added using Smooks but not having to deal with hundreds or thousands of formats would be quite the advantage.

Edited by: desktopman on Jul 22, 2009 6:09 PM

[lvisnick]

What type of EDI messages are supported out of the box in Fuse MB

None.  What FUSE MB supports is the same as ActiveMQ:

   http://activemq.apache.org/connectivity.html

There are containers, cross language clients and then protocols.  I think at the end of the day you are asking about protocols.

You can stuff any "standard"/format into a jms object - and send that as your jms message.  How you send it depends on the protocol.  You can use any of the out of the box supported protocols (openwire, stomp etc).

Or, if you find you want some other form of transport, then you can look to see what other camel components have been written by others (for example, ftp or email).

And finally, if you want or need some form that is not yet implemented, you can implement your own camel component.

Does this make sense/answer your question?

Lorinda

[desktopman]

Yep. Just started researching so some of the terms are a bit unfamiliar. Thanks for your help.

[cmoulliard]

Hi,

1. What type of EDI messages are supported out of the box in Fuse MB?

The Fuse Message Broker which is based on ActiveMq allows to transport any Java Object. So, it can transport any kind of EDI message defined in XML format, as a string or a collection of Java Objects.

Fuse Mediation Router offers an EDI connector which allows you to transform an inputStream into a org.w3c.Document Object (http://camel.apache.org/edi.html).

2. Are there other external components that add support for formats that aren't supported? This isn't necessarily only EDI, e.g. ebXML.

As ebXml is based on SOAP/Web service, this kind of connector could be added easily to Fuse Mediation Router. To format CSV or FIX data into a collection of Java Objects, you can use Apache Camel-Bindy : http://camel.apache.org/bindy.html

I guess unsupported formats could be added using Smooks but not having to deal with hundreds or thousands of formats would be quite the advantage.