Within the ETA C++ documentation:
Section 2.4 Functionality within the API Concepts guide contains a table of features, capabilities, APIs etc. Specifically, there is a capability called Warm Standby: API-based, which indicates the capability is only available within RFA. However, in section 2.4.2 Layer-Specific Capability Comparison within the Developer Guide, also contains a capability chart and lists Warm Standby: API-based. However, the availability of this contradicts the previous chart. That is, it is planned in the future for EMA and apparently the capability is possible with ETA. However, it is unclear whether this is implying if the developer has to perform this capability themselves or whether the ValueAdd reactor supports it. Can anyone clear up the confusion?
With regards to the Load Balancing feature, apparently it is available within the Reactor as mentioned within section 2.4 Functionality within the API Concepts guide.. Can someone point within the documentation any explanation of how this works?
Warm Standby falls under the 'implement yourself' category. I have mentioned the confusion caused and hopefully this will be clarified in a future version of the document.
With regards Load Balancing, that appears to be a typo as I have been advised we do not currently support API Load Balancing in ETA or EMA.