Starting with release 7 Red Hat switched to systemd as service manager. Old init based services are still handled correctly, so I expected to be able to follow Red Hat’s instructions in order to configure my JBoss EAP 6.x installation as a system service. However when I tried to run my service with
service jboss-as-standalone.sh start
I got an error message stating that the jboss-as-standalone.sh.service unit could not be started. After a little googling and a little trial and error I discovered that systemctl – the systemd replacement for the service command – didn’t like my service’s name. I moved the jboss-as-standalone.sh file to jboss, rerun chkconfig, and everything is now working.