Setting up Services to Start on Boot

There are several ways to setup services to start on boot. These include:

Windows: Startup folder
Windows: via the registry
Windows: Scheduled Tasks
Linux: /etc/rc.local/
Linux: /etc/init.d/ SysV LSB-compliant scripts
Linux: systemd .service files
Linux/Windows: using Apache Commons Daemon to install JVM apps as a service.

The following instructions will focus on the 3rd and 6th methods.

Those methods will be used to setup Syndeia Cloud and its dependency, Cassandra, to start on boot

Note, these instruction assume the user has installed Syndeia Cloud under syndeia-cloud-current or created a symbolic link (symlink) named syndeia-cloud-current pointing to the current installed version. For instructions on how to set this up, see Appendix D4.1 for Windows and Appendix D4.2 for Linux.

Windows 2012-R2

The following instructions describe how to setup the Syndeia Cloud service to only start after the Cassandra service has fully started and the port is available on Windows via Scheduled Tasks. See the appropriate Single node Cassandra or Multi node Cassandra section depending on your Cassandra deployment type.

1. From your installation of Syndeia Cloud, import in the Start Cassandra.xml Scheduled Task from <syndeia-cloud-home>/conf/, ie: from CMD.EXE, run schtasks /create /xml "Start Cassandra.xml" /tn "Start Cassandra".
2. From your installation of Syndeia Cloud, import in the Start Syndeia Cloud wait for Cassandra.xml Scheduled Task from <syndeia-cloud-home>/conf/, ie: from CMD.EXE, run schtasks /create /xml "Start Syndeia Cloud wait for Cassandra.xml" /tn "Start Syndeia Cloud".

If the above files are unavailable, see Appendix D4.3 to create the Scheduled Tasks manually for a single-node Cassandra deployment and Appendix D4.4 for a multi-node Cassandra deployment.

Linux RHEL/CentOS7

The following instructions describe how to setup the Syndeia Cloud service to only start after the Cassandra service has fully started and the port is available on Linux RHEL/CentOS7 or machines with the systemd init system.

Single node Cassandra

1. From your installation of Syndeia Cloud, copy the syndeia-cloud.single_node_cassandra.service systemd .service file from <syndeia-cloud-home>/conf/ to /etc/systemd/system/ as syndeia-cloud.service, ie: sudo cp <syndeia-cloud-home>/conf/syndeia-cloud.single_node_cassandra.service /etc/systemd/system/syndeia-cloud.service.

If this file is unavailable, copy and paste the code from Appendix D4.4 into the above location and comment/uncomment out the relevant section for single or multi-node Cassandra.

2. Run sudo systemctl reload-daemon
3. Run sudo systemctl enable syndeia-cloud

Multi node Cassandra

1. From your installation of Syndeia Cloud, copy the syndeia-cloud.multi_node_cassandra.service systemd .service file from <syndeia-cloud-home>/conf/ to /etc/systemd/system/ as syndeia-cloud.service, ie: sudo cp <syndeia-cloud-home>/conf/syndeia-cloud.single_node_cassandra.service /etc/systemd/system/syndeia-cloud.service

If this file is unavailable, copy and paste the code from Appendix D4.5 into the above location and comment/uncomment out the relevant section for single or multi-node Cassandra.

2. Run sudo systemctl reload-daemon
3. Run sudo systemctl enable syndeia-cloud

Linux SysV init based system/non-systemd

The following instructions describe how to setup the Syndeia Cloud service to only start after the Cassandra service has fully started on Linux machines with an LSB-compliant SysV init system

1. From your installation of Syndeia Cloud, copy the syndeia-cloud.init_script.bash LSB-compliant, SysV, init script from <syndeia-cloud-home>/conf/ to /etc/init.d/ as syndeia-cloud, ie: sudo cp <syndeia-cloud-home>/conf/syndeia-cloud.init_script.bash /etc/init.d/syndeia-cloud.

If this file is unavailable, copy and paste the code from Appendix D.6 into the above location.

2. Run sudo chkconfig syndeia-cloud