Table Of Contents

Setting Up a SystemLink Server

Last Modified: August 27, 2020

Install and configure SystemLink Server on your host to begin managing systems and working with data. SystemLink Server includes NI SystemLink Web Application and SystemLink APIs.

Before you begin, determine the size of the server to optimize performance. If you will use SystemLink on machines other than the host, install Volume License Manager.
spd-note-note
Note  

SystemLink Server is backwards compatible with older SystemLink Client versions, but it is not forwards compatible.

  1. In NI Package Manager, search for and install SystemLink Server.
  2. Launch NI SystemLink Web Application. NI Web Server Configuration launches automatically.
    spd-note-note
    Note  

    If you install an NI SystemLink TDM module or add-on, the NI SystemLink TDM Configuration wizard launches automatically. Refer to the NI SystemLink TDM Configuration help for more information.

  3. Follow the prompts in NI Web Server Configuration to set up the web server. You will use the credentials you specify each time you launch NI SystemLink Web Application. Refer to NI Web Server Configuration help for more information on server settings.
  4. Prepare your server to connect to SystemLink Client.
    1. Ensure the following default ports are open on your server. SystemLink automatically manages the local Windows firewall. If you are on a corporate network, you may need to work with your IT department to configure your corporate network firewall.
      Port Purpose
      80 (default HTTP) or 443 (default HTTPS, recommended) NI SystemLink Web Application uses these ports to enable targets to install packages from the server and publish and receive data.
      2343, 2809, 59100-59110 DataFinder uses these ports to find technical data on local computers and servers in a global network or in the SystemLink file service
      4505-4506 SaltStack uses these ports to execute remote procedures on targets.
      5673 and 15672 RabbitMQ uses these ports to transfer files, tags, health data, and test results.
  5. Create a DNS alias.
    1. In NI Web Server Configuration, click Remote.
    2. Select Allow remote connection from any client.
    3. Enter the DNS alias you want to use for your server. For example, test.systemlink.io.
    4. Click Apply and Restart.
  6. Add the DNS alias to NI SystemLink Server Configuration.
    1. Launch NI SystemLink Server Configuration.
    2. Click RabbitMQ and enter the DNS alias.
      spd-note-tip
      Tip  

      Use the DNS alias to connect your clients to the server.

  7. In NI SystemLink Server Configuration, click Security and disable insecure access. Insecure access ensures AMQP clients can access SystemLink. However, NI recommends all clients use HTTP(S). Clients using AMQP can access only the default workspace.
Set up at least one SystemLink client for a Windows target or NI Linux Real-Time target to begin managing systems in NI SystemLink Web Application.

Recently Viewed Topics