Java Applications talking to each other - best way

[Kurt M Peters]

I have a program (not a servelet) that is controlling a piece of
equipment. I want to be able to "talk to it" and see alarms, set-points,
graphs, etc.
What is currently the "approved/best" way to do the communications?
I was thinking, initially, of just creating a socket-server and
communicating via my own personal message set via a socket, but I think that
may not be the "best" way. Would someone recommend something like SOAP,
CORBA, RMI, instead?
Just wondering what the "way to go" is now-a-days?
Kurt

 

[Ferenc Hechler]

Hi Kurt,

talking from java to java RMI is the "way-to-go".

RMI allows you to use remote Java Objects seamlessly. It uses java
serialization without any abstraction level and is much faster than SOAP.

SOAP is sessionless and as such holds no remote objects for you. It is best
practice for Interoperablity with other Systems (non-java) and to
communicate over Fire-Walls (HTTP / HTTPS)

CORBA is similair to RMI but only necessary if you want to communicate to
non-java systems.

One thing I did not like with RMI was the need to start the standalone
application rmiregistry.
If you need a many-to-one (frontend to backend) communication you can
integrate the registry
into the backend-process (see "Using Java RMI without rmiregistry"
http://www.st.informatik.tu-darmstadt.de/static/staff/Haupt/rmi.html )

Best regards,
feri

 

[Sonal]

Hi Kurt,

Do check JMX Java Management Extensions to see if they suit you.

Sonal