IBM WebSphere Multichannel Bank Transformation Toolkit, Version 7.1
Fetching data and destroying context
About this task
The following scenarios focus on Data Fetching and Context destroying.
These scenarios happen when user logs off, which is the last step of the transaction.
Procedure
Scenario X (for Persistence Shared CHA or Memory Shared CHA):
Use the API getContextbyInstanceID() to get the Context A with the given
Instance ID
Get the value of the Context A using the APIs like getValueAt(), getKeyedCollection()
Unchain the Context A from the parent Context
Prune the Context A;
Scenario XI (for Persistence Shared CHA or Memory Shared CHA):
Use the API getContextbyInstanceID() to get the Context A with the given
Instance ID
Get Context B, one of the Children of the Context A
Get the value of the Context B using the APIs like getValueAt(), getKeyedCollection()
Unchain the Context B from the parent Context
Prune the Context B
Scenario XII (for Local CHA):
Use the API getContextbyInstanceID() to get the Context A with the given
Instance ID
Get the value of the Context A using the APIs like getValueAt(), getKeyedCollection()
Unchain the Context A from the parent Context
Scenario XIII (for Local CHA):
Use the API getContextbyInstanceID() to get the Context A with the given
Instance ID
Get Context B, one of the Children of the Context A
Get the value of the Context B using the APIs like getValueAt(), getKeyedCollection()