go to post John Murray · Jan 9, 2018 Using my DC mod superpowers I changed this post from a Question into an Article.
go to post John Murray · Jan 8, 2018 The page at http://www.georgejames.com/ws/ looks like this:Use the link I've highlighted.You may also need some of the Hints & Tips entries, and/or Patches entries.If you get stuck I suggest you contact me directly, using the "John Murray" link near the top of that page.
go to post John Murray · Jan 8, 2018 Brian, if you don't mind using 20-year-old software, the link in my previous reply goes to a page from where I think MSM-Workstation can still be downloaded.
go to post John Murray · Jan 8, 2018 I have removed the "Developer Community FAQ" tag from this post. Please do not use this tag.
go to post John Murray · Jan 8, 2018 What sort of webserver is at http://xyzx.x.edu ?How was it set up and configured to use CSP Web Gateway?I suggest you contact InterSystems Support (a.k.a WRC) for help resolving your issue.
go to post John Murray · Jan 8, 2018 No, it's not possible to do this with Caché.Some old-timers (like myself) may recall MSM-Workstation, which could do this kind of thing.
go to post John Murray · Jan 8, 2018 That'll be the problem, because /api/atelier is how Atelier talks to the server.
go to post John Murray · Jan 8, 2018 OK, I've just seen your version info in a comment on another answer.Given you're using accessing port 80 on server xyz.x.edu I assume a regular webserver (e.g. IIS or Apache) has been set up on that server and the CSP Web Gateway added to it, then configured to connect to an InterSystems instance (perhaps on the same server, or perhaps elsewhere).In that case, is your webserver set up to dispatch /api/atelier to the 2017.1 instance?
go to post John Murray · Jan 8, 2018 So does the following URL (or similar) give you access to Portal on the remote server?http://xyz.x.edu/csp/sys/UtilHome.csp
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.
