Skip to main content
OnCommand Workflow Automation 5.0
A newer release of this product is available.

Configure Workflow Automation with MSCS

Contributors
PDFs

After you install Workflow Automation (WFA) in Microsoft Cluster Server (MSCS), you must configure WFA for high availability in MSCS using configuration scripts.

What you'll need

You must have created a backup of WFA.

Steps

  1. Log in to the first node of the MSCS cluster, and perform the following steps:

    For…​ Do this…​

    Windows 2012

    1. From the Failover Cluster Manager, right-click Service Roles.

    2. Select Create Empty Service Role, and then rename the role to “WFA”.

    3. Add the IP address resource to the newly created “WFA” role:

      1. From the Failover Cluster Manager, right-click the newly created “WFA” role.

      2. Select Resource > More Resources > IP Address.

      3. Configure the cluster IP address.

    Windows 2008

    1. From the Failover Cluster Manager, right-click Services and applications.

    2. Click More Actions > Create Empty Service or Application, and rename the service to “WFA”.

    3. Add the IP address resource to the newly created “WFA” service:

      1. From the Failover Cluster Manager, right-click the newly created “WFA” service.

      2. Select Add a resource > More resources > Add IP Address.

      3. Configure the cluster IP address.

  2. At the command prompt, run the ha_setup.pl script to move the WFA data to the shared location and to configure WFA with MSCS for failover: perl ha_setup.pl --first [-t type_of_cluster_vcs] [-g cluster_group_name] [-i IP_address_resource_name] [-n cluster_name] [-k shared_disk_resource_name] [-f shared_drive_path]

    The script is available at WFA_install_location\WFA\bin\ha\.

    Example

    perl ha_setup.pl --first -t mscs -g WFA -i "Cluster IP Address" -n wfa_cluster -k "Cluster Disk 2" -f E:\

  3. Verify that the MSCS resources are created.

  4. Stop the WFA services from the Failover Cluster Manager:

    For…​

    Do this…​

    Windows 2012

    1. Select Service Roles, and then select the newly created “WFA” role.

    2. In the Resource pane, right-click NA_WFA_DB, and then select Take Offline.

    3. In the Resource pane, right-click NA_WFA_SRV, and then select Take Offline.

    Windows 2008

    1. Select Services and applications, and then select the newly created “WFA” service.

    2. In the Other Resources pane, right-click NA_WFA_DB, and then select Take this resource offline.

    3. In the Other Resources pane, right-click NA_WFA_SRV, and then select Take this resource offline.

    The WFA database service and the WFA server service must be taken offline. The WFA services must not be stopped from the Windows services.

  5. Manually move the WFA resources to the secondary node.

  6. Verify that the shared disk is accessible from the second node.

  7. At the command prompt, run the ha_setup.pl script on the secondary node of the cluster to configure WFA for using the data from the shared location: perl ha_setup.pl --join [-t type_of_cluster_mscs] [-f shared_drive_path]

    The ha_setup.pl script is available at WFA_install_location\WFA\bin\ha\.

    Example

    perl ha_setup.pl --join -t mscs -f E:\

  8. From the Failover Cluster Manager, bring the WFA resources online:

    For…​ Do this…​

    Windows 2012

    1. Right-click the newly created “WFA” role, and then select Start Role. The role must be in the Running status, and the individual resources must be in the Online state.

    Windows 2008

    1. Right-click the newly created “WFA” service, and then select Bring this service or application online. The service must be in the Running status, and the individual resources must be in the Online state.

  9. Manually switch to the second node of the MSCS cluster.

  10. Verify that the WFA services start properly on the second node of the cluster.