High Availability with File/FTP adapter

High availability in B2B is typically achieved by running muliple instance of B2B pointing to the same metadata repository, front ended by a load balancer such as web cache or any hardware load balancer. Always HA using File/FTP transport is very challenging due to the non transactional nature of the transport. We have come up with two properties to handle the same.

1. oracle.tip.adapter.b2b.inHAMode= true
2. oracle.tip.adapter.b2b.HAInstanceName=MyHost

Note that the setting for oracle.tip.adapter.b2b.HAInstanceName must be unique among the B2B instances using the same B2B repository.This is followed by running the script against b2b schema.

This feature allows the File/FTP to automatically detect which instance should poll and when the first instance stop polling (due to outages), the second instance will start polling by registering itself in the B2B_HA_REGISTRY after detecting the first instance is down. Even if there is a restart of the first instance it will not poll as the second instance is registered and active and acts as a Fail over instance, ready to take over in case of issue with second instance.
P.S

1. Please ensure to be on 10.1.2.3 patch.
2. Do not create the table manually and insert the instance related information, it should happen on its own if the patch is functional.
3. Need B2B restart after adding the above properties to tip.properties.