{"id":395,"date":"2015-12-09T10:10:28","date_gmt":"2015-12-09T10:10:28","guid":{"rendered":"https:\/\/www.sharepoint13.org\/?p=395"},"modified":"2015-12-09T21:30:52","modified_gmt":"2015-12-09T21:30:52","slug":"the-hitchhikers-guide-to-the-galaxy-of-workflows-part1","status":"publish","type":"post","link":"https:\/\/www.sharepoint13.org\/?p=395","title":{"rendered":"The Hitchhiker’s Guide to the Galaxy of WorkFlows Part1"},"content":{"rendered":"

<\/sub>SharePoint 2013 Workflow Platform Type is a seperate and powerful service to either O365 or SP2013 onPrem. First step is to get that WorkFlow Manager and ServiceBus thingie up and running. After that you\/dev\/anyone can create great workflows. Read on to  discover step-by-step what to do, or not to do, to get the platform in place on Premises. \u2013 Are you all into Office365? Don\u2019t bother to read any more \u2013U got it allready \"Smilefjes\"<\/p>\n

So here is my step by step guide (references and nice go-to places at the bottom)<\/p>\n

Step 1: Create users in Active Directory:<\/strong>
a) WFSetup account b) WFAdminAccount c)WFServiceAccount, I also use the same service account for the ServiceBus.
Step 1.1: Create WFAdmin security group in AD.
Add SharePoint setup account, SharePoint Farm Admin and the WFAdminAccount created in step 1<\/p>\n

Step 2: Grant access to SQL server<\/strong>
You can really use any SQL server to make this work, I used the SPFarm SQL server, standard edition is fine. Give the WFSetup account SysAdmin (wow) access. (yeah I know; should be dbcreator and security admin, but all Technet articles says sysadmin, believe you me \u2013 I tried..)<\/p>\n

Step 3: Give WFAdminAccount local admin rights and Install binaries:<\/strong> on the WorkFlow manager server \u2013or the SharePoint farm server you intend to use for this.
Step 3.3 Install Workflow Manager with the Web Platform Installer<\/a> 
Step 3.3.1 I didn\u2019t have Internet on my server so I had to extraxt the files, this you must do on a PC with Internet and WPI using elevated cmd
%programfiles%\\microsoft\\web platform installer\\webpicmd \/offline \/Products:WorkflowManager \/Path:c:\\WorkflowManagerFiles
<\/em>Copy the extracted files to WF Manager server
Run this elevated cmd from the folder c:\\workflowManagerFiles\\bin\\
WebpiCmd.exe \/Install \/Products:WorkflowManager \/XML:c:\/WorkflowManagerFiles\/feeds\/latest\/webproductlist.xml<\/em><\/p>\n

AT THIS POINT \u2013DO NOT RUN THE WIZARD OR CONFIG AT THE END OF SETUP! \u2013we must patch the WorkFlow manager and ServiceBus 1.0 first<\/em><\/p>\n

\"image\"<\/a>
Picture: by runnin the script I noticed that I had the latest WF Client (CU3) but not the latest WFM and ServiceBus cumulative updates<\/p>\n

Step 4: Install the latest CU\u2019s<\/strong> for: Cumulative update for ServiceBus<\/a> and Workflow Manager<\/a> (Desember 2015) \u2013always look for newer. ServiceBus 1.1 is released, but that version is not working for WorkFlow Manager 1.0 (as far as I know anywayz)<\/p>\n

Step 5: Configure WorkFlow Manager<\/strong>
(start the app you got) an select Custom settings!
\"image\"<\/a><\/p>\n

For SQL server address I uesd the same SQL Alias as I did for SharePoint farm, (added the farm with AutoSP installer and it\u2019s Best Practices to use an SQL Alias) click test in Form (don\u2019t change DB\u2019s name)
\"image\"<\/a><\/p>\n

. Add the WFServiceAccount from step1 as the Service Account, and the WFAdmin security group as Admin. I use http for farm, since its only a strictly internal farm. Autogenerated the Certs, and checked to allow http.
\"image\"<\/a><\/p>\n

Summary:
\"image\"<\/a>
I used the same service account for the ServiceBus<\/p>\n

Step 5:<\/strong> Pair the SharePoint Farm<\/strong> with the WorkFlow Manager service bus:
Logon locally to one of the WFEs using an account that has the following rights:
\u2022member of DOMAIN\\WFAdmins-securitygroup
\u2022member of SharePoint Farm Administrators
\u2022has been added to the ShellAdmin role for the target contentDb, refer to Add-SPShellAdmin PS cmdlet
– So that\u2019s why I did this as the SPFarm account \u2013don\u2019t use the setup account, to avoid doing the same mistake as I did..<\/p>\n

Before running the pairing script test that you can open with your browser both
1) SharePoint site 2) \u201cmyiiswebserver\u201d:122291 (you should see XML output) similar to this
\"image\"<\/a><\/p>\n

Run this PowerShell script as Admin to Pair (SP PowerShell or Add-PSSnapin microsoft.sharepoint.powershell<\/em>)
PS>Register-SPWorkflowService \u2013SPSite <\/em><\/strong>http:\/\/"MySPSite"<\/em><\/strong><\/a> -WorkflowHostUri <\/em><\/strong>http:\/\/"myiiswebserver":12291\/<\/em><\/strong><\/a> -AllowOAuthHttp<\/em><\/strong><\/p>\n

Step 6: Test it!
<\/strong>Install and open SharePoint Designer add a list workflow \u2013if you can select Platform Type: SharePoint 2013 Workflow you are Good To Go! \"Smilefjes<\/p>\n

<\/strong>
\"image\"<\/a><\/p>\n

– later I will blog a nice WorkFlow, so hang in.
Good Luck!<\/strong><\/p>\n

References:<\/p>\n

MS Technet on How to Configure: https:\/\/technet.microsoft.com\/en-us\/library\/jj658588.aspx?tduid=(6eead09eda78d971cee4b51d33eb3a5a)(256380)(2459594)(TnL5HPStwNw-Qb5gDxke69LQC4sZBrVhDw)()#section5<\/a><\/p>\n

Video Series to understand: https:\/\/technet.microsoft.com\/en-us\/library\/dn201724.aspx#episode2<\/a><\/p>\n

Least privelege blog http:\/\/blogs.msdn.com\/b\/briangre\/archive\/2013\/02\/20\/least-privilege-configuration-for-windows-azure-workflow-with-sharepoint-2013.aspx<\/a>
And never miss out Wictor Wil\u00e9n  http:\/\/www.wictorwilen.se\/Tags\/Workflow%20Manager<\/a><\/p>\n

Start all over (sometimes you just got to remove the whole shabong and start all over ) Follw this Technet article to fully uninstall
http:\/\/social.technet.microsoft.com\/wiki\/contents\/articles\/27689.sharepoint-2013-how-to-fully-uninstall-workflow-manager-1-0.aspx<\/a><\/p>\n

Download the Web Platform Installer: https:\/\/www.microsoft.com\/web\/downloads\/platform.aspx<\/a><\/p>\n

ShellAdmin Access https:\/\/technet.microsoft.com\/en-us\/library\/ff607596.aspx<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

SharePoint 2013 Workflow Platform Type is a seperate and powerful service to either O365 or SP2013 onPrem. First step is to get that WorkFlow Manager and ServiceBus thingie up and running. After that you\/dev\/anyone can<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[39,6],"tags":[5,40],"class_list":["post-395","post","type-post","status-publish","format-standard","hentry","category-guide","category-tip","tag-sharepoint-2013","tag-workflow"],"_links":{"self":[{"href":"https:\/\/www.sharepoint13.org\/index.php?rest_route=\/wp\/v2\/posts\/395","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sharepoint13.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sharepoint13.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sharepoint13.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sharepoint13.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=395"}],"version-history":[{"count":4,"href":"https:\/\/www.sharepoint13.org\/index.php?rest_route=\/wp\/v2\/posts\/395\/revisions"}],"predecessor-version":[{"id":403,"href":"https:\/\/www.sharepoint13.org\/index.php?rest_route=\/wp\/v2\/posts\/395\/revisions\/403"}],"wp:attachment":[{"href":"https:\/\/www.sharepoint13.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=395"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sharepoint13.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=395"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sharepoint13.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=395"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}