This example describes how to use the end user interface (EUI)
to balance an enterprise bean workload.
In an enterprise bean environment, the TOR CICSPT01 is the listener, and the enterprise bean may run in any of the AORs, CICSPA01, CICSPA02, and CICSPA03 in response to a client request. There are MRO links between the regions.
If you are using BAS you should include the statement:
MASPLTWAIT(YES)
in the EYUPARM file for all listener regions, to ensure that the local CICSPlex SM environment is properly established at MAS initialization time. If you do not, and there are enterprise beans queued for execution when the MAS initializes, it is possible that the routing requests for the first few enterprise beans will be rejected. By including this EYUPARM statement, the CICS PLTPI processing will suspend until the critical components of the local CICSPlex SM environment complete their initialization.
Use CEDA or BAS to define and install the following:
If all enterprise beans are to be balanced across all available AORs, the only definition you need is a workload specification (WLMSPEC):
------------------- Create WLM Specification for EYUPLX01 --------------------- COMMAND ===> WLM Spec Name EJBSPEC1 Description ===> Balanced EJB Workload Affinity Relation ===> Default Affinity Relation (USERID, LUNAME, GLOBAL, BAPPL) Affinity Lifetime ===> Default Affinity Lifetime (SIGNON, LOGON, SYSTEM, PERMANENT, PCONV, DELIMIT, ACTIVITY, PROCESS) Match Key ===> USERID Default Primary search criteria (USERID, LUNAME) Create Affinity ===> N/A Create auto affinity (YES, NO, N/A) Target Scope ===> EJBCSG02 Default CICS System, Group or Generic Event Name ===> RTADEF, STATDEF or Generic Abend Health ===> 0 Target ABEND Health Factor (0 - 99) Abend Load ===> 0 Target ABEND Load Factor (0 - 99) Algorithm Type ===> QUEUE Algorithm Type (GOAL, QUEUE) Press ENTER to create the WLM Specification. Type END or CANCEL to cancel without creating.
In this definition theTarget Scope is the group which contains AORs only (EJBCSG02). This is because all dynamic transactions are to be routed to the AORs through this WLMSPEC.
This is because the scope of the WLM balancing processing must cover all of the regions, the listener region for routing decisions and the AORs so that their workloads are made visible to CICSPlex SM. On the other hand, the target scope of the transactions directed by the WLMSPEC covers just the regions that the routed transactions may be executed in. In other words, all regions must be aware of this WLMSPEC, but only the group of AORs may execute the dynamic transactions routed through it.
W1 =WLMSCOPE=========EYUPLX01=ALLMAS===02/02/2001=11:06:24====CPSM====5== CMD WLM Scope Scope Scope Scope Update --- Spec---- Name---- Type---- Mode---- Link---- Option-- EJBSPEC1 EJBCSG01 SYSGROUP EJBSPEC1 CICSPA01 CICSSYS INHERIT EJBCSG01 EJBSPEC1 CICSPA02 CICSSYS INHERIT EJBCSG01 EJBSPEC1 CICSPA03 CICSSYS INHERIT EJBCSG01 EJBSPEC1 CICSPT01 CICSSYS INHERIT EJBCSG01
When all of the MASs are started, ensure that each MAS confirms
EYUNL0160I xxxxxxxx Workload registration complete
where xxxxxxxx is the corresponding MAS name. At that point, the workload management environment should be ready to balance the execution of enterprise beans.
Restart the MASs and ensure that all the resources needed by each region are installed. You can use the EJCOSE view to monitor the CorbaServer status and the EJDJAR view to monitor DJAR status.
When all the CorbaServers and their assiciated DJARs are INSERVICE, issue the PUBLISH command against each CorbaServer in one of the AORs. This command causes the attributes of the CorbaServer, its associated DJARs and the beans contained in them to be identified to the Java Naming and Directory Interface (JNDI). When the command completes, the CICS routing and execution environment should be ready to run the enterprise beans.
When the initial process is run on the client, it uses the services of JNDI to identify a TCP/IP port. This port is used to pass a bean execution request to the configured listener region. The request receiver transaction CIRR is invoked within that region and issues a START request to the request processor transaction CIRP. This transaction has been redefined as dynamic and so the listener calls the DSRTPGM routing exit program to select a target region. In this case that program is EYU9XLOP, which will drive the workload balancing services of CICSPlex SM to select a suitable AOR. This AOR name is returned to the routing exit in the listener, which will route the execution of CIRP to the selected AOR. Finally the CorbaServer in the target AOR receives the request and executes the enterprise bean on behalf of the original client. The usage count value of the CIRP transaction across each of the AORs should increase with each execution of the client program. This can be verified using the CICSPlex SM command LOCTRAN CIRP.
[[ Contents Previous Page | Next Page Index ]]