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.
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.
Download and unzip wildfly within the quickstart. Execute startwildfly and then create a user.
Once created, head over to localhost:8080 and log in to the admin console.
Wildfly comes with a bunch of configurations. We run a stripped down jboss 5. We probably want a stripped down wildfly. Do we use the mimimalist version? Do we strip it down ourselves?
For the moment using the full standalone version and adding stuff to standalone.xml
Startup shell script can set runtime properties to configure the system - as it does with jboss 5.
Many configurations run with Apache as a front end using ajp to communicate with bedework. Wildfly does not have ajp enabled by default. To do so make the following changes.
Add an ajp listener to the undertow config in standalone.xml
Add a socket binding for ajp on port 8009 also in standalone.xml (it may already be present)
Download and deploy the hawtio war. This provides us with a jmx console. Rename downloaded file as hawtio.zip.
Remove the log4j config:
zip -d hawtio.war WEB-INF/classes/log4j.properties
Add system properties to enable authentication
Then add an account:
It's quite possible a site will need to deploy their own to match the version of their database. We can probably add some popular ones to the quickstart but there may be version issues. Current driver jars are probably all compliant - we'll find out I guess.
The documentation DataSource+configuration provides information and links on deploying the drivers and editing the config.
A script is provided in bedework/config/datasources under each of the database names, for example bedework/config/datasources/postgresql/wildfly-add-driver.txt
Take a copy of this script and run the jboss-cli to deploy your jar. You may need to delete the module if you wish to upgrade.
When loaded wildfly claims the postgresql-9.3 driver to be non-JDBC-compliant. It does, however, contain the file described in the documentation and it does recognize the driver class.
The jboss documentation has this to say:
Note on MySQL driver and JDBC Type 4 compliance: while the MySQL driver (at least up to 5.1.18) is designed to be a Type 4 driver, its jdbcCompliant() method always return false. The reason is that the driver does not pass SQL 92 full compliance tests, says MySQL. Thus, you will need to install the MySQL JDBC driver as a module (see below).
Presumably the same is true of the postgresql driver.
It appears that if the exampleds is removed from the configuration deployment of the postgresql driver and datasources fails.
(Wildfly 8 note) Also the above method seems unreliable in that intermittently wildfly refuses to start because of a damaged deployment. Other deployment approaches might be more reliable.
Bedework is currently being run on postgresql, mysql, oracle and possibly sqlserver.
Using the console seems to be reasonably easy if repetitive. The following datasources are required:
Add a datasource for selfreg - even if it's not being used. We may need that to handle roles - see below
There is a script and a set of properties - one for each datasource and each database type - in the quickstart config directory. Take a copy of the properties and modify them with the correct url, id and password for your site, Then run the cli as follows
Do this for each datasource you want to deploy.
Note - there appears to be a bug in the cli - it gets a string range error if you try to provide a null password. Give it one and then edit the resulting configuration.
Wildfly comes with a fairly old version of h2. Navigate down to modules/system/layers/base/com/h2database/h2/main and replace the jar and update the module.xml file appropriately.
Wildfly comes with a relatively old versioon of hibernate. Install a later moduel by downloading from http://central.maven.org/maven2/org/hibernate/hibernate-orm-modules/5.2.5.Final/hibernate-orm-modules-5.2.5.Final-wildfly-10-dist.zip
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
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"/>
Then build and deploy the selfreg module
Because of issues with naming conventions the sysevents module optionally uses jmx to get its configuration. If that fails it falls back on sysevents.properties. That option will be removed from 4.0. It is there to preserve compatability with the jboss5 version.
Change the value of the system property:
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.
The bedenote (to be renamed to bwmsg) module uses camel to provide the activemq features that were used in jboss, mostly virtual destinations. We are now able to use the standard wildfly jms system.
Particularly useful for debugging. Go to the cli tool and enter the following:
Needed before the calendar engine can be built
Build bedework and specify the wildfly properties file
The post build deployer will remove the jboss-service.xml file from the ear as that is no longer appropriate.
Copy or deploy the exploded ear into the deployment directory and create a .dodeply:
Does this make sense?
Needs the following in web.xml - don't know at the moemnt if it works in jboss 5
without this we get forbidden
At that point it seems to deploy correctly and we can log in.