Troubleshooting the hub and spoke capability

Make sure that the Distributed Server Option (DSO) service is running on the hub server.

For information about implementing the DSO service, see Setting up DSO to synchronize data across multiple AR System servers .

Make sure that the DSO service on the hub server can communicate with the spoke server.

For information about implementing the DSO service, see Setting up DSO to synchronize data across multiple AR System servers .

The Key Map form on the hub server does not contain a record for the spoke server and the following message is displayed.

AR System Key Map contains no records for the hub or spoke servers


You open the AR System server to Key Map form on the hub server after successfully entering the web path information on a spoke server.

Make sure that the DSO service on the spoke server can communicate with the hub server.

• For information aboutAR System server to Key Map form, see  Securing DVM communication .
• For information about implementing the DSO service, see  Setting up DSO to synchronize data across multiple AR System servers .

The BMC Helix ITSM applications used for the hub and spoke capability communicate with the Mid Tier server.

By default, the BMC Helix ITSM applications that are used for the hub and spoke capability are not set up to use the Hypertext Transfer Protocol Secure (HTTPS) protocol when they communicate with the Mid Tier server.

Set up all hub and spoke connections to the Mid Tier by using the HTTPS protocol. If you do not set the connections, each time a user opens a spoke record on the hub server, the following message appears in the browser window:

For enhanced security, BMC advises using HTTPS protocol for the current mid tier server and for Web Path of the remote server <serverName> (ARWARN 9508)