This page documents the steps taken to deploy in Wildfly 10.1.0-Final. This is mostly complete and bedework seems to be running on that platform.
...
Instructions are at https://docs.jboss.org/hibernate/orm/5.2/topical/html_single/wildfly/Wildfly.html
Selfreg
Then build and deploy the selfreg module
...
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
| Code Block |
|---|
./bw -dc bedework/config/wildfly.deploy.properties -wildfly -selfreg |
...
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.