This documentation supports the 9.1 version of Remedy IT Service Management Suite.

To view the latest version, select the version from the Product version menu.

Planning the hub and spoke setup

This topic describes issues to plan for before you start configuring the Hub and Spoke capability.

Note

If you experience any problems with the Hub and Spoke capability after you complete the configuration process, check Troubleshooting the Hub and Spoke capability for suggestions on how to solve commonly encountered issues.

Creating companies

Ensure that you finish all of the hub and spoke configuration procedures before you create companies.

Use Hypertext Transfer Protocol Secure (HTTPS)

Recommendation

Set up all connections between the BMC Remedy Mid Tier server and the hub and spoke servers with the Hypertext Transfer Protocol Secure (HTTPS) protocol.

Application permission models

The application permission models on the spoke server must be the same as those on the hub server.

Naming spoke servers

When deciding on spoke server names, be aware of the following points. The name must be reachable:

  • By the spoke mid-tier server
  • From the hub (the hub must be able to use the DSO service for sending information to the spoke)

Use the spoke server name consistently

Use consistent names to identify the spoke servers. For example, if you identify the spoke server by its long name when you register it on the hub server, do not later use the spoke server's short name or its IP address when identifying it to the mid-tier server.

When using a single reverse proxy server

If your environment shares a single reverse proxy server among the hub and spoke servers, always use name based virtual hosting when identifying the hub and spoke servers to the system. Using the context path to identify the servers causes inconsistent system behavior. The following examples illustrate the correct and incorrect method of identifying the hub and spoke servers in your environment:

Name-based virtual hosting (correct)
Hub — https://<Reverse Proxy alias for Hub>/arsys
Spoke — https://<Reverse Proxy alias for Spoke1>/arsys
Spoke — https://<Reverse Proxy alias for Spoke2>/arsys

URL-path-based virtual hosting (incorrect)
Hub — https://<Reverse Proxy Server>/arsys
Spoke — https://<Reverse Proxy Server>/arsys
Spoke — https://<Reverse Proxy Server>/arsys

See Sample configuration of a single reverse proxy server for more information about configuring your system if you use a single reverse proxy server. You must perform the procedure described there after you install and configure the supporting systems.

BMC Remedy Mid Tier server

Each BMC Remedy AR System server spoke environment must have its own, dedicated BMC Remedy Mid Tier server.

Where to go from here

When you finish reading this section, see Installing and configuring the supporting systems.

Was this page helpful? Yes No Submitting... Thank you

Comments