During the Cloud Pod Architecture initialization process, the Cloud Pod Architecture feature creates a pod federation that contains a single pod. You can use Horizon Console to join additional pods to the pod federation. Joining additional pods is optional.
Global entitlements, global sessions, and federation access groups are replicated from the pods in the pod federation. Connection Server creates federation access group permissions on the root federation access group for all authorized administrators automatically.
Important: Do not stop or start a Connection Server instance while you are joining it to a pod federation. The Connection Server service might not restart correctly. You can stop and start the Connection Server after it is successfully joined to the pod federation.
Prerequisites
- Make sure the Connection Server instances that you want to join have different host names. You cannot join servers that have the same name, even if they are in different domains.
- Initialize the Cloud Pod Architecture feature. See Initialize the Cloud Pod Architecture Feature.
Procedure
Results
After the pod is joined to the pod federation, it begins to share health data. You can view this health data on the dashboard in
Horizon Console. See
Review Pod Federation Health.
Note: A short delay might occur before health data is available in
Horizon Console.
What to do next
You can repeat these steps to join additional pods to the pod federation.