How does global cache help resolve message affinity issues with request/reply scenario when scaling IBM Integration Bus nodes?
The requests and replies may be collected in the global cache for audit.
The global cache improves the performance of the request/reply message communication.
Request messages are sent to the back end and synchronized through the global cache lock.
The incoming information may be saved in the global cache with the message id as the key and correlated on any server from the correlation id.
What can the DatabaseInput node be configured to do?
Insert data in a database.
Update data in a database.
Update the local environment tree.
Retrieve data from a database.
Use the DatabaseInput node to detect events recorded in a database, and to retrieve the data affected by those events.
References: https://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bc34041_.htm