3 years ago

by In the previous article in this series introduced our thoughts on setting up a mission-critical open source Java platform using high availability in our Web layer. In this article we'll continue by installing WildFly and configure our platforms topology. Note: the terminology in this article, where possible, has been adjusted from the traditional master / slave descriptions to master / subordinate.

In this same host-slave.xml file add the secret and user: Edit again the domain.conf file and add the configuration file settings for the JAVA_OPTS variable: Restart the wildfly service: In the “Host Master” logs you can see the “Host subordinate 0” connection log.