Factorysoft Opc - Client Install

Technical Implementation Guide: FactorySoft OPC Client FactorySoft provides specialized developer toolkits designed to build custom OPC (Open Platform Communications) client applications. These toolkits streamline the complex COM/DCOM and OPC specifications, allowing developers to integrate industrial data into Windows-based environments. 1. Pre-Installation Requirements

Before installing or developing with a FactorySoft toolkit, ensure your environment meets the following criteria: Operating System:

Windows versions ranging from Windows 2000/XP to modern Windows Server (2016–2025) and 64-bit client OS for testing. Frameworks: Many FactorySoft components require the .NET Framework

(typically version 1.1, 2.0, or 3.5 depending on the specific toolkit age). Permissions: factorysoft opc client install

Administrative rights are required to register COM/DCOM components and install software services. Firewall ports must be open for OPC communication (e.g., TCP port 4840 for OPC UA or standard RPC ports for DCOM). 2. Installation Procedure

Installation typically follows a standard Windows setup process: Launch Setup: Run the provided installer (e.g., OPC Client.exe ) from your source media or download. Language & Path Selection:

Choose your preferred language and destination directory (default is often C:\JXServer or similar). Feature Selection: Select the specific components needed, such as the OPC DA Client Toolkit for real-time data or the OPC A&E Client Toolkit for alarms and events. Registration: Part 6: Automating Your FactorySoft OPC Client Install

The installer will automatically register the necessary COM/DCOM DLLs required for the toolkit to interact with external OPC servers. 3. Toolkit Capabilities & Configuration

Once installed, the toolkit provides a developer-friendly API to perform the following: Maxum OPC Server User Manual

Part 6: Automating Your FactorySoft OPC Client Install (For System Integrators)

If you deploy the client across 10+ workstations, use silent installation parameters: Then, push a PowerShell script to set DCOM

msiexec /i "FactorySoft_OPC_Client_v5.2.8.msi" /quiet /qn /norestart 
  ADDLOCAL=ALL 
  REGISTER_COM_SERVER=0 
  ALLOW_DCOM_CONFIG=1

Then, push a PowerShell script to set DCOM permissions:

# PowerShell snippet for DCOM config (run as Admin)
$appID = "B2C5D6A3-8F1E-4B9A-9C2D-3E4F5A6B7C8D" # Replace with actual FactorySoft AppID
Grant-DCOMAccess -AppId $appID -Account "DOMAIN\OPCClientSvc" -Permissions Launch,Activation

Always test silently on a staging VM first.

Step 1: Prepare the Environment

  1. Log in as a user with Local Administrator rights.
  2. Disable UAC (User Account Control) temporarily on Windows Vista/7/10. UAC blocks the COM registration scripts that run at the end of the install.
  3. If you are on Windows 7 or newer, locate the setup file (setup.exe), right-click, go to Properties > Compatibility, and check "Run this program in compatibility mode for Windows XP (Service Pack 3)."

Example quick checklist

Step 2: Choose Installation Type