Resolution:
Here is the Remote Client connect setup with Leech proxy: (-autojoin.role "leech").


------------------Host-01-------------------

as-agent (Seeder)
java -jar as-agent.jar -metaspace "metaspace_name" -discovery "tcp://HOST-01:Port-01;HOST-02:Port-01" -listen "tcp://HOST-01:Port-01"

as-agent (Leech-Proxy)

java -jar as-agent.jar -metaspace "metaspace_name" -discovery "tcp://HOST-01:Port-01;HOST-02:Port-01" -listen "tcp://HOST-01:Port-02" -autojoin.role "leech" -remote_listen "tcp://HOST-01:Port-03"

------------Host02----------------------

as-agent (Seeder) 

java -jar as-agent.jar -metaspace "metaspace_name" -discovery "tcp://HOST-01:Port-01;HOST-02:Port-01" -listen "tcp://HOST-02:Port-01"

as-agent (Leech-Proxy)

java -jar as-agent.jar -metaspace "metaspace_name" -discovery "tcp://HOST-01:Port-01;HOST-02:Port-01" -listen "tcp://HOST-02:Port-02" -autojoin.role "leech" -remote_listen "tcp://HOST-02:Port-03"



BW applications and Java client :


connecting to both the as-agent (Leech Proxy) in fault tolerance mode  (This feature available from AS 2.1.5 onward )


-metaspace "metaspace_name" -discovery "tcp://HOST-01:Port-03:HOST-01:Port-03?remote=true"

Sample deployment mode: (Refer to the attachment, Filename Sample Deployment.png)

Remote Client deployment as-agent as Leech proxy (-autojoin.role "leech").

as-admin, -autojoin.role "leech"