 |
SharePoint 2013 Workflow platform diagram |
- Workflow Manager (WM) provides the management of workflow.
- Workflow Manager (WM) is a separate entity outside SharePoint 2013 Server. WM doesn't install automatically with SP 2013 installer. First install Window Platform Installer (64 bit) and then with the help of WPI, you can install Workflow Manager 1.0. Download WPI over here. Once you install WPI, Open Application Tab and search for Workflow. Add "Workflow Client" component. Install it. Check out full video below. Note: Workflow Engine is still a part of SharePoint 2013 Server same like SharePoint 2010 Server.
- Workflow Manager is built on top of Windows Workflow Foundation (check screen above).
- Workflow Manager has its own dedicated DB & Farm in server where WM is installed.
- Service Bus is also an entity resides along with WM on WM Server. Service bus also has its own dedicated DB in server where WM is installed. This Service Bus is use to take SharePoint events like itemCreated, ItemUpdated and give it to WM.
- The SharePoint 2013 Workflow
platform uses the new Workflow Manager service.
- WM also hosts the execution processes for workflow instances. This process is called as ServiceHost.exe. ServiceHost.exe is the process use to debug Workflow in SharePoint 2013.
- Since WM is now a separate entity outside SP, it can be used by different application also (non SharePoint application) to enhance its ability. This was not the case in SP2010, where WF is used only for SharePoint purpose.
- The SharePoint 2010 Workflow platform that came with SharePoint Server 2010 like Sequential and State Machine is still available in SharePoint Server 2013.
- Window Workflow Foundation and WCF are hosted on Workflow Manager.
- Workflow Manager Client 1.0 is represented in SharePoint 2013 in the form of the Workflow Manager Client 1.0 Service Application Proxy.
- SharePoint events for which a workflow is listening, like itemCreated, itemUpdated, and so on, are routed to Workflow Manager Client 1.0 using the Microsoft Azure service bus. For the return trip, the platform uses the SharePoint Representational State Transfer (REST) API to call back into SharePoint.
References:-
No comments:
Post a Comment