Installare WildFly 9 su Centos6

WildFly, precedentemente noto come JBoss AS o semplicemente JBoss, è un Application Server open source che implementa le specifiche Java EE.
WildFly è un sistema multipiattaforma, interamente realizzato in Java.

Prerequisito installare JDK 
JDK = java development kit
Per verificare se java è installato, eseguire il comando:
[root@coslab02 conf.d]# java -version
java version "1.7.0_191" OpenJDK Runtime Environment (rhel-2.6.15.4.el6_10-x86_64 u191-b01) OpenJDK 64-Bit Server VM (build 24.191-b01, mixed mode)

Per trovare la directory di installazione di java:
[root@coslab02 ~]# which java
/usr/bin/java
[root@coslab02 ~]# ll /usr/bin/java
lrwxrwxrwx. 1 root root 22  6 set  2018 /usr/bin/java -> /etc/alternatives/java
[root@coslab02 ~]# ll /etc/alternatives/java
lrwxrwxrwx. 1 root root 46  6 set  2018 /etc/alternatives/java -> /usr/lib/jvm/jre-1.7.0-openjdk.x86_64/bin/java

La JAVA_HOME è /usr/lib/jvm/jre-1.7.0-openjdk.x86_64


Effettuare il download di wildfly sotto la directory /opt
Collegarsi a https://wildfly.org/downloads/
Cliccare con il pulsante destro sul file zip di di Java EE Full & Web Distribution della versione 9.2 e copiare il link.



[root@coslab02 opt]# wget https://download.jboss.org/wildfly/9.0.1.Final/wildfly-9.0.1.Final.zip

Unzippare il file
#unzip wildfly-9.0.1.Final.zip

[root@coslab02 opt]# ls -lrt
drwxr-xr-x. 10 root root      4096 23 lug  2015 wildfly-9.0.1.Final
-rw-r--r--.  1 root root 133617224 24 lug  2015 wildfly-9.0.1.Final.zip

Creare l'utente
[root@coslab02 opt]# useradd -s /bin/bash wildfly

Cambiare la password
[root@coslab02 wildfly]# passwd wildfly


Crea un link simbolico a wildfly
[root@coslab02 opt]# ln -s /opt/wildfly-9.0.1.Final /opt/wildfly
[root@coslab02 opt]# ls -lrt
drwxr-xr-x. 10 root root      4096 23 lug  2015 wildfly-9.0.1.Final
lrwxrwxrwx.  1 root root        24  7 ott 15:59 wildfly -> /opt/wildfly-9.0.1.Final

Cambiare il proprietario
[root@coslab02 opt]# chown -R wildfly:wildfly wildfly-9.0.1.Final

[root@coslab02 opt]# ls -lrt
drwxr-xr-x. 10 wildfly wildfly 4096 23 lug  2015 wildfly-9.0.1.Final
lrwxrwxrwx.  1 root    root      24  7 ott 15:59 wildfly -> /opt/wildfly-9.0.1.Final


Esportare nel batch profile dell'utente wildfly la variabile JAVA_HOME.
cd /home/wildfly
[root@coslab02 wildfly]# ls -lart
totale 24
-rw-r--r--. 1 wildfly wildfly  124 23 mar  2017 .bashrc
-rw-r--r--. 1 wildfly wildfly  176 23 mar  2017 .bash_profile
-rw-r--r--. 1 wildfly wildfly   18 23 mar  2017 .bash_logout
-rw-r--r--. 1 wildfly wildfly  171 13 mar  2018 .kshrc

[root@coslab02 wildfly]# vi .bash_profile
JAVA_HOME=/usr/lib/jvm/jre-1.7.0-openjdk.x86_64
export JAVA_HOME
PATH=$JAVA_HOME/bin:$PATH
export PATH

[root@coslab02 wildfly]# .  ./.bash_profile

Come verifica accedere come wildfly e controllare la versione di java sia la stessa visibile come root.
[root@coslab02 wildfly]# su - wildfly
[wildfly@coslab02 ~]$ java -version
java version "1.7.0_191"
OpenJDK Runtime Environment (rhel-2.6.15.4.el6_10-x86_64 u191-b01)
OpenJDK 64-Bit Server VM (build 24.191-b01, mixed mode)


Eseguire wildfly come un servizio

[root@coslab02 init.d]# cp /opt/wildfly/bin/init.d/wildfly-init-redhat.sh   /etc/init.d/wildfly

Dar i permessi allo script
[root@coslab02 init.d]# chmod 755 wildfly



Creare la directory contenente il PID file per il servizio wildfly
mkdir /var/run/wildfly/
chown -R wildfly:wildfly /var/run/wildfly/

Copiare il file di configurazione di wildfly sotto /etc/deafult e modificarlo.
[root@coslab02 bin]# cp /opt/wildfly/bin/init.d/wildfly.conf    /etc/default/

Fare le seguenti modifiche:
vi wildfly.conf

## Location of JDK
JAVA_HOME="/usr/lib/jvm/jre-1.7.0-openjdk.x86_64"
## 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
## 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"
# Location of lockfile on redhat
JBOSS_LOCK="/var/lock/subsys/wildfly"


Per rendere Wildfly accessibile dall'esterno cambiare 127.0.0.1 in 0.0.0.0 nel seguente file.

vi /opt/wildfly/standalone/configuration/standalone.xml

<interface name="management">
            <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
        </interface>
        <interface name="public">
            <inet-address value="${jboss.bind.address:127.0.0.1}"/>
        </interface>
        <!-- TODO - only show this if the jacorb subsystem is added  -->
        <interface name="unsecure">
            <!--
              ~  Used for IIOP sockets in the standard configuration.
              ~                  To secure JacORB you need to setup SSL
              -->
            <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
        </interface>
    </interfaces>


Creare la directory
mkdir /opt/wildfly/standalone/tmp/vfs/temp
chown -R wildfly:wildfly opt/wildfly/standalone/

cd /opt/wildfly/standalone/configuration/
chown -R wildfly:wildfly standalone_xml_history


Aggiungere un utente che sia abilitato ad accedere alla console di amministratore.

[root@coslab02 bin]# cd /opt/wildfly/bin
[root@coslab02 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
Enter the details of the new user to add.
Using realm 'ManagementRealm' as discovered from the existing property files.
Username : wildfly
Password :
Re-enter Password :
What groups do you want this user to belong to? (Please enter a comma separated list, or leave blank for none)[  ]:
About to add user 'wildfly' for realm 'ManagementRealm'
Is this correct yes/no? yes
Added user 'wildfly' to file '/opt/wildfly-9.0.1.Final/standalone/configuration/mgmt-users.properties'
Added user 'wildfly' to file '/opt/wildfly-9.0.1.Final/domain/configuration/mgmt-users.properties'
Added user 'wildfly' with groups  to file '/opt/wildfly-9.0.1.Final/standalone/configuration/mgmt-groups.properties'
Added user 'wildfly' with groups  to file '/opt/wildfly-9.0.1.Final/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? y
To represent the user add the following to the server-identities definition <secret value="d2lsZGZseTIyIQ==" />


[root@coslab02 default]# service wildfly start
Starting wildfly:

Se vogliamo lo start automatico del servizio al boot della macchina
chkconfig --add wildfly
chkconfig wildfly on

Verifica
http://<indirizzo ip>:8080


Cliccare su "Administration Console"



Alla console di amministrazione si può accedere direttamente dalla url seguente.
http://<indirizzo ip>:9990

Inserire l'utente definito precedentemente per accedere alla console di amministratore.



Log
/opt/wildfly/standalone/log/server.log
/var/log/wildfly/console.log


Post popolari in questo blog

ORA-12154: TNS: il listener non è attualmente a conoscenza del servizio richiesto nel descrittore di connessione

Funzione TO_DATE

CREATE DATABASE LINK