Integration Broker

Hi,

We are planning to use develop a integration broker using MDB.

The idea is to take the files from FTP server and process asynchronously.

The volume of message is hyge and want to implement proper error handling mechanism to this.

There is any predefined framework available for these kind of task ?

Thanks

[346 byte] By [Baskara] at [2007-11-27 6:39:11]
# 1

http://mulesource.com and http://incubator.apache.org/servicemix/home.html are opensource and have ftp support.

Most of the commercial offerings from IBM, WebMethods and so on also support ftp too.

I would say MDB is optional as these ESB/EAI platforms do not mandate it.

Colin.

http://hermesjms.com

colincrista at 2007-7-12 18:08:14 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...
# 2

Also if you find yourself wishing to implement some of the Enterprise Integration Patterns using a simple to use Java library there's also Apache Camel...

http://activemq.apache.org/camel/enterprise-integration-patterns.html

we're in the process of integrating Camel with the ActiveMQ JMS provider; so that you can get the benefits of multiple transports & protocols and EIP; yet hide all this inside your JMS provider (if you want to see the world as JMS/MDB that is).

Here's the current protocols supported...

http://activemq.apache.org/camel/components.html

James

http://www.iona.com/

Open Source SOA

strachaja at 2007-7-12 18:08:14 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...
# 3

IBM's commercial support for FTP is seriously expensive, especially if you need to operate in a clustered environment. Last time I checked it was a per CPU license, so once you take into account each CPU in every server in every environment (integration-test / pre-prod / live etc), then you're talking serious cash just to read a file from an FTP server and pop it on a queue.

If you want to avoid the ESB/EAI tools (and I'm not suggesting you should) the route I would go down in future is a custom FTP -> JMS client using the Apache FTP classes in commons.net. For added robustness you could use a database and distributed transaction to keep a track of what messages had been sent, since the FTP part won't be transactional.

SteveNaivea at 2007-7-12 18:08:14 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...