From Release 3.18, the jtel system uses the wildfly server, currently version 18.0.1.

These are the following main differences between the instatllations:

ItemjbosswildflyComments
Installation LocationNo directory linking.

Directory is linked:

/home/jtel/wildfly-18.0.1.Final 

is linked by

/home/jtel/wildfly-current
This enables simpler version changes.
Configuration File
/home/jtel/jboss-as-7.1.1.FINAL/standalone/configuration/standalone-full.xml
/home/jtel/wildfly-current/standalone/configuration/standalone-full.xml
The messaging queue services are no longer required. Not using standalone-full.xml saves a little bit of memory and a few seconds on startup.
Log Files
/home/jtel/jboss-as-7.1.1.FINAL/standalone/log/
/home/jtel/wildfly-current/standalone/log/
Use linked directory.
Deployment Files
/home/jtel/jboss-as-7.1.1.FINAL/standalone/deployments/
/home/jtel/wildfly-current/standalone/deployments/
Use linked directory.
Updating
updatejb.sh

or

/usr/local/bin/updatejb.sh
updatejb.sh

or

/usr/local/bin/updatejb.sh
No Change.
Restarting / Starting / Stopping

CentOS 7.x

systemctl restart jboss.service
systemctl start jboss.service
systemctl stop jboss.service

CentOS 6.x

service jboss restart
service jboss start
service jboss stop

CentOS 7.x and 8.x

systemctl restart wildfly.service
systemctl start wildfly.service
systemctl stop wildfly.service

CentOS 6.x

service wildfly restart
service wildfly start
service wildfly stop
Change of service name.
Java VersionJava 7.Java 8 or higher.Recommend: use OpenJDK 8.x package, as this is updateable via yum.
  • No labels