Configure Hybrid Connection Manager

Your Schneider Electric implementation team handles this preparation step.

In most cases, Microsoft’s Hybrid Connection Manager (HCM) is required for an open channel of communication between the Work Management System Integration (WMSI) App Service and ArcFM Session Manager Function app (both of which live in Schneider Electric’s Azure portal) and your client-hosted services like ArcGIS Portal and on-site Designer XI Design Storage services. To enable this open channel, the HCM service must be installed on the same server as ArcGIS Server is installed. Most likely, this is the same server where the Designer XI network feature services are running. Depending upon your environment and organization, it might make sense to install HCM on a different server, but that server must have access to the server on which the ArcGIS Server instance is running, as well as the server on which the Designer XI Design Storage service is running, if not hosted by Schneider Electric. 

Good to Know

The following information is good to know during this process:

• HCM is configured in Solution Center. See the help topic Hybrid Connections for more information.

• As stated above, the HCM service must be installed on the same server as ArcGIS Server is installed. If the implementation team is granted the appropriate permissions, they can perform this step. If permissions cannot be granted to the implementation team, somebody at your company with the appropriate permissions needs to perform this installation. Further, the same people responsible for installing HCM need to configure it with the appropriate connections strings once those strings are made available.

• A hybrid connection is needed for each unique host machine. If your on-premises design storage service is on the same machine as the network feature service, you need one hybrid connection. If the two services are hosted on separate machines, you need a hybrid connection for each, and these two connections should reside in a relay within your respective Azure resource group.