This is the protocol stack we are planning to use for this architecture. As
per the initial architecture (also attached with this mail just in case
others haven't received it) the custom Gateways between the ESBs do
communicate over TCP/IP using HTTP/s(Inorder to support JMS).
Ashish
On 3/1/07, Mark Little <mlittle(a)redhat.com> wrote:
Can you connect them using HTTP, or FTP? Does it have to be raw TCP/IP?
Mark.
On 1 Mar 2007, at 14:18, Ashish Rajhansha wrote:
---------- Forwarded message ----------
From: Ashish Rajhansha <ashish.rajhansha(a)googlemail.com>
Date: Mar 1, 2007 12:49 PM
Subject: JBossESBs over TCP/IP
To: esb-issues(a)lists.jboss.org
Hi,
My company has several heterogeneous applications deployed at different
sites around the globe and we are aiming at integrating these using ESB. The
architecture will involve JBossESBs at each site running on clustered JBoss
AS with HA-JBossMQ(moving onto JBoss Messaging when its released). The sites
will use custom Gateways for communication between the JBossESBs in order to
achieve complete integration. The architecture is aims at supporting any
future applications added as services. The new services will be ESB aware
and hence will be just plug into the ESBs. Please find the architecture as
attachment.
Question - What is the most efficient way to integrate JBossESBs on
different sites (only communication available is TCP/IP) so that
applications plugged into any of them can provide services to any other
application anywhere on the infrastructure preferably without exposing the
JNDI globally.
Regards,
Ashish
<Discussion only.jpg>
_______________________________________________
esb-issues mailing list
esb-issues(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/esb-issues