Start WildFly as a systemd Service on Linux: Difference between revisions
No edit summary |
|||
| Line 12: | Line 12: | ||
=Install the Pre-Packaged System V Startup Scripts into Standard <tt>systemd</tt> Location= | =Install the Pre-Packaged System V Startup Scripts into Standard <tt>systemd</tt> Location= | ||
Copy the pre-packaged System V startup scripts (<tt>jboss-as-domain.sh</tt>, <tt>jboss-as-standalone.sh</tt>) from <tt>$JBOSS_HOME/bin/init.d</tt> into <tt>/usr/lib/systemd/scripts</tt>. | |||
Perform the following operations as "root", re-name the scripts as indicated below. | |||
For a standalone installation, name the script <tt>jboss</tt>. | |||
<pre> | |||
cp $JBOSS_HOME/bin/init.d/jboss-as-standalone.sh /usr/lib/systemd/scripts/jboss | |||
</pre> | |||
For a domain installation, name the script <tt>jboss-host-controller</tt>, regardless of whether we're configuring to start the domain controller or a subordinate host controller. This is because on the domain controller host, the domain controller process and the host controller process coincide. | |||
<pre> | |||
cp $JBOSS_HOME/bin/init.d/jboss-as-domain.sh /usr/lib/systemd/scripts/jboss-host-controller | |||
</pre> | |||
Revision as of 07:46, 16 February 2016
Internal
Overview
We create a simple systemd Type=oneshot unit file that delegates the work of starting and stopping the instance to the System V wrappers shipped with EAP installation bundle.
systemd File Locations
We adapted the installation procedure after an ActiveMQ installation procedure that recommended placing files in /usr/lib/systemd/scripts and /usr/lib/systemd/system. However, a better location seems to be /etc/systemd/... More research is needed, the results will go here systemd Concepts#Unit_File_Location.
Install the Pre-Packaged System V Startup Scripts into Standard systemd Location
Copy the pre-packaged System V startup scripts (jboss-as-domain.sh, jboss-as-standalone.sh) from $JBOSS_HOME/bin/init.d into /usr/lib/systemd/scripts.
Perform the following operations as "root", re-name the scripts as indicated below.
For a standalone installation, name the script jboss.
cp $JBOSS_HOME/bin/init.d/jboss-as-standalone.sh /usr/lib/systemd/scripts/jboss
For a domain installation, name the script jboss-host-controller, regardless of whether we're configuring to start the domain controller or a subordinate host controller. This is because on the domain controller host, the domain controller process and the host controller process coincide.
cp $JBOSS_HOME/bin/init.d/jboss-as-domain.sh /usr/lib/systemd/scripts/jboss-host-controller