On our CentOS 7.1 Linux machine, we would like to install WildFly 9.0.2 running on Java 8

Java 8 SDK installation

Get Java SDK from Oracle, then copy it to your Linux CentOS machine :

[root@wildfly tmp]# ls -l jdk-8u65-linux-x64.rpm
-rw-r--r--. 1 root root 160102255 Dec 2 11:14 jdk-8u65-linux-x64.rpm

And install it :

[root@wildfly tmp]# rpm -ivh jdk-8u65-linux-x64.rpm
Preparing...                        ################################# [100%]
Updating / installing...
   1:jdk1.8.0_65-2000:1.8.0_65-fcs  ################################# [100%]
Unpacking JAR files...
        tools.jar...
        plugin.jar...
        javaws.jar...
        deploy.jar...
        rt.jar...
        jsse.jar...
        charsets.jar...
        localedata.jar...
        jfxrt.jar...

Your Java8 is here :

[root@wildfly tmp]# type java
java is hashed (/usr/bin/java)
[root@wildfly tmp]# java -version
java version "1.8.0_65"
Java(TM) SE Runtime Environment (build 1.8.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.65-b01, mixed mode)

WildFly 9.0.2 installation

Download WildFly 9.0.2 final from www.wildfly.org, then copy it to your Linux CentOS machine :

[root@wildfly tmp]# ls -l wildfly-9.0.2.Final.tar.gz
-rw-r--r--. 1 root root 135659070 Dec 2 10:55 wildfly-9.0.2.Final.tar.gz

Uncompress this archive :

[root@wildfly tmp]# gunzip wildfly-9.0.2.Final.tar.gz

Create a a file system or a directory and untar this file inside,

[root@wildfly tmp]# mkdir /wildfly
[root@wildfly tmp]# cd /wildfly
[root@wildfly wildfly]# tar xf /tmp/wildfly-9.0.2.Final.tar

Start WildFly

Go to the distribution directory :

[root@wildfly wildfly]# cd wildfly-9.0.2.Final

By default “localhost” is used to manage WildFly, to change it :

  • Backup the original “standalone.xml” configuration file :
[root@wildfly wildfly-9.0.2.Final]# cp -p ./standalone/configuration/standalone.xml ./standalone/configuration/standalone.xml.old
  • Replace old localhost binding addresses :
  <interfaces>
    <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>
  • by :
  <interfaces>
    <interface name="management">
      <any-address/>
    </interface>
    <interface name="public">
      <any-address/>
    </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
      -->
      <any-address/>
    </interface>
  </interfaces>

Launch this command (here WildFly is listening on all interfaces) :

[root@wildfly wildfly-9.0.2.Final]# ./bin/standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /wildfly/wildfly-9.0.2.Final
JAVA: java
JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
...
...
...
11:34:21,200 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://0.0.0.0:9990
11:34:21,200 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) started in 7711ms - Started 203 of 379 services (210 services are lazy, passive or on-demand)

You can now open a WEB brower on port 8080 :

WildFly

 

 

 

 

 

 

 

 

 

 

 

 

 

Open another WEB browser on port 9990 :

WildFly1

 

 

 

 

 

 

 

 

 

 

Create a user account, for example :

[root@wildfly wildfly-9.0.2.Final]# 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):

Enter the details of the new user to add.
Using realm 'ManagementRealm' as discovered from the existing property files.
Username : wou
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 :
WFLYDM0102: Password should have at least 1 non-alphanumeric symbol.
Are you sure you want to use the password entered yes/no? yes
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 'wou' for realm 'ManagementRealm'
Is this correct yes/no? yes
Added user 'wou' to file '/wildfly/wildfly-9.0.2.Final/standalone/configuration/mgmt-users.properties'
Added user 'wou' to file '/wildfly/wildfly-9.0.2.Final/domain/configuration/mgmt-users.properties'
Added user 'wou' with groups to file '/wildfly/wildfly-9.0.2.Final/standalone/configuration/mgmt-groups.properties'
Added user 'wou' with groups to file '/wildfly/wildfly-9.0.2.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? yes
To represent the user add the following to the server-identities definition <secret value="YWdlbnQwMDc=" />

So, you can continue on the WEB page :

WildFly2

 

 

 

 

 

 

 

You have now access to the console :

WildFly3

 

 

 

 

 

 

 

 

 

 

 

 

PDF24    Send article as PDF   

Leave a Reply

Your email address will not be published. Required fields are marked *


*