The installation of Microsoft Workflow Manager 1.0 is not that complex. A description could be found in Technet. To use Workflow Manager in a SharePoint 2013 development environment, I will show the necessary steps in this post.

First of all, I have prepared a development environment that is composed of two parts, because Workflow Manager can/should not run on an Active Directory domain controller.

Machine 1 (machine name “WS2012”):

  • Windows Server 2012
    • Active Directory Domain Services
    • DNS
  • SQL Server 2012 SP1

Machine 2 (machine name “sharepoint”):

  • SharePoint Server 2013
    • CU March 2013
    • CU August 2013
  • Office 2013 ProPlus
  • SharePoint Designer 2013
  • Visual Studio 2012 Premium with Update3

In SharePoint 2013 the CU March 2013 should be installed! For completeness it is useful, to have Visio 2013 installed, because this brings the functionality to design workflows in SharePoint Designer with a graphical interface.

In SharePoint I have these service applications configured, which are necessary for workflows with Workflow Manager:

To test the workflow functionality I have created one web application http://workflow.mydomain.local.

In the next steps I will install Workflow Manager 1.0 and connect the instance to the SharePoint farm. Most parts are following the description from Microsoft.

For Workflow Manager a separate account was created in my Active Directory domain. This account is local administrator on the machine, where the Workflow Manager is installed. Microsoft recommends installing Workflow Manager, when you are logged in with this service account. I installed Workflow Manager in this development environment, when I was logged in as the domain administrator without any problem.

Start an Internet Explorer instance with administrative priviledges and open the Web Platform Installer.

In the Workflow Manager 1.0 line click “Add” and then “Install”.

Click “I Accept”…

… and “Continue”.

This will install the Service Bus and the Workflow Manager on the machine (Machine 2 in our case).

When the installation is done, the Workflow Manager Configuration Wizard is started automatically.

Click “Configure Workflow Manager with Default Settings (Recommended”).

Even when the USER ID in the picture above is shown in email format, use “DOMAIN\username” instead!

On the development machine we can use HTTP for Workflow Manager, so check this option. Enter a phrase for the certificate generation key in the fields at the bottom.

Click the right arrow to continue.

Check the settings on the summary screen and click the right arrow.

The installation is started and after a few seconds (minutes J) it will finish successfully. Click the check mark at the bottom.

The installation of Workflow Manager 1.0 is done, but we are not finished.

Next we need to install the CU1 of the Service Bus and of the Workflow Manager. Microsoft provides separate CUs for these products. I recommend to install the CU1 for the Service Bus first.

Start the Web Platform Installer (in Windows Server 2012 by pressing the Windows key and typing “Web platform”, this will show the link).

In the Web Platform Installer search for “Service Bus” and click “Add” in the line with “Service Bus 1.0 Cumulative Update 1”, then click “Install”.

Click “I Accept” and the installation of the Service Bus CU1 is started. When the installation is finished, the machine reboots automatically.

When you are logged in again, start the Web Platform Installer and search for “Workflow Manager”.

Click “Add” in the line with “Workflow Manager 1.0 Cumulative Update 1” and click “Install”.

Click “I Accept” to start the installation.

Click “Finish”.

Next we need to install the Microsoft Office Developer Tools for Visual Studio 2012. Again, start the Web Platform Installer and search for “Office”.

Click “Add” in the line with “Microsoft Office Developer Tools for Visual Studio 2012” and click “Install”. Alternatively you can use this link http://aka.ms/OfficeDevToolsForVS2012 to start the installation.

Click “Install”.

Click “I Accept”.

It is recommended to check “Use Microsoft Update…”, but in virtualized development environments I often check the “I don’t want to use Microsoft Update”, because it is not funny to work via mobile connection, when Microsoft Update is downloading files. Click “Continue”, when your selection is done.

This installation should finish sucessfully. Click “Finish” to close the dialog.

Next we have to connect Workflow Manager to our SharePoint environment. This is done with the cmdlet Register-SPWorkflowService:

Register-SPWorkflowService –SPSite "http://workflow.mydomain.local" –WorkflowHostUri "http://sharepoint:12291" –AllowOAuthHttp

When the cmdlet has finished we see the Workflow Service Application Proxy in the service applications in Central Administration.

Clicking the link should show a connection message.

That’s it. Workflow Manager is installed in our development environment. To test the functionality create a simple workflow, deploy the workflow and execute the workflow on an item or a document. From my experience also test sending emails from a workflow.

You may run into a problem with the permissions of the Workflow Manager account in one of the databases. In my environment I had to make the account a “dbo” in the “WFInstanceManagementDB” in SQL Server.

Some additional hints for the installation and configuration:

The Workflow Manager account should be local administrator on the machine, where Workflow Manager is installed.

First install the CU1 for Service Bus 1.0 and then install the CU1 for Workflow Manager 1.0.

There may be problems in name resolution. This may result in an Oauth error in the ULS log. Follow this article in this case.

In a second post I will show the installation of Workflow Manager 1.0 in an offline scenario.

Advertisements