In the Thinfinity Workspace environment, a Secondary Broker serves as an essential load-balancing and redundancy component. It delivers high availability and fault tolerance while working in tandem with the primary broker. The Secondary Broker easily steps in to take over in the case that the primary broker fails or needs maintenance, ensuring that resources are still accessible. It improves load balancing, maximizing system performance, by spreading user requests wisely. Additionally, the geographical redundancy feature of the system can be deliberately used in disaster recovery scenarios to preserve business continuity even in the face of catastrophic events. In short, the Thinfinity Workspace Secondary Broker serves as a robust safety net, protecting the system from interruptions and giving all users access to a stable, responsive, and scalable infrastructure.
You should have this in place before starting:
Thinfinity Workspace Secondary Broker installed.
Thinfinity Workspace Gateway and Primary Broker installed on a separate computer.
In the Primary Broker:
1- First, launch Thinfinity Workspace Configuration Manager.
2- Then, access the 'General' tab and click on 'NetworkID'; copy or take note of the NetworkID for use with the Secondary Broker.
3- Now, in the 'Broker' tab, 'Secondary Brokers' section, add Secondary Broker information to the list by clicking 'Add'.
4- Configure Secondary Broker Pool settings by especifying the Pool Name, Users Limit, and Load Balancing Method. When done, click 'OK' then 'Apply'.
5- Open Thinfinity Workspace Configuration Manager.
6- Confirm it is configured as Secondary Broker in the 'General' tab.
7- Enter the same ‘Pool Name’, ‘NetworkID’, and ‘Gateway’ (IP : Port) used on the Primary Broker.
8- Next, use 'Show Log' button to verify the connection to the Gateway.
9- To do so, check the latest entries in the log for 'Connected', 'Access Granted', and 'Registered' messages.
This will indicate the connection to the Gateway was successful.
You have completed the Secondary Broker Configuration and should now proceed to create the connection with the appropriate protocol.