Two node slave WildFly configuration on Windows - CustomerID

Configuring the WildFly Slave


Make 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\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

This web page (including any attachments) may contain confidential, proprietary, or privileged information – not for disclosure without authorization from Ubisecure Inc. Copyright © 2024. All Rights Reserved.