Hi,
Although I would love to play with the latest technology, I
need to consider the best solution to meet our business
needs. That Said. I am looking for the Best way to
communicate between servers/services on an Intranet.
We have a set of Java applications/servers/services (call
them what ever you like) that act as servers and clients.
They need to send data (large at times) between each other
and notify each other of events. Since we are on an
Intranet we have full control over issues of security,
protocols, etc...
The only real issue is that there are large amounts of data
(1K to 50K to 8+MB) and they need to be transferred securely
and quickly.
Some though has been given to RMI, RMI/IIOP, EJB, JMS, HTTP,
etc...
Any thoughts would be appreciated. Thanks.
...Dave
Discussions
Web tier: servlets, JSP, Web frameworks: Best way to communicate between servers/services on an Intranet
-
Best way to communicate between servers/services on an Intranet (2 messages)
- Posted by: David Brown
- Posted on: January 23 2002 15:17 EST
Threaded Messages (2)
- Best way to communicate between servers/services on an Intranet by Toby Hede on January 23 2002 20:06 EST
- Best way to communicate between servers/services on an Intranet by Adam Young on January 23 2002 21:27 EST
-
Best way to communicate between servers/services on an Intranet[ Go to top ]
- Posted by: Toby Hede
- Posted on: January 23 2002 20:06 EST
- in response to David Brown
I think that FTP or HTTP transfer is probably easiest. You don't need to have SOAP, but just get connections and transfer.
FTP is probably the best for transferring larger amounts of data, transfer it across, and then use HTTP to trigger a servlet at the receiver to notify it of the change. -
Best way to communicate between servers/services on an Intranet[ Go to top ]
- Posted by: Adam Young
- Posted on: January 23 2002 21:27 EST
- in response to Toby Hede
I would recommend using a JMS provider. There are numerous open source ones out there. They will p;rovide guarenteed once and only once deliver, can participate in transaction, etc.
JBoss has one built in, I believe it is spider MQ.
If you write your code to the JMS spec, you can use anything that supports it. IBM MQSeries is the leader in this area, if you need to go with the BIG iron. THere are many others.
Also, You may want to look at the Java Connector Architecture. I read a brief article on it in the latest Javapro magazine.