×

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

Workflow IPI
Get Started
- Get Started Guide
  - Installation Requirements
  - Pre-Installation Consideration
    - Architecture Considerations
      If you are installing an application server or extension server (that is, Workflow or User) on a 64-bit computer, you can configure the server for either 32-bit or 64-bit operation.
    - Prerequisites for Windows 2012 R2 Installations
    - Configure Windows Authentication for Workflow
      You can configure Workflow to use Windows authentication to connect to a remote SQL Server instance.
    - Windows Services for Workflow
      There are several Windows services that must be running in order for Workflow to function properly.
    - Security Certificates
    - Firewall Ports
      During server installations, the installation setup detects whether there is a firewall on the computer. You must either disable the firewall or configure it to allow communication with remote clients.
    - Database Backup and Restore
      Workflow utilizes SQL Server to store information. In order to ensure that the integrity of the information is maintained, it is important to back up your database on a regular basis.
    - Multiple Servers
      Workflow provides the ability to install across multiple servers, each of which hosts a set of services. A multi-server environment is transparent and appears to be a single server to remote clients.
    - Server Clustering and Failover
      Workflow provides the ability to implement Microsoft^® Windows Clustering, which allows you to configure your server environment to be fault tolerant.
    - Enable Connection between Workflow and SQL Server
      In order for Workflow to connect to any edition of Microsoft^® SQL Server 2012 or later, you must configure SQL Server to enable the db_owner role on the SOADB database for the applicable login account.
    - License Management
      The GE License Client provides a single, easy-to-use tool to both view and manage online software licensing.
    - Performance Counters
      - Performance Counters
        Windows performance counters are exposed as objects with counters. The counters are grouped into two categories: DTL and Events.
      - DTL Counters
        You can use DTL counters in Workflow.
      - Events Counters
        You can use events counters in Workflow.
      - Log performance counters
        Using this procedure, you can write (increment/decrement) to the performance counter.
      - Add or remove performance counters
        Using this procedure, you can manually add performance counters to your system, or remove them. You must have administrative privileges in order to perform this action.
      - View performance counters
        You can view performance counters using the Microsoft Windows Reliability and Performance Monitor application.
  - Installation Procedures
  - Server Clustering Implementation
  - 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

Events Counters

You can use events counters in Workflow.

Counter Name	Description
Events Queued Messages to Subscribers		Monitors the queue in the events subsystem for the subscribers. Typically, a high volume of events cause this rate counter to increment. If there are `N` subscribers to a given event, there will be `N` Events Queued Messages to Subscribers for each event generated.
Events DTL Subscriptions		Records the number of DTL points being subscribed to. The event subsystem re-uses DTL subscriptions so that multiple event clients requesting the same DTL point create only one subscription. Thus, if there are three WorkflowClients subscribing to the WorkflowTaskInstanceEvent, there should be one Events DTL Subscription and three Events Remote Subscriptions.
Events Remote Subscriptions		Records the number of subscribers to events on another server (such as those requiring DTL subscription). The event subsystem re-uses DTL subscriptions so that multiple event clients requesting the same DTL point create only one subscription. Thus, if there are three WorkflowClients subscribing to the WorkflowTaskInstanceEvent, there should be one Events DTL Subscription and three Events Remote Subscriptions.
Events DTL Change Rate		Reports the number of events per second being fed to the event subsystem from DTL, which is the subscriber side of the multi-server system. When events are generated, this rate counter changes. The DTL Change Record Rate and the Events DTL Change Rate represent the input side and output side, respectively, of the DTL link for events and, in a stable system, should be the same value (with some room for movement).
Events Messages to Subscribers Rate		Reports the number of events per second being sent to subscribers. In a stable system, if there are `N` subscribers to a given event, the Events Messages to Subscribers Rate will be `N` times the Events DTL Change Rate (assuming only that event is being generated). If the Events Messages to Subscribers Rate is less then `N` times the Events DTL Change Rate, the Events Queued Messages to Subscribers should increase.