IBM WebSphere Multichannel Bank Transformation Toolkit, Version 7.1

Persistence shared CHA architecture

The following diagram shows a high level view of the Persistence shared CHA architecture.

A high level view of the Persistence shared CHA architecture

A service or business process instantiates a local or remote CHA context using the API of the Context class. Note that the service or business process can use a provided name or a generated one. The service or business process interacts with local and remote contexts using the same API.

The client side of a remote context is little more than a mechanism for passing requests on to the server side. It delegates business functions to the server side.

In the CHA server, EJB instances create and maintain the server side of remote contexts. A session bean (CHASession) handles static method calls while an entity bean (CHAInstance) handles instance method calls. Note that the Context class does not require access to the CHAInstance home interface to retrieve a remote interface. The CHASession EJB can perform all instance queries using local EJB interfaces to create or find CHAInstance objects.

The client side of the context or a non-toolkit J2EE client drives the creation of the EJBs. Toolkit applications cannot directly create the EJBs. Each context has an instance ID, which is unique in the global system. Note that the server side of a remote context identifies whether the context is static or dynamic depending on whether the definition files contain a definition for the context. See Context type for more information.

The remote CHA context is stored as a cache in memory, which greatly improves the performance of CHA remote context. A singleton is used to access hashMap which contains the whole remote context tree.

You can use one hashMap to store the information related to the context.

The key of the hashMap is an instance ID and the value is context object. CHA will manipulate this hashtable using instance ID as the key. For example, you can insert, delete or update the context according to the instance ID.

The children-parent relationship is stored in each context instance. Variables in the context for this purpose are as follows:

The following is the possible deployment picture in a production environment for BTT CHA. In the deployment, CHA must be packaged together with other components such as struts, Single Action EJB,etc.

WebSphere Clustering

The execution sequence described below can help you understand the architecture.



Feedback