Setting up the hub and spoke capability
A hub and spoke environment is a logical topology that allows a single service provider company that is residing on the hub server to support multiple operating companies that are residing each on their own spoke server.
As an administrator, you configure and set up the hub and spoke servers. Also, you create and synchronize foundation data. You perform the various registration and any ongoing administration functions on hub or spoke servers and maintain a hub and spoke system. The hub server and the spoke server runs with AR System, BMC Helix CMDB, and the the BMC Helix ITSM applications.
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) | Configuring a single reverse proxy server for hub and spoke |
Configure the Distributed Server option | Configuring the Distributed Server Option service for a hub and spoke system |
| Create DSO logical mappings | Mapping the servers' logical and physical names |
Register the hub and spoke servers (on the hub server) | Registering hub and spoke servers |
Run the Prefix Manager utility (on the individual servers) | Running the Prefix Manager |
On the hub server, create Service Provider company and foundation data (The DSO pushes this data to all spoke servers.) | Creating foundation data for hub and 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.) | Creating foundation data for hub and 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 | Synchronizing foundation data from the hub server to a 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 | Renaming 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 | De-registering a spoke server |
| To push the service provider company specific foundation data records from the hub server to a new spoke server | Synchronizing foundation data from the hub server to a new spoke server |
Comments
Log in or register to comment.