eXo Platform 5.0 integrates with JBoss EAP 7.0.
Have JBoss EAP 7.0 extracted in
You can download and install JBoss EAP 7.0 by following instructions on this link.
Have the eXo Platform package for JBoss EAP downloaded into your local.
Installing eXo Platform on JBoss EAP
Extract your downloaded eXo Platform package.
Copy all extracted folders and files into
This step will overwrite some files of JBoss EAP with new files of eXo Platform.
Optionally, if you want to customize the JVM Options, create a copy of
$PLATFORM_JBOSS_HOME/bin/standalone-customize.sample.conf on Linux
$PLATFORM_JBOSS_HOME/bin/standalone-customize.sample.conf.bat on Windows.
Rename the copy to
standalone-customize.conf.bat on Windows), then edit it with your JVM Options.
Start up the server.
On Linux and OS X:
The server starts up successfully when you see the following message in your log/console:
INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) started in 256780ms - Started 4206 of 4787 services (877 services are lazy, passive or on-demand)
Shut down the server.
On Linux and OS X:
$PLATFORM_JBOSS_HOME/bin/jboss-cli.sh --connect command=:shutdown
%PLATFORM_JBOSS_HOME%\bin\jboss-cli.bat --connect command=:shutdown
The server stops successfully when you see the following message in your log/console:
INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) stopped in 13470ms
Since JBoss EAP 6.3, there is a new blocking timeout property for JBoss startup.
This property is not a timeout per deployment but a timeout on container stability and if
jboss.as.management.blocking.timeout is reached during startup then all applications will be undeployed and the container shutdown.
The default value is set to 300s which is too low for eXo Platform in which we overrode the value.