Here are some suggested solutions for our problem of how best to update
beans in a production region. The solutions offered depend on whether your
EJB server consists of a single listener/AOR or of multiple listeners and
AORs.
As a general rule, upgrade solutions will be easier to implement if you:
- Divide your enterprise beans between CorbaServers based not only on the
beans' functions but also on their maintenance and availability requirements.
That is, sets of beans that have distinct maintenance and availability requirements
should be installed in distinct CorbaServers.
- Allocate CICS® transaction
IDs to enterprise bean methods based not only on the beans' functions but
also on their maintenance and availability requirements. That is, for ease
of maintenance sets of beans that have distinct maintenance and availability
requirements should run under distinct CICS transaction IDs.
Important: - In a multi-region EJB server, if your AORs contain multiple CorbaServers
you are strongly advised to assign different sets of transaction IDs to the
objects supported by each CorbaServer. That is, each CorbaServer in an AOR
should support a different set of transaction IDs.
- This makes it easier for the distributed routing program to route around
a disabled CorbaServer, while keeping available any other, enabled, CorbaServers
in the region. For further information about how to code a distributed routing
program to deal with a disabled CorbaServer, see the CICS Customization Guide.
Note: The CICS transaction under which a bean method runs is
specified on the REQUESTMODEL definition that matches the method. You can
use the CREA CICS-supplied transaction to:
- Display the transaction IDs associated with particular beans and bean
methods
- Change the transaction IDs, apply the changes, and save the changes to
new REQUESTMODEL definitions