Sharing my approach and knowledge of setting up a SharePoint 2013 development server with Workflow Manager 1.0. There are many step by step guides on installing and configuring Workflow Manager 1.0; however, this is from a topology point of view as well as areas of validating the setup.

1. Database ServerWeb Front End & App Server
Workflow
Manager
Service Bus
SQL
Server 2012
Workflow
Client
SharePoint
Server
My Development Server: Component Architecture
I have a 2 server farm where one server acts as the SharePoint web and app server as well as the Workflow Farm.
The other server is the database for both SharePoint Server, Workflow Manager and any other applications.

2. Web Front End &
App Server
Workflow
Manager
Service Bus
Workflow
Client
SharePoint
Server
Installation Components
Downloads
Workflow Manager 1.0
(includes workflow client and tools)
Cumulative Update for Workflow
Manager 1.0
Service Bus 1.0
Cumulative Update for Service Bus
1.0

3. Web Front End Server
Database Server
Web Front End Server
SQL
Server 2012
SharePoint
Server
Workflow Server (1)
Workflow
Manager
Service BusWorkflow
Client
App Server
SharePoint Server
Workflow Server (N)
Workflow
Manager
Service Bus
. . .
Workflow Manager Farm
Database Server
SQL
Server 2012
Workflow Service
Application
http / https
Scaled Out SharePoint and Workflow Farm
SharePoint Farm

4. SharePoint Server
Workflow Server
Service Accounts
Assume Workflow Manager Service Account as
corpwfmanager
IIS Web Server
Application Pool Name: WorkflowMgmtPool
Service Account : corpwfmanager
Urls / endpoints:
Https://localhost:12290
http://localhost:12291
Services Service Account : corpwfmanager
Note: Ensure corpwfmanager account is in the Administrators group.
This ties into the Workflow Configuration setting of
WorkflowAdminGroupName to ‘BUILTINAdministrators’ (by default)

5. Database Server
Service Accounts (continued)
SQL Server Windows Service Account : corpwfmanager
Note: Before configuration, assign this account db_owner and
db_securityadmin roles.

6. Registering Workflow Server via PowerShell
After Workflow Manager is setup and configured, you must configure the
SharePoint host to use the workflow service.
A Workflow Service Application Proxy is created for the farm and for all web
applications. Look in Central Administration > Manage Service Applications.
Register-SPWorkflowService –SPSite "http:<SP_Server>/yourSite" –
WorkflowHostUri "https:WF_Server:12290" –AllowOAuthHttp
Note: best that <WF_Serve> is the fully qualified domain name.
e.g. wfserver.mydomain.com
Reference: http://technet.microsoft.com/en-us/library/jj663115.aspx

7. Workflow Service Application Proxy
Go to Central Administration > Service Applications
Click
Validating Configuration

8. Validating Configuration
IIS Web Server - Workflow Management Site
Go to any browser > Enter url https://localhost:12290 and http://localhost:12291

9. Validating Configuration
Workflow Manager Service Host
Open Workflow Manager or Service Bus PowerShell Command
Make sure to ‘Run As Administrator’ even if you logged as a user with Administrator rights.
This is so that the application you are opening is running with an access token of that of an
administrator.
To display to return the status of Workflow Manager 1.0 services in all of the Workflow Manager 1.0 farm’s hosts.
That is the Workflow Management Site (IIS) and Workflow Manager Backend Service.
PS > Get-WFFarmStatus
To display the configuration of the workflow farm.
PS > Get-WFFarm

10. Validating Configuration
SharePoint Designer 2013 – Create a workflow and then Publish

11. Troubleshooting
• I have used Fiddler to observe the http calls from the browser and
SharePoint Designer. Sometimes you can see error messages and
stack traces in the http response body.
http://fiddler2.com/
• You can also refer to event logs via Event Viewer
http://msdn.microsoft.com/en-us/library/windowsazure/jj193526(v=azure.10).aspx

12. Tips
• Run as Administrator for running applications, even though logged in as a user part of Local
Administrator group
• PowerShell
• Web Platform Installer
• Apply fully qualified domain name (FQDN) in any aspect of configuration for URL and domain accounts.
Even though in the Workflow Configuration Wizard allows and states <domain><userID> format.
• In Production environment, communicate to Workflow Manager via HTTPS for secured communication.
• Apply SSL certificates
• Create and execute workflows with non sharepoint service and workflow manager accounts
• The Register-SPWorkflowService command is really registering at the web application level, even
though you can set a site collection url as the SPSite parameter.
Not reliable

13. Tips
• Workflow Resource Browser Tool
Allows you to browse the scope hierarchy of a Workflow Manager 1.0 installation, and view
information about activities, workflows and instances under the currently selected scope.
http://code.msdn.microsoft.com/windowsdesktop/Workflow-Resource-Browser-a67b1d27

14. MSDN Resources
Installing and Configuring Workflow Manager 1.0
http://msdn.microsoft.com/en-us/library/windowsazure/jj193478(v=azure.10).aspx
Workflow in SharePoint Server 2013 FAQ
http://social.technet.microsoft.com/wiki/contents/articles/16235.workflow-in-sharepoint-server-2013-faq.aspx
Workflow in SharePoint 2013
http://technet.microsoft.com/en-us/sharepoint/jj556245.aspx
Workflow Deployment PowerShell Commands
http://msdn.microsoft.com/en-us/library/windowsazure/jj193264(v=azure.10).aspx
Troubleshooting Workflow Manager 1.0
http://msdn.microsoft.com/en-us/library/windowsazure/jj193445(v=azure.10).aspx