Start-up logic for Linux systemctl systems
Â
Create two services. Â The first (apacheds.service) starts up ApacheDS (if you are running it). Â The second (bedework.service) starts up jboss (with bedework inside). Â It also starts up the webcaching system.
Â
Save something like the block of code that follows into /etc/systemd/system/apacheds.service
Â
[Unit] Description=Bedework Calendar ApacheDS After=network.target  [Service] Environment=JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk WorkingDirectory=/opt/quickstart-3.10 Type=idle ExecStart=/opt/quickstart-3.10/bw dirstart User=bedework Group=bedework TimeoutStartSec=0 TimeoutStopSec=180  [Install] WantedBy=multi-user.target
Â
Save something like the block of code that follows into /Â /etc/systemd/system/bedework.service
Â
[Unit] Description=Bedework Calendar After=apacheds.service [Service] Environment=JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk WorkingDirectory=/opt/quickstart-3.10 Type=idle ExecStart=/opt/quickstart-3.10/startjboss -heap 2G ExecStartPost=/opt/quickstart-3.10/runcache User=bedework Group=bedework TimeoutStartSec=0 TimeoutStopSec=180 [Install] WantedBy=multi-user.target
Â
Start up with
Â
$ sudo systemctl start apacheds.service
$ sudo systemct start bedework.service
Set up for boot with:
$ sudo systemctl enable apacheds.service
$ sudo systemctl enable bedework.service
Bedework Enterprise Calendar Server, version 3.10