Start the application on each server or virtual machine

Content Intelligence Installation Guide

Version

2.2.x

Audience

anonymous

Part Number

MK-HCI002-17

Start the application script run using whatever methods you usually use to run scripts.

Important: Ensure that the method you use can keep the run script running and can automatically restart it in the event of a server restart or other availability event.

You can run the script in the foreground: sudo install_path/hci/bin/run
When executed this way, the run script does not automatically complete, but instead remains running in the foreground.
You can run the script as a service using systemd:
1. Open the HCI.service file in a text editor, located in install_path/bin.
2. Verify that the following two lines have the correct install_path:
  ExecStart=install_path/hci/bin/run
  
  ExecStopPost=install_path/hci/bin/stop
3. Save the file.
4. Copy the HCI.service file to the appropriate location for your OS:
  cp install_path/hci/bin/HCI.service /etc/systemd/system
5. Enable and start HCI.service:
```
sudo systemctl daemon-reload
sudo systemctl enable HCI.service
sudo systemctl start HCI.service
```

Note: When you enable HCI.service, systemctl might display this message:

The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are:

1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory.

2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it.

3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...).

Depending on your OS, HCI.service may or may not have successfully been enabled.

To avoid this, make sure that you move HCI.service to the appropriate location, typically /etc/systemd/system.