About Me

Having 12 years experience in Microsoft technologies.Since more than 7 years working in SharePoint technologies. Expert in providing consultation for SharePoint projects. Hands on with development and administration.

Thursday, 16 May 2013

Installing Workflow Manager farm SP 2013

Before installing a Workflow Manager farm, you must have the following:
1. Access to an SQL Server on which the Workflow Manager databases can be created, such as an instance of SQL Server 2008 R2 SP1, SQL Server Express 2008 R2 SP1, or SQL Server 2012.
2. Relevant port numbers. The default ports numbers are 12290 and 12291.

3. A mixed IPv4/IPv6 environment. The Workflow Manager installer available for SharePoint 2013 only works with IPv4 and not in pure IPv6 environments.
4. A Workflow Manager installer that matches the build number of SharePoint 2013 with which you want to use it.

     Imp - The Workflow Manager installer uses the Web Platform Installer (Web PI) to initiate the     installation steps. You can find the Workflow Manager at go.microsoft.com/fwlink/?LinkID=252092.

   You can find the Workflow Manager Client, which is only needed on SharePoint servers that respond to web requests and do not have the Workflow Manager installed, at go.microsoft.com/fwlink/?LinkID=258749.

5. Access to the Internet for the computers on which you are installing Workflow Manager;otherwise, you need to download and install the prerequisites prior to running the Workflow Manager installer.
6. A service account known as the RunAs account, that must have read/write access to the SQL Server. An account to install and configure the Workflow Manager added to the local administrators group on each server that will be a node in the Workflow Manager farm.

7. When you install the Workflow Manager on the first server, you create a workflow farm. You are asked which SQL server instance to create the farm databases, the service account, and to provide a
Certification Generation Key, which has a similar function to the passphrase in a SharePoint farm.
You will need this key when you join subsequent servers to the workflow farm. Each server within a workflow farm is known as a workflow node.

8. When adding more than one server to a workflow farm, you need to edit the Domain Name System (DNS) and install load balancers so that any workflow node can respond to a request from your
SharePoint farm.

9. After the workflow farm is created, you then need to register the farm with your SharePoint farm by running a Windows PowerShell cmdlet similar to the following on one of the servers in your
SharePoint farm:

Register-SPWorkflowService –SPSite http://xxxxxxx.com –WorkflowHostUri http:/xxxxxx:12291 -AllowOauthHttp

After this command is successfully executed, the Workflow Service Application Proxy will be started in the SharePoint farm

Note -  If the SharePoint server on which you run this command is not a workflow node in your workflow farm, you will need to install the client version of Workflow Manager to run
the command successfully. The –AllOAuthHttp is only needed if you are using the HTTP protocol to communicate between the two farms. In a production environment, you should
use HTTPS.

1 comment:

  1. Can you please elaborate more on point #8?
    "When adding more than one server to a workflow farm, you need to edit the Domain Name System (DNS) and install load balancers so that any workflow node can respond to a request from your sharePoint"

    Do we have to create a DNS and put that DNS name into host header of workflow manager website in IIS and then when making calls we use that DNS?
    Please confirm.