SharePoint Workflow Manager setup

(see also Part1: SharePoint Workflow Manager Review)

Installation (offline) step-by-step

Ensure hardware/software requirements. Ensure/configure your server (time, time zone, IP, hostname, domain, language, region, ESC, updates, event log).

Accounts you need (for example):

  • Svc-WFM-FarmAdm – domain users + local admin on WFM Servers, DBCreator and SecurityAdmin on SQL
  • Svc-WFM-SBAcc – domain users
  • Svc-WFM-WFAcc – domain users

DNS: wfm.contoso.kz points to Workflow Manager Server (or load-balancer)

On an Internet connected machine:

(see also Part1: SharePoint Workflow Manager Review)

Installation (offline) step-by-step

Ensure hardware/software requirements. Ensure/configure your server (time, time zone, IP, hostname, domain, language, region, ESC, updates, event log).

Accounts you need (for example):

  • Svc-WFM-FarmAdm – domain users + local admin on WFM Servers, DBCreator and SecurityAdmin on SQL
  • Svc-WFM-SBAcc – domain users
  • Svc-WFM-WFAcc – domain users

DNS: wfm.contoso.kz points to Workflow Manager Server (or load-balancer)

On an Internet connected machine:

  • Download and install WebPICmd.exe  http://bit.ly/WebPIv4
  • From an Administrator Command prompt:
    webpicmd.exe /offline /Products:WorkflowManager /Path:c:OfflineWorkflow
    (Will download Workflow Manager and it’s pre-reqs to the specified folder)

Copy contents "c:OfflineWorkflow" to intended servers.

On SharePoint Servers:

  • enshure updates (run psconfig)
  • Start Microsoft SharePoint Foundation Subscription Settings Service
  • Start App Management Service

Run Powershell commands (admin):

$account = Get-SPManagedAccount "domainSvc-SP15-SvcApplP"
$sssdbname = "SP15_SubscriptionSettingsService"
$appsvcdbname = "SP15_AppManagementService"
# SubscriptionSettingsServiceApplication
$appPoolSubSvc = New-SPServiceApplicationPool -Name SubscriptionSettingsServiceAppPool -Account $account
$appSubSvc = New-SPSubscriptionSettingsServiceApplication -ApplicationPool $appPoolSubSvc -Name SubscriptionSettingsServiceApp -DatabaseName $sssdbname
$proxySubSvc = New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $appSubSvc
#  App Management service
$appPoolAppSvc = New-SPServiceApplicationPool -Name AppServiceAppPool -Account $account
$appAppSvc = New-SPAppManagementServiceApplication -ApplicationPool $appPoolAppSvc -Name AppManagementService -DatabaseName $appsvcdbname
$proxyAppSvc = New-SPAppManagementServiceApplicationProxy -ServiceApplication $appAppSvc

From an Administrator Command Prompt:
(Workflow Client 1.0 must be installed on each web-front end (WFE) in the SharePoint 2013 farm):
install WebPICmd.exe
WebpiCmd.exe /Install /Products:WorkflowClient  /XML:c:offlineWorkFlowfeedslatestwebproductlist.xml /AcceptEULA

restart-computer, Updates, Event Viewer

On Workflow Manager Server(s), From an Administrator Command Prompt:

add .NET 3.5 feature
install WebPICmd.exe
WebpiCmd.exe /Install /Products:WorkflowManager /XML:c:offlineWorkFlowfeedslatestwebproductlist.xml /AcceptEULA
cliconfg – set SQL Server Alias
consider admins (privileged) group – domain group, add Svc-WFM-FarmAdm and Svc-SP-FarmAdm (SharePoint setup) accounts
Configuration Wizard: Start | All Programs | Workflow Manager 1.0 | Workflow Manager Configuration
Store cert gen key
 

Validating install and configuration

Get-SBFarmStatus & Get-WFFarmStatus: Will report on Windows Services state and http(s) availability

Windows Services:

  • Workflow Manager Backend
  • Service Bus Message Broker      <- will often take a while to start
  • Service Bus Gateway
  • Windows Fabric Host Service

Certificates:

On SharePoint servers:
Open "https://wfm.contoso.kz:12290", save certificate, then:
$trustCert=Get-PfxCertificate "C:Distrswfm.cer"
New-SPTrustedRootAuthority -Name "Workflow Manager Farm" -Certificate $trustCert

From IIS export certificate, copy file to WFM servers, On WFM servers: add to trusted…

Register-SPWorkflowService :

On SharePoint servers:
Register-SPWorkflowService -SPSite "https://sharepoint.contoso.com" -WorkflowHostUri "https://wfm.contoso.com:12290"

 

Federated WFM Topology

If you want multiple SharePoint 2013 farms to use the same Workflow farm (Federated WFM Topology)
… you should use the ScopeName parameter of the Register-SPWorkflowService cmdlet.
That parameter will create a new Scope in the Workflow farm, and with that create an isolated container for this new SharePoint farm.
Some people say in this case -Force parameter needed.
So on our second farm we run this PowerShell cmdlet:

1
2
3
4
Register-SPWorkflowService
    -SPSite https://farmb.corp.local
    -WorkflowHostUri https://wffarm.corp.local:12290
    -ScopeName FarmB
-Force

 

Workflow Manager Business Continuity Management

…

Service Account Password Changes

Workflow Manager and Service Bus.If Service Accounts are expired by policy. Using the Configuration Account, or other Workflow Manager and Service Bus Administrator account.

$newPassword = ConvertTo-SecureString -String "NewPassword" -AsPlainText -Force

# to run on each host of the Service Bus farm
Stop-SBHost -Verbose
Update-SBHost -RunAsPassword $newPassword -Verbose
Start-SBHost -Verbose
# to run on each host of the Workflow manager Farm
Stop-WFHost -Verbose
Update-WFHost -RunAsPassword $newPassword -Verbose
Start-WFHost -Verbose

Rename a Server

  • Remove from Farm
  • Rename Server
  • Join back to Farm

Reduce Farm to one Server

  • Remove all machines (keep databases)
  • Join existing farm from existing machine

 

==============

sources:

One thought on “SharePoint Workflow Manager setup”

  1. Pingback: SharePoint Workflow Manager quick review and setup guide - Vladilen

Comments are closed.