Test and Save the database connection settings

When you have finished specifying the MES middleware and database connection settings on the Security, Production, AVEVA Identity Manager, and optionally the Restore and Staging tabs, you are ready to test and save them.

Test and save the database connection settings

• Click the Configure button.

During the configuration, the following occurs:

• If the Set the minimal SQL permissions option on the Security tab was selected, the minimal SQL permissions to the databases for the MES middleware service Windows user account are granted. This is performed regardless of whether the connection string tests are successful.

• The local Trusted Root folder is checked to see if the SSL certificate from the Identity Manager already exists.

• The MES middleware client registration with the Identity Manager is performed.

• The database connection strings are tested and saved.

• MES middleware custom performance monitor counters are installed. For more information about these counters, see Understand the MES middleware performance counters.

• MES middleware service user account access to the Archive root directory is set, to support MES database Archive/Purge/Restore operations.

• The Archive root directory is specified by the Archive root directory path system parameter, which can be modified in MES Client. The default path is [MES application folder path]\MES\Archives.

• The MES Async Private Message Queue—mesasyncqueue—is created, with the following permission settings:

  • Everyone: Send Message

  • Anonymous Logon: Send Message

  • MES Middleware Service user account: Receive Message and Peek Message

  • Users in the local Administrators group: Full control

• The MES middleware service user account access to the HTTPS port is set so that the MES middleware can open a secured HTTPS connection on this port.

• A Windows inbound firewall rule exception for the configured TCP port is added so that the middleware proxy on a client node can connect to the middleware without having to disable the Windows Firewall on the MES middleware node. TCP information required to add the rule exception is read from the middleware configuration file. Note that changes to the middleware configuration file should only be performed using the Middleware Configuration Editor.

• The MES middleware is started.