Installing Azure Workflow Server is very much like installing SharePoint:
1. Install the Windows Azure Workflow Server software.
2. Configure a workflow farm.
3. Join the SharePoint farm to the workflow farm, which enables the new workflow capability for SharePoint 2013.
The following sections describe how to use the
Web Platform Installer (Web PI) to install the necessary software
requirements, how to use the configuration wizard to configure the
farm, and how to use PowerShell to configure SharePoint to use the
Workflow Server.
1. Hardware and Software Requirements
To install the Workflow Server, you should meet the same requirements
specified for SharePoint 2013,
but many of these requirements are already included in the previous
reference. Administrators should check these references, as they will
likely be updated as experience with SharePoint 2013 increases.
Supported Operating Systems
The following operating systems are supported:
- 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.
The following editions for these operating systems are supported:
- Standard
- Enterprise
- Core
- Datacenter
SQL Server Requirements
The following SQL Server releases are recommended:
- SQL Server 2012
- SQL Server 2008 R2 SP1
NOTE SQL
Server can be installed on the same physical machine with Workflow 1.0
and Service Bus, or on a different one. The Service Bus databases can
reside on multiple machines as well. This flexibility is most valuable
for your development environment, minimizing the number of servers or
virtual machines you need.
Following are the requirements for SQL Server,
which serves as the repository for workflow configuration and runtime
information:
- TCP/IP, shared memory, and named pipes must be enabled.
- Ports 1443, 12290, and 12291 on the firewall must be open to inbound and outbound communications.
- 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 also carry the 16-character restriction.
- The SQL Server Browser service should be running on the SQL Server.
- Your workflow service account, domain\sp_workflow, is a registered login for your SQL Server instance.
Service Account Requirements
This account needs to be part of the
local domain, but only as a standard user, and it does not require
special domain privileges (such as a domain administrator). The service
account is used for the following Windows services:
- Service Bus Gateway
- Service Bus Message Broker
- Windows Fabric Host Service
- Workflow Service Backend
WARNING It
is permissible to run Azure Workflow Server under a SharePoint farm
account in development environments, but this isn’t considered a best
practice. For production environments, to abide by the principle of
least privilege, it is recommended that you run Azure Workflow Server
under a dedicated service account.
2. Workflow Manager Install
You can install Workflow Manager using
the Web Platform Installer (Web PI). The Web PI automatically checks
for prerequisites before it installs workflow manager, and it will
automatically download and install any prerequisites that it does not
find as long as you have Internet access on the installation server.
You do not need to install any prerequisites separately. You should
download the Workflow Manager Installer, which includes the Web PI,
from the following URL:
http://go.microsoft.com/fwlink/?LinkID=252092
The installer requires Internet access, and it
will download and install the necessary prerequisite components, which
include the following:
After installation is complete, the Configuration
Wizard will be launched. You can choose to perform the configuration
later by opening the Configuration Wizard from the Start menu (select
Start ⇒ All Programs ⇒ Workflow Manager 1.0 ⇒ Workflow Manager
Configuration). In the next section, you will walk through the complete
installation and configuration of the Workflow Manager.
3. Step-by-Step Install
You have learned about the various
installation and configuration options for adding an Azure Workflow
Server to your SharePoint 2013 farm. This section now brings it all
together with step-by-step installation instructions.
The Environment
This example uses two servers. One
server will be an Active Directory domain controller, and the other
server will be the SharePoint 2013 server.
WARNING Installing
Windows Azure Workflow Server on a domain controller is not a supported
scenario for a production environment. Although it is possible to
install Workflow Manager on a domain controller, it is not recommended.
For a SharePoint 2013 production farm with workflow, you need a minimum
of two machines.
ContosoDC
The first server, named ContosoDC, is
running Windows Server 2008 R2 (64-bit) with all the latest Windows
Updates installed. It has been configured as an Active Directory domain
controller for the Contoso domain.
NOTE If
you are building a development and/or test farm and are
hardware/resource constrained, you can use Windows Server Core for
Windows Server 2008 R2. Server Core has lower memory requirements.
ContosoServer
The second server, named ContosoServer,
is also running Windows Server 2008 R2 (64-bit) with all the latest
Windows Updates installed. A supported SQL Server instance has been
installed and is hosting the SharePoint 2013 farm. In addition,
ContosoServer is a member of the Contoso domain.
