IBM WebSphere Multichannel Bank Transformation Toolkit, Version 7.1

Memory shared CHA

Memory shared means Remote CHA with only EJB support.

The memory shared CHA is a sub-set of the whole CHA architecture. In the memory shared CHA, CHAInstance CMP bean and the database are excluded from the CHA architecture. The context persistence feature is not used.

To the local contexts, there is no difference between memory shared CHA and persistence shared CHA. But for remote contexts, there are differences: remote contexts under the memory shared CHA always stay in the singleton memory cache during their lifecycles, and they will never be stored into the database.

Access to the database is very time-consuming and always impacts the performance of BTT application. Therefore, to remove the database dependency and to keep all the runtime data in memory can guarantee good performance of the BTT applications, especially CHA performance.

Memory shared CHA has one limitation: it does not support fail-over because session and root level data cannot be persisted into database under the cluster environment. However, there are several ways for the BTT application to bypass this limitation:
To leverage the memory shared CHA, you need to identify only one item: to fill "startMode" with "MemoryShared". There is no need to create JDBC provider and data source in WebSphere® Application Server for CHA:
<kColl id="cha-server">
    ...
    <field id="startMode" value="MemoryShared"/>
    ...
</kColl>

Furthermore, the function of "cleanupCHAServer" is disabled under memory shared CHA.



Feedback