Start the application on each virtual machine

Content Intelligence Deploying the Example OVF

Version

2.2.x

Audience

anonymous

Part Number

MK-HCI003-15

ft:lastEdition

2023-10-23

On each server or virtual machine that is to be a system instance:

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.

Here are some examples of how you can start the script:

You can run the script in the foreground:
sudo /<path>/hci/bin/run

When you run the run script this way, the script does not automatically complete, but instead remains running in the foreground.
You can run the script as a service using systemd:
1. Copy the HCI.service file to the appropriate location for your OS. For example:
  cp /<path>/bin/HCI.service/etc/systemd/system
2. Enable and start the search service:
```
sudo systemctl enable HCI.service
sudo systemctl start HCI.service
```

Note: When you enable the search service, systemctl may 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, the search service may or may not have successfully been enabled.

To avoid this, make sure that you moved the Hitachi Content Intelligence.service to the appropriate location, typically /etc/systemd/system.