Installazione di WildFly (Jboss) su Ubuntu 16.04
In questo tutorial andremo ad installare Wildfly su Ubuntu 16.04.
Partiamo da una virtual machine preinstallata Ubuntu 16.04 ( fare riferimento a questo articolo), aggiorniamo il sistema
sudo apt-get update
sudo apt-get upgrade
scarichiamo dal sito ufficiale Wildfly versione 12
sudo apt-get install wget
sudo wget http://download.jboss.org/wildfly/12.0.0.Final/wildfly-12.0.0.Final.tar.gz
sudo tar -xvzf wildfly-12.0.0.Final.tar.gz
sudo mv wildfly-12.0.0.Final/ wildfly/
copiamo questa cartella sotto /opt
sudo cp -rp wildfly/ /opt
sudo chmod -R 755 /opt/wildfly
chown -R root. /opt/wildfly
A questo punto installiamo la Oracle JDK versione 8
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java8-installer
aggiungiamo un utente all’application server
cd /opt/wildfly/bin
./add-user.sh
What type of user do you wish to add?
a) Management User (mgmt-users.properties)
b) Application User (application-users.properties)
(a): a
aggiungiamo l’ utente e inseriamo la password
Enter the details of the new user to add.
Using realm ‘ManagementRealm’ as discovered from the existing property files.
Username : test
Password recommendations are listed below. To modify these restrictions edit the add-user.properties configuration file.
– The password should be different from the username
– The password should not be one of the following restricted values {root, admin, administrator}
– The password should contain at least 8 characters, 1 alphabetic character(s), 1 digit(s), 1 non-alphanumeric symbol(s)
Password : password_a_vostra_scelta
WFLYDM0098: The password should be different from the username
Are you sure you want to use the password entered yes/no? yes
Re-enter Password : password_a_vostra_scelta
creiamo anche il gruppo
What groups do you want this user to belong to? (Please enter a comma separated list, or leave blank for none)[ ]: test
About to add user ‘test’ for realm ‘ManagementRealm’
Is this correct yes/no? yes
Added user ‘test’ to file ‘/opt/wildfly/standalone/configuration/mgmt-users.properties’
Added user ‘test’ to file ‘/opt/wildfly/domain/configuration/mgmt-users.properties’
Added user ‘test’ with groups test to file ‘/opt/wildfly/standalone/configuration/mgmt-groups.properties’
Added user ‘test’ with groups test to file ‘/opt/wildfly/domain/configuration/mgmt-groups.properties’
Is this new user going to be used for one AS process to connect to another AS process?
e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server EJB calls.
yes/no? yes
To represent the user add the following to the server-identities definition <secret value=”dGVzdA==” />
per effettuare dei test sulla piattaforma, leghiamo il Wildfly alla porta 0.0.0.0 (a tutte, in modo da essere contattato dall’esterno)
cd /opt/wildfly/standalone/configuration
vim standalone.xml
sostituiamo al posto dell’indirizzo 127.0.0.1 lo 0.0.0.0 (facilitiamo i nostri test), a questo punto avviamo adesso la versione STANDALONE di Wildfly (Jboss)
cd /opt/wildfly/bin
./standalone.sh
avremo il seguente output
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/wildfly
JAVA: java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSiz e=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byt eman -Djava.awt.headless=true
=========================================================================
17:28:35,814 INFO [org.jboss.modules] (main) JBoss Modules version 1.7.0.Final
17:28:38,333 INFO [org.jboss.msc] (main) JBoss MSC version 1.3.2.Final
17:28:38,372 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.1.Final
17:28:38,663 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 12.0.0.Final (WildFly Core 4.0.0.Final) starting
accediamo al seguente link http://ip_macchina_server:8080
accediamo alla console di amministrazione oppure al link http://ip_macchina_server:9090/console/
inseriamo l’utente e la password creata in precedenza (test) avremo
Per poter avviare in background l’application server
cd /opt/wildfly/bin
./standalone.sh &
E’ possibile creare uno script per l’avvio automatico di Wildfly, aggiungiamo un utente di sistema
sudo adduser --no-create-home --disabled-password --disabled-login wildfly
concediamo i permessi all’utente wildfly sulla cartella d’ installazione
sudo chown -R wildfly:wildfly /opt/wildfly/
copiamo lo script di startup sotto la cartella init.d
sudo cp /opt/wildfly/docs/contrib/scripts/init.d/wildfly-init-debian.sh /etc/init.d/wildfly
sudo update-rc.d wildfly defaults
copiamo il file di configurazione delle variabili di ambiente sotto la cartella default
sudo cp /opt/wildfly/docs/contrib/scripts/init.d/wildfly.conf /etc/default/wildfly
decommentiamo le seguenti variabili d’ambiente
vim /etc/default/wildfly
## Location of WildFly
JBOSS_HOME=”/opt/wildfly”## The username who should own the process.
JBOSS_USER=wildfly## The mode WildFly should start, standalone or domain
JBOSS_MODE=standalone## Configuration for standalone mode
JBOSS_CONFIG=standalone.xml## Configuration for domain mode
# JBOSS_DOMAIN_CONFIG=domain.xml
# JBOSS_HOST_CONFIG=host-master.xml## The amount of time to wait for startup
STARTUP_WAIT=60## The amount of time to wait for shutdown
SHUTDOWN_WAIT=60## Location to keep the console log
JBOSS_CONSOLE_LOG=”/var/log/wildfly/console.log”
A questo punto possiamo utilizzare i classici strumenti per avviare e fermare il servizio
service wildfly start
service wildfly stop
