Install and configure SystemLink Server on your host to begin managing systems and working with data. SystemLink Server includes the SystemLink web application and SystemLink APIs.

Before you begin, determine the size of the server to optimize performance. You must also install the following applications.
  • NI Package Manager (NIPM)
  • Volume License Manager
    Note Install this application if you plan to use SystemLink on non-host machines. For example, if you are connecting a machine to a server through SystemLink Client.
Note SystemLink Server is backwards compatible with older SystemLink Client versions but not forwards compatible.
  1. In NI Package Manager, on the Browse Products tab, search for and install SystemLink Server and related installers.
    You do not need to install SystemLink Client on your server machine.
  2. Restart your machine to complete the installation.
  3. Launch NI Web Server Configuration and follow the prompts in NI Web Server Configuration to set up your server. You can use these credentials to log into SystemLink with server administrator privileges.
    For more information on server settings, refer to the NI Web Server Configuration help.
  4. 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 to use for your server.
      The third-party DNS server you use determines the alias.
    4. Click Apply and Restart.
  5. Prepare your server to connect to SystemLink Client.
    1. Ensure the following default ports are open on your server.
      Note SystemLink automatically manages the local Windows firewall. If you are on a corporate network, you might need to work with your IT department to configure your corporate network firewall.
      Port Purpose
      80 (default HTTP) or 443 (default HTTPS, recommended)

      SystemLink uses these ports to allow targets to perform the following actions.

      • Install packages from the server.
      • Publish data.
      • Receive data.
      4505-4506 SaltStack uses these ports to execute remote procedures on targets.
      5672 RabbitMQ uses this port. Legacy client communications require this port. SystemLink disables the port by default.
      59100-59110 LogosXT uses these ports for OPCUA connectivity.
      2343, 2809, and 59110-59210 Clients, such as DIAdem, use these ports to access the SystemLink DataFinder index and TDM. SystemLink Base, Full, and Pro do not require these ports.
    2. If you are setting up SystemLink on a network that uses a proxy server, configure proxy settings for SystemLink.
After completing basic setup for your server, you can complete the following tasks.
  • Connect to a remote database or file share to enhance scalability.
  • Manage access to SystemLink using workspaces, roles, and privileges.
  • Set up at least one SystemLink client for a Windows target or NI Linux Real-Time target to begin managing systems.