go to post John Murray · Jan 8, 2018 Try port 57772.In other words, use the same port number as you use when accessing InterSystems Management Portal.
go to post John Murray · Jan 8, 2018 See also my post here which documents how to set up %ALL, and how it doesn't actually apply to 100% of your namespaces.
go to post John Murray · Jan 8, 2018 Well, the %Z* names were safe from overwrite by InterSystems, until they came out with the %ZEN package
go to post John Murray · Jan 3, 2018 A CACHE.DAT database file can be mounted, read and modified by any instance of Caché, including one running "locally", by which I assume you mean "on your workstation".
go to post John Murray · Jan 3, 2018 Congratulations to the Atelier team for releasing 1.1. However I'm still disappointed that suggestions #2 and #3 which I made more than 18 months ago haven't (yet) been taken up. IMO they'd significantly improve the usability of part of the Atelier Explorer (AE).
go to post John Murray · Jan 3, 2018 In which case, please mark one of the Answers as "accepted". This helps the Developer Community spot questions that haven't yet been answered to the satisfaction of the OP.
go to post John Murray · Jan 2, 2018 I don't know of any publicly-accessible InterSystems servers you could point your Atelier at. You probably need to set up your own. It must be version 2016.2 or later.
go to post John Murray · Jan 2, 2018 I also have a hunch that if your webserver is prepared to serve HTTP then it may be sufficient to make some server-side settings in Portal on your Caché / Ensemble server, as follows.The settings are WebServerName, WebServerPort, and WebServerURLPrefix. These can be found in the Startup Settings ([System Administration] > [Configuration] > [Additional Settings] > [Startup Settings])Doing this may mean you don't need to get each Studio user to change their settings. But it seems possible the server-side settings won't be able to make Studios use HTTPS for templates and add-ins rather than HTTP.
go to post John Murray · Jan 2, 2018 For the record, I checked back through the old Studio versions I have access to. This setting first appeared in 2009.1.
go to post John Murray · Dec 22, 2017 Each Cache instance on your PC can run its Telnet service on a different port. Set it here:
go to post John Murray · Dec 15, 2017 It shouldn't matter to you. I suggest you just ignore results that begin with "^"
go to post John Murray · Dec 15, 2017 As noted by Keith Avery in his comment, the ListAll classmethod of %SYS.Namespace may also include implicit namespaces. This is mentioned in the class doc. I haven't verified, but I guess that you may get different results from ListAll() if you run it once immediately after Cache startup and again after Portal has been used to change namespace definitions (e.g. mappings).ListAll() is implemented using calls to the undocumented $ZUTIL(90) function. I dug up some WRC information we received in 2010 about a change in behaviour in that function starting with Caché 2010.2. The summary was:SML1081 - Support single namespace activation and reduce usage of mapping memory.
go to post John Murray · Dec 13, 2017 I strongly recommend you contact InterSystems Support (a.k.a. WRC) for assistance. See https://www.intersystems.com/support-learning/support/ for details.
go to post John Murray · Dec 13, 2017 Maybe this post will help you:https://community.intersystems.com/post/configuring-cach%C3%A9-client-ap...
go to post John Murray · Dec 12, 2017 Per Michelle's answer, moving up to the 1.1 beta may be worthwhile for you. See http://docs.intersystems.com/documentation/atelier/UpdateNotes-1.1.html for what it currently includes, plus instructions on how to get it.
go to post John Murray · Dec 12, 2017 There are two versions of Atelier currently available. Are you using 1.0 or the 1.1 Beta?
go to post John Murray · Dec 6, 2017 It's possible that a Solaris patch could have broken something. I strongly recommend you contact WRC about this.
