Coherence Clustered Client Server Configuration

Question

Hi,
I am trying to create a client-server setup in coherence and I have been able to do that successfully using Coherence Extend in a single client - single server environment. However, what I need to do is that, I need to create a cluster of servers and my client should be able to pick the data from any of the clustered servers. Can someone tell me how to configure that.
Right now my server-config xml looks like : -
<cache-config>
     <caching-scheme-mapping>
          <cache-mapping>
               <cache-name>dist-MYCache</cache-name>
               <scheme-name>MY-distributed-cache-scheme</scheme-name>
          </cache-mapping>
     </caching-scheme-mapping>
     <caching-schemes>
          <!--
Distributed caching scheme.
-->
          <distributed-scheme>
               <scheme-name>MY-distributed-cache-scheme</scheme-name>
               <lease-granularity>member</lease-granularity>
               <backing-map-scheme>
                    <local-scheme/>
               </backing-map-scheme>
               <autostart>true</autostart>
          </distributed-scheme>
          <proxy-scheme>
               <service-name>ExtendTcpProxyService</service-name>
               <thread-count>5</thread-count>
               <acceptor-config>
                    <tcp-acceptor>
                         <local-address>
                              <address>server1.domain.com</address>
                              <port>8081</port>
                         </local-address>
                    </tcp-acceptor>
               </acceptor-config>
               <autostart>true</autostart>
          </proxy-scheme>
     </caching-schemes>
</cache-config>
My Client-config xml looks like :-
<cache-config>
     <caching-scheme-mapping>
          <cache-mapping>
               <cache-name>dist-MYCache</cache-name>
               <scheme-name>extend-MYCache</scheme-name>
          </cache-mapping>
          <cache-mapping>
               <cache-name>dist-extend-MYdist</cache-name>
               <scheme-name>extend-MYdist</scheme-name>
          </cache-mapping>
     </caching-scheme-mapping>
     <caching-schemes>
          <!--
Distributed caching scheme.
-->
          <distributed-scheme>
               <scheme-name>extend-MYdist</scheme-name>
               <service-name>MYDistributedCache</service-name>
               <local-storage>false</local-storage>
               <local-scheme></local-scheme>
               <back-scheme>
                    <remote-cache-scheme>
                         <scheme-ref>extend-MYCache</scheme-ref>
                    </remote-cache-scheme>
               </back-scheme>
          </distributed-scheme>
          <remote-cache-scheme>
               <scheme-name>extend-MYCache</scheme-name>
               <service-name>ExtendTcpCacheService</service-name>
               <initiator-config>
                    <tcp-initiator>
                         <remote-addresses>
                              <socket-address>
                                   <address>client.domain.com</address>
                                   <port>8081</port>
                              </socket-address>
                         </remote-addresses>
                         <connect-timeout>5s</connect-timeout>
                    </tcp-initiator>
                    <outgoing-message-handler>
                         <request-timeout>2s</request-timeout>
                    </outgoing-message-handler>
               </initiator-config>
          </remote-cache-scheme>
     </caching-schemes>
</cache-config>
And my tangosol-override xml (SAME FOR CLIENT AND SERVER) looks like :-
<coherence>
     <cluster-config>
          <member-identity>
               <cluster-name>MYUATCluster</cluster-name>
          </member-identity>
          <unicast-listener>
               <well-known-addresses>
                    <socket-address id="1">
                         <address>server1.domain.com</address>
                         <port>8088</port>
                         <port-auto-adjust>true</port-auto-adjust>
                    </socket-address>
                    <socket-address id="2">
                         <address>server2.domain.com</address>
                         <port>8088</port>
                         <port-auto-adjust>true</port-auto-adjust>
                    </socket-address>          
               </well-known-addresses>
          </unicast-listener>
          <multicast-listener>
               <time-to-live system-property="tangosol.coherence.ttl">4</time-to-live>
               <join-timeout-milliseconds>3000</join-timeout-milliseconds>
          </multicast-listener>
          <packet-publisher>
               <packet-delivery>
                    <timeout-milliseconds>30000</timeout-milliseconds>
               </packet-delivery>
          </packet-publisher>
          <service-guardian>
               <timeout-milliseconds system-property="tangosol.coherence.guard.timeout">35000
               </timeout-milliseconds>
          </service-guardian>
     </cluster-config>
     <logging-config>
          <severity-level system-property="tangosol.coherence.log.level">5</severity-level>
          <character-limit system-property="tangosol.coherence.log.limit">0</character-limit>
     </logging-config>
</coherence>

Answer 1

I am not sure I understand you correctly, so let me re-phrase my question :
Right now my client-config.xml has :
<remote-cache-scheme>
<scheme-name>extend-MYCache</scheme-name>
<service-name>ExtendTcpCacheService</service-name>
<initiator-config>
<tcp-initiator>
<remote-addresses>
<socket-address>
*<address>server.domain.com</address>*
<port>8081</port>
</socket-address>
</remote-addresses>
<connect-timeout>5s</connect-timeout>
</tcp-initiator>
<outgoing-message-handler>
<request-timeout>2s</request-timeout>
</outgoing-message-handler>
</initiator-config>
</remote-cache-scheme>
where server.domain.com is one of the servers of the cluster, so I will face a problem when this server goes down but the cluster is still up and running. Because this client can only contact server.domain.com. What do I need to change so that every time it looks for the cluster and not a specific server.
Edited by: user1945969 on Sep 10, 2009 10:05 AM