Bug 1328812

Summary: Deprecated chkconfig command in service configuration instructions
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Katerina Odabasi <kanovotn>
Component: DocumentationAssignee: Lucas Costi <lcosti>
Status: CLOSED WONTFIX QA Contact: Pavel Slavicek <pslavice>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.7CC: eap-docs, sjay
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-08 00:11:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Katerina Odabasi 2016-04-20 10:39:19 UTC
Document URL: 
https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Installation_Guide/index.html#Configure_JBoss_Enterprise_Application_Platform_as_a_Service_in_Red_Hat_Enterprise_Linux_RPM_Method

Section Number and Name: 
2.10.1. Configure JBoss EAP 6 as a Service in Red Hat Enterprise Linux (RPM Method)

Describe the issue: 
The procedure "Procedure 2.17. Configure JBoss EAP 6 as a Service using the RPM Method in Red Hat Enterprise Linux" contains commands which are valid for RHEL6  but for RHEL7 are deprecated (chkconfig).

Suggestions for improvement: 
Please replace usage of 'chkconfig' command examples for RHEL7 with appropriate equivalent of 'systemctl' command

Additional information:

Comment 1 Lucas Costi 2016-09-15 05:14:47 UTC
Hi Katerina, running the systemctl commands result in the following output (tested on RHEL 7.0 with EAP 6.4 installed from RPMs):

$ sudo systemctl enable jbossas.service
jbossas.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig jbossas on
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).

As above, it fails-over to using "chkconfig jbossas on" to enable the service. I believe that it is a better user experience to directly use the deprecated command rather than get the above warning which is confusing as to whether the service has been enabled or not. 

If the service files are updated to natively work with systemctl on RHEL7, I think it would be better to update the documentation then.

Please let me know if you have any problems with this.

Comment 4 Lucas Costi 2018-06-08 00:11:09 UTC
I'm going to close this, as 6.4 is currently in maintenance-only, and the current instructions do work. It has been updated with new service scripts in EAP 7.0 (docs here: https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.1/html-single/installation_guide/#configuring_jboss_eap_as_a_service_in_red_hat_enterprise_linux_rpm_installation).