To connect with SwiftMQ Explorer to a SwiftMQ HA Router, use the SMQP-URL supplied from the HA Wizard (in file "ha_next_tasks.txt") and lookup the connection factory:
SwiftMQ Explorer connects to the ACTIVE HA instance. The STANDBY HA instance is hidden. SwiftMQ Explorer automatically reconnects after a failover and displays the same set of open frames. So it has always a connection to the ACTIVE HA instance.
Configuration changes are automatically replicated to the STANDBY HA instance. It doesn't matter if the STANDBY HA instance is not connected (state STANDALONE). Once it connects, the ACTIVE HA instance replicates the whole configuration to the STANDBY, so both HA instances are always in sync and consistent and configuration changes can be done at any time, no matter if the STANDBY is connected or not.
There are some configuration entities that are bound to the resp. HA instance (e.g. trace settings). These entities are not replicated. The High Availability Controller Swiftlet controls configuration replication. Under Configuration Controller / Replication Excludes is a list of configuration contexts (SQL LIKE predicates) that defines the elements that are excluded from replication. Never change this list! Example:
SwiftMQ Explorer interacts with the Management Swiftlet of the ACTIVE HA instance in a request/reply manner. If a request (e.g. configuration change or viewing queue messages) is issued and a failover occurs before a reply to this request is received, the request will be canceled with a warning message. The request must be issued again after the failover.
SwiftMQ Explorer in HA edition has additional commands to manage both HA instances. These commands are located at the router node and shown in a popup menu on a right mouse click. See below (self-explanatory):
