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.

The presentation will be available in about a week or so. It will be available on learning.intersystems.com.

If I understand correctly, you are looking for the DTL graphical editor within Atelier? To do this you will want to open the DTL class code, then right-click in the editor and select "Open diagram editor". You can find a previous post with more detail here:

https://community.intersystems.com/post/how-edit-business-process-and-data-transformation-files-atelier

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.

There are currently no plans to merge the Atelier documentation with the docs for other InterSystems technologies (Caché, Ensemble, HealthShare, InterSystems IRIS Data Platform). Atelier is a separate product and will continue to have its own documentation that follows industry standards for Eclipse plug-ins.

You can do this in Atelier by placing the cursor on the class/method and clicking F3. You may want to take a look at the Atelier Equivalents for Studio Actions section of the Atelier documentation for other similar tips.

You can enter the arguments to pass into a Run/Debug Configuration here:

I'm not sure what you mean by the "select class file" that you are trying to pass in. Here is the method signature for %UnitTest.Manager/DebugRunTestCase:

ClassMethod DebugRunTestCase(testsuite As %String = "", testcase As %String = "", qspec As %String = "", testmethod As %String = "", ByRef userparam) As %Status

Which parameter are you trying to pass in?

Thanks for reporting this Peter. It looks like Atelier is not properly recognizing the end of a class' Query member. I found a couple other ways that this issue presents itself - a syntax error on the closing bracket of the class before you compile, and any class members following the Query are not listed in the Outline.

I logged this bug for the Atelier development team (internal reference ATL-4372).

Hi Shobha, here is the relevant documentation about using Ensemble with SOAP:

http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY…

This should give you some background about using Ensemble to send and receive SOAP messages. I would suggest reviewing this and letting us know if you have any specific questions, configuration problems, errors, etc. You can also reach out to Support or your InterSystems Sales team with more involved questions that might be easier to discuss on the phone rather than in the Developer Community.

Hi Jean,

I tried out the Eclipse SQL Explorer and was able to connect to my local instance just fine. I installed the plug-in using the update site from the link you provided, http://eclipsesql.sourceforge.net/.

Then I opened the associated perspective by going to Window > Perspective > Open Perspective Other > SQL Explorer. I right-clicked in the Connections view and hit New Connection Profile. I had to select Add/Edit Drivers to add the Caché JDBC driver with these settings:

The keys were to 1) select the Extra Class Path tab and Add JARs to pick the JDBC driver from my Caché install directory and 2) to add the correct Driver Class Name, com.intersys.jdbc.CacheDriver.

Once I had that configured I selected it in the Connection Profile Wizard, entered my JDBC connection URL, jdbc:Cache://localhost:56773/SAMPLES, and selected the authentication information:

This also worked for me when I unselected "Username is not required", checked "Auto Logon" and entered my Caché credentials.

I right-clicked the connection and hit Connect. Then double-clicking the connection (listed as "Connected since <timestamp>") opened the connection in the Editor where I could enter my SQL statement:

Where are you running into problems?

You can use the Outline view in Atelier for information about the current class' properties, parameters, class methods, etc:

There is an enhancement request to show inherited members in the Outline view which is currently planned for Atelier 1.1.

Atelier's code completion, which can be accessed by hitting ctrl+space, is also a good tool here. For example you can use code completion to quickly check the possible options for an index's keywords (with documentation):

When you generate an HTML Zen Report that request is served through the web server. It looks like on your system: in the case of the IIS web server using the alias name rather than the IP address and IE 8+, some of the static files are not being served properly. I think this would be best investigated by Support in a WRC case. You can open up a new case by emailing a brief description to support@intersystems.com, or by calling the Support line at (617) 621-0700.