Example server node configurations

The following diagrams show examples of some simple server node configurations. The server/node configurations required for your solution depend on your system performance requirements.

• For additional information about Work Tasks node architectures, see the topics about Architecture and Edition Installation Scenarios in the Work Tasks Administration Guide.

• For additional information about MES node architectures, see the MES Deployment Guide.

Note the following about node configurations:

• No AVEVA software is required on client nodes (unless the client is an HMI, such as an InTouch application). Client node users simply use a web browser to point to the Work Tasks Repository URL.

• In many cases, the servers need to connect to a domain controller that must be on a separate node from the servers.

• Additional servers might be required for scalability of System Platform and Work Tasks. See the System Platform and Work Tasks user documentation for information about their configuration requirements with scalable architecture.

• For larger systems, contact AVEVA or an AVEVA authorized partner for more details.

  Note: The MES Middleware, which includes the MES Web API, must be installed on the same node as the Work Tasks software.

One-node system: MES, BI Gateway, and automation servers on the same node

A one-node system is typically used for demonstration or proof-of-concept solutions.

Two-node system: MES and BI Gateway servers on one node, automation server on another

Three-node system: MES, BI Gateway, and automation servers on separate nodes