SharePoint 2013 now abstracts workflow processing to the cloud – using Windows Azure Workflow (WAW). SharePoint still maintains the legacy workflow engine, as part of the .NET Framework 3.5.1, to enable execution of SharePoint 2010 workflows. However, SharePoint 2013 does not install WAW by default. The following steps detail additional configuration.
1. Ensure you are not installing on a domain controller – WAW integration does not work with SharePoint 2013 running on a single server domain controller
2. Create an account in your domain for WAW
3. Add this account to the local administrators group on the SharePoint server and grant log on locally permissions
4. Ensure the SQL server accepts connections via TCP/IP – use the SQL Server Configuration Manager tool
5. Provide the WAW account access to SQL Server, include create database permissions (or you could grant administrative permissions if you are brave)
6. Log onto the SharePoint server as that account
7. Install Workflow Beta 1.0 (http://technet.microsoft.com/en-us/library/jj193478), using the Web Platform Installer
8. After installation, you should see the WAW Configuration Wizard
9. Click to create a new farm, using custom settings
10. Configure databases and click the Test Connection button for each
11. Make sure the WAW service account is correct – use the fully qualified domain name (FQDN), by default it prepopulates the textbox with a non-FQDN
12. Provide certificate generation keys
13. Leave the ports as default
14. Check the checkbox to allow management over HTTP (if you choose to use HTTPS you will need to establish trust between SharePoint and WAW using a trusted certificate)
15. Click the next button to move onto configuring the service bus
16. Complete similar steps for database, service account, and certificates settings as you did above
17. Again, leave the ports as default
18. Review the summary page, then click the tick button to complete the configuration
19. Wait for the configuration to complete – this might take a little time
20. After WAW configuration completes, run the following PowerShell command:
Register-SPWorkflowService –SPSite "http://{sitecollectionurl}" –WorkflowHostUri "http://{workflowserve}:12291" –AllowOAuthHttp
21. Assuming no errors, you have now configured WAW in SharePoint 2013 for your site collection
More information on installing and configuring WAW is available at the following URL: http://technet.microsoft.com/en-us/library/jj658588%28v=office.15%29
Item #1, WAW integration does not work with SharePoint 2013 running on a single server domain controller. Is this still true. If so, how would you configured this in a test lab? Two domain controllers?
You effectively answered your own question – avoid installing SP2013 on the same server as a domain controller. Allocate one server for your DC and another for SP. If you can spare boxes, also put SQL server on another server. (Virtualization recommended)