Do Ejbs Have To Be Homogeneously Deployed Across A Cluster? Why?

1.	Do Ejbs Have To Be Homogeneously Deployed Across A Cluster? Why?
Answer» Yes. BEGINNING with WebLogic Server version 6.0, EJBS must be homogeneously deployed across a cluster for the FOLLOWING reasons: To keep clustering EJBs simple. To avoid cross server calls which results in more EFFICIENCY. If EJBs are not deployed on all servers, cross server calls are much more likely. To ensure that every EJB is available locally. To ensure that all classes are loaded in an undeployable way. Every server must have access to each EJB’s classes so that it can be bound into the local JNDI tree. If only a subset of the servers deploys the bean, the other servers will have to load the bean’s classes in their respective system classpaths which MAKES it impossible to undeploy the beans. Yes. Beginning with WebLogic Server version 6.0, EJBs must be homogeneously deployed across a cluster for the following reasons:

Answer»

Yes. BEGINNING with WebLogic Server version 6.0, EJBS must be homogeneously deployed across a cluster for the FOLLOWING reasons:

To keep clustering EJBs simple.
To avoid cross server calls which results in more EFFICIENCY. If EJBs are not deployed on all servers, cross server calls are much more likely.
To ensure that every EJB is available locally.
To ensure that all classes are loaded in an undeployable way.
Every server must have access to each EJB’s classes so that it can be bound into the local JNDI tree. If only a subset of the servers deploys the bean, the other servers will have to load the bean’s classes in their respective system classpaths which MAKES it impossible to undeploy the beans.

Yes. Beginning with WebLogic Server version 6.0, EJBs must be homogeneously deployed across a cluster for the following reasons:

Discussion