I just took a quick look through some past InterSystems Support cases. I haven't seen this error reported to the WRC before.
There is not an obvious/general reason for this error. I would suggest opening a WRC case to investigate this issue on your system (either by emailing support@intersystems.com or calling +1 617-621-0700).
This solution is now written up more cleanly in a Developer Community post here.
All set, John. You should see WRC 899885 when you log into the WRC application.
Hi John, yes this is still on the dev team's radar. There is a development issue filed to address it. However it is not a high priority at the moment. Let me know if you'd like me to create a WRC case in your name linked to that dev issue so that you can monitor its progress in your WRC application.
Right you are John. I sent you the wrong flag+StackOverflow page, sorry about that. The command-line flag you'll want to add is:
-clearPersistedState
This will clean persistent workbench data. Then you'll need to re-open the Atelier perspective, or the Atelier views that you use.
Hi, John - thanks for pointing this out. You'll want to run Eclipse with the -clean argument to clear all cached plug-in data. There's a good discussion about that on StackOverflow here.
I'd suggest adding the clean argument by launching Eclipse from the command line (less risk than adding it to the eclipse.ini and forgetting to remove it).
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.
Hi Dieter, I think that we'll need to collect some system-specific information to debug this further. The best next step will probably be to open a WRC case to investigate (by emailing support@intersystems.com or calling +1 617-621-0700).
I think the best next step will be to file a WRC case (by emailing support@intersystems.com or calling +1 617-621-0700). There is some system-specific info that we'd like to collect to try and debug this further.
I'm not sure exactly how Eclipse decides where your secure storage file should be located. I thought it had to do with where the application was installed, but after doing a bit more research I think it may be a hard-coded location. I Googled "changing eclipse secure storage location" and found this in the Eclipse documentation:
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.
What exactly have you tried so far? What version of Atelier are you using? What version of Caché/Ensemble/HealthShare?
I would suggest contacting the WRC (by emailing support@intersystems.com or calling 617-621-0700) to get further help on this. A Support advisor will be able to give you one-on-one help to get to the root of the problem on your system.
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.
Thanks for the additional information. This has been fixed in later server versions but, as John mentioned, those have not been released yet. If you need this fix now we will have to provide it in a patch kit (Adhoc). Note that our Adhocs do not go through our full suit of QD tests . You will need to contact the WRC (support@intersystems.com) to request an Adhoc.
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 Atelier team is working on this navigation feature. The Atelier Explorer and Server Explorer are scheduled to be improved with the 1.2 release (although it has not yet been implemented, so we can't guarantee the version).
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:
This is on the Atelier team's radar. There is an internal bug report to get this implemented. It is currently categorized as a low priority and targeted for Atelier 1.5. I just noted in that report that a customer requested this feature and linked to this DC post.
If you (or any of you other customers out there) would like to discuss changing the priority on this report, I'd suggest filing a new WRC case with Support. Our Support team can have a conversation with you about your specific needs then make the case with development.
The Atelier/Eclipse equivalent for jumping to a class/routine/macro referenced in the code you are looking at is F3 (or Open Declaration in the right-click context menu):
I don't know of an exact Eclipse equivalent for Studio's bookmarks. An Eclipse bookmark can be set on the line your cursor is at by going to Edit > Add Bookmark. Then you can open the Bookmarks View (Window > Show View > Bookmarks) to see a list of your bookmarks and double-click them to navigate to that line in the code:
The go to tag+offset feature is still in development for Atelier. It is a very high priority and should be coming in an upcoming version soon.
Here are another couple of keyboard shortcuts that I often use for Eclipse/Atelier navigation:
Ctrl+O (or cmd+O on a Mac) shows Atelier's Quick Outline, where you can see a list of members for a given class/routine. Hitting ctrl/cmd+O again shows the inherited members. You can start typing in this view to narrow down the members listed:
I also use Eclipse's go back and forward navigation commands to jump back and forth as I'm viewing/editing code. To go back you can use Navigate > Back, ctrl+[ on Windows or cmd+[ on Mac. To go forward it's Navigate > Forward, ctrl+] or cmd+].
Ctrl+Shift+R and Ctrl+Shift+T (again, cmd instead of ctrl on a Mac) can be used to open a resource or an Atelier class/routine, respectively, that exists in a local project. The "Open Atelier Class/Routine" dialog (Ctrl+Shift+T) will show server-side files in an upcoming version of Atelier.
There is also a page in the documentation on Atelier equivalents for Studio actions here.
Thanks for checking in, Wolf. You are correct - the bug is with the recognition of the end of a class query. This can present itself in many ways and cause other parser issues throughout the code.
This has been corrected starting with Atelier 1.2. The fix will therefore be available with the next beta update, which we expect to be coming in February.
Thanks for pointing this out, William. I'm going to report it to the Atelier development team to see what we can do.
You can also see this information in the Atelier Documentation view as you are moving focus within a class. If you do not see this view you can launch it by selecting Window > Show View > Other > Atelier > Atelier Documentation > Open.
For example, I opened Sample.Person on my local Atelier client, selected the tab at the bottom for Atelier Documentation, then clicked on "%Populate" in the list of superclasses. Now I can see this in the Atelier Documentation view:
Hi Fabio, thanks for the detailed information on using the Atelier debugger to attach to a process!
It looks like you posted this as a question instead of as an article. So it will show up as an unanswered question until an "answer" is posted. I'm adding this as an answer to fix that.
Vivek, if Fabian's suggestion is the solution that works for you can you mark that as the correct answer here? Thanks!
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.
John - I'm going to create a WRC case for you and link the associated enhancement requests so that you can see the status as these progress.
The way to test out Atelier is to install Eclipse and download the Atelier plug-in. Then you can connect that to any 2016.2+ instance. As Eduard mentioned you can do that by following the instructions here: www.intersystems.com/atelier.
If you want to learn more about Atelier without installing, there are a number of InterSystems docs where you can read about the new development environment.
The Atelier documentation has a lot of information on getting started:
The Atelier release notes outlining bug fixes and new features can be found here:
https://docs.intersystems.com/documentation/atelier/index.html
The Caché documentation has a number of sections that mention Atelier, such as:
http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GSTD_atelier
http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GCRN_new20172_atelier
There is also an Atelier playlist on the InterSystems Developer Community YouTube channel with a mix of introductory and more advanced/targeted videos:
https://www.youtube.com/playlist?list=PLKb2cBVphNQT11WwvAN59idx2CZTkK9CA