×

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

DTL Counters

You can use DTL counters in Workflow.

Counter Name	Description
DTL Pending Packets Acknowledged		Shows how many non-specific packet acknowledgements are in the queue. If this number starts increasing, it indicates that DTL is having difficulties processing.
DTL Received Packets Queued		Monitors the queue from the RxThread to PacketProcessThread. If you are generating many events with multiple clients, this counter should increment.
DTL Received Packets Dropped		DTL limits the size of the queue from the RxThread to the PacketProcessThread to a maximum of 1,000 (ReceiveQueueLimit) packets. If the RxThread gets a packet when the queue is full, the packet is dropped, and this counter increments.
DTL Send Packets Queued		Monitors the queue of packets to be sent, which is added to by the BuildPacketThread and emptied by the TxThread. Normally, this queue is not busy. It indicates that something is generating packets faster than they are being transmitted. If your network connection is slow, or is very busy and generating a high volume of events, this counter may increase.
DTL Record Rate Changed		Reports the number of change records per second coming into the DTL subsystem (typically from an event subsystem), which is the event producer side of the multi-server system. When events are generated, this rate counter moves.
DTL Change Records Queued		Monitors the queue of change records coming from the Events subsystem (and possibly others) that are emptied by the BuildPacketThread. Because the BuildPacketThread pauses to try to get multiple changes per packet, this counter should change when there are a high volume of events.
DTL Change Records Dropped		The queue of change records is limited to 1,000. If more change events come in than can fit in the queue, DTL starts dropping change records, and this counter increases. Typically, this counter does not move, but if the events are generated fast enough, it may move.