Separation of WebService & Enterprise Java Beans on two different Machines

Question

All,
Have anybody been able to separate the webservices and the ejb's into two weblogic
servers. To be precise, I want to invoke a web service and the web service should
be able to talk to the weblogic server a different one than that is hosting the
webservice to execute the ejb methods.
Any help would be appreciated.
Thanks,
--Pratap

Answer 1

Rob, thanks for your input. theoretically,
i agree with you. but using a pure web server
to pick up web services request nicely fits
the already widely accepted web-tier/ejb-tier
design and implementation.
could you please take a look at my message
184 Help needed in web service example - "david zhang" , 10 Dec 2001
i really need some help on that. thanks in advance.
david
Rob Woollen <[email protected]> wrote:
There's pros and cons to both approaches.
The reasons that I generally recommend co-location are:
1) Much better performance -- We can optimize the web/web service -->
EJB call to be a direct method call. If they are in separate
processes/machines, you will need to go through rmi marshalling and
unmarshalling of the data and send your requests over a network connection.
2) one less remote programming error case to handle -- Anytime that you
make a remote call, you need to handle a set of error cases that do not
occur with in-process calls. Failures during marshalling, sending the
request, during the response etc. Distributed programming is hard.
I would avoid it whenever possible.
-- Rob
david zhang wrote:
maybe i have the same thoughts as Pratap has.
i notice that this is actually a difference
between Apache SOAP implmentation and Weblogic
web service implementation. In the Apache's
implementation, a pure WEB server with a servlet
engine is able to pick up a service request.
if the request handler needs to use an EJB running on
another application server, it just call it.
so with apache implementation, i can put all EJBs
on one application server. with weblogic's implementation,
there has to be an APPLICATION server up front to
to pick up a web service. sounds like an overkill or
in elegant design. actually, Sun blueprints has an article
"Initial Thoughts on Web Services", and it is my understanding
that a web tier should pick up a web service.
Rob, please give us the magic:-)
regards,
david
Rob Woollen <[email protected]> wrote:
It's possible to do this, but I wouldn't recommend the configuration.
Why do you
want to do this?
-- Rob
Pratap Srivastav wrote:
All,
Have anybody been able to separate the webservices and the ejb's
into
two weblogic
servers. To be precise, I want to invoke a web service and the
web
service should
be able to talk to the weblogic server a different one than that
is
hosting the
webservice to execute the ejb methods.
Any help would be appreciated.
Thanks,
--Pratap