Creating foundation data for hub and spoke servers
Hub server
The default behavior of a spoke server prevents you from creating or updating Company, Support Group, and People records (or any of their related child records) for any company. However, you can configure a spoke server to let you create and update these record types. If you update a Company, Support Group, or People record on a spoke server that was created on the hub server (for example, a service-provider-company People record), the record is overwritten during the next update of that record from the hub server.
Any transactional data created on the spoke server through the hub server or through a spoke mid-tier server is dynamically synchronized back to the hub server via the DSO service.
On the hub server, create the following data types for the indicated companies.
Data type | For the service provider | For an operating | For a customer |
|---|---|---|---|
Company | Yes | Yes | Yes |
Company alias | Yes | Yes | Yes |
Organization | Yes | No | No |
Location | Yes | No | No |
Support group | Yes | No | No |
People | Yes | No | No |
When adding a new spoke server to an existing hub and spoke system, synchronize the service-provider-specific foundation data with the new spoke server. This synchronization updates the service-provider-company-specific foundation data on the new spoke server.
Operating company names must be unique across the entire hub and spoke environment.
Spoke server
Create the following data types on the spoke server:
Data type | For the service provide | For an operating | For a customer |
|---|---|---|---|
People | Yes | Yes | Yes |
Approval mappings | No | Yes | Yes |
Asset data in the | No | Yes | Yes |
Assignment rules | No | Yes | Yes |
Audit and archive data | No | Yes | Yes |
Business time segments | No | Yes | Yes |
Financial configuration | No | Yes | Yes |
Notifications | No | Yes | Yes |
Product and | No | Yes | Yes |
Risk configuration | No | Yes | Yes |
Rules | No | Yes | Yes |
Service targets | No | Yes | Yes |
Templates | No | Yes | Yes |
Organization | No | Yes | Yes |
Location | No | Yes | Yes |
Support group | No | Yes | Yes |
Although the data listed in the table that follows can also be created on the hub server, you might choose to create the following data types on the spoke server. You might consider this configuration; for example, if you prefer that one or more of these data types resides locally, on the spoke server instead of the hub server.
As with other foundation data that is created on a spoke server, if you create these data types also on a spoke server, the spoke server instances are not visible from the hub server.
Data type | For the service provider | For an operating | For a customer |
|---|---|---|---|
Company | No | Yes | Yes |
Company alias | No | Yes | Yes |
Using the Data Management dataload tool
If you are using the Data Management tool and hub and spoke servers to load foundation, transactional, and process setup data, see Loading Foundation data by using Data Management before you use the Data Management tool.
Where to go from here
This procedure completes the basic hub and spoke server configuration process. However, read Synchronizing foundation data to determine if you also need to perform that procedure.