Configuring the WildFly Slave

To perform this step, you will have done the preceeding steps on the Master Node and copied over the %PROGRAM_FILES%\Ubisecure\customerid folder to the Slave Node. When this is done, copy the win32.config file from the master node and deposit it in the path %PROGRAM_FILES%\Ubisecure\customerid\application\win32.config.

Modify the value proxy.local.url so it has the FQDN or IP address of this specific host, then perform the setup.cmdMake sure that Wildfly service is up and running

net start wildfly

WildFly comes configured with unnecessary configuration options that we will not use. The following script will remove them so that the relevant configuration options can be managed more easily without extra clutter.

cd /D %PROGRAMFILES%\ubisecure\customerid\application
start notepad win32.config
setup.cmd

Make sure that Wildfly service is up and running

net start wildfly

tools
config-wildfly-domain-prepare.cmd

When the previous script has finished, run the config-wildfly-domain-slave.cmd. This will transform the local domain installation to a slave node and connects it to the domain master that was configured earlier.

At least under slow connections the script may show error message "Failed to establish connection in 6044ms" when reloading configurations. If you see it in the end-of-the script it is a good idea to verify your slave node Wildfly is running properly and can access the master node.

cd %PROGRAMFILES%\ubisecure\customerid\tools
config-wildfly-domain-slave.cmd

...