×

Supercharge your Proficy solution! Download a free trial of Proficy Operations Hub, CSense analytics, and more. Explore our Proficy 2024 releases!

Home
Get Started
Get Started Guide
Server Clustering Implementation
Clustering Tips
Use the clustering tips to ensure your failover cluster runs smoothly.

Workflow IPI
Get Started
- Get Started Guide
  - Installation Requirements
  - Pre-Installation Consideration
  - Installation Procedures
  - Server Clustering Implementation
    - Supported and Validated Cluster Configurations
      Before you begin installing Workflow, it is important to determine your architecture so you can know where to install your servers.
    - Microsoft Failover Cluster Manager for Windows Servers
      The Microsoft Failover Cluster Manager is used to create the cluster and to add nodes to the cluster.
    - Install Microsoft Failover Cluster Manager
      The Microsoft Failover Cluster Manager must be installed in order to configure your failover cluster.
    - Configure the Microsoft Failover Cluster Manager
      The Microsoft Failover Cluster Manager is used to create a new DNS entry to manage your server cluster.
    - Configure quorum options for a cluster
      Although this application does not require a disk for clustering, it is recommended that you configure either a file share witness or a disk witness.
    - Configure the primary cluster server
      After installing the application server on your primary server machine, you must configure the machine as the primary cluster server to begin the clustering process.
    - Configure the failover cluster server
      After configuring the primary application server cluster server and exporting the server security certificates, you can configure the failover cluster server.
    - Configure a local client for a cluster node (32-bit)
      If you want to run a cluster node on a 32-bit system, follow this procedure.
    - Configure a local client for a cluster node (64-bit)
      If you want to run a cluster node on a 64-bit system, follow this procedure.
    - Server Clustering and One-Click Deployment
      If you have implemented a server cluster environment and you want to use one-click deployment in that environment, additional configuration is required to set up the one-click deployment.
    - Clustering Tips
      Use the clustering tips to ensure your failover cluster runs smoothly.
  - Deploy the Web Task List
  - Log On Overview
  - Post-Installation Configuration
  - Upgrade Workflow
  - Install a Reporting Database
  - Terminal Server
  - ActiveX Task Controls
  - Workflow Task Client
  - Installation Security
  - Troubleshooting Workflow Issues
    This topic describes how to troubleshoot issues that you encounter when working with Workflow.
Tutorials
Orientation
Configure Your Environment
Security
Resource Information and Configuration
Data Administration
Forms and User Displays
Building and Configuring Workflows
eSOP
ActiveX Task Controls
Service Interfaces
Operator Task List in the Workflow Client
Best Practices

Clustering Tips

Use the clustering tips to ensure your failover cluster runs smoothly.

Security Certificates

When setting up a clustered environment, you must regenerate and export Proficy security certificates as part of configuring the primary cluster server, and then import the certificates when configuring the failover cluster server. Symptoms of incorrect security certificate configuration include the inability to create or display Silverlight forms and the Web Task List. For more information on setting up security certificates for a clustered environment, see Configure the Primary Server Cluster, Configure the Failover Cluster Server, and Modify Security Certificates.

Proficy Server Service is Marked for Deletion

Occasionally, after a server configuration, the Proficy Server service is marked for deletion. You can restore the service by running the Configure Server tool again.

Clients on Clustered Proficy Servers

Clients that are installed with clustered Proficy servers will work only if the server is the primary server.

Note: If you have a cluster with multiple nodes, the cluster must be pointing to the client name, and the server that each node is running on must state the role name for the cluster. For more information, see Configure a local client for a cluster node (32-bit) and Configure a local client for a cluster node (64-bit).

Running a Clustered Multi-server Environment

When running with both a clustered application server and clustered Workflow/User servers, you must restart the primary server and then, after a few minutes, restart the primary Workflow/User server. This can be performed using the Microsoft Failover Cluster Manager by taking the servers offline, and then putting them back online.