Installing and configuring Granta MI

Install and configure the required Granta MI software on the first node in the cluster.

Prerequisites:
  • Review Software requirements to ensure all required software and databases have been installed and configured.
  • Ensure you have completed the necessary SQL Server setup. You will need to provide your SQL login details.
  • Ensure you have completed the necessary remote Elasticsearch instance setup. You will need to specify the URL and API key for your remote Elasticsearch instance.
  • MI Selection Service must use the same port number on all cluster nodes.

Complete the steps documented in 'Setting up your Granta MI server' in the Granta MI installation documentation to install and configure Granta MI on the first node of your cluster, and then verify the installation.

  1. Do not install MI Search Server.
    Database indexing for the cluster will be provided by the remote Elasticsearch instance you configured previously, and so MI Search Server should not be installed on any of the cluster nodes.
  2. When the MI Server installer detects that MI Search Server has not been installed, it will prompt you to enter the connection details for the remote Elasticsearch instance that will provide MI search and indexing features in the cluster:
    1. Select Other Elasticsearch.
    2. Enter the URL of your remote Elasticsearch instance.
      https://your.esserver.name:9200/
      If you have an Elasticsearch cluster, you can enter multiple URLs here.
    3. Paste in the Elasticsearch API Key you generated earlier.
      See Generating an Elasticsearch API key for Granta MI.
    4. Click Next.
  3. Do not install MI Material Calibration.
    This should be installed on a separate 'compute' server, and not on a Granta MI application server. See Setting up MI Material Calibration and MI Machine Learning servers.
  4. To use MI User Manager or OpenID Connect protocol (OIDC) instead of Windows Authentication for user authentication in your Granta MI cluster, follow the steps below.
    1. Enable User Manager or OIDC authentication on this node following the procedure documented in Granta MI Administration and Configuration.
    2. Open the MI Settings application, and edit the following settings to replace the machine name part of the URL with a [NODENAME] or [NODEFQDN] placeholder, where NODENAME resolves to the machine name, and NODEFQDN resolves to the Fully-Qualified Domain Name. If using HTTPS, you need to use whichever matches your HTTPS certificate.
      • On the Application Integration settings page, edit the MI User Manager server access URL field to replace the domain name part of the URL with [NODENAME] or [NODEFQDN]. For example: https://[NODEFDQN]:9000/api
      • On the Service Layer settings page, edit the Service Layer Proxy service configuration field to replace the default [NODENAME] placeholder text in the User Manager backendUrl property with [NODEFQDN] to match the name specified in your HTTPS certificate. You may find that clicking Format JSON below the edit panel makes the JSON easier to review and edit here.

      • On the Advanced settings page, edit the Authentication.Parameter.ServiceUrl field to replace the node name in the URL with [NODEFQDN]. For example: https://[NODEFQDN]:9000/api.
If you intend to enable log aggregation in the cluster, you will also need to install MI Log Collector on this node. See Installing and configuring MI Log File Collector (Filebeat).