Skip to main content
Matrix42 Self-Service Help Center

Backend

  1. Last updated
  2. Save as PDF

Remote Assistance Backend

To use Remote Assistance, it must be enabled and configured before installing the Frontend.


Do not install Remote Assistance on the same server as Matrix42 Digital Workspace Platform, but on a separate system, otherwise, there will be unnecessary configuration challenges.

The installation instructions are in your FastViewer portal under "General" --> "Documents" --> "Server."

License Activation
Cloud

If the Remote Assistance Backend is installed in the Matrix42 Cloud, then it is always ensured that they have the latest version available and that it is already activated and configured accordingly.

On-Premise

The license must now be imported into the local installation.
Proceed as follows:

  1. Change to the local installation directory e.g. C:\Program Files (x86)\WebConferenceServer
  2. Run the program "ServerAdmin.exe".
  3. Click the button "Import Licenses"  in the lower right corner of the dialog.
  4. Choose the option "Use Download" and press the button "Start Import".
  5. Then enter your individual license password from your installation to start the import.

    clipboard_ef3ec722bf91191b732c7d5eb26c9b00c.png

    clipboard_e8f6548b0d78f48f937a945e705e7adb4.png
  6. After successfully importing the license, click on "Exit".

Service Bus Settings

Cloud

If the Remote Assistance Backend is installed in the Matrix42 Cloud, then it is always ensured that they have the latest version available and that it is already activated and configured accordingly.

On-Premise

Make sure that the on-premise server version you are using is at least version 3.3.8541.36312 or greater. If this is not the case, then install or upgrade your installation.

The individual service bus settings must still be entered in the Remote Assistance backend.
Proceed as follows:

  1. Change to the local installation directory e.g. C:\Program Files (x86)\WebConferenceServer
  2. Run the program "ServerAdmin.exe".
  3. Click the button "ServiceBus Settings"  in the lower left corner of the dialog.
  4. Enter the following information:

    Type: RabbitMQ
    Topic: matrix42.suem.topic
    Subscription: matrix42.fastviewer.sucription
    Connection String: Type here the RabbitMQ Connection String from your own RabbitMQ installation.

    clipboard_e3f3a392baab8ff198bba4e5ef67088b7.png
     
  5. Click on "Save".

SSL-Certificate


A valid SSL certificate is always mandatory for a secure encrypted connection.
The backend server must be accessible via HTTPS and must have a valid certificate.

Cloud

If the Remote Assistance Backend is installed in the Matrix42 Cloud, then it is always ensured that there is a valid SSL certificate available and that it is already configured accordingly.

On-Premise

To activate an SSL certificate, proceed as follows:

Change to the local installation directory e.g. C:\Program Files (x86)\WebConferenceServer

  1. Run the program "CertificateInstaller.exe".
  2. In the right drop-down select the IP address to which you want to bind the SLL certificate.
  3. Click the button "Select cert". A dialog for selecting the certificate appears.
  4. Choose the valid certificate for your server (dedicated server certificate or wildcard certificate).
  5. Click the "OK" button to confirm the certificate.
  6. Click the button "Install cert.
  7. Confirm the successful installation with "OK".
  8. With the "Show installed" button you can view the installed certificates.
  9. Close the program "CertificateInstaller.exe".
HTTPS Settings

For problem-free communication via https, it is necessary to make appropriate changes in the settings.ini configuration file.

  1. Change to the local installation directory e.g. C:\Program Files (x86)\WebConferenceServer and open the settings.ini file.
  2. Adjust the following parameters:
    1. ExternalAddress - Here please enter the FQDN under which your server is reachable.
      If the Webconference Server should also be reachable from the internet, this must be an external FQDN.
      e.g. ExternalAddress=yourservername.imagoverum.com
    2. Listen2 - In case you use a wildcard certificate, the FQDN of your server must be stored in the parameter listen2.
      e.g. The certificate runs on "*.imagoverum.com".
      The parameter listen2=https://yourservername.imagoverum.com/
  3. Save the settings.ini file.
  4. Restart the service "WebconferenceServer" so that the settings are applied.

Check the functionality by calling the FQDN of your server with https://prefix in the browser.
e.g. https://yourservername.imagoverum.com

As a response the following text appears in the browser: FastViewer Webconference Server

The configuration of the infrastructure is now complete.
    1. Back to top
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
    2. Tags
      This page has no tags.