Configuring Windows Communication Foundation

This page describes the installation and configuration process of Windows Communication Foundation (WCF). You have to configure WCF to use the following features:

WCF overview

WCF is a component of the .NET Framework that provides a programming model for building service-oriented multi-platform applications that communicate across the web. For more information on the technology, visit http://msdn.microsoft.com/en-us/netframework/aa663324.

Installing WCF

WCF is automatically installed with .NET 3.0 and any higher version. However, you still need to install the WCF HTTP Activation feature yourself:

  1. Open the Start menu in Windows.
  2. Navigate to Settings -> Control Panel -> Programs -> Programs and Features.
  3. Click on Turn Windows features on or off.
  4. Under the Microsoft .NET Framework 3.5 node, select the Windows Communication Foundation HTTP Activation check box.



  5. Click OK to start the installation.

The system installs WCF on your computer.

If you've installed WCF on a machine that had ASP.NET already installed, re-register ASP.NET into IIS. Use the ASP.NET IIS Registration Tool (aspnet_regiis.exe) with the -i parameter.

aspnet_regiis.exe -i

Configuring WCF services to use SSL

WCF services in Kentico applications are defined as service endpoints. By default, the service endpoints point to HTTP bindings. To use the services with SSL enabled, you must point the service endpoints to secure HTTPS bindings. Service endpoints and bindings are defined in local, application-specific, web.config files. You configure each service separately.

  1. Locate the application-specific web.config file according to the following table:

    ApplicationWeb.config location
    Chat/CMSModules/Chat
    Marketing automation/CMSModules/Automation
    Workflow/CMSModules/Workflows



  2. Open the web.config file and uncomment the secure endpoint code. The endpoint is defined in the configuration/system.serviceModel/services section.

    Example - commented HTTPS (secure) endpoint for Workflow
     <!--<endpoint name="Secure" address="" behaviorConfiguration="WorkflowDesignerEndpointBehavior" binding="webHttpBinding" bindingConfiguration="WorkflowDesignerSecureBinding" contract="CMS.WebServices.IWorkflowDesignerService" />-->
  3. (Optional) If you don't want the service to use the non-secure HTTP, comment out (or delete) the non-secure endpoint code.

    Example - HTTP (non-secure) endpoint for Workflow
    <endpoint name="Public" address="" behaviorConfiguration="AutomationDesignerEndpointBehavior" binding="webHttpBinding" contract="CMS.WebServices.IWorkflowDesignerService" />

The system now communicates with the services defined in the services section using the specified endpoints.

On this page