I haven't heard of it done this way. My understanding is that you would have
1 (or more if clustering) front-end web server/servlet/jsp engine on the
front tier. They would communicate with the middle-tier orion app servers
for ejb stuff. There you would have one or more clustered for fail-over.
Question on this..if anyone knows. If we use statless EJB, do we need a
clustered environment for fail-over? Or is there no use in fail-over for a
statless ejb setup? I definitely want to store session state on the
HttpSession side, so our JSP pages can dynamically access everything to
display. I heard if you use HttpSession state, then you should use EJB in a
statless method, so I am not sure if that means I should have a cluster of
EJB servers for fail-over. However, I would believe a cluster is good for
load-balancing. What is the setup in this manner?
Thanks.
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 19, 2000 2:27 PM
> To: Orion-Interest
> Subject: Need some ideas
>
>
>
>
> Dear all
>
> Has anyone been able to set up 2 orion servers for EJB ?
> Server A has all modules, while Server B is just a client to it.
> I want to use Server B as servlet client to connect to Server A.
>
> Is it possible and efficient to set up a distributed system
> like this using
> orion servers ?
>
> How should i go about doing all this ?
>
> Could anyone show me the steps ?
>
> Thanks a lot.
>
> -alex
>
>
> ps: just don't understand why orion team has such bad documentation.
> it's very frustrating to use their product. i am very
> sure it's wasting
> a tremendous amount of time for a lot of people to
> figure things out.
>
