Desktop Intelligence Client Failover in DR
We are trying to come up with an strategy to failover the Desktop Intelligence Client XI R3 in a disaster recovery situation. We haven't found any proper disaster recovery documentation or any details on how to achieve high availability in R3. Any ideas where and when this will be available?
Also while on this question we noticed the Desktop Intelligence Client doesn't seem to like connecting to the CMS server via a VIP, which is very unfortunate. We run our CMS services on a specific port and want to hide the machine and port information from our users so that instead of using something like this "lonrs00845:16525" they could just use a more friendly name such as "mi-bo-dev-env1". The error we get is this:
[repo_proxy 13] SessionFacade::openSessionLogon with user info has failed(Unable to connect to CMS mi-bo-dev-env1:6400. A wrong connection is made to @@lonrs00845:16525(lonrs00845:16525). Logon cannot continue.(hr=#0x80042a79)
mi-bo-dev-env1 is our VIP which forwards all requests in port 6400 to a physical machine lonrs00845 on port 16525 which is the CMS port. It seems the Deski client is aware of the port redirection and doiesn't like it. If this kind of port re-direction is not supported then how are we supposed to failover Deski clients? Sure there must a better way than having to telling all your users to change their connection string to connect to the DR server...
Tim Ziemba replied
try configuring the CMS -port setting in the CCM,
But instead of picking -port 6400 choose server:port(where server = the system name you are attempting to login to from deski). I resolved a similar issue with this before but not sure it will work in your case.
Can you open a message with support? You may need the help of an engineer on this one.