How To Install WildFly 18.0.1.Final & Connecting to Eclipse IDE on Ubuntu 19.04

What is WildFly ?

WildFly/JBoss is a Java Server used for the development of Java Projects and provides most of the features and being used by the Enterprises for its better performance & almost all features required. So mostly it is used by main Enterprises as compared to its competitors like Apache, Tomcat, Glassfish, Jetty. Other servers do not provides the all features needed but all of them provides most of the enterprise features. WildFly is the community edition & JBoss is the enterprise edition. JBoss is more secure but both are provided by Redhat Inc. So we recommend WildFly & we’re going to Install it on Our Ubuntu system today. So , follow the steps to proceed further.
First of all you must have installed Java.

java -version

Install WildFly 18 on Ubuntu 19.04

Download the WildFly 18 & choose the location to install it .

mkdir -p ~/sabi/servers
cd ~/sabi/servers
wget https://download.jboss.org/wildfly/18.0.1.Final/wildfly-18.0.1.Final.zip
unzip wildfly-18.0.1.Final.zip

Now add an admin to manage some sources (data sources).

cd wildfly-18.0.1.Final/bin/
./add-user.sh 

Fill the required details.

Now, start WildFly server instance in standalone as shown below:

$ ./standalone.sh
 JBoss Bootstrap Environment
 JBOSS_HOME: /home/sabi/sabi/servers/wildfly-18.0.1.Final
 JAVA: java
 JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true  --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED
 =========================================================================
 22:16:09,321 INFO  org.jboss.modules JBoss Modules version 1.9.1.Final
 22:16:12,711 INFO  org.jboss.msc JBoss MSC version 1.4.11.Final
 22:16:12,775 INFO  org.jboss.threads JBoss Threads version 2.3.3.Final
 22:16:13,655 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 18.0.1.Final (WildFly Core 10.0.3.Final) starting
 22:16:24,470 INFO  [org.wildfly.security] (ServerService Thread Pool -- 28) ELY00001: WildFly Elytron version 1.10.4.Final
 22:16:29,899 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 22:16:30,156 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 9) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 22:16:30,795 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 22:16:31,359 INFO  [org.xnio] (MSC service thread 1-2) XNIO version 3.7.3.Final
 22:16:31,539 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.7.3.Final
 22:16:31,744 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 51) WFLYCLINF0001: Activating Infinispan subsystem.
 22:16:31,875 INFO  [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 60) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
 22:16:31,934 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 63) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
 22:16:31,945 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 64) WFLYNAM0001: Activating Naming Subsystem
 22:16:32,121 INFO  [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 61) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
 22:16:32,449 INFO  [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 62) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem
 22:16:32,110 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 52) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
 22:16:32,444 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 70) WFLYSEC0002: Activating Security Subsystem
 22:16:32,442 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 72) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
 22:16:32,707 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 58) WFLYJSF0007: Activated the following JSF Implementations: [main]
 22:16:32,760 INFO  [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.3.Final
 22:16:32,808 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 74) WFLYWS0002: Activating WebServices Extension
 22:16:32,803 INFO  [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.17.Final)
 22:16:33,440 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 43) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
 22:16:33,835 INFO  [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 5.0.15.Final
 22:16:34,139 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 53) WFLYRS0016: RESTEasy version 3.9.1.Final
 22:16:34,343 INFO  [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
 22:16:34,347 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2
 22:16:34,358 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
 22:16:34,802 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 2.0.27.Final starting
 22:16:35,888 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0014: Creating file handler for path '/home/sabi/sabi/servers/wildfly-18.0.1.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
 22:16:36,574 INFO  [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 32 (per class), which is derived from thread worker pool sizing.
 22:16:36,574 INFO  [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 8 (per class), which is derived from the number of CPUs on this host.
 22:16:37,074 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
 22:16:37,106 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
 22:16:37,366 INFO  [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0493: EJB subsystem suspension complete
 22:16:37,590 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
 22:16:37,838 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
 22:16:39,388 INFO  [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
 22:16:39,484 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore /home/sabi/sabi/servers/wildfly-18.0.1.Final/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
 22:16:39,572 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory /home/sabi/sabi/servers/wildfly-18.0.1.Final/standalone/deployments
 22:16:40,643 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
 22:16:41,897 INFO  [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.3.0.Final (Apache CXF 3.3.3) 
 22:16:42,402 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
 22:16:42,418 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
 22:16:42,418 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
 22:16:42,419 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 18.0.1.Final (WildFly Core 10.0.3.Final) started in 35444ms - Started 315 of 577 services (369 services are lazy, passive or on-demand)

You can access the web management interface during the running of WildFly server by visiting http://localhost:9990/console. Provide the Authentication details to access Dashboard.

Now you can easily create, manage & configure datasources, deployments & server respectively.

Adding WildFly 18 to Eclipse IDE

Navigate to Help>Install New software..> Work with:

Add JBoss Tools Plugin

Name: JBoss Tools

Location: http://download.jboss.org/jbosstools/photon/development/updates/

Choose the feature you want to Install & click finish.

After it, restart and click on the server tab.

First time it will be blank with a link to create a new server. Click on the link and configure the server.

Choose WildFly 18 from the JBoss Community.

Click Next.

Set the Home directory of installed WildFly.

Click Finish.

Testing WildFly 18 to Eclipse IDE integration

For testing purposes create a simple project.

You’ll see that you’ve successfully created new project & the server is ready to use from now on your upcoming projects.

If have any queries regarding this tutorial, feel free to ask in comment section!