Add-WFHost

Updated: August 31, 2012

[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

Add-WFHost

You can use this cmdlet to add this computer to the workflow farm. Workflow Manager 1.0 must already be installed on the computer.

Syntax

Parameter Set: Default
Add-WFHost -CertificateAutoGenerationKey <SecureString> -RunAsPassword <SecureString> -WFFarmDBConnectionString <String> [-EnableFirewallRules <Boolean> ] [-EnableHttpPort] [-SBClientConfiguration <String> ] [ <CommonParameters>]

Detailed Description

Run Add-WFHost to add a new host to the Workflows farm. When a Workflows farm is created it contains no hosts and cannot provide any service. Only when the first host is added to the farm it is considered to be running.

Parameters

-EnableFirewallRules<Boolean>

Use this parameter to specify the user acceptance for enabling firewall rules. The firewall rules must be enabled for the farm to work properly.

Aliases	none
Required?	false
Position?	named
Default Value	none
Accept Pipeline Input?	false
Accept Wildcard Characters?	false

-CertificateAutoGenerationKey<SecureString>

This passphrase is required for certificate auto generation. This is a mandatory parameter if you want certificates to be auto generated.

Aliases	none
Required?	true
Position?	named
Default Value	none
Accept Pipeline Input?	false
Accept Wildcard Characters?	false

-EnableHttpPort

Indicates whether to enable the HTTP port.

Aliases	none
Required?	false
Position?	named
Default Value	none
Accept Pipeline Input?	false
Accept Wildcard Characters?	false

-RunAsPassword<SecureString>

Specifies the password for the user account under which services are running on the farm.

If all the machines in a farm share the same service account and security policy requires the service account password to be changed at regular intervals, you must perform specific actions on each machine in the farm to be able to continue adding and removing nodes in the farm. See the section titled "Managing Farm Password Changes Using Cmdlets" for this procedure.

Aliases	none
Required?	true
Position?	named
Default Value	none
Accept Pipeline Input?	false
Accept Wildcard Characters?	false

-SBClientConfiguration<String>

The Service Bus client configuration.

Aliases	none
Required?	false
Position?	named
Default Value	none
Accept Pipeline Input?	false
Accept Wildcard Characters?	false

-WFFarmDBConnectionString<String>

Specifies the connection string for the SQL Server instance being added as the farm management database.

Aliases	none
Required?	true
Position?	named
Default Value	none
Accept Pipeline Input?	false
Accept Wildcard Characters?	false

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see about_CommonParameters

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

Outputs

The output type is the type of the objects that the cmdlet emits.

Examples

Example 1

Add this computer to the workflow farm.

PS C:\> $CertKey=convertto-securestring 'CertificatePassword' -asplaintext -force;
$RunAsPassword=convertto-securestring 'RunAsPassword' -asplaintext -force;
$config = Get-SBClientConfiguration -NameSpaces 'SBNamspace';
Add-WFHost -WFFarmDBConnectionString 'Data Source=localhost;Initial Catalog=WFManagementDB;Integrated Security=True' -SBClientConfiguration $config -EnableFirewallRules $True -RunAsPassword $RunAsPassword -CertificateAutoGenerationKey $CertKey -verbose