<div>
Hi,<br />
<br />
You could look at Routing. <a href="http://msdn.microsoft.com/en-us/library/ee517422.aspx" rel="ugc nofollow">http://msdn.microsoft.com/en-us/library/ee517422.aspx</a><br />
<br />
Might be handy instead of pinging servers. See the Error Handling section.<br />
<br />
Cheers,<br />
<br />
Darren
</div>


Hi,

You could look at Routing. http://msdn.microsoft.com/en-us/library/ee517422.aspx [http://msdn.microsoft.com/en-us/library/ee517422.aspx]

Might be handy instead of pinging servers. See the Error Handling section.

Cheers,

Darren

<div>
Hi Darren,<br />
<br />
Thanks for the reply, but I've to use the application way of checking if the primary service IsAlive or not. Any ideas on this approach?
</div>


Hi Darren,

Thanks for the reply, but I've to use the application way of checking if the primary service IsAlive or not. Any ideas on this approach?

<div>
<div class="content wysiwyg-content">
I need to device a Failover mechanism for the following scenario.<br />
<br />
&nbsp;I have a WCF windows service (An auto-start producer service whose method returns values every 15 seconds) which would be having 4 instances (Geo Location &quot;A&quot; would have a Primary (PA) and Secondary (SA) and Geo Location &quot;B&quot; would have two instances Primary (PB) and Secondary (SB) ). At any given time, one instance in each location should be up and running( i.e. Active) and the other is Inactive. <br />
<br />
Considering one location at a time, Secondary(Inactive) should be able to PING the Primary (Active) for health info. and if its not found to be &quot;healthy&quot;, then the Secondary(Inactive) should activate itself and start producing the values periodically.<br />
<br />
I would appreciate your expert opinions on how to achieve the same. What is the best way to communicate between the two WCF Windows Services?<br />
<br />
Regards!
</div>
</div>


I need to device a Failover mechanism for the following scenario.

 I have a WCF windows service (An auto-start producer service whose method returns values every 15 seconds) which would be having 4 instances (Geo Location "A" would have a Primary (PA) and Secondary (SA) and Geo Location "B" would have two instances Primary (PB) and Secondary (SB) ). At any given time, one instance in each location should be up and running( i.e. Active) and the other is Inactive. 

Considering one location at a time, Secondary(Inactive) should be able to PING the Primary (Active) for health info. and if its not found to be "healthy", then the Secondary(Inactive) should activate itself and start producing the values periodically.

I would appreciate your expert opinions on how to achieve the same. What is the best way to communicate between the two WCF Windows Services?

Regards!

WCF Windows Services Failover Strategy

Windows Communication Foundation (WCF) is a tool used to implement and deploy a service-oriented architecture (SOA) to support distributed computing where services have remote consumers. It features a runtime and a set of APIs in the .NET Framework for building connected, service-oriented applications. Services typically have a WSDL interface (Web Services Description Language) that any WCF client can use to consume the service, regardless of which platform the service is hosted on. WCF implements many advanced Web services (WS) standards such as WS-Addressing, WS-ReliableMessaging, WS-Security, RSS Syndication Services, WS-Discovery, routing and better support for REST services.

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Most development for the Microsoft platform is done utilizing the technologies supported by the.NET framework. Other development is done using Visual Basic for Applications (VBA) for programs like Access, Excel, Word and Outlook, with PowerShell for scripting, or with SQL for large databases.