Installing the collector
The installation of the collector is done by running the install command on the binary. The install process will copy the binary to the correct directory and create a service.
Download the collector binary here.
Install command
- Copy the binary to the collector server (location doesn’t matter)
- Run the install command from within the directory where the binary is located, using an administrator terminal.
"factry-collector-binary-path" install --token "token"
Example on windows
.\factry-opcua-collector_v1.1.4_linux-x64 install -t "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJodHRwOi8vbG9jYWxob3N0OjgwMDAiLCJleHAiOjI0MzcyMDI0MDcsImdycGMtcG9ydCI6IjgwMDEiLCJpYXQiOjE2NDg4MDI0MDcsImlzcyI6ImZhY3RyeS5pbyIsInJlc3QtcG9ydCI6IjgwMDAiLCJ1dWlkIjoiNjgxZmZiNjQtYjE4Ny0xMWVjLWJlNWYtMDI0MmFjMTgwMDAzIn0.RQlzFoi7I-793-sRIe8bGcQAM5fxQ7lHHkUCVcwxNu8"
Example on linux
./factry-opcua-collector_v1.1.4_linux-x64 install -t "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJodHRwOi8vbG9jYWxob3N0OjgwMDAiLCJleHAiOjI0MzcyMDI0MDcsImdycGMtcG9ydCI6IjgwMDEiLCJpYXQiOjE2NDg4MDI0MDcsImlzcyI6ImZhY3RyeS5pbyIsInJlc3QtcG9ydCI6IjgwMDAiLCJ1dWlkIjoiNjgxZmZiNjQtYjE4Ny0xMWVjLWJlNWYtMDI0MmFjMTgwMDAzIn0.RQlzFoi7I-793-sRIe8bGcQAM5fxQ7lHHkUCVcwxNu8"
Changing environment variables after installation
Linux
You can change the environment variables by changing them in the environment file.
This can be found here /etc/systemd/system/environments
Windows
- open regedit.
- Navigate to
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
- Select factry-collector-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (replace the x’s with the collector ID which you can find in the historian).
- Right click Environment and select “Modify…”
- Edit the environment variables
- Restart the service, service name looks this “Factry Collector (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)”
Configuration
After installation the collector will register itself on the historian server and the collector settings will be ready to be filled in.
Switching to a new collector service
To switch a collector instance in the historian webpage to a new collector service, one needs to
generate a new api token
first. Next, use this token to
install a new collector service
. Finally,
delete the previously existing collector service
to cleanup the inactive collector service.
Using a new server
One is able to switch from an existing collector service, to a new collector service on a different server. In this case make sure that the necessary TCP ports from the Historian server are reachable by the new collector server.
Deleting a collector
This section describes how to delete a collector service. To delete a collector instance in the Historian webpage as well, one needs to contact Factry support.
The best practice is to re-link a collector instance in the Historian webpage to a new collector service, before deleting the existing collector service.
Delete a collector service
Before deleting a collector service, make sure to stop the collector service first.
Example collector service
The service name of the collector is named after it’s uuid in the Historian. The uuid of a collector can be found by selecting the according collector in the Historian webpage and looking at the ID
in the collector details on the right side of the screen.
An example uuid and the according collector service name:
05a094a4-118a-11ed-9351-0242ac1c0003
factry-collector-05a094a4-118a-11ed-9351-0242ac1c0003
Windows service
First, lookup the service name of the collector by clicking on the according collector service in the windows service manager. Stop
the service in the service manager before deleting the collector service by executing the following command in a cmd administrator terminal:
sc delete "factry-collector-service-name"
Linux service (systemd)
Perform the following commands on a sudo
terminal on the linux machine to stop, disable and remove the service from the system daemon:
systemctl stop factry-collector-service-name
systemctl disable factry-collector-service-name
rm /etc/systemd/system/factry-collector-service-name.service
systemctl daemon-reload