JOC should show correct status of standalone master when using behind a virtual IP or application load balancer

Current Situation

• Customer has installed 2 JobSchedulers as a standalone instance on two different hosts. Both the Instances has the same JobScheduler Instance ID and share the same JobScheduler and Reporting databases. Both the instances are active and running.
• The INVENTORY_INSTANCES table have two identical records, only difference is HOSTNAME

• ID    OS_ID    SCHEDULER_ID    HOSTNAME         PORT    LIVE_DIRECTORY                                                                 VERSION            COMMAND_URL                URL                            TIMEZONE        CLUSTER_TYPE    PRECEDENCE    DBMS_NAME    DBMS_VERSION    STARTED_AT         SUPERVISOR_ID    AUTH    CREATED    MODIFIED
  1    1    jobscheduler12_4412    EC2AMAZ-D2SBRU6    44412    C:/ProgramData/sos-berlin.com/jobscheduler/jobscheduler12_4412/config/live    1.12.8-SNAPSHOT    EC2AMAZ-D2SBRU6:4412    http://EC2AMAZ-D2SBRU6:44412    Europe/Berlin    standalone         NULL        MySQL         5.5.61        2018-12-19 09:52:30         0               NULL    2018-11-13 09:12:08    2018-12-19 09:52:57
  4    1    jobscheduler12_4412    EC2AMAZ-D2SBRU7    44412    C:/ProgramData/sos-berlin.com/jobscheduler/jobscheduler12_4412/config/live    1.12.8-SNAPSHOT    EC2AMAZ-D2SBRU6:4412    http://EC2AMAZ-D2SBRU6:44412    Europe/Berlin    standalone         NULL         MySQL         5.5.61         2018-12-19 09:52:30     0            NULL    2018-11-13 09:12:08    2018-12-19 09:52:57
   

• See attached screenshot from JOC JOC-654.png
• The customer implemented a fail-over mechanism using Virtual IP/Application load balancer, where all the traffic to and from JOC to JobScheduler is routed through network interface attached to Host1. In the event of Failure of Host1, the Virtual IP/Application load balancer detach the network interface from Host1 and attache it to Host2. For JOC the URL does not change but due to change in the network interface hostname, the Host2 JobScheduler become the active instances.
• The Fail-over mechanism implemented by the customer is not a standard JobScheduler architecture.
• The JOC have no information of such a fail-over being implemented and consider both the JobScheduler as Standalone job schedulers

Desired Behavior

• The JOC Cockpit should show single JobScheduler Instance on the Standalone JobScheduler Master Widget.