Configuring MES Middleware Communication with MES Databases

The DB/MW Communication component is used to create the database connection strings that the MES middleware service uses to access MES databases. In addition:

• It is used to create a firewall inbound rule exception to allow the MES middleware proxies to communicate securely with the MES middleware.

• It is used to register the MES middleware with the AVEVA Identity Manager (AIM) for the MES Web API authentication.

• It can also be used to assign the minimal SQL permissions required to access and query an MES database to the MES middleware service's Windows user account. Otherwise, the SQL permissions have to be assigned manually.

If the MES middleware and the MES database are on separate nodes, the Microsoft Distributed Transaction Coordinator service (MSDTC) must be added to the Windows Firewall exception list on both nodes to allow them to communicate.

The Security tab of the DB/MW Communication component is shown below.

The Security, AVEVA Identity Manager, and Production tabs, and optionally the Restore tab if the Enable Restore Database option is selected, need to be completed before clicking the Configure button to configure the component. The order in which they are completed does not matter. The next few topics describe the Production and Restore tabs first, and then the Security and AVEVA Identity Manager tabs.

• Database connection string information is entered on the Production and Restore tabs.

• The MES middleware service's Windows user account is shown on the Security tab. If this user account will be used to access the MES database using Windows integrated security, then the option to automatically create a SQL Server login for that account is also provided on this tab.

• The AVEVA Identity Manager client registration information for the MES middleware on this node is entered on the AVEVA Identity Manager tab.