Configure MES middleware communication with the MES database

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.

  Note: The primary System Management Server (SMS) must be active when configuring AIM for the MES middleware.

• 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.

  Important: If you update the MES Middleware Service HTTP Port number, you must reconfigure the DB/MW Communication component. The Configurator's component status may not indicate that reconfiguration is required. Regardless of the status, always perform the reconfiguration. For more information about updating the middleware service settings, refer to the MES Middleware and Cloud Integration documentation.

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, AVEVA Identity Manager, and Production tabs, and optionally the Restore tab if the Enable Restore Database option is selected, need to be completed to successfully configure the component. The order in which they are completed does not matter.

Configure the MES DB/MW Communication component

1. Complete each of the following:

   • Configure the database connection string information on the Production and Restore tabs.

   • Configure the MES middleware service's Windows user account 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.

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

2. Select Configure.