You can install the various PingIntelligence components as a systemd
service. When
installing as a service, the various components are started automatically when the host
system restarts.
Ensure you have sudo
access to install PingIntelligence components as a
service. Complete the following steps only if the automated deployment did not
install PingIntelligence
components as a service. To verify whether service is installed on the desired host
machine, run the following command:
# systemctl status <service-name>
For example, to check ASE service, enter the following command on ASE host machine:
systemctl status pi-ase.service
● ase.service - ASE
Loaded: loaded (/etc/systemd/system/ase.service; disabled; vendor preset: disabled)
Active: active (running) since Sun 2019-11-03 23:01:19 MST; 23h ago
.
.
Nov 03 23:01:19 T5-06 systemd[1]: Started ASE.
Verify that PingIntelligence services are not running. Use the following service names to verify the status of each component:
- ASE:
pi-ase.service
- ABS:
pi-abs.service
- MongoDB:
pi-mongodb.service
- Dashboard:
pi-dashboard.service
- Web GUI:
pi-webgui.service
- Elasticsearch:
pi-elasticsearch.service
- Kafka:
pi-kafka.service
- Zookeeper:
pi-zookeeper.service
- API Publish:
pi-apipublish.service
Stop the component for which you want to install the service.
To install PingIntelligence as a
systemd
service:
Edit the service files in the following order to make sure that PingIntelligence components
successfully installed. Use the Required
option to set the order of
starting of service. For more information, see Creating and modifying systemd unit files.
- MongoDB
- Kafka
- ABS
- ASE
- API Publish
- Elasticsearch
- Dashboard
- Web GUI