Configure the MES middleware proxy AIM client registration

Use the AVEVA Identity Manager (AIM) tab to register the MES middleware proxy with AIM in order to secure the client and server communication using message authentication.

The MES middleware proxy must be registered with AIM.

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

When you configure the MES middleware proxy component:

• The MES middleware proxy is registered with AIM. Two clients are registered:

  • A synchronous and event notification client with a token life span of one day.

  • An asynchronous message client with a token life span of five days.

    Note: Neither life span value is configurable.

• The client secrets used for client registration in AIM are stored in the AVEVA Data Store (ADS).

To configure the Middleware Proxy AIM settings

1. In the AIM Host field, enter the fully qualified domain name of the node on which the Identity Manager is running.

   If the SMS value is configured, this field defaults to the SMS value. If the SMS value is not configured, the field defaults to the local node.

2. In the AIM HTTPS Port field, enter the HTTPS port number for the Identity Manager.

   If the SMS value is configured, this field defaults to the SMS value. If the SMS value is not configured, it defaults to 443.

   The Identity Manager port number must match the System Management Server's HTTPS port number, which can be viewed or set on the System Management Server component's Advanced Configuration settings. For more information, see System Management Server and local node common platform HTTPS port settings.

3. Enter the User Name and Password of an administrative account on the node on which AIM is running.

   If user accounts are managed with Windows Active Directory, the User Name must include the domain and user name in the format domain\username.