Question
· Sep 27

Local Ensemble instance clashing with another application's local client

We are doing healthcare interface development.

Developers have Ensemble installed locally on their laptops - code will be developed locally then deployed to integration, test/UAT and ultimately production servers in due course.

One of the other applications we are developing around happens to utilise an Iris desktop client to a remote Iris server. We want to have the application available on the developers laptops alongside the local Ensemble instance.

✅ It appears that if we install their desktop client then install our local Ensemble server, things work.

❌However, if we install a local Ensemble instance then the desktop client, their installation process breaks the local Ensemble instance.

When you do it the correct order the Cache Server Manager shows the local instance, the integration/test/production instances, plus the Iris instance related to the application. When you do it in the "wrong" order Cache Server Manager only shows the Iris instance related to the application. We don't want to have to rely on this ordering - a local Ensemble instance may have multiple namespaces set up, relating to various on-going development we don't want to have to recreate just to install the desktop client for the other application...

We can't figure out where Cache Server Manager stores its list of available instances - filesystem and Registry browsing so far not showing anything obvious!

We are taking it up with the supplier of the application, but in the meantime where might we look to "remind" Cache Server Manager about the local, integration, test and production servers it appears to have "forgotten" about when the application was installed? Developers are on Windows 10 laptops.

Product version: Caché 2018.1
$ZV: Cache for Windows (x86-64) 2018.1 (Build 184U) Wed Sep 19 2018 09:09:22 EDT
Discussion (3)2
Log in or sign up to continue

@Colin Brough - values for Cache Server manager are stored in the registry.  If these servers are using CCR, you can actually download registry keys directly from you CCR System page (above Environments select Export > Studio) and load it onto a developers desktop in order to have the Environments automatically show up in the Caché Server Manager.  If these are not CCR-controlled, then you can create a .reg file similar to the following in order to pull them in (this was generated by CCR for an internal System and I have modified a few fields; the last two entries change Studio to have a red background on LIVE to make it easier to see where you are located):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\InterSystems\Cache\Servers\ISCU-Demo-BASE]
"Address"="base.demo.iscdemo.com"
"AuthenticationMethod"="0"
"Comment"="This has been created by the CCR system export."
"ConnectionSecurityLevel"=""
"LastNamespace"=""
"Port"="51773"
"ServerType"=""
"ServerPrincipalName"=""
"Telnet"="22"
"WebServerAddress"=""
"WebServerInstanceName"=""
"WebServerPort"="443"
"HTTPS"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\InterSystems\Cache\Servers\ISCU-Demo-BASE]
"Address"="base.demo.iscdemo.com"
"AuthenticationMethod"="0"
"Comment"="This has been created by the CCR system export."
"ConnectionSecurityLevel"=""
"LastNamespace"=""
"Port"="51773"
"ServerType"=""
"ServerPrincipalName"=""
"Telnet"="22"
"WebServerAddress"=""
"WebServerInstanceName"=""
"WebServerPort"="443"
"HTTPS"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\InterSystems\Cache\Servers\LIVE-ISCU-Demo]
"Address"="monitor.iscdemo.com"
"AuthenticationMethod"="0"
"Comment"="This has been created by the CCR system export."
"ConnectionSecurityLevel"=""
"LastNamespace"=""
"Port"="51773"
"ServerType"=""
"ServerPrincipalName"=""
"Telnet"="22"
"WebServerAddress"=""
"WebServerInstanceName"=""
"WebServerPort"="443"
"HTTPS"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\InterSystems\Cache\Servers\LIVE-ISCU-Demo]
"Address"="monitor.iscdemo.com"
"AuthenticationMethod"="0"
"Comment"="This has been created by the CCR system export."
"ConnectionSecurityLevel"=""
"LastNamespace"=""
"Port"="51773"
"ServerType"=""
"ServerPrincipalName"=""
"Telnet"="22"
"WebServerAddress"=""
"WebServerInstanceName"=""
"WebServerPort"="443"
"HTTPS"="1"

[HKEY_CURRENT_USER\Software\InterSystems\Cache Studio\Editor\Server Background Color]
"LIVE-ISCU-Demo"=dword:00a0a0ff

[HKEY_CURRENT_USER\Software\InterSystems\Cache Studio\Editor\Status Bar Color]
"LIVE-ISCU-Demo"=dword:005757ff 

Hope this helps!

Ben