/
Two node slave WildFly configuration on Linux - CustomerID
Two node slave WildFly configuration on Linux - CustomerID
Modify the value proxy.local.url so it has the FQDN or IP address of this specific host, then perform the setup.sh.
cd /usr/local/ubisecure/customerid/application nano linux.config ./setup.sh
After these steps, run the script config-wildfly-domain-prepare.sh
, which will remove unnecessary options from the host configuration.
cd /usr/local/ubisecure/customerid/tools ./config-wildfly-domain-prepare.sh
When the previous script has finished, run the config-wildfly-domain-slave.sh
. 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 /usr/local/ubisecure/customerid/tools ./config-wildfly-domain-slave.sh
, multiple selections available,
Related content
Two node JDBC data source creation on Windows - CustomerID
Two node JDBC data source creation on Windows - CustomerID
Read with this
Two node upgrade on Windows - CustomerID
Two node upgrade on Windows - CustomerID
Read with this
Two node WildFly installation on Windows - CustomerID
Two node WildFly installation on Windows - CustomerID
Read with this
Two node in-place upgrade on Windows - CustomerID
Two node in-place upgrade on Windows - CustomerID
Read with this
Two node WildFly preparation on Windows - CustomerID
Two node WildFly preparation on Windows - CustomerID
Read with this
Related tasks when upgrading SSO in Windows - CustomerID
Related tasks when upgrading SSO in Windows - CustomerID
Read with this