How to change the default port for a cluster's Management Traffic

Introduction

By default, the Fusion Application Server (FAS) cluster binds to port 9999 for management traffic, which is used by the JBoss CLI, the Management Console and for communication between the master and slave nodes.

Although a custom port can be defined at install time, the instructions below show how to change this default value post-install.

Master and Slave Nodes

Master Node

The host.xml file, which resides within the <FAS_INSTALL_DIR>/domain/configuration/ folder, defines the management port that the master node will use.

This is the only file that needs to be updated on the master node, as per the steps below.

Slave Node(s)

This host.xml file resides within the <FAS_INSTALL_DIR>/domain/configuration/ folder. It defines the default configuration used by the slave node to communicate with the master node.

On installation of each slave node, the FAS installer populates the fas.properties file (which also resides within the <FAS_INSTALL_DIR>/domain/configuration/ folder) with entries that override the defaults defined in the host.xml.

These are the only 2 files that needs to be updated on each slave node, as per the steps below.

Changing the Port

1. Stop all the servers in the cluster
2. On ALL nodes within the cluster, edit the <FAS_INSTALL_DIR>/domain/configuration/host.xml file
3. Replace the references to the default port (9999) to the required custom port
4. On ONLY the slave nodes, edit the <FAS_INSTALL_DIR>/domain/configuration/fas.properties file
5. Replace the reference to the default port (9999) to the required custom port - This will be against the property named:  jboss.domain.master.port
6. Restart all the nodes within the cluster

From this point onwards, the management traffic will be conducted over the new custom port.