Configuring Workflow Manager in SharePoint 2013

Workflow Manager is a multi-tenant host for running and managing Windows Workflow Foundation workflows, and supporting high scale and high density execution. Workflow Manager builds on the Windows Workflow Foundation programming model, run time, and activity library in the .NET Framework.

When you install SharePoint 2013 in your server only 2010 workflows will be available in SharePoint. To work on SharePoint 2013 workflows, you should install and configure the workflow manager in the server.

Given below are the steps to configure your Workflow Manager:

  1. Ensure you have installed the SharePoint 2013, SQL, Active directory in your server.
  2. Ensure SharePoint related services are running.
  3. Install workflow manager and select default values, click finish and exit.To download the file:
  4. Install Cumulative updates for workflow manager and service bus.
  5. Now open workflow manager to configure.

  1. Give DB name and required details
  2. Give admin account for configuration.
  3. Select HTTP
  4. Give subscription key as configuration key (example: Zebra#@!)
  5. Click next
  6. Give same details for service bus configurations.
  7. Click finish

Go to IIS manager, select workflow management site under `sites’, click on browse 1229: http and note down the Url.

Open workflow management PowerShell and run the following script:

Register-SPWorkflowService -SPSite “http://localhost:port ” -WorkflowHostUri “http://localhost:12291″ -AllowOAuthHttp

SPsite will be your site collection URL and workflowHostUri will be your workflow manager site Url you just copied in the above steps.

if you get an error,  please run Add-PSSnapin and give the name as ” microsoft.sharepoint.powershell.

Then you go ahead and check whether SharePoint 2013 workflow option coming or not in designer. Create one test workflow. If you get the error while publishing below are the troubleshoots.

  1. Check whether the App Management Service application is created, if not then create the App Management Service application.
  2. Click on “Configure service application associations” available under the Service Applications section.
  3. Check whether the App Management Service proxy is added to the default proxy group, if not then add it to the default proxy group.
  4. Check whether the App Management Service is started, if not then start the service.
  5. Please refer 🙁 or follow below steps.


  • Hema Manjunath is a Senior Software Engineer with Trigent Software. She has over five years of experience and worked on languages such as CSS, HTML and JavaScript. She also has strong expertise in SharePoint (started working with SharePoint 2010 and now works with SharePoint 2013).