Right-click on the TradeRecordingServiceHost project of the trading service solution in Visual Studio 2005, and choose Debug, Start New Instance from the context menu. An exception should be thrown with this error message:

Service 'Fabrikam.TradeRecorder' has zero application (non-infrastruc-
ture) endpoints. This might be because no configuration file was found
for your application, or because no service element matching the service
name could be found in the configuration file, or because no endpoints
were defined in the service element.

The message is quite accurate: The service cannot start because no endpoints have been defined for it. There is indeed no configuration file with endpoint definitions.

Choose Debug, Stop debugging from the Visual Studio 2005 menus to terminate the application.

Right-click on the TradeRecordingServiceHost project and choose Add, New Item from the context menu, and proceed to add an application configuration file called App.config to the project.

Right-click on the new App.config file and choose Edit WCF Configuration from the context menu. The Service Configuration Editor will open, as shown in Figure 19.1.

Figure 19.1. The Service Configuration Editor.

Click on the Create a New Service link in the right pane to start the New Service Element Wizard.

The first step in the wizard is to identify the service type of the service. To do that for the trade-recording service, start by clicking on the Browse button to open the Type Browser dialog.

In the Type Browser dialog, locate the TradeRecordingService.dll assembly in the bindebug subdirectory of the TradeRecordingServiceHost project directory.

Double-click on that assembly to see a list of the service types defined in that assembly. Select the Fabrikam.TradeRecordingService type, and click Open. The Type Browser dialog will close and the New Service Element Wizard will be back in the foreground.

Click Next. A list of Windows Communication Foundation service contracts implemented by the Fabrikam.TradeRecordingService type is displayed.

There is only one such contract, so there is no need, in this case, to select one. Simply click Next.

The next dialog asks what mode of communication is to be used, as shown in Figure 19.2. The trade-recording service receives requests via a Microsoft Message Queue, so choose MSMQ from among the options displayed, and click Next.

Figure 19.2. The communication mode dialog of the New Service Element Wizard.

The next dialog is for the New Service Element Wizard to choose between the predefined bindings NetMsmqBinding and LegacyMsmqBinding. To do so, it asks the user whether Windows Communication Foundation clients for MSMQ clients will be connecting to the service. Select the former option, and click Next.

Now the address for the endpoint is to be entered. Enter net.msmq://localhost/private/TradeRecording as the address and click Next.

Click Finish on the final screen of the New Service Element Wizard.

The binding for the newly defined endpoint will need to be modified slightly to accommodate the possibility of the host system not being attached to a Windows domain. To initiate that modification, click on the link labeled Click to Create opposite the Binding Configuration label on the right pane of the Service Configuration Editor, shown in Figure 19.3. A panel for configuring the NetMsmqBinding opens in the right pane of the Editor, as shown in Figure 19.4.

Figure 19.3. Service endpoint configuration.

Figure 19.4. Binding Configuration panel.

Enter MyMSMQBindingConfiguration as the name of the binding configuration opposite the Name label in the right pane of the editor.

Click on the Security tab.

Select None as the mode from the list of security modes opposite the Mode label on the right pane of the editor.

Choose File, Save from the Service Configuration Editor menus.

Choose File, Exit to close the Service Configuration Editor.

Right-click on the TradeRecordingServiceHost project of the trading service solution in Visual Studio 2005, and choose Debug, Start New Instance from the context menu. A console window for the application should open, and after a few moments, a message should appear confirming that the trade-recording service is available.

Choose Debug, Stop Debugging from the Visual Studio 2005 menus to terminate the application.

Right-click on the Client project within the trading service solution, and choose Build from the context menu.

Right-click on the TradeRecordingServiceHost project and choose Add, New Item from the context menu, and proceed to add an application configuration file called App.config to the project.

Right-click on the new App.config file and choose Edit WCF Configuration from the context menu. The Service Configuration Editor will open as shown in Figure 19.1.

Click on the Create a New Client link on the Tasks panel on the bottom left of the Service Configuration Editor. The New Client Element Wizard opens.

On the first dialog, select the option to configure the client manually using the wizard, rather than have the wizard configure the client from the configuration file of the service.

The next dialog is for identifying the service contract. Click Browse to open the Type Browser dialog.

Use the dialog’s controls to locate the Client.exe assembly, which should be in the bindebug subdirectory of the Client project directory.

Double-click on that assembly to display a list of service contracts it defines.

Select the Client.ITradingService contract, and click Open, which should serve to close the Type Browser dialog, and bring the New Client Element Wizard back to the foreground.

Click Next to proceed to a selection of communication modes.

Select HTTP from the list, and click Next.

The next screen is for the wizard to choose between the predefined BasicHttpBinding and the predefined WSHttpBinding. It displays that choice to the user as a choice between Basic Web Services Interoperability and Advanced Web Services Interoperability. Opt for the latter, and click Next.

Enter http://localhost:8000/TradingService as the address on the subsequent dialog, and click Next.

Enter TradingServiceConfiguration as the name for the client endpoint configuration, and click Next.

Click Finish to complete the wizard’s steps.

The binding for the newly defined endpoint will need to be modified slightly to add the assurance of the messages being delivered exactly once and in order. To initiate that modification, click on the link labeled Click to Create opposite the Binding Configuration label on the right pane of the Service Configuration Editor. A panel for configuring the WSHttpBinding opens in the right pane of the Editor.

Enter MyReliableBindingConfiguration as the name of the binding configuration opposite the Name label in the right pane of the editor.

Scroll down to the ReliableSession properties section.

Select True as the value for the Enabled property in that section, as shown in Figure 19.5.

Figure 19.5. Enabling a Reliable Session.

Choose File, Save from the Service Configuration Editor menus.

Choose File, Exit to close the Service Configuration Editor.

Choose Debug, Start Debugging from the Visual Studio 2005 menus.

Choose Debug, Start Debugging from the menus.

When there is activity in the console application windows of the Trade Recording Service Host and the Trading Service Host applications confirming that the services they host are ready, enter a keystroke into the console application window of the client application.

After a few moments, activity should start to appear in the console application window of the trading service host, as the client risk management system begins pricing and purchasing a derivative. There might be a pause as the trading service loads the Microsoft Distributed Transactions Coordinator for the first time. Then the pricing and purchasing of primary and hedging derivatives purchases should proceed.

Choose Debug, Stop Debugging from the Visual Studio 2005 menus.

Right-click on the App.config file of the TradingServiceHost project and choose Edit WCF Configuration from the context menu. The Service Configuration Editor opens.

Click on the Diagnostics node in the tree in the left pane. The right pane should now show links for configuring message logging and other diagnostic facilities, as shown in Figure 19.11.

Figure 19.11. Diagnostics configuration.

Click on the Enable Message Logging link.

Click on the ServiceModelMessageLoggingListener link that will have appeared, to configure the trace listener to which logged messages will be directed.

In the Listener Settings window, observe that the trace listener will, by default, be writing the logged messages to a file called app_messages.svclog in the same folder as the Trading Service Host project.

Click OK to close the Listener Settings dialog and return to the Diagnostics Configuration pane.

Click the link labeled Malformed, Transport opposite the Log Level label. The Message Logging Settings dialog appears, which allows one to determine which messages will be captured.

Selecting Transport Messages on that dialog will mean that messages will be logged as they are sent or received, which would mean that if the messages being exchanged are encrypted, the logged messages will be encrypted. Selecting Service Messages will mean that messages are logged as they pass in or out of the Windows Communication Foundation Service model layer, at which point they would usually no longer be encrypted. Select all the options on the dialog and click OK.

Click on the Enable Log Auto Flush link which will ensure that any message log data cached by the trace listener will be flushed to the message log.

Choose File, Save from the Service Configuration Editor menus.

Choose File, Exit to close the Service Configuration Editor.

In Visual Studio 2005, in the trading service solution, choose Debug, Start Debugging from the menus.

When there is activity in the console application windows of the trade recording service host and the trading service host, confirming that the services they host are ready, enter a keystroke into the console application window of the client application.

Wait until the console application window of the client application confirms that it is done pricing and purchasing derivatives.

Choose Debug, Stop Debugging from the Visuals Studio 2005 menus.

Execute the Windows Communication Foundation’s Trace Viewer, which is SvcTraceViewer.exe. It should be found in the bin subdirectory of the installation of folder of the .NET Framework 3 SDK. The Trace Viewer is shown in Figure 19.12.

Figure 19.12. The Trace Viewer.

Choose File, Open from the menus, and open the file app_messages.svclog, which should be found in the same folder as the TradingServiceHost project file.

Select the first entry in the activity list on the left of the Trace Viewer.

Select the XML tab on the lower right, and scroll through the entry on that tab. It contains a record of a message, as shown in Figure 19.13.

Figure 19.13. A logged message.

Right-click on the App.config file of the TradingServiceHost project and choose Edit WCF Configuration from the context menu. The Service Configuration Editor opens.

Click on the Diagnostics node in the tree in the left pane. The right pane should now show links for configuring message logging and other diagnostic facilities, as shown in Figure 19.11.

Click on the Enable Tracing link.

Click on the ServiceModelTraceListener link that will have appeared to configure the trace listener to which activity traces will be directed.

In the Listener Settings window, observe that the trace listener will, by default, be writing the logged messages to a file called app_tracelog.svclog in the same folder as the Trading Service Host project.

Click OK to close the Listener Settings dialog and return to the Diagnostics Configuration pane.

Click the link labeled Warning, Activity Tracing, Propagate Activity opposite the Trace Level label. The Tracing Settings dialog appears, which allows one to set the trace level.

Choose Verbose from the list of options, and click OK.

Choose File, Save from the Service Configuration Editor menus.

Choose File, Exit to close the Service Configuration Editor.

Open the Service Trace Viewer, SvcTraceViewer.exe, in the bin subdirectory of the Windows SDK installation folder.

Choose File, Open from the menus.

In the File Open dialog, select all the trace files in the Logs subdirectory of the Management folder that contains the code associated with this chapter.

Click on the Open button.

If the Partial Loading Dialog appears, click OK to dismiss it.

A progress bar might appear at the bottom of the Service Trace Viewer. Wait until it disappears and the counts of traces and activities appear. These activities were recorded from all three components of the trading system that has been used as an example throughout this chapter: the client risk management system, the trading service, and the trade-recording service. The total number of traces recorded at the verbose trace level across all three applications over a period of less than two minutes was 72,980—a quite considerable quantity of diagnostic information.

Select any activity labeled Process Action in the list of activities in the left pane, such as the one shown highlighted in Figure 19.15.

Figure 19.15. Selecting an activity.

Select the Graph tab, shown in Figure 19.16. The Trace Viewer is able to show transfers of activity between the endpoints of a system! That feature allows one to follow an activity from a client to a service and back. For instance, one can select any step in the sequence depicted in the graphical view to see details of the traces emitted in that step in the panes on the right.

Figure 19.16. The Graph tab.

Open the Program.cs file of the Trading Service Host project, and modify the code therein as shown in Listing 19.2. The two additional lines serve to define a trace source with the arbitrary name, MyTraceSource, and to emit a trace from that source.

using System;
using System.Collections.Generic;
using System.ServiceModel;
using System.Text;

namespace Fabrikam
{
    public class Program
    {
        private static System.Diagnostics.TraceSource source =
            new System.Diagnostics.TraceSource("MyTraceSource");

        public static void Main(string[] args)
        {
            using (ServiceHost host = new ServiceHost(typeof(TradingSystem)))
            {
                 host.Open();

                 Console.WriteLine("The trading service is available.");

                 source.TraceEvent(
                     System.Diagnostics.TraceEventType.Verbose,
                     1,
                     "My trace message.");

                 Console.ReadKey(true);
            }
        }
    }
}

Right-click on the App.config file of the TradingServiceHost project and choose Edit WCF Configuration from the context menu. The Service Configuration Editor opens.

Proceed to identify the new trace source to the Windows Communication Foundation. Begin by expanding the Diagnostics node in the tree in the left pane.

Right-click on the Sources child node and choose New Source from the context menu.

Enter MyTraceSource as the name of the source—the name of the trace source to which the activity trace emitted by the code in Listing 19.2 is ascribed.

Select Verbose as the trace level.

Now that the new trace source has been identified to the Windows Communication Foundation, traces from that source have to be directed to the Windows Communication Foundation’s trace listener. To begin doing that, expand the Listeners child node of the Diagnostics node.

Select the ServiceModelTraceListener child node.

Click Add on the right pane, and, from the Add Tracing Source dialog, select MyTraceSource from the list of defined trace sources, and click OK.

Choose File, Save from the Service Configuration Editor menus.

Choose File, Exit to close the Service Configuration Editor.

Delete the app_tracelog.svclog file in the same folder as the TradingServiceHost project so that a new trace file will be created in which the custom trace emitted by the code in Listing 19.2 will be easier to pick out.

Right-click on the TradingServiceHost project, and choose Debug, Start New Instance from the context menu.

When the output in the console of the TradingServiceHost application confirms that the trading service is ready, enter a keystroke into the console to terminate the application.

Open the Service Trace Viewer, SvcTraceViewer.exe, in the bin subdirectory of the Windows SDK installation folder.

Choose File, Open from the Service Trace Viewer menus.

In the File Open dialog, select the app_tracelog.svclog that is in the same folder as the TradingServiceHost project, and click the Open button.

Select the first activity in the pane on the left, and the trace emitted by the code in Listing 19.2 will appear in the list of traces associated with that activity, as shown in Figure 19.17.

Figure 19.17. A trace from a custom source in the Service Trace Viewer.

Choose File, Exit from the Service Trace Viewer menus.

Right-click on the App.config file of the TradingServiceHost project and choose Edit WCF Configuration from the context menu. The Service Configuration Editor opens.

Select the Diagnostics node from the tree in the left pane.

Click on the link labeled Enable WMI Provider on the right pane to activate the WMI provider.

Choose File, Save from the Configuration Editor menus to save the configuration.

Select File, Exit from the menus to close the Configuration Editor.

Download the WMI Administrative Tools from http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6430F853-1120-48DB-8CC5-F2ABDC3ED314.

Install the WMI Administrative Tools.

In Visual Studio 2005, in the trading service solution, choose Debug, Start Debugging from the menus.

Wait until there is activity in the console window of the trade-recording service host.

Choose WMI Tools, WMI CIM Studio from the Windows Start menu.

Enter rootServiceModel into the Connect to Namespace dialog that appears, as illustrated in Figure 19.21. rootServiceModel is the namespace of the classes that the Windows Communication Foundation exposes to WMI.

Figure 19.21. Connecting to the rootServiceModel namespace.

Click OK on the WMI CIM Studio Login dialog to log in as the current user.

The classes that the Windows Communication Foundation exposes to WMI are enumerated in the pane on the left. Select Endpoint, as shown in Figure 19.22.

Figure 19.22. Selecting a class.

Click on the Instances button, which is the fourth button from the left in the row of buttons at the top of the right-hand pane. Information is displayed for each endpoint of any running Windows Communication Foundation application for which the WMI provider is enabled, as shown in Figure 19.23. The WMI CIM Studio retrieves that information via WMI, which, in turn, retrieves it using the Windows Communication Foundation’s WMI provider.

Figure 19.23. Viewing data retrieved via WMI.

Select the AppDomainInfo class in the pane on the right. As illustrated in Figure 19.24, one can modify properties of that class, such as the LogMessagesAtServiceLevel property, which configures message logging for a service. This facility allows one to configure properties of services while they are executing. Any modifications made in this way are made to the running instances only and are not persisted in any configuration file. To persist configuration elements in configuration files, use the Service Configuration Editor.

Figure 19.24. Configuring running services.

Choose File, Close from the WMI CIM Studio menus to close WMI CIM Studio.

Choose Debug, Stop Debugging from the Visual Studio 2005 menus.

Download Windows PowerShell from the Microsoft Downloads site, http://www.microsoft.com/downloads.

Install Windows PowerShell.

In Visual Studio 2005, in the trading service solution, choose Debug, Start Debugging from the menus.

Wait until there is activity in the console window of the trade recording service host.

Choose Programs, Windows PowerShell 1.0, Windows PowerShell from the Windows Start menu.

Enter the following command at the Windows PowerShell command prompt:

get-wmiobject endpoint -n rootServiceModel |ft name

Windows PowerShell displays the names of each Windows Communication Foundation endpoint on the local machine by querying WMI for the data for all endpoint objects in the rootServiceModel namespace, and displaying the name property of each one.

Close the Windows PowerShell console.

In Visual Studio 2005, choose Debug, Stop Debugging from the menus.

Right-click on the App.config file of the TradeRecordingServiceHost project and choose Edit WCF Configuration from the context menu. The Service Configuration Editor opens.

Select the Diagnostics node from the tree in the left pane.

Click on the link labeled Enable WMI Provider on the right pane to activate the WMI provider.

Click twice on the Toggle Performance Counters link on the right pane to cycle through the performance counter settings to the setting by which all the performance counters are enabled.

Choose File, Save from the Configuration Editor menus to save the configuration.

Select File, Exit from the menus to close the Configuration Editor.

Open the Program.cs file of the TradeRecordingServiceHost project in the trading service solution. After initializing the host of the trade recording service, the code in that file calls a custom IntializeCounters() method of the trading service’s service type:

public static void Main(string[] args)
{
    if (!(MessageQueue.Exists(queueName)))
    {
        MessageQueue.Create(queueName, true);
    }

    TradeRecorder tradeRecorder = new TradeRecorder();
    using (ServiceHost host = new ServiceHost(tradeRecorder))
    {
        host.Open();
        tradeRecorder.InitializeCounters(host.Description.Endpoints);
        Console.WriteLine("The trade recording service is available.");
        Console.ReadKey();
    }
}

Examine that method, which is in the TradeRecorder.cs module of the TradeRecordingService project. It is reproduced in Listing 19.3. The code for the method assembles a list of the names for the service’s endpoints:

foreach (ServiceEndpoint endpoint in endpoints)
{
  names.Add(
  string.Format("{0}@{1}",
  this.GetType().Name, endpoint.Address.ToString()));
}

Then it uses those names to retrieve the WMI objects corresponding to the endpoints of the running instance of the service:

string condition = string.Format(
  "SELECT * FROM Service WHERE Name="{0}"", name);
SelectQuery query = new SelectQuery(condition);
ManagementScope managementScope =
  new ManagementScope(
    @"\.
ootServiceModel",
    new ConnectionOptions());
ManagementObjectSearcher searcher =
  new ManagementObjectSearcher(managementScope, query);
ManagementObjectCollection instances = searcher.Get();

Those objects are then used to add the trade volume counter to that instance of the service:

foreach (ManagementBaseObject instance in instances)
{
    PropertyData data =
        instance.Properties["CounterInstanceName"];

    this.volumeCounter = new PerformanceCounter(
        TradeRecorder.CounterCategoryName,
        TradeRecorder.VolumeCounterName,
        data.Value.ToString());
    this.volumeCounter.ReadOnly = false;
    this.volumeCounter.RawValue = 0;
    break;
}

public void InitializeCounters(ServiceEndpointCollection endpoints)
{
    List<string> names = new List<string>();
    foreach (ServiceEndpoint endpoint in endpoints)
    {
        names.Add(
            string.Format("{0}@{1}",
                this.GetType().Name, endpoint.Address.ToString()));
    }

    while (true)
    {
        try
        {
            foreach (string name in names)
            {
                 string condition = string.Format(
                     "SELECT * FROM Service WHERE Name="{0}"", name);
                 SelectQuery query = new SelectQuery(condition);
                 ManagementScope managementScope =
                     new ManagementScope(
                         @"\.
ootServiceModel",
                         new ConnectionOptions());
                 ManagementObjectSearcher searcher =
                     new ManagementObjectSearcher(managementScope, query);
                 ManagementObjectCollection instances = searcher.Get();
                 foreach (ManagementBaseObject instance in instances)
                 {
                     PropertyData data =
                         instance.Properties["CounterInstanceName"];

                     this.volumeCounter = new PerformanceCounter(
                         TradeRecorder.CounterCategoryName,
                         TradeRecorder.VolumeCounterName,
                         data.Value.ToString());
                     this.volumeCounter.ReadOnly = false;
                     this.volumeCounter.RawValue = 0;

                     break;
                 }
            }
            break;
        }
        catch(COMException)
        {

        }

    }

    if(this.volumeCounter != null)
    {
        Console.WriteLine("Volume counter initialized.");
    }
    Console.WriteLine("Counters initialized.");

}

Look at the RecordTrades() method of the trade-recording service’s service type, which is in the same module:

void ITradeRecorder.RecordTrades(Trade[] trades)
{
    Console.WriteLine("Recording trade ...");
    return;
    lock (this)
    {
        while (this.volumeCounter == null)
        {
            Thread.Sleep(100);
        }
    }
     foreach(Trade trade in trades)
     {
         this.tradeCount+=((trade.Count != null)?trade.Count.Value:0);

         this.volumeCounter.RawValue = this.tradeCount;

         Console.WriteLine(string.Format("Recorded trade for {0}",trade));
     }
}

The method updates the trading volume performance counter with the value of each trade the service records. Currently, however, this return statement

Console.WriteLine("Recording trade ...");
return;

causes the method to exit prematurely. The reason is that the performance counter would not have been available until the WMI provider was activated for the service according to the instructions given previously. Only after the WMI provider was activated for the service would the InitializeCounters() method have been able to retrieve the running instance of the service to which to add the performance counter.

Because the WMI provider has now been activated for the service, comment out the return statement:

Console.WriteLine("Recording trade ...");
//return;

Choose Debug, Start Debugging from the menus.

Wait until there is activity in the console window of the trade-recording service host.

Choose Run from the Windows Start menu; then enter

perfmon

and click OK.

In the Performance console, right-click on the graph on the right side, and choose Add Counters from the context menu, as shown in Figure 19.18.

Select TradeRecording from the Performance Object list, TradeRecording being the name provided by the InitializeCounters() method for a custom performance counter category for the trade volume counter. As shown in Figure 19.25, the Trade Volume counter is shown as being available for the running instance of the trade recording service.

Figure 19.25. Adding the Trade Volume performance counter.

Click the Add button on the Add Counters dialog, and then the Close button.

Enter a keystroke into the console application window of the client application.

Observe, in the Performance Console, the movement of the custom trade volume performance counter, as depicted in Figure 19.26.

Figure 19.26. Monitoring the Trade Volume performance counter.

In Visual Studio 2005, choose Debug, Stop Debugging from the menus.

In the Performance Console, choose File, Exit from the menus to close it.