Routing in WCF - Action Filters

In my previous article, we discussed about the basic concept of routing in WCF service. We learned about how we can configure the router service and add filters to it. Now let's try to apply this in a practical example.

So we will start by creating an empty solution and add following projects in it:

Two wcf services, Service_1 and Service_2. These two services will have simple methods GetData1 and GetData2 respectively which will simply return the string with data entered by the user.
Another wcf service which will act as the routing service.
A windows application which will call the router service, which will further forward the call to either Service_1 or Service_2.

So our complete solution will look like the following:

So we will start by adding the GetData methods in our services Service_1 and Service_2. So these will look like the following:

public class Service1 : IService1
{
public string GetData(int value)
{
return string.Format("Data retuned from Service 1: {0}", value);
}
}
public class Service2 : IService2
{
public String GetData(Int32 value)
{
return string.Format("Data retuned from Service 2: {0}", value);
}
}

Next, we will configure our router service with the settings as per our previous discussion here. So, we will start by creating the basic configuration for the service, like defining the endpoint address, contract and service behavior of our routing service. So it would look like the following:

<services>
<service name="System.ServiceModel.Routing.RoutingService"
behaviorConfiguration="RoutingSvcBehavior">
<endpoint
address=""
binding="wsHttpBinding"
contract="System.ServiceModel.Routing.IRequestReplyRouter"/>
</service>
</services>
<behaviors>
<serviceBehaviors>
<behavior name="RoutingSvcBehavior">
<serviceMetadata httpGetEnabled="true" httpsGetEnabled="true"/>
<serviceDebug includeExceptionDetailInFaults="true"/>
<routing filterTableName="ServiceRouterTable"/>
</behavior>
</serviceBehaviors>
</behaviors>

Next we define the possible endpoints, where the request can get routed to. So this section will look like the following:

<client>
<endpoint
name="Service_1" binding="wsHttpBinding"
address="http://localhost:65145/Service1.svc"
contract="*">
</endpoint>
<endpoint
name="Service_2" binding="wsHttpBinding"
address="http://localhost:65253/Service2.svc"
contract="*">
</endpoint>
</client>

Moving on, we will define our filters which will use the filterType as Action. Based on the action request, it will route to either Service_1 or Service_2.

So our filter section will look like the following:

<routing>
<filters>
<filter name="MyFilter" filterType="Action" filterData="http://tempuri.org/IService1/GetData"/>
<filter name="MyFilter2" filterType="Action" filterData="http://tempuri.org/IService2/GetData"/>
</filters>
<filterTables>
<filterTable name="ServiceRouterTable">
<add filterName="MyFilter" endpointName="Service_1"/>
<add filterName="MyFilter2" endpointName="Service_2"/>
</filterTable>
</filterTables>
</routing>

Next, we will configure the Program.cs of our router service to host the application. So the Main function will look like the following:

class Program
{
static void Main(string[] args)
{
ServiceHost Host = new ServiceHost(typeof(RoutingService));
try
{
Host.Open();
Console.WriteLine("Routing Service is Started...............");
Console.ReadLine();
Host.Close();
}
catch (Exception ex)
{
Console.WriteLine(ex.Message);
}
Console.ReadLine();
}
}

Now, is the time to call the router service from our windows application. To start with, we will add a textbox and two buttons which will call the router service. So our form will look like the following:

Next, we will add service references to the Service_1 and Service_2, to this project in order to call these services. Once we add these references, the system will generate its configuration code in the App.config. We will remove all the generated configuration and add the following client end points. These will simply redirect the user to the router service, instead of directly routing them to Service_1 or Service_2.

<system.serviceModel>
<bindings>
<wsHttpBinding>
<binding name="WSHttpBinding_IService2" />
</wsHttpBinding>
</bindings>
<client>
<endpoint address="http://localhost:5643/MyServ" binding="wsHttpBinding"
contract="ServiceReference1.IService1" name="routingSvcEndPoint_Svc1" />
<endpoint address="http://localhost:5643/MyServ" binding="wsHttpBinding"
contract="ServiceReference2.IService2" name="routingSvcEndPoint_Svc2" />
</client>
</system.serviceModel>

On click of these buttons, we will add the following code, which will call the Service_1 or Service_2. Note that we could have also used the ChannelProxy to call the services. But in that case, it would have required us to use common Interface contract among the services and the client applications. So our code will look like the following:

private void button1_Click(object sender, EventArgs e)
{
ServiceReference1.Service1Client _client = new ServiceReference1.Service1Client("routingSvcEndPoint_Svc1");
label2.Text = "Response from Service 1: " + _client.GetData(Convert.ToInt32(textBox1.Text));
}
private void button2_Click(object sender, EventArgs e)
{
ServiceReference2.Service2Client _client2 = new ServiceReference2.Service2Client("routingSvcEndPoint_Svc2");
label2.Text = "Response from Service 2: " + _client2.GetData(Convert.ToInt32(textBox1.Text));
}

Finally we will set multiple projects as start-up projects.

Run the application, enter the values and see the results.

How it works ?

When we call the service1 or service2, using client proxies, we get the endpoint routingSvcEndPoint_Svc1 or routingSvcEndPoint_Svc2. These will route the requests to the router service. Router service will check its filter configuration and based on the action defined in filterData, it will select either MyFilter or MyFilter2. It will pick the corresponding endpoint from filterTable and route the request to its service.

Hope you enjoyed reading it. Complete source code is also attached here. Happy coding...!!!