Has anyone had any experience with load balancing Airwatch’s AWCM component? We have an on-premise installation and currently our two AWCM servers are setup in an active/failover manner. As we are migrating to a software load balancer (haproxy), we’d also like to have this switched to have both of the servers being active. According to the Airwatch documentation, persistence is based on a parameter awcmsessionid in either the URI or the http header. They even go a step further to explain how this can be accomplished, if we were using F5.
That being said, based on the information in the following article, can anyone provide details on how to begin with this, or if it’s even possible?