SPCA2013 - Windows Workflow Manager for the IT Pro


Published on

Windows Workflow Manager for the IT Pro

Published in: Technology
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Day 2: 14:50 – 16:00 pmSharePoint 2013 allows you create similar workflows to those that you can build using SharePoint Designer 2010. SharePoint 2010 workflows are based on .NET Framework 3.5. Using SharePoint Designer 2013 you can also build SharePoint 2013 workflows which are based on .NET Framework 4.0. In this session, Penny will discuss the configuration and topology options available and their implications on availability. She will detail what an IT Pro must do to allow end users to build SharePoint 2013 workflows, as well as the architectural differences between SharePoint 2010 and 2013 workflows.Audience :Project Manager - IT Management - IT ProfessionalTopics :Infrastructure and Technology
  • /_layouts/closeConnection.aspx?loginasanotheruser=true
  • The art of workflowSet of activities mostly around control flow. Supplement. Domain specific – users create workflow from activities provide.Runtime – a way of taking a workflow and running those activities. Workflow hosts: workflow invoker, workflow application, workflow service host. Rehost VS Designer – Dynamics Exactor
  • SharePoint 2010 = Workflow Service Host – runs SharePoint 2010 workflowsSharePoint 2013 workflows => Workflow Manager – defacto, scalable host.Diagram does not mention invoker – as simplistic.
  • Cloud – messagingRoll you ownWF Backend – good at running workflow, high availability, multiple nodes in farm. Multi definition, multi instance. Fairness. Reads off service bus and runs workflows. Core runtime, and Activity Program Model.Cloud based. Message, state management, brokerage. durabilityGateway – entry point into the system. Manage instance – way to come in. Activity Program Model.Separation
  • The Workflow farm consists of two components: the Workflow Manager and a service bus that facilitates the communication among components within the farm by using the Open Authentication (OAuth protocol). The service bus is a messaging platform that has been running in Azure for some time that now can run on on-premises servers. The Workflow Manager uses the service bus as its core state management and messaging layer. All communication between SharePoint and the Workflow Manager is message based using a well-defined contract for events and management operations happening from SharePoint into the Workflow Manager using a series of Representational State Transfer (REST) HTTP calls. Therefore, the service bus is used for reliable message delivery and a message broker that also keeps the message state and workflow instance state consistent.
  • All communications with the workflow farm uses either the HTTP or HTTPS protocol. On servers within the workflow farm, within Internet Information Server (IIS) Manager, you will see one application pool, WorkflowMgmtPool, and one site, Workflow Management Site. A Workflow Manager server also contains the following four Windows NT services:
  • End to end reliabilityScalabilityFunctionality of running workflows in cloud, sandbox workflow execution + ship on-premises. Workflow Manager farm uses new SharePoint REST endpoints to communicate back to the SharePoint farm by using the App model API. Therefore, SharePoint 2013 workflows use the same set of services as Apps to complete their tasks.
  • SharePoint 2013 contains a new component known as the Workflow Services Manager, which is the integration layer between SharePoint and the Workflow Manager. The Workflow Services Manager connects to other SharePoint services by using the Workflow Service Application Proxy and connects to the Workflow Manager via the Workflow Manager Client. You can install the Workflow Manager on the same servers as SharePoint, in which case the Workflow Manager Client is automatically installed as part of the Workflow Manager installation, known as the collocated model. You can also install Workflow Manager on servers that do not have SharePoint installed—the federated model—in which case you will need to install separately the Workflow Manager Client on SharePoint servers that are responding to web requests, so that they can communicate with the Workflow Manager. You can build a federated workflow farm to achieve high availability by joining three servers to the farm because they work like a mirror with a witness; that is, the servers need to achieve a quorum (you can do this with just two servers).The Workflow Services Manager contains a number of services:Deployment This service manages workflow definitions. This is the service that deploys workflows you create in SharePoint Designer when you click the Publish command or when in the browser you associate a workflow template in the browser with SharePoint components, such as lists, libraries, content types, and sites.12 Exploring Microsoft® SharePoint® 2013: New Features & Functions Messaging This service takes events, such as when properties of a document change, and sends them as messages to the Workflow Manager. This Messaging service is also exposed to Apps. This makes it possible for Apps to have custom messages; for example, you can define a custom message from an external application that can be sent to a workflow and you can have a workflow that subscribes to that message. Instance This service manages workflow instances. Therefore, it is this service that is used to obtain workflow instance status information, or if you wish to terminate a workflow instance.Interop This service invokes SharePoint 2010 workflows.
  • Can be install on your SharePoint servers or on any servers.Not good practice to install on domain controllers.If heavy use of Workflows – or plan to be, then create a Workflow Manager farm separate from your SharePoint farmFor the communication between SharePoint and the Workflow Manager using web protocols, you can use web debugging tools such as Fiddler. In such debugging scenarios it is helpful to use the same service account for the Workflow Manager as is used for the application pool ID for your web application. You can read more about debugging workflows with fiddler at www.andrewconnell.com/blog/archive/2012/07/18/sharepoint-2013-workflow-advanced-workflow-debugging-with-fiddler.aspx.
  • The Workflow Manager installer checks for any prerequisites and installs any that it does not find. After the binaries are installed, the Workflow Configuration Wizard starts (you can also start it manually at any time).When you install the Workflow Manager on the first server, you create a workflow farm. You are asked which SQL server instance to create the farm databases, the service account, and to provide a Certification Generation Key, which has a similar function to the passphrase in a SharePoint farm. You will need this key when you join subsequent servers to the workflow farm. Each server within a workflow farm is known as a workflow node.
  • SBCA = Service Bus Certificate Authority – issues Farm and Encryption certificates (same), copied to Trusted Root Certificate Authorities store on servers that join the farm.
  • The Workflow Manager farm provides no native support for high availability at the storage layer. You can use your own solution, such as SQL Server mirroring.
  • SPCA2013 - Windows Workflow Manager for the IT Pro

    1. 1. Windows Workflow Manager for the IT Pro Penelope Coventry
    2. 2. 2
    3. 3. Speaker Bio • • • • • • • • PPP Consulting Ltd Microsoft MVP SharePoint Server MCSE: SharePoint Independent Consultant Author/Co-author of 10+ SharePoint Books Trainer Worked with SharePoint since 2001 Based in UK, work in Europe & US • Blogs/Web Site • http://www.sharepointdesignerstepbystep.com/ Twitter: @pjcov
    4. 4. Agenda Overview SharePoint 2013 Workflows Out-of-the-Box SharePoint 2010 Workflows SharePoint 2013 Workflows & SharePoint Designer 2013 IT Infrastructure Workflow Manager Installation
    5. 5. SharePoint 2013 : Two Workflow Engines • SharePoint Workflow Host o o o o o “Classic model” “2010 model” No enhancements Same limitations Same Actions/Conditions • Workflow Manager o o “New model” “2013 model”
    6. 6. Comparing 2010 / 2013 Workflow • WF 3.5 o Workflows run inside SharePoint • WF 4.5 o Workflows run outside in remote service
    7. 7. 2010 Issues that 2013 Addresses • 2010 o o o o On-Premise focus Full-trust extensions Limited scale Limited robustness • 2013 o o o o Cloud ≈ On-Premises CSOM/REST/OAuth Flexible scale More robust
    8. 8. Why use 2010 workflow at all? • • • You‟re upgrading You know 2010 workflow; it works Quirks well-understood No extra installations o o You have SharePoint Foundation o • 3.5 and 4.5 are incompatible No upgrade / conversion option o o • • Workflow Manager SharePoint Server Depends on SharePoint User Profiles You want features not in 2013 o (and you don‟t want to use Visual Studio)
    9. 9. Agenda Overview SharePoint 2013 Workflows Out-of-the-Box SharePoint 2010 Workflows SharePoint 2013 Workflows & SharePoint Designer 2013 IT Infrastructure Workflow Manager Installation
    10. 10. SharePoint 2013 Workflow Templates • There isn‟t any
    11. 11. Agenda Overview SharePoint 2013 Workflows Out-of-the-Box SharePoint 2010 Workflows SharePoint 2013 Workflows & SharePoint Designer 2013 IT Infrastructure Workflow Manager Installation
    12. 12. SharePoint 2010 Workflows • • • • As Before Workflow Foundation 3.5 Use Visio To Capture Requirements Use SharePoint Designer or Visual Studio to Build Workflow Templates
    13. 13. Agenda Overview SharePoint 2013 Workflows Out-of-the-Box SharePoint 2010 Workflows SharePoint 2013 Workflows & SharePoint Designer 2013 IT Infrastructure Workflow Manager Installation
    14. 14. SharePoint 2013 Workflows New Building Blocks • • • Stages Control Actions Loop o • o App-Only Step o • Loop n times Loop with Condition o Actions (activities) run as App ID permission Not restricted to permissions of initiator Parallel Block o „CompletionCondition‟ short-circuit of exit
    15. 15. New Variable Type: Dictionary • Container o • Actions o o o • A Collection of other Variables Build Dictionary Count Items In A Dictionary Get An Item From A Dictionary Critical when using Call HTTP Web Services
    16. 16. Copy & Paste • • Workflow logics can be copied and pasted Pasted into Word & Notepad
    17. 17. Packaging • Not only reusable workflow but also list/site workflow can be packaged
    18. 18. Views - Visual Designer • New design surface in SharePoint Designer 2013 o o o • Creating and editing SharePoint 2013 workflows Based off the Visio design surface Click and drag experience for creating/editing Workflow Fully integrated experience between Business Analyst and Workflow Developer o o SPD and Visio both use the same VSDX file Stage View for flow-level view
    19. 19. SharePoint 2013 Workflows: Missing Actions & Conditions • • Document Set related actions o o o o Capture a version of the Document Set Send Document Set to Repository Set Content Approval Status for the Document Set Start Document Set Approval Process Impersonation Step Permission related actions and conditions o o o o o o Add List Item Permissions Inherit List Item Parent Permissions Remove List Item Permissions Replace List Item Permissions Check list item permission levels (condition) Check list item permissions (condition)
    20. 20. SharePoint 2013 Workflows: Missing Features • Task and Task Process related actions o o o o o o • Assign a Form to a Group Assign a To-do Item Collect Data from a User Start Approval Process Start Custom Task Process Start Feedback Process Others o o o o o o Lookup Manager of a User Declare Record Set Content Approval Status Wait for Field Change in Current Item If current item field equals value (condition) Impersonation Step (Block)
    21. 21. SharePoint 2013 Workflows: No Visualization • Not supported in WF4
    22. 22. Windows 2013 Workflows: No InfoPath Forms • • Not supported in WF4 Aspx pages are auto-generated: o o o Association Form Initiation Form Task forms
    23. 23. Mitigation • • Start a List Workflow Start a Site Workflow 23
    25. 25. Agenda Overview SharePoint 2013 Workflows Out-of-the-Box SharePoint 2010 Workflows SharePoint 2013 Workflows & SharePoint Designer 2013 IT Infrastructure Workflow Manager Installation
    26. 26. What is Workflow? • Window Workflow Foundation: 3 components o • Runtime Activity Programming Model Runtime • Workflow Execution • Workflow Lifecycle Management o Workflow Activity Library Activities • Sequential • State Machines • Custom Activities o Activities Core Runtime (Workflow Instance) Persistence Tooling No Inherent execution process Host Runtime & Services Tracking Timers Process (.exe, IIS, …) Tooling VS Designer Rehost Designer Custom Designer 26
    27. 27. Hosting .NET Workflows • Async execution of a single workflow instance • Explicit, fine-grained control of the WF runtime • Host application integration • WF-driven UI • Async execution of multiple workflow instances • Supports durable timers, persistence, tracking, WCF SOAP, correlation, etc. • Systems integration • Service-based architecture • Multi-tenant, scalable hosting of workflows • Turnkey artifact management • Supports durable timers, persistence, HTTP, pub/sub using Service Bus, etc. • Extensible SaaS applications Workflow Application Activity Prog Model Core Runtime Host Services Workflow Service Host Activity Prog Model Core Runtime Host Services Workflow Manager Activity Prog Model Core Runtime Host Services
    28. 28. What is Workflow Manager? • Design Goals o o o o o Scale & Reliability Multi-tenancy Cloud-based Messaging Turnkey WF4 Prog Model HTTP & HTTPS WF Resources .NET Client WF Backend (.EXE) WF Gateway (IIS) Service Bus
    29. 29. Workflow Manager Components 29
    30. 30. Workflow Manager Infrastructure • • • • HTTP or HTTPS communication • One App Pool: WorkflowMgmtPool One Site: Workflow Management Site 6 SQL Server Databases o • WFManagementDB • WFInstanceManagement DB • WFResourceManagemet DB 4 Windows NT Services o o o o WorkflowServiceBackend Service Bus Backend Service Bus Gateway FabricHostSvc Workflow Databases o Service Bus Databases: • SBManagementDB • SbGatewayDatabase • SBMessageContainer01
    31. 31. SharePoint 2013 Workflows SharePoint Workflow Authoring SharePoint WF Workflow Visual Studio SharePoint Designer WF HTTP / OData Office 365 ----SharePoint Server Windows Azure Workflow ----Workflow Manager
    32. 32. Workflow Manager Architecture
    33. 33. Agenda Overview SharePoint 2013 Workflows Out-of-the-Box SharePoint 2010 Workflows SharePoint 2013 Workflows & SharePoint Designer 2013 IT Infrastructure Workflow Manager Installation
    34. 34. Workflow Manager Installation: Before 1. SQL Server o o 2008 R2 SP1, Express 2008 R2 SP1, or 2012. TCP/IP connections or named pipes must be configured in SQL Server. 2. Minimum Hardware: 2 Cores, 2GB RAM o o Windows Firewall must be enabled. Ports 12290 and 12291 must be available 3. User Accounts i. ii. iii. Configuration user: administrative credential RunAs User (service account) Admin Group
    35. 35. Workflow Manager Installation • Install o o o • • Using WebPI or Download Center Prerequisites Binaries Run Workflow Manager Configuration Wizard Create Workflow Manager Farm o o Certification Generation Key Similar to PassPhrase in a SP Farm
    36. 36. Web Platform Installer (WebPI) • • Free tool Makes getting the latest Web components easy o o o o o o o o Internet Information Services (IIS), SQL Server Express, .NET Framework and Visual Web Developer Service Bus 1.0 Service Bus 1.0 Cumulative Update 1 Workflow Manager 1.0 Workflow Manager 1.0 Cumulative Update 1 36
    37. 37. Autogenerated Certificates • Workflow Manager Configuration wizard o • Service Bus o o o • Expiry date (5 years) AppServerGeneratedSBCA Farm certificate Encryption certificate Workflow Manager o o o Services SSL certificate – Self-signed Encryption certificate Outbound signing certificate – CA Root Certificate 37
    38. 38. Viewing Certificates 38
    39. 39. Check Workflow Manager Installation • PowerShell o o o o • Get-SBFarm Get-SBFarmStatus Get-WFFarm Get-WFFarmStatus Browser o https://wmnlbname:12290 39
    40. 40. Register Workflow Manager Farm with SharePoint Farm • SharePoint Server : o At least KB2767999 March 2013 Cumulative Update Register-SPWorkflowService –SPSite http://intranet.adventure-works.com –WorkflowHostUri https://wmnlbname:12290 –AllowOauthHttp • If SP Server not a Workflow Node: Install Client Version of WM
    41. 41. Check Workflow Manager to SharePoint Communication • Central Administration o o Workflow Service Application Proxy Workflow Service Status page • Workflow is Connected • Create a SharePoint 2013 workflow using SharePoint Designer 41
    42. 42. Valid Topologies and High Availability • Storage – No Native support in Workflow Manager o o • o SQL Mirroring SQL Replication Backups and / or Backup and log shipping Service Bus o One or Three servers 42
    43. 43. Recommended Configurations • Use o o o o o • • SSL SQL Alias for SQL Server Separate SQL Instance Dedicated RunAs (service) Account Leave everything else as defaults Use Workflow Manager Configuration Wizard or PowerShell Disaster Recovery / Business Continuity 43
    44. 44. Monitoring a Workflow Manager Farm • • Performance Counters Event Tracing for Windows(ETW) o • Windows PowerShell o • Event Viewer Get-WFFarm System Center Operations Manager Management Pack
    45. 45. Resources • Spence Harbar‟s Workflow Manager series o • • • • Andrew Connell‟s blog o http://www.andrewconnell.com/Tags/Workflow Configure workflow in SharePoint Server 2013 o http://technet.microsoft.com/en-us/library/jj658586.aspx Workflow Manager 1.0 o http://msdn.microsoft.com/en-us/library/jj193528(v=azure.10) Service Bus Architecture o • • http://www.harbar.net/archive/2013/08/02/Article-Workflow-Manager-Farms-for-SharePoint2013-Part-Four-End.aspx http://technet.microsoft.com/en-us/library/72646b45-646f-4dfb-ab52e42f187655e7(v=azure.10) Disaster Recovery and Scope Restore in Workflow Manager 1.0 o http://msdn.microsoft.com/en-us/library/jj730570(v=azure.10).aspx Web Platform Installer v4 command line (WebPICMD.exe) o http://www.iis.net/learn/install/web-platform-installer/web-platform-installer-v4-command-linewebpicmdexe-rtw-release 45
    46. 46. Questions 46
    47. 47. Please rate this session! Fill out the survey and get a chance to win a Surface
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.