Product Documentation

    Before starting these steps, ensure no traffic is being sent to the SAKA having its FQDN changed. This process will stop Payara on that node, change the FQDN on that node, reboot the node, and afterwards restart Payara on all other nodes. Before starting this process, be sure a plan is pared for restarting each node (one at a time is fine).

    To change the IP address after the appliance is in production, perform these tasks:

    1. Login as the root user into the appliance—either on the console directly or using SSH;

    2. Stop Payara with the following:

      shell> systemctl stop payara

    3. Update your DNS master to reflect the new FQDN of the appliance, and propagate it to your network. Verify that the new name is visible using dig on Linux or nslookup on Windows and UNIX-like operating systems. Alternatively (or additionally), update the /etc/hosts file on all SAKA servers in the cluster to update the FQDN for this host.

    4. Make a copy of the /etc/hostname file (in case you need to reverse your changes).

    5. Edit the hostname file with a text editor and modify the content with the appropriate value. Save the file after the changes.

    6. Using the hostname command on the command line, change the FQDN of the appliance:

      hostnamectl set-hostname <new hostname>

    7. From a remote PC, SSH into the appliance using the new FQDN. if it connects, the changes are successful at the network layer. If unable to connect, retrace the steps and correct any errors; if still having trouble, contact a network administrator for help.

    8. Once connected to the appliance, change directory to /usr/local/software/saka.

    9. Execute the script change-fqdn.sh, supplying the SID and the FQDN of this appliance. You will be prompted to generate a new self signed certificate. Example:

      /change-fqdn.sh 1 saka02.company.com

    10. Reboot the appliance.

    11. Each other appliance in the cluster will need to run change-fqdn.sh using the same input parameters of SID and FQDN, with the exception that you will not be prompted to generate a new keystore.

    12. After running the script, Payara needs to be restarted before replication will be able to properly connect to the appliance which had its FQDN changed