Physical Deployment of a J2EE application

I may have missed something in my research and training in J2EE and EJB but is it possible to physically separate the tiers of the application. That is, the JSP's and servlets within a web container run on a physically different machine than the EJB's in the EJB container. And usually, the database is is on its own machine. I normally see the term J2EE server refer to a combination of a web container (aka web server) and EJB container. If this is the case, where does the distributed in "distributed" architecture come in.

With Microsoft ASP and COM+, the server running IIS can be physically separate from the application server hosting the buisness components. How does this relationship translate in J2EE?

[741 byte] By [mhartman] at [2007-9-26 3:33:58]
# 1

Ofcourse that is possible. EJBs are remote objects (i.e., you call methods on them via RMI - Remote Method Invocation).

Accessing an EJB remotely is exactly the same as accessing it locally - lookup the home interface via JNDI, use the home interface to create instances and get the remote interface, call business methods on the remote interface.

Jesper

jesper1 at 2007-6-29 12:02:58 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...
# 2
Yes, but what of the physical aspects? How do enable the invocation of remote object methods from one container (e.g. web container) to another (e.g. EJB container)? RMI is the enabling technology and IIOP is the wire protocol (usually) but how do you bolt the pieces together?
mhartman at 2007-6-29 12:02:58 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...