Home > Workflow Manager > Installing Workflow Manager 1.0

Installing Workflow Manager 1.0

This post covers the installation of a new Workflow Manager 1.0 farm. For this installation, we are choosing to use an existing SharePoint 2013 farm. The intent is to have the SharePoint farm configured to leverage Workflow Manager to enable the SharePoint 2013 workflow platform. It is not required that you install a workflow farm on a SharePoint farm. Workflow Manager 1.0 can be installed on its own server farm and SharePoint 2013 can be setup to communicate with it over the standard service endpoints.


Before installing the Workflow Manager and Service Bus components on a new environment, it will help greatly to plan a few things out and have them ready for when the installation and configuration of the product will commence.

The following documentation has been captured from an installation on a single server SharePoint 2013 farm but if you are installing on a larger farm, it may be advisable to install the product on more than one server and add them to the farm that is created through the configuration process after the installation on the first server. This ensures the workflow services are highly available and are not prone to a single point of failure.


To prepare for the installation of workflow manager, check for the pre-requisites where installing.

The following are the pre-requisites to install Workflow Manager 1.0

  • .NET Framework 4 Platform Update 3 or .NET Framework 4.5
  • Service Bus 1.0
  • Workflow Client 1.0
  • PowerShell 3.0

The following are the pre-requisites to configure Workflow Manager 1.0

  • Instance of SQL Server 2008 R2 SP1, SQL Server Express 2008 R2 SP1, or SQL Server 2012.
  • TCP/IP connections or named pipes must be configured in SQL Server.
  • Windows Firewall must be enabled. [Windows Firewall is Off on target server]
  • Ports 12290 and 12291 must be available.

Supported platforms

Check for supported platforms. The below represents the platforms on which installation will be attempted and the confirmation that they are supported.

  • Windows Server 2012 x64 Standard and Enterprise are supported
  • SQL Server 2012 with Default Collation and Windows Authentication is supported

The installation will be performed using an account that is a domain account on the domain the SharePoint 2013 farm servers are joined to and also a local administrator on the machine.

Runas Account

The Workflow Manager and Service Bus components of the Workflow solution will both expose a service endpoint that clients can connect to. The service will need a domain account to run as. The service account spdev\spsvcs which corresponds with the SharePoint Managed Account for SharePoint services will be used as the RunAs account for Workflow Manager. This account will automatically be granted Logon as a service privilege during configuration.

Database names

The Workflow Manager and Service Bus components of the solution will each create three databases that they can work with. If you have naming conventions for databases or need to do some general cleanup of names for better future understanding, this is the time to do it. Here are the names that I am going with.

Workflow Manager databases

  • WFManagement
  • WFInstanceManagement
  • WFResourceManagement

Service Bus databases

  • SBManagement
  • SBGateway
  • SBMessageContainer01


The product can be installed directly through the Web Platform Installer on a machine that is connected to the Internet. However, the installation on the target SharePoint 2013 farm that I am attempting will be done in Offline mode based on the instructions provided here.

Download the Web Platform Installer

On a machine connected to the Internet – to be referred to as the source machine – access this location and download the installer file for the Web Platform Installer. Once downloaded, run the MSI and the Web Platform Installer should be installed to %ProgramFiles%\Microsoft\Web Platform Installer.

Launch a new command prompt as administrator and run the following command

webpicmd /offline /Products:WorkflowManager /Path:C:\WorkflowManagerFiles

The required files will be copied down to the location indicated.


If the specified directory doesn’t exist, it gets created during the download process and the required files should now be available there if the process was successful as indicated below.


The next step is to copy these files over to the target machine.


Once the files are copied to the target server, launch an elevated command prompt and navigate to the bin folder contained within the Workflow Manager files folder used. This location will contain the Web Platform Installer executable that can be run in offline mode. Run the following command

WebpiCmd.exe /Install /Products:WorkflowManager

NOTE: The command provided in the TechNet article referenced above does not work with the list of files available through the download. Run the command as provided here.


Once the files required are identified, the EULA for the files is presented. Type ‘Y’ and press Enter to proceed.


Once the installation is done, the following messages is what you should see unless there was an error somewhere.


Also, the Workflow Configuration tool is launched as shown below


This article focused on the planning and installation of the Workflow Manager product in offline mode on a target SharePoint 2013 environment. Check out how to Configure Workflow Manager 1.0 to continue.

  1. No comments yet.
  1. December 12, 2013 at 6:34 AM

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: