Fast Connection Failover differs from TAF in the following ways:
Application-Level Connection Retries. Fast Connection Failover supports application-level connection retries. This gives the application control of responding to connection failovers: the application can choose whether to retry the connection or to rethrow the exception. TAF supports connection retries only at the OCI/Net layer.
Integration with the Connection Cache. Fast Connection Failover is well-integrated with the Implicit Connection Cache, which allows the connection cache manager to manage the cache for high availability. For example, failed connections are automatically invalidated in the cache. TAF works at the network level on a per-connection basis, which means that the connection cache cannot be notified of failures.
Event-Based. Fast Connection Failover is based on the RAC event mechanism. This means that Fast Connection Failover is efficient and detects failures quickly for both active and inactive connections. TAF is based on the network call mechanism.
Load-Balancing Support. Fast Connection Failover supports UP event load balancing of connections and runtime work request distribution across active RAC instances.
Perform the following in your Java code:
Get an instance of the FanManager class by using the getInstance method.
Configure the event daemon using the configure method of the FanManager class. The configure method sets the following properties:
onsNodes: A comma separated list of host:port pairs of ONS daemons that the ONS runtime in this Java VM should communicate with. The host in a host:port pair is the host name of a system running the ONS daemon. The port is the local port configuration parameter for that daemon.
onsWalletFile: The path name of the ONS wallet file. The wallet file is the path to a local wallet file used by SSL to store SSL certificates. Same as wallet file configuration parameter to ONS daemon.
onsWalletPassword: The password for accessing the ONS wallet file.