FTM DB and Datasharing recommendation
Business continuity, High Availability, Scalability, and Performance lead the decision to go with a multi-instance topology, running more than one Financial Transaction Manager instance two or more logical partitions, sharing the same FTM Database.
This support is requested for:
1. to have recommendation, best practices, dependencies documented on KC or at least in white paper, redbook in order to avoid deadlock in FTM Tables sharing the same FTM DataBase.
2. to have recommendation, best practices, dependencies documented on KC or at least in white paper, redbook in order to avoid additional costs due to sysplex implementing such a kind of configuration without loosing the ability to process the payment by one FTM instance and to merge the ack to another FTM instance (sysplex exploitation).
Standards (Protocols, Rule Books, Specifications, etc.)
Medium - Important