Limitations in Work Group Environment
- Last UpdatedOct 01, 2024
- 2 minute read
AVEVA Batch management in a work group environment presents several limitations that may impact the efficiency and effectiveness of operations. Understanding these limitations is crucial for setting realistic expectations and ensuring that system performance meets operational needs.
Below are some key limitations typically encountered in the distributed setup:
Environment
-
Node 1: AVEVA System Platform (IDE + Bootstrap) + AVEVA Batch Management Server
-
Node 2: AVEVA System Platform (IDE + Bootstrap + GR + InTouch) + AVEVA Batch Management Clients (Development + Runtime)
-
Node 3: AVEVA Batch Management (History + Reports)
Limitations
-
Deployment Issue on GR Node:
The remote Windows platform on the GR node fails to deploy.
Error:
This prevents the IBMX service from starting on the batch server node, ultimately blocking batch execution with IBMX.
-
Development Client Configuration Failure:
The development client cannot be configured because users on the development client node lack permissions to access the Batch Server’s shared folder.
Error:
-
History Server Configuration Failure:
Unable to configure the History Server when pointing to a remote SQL server.
Error:
This occurs because the local user of the remote node cannot be added to SQL Server, a known limitation of SQL.
-
SMS Configuration Limitation:
SMS cannot be configured by pointing to a remote SMS. Each node must act as a separate SMS to generate the required certificates for configuring AVEVA Batch Management features.