Integrating Additional SOTI MobiControl Instances

About this task

This section describes the following topics related to integrating SOTI XSight with additional SOTI MobiControl instances.
Note: Additional SOTI MobiControl instances are supported in SOTI MobiControl version 15.4 and later.

Enabling the SOTI XSight Login Page

Procedure

  1. Login to SOTI XSight web console.
  2. Select the main menu from within the SOTI XSight web console.
  3. Select Settings > Integration > MobiControl Integration.
  4. Toggle Enable to support additional MobiControl Instances on.

    Enable support for additional SOTI MobiControl instances

  5. Select to the right of XSight Management Server Logon configuration.
  6. Add the XMS domain name under Management Server.
    Note: This part is full/partial domain name of the XMS address for accessing the web console.
  7. Set the Login Mode to XSight Login .

    Set the login mode to SOTI XSight Login

    Note: Select XSight Login for legacy setups, to display the legacy (race car) login page .
    Note: If the domain name does not work, put an asterisk before the domain address.
  8. Select Save.
  9. Select Ok.

    Restart all XMS instances

    Note: If SOTI XSight has more than one XMS instance, you must restart XMS on all XMS instances.
  10. Re-login to SOTI XSight. The SOTI XSight Native Login page displays.

Adding a Non-Primary SOTI MobiControl Instance

Procedure

  1. Select to the right of Other Instances.

    Adding a new other instance

  2. Enter the following information in the Add MobiControl panel.
    Instance details
    Table 1. Instance Details
    Setting Value
    Name Enter the name of the non-primary instance to add. The name is reflected on the device search points throughout SOTI XSight (Incident Management, Chat Container and Operational Intelligence).
    Access URL The URL of the non-primary SOTI MobiControl.
    Note: For SOTI Identity, /mobicontrol in the URL should be in lowercase as SOTI Identity is case sensitive.
    Use SOTI Identity for user authentication Toggle off
    Configure credentials
    Table 2. Configure Credentials
    Setting Value
    SOTI MobiControl Database Server The database server name of the non-primary SOTI MobiControl instance. The SQL instance which hosts the SOTI XSight database must be able to connect to the SQL Server (ports) instance which hosts the secondary SOTI MobiControl database.
    SOTI MobiControl Database Name The name of the non-primary SOTI MobiControl database.

    For example: MobiControlDB
    Username The SQL Server username of the user that has full privileges.
    Password The SQL Server password of the user that has full privileges.
  3. Select Save.
  4. Follow the instructions in the Add MobiControl prompt. Complete the following:
    • Install the root certificate of the added SOTI MobiControl instance on the SOTI XSight server.
    • Restart the SOTI XSight Display Service in the SOTI XSight Administration Utility.
    • Re-login to SOTI XSight.
    Select Ok.
    Certificate prompt
  5. Add the non-primary SOTI MobiControl root certificate to VM where XMS is installed and restart XMS from the Admin Utility/Services.
    Note: If the SOTI XSight installation has more than one XMS instance, you must install the certificate on all XMS instances and restart these instances.

Getting Non-primary SOTI MobiControl Root Certificate

Procedure

  1. RDP into the non-primary SOTI MobiControl instance.
  2. Open the SOTI MobiControl Admin Utility.
  3. Select the Certificates tab.
    Select the Certificates tab
  4. In the Root Certificate Management panel, select Export.
    Export the root certificate
  5. Transfer the non-primary SOTI MobiControl root certificate file to the primary XMS server. For example, Root.cert.
    Note: If SOTI XSight has more than one XMS instance, you must install the certificate on all XMS nodes.
  6. On the primary XMS server, double-click on the non-primary SOTI MobiControl root certificate file that was copied over.
    1. Select Install Certificate.

      Select install certificate

    2. In the Certificate Import Wizard, select Local Machine and then select Next.

      Select local machine

    3. Select Yes.

      Select yes

    4. In the Certificate Import Wizard, select Place all certificates in the following store and then select Browse.

      Save all certificates to a specified store

    5. Select the Trusted Root Certification Authorities certificate store, then select Ok.

      Select the Trusted Root Certificates Authorities certificate store

    6. In the Certificate Import Wizard, select Next.

      Select next

    7. In the Certificate Import Wizard, select Finish.

      Select Finish

    8. In the Certificate Import Wizard, the message The import was successful displays.

      The import was successful

Deleting a Non-Primary SOTI MobiControl Instance Integrated with SOTI XSight

Procedure

  1. Login to SOTI XSight web console.
  2. Select the main menu from within the SOTI XSight web console.
  3. Select Settings > Integration > MobiControl Integration.
  4. To delete an instance, hover over the instance name in the Other Instances section and select the icon.

    The delete instance icon

  5. In the Delete MobiControl Instance pop-up. Select the Yes, please delete this instance checkbox.

    Deleting the instance

  6. Select Delete.
    Note: You must restart the XMS services and re-login to complete the deletion of the instance. If SOTI XSight has more than one XMS instance, you must restart XMS on all XMS instances.

Updating a Non-primary Instance

About this task

Update the instance configuration, selecting the instance name.

Procedure

  1. Login to SOTI XSight web console.
  2. Select the main menu from within the SOTI XSight web console.
  3. Select Settings > Integration > MobiControl Integration.
  4. Select the instance name.

    Select the instance

  5. The Update MobiControl Integration panel displays

    The Update SOTI MobiControl Integration panel displays

  6. Update the settings and select Save.
  7. After successfully updating the settings the following prompt displays.

    Successful update of the settings

    Note: If SOTI XSight has more than one XMS instance, you must restart XMS on all XMS instances.

Troubleshooting

Procedure

  1. If there are incorrect instance configurations settings when setting up additional SOTI MobiControl instances (for example, incorrect DB credentials or an incorrect access URL), a Save not successful error occurs.
  2. If adding an instance with the same Access URL as an existing instance, a Duplicate MC Connection Name error occurs.

Requirements

Procedure

  1. Ensure all primary and non-primary SOTI MobiControl instances have the same username and password.
    Important: The same username and password are also required for the service user account.
  2. All SQL server ports must be open (default:1433 and non-default ports).
  3. After successful set-up, you must restart all XMS instances.
  4. When prompted to re-login you must logout from all different browsers and then log back in.

Limitations

Procedure

  1. Enrolling a device that was enrolled in instance A to instance B still opens a session on instance A in the chat container.
  2. If you do not select Save when setting up and additional SOTI MobiControl instances or updating an instance, any changes made are not saved.
    Note: If you do not select Save, you are not prompted to save your changes.
  3. Upgrading SOTI XSight from an earlier version (for example, version 4.3.x to 2024.x) does not update the database values for the non-primary SOTI MobiControl instances in the im_McConnection table.
  4. Using a relative URL when setting up additional SOTI MobiControl instances gives a duplicate instance error.
    Note: This limitation is removed in versions 2024.1.0 and later.