Release Notes for Laserfiche Distributed Computing Cluster 9.1 Preview.

February 18, 2014 | KB: 1013427
Distributed Computing Cluster 9.1

Summary

Laserfiche Distributed Computing Cluster (DCC) is a Windows service installed on one or more machines that performs processing work for Laserfiche applications. DCC 9.1 Preview performs OCR-processing work and can connect to Workflow 9.1 and Web Access 9.1 to allow these applications to enable OCR-related features (the Schedule OCR activity in Workflow and the Generate Searchable Text feature in Web Access).

System Requirements

  • Processor (CPU): 2.93 GHz or faster multi-core processor
  • Memory: 1 GB RAM (2 GB recommended) per processor core
  • Operating system: Windows Server 2008, Windows Server 2008R2, Windows Server 2012, Windows Vista, Windows 7, Windows 8.

    • Note: The number of concurrent tasks a DCC worker can perform is usually limited by the number of processor cores on the machine hosting it. To increase a worker's performance, install it on a machine with a multi-core processor.

    Note: When you install the Laserfiche Distributed Computing Cluster Service, PowerShell modules for administering the service are also installed. In order for these modules to be installed, the machine must have PowerShell 2.0 or higher installed. Windows Server 2008 and Windows Vista do not come with PowerShell 2.0.

Software Requirements

  • Laserfiche Rio or Avante
  • Laserfiche Server 9.1+
  • Web Administration Console 9.1.1+
  • Workflow 9.1+
  • Web Access 9.1+

Note: If you are using License Manager 8.3.1, please install License Manager 8.3.1 Hotfix 1013437 to use Distributed Computing Cluster.

Known Issues

  • When the number of concurrent tasks a worker machine can perform is set above one, a rare issue that causes tasks to take longer than anticipated to complete can occur. (111314)
  • On Windows Server 2008 machines, Distributed Computing Cluster services running as the Local System account cannot authenticate to other machines using Windows Authentication. To fix this issue, run the services as a domain user that has been added to the Worker Distributed Computing Cluster authorization group in the Web Administration Console.