Home » SharePoint 2013 » Notes from Installing and Configuring Workflow in SharePoint Server 2013, Part One

Notes from Installing and Configuring Workflow in SharePoint Server 2013, Part One

Microsoft® provides SharePoint administrators with a set of six video presentations on the subject of installing Workflow Manager 1.0 for SharePoint Server 2013. As we just wrote in the previous post to this blog, SharePoint administrators for on premises SharePoint Server 2013 may want to skip this installation for several reasons:

  • The organization already has an extensive set of workflows in use, which were developed with the Workflow engine included with SharePoint Server 2010. As we noted in our last post, these workflows will continue to work fine with SharePoint Server 2013.
  • The organization requires workflows to be developed in accordance with the SharePoint Client Object Model. Workflow Manager 1.0 does not conform to the SharePoint Client Object Model, neither will workflows built to run over Workflow Manager 1.0
  • SharePoint Server 2013 Farm architecture does not conform to a high density, multi-tenant cloud profile. Workflow Manager 1.0 is intended to optimize performance of workflows for the likelihood an organization will implement a high density, multi-tenant cloud profile

If, given the above it still looks to be a sensible approach to install Workflow Manager 1.0, this series of videos from Microsoft can be helpful.

The set of 6 videos on this topic, Video series: Install and configure Workflow in SharePoint Server 2013, can be accessed on one page of Microsoft’s SharePoint site on TechNet.

The first video, “Installing and Configuring Workflow in SharePoint Server 2013, Part 1, and Introduction” is approximately 1 minute in length. The video presents the supporting infrastructure, which includes dedicated servers for SharePoint Server 2013, Workflow Manager, Active Directory, and SQL Server 2012. Windows Server 2012 runs on each of the 4 servers. The Domain Controller is Active Directory. The Active Directory server also performs the role of Certificate Authority for the example, Contoso domain. SharePoint Server 2013 should already be running for the example scenario to work.

Workflow Manager 1.0 implements a client server model. The client will run on SharePoint Server 2013. The server runs on the Workflow Manager server included in the infrastructure plan. A PowerShell commandlet will be run from the client to the Workflow Manager server. The client and server will be paired to complete the installation.

Ira Michael Blonder

© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved