Setting up the hub and spoke capability
Process overview
The following table provides a high-level map of the processes that you must perform to register a hub server and the spoke servers in your environment. Use this process for all registration scenarios.
Task | Reference |
|---|---|
Configure a single reverse proxy server (optional) | |
Configure the Distributed Server option | |
Create DSO logical mappings | |
Register the hub and spoke servers (on the hub server) | |
Run the Prefix Manager utility (on the individual servers) | |
On the hub server, create Service Provider company and foundation data (The DSO pushes this data to all spoke servers.) | |
On the hub server, create all the spoke server companies and their data (The DSO service sends this data to the appropriate spoke servers.) | |
When you add a new spoke server to the hub and spoke environment, synchronize the service provider foundation data with the new spoke server |
Maintaining spoke servers
The DSO service dynamically synchronizes all of the information created on the hub server with the spoke servers, except when you are adding a new spoke server to an existing hub and spoke system. Adding a new spoke server to an existing system requires synchronization.
Task | Reference |
|---|---|
To rename a spoke server | |
To de-register a spoke server when the operating company no longer needs to consume services from the service provider company on the hub server | |
To push the service provider company specific foundation data records from the hub server to a new spoke server |