Running the wildfly quickstart

Some of the configuration and deployment has already taken place.

First download the quickstart and unzip it.

cd into the quickstart

Set JAVA_HOME to a 1.8 or later JDK and then

./startwildfly -heap 2G -debug

You will need to create an administration account for hawtio. To do this you will use the wildfly administration tool.

Then add an account:

./bin/add-user.sh 

What type of user do you wish to add?
 a) Management User (mgmt-users.properties)
 b) Application User (application-users.properties)
(a): b

Enter the details of the new user to add.
Using realm 'ApplicationRealm' as discovered from the existing property files.
Username : hawtio-admin
Password recommendations are listed below. To modify these restrictions edit the add-user.properties configuration file.
 - The password should not be one of the following restricted values {root, admin, administrator}
 - The password should contain at least 8 characters, 1 alphabetic character(s), 1 digit(s), 1 non-alphanumeric symbol(s)
 - The password should be different from the username
Password :
Re-enter Password :
What groups do you want this user to belong to? (Please enter a comma separated list, or leave blank for none)[  ]: admin
About to add user 'hawtio-admin' for realm 'ApplicationRealm'
Is this correct yes/no? yes
Added user 'hawtio-admin' to file '/Users/xxx/dev/eap/wildfly-10.1.0.Final/standalone/configuration/application-users.properties'
Added user 'hawtio-admin' to file '/Users/xxx/dev/eap/wildfly-10.1.0.Final/domain/configuration/application-users.properties'
Added user 'hawtio-admin' with groups admin to file '/Users/xxx/dev/eap/wildfly-10.1.0.Final/standalone/configuration/application-roles.properties'
Added user 'hawtio-admin' with groups admin to file '/Users/xxx/dev/eap/wildfly-10.1.0.Final/domain/configuration/application-roles.properties'
Is this new user going to be used for one AS process to connect to another AS process?
e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server EJB calls.
yes/no? no

JDBC Drivers.

You will probably need to deploy your own to match the version of their database. 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.

Deploying the driver - an example:

Start wildfly
cd into the bin directory
./jboss-cli.sh --file=path-to-your-script

Datasources

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:

1. java:CardDS - for CardDAV address books (use the hsql service if you don't use them)
2. java:CalendarDS - for the main calendar engine
3. java:EventregDS - for the event registration system
4. java:NotifyDS - for the notification engine
5. java:selfregDS - for the self-registration system
6. java:SynchDS - for the synchronization engine

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

./jboss-cli.sh --file=path-to-your-quickstart/bedework/config/datasources/wildfly-create.txt --properties=your-properties-file

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.