Adding a system to SystemLink for Trial

[Kenny_K]

We are currently running a trial of NI Systemlink, and I am importing some data from our existing database to show some of the dashboarding capabilities.

When uploading the data using the LabVIEW API, I set the hostName to the PC that originally submitting the data to our existing database, but it seems that Systemlink converts it to the host name of the PC that is configured as the systemlink client.

If I try to add a system using the HTTP API, I get an error that the minion cannot be found:

https://milsystemlink1/nisysmgmt/v1/register-systems

{

  "systemsCredentials": [

    {

      "hostname": "72307-2",

      "ipAddress": "10.10.10.10",

      "password": "admin",

      "username": "password"

    }

  ],

  "activate": true,

  "workspaces": [

    "ec920196-a5fc-4fc2-892b"

  ]

}

Are we able to add data and have it retain the proper Host Name if the system does not have the SystemLink client on it yet???

[ThamS]

---

@Kenny_K wrote:

Are we able to add data and have it retain the proper Host Name if the system does not have the SystemLink client on it yet???

---

I also have the same Question.

But, wow, there is no any answer yet?

[T-REX$]

I'm not as intimately familiar with the LabVIEW API for uploading test results as I ought to be, but I would be surprised if it was overwriting the host name provided. Under the hood, the LabVIEW API is really just a wrapper around the HTTP API to SystemLink, which treats the hostname as a simple string:

The only thing the client should be providing is an API key with the privileges of the "Automated Agent" role in the case that you aren't providing login credentials.

What version of LabVIEW are you seeing this issue with?

[ThamS]

---

@T-REX$ wrote:

The only thing the client should be providing is an API key with the privileges of the "Automated Agent" role in the case that you aren't providing login credentials.

---

Is there any way for a 3rd-party client device (non-windows, has no SystemLink Client software) to be added as System on SystemLink Server?

[T-REX$]

Not as a System today. Without the SystemLink client to manage API keys, software, health reporting, and asset presence, there is not much perceived value to tracking hardware as a system.

That said, we do allow the creation and management of 3rd-party asset tracking from both the UI and programmatic APIs. You can do things like setting their location and set a parent/child hierarchy between them, track calibration status and history, associate files to them, and track utilization programmatically. 

What sort of functionality or workflow are you hoping to achieve with adding systems without the Client installed?

[ThamS]

---

@T-REX$ wrote:

What sort of functionality or workflow are you hoping to achieve with adding systems without the Client installed?

---

our answer is exactly as you mentioned here:

---

creation and management of 3rd-party asset tracking. Things like setting their location and set a parent/child hierarchy between them, track calibration status and history, associate files to them, and track utilization programmatically. 

We do have several 3rd-party hardware as datalogger/iot devices. they could POST HTTP with API key Authentication on the header.

And now they already sends the data and the device status to our LabVIEW WebService, and the web service interpret it into a each tag-path accordingly.