Actually, I skipped that step because a previous employee had already run the migrator in windows 7 (since windows doesnt have a native shell scripting processor via cmd prompt) using this command he found somewhere: java -classpath ups-migrator.jar -Dliquibase.databaseChangeLogTableName="ups_db _changelog" -Dliquibase.databaseChangeLogLockTableName="ups_db_changeloglock" l iquibase.integration.commandline.Main "--defaultsFile=liquibase.properties" upda te Apparently that worked for him in UPS 1.0.2, but I am trying to do a fresh install to the same mySQL database and I had hoped his migrator run had done the trick but clearly not. What would you recommend I do? I was thinking I would install CYGWIN on the windows box so that I could run the migrator shell script, wipe the database, set up a fresh one as per the tutorial i mentioned above, and then I could run "./bin/ups-migrator --logLevel=DEBUG update" as per your request thoughts? -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Aerogear-UPS-1-0-3-Wildfly-serv... Sent from the aerogear-dev mailing list archive at Nabble.com.

nevermind, instead of using CYGWIN, I simple ran the ups-migrator like so: java -classpath "C:\path_to_jar/ups-migrator.jar -Dliquibase.databaseChangeLogTableName="ups_db_changelog" -Dliquibase.databaseChangeLogLockTableName="ups_db_changeloglock" liquibase.integration.commandline.Main "--defaultsFile=liquibase.properties" update and then rebooted the JBOSS server in order for the keycloak to create the required tables (i.e. realm table etc) after rebooting jboss the numebr of SQL tables increased from 14 to 43. -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Aerogear-UPS-1-0-3-Wildfly-serv... Sent from the aerogear-dev mailing list archive at Nabble.com.