Along with the client mode of the Context class, a remote mode is also required at the server end of the subsystem. The remote mode performs the actual data artifact collection and management in the service side rather than in the client side. In fact, this main difference between this mode of operation and previous versions of the toolkit is the primary value of CHA.
The remote mode Context is created as a result of creating a CHA Instance Session Bean and Entity Bean. For detailed information, see Using CHA.
Remote CHA is the key value of UDTT and CHA. It's advantages are:
▪ Data in remote server can be shared within the Context hierarchy and another container so that data stored in CHA server can be re-used and accessed cross multi-JVMs.
▪ Remote Contexts may be persisted in database that is controlled by CHA server itself. With this persistence capability, the data can be restored by another CHA server instance. Fail-over support is provided and managed by CHA component.
▪ Remote Context is constructed from definitions in the centralized context xml definition files.
