This page documents the steps taken to deploy in Wildfly 910.1.0.2-Final. This is not mostly complete and , so far, bedework is not bedework seems to be running on that platform.
This is a set of notes which should turn into instructions for configuration. This is NOT a set of instructions for someone who wishes to run a wildfly quickstart.
These instructions will provide a reference for upgrading to later versions of wildfly.
Startup
Download and unzip wildfly within the quickstart. Execute startwildfly and then create a user.
...
Ajp
Many configurations run wit with Apache as a font front end using ajp to communicate with bedework. Wildfly does not have ajp enabled by default. To do so make the following chnageschanges.
Add an ajp listener to the undertow config in standalone.xml
...
Instructions are at https://docs.jboss.org/hibernate/orm/5.2/topical/html_single/wildfly/Wildfly.html.org/hibernate/orm/5.2/topical/html_single/wildfly/Wildfly.html
SSL
Our experience is running wildfly behind a combination of stunnel and haproxy. I believe the configuration is much the same for running behind apache. The key is that haproxy or apache must add X-Forwarded-For headers to each request.
In our setup we have theses requests come in on port 8081.
In haproxy add the line
option forwardfor
to the defaults section.
In the undertow subsystem configuration add the line:
<http-listener name="stunnel" socket-binding="stunnel" secure="true" redirect-socket="https" proxy-address-forwarding="true" enable-http2="true"/>
and in the socket-binding section add
<socket-binding name="stunnel" port="8081"/>
Selfreg
Then build and deploy the selfreg module
...
There is a system property org.bedework.jmx.isJboss5 which is set in the jboss 5 startup and used by the JMX utility classes in the ManagementContext.registerMBean method. It's unclear if this is needed for wildfly or if it was to address a jboss5 specific issue.
...
At that point it seems to deploy correctly and we can log in.