• The MES Setup tool allows you to select role-based groups of products and components for installation on a node. The Setup tool also allows you to customize the installation by selecting specific components.
• Role-based installation provides a combination of MES features specific to a node's role in a multi -node system. For example, if the node is going to be located on the production floor for use only by production operators, then only the Operator role's set of components needs to be installed.
• Note that more than one role can be selected for installation on a node, to support nodes that will be running a number of MES clients or services. Although the MES installation software includes a limited version of Intelligence, none of the MES roles will install Intelligence. During the installation, you have to select the customize option to manually select the Intelligence components.

1.    Database Server with MES

Select this role to install the MES database on the node. This role includes the following components:

• • MES Database
  • MES Service
  • MES Middleware
  • MES Middleware Proxy

To optimize performance on a system that will also be running Intelligence, the MES database should be installed on a separate server from the Intelligence database.

2.    Operator Client

Select this role if production operators, application objects, or third-party applications will be using the node to record production, utilization, or quality management data.

This role includes the following components:

• • MES Operator
  • MES .NET controls
  • MES Development Library (API DLLs)
  • MES Middleware Proxy

3.    Web Portal

Select this role to install the MES Web Portal web application on the node. This role includes the following components:

• • MES Web Portal
  • MES Middleware Proxy

4.    Report Server

Select this role to install support for deploying MES Intelligence Reports. This role includes the following component:

• • MES Intelligence Reports

If you want to deploy MES Intelligence Reports but Intelligence has not been installed on the network, you can customize the installation to include the Intelligence Server, Intelligence Model B uilder, and Intelligence Data Adapters.

To distribute the client load, a system can have multiple MES Middleware components installed. All five-equipment licenses include two MES Middleware components. All larger equipment licenses include six MES Middleware components. Additional MES Middleware components can be purchased separately. Dedicated MES Middleware components are recommended for the MES Service, enterprise integration, MES Application object/scripting servers, Skelta BPM .NET workflow integration, and nodes making heavy use of the MES API through custom applications.

6.    Configuration Client

Select this role if MES administrators, supervisors, or developers will be performing configuration or supervisory tasks from the node.

This role includes the following components:

• • MES Client
  • MES Supervisor
  • MES Data Editor
  • MES Middleware Proxy

7.    ArchestrA Development

Select this role if MES devel opers will be using ArchestrA and MES application objects to develop or run MES applications on the node.

This role includes the following components:

• • Application Objects (OCO, SRO, UCO)
  • MES .NET Controls
  • MES Entity Model Builder
  • MES Development Library (API DLLs)
  • MES Middleware Proxy

8.    .NET Development

Select this role if MES developers will be using .NET Controls to develop or run custom MES applications on the node.

This role includes the following components:

• • MES .NET Controls
  • MES Development Library (API DLLs)
  • MES Middleware Proxy