Avid SharePointer, Global Expert Speaker in most SharePoint Conferences.. Was living in Dubai and worked @ Infusion Founder of Dubai SharePoint User Group Mai Omar Desouki Workflow Manager Tips & Tricks Senior SharePoint Consulant Vodafone Egypt Cairo Egypt Contacts @MaiOmarDesouki Mai_omar_86@live.com http://maiomardesouki.com
SharePoint 2010 Workflows • If you had 2010 WF, it will continue to work in SP 2013 farm • And you still can create a new 2010 WF in SP 2013 Farm
Supported Operating Systems • Windows Server 2008 R2 SP1 x64 • Windows Server 2012 x64 WARNING: Windows 7 SP1 ×64 and Windows 8 ×64 are not supported for production environments, but you can install Workflow 1.0 on them for development purposes.
SQL Server requirements • SQL Server 2008 R2 SP1 • SQL Server 2012 Note: SQL Server can be installed on the same physical machine with Workflow 1.0 and Service Bus, or on a different one. This flexibility is most valuable for your development environment, minimizing the number of servers or virtual machinesyou need.
Requirements for SQL Server • TCP/IP, shared memory, or named pipes must be enabled. • Port 1443,12290 and 12291on the firewall must be open to inbound and outbound communications. • If named pipes are used, the name of the machine on which the SQL Server instance is running should have a name with no more than 16 characters. Named pipes use NetBIOS names, which carry that restriction. • Supported Authentication • Integrated Authentication • SQL Authentication
Current userThe user that is configuring Workflow Manager must meet this requirements • If the machine is domain joined, the user must be a domain user; otherwise the user must be a local user. • The user must be an administrator on the computer on which the configuration is running. • The user must have DBCreator privilege on this SQL Server instance. Note: Workflow Manager does not support built-in accounts (for example, NETWORK SERVICE).
Installing & configuring Windows Azure Workflow Manager • Install the Windows Azure Workflow Server software • Configure a workflow farm • Join the SharePoint farm to the workflow farm
Firewall • During configuration, Workflow Manager will open ports that are configured by default or set explicitly by the user in the Windows Firewall. • If a firewall other than Windows Firewall is used, you will have to make these exceptions manually.
Database Names Workflow Manager databases • WFManagement • WFInstanceManagement • WFResourceManagement Service Bus databases • SBManagement • SBGateway • SBMessageContainer01
Once it’s installed, we need to pair it with SharePoint By PowerShell; there is no user interface for this
Https certificate For your production environment and communication over HTTPS.. • Create a digital certificate • configure IIS • export the certificate • and then import and install the certificate on the SharePoint server This ensures encrypted communication between SharePoint and Workflow Manager
Tips When you are ready to pair the farms… Execute the following PowerShell cmdlet using the SharePoint 2013 Management Shell window. The command does not return any output if successful, so no news is good news. This script describes how SharePoint and workflow manager will communicate. Register-SPWorkflowService –SPSitehttp://intranet.contoso.com–WorkflowHostUrihttp://contososerver.contoso.com:12291–AllowOAuthHttp
Important Ports • HTTP = 12290 • HTTPS = 12291 intranet.contoso.com, then you would use http://intranet.contoso.com:12291