Workload separation is the WLM function that causes transactions which
meet predesignated selection criteria to be routed to specific target scopes.
The target scope for a separated workload item may vary from a single AOR
to a large AOR group comprising many CICS regions. If an AOR group is the
target, the balancing algorithm will be applied to select the most suitable
region from those defined to it. To implement a workload that includes separated
enterprise beans, you must first establish the prerequisite workload balancing
described in
Workload balancing. That configuration needs to be augmented
with the following additional components:
- A cloned CIRP transaction for each enterprise bean that needs to be separated
(a simple copy of the existing definition to a new name)
- A request model for each enterprise bean to be separated, to associate
it with one of the cloned CIRP transactions
This will allow the CICS and EJB environments to be established
enabling enterprise bean separation. The WLM definitions will then need to
be created to implement it. This entails identifying the cloned CIRP transactions
as being objects of interest, and associating them with the required target
scopes through a series WLM definitions. These WLM definitions must be associated
to an overall WLM specification, via an intermediate WLM group, and then the
specification must be added to the CICS group that includes all listeners
and AORs that are to participate in the workload. A detailed example of enterprise
bean workload separation is given in the CICSPlex® System Manager Managing Workloads.