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.

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.

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.

That'll be the problem, because /api/atelier is how Atelier talks to the server.

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?

What is the $ZVERSION string of the remote server?

So does the following URL (or similar) give you access to Portal on the remote server?

http://xyz.x.edu/csp/sys/UtilHome.csp

Yes, that's what I mean.

Well, the %Z* names were safe from overwrite by InterSystems, until they came out with the %ZEN package

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.

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.

For the record, I checked back through the old Studio versions I have access to. This setting first appeared in 2009.1.

Each Cache instance on your PC can run its Telnet service on a different port. Set it here:

It shouldn't matter to you. I suggest you just ignore results that begin with "^"

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.

It's possible that a Solaris patch could have broken something. I strongly recommend you contact WRC about this.