We might have some developers on the Community using HealthShare who can give you tips here. But I think that the best way to move forward, since these are reasonably broad questions, will be to reach out to your InterSystems Sales team or Support. The answers to many of your questions will probably be better with more information about your current development process and Sales/Support can discuss the specifics with you.

Your Atelier server connection information is stored in Eclipse's secure storage file. The secure storage file is shared among different workspaces created in the same Eclipse client. You can see the location of this file in your Eclipse preferences under General > Security > Secure Storage > Contents > Storage location.

The location of the secure storage file depends on the directory in which Eclipse was installed. If you want a second install with an independent list of server connections, you will need to install the second Eclipse client in a new directory.

Hi Trevor, this has been reported to development (internal code ATL-3359). The ability to filter out system files in the Atelier Explorer view is currently targeted for an Atelier 1.5 release.

I'll look into the Developer Community tag options. Regardless of the tag selected it never hurts to mention the build number in your post as well.

Currently (with Atelier 1.1.391), opening and editing class, routine and csp files are supported. The BPL and DTL graphical editors are also fully supported. Beyond that, more inclusive Ensemble support is targeted for Atelier 2.0. Keep an eye on announcements in the Atelier group in the Developer Community and Atelier release notes for information about upcoming versions.

This has been reported and corrected (development code CDS2960). This required a server-side change that appears in 2017.1.3, 2017.1.4 and 2017.2.2. Can you send your Caché/Ensemble/HealthShare version string so that I can confirm you do not already have a version with this fix? You can get that by clicking the About link in the top-left of the System Management Portal.

This should be the web server port. The PKIX error usually indicates an issue with HTTPS (such as the web server expecting HTTPS but receiving an HTTP request). The "Connection refused" message could mean that the path for the REST requests made by Atelier are not being properly served to the CSP Gateway.

As Francisco mentioned, you can give this a try with the private Apache web server (by default listening on port 57772) which should be able to serve the REST requests from Atelier out of the box. That will give us a baseline of whether you can connect your Atelier client to the server.

I would suggest opening a WRC case so that a Support advisor can get specifics about the web server you are using and how that is configured.

Fabian's comment is the correct solution. The Atelier client makes REST requests to the server, and those requests start with /api/atelier. So you need to set up a mapping for "/api/atelier*" on the web server listening on port 80 to route those requests to the Caché server.

Hi Mike, I know you already figured this out yourself but just wanted to write up some instructions for others who find this post.

The Eclipse documentation will contain separate sections for each plug-in. To filter on only the "InterSystems Atelier User Guide":

  1. Select the Scope link next to the search box
  2. Pick the radio button for "Show only the following topics"
  3. Click the New button
  4. Check the Atelier guide and give this scope a name
  5. Click OK > OK

The documentation is also available online here, where it contains only the Workbench and Atelier User Guides.