Program guide > (deprecated) Partitioning facility > The partitioning facility > J2EE partitioning capabilities > EJB workload partitioning
Deprecated feature: The partitioning facility (WPF) feature is deprecated. You can configure partitioning with WebSphere eXtreme Scale.
Typical J2EE enterprise bean clustered workload processing
The following diagram illustrates a simple scenario with two nodes and a one application server per node cluster configuration. The diagram depicts an enterprise bean workload management example that includes a Java™ 2 Platform Enterprise Edition (J2EE) application with two enterprise beans:
In this case, each client request is routed from the enterprise bean client through the ORB and WLM plug-in to EJB1 in an alternating fashion between enterprise bean instances. Both EJB1 instances are active in the cluster, but they are not unique; work is routed between them without client intervention. While the ability to share the requests helps scalability, implicit limits and constraints exist to ensure the same data that is loaded in each entity during normal transactions is safely managed and replicated back to the database. The invisible functionalities provided in the enterprise bean container, relational resource adapter, and other WebSphere components ensure that data corruption is not possible, but these functionalities can detract from the performance capabilities of the system. For some workloads, performance costs are relatively expensive and several application styles exist where this can be avoided.
The ability for two or more entity bean instances to share the same data is enforced by Extended Deployment server and the database server. One of the partitioning facility's (WPF) goals is to allow a single endpoint in the cluster to handle all data for a specific instance and reduce the burden of the WebSphere and database server to enforce these semantics, dramatically improving overall system scalability and throughput. Currently, WAS and Extended Deployment entity bean developers can use only options B and C, because in option A exclusive access is not permitted.
Parent topic:EJB workload partitioning
EJB workload partitioning