Can you provide a more concrete example of what you're trying to achieve?
In general, how you integrate these services will be guided by their design - how they were designed to communicate with the world around them - using JMS, FTP, HTTP etc. From there, the ESB should be able to provide the pluming to get those to wherever they need to go using Content Based Routing, Transformation... + crossing protocols etc
A good place to start getting a feel for the capabilities of JBossESB is in the Quickstarts and the Trailblazer.
Excuse the typo...
From there, the ESB should be able to provide the pluming to get those to wherever they need...
should have been...
"From there, the ESB should be able to provide the pluming to get those messages to wherever they need..."
I could provide you with the intended architecture if you could provide me with your mail id. i am unable to post it here.
Ups, sorry Ashish! You were actually asking a different question - more to do with crossing network boundaries.
JBoss ESB doesn't currently centrally manage multiple ESB instances, so, my take on your scenario would be that for now it's basically a network admin issue for your IT guys to work out i.e. making sure messages can get to their destinations and be accessed. Mark would have more to offer you on this I'm sure.
Security is something that's on the roadmap.
Is the requirement to have a TCP/IP connection that is active?
Essentially staying a connected and passing messages back and forth.
Or is the requirement a raw socket open/close without a constant connection.
Also from an input or output perspective is the concept:
TCP/IP -> BUS -> Service
BUS -> TCP/IP -> Service
ROUTING BUS <- TCP/IP <- BUS
Are the TCP/IP connections workers to process messages, etc... from the bus?
Just trying to figure out if it is something similar to a requirement I have.
Provide me with your mail id and i shall send you the architecture to look at.
Can you post here? Or join the esb mailing lists and discuss there.